NavigationUser loginSpam?See spam posts on this site? If so, please don't reply to the spam! Instead, just report the URL to the webmaster. |
Accessing my network wirelesslyHi folks, I have my desktop connected by ethernet to an ADSL modem which connects me to the outside world. The modem looks after most of the networking (DHCP, NAT translation, firewalling, etc) but set up so the desktop has a static IP and all ssh traffic to the network is directed to it (nothing else is let through from the outside world). I have one or two other machines that attach to the network from time to time. They also connect to the modem via ethernet. My employer has just graced me with a Toshiba Tecra laptop, complete with Centrino processor, which means I can (theoretically) connect to my home network wirelessly. It's running an up to date (?) copy of Windows XP Pro. My desktop has an old wireless card in it. I have installed it, sorted out modules and so on. I have even been able to assign an IP number to it. I presume the thing is working, but given the lack of wireless services in my neighbourhood that's a little hard to tell. My wish is to be able to use the wireless abilities of my desktop and the laptop to allow the laptop to access my desktop (via ssh) and the internet (via the modem/router.) It all looks so simple to do, and a lot of the reading I've done suggests it's insanely easy. The only problem is I can't figure out how to get everyone talking to each other. Ideas? |
easy
1. set up the wireless PC card and make sure you set encryption keys etc - the latest wireless tools plus a decent card should allow you to set up WPA-PSK type encryption. You may set a static IP for the wireless card - use a unique subnet, not the same as used to talk to the modem.
2. do the same on your WinDos computer (set up for 'peer'), and set a static IP address similar to your desktop. Ping your desktop and see that the desktop can also ping WinDos. At this point you may give WinDos a DNS address (usually the router/modem) and a gateway (the wireless static IP of your desktop). At this stage WinDos cannot actually access any of that.
3. set up NAT on the desktop (you can use the ipmasq tool). At this point WinDos should be able to ping the modem and also resolve names.
That should all be done. Of course for better security you can force the desktop to tunnel absolutely everything on wireless via ssh - that just depends what you need.
Another alternative to the all-static wireless addresses is to set up a dhcp server on your desktop; you may also put in a bind9 server to provide name resolution.