ra ra routing!
silly techy post.
We've got a wired and a wireless network here, and I was trying to get some uber-encrypted VPN solution to move data between them. Turns out you just do it like this:
Wireless Network: 10.0.1.1-255
Wired Network: 192.168.1.1-255
Gateways are .1
Wireless+Wired linux box (default gateway for wired users):
echo 1 > /proc/sys/net/ipv4/ip_forward
route add -net 10.0.1.0 netmask 255.255.255.0 gw 10.0.1.1
Internet router (default gateway for wireless users):
route add -net 192.168.1.0 netmask 255.255.255.0 gw 192.168.1.1
Obviously this isn't as perfect as the VPN bridging because its layer 3 routing so only TCP/IP will move across. But that stuff is *hard* and *slow* and let's face it, when are you going to use IPX/IPSec/X.25/DDP-AppleTalk?
We've got a wired and a wireless network here, and I was trying to get some uber-encrypted VPN solution to move data between them. Turns out you just do it like this:
Wireless Network: 10.0.1.1-255
Wired Network: 192.168.1.1-255
Gateways are .1
Wireless+Wired linux box (default gateway for wired users):
echo 1 > /proc/sys/net/ipv4/ip_forward
route add -net 10.0.1.0 netmask 255.255.255.0 gw 10.0.1.1
Internet router (default gateway for wireless users):
route add -net 192.168.1.0 netmask 255.255.255.0 gw 192.168.1.1
Obviously this isn't as perfect as the VPN bridging because its layer 3 routing so only TCP/IP will move across. But that stuff is *hard* and *slow* and let's face it, when are you going to use IPX/IPSec/X.25/DDP-AppleTalk?