• Thomson SpeedTouch 780WL – port forwarding to broadcast address

    For your home network to be able to wake-on-lan a computer from the Internet so that you could later remotely access it, you need to forward a port to your broadcast address. This way you can broadcast a magic packet to all the computers in your network and then wake only one of them using its MAC address.

    If you are reading this, you probably already tried forwarding a port to 255.255.255.255 but to no avail. That is because ST780 just drops anything forwarded to the broadcast address.

    So, what you should do is choose one unused IP address in your subnet and make it appear like it’s a broadcast address, and later do the port forwarding to that IP. How to do that? Telnet into your router, and assign a hardware (MAC) address of FF:FF:FF:FF:FF:FF (when translated to IP, that MAC address makes 255.255.255.255) to the chosen IP address. This is the basic idea behind this tutorial and a way to trick the router into doing the port forwardng to a (fake) broadcast address. So, do the following:

    1
    telnet <router_ip_address>

    enter your superadmin username and password and execute the following two commands:

    1
    2
    :ip arpadd intf=LocalNetwork ip=192.168.1.xxx hwaddr=FF:FF:FF:FF:FF:FF
    :saveall

    where xxx is the last octet of your chosen IP address (make sure that the chosen IP is not already in use, and that it’s not 192.168.1.255).

    Now go to your routers webinterface and create an application with UDP port 9 (to make it a little bit more secure, I recommend you choose a port above 1024, and then translate it into 9). Assign the created application to a newly created IP address (192.168.1.xxx) and voila, you got it.

    Now you can try and use wol (for Linux) or this one (for Windows) to remotely turn on your computer. For this you will need your routers public address (I recommend using DynDns for that), and the MAC address of the computer you want to wake up.

    cheers =)

  • Using irssi as proxy for pidgin

    If you would like to use irssi on a remote server so that it works as proxy for pidgin, you should already have ‘server’ and ‘network’ parameters set up in your ~/.irssi/config . If you don’t know what I’m talking about, take a look here and also examine the config file. You should figure it out pretty fast how to configure irssi to do basic stuff it is supposed to do.

    What you will also need is GNU screen installed on the remote server. So, what is screen? “Screen is a full-screen window manager that multiplexes a physical terminal between several processes, typically interactive shells.” Basically what you can do with it is that you can run certain processes and put them into the background (detach from them), and than later see them again (attach to them) when you want to. If you don’t know how to use screen, take a look here, or use google to find a tutorial on using screen. There is plenty of them out there. You will need screen to put the running irssi into the background on your server so that you may disconnect from the remote server after you set irrsi up.

    So, after you have got your irssi configured and running under screen, you will have to load the proxy plugin for irssi, set a password for your future pidgin-to-irssi connection and bind one free port to irssi for sharing server connection. Here is how to do it:

    1
    2
    3
    /LOAD proxy
    /SET irssiproxy_password <password>
    /SET irssiproxy_ports <network>=<port>

    where the parameter is a network name you configured earlier, and

    is the port number you want to bind irssi to.

    The final step is to configure your pidgin client to connect to your remote server. In pidgin, go to accounts -> manage accounts and then add a new IRC account. Fill the following parameters:

    1
    2
    3
    4
    Username: <network name from your config file>
    Server: <IP address or hostname of your server>
    Password: <password you set for irssiproxy>
    Port: <port number you used for binding>

    Keep in mind that you should have your irssi running all the time on your remote server under screen for this connection to work… and, that’s all folks!

    cheers

  • Installing Backtrack3 to hard drive

    backtrack3

    Here I’ll explain how to install BackTrack3 to your hard drive, using GRUB, and keep the bootsplash since I didn’t find the proper How-to for this… I will assume you already use linux and have some distribution installed on your computer. Please read everything first, and then continue with your installation.

    First of all, download and burn the backtrack image to a CD, and then reboot to your live CD.
    Login as root and download the installer which I found somewhere on the web, and then start it…
    (If the installer opens in your browser and shows just a bunch of code, make a new file and name it BT3.kmdr an c/p the code into that file and then run the file)

    You’ll get this window:
    install

    There are a few things that need setting up:
    Source (BackTrack CD) – leave this as it is.
    Install BackTrack toput a name of the partition you want to use for BackTrack installation.
    Write new MBR (lilo.mbr) to – also leave this as it is.
    Installation methodset to “Real”.
    I use GRUB instead of LILO, so I had to check “Restore Original MBR after lilo”.

    After the installation has finished, boot to your main distribution and edit GRUB
    Add the following lines to your GRUB:

    1
    2
    3
    4
    5
    Title BackTrack3 KDE
    root (hd0,5)
    kernel /boot/vmlinuz vga=791 ro autoexecxconf;kmd
    initrd /boot/splashinitrd
    boot

    If you wish to login to console instead of KDE, use the following:

    1
    2
    3
    4
    Title BackTrack3 console
    root (hd0,5)
    kernel /boot/vmlinuz vga=791 ro
    boot

    Keep in mind that root (hd0,5) will probably be different for you since we almost sure don’t have the same partition order.

    If you liked the fancy bootsplash from the live cd, you’ll have to make it work for your installation first.
    If you used the GRUB options for KDE, when the GRUB boots, navigate to “BackTrack3 KDE” and pres “e” to temporarily edit the GRUB only for this one session so you can enable the bootsplash. Then delete the initrd line with “d”, and also edit (with “e” again) the kernel line to look like showed in “BackTrack3 console”.
    After that, boot to BackTrack and run the following command in your terminal as root:

    1
    splash -s -f /etc/bootsplash/themes/Linux/config/bootsplash-1024x768.cfg >> /boot/splash.initrd

    and reboot.

    There you go, you’re ready to use BackTrack3.

Back to top