Free internet at my house!
Robert.Edwards at anu.edu.au
Thu Jun 13 12:11:49 EST 2002
Use routing instead of bridging onto your wireless network (you will
have to use NAT in any case to get onto your ADSL link). Then use
CIPE for your encryption/authentication - works fine on Linux (comes
standard in RH7.2 and 7.3) and Win2k, doesn't work for Win98 though.
Can use DHCP easily (useful if you also want to use your wireless
laptop on other networks). Basically, set up another subnet (other
than the one you are using for your wired network) and ocnfigure
the DHCP server to issue IP addresses onto that subnet. Better to
use a "fixed-address" for your laptop as then the CIPE startup can
always know that it is using the same IP address.
This is more or less how I have it set up at home.
Michael Still wrote:
> Hey all.
> I have wireless. It is bridged to my wired network on the firewall
> machine, using the kernel ethernet bridging. It looks something like:
> <<<scary wireless>>> <<<telstra adsl>>>
> | |
> | ********************* |
> |-----------------> br0 eth1 <---------
> * *
> * eth0 *
> * ^ *
> * | *
> <<<wired network>>>
> The bridge between br0 and eth0 currently pushes all traffic -- which is
> obviously not a good thing.
> Anyway, I am after suggestions on how to do the crypto thing which meet
> these criteria:
> - I would still like to use DHCP for ip addresses on wireless machines
> (denial of service on the IP address range doesn't bother me much)
> - Yay crypto on the wireless stuff (ipsec?)
> - It needs to work with linux, and win2k
> - I'm most concerned with people yoinking ADSL bandwidth than protecting
> my internal network, which is fairly secure...
> Any suggestions?
> Michael Still (mikal at stillhq.com) UMT+10hrs
More information about the linux