[geeks] networking notworking complete with unusual routing
Charles Shannon Hendrix
shannon at widomaker.com
Thu Dec 21 20:32:48 CST 2006
Thu, 21 Dec 2006 @ 19:07 -0500, Charles Shannon Hendrix said:
> I finally got all the pieces together to have dual WAN access from my
> home LAN. However, for some reason I can't make it work, even though
> I've done this in the past several times.
Just a few more details:
My posting had an error: I'm not using a WAP, I'm using a WGA for the
wireless bridge.
I did some more testing, and I can still confirm that my NetBSD machine
can ping the wireless NAT box on the other LAN:
escape# ping 192.168.100.1
PING 192.168.100.1 (192.168.100.1): 56 data bytes
64 bytes from 192.168.100.1: icmp_seq=0 ttl=64 time=1.965 ms
64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=2.070 ms
(escape is the name of my Ultra 1)
(192.168.100.1 is the NAT box (WRT54G) on the wireless LAN)
Routing tables:
escape# netstat -nrf inet
Routing tables
Internet:
Destination Gateway Flags Refs Use Mtu Interface
default 209.163.126.59 UGS 4 9703 - ppp0
127/8 127.0.0.1 UGRS 0 0 33136 lo0
127.0.0.1 127.0.0.1 UH 3 186 33136 lo0
192.168.1/24 link#1 UC 4 0 - hme0
192.168.100/24 link#2 UC 3 0 - hme1
192.168.100.1 00:13:10:8d:3a:6d UHLc 0 1850 - hme1
192.168.100.101 00:13:d3:38:37:c5 UHLc 0 7 - hme1
192.168.100.250 00:18:39:08:d2:29 UHLc 0 369 - hme1
209.163.126.59 69.72.100.1 UH 1 0 - ppp0
If I go to any of the other three machines on the 192.168.1.0 LAN, and
try to connect to 192.168.100.1 on any port, it doesn't work.
All of them can connect to hosts on the ISP side fine, so forwarding
does work on the system.
--
shannon "AT" widomaker.com -- ["The object of war is not to die for your
country but to make the other bastard die for his." -- General George S.
Patton]
More information about the geeks
mailing list