[PLUG] Network routing

[Russell Senior]

>>>>> "Jeff" == Jeff Blain <jelque at feather.net> writes:

>>  Try running tcpdump with a -n option and post again.
>> 

Jeff> bash-2.05a# tcpdump -n tcpdump: listening on eth0
Jeff> [...] 
Jeff> 16:44:15.639729 192.168.1.2 > 192.168.0.1: icmp: echo request
Jeff> 16:44:15.641108 arp who-has 192.168.1.2 tell 192.168.0.1
Jeff> 16:44:15.652166 192.168.0.1.514 > 192.168.0.10.514: udp 58
Jeff> 16:44:16.638050 arp who-has 192.168.1.2 tell 192.168.0.1
Jeff> [...] 

Jeff> When doing tcpdump -n on my firewall it shows that packets are
Jeff> being recieved, but do not route from there.

Jeff> 10:50:24.170628 192.168.1.2 > 192.168.0.1: icmp: echo request
Jeff> 10:50:24.170628 arp who-has 192.168.1.2 tell 192.168.0.1

Yeah, you were on the right track with your earlier message.  Your
firewall needs to know where to send packets destined for 192.168.1.x.
It isn't a directly connected network, so it doesn't know what to do.
It tries ARP'ing but nothing replies.  Tell the firewall to route such
packets via your internal gateway machine, whatever that is, .10 I
guess.  You'll have to figure out the proper syntax for that in your
firewall.


-- 
Russell Senior         ``The two chiefs turned to each other.        
seniorr at aracnet.com      Bellison uncorked a flood of horrible       
                         profanity, which, translated meant, `This is
                         extremely unusual.' ''