Wireless bridge routing problem
- From: "pvl" <pvl@xxxxxxxxxxxx>
- Date: 10 Jan 2006 03:37:28 -0800
We have a strange routing / firewalling problem involving a wireless
We connected a computer (call it PC1) to our firewall (interface eth4)
using a cross-over cable. The firewall is connected to two other
networks as well: the DMZ on eth1 and our internal network on eth0. It
runs iptables and also does some source-based routing which I don't
think is relevant.
In the above configuration, PC1 can ping any machine on the DMZ and our
internal network as well as eth0 and eth1 themselves.
The moment we replace the cable with a wireless bridge (two AP's in
point-to-point mode), PC1 can no longer reach the other networks
connected to the firewall. It can however still ping eth0 and eth1.
If I ping PC2 (located on the DMZ) from PC1 the icmp packets reach eth4
according to tcpdump. That is the last time I can see the packet. It is
definitely never sent out on eth1 as expected.
I can however fix the problem by going to PC2 and pinging PC1. This is
successful and also causes the ping requests from PC1 to be passed on
to PC2. From that point on, everything works untill the firewall is
restarted. I also have to do this for each machine I want to reach from
I suspect that the problem lies with ARP requests and the neighbor
tables on the firewall not being updated, but I cannot see problems.
How dow I solve this?
Any help will be appreciated.
- Prev by Date: Re: Find where diskspace is being used up most
- Next by Date: linux-2.4 IPStack Profiling
- Previous by thread: can not ping on two virtual nic cards
- Next by thread: linux-2.4 IPStack Profiling