Hi everybody, I have 3 routers (Linux boxes with Red Hat 8.0 server), with iproute2 and ip_forward activated; they are linked together in this way: AP1------Router1---------Router2----------Router3---------AP2 AP1 and AP2 are WLAN 802.11b Cisco Aironet 350 access points. I can''t ping AP2 from Router1 and Router2 and AP1 from Router3 and Router2. Changing one of the AP with a laptop connected to Router (1 or 3) results in no effects. The routing tables seem correct. Router1 and Router3 can ping each other, so Router2 seems to make right routing. The dotted lines above are 4 different subnets. Any suggestion would be of great help! Jhonatan _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
On Wednesday, 20 November 2002, at 18:31:42 +0100, Mauro Cerboni wrote:> I have 3 routers (Linux boxes with Red Hat 8.0 server), with iproute2 and ip_forward activated; they are linked together in this way: > > AP1------Router1---------Router2----------Router3---------AP2 > > The routing tables seem correct. >But the symptoms you describe seem to tell the opposite :-(> Router1 and Router3 can ping each other, >Router1 and Router2 share a network segment, as well as Router2 and Router3. So as Router2 seems to be forwarding packets, and it has router to directly connected networks (shared with Router1 and Router3) the communication between Router1 and Router3 works. My guess is a wrong configuration of routing tables. Maybe you could try traceroute to see if packets reach the other end, or they get lost at some point. It wouldn''t be unusual for the packets to reach the destination, but be unable to return to the source, so check the routing tables and follow the path the packets would travel. Hope it helps. -- Jose Luis Domingo Lopez Linux Registered User #189436 Debian Linux Woody (Linux 2.4.19-pre6aa1) _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Mauro, Unless both Aironets have routes to each other (either default or static) they cannot communicate, and AFAIK, the Aironets are layer-2 devices with no routing capabilities. Wireless hosts behind AP1 should be able to communicate with wireless hosts behind AP2 though. Just make sure hosts at both ends have appropriate routes to each other. -----Original Message----- From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl] On Behalf Of Mauro Cerboni Sent: Wednesday, November 20, 2002 7:32 pm To: lartc@mailman.ds9a.nl Subject: [LARTC] Routing problem Hi everybody, I have 3 routers (Linux boxes with Red Hat 8.0 server), with iproute2 and ip_forward activated; they are linked together in this way: AP1------Router1---------Router2----------Router3---------AP2 AP1 and AP2 are WLAN 802.11b Cisco Aironet 350 access points. I can''t ping AP2 from Router1 and Router2 and AP1 from Router3 and Router2. Changing one of the AP with a laptop connected to Router (1 or 3) results in no effects. The routing tables seem correct. Router1 and Router3 can ping each other, so Router2 seems to make right routing. The dotted lines above are 4 different subnets. Any suggestion would be of great help! Jhonatan _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
hello,
(sorry for my bad english)
1,5 Mbit 2 Mbit
www www
| |
+---------------------------+
| LINUX Box |----- DMZ
+---------------------------+
|
LAN
most of clients in the lan are connectet to the 1,5 Mbit connection
and some are connectet to the 2 Mbit connection
the linux box has 4 network adapters
problem
the clients which are routet to the 2 Mbit couldn''t acces the
dmz
u will be able to connect the dmz from all other routes.
routes are following defined.
default --> 1,5 Mbit
table fast
default -> 2mbit
clientXX lookup table fast
dmz-Network lookup table fast
where I''ve done a mistake
I''ve tried to solve it with fw-mark but there is also the same problem
thanks for help
with friendly regards
Andre
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/