Thanks Jose, I found the key in the routing table of Router2; it had bad entries for the farest subnets (didn't have the 'via' commands...). Thanks for helping me. Now I'm gonna configure the network with IPv6 'cause I have to make it work with Mobile IPv6. Anybody working on these funny things can mail me, so we can suffer togheter! :-) Bye, Mauro -----Messaggio originale----- Da: Jose Luis Domingo Lopez [mailto:lartc@24x7linux.com] Inviato: ven 22/11/2002 1.03 A: lartc@mailman.ds9a.nl Cc: Oggetto: Re: [LARTC] Routing problem 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/ ,S f)+-L)Y=jyaffvZ_j)fjb?psLmr