> > Message: 1 > Subject: Re: Routing problem > From: Ronny Aasen <list@xxxxxxxxxxxxxx> > To: lartc <lartc@xxxxxxxxxxxxxxx> > Cc: Damion de Soto <damion@xxxxxxxxxxxx> > Organization: > Date: 08 Sep 2003 08:41:46 +0200 > > On Mon, 2003-09-08 at 01:03, Damion de Soto wrote: > > gaston wrote: > > > Problem: > > > This configuration didn't work. From the clients network > (208.53.164.0) I > > > could only reach the Cisco router but was unable to reach Internet. > > > > > > The only quick solution was to connect Switch 1 with Switch 2. > > > Any ideas why this didn't work? > > > > did you have IP forwarding enabled and the appropriate iptables rules > on the linux box ? > > for pure routing: > > > > echo "1" > /proc/sys/net/ipv4/ip_forward > > iptables -P INPUT ACCEPT > > iptables -P FORWARD ACCEPT > > iptables -P OUTPUT ACCEPT > > > > If you already done that, where does a traceroute from the clients' > network > > (208.53.164.0) go ? does it try to go through 208.53.164.254? > > does it go anywhere after ? > > > in addition, was the cisco aware that the route to > 208.53.164.0/24 was thru the linux ? > > post the routing table from the cisco also. > > still good luck > -- > Ronny Aasen <list@xxxxxxxxxxxxxx> > > > --__--__-- Yes, the cisco knows that everything going to the net 208.53.164.0 goes through the linux. I did a traceroute from one of the clients to cisco's website ip: 1st hop --> 208.53.164.254 2nd hop --> Time out 3d --> Time out and so on while doing this i sniffed with ethereal: source dest 208.53.164.2 208.53.98.254(dns) standard query ptr 208.53.164.2 208.53.98.254(dns) destination unreachable 208.53.164.2 198.133.219.25 echo ping request _______________________________________________ LARTC mailing list / LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
