Date: Fri, 14 Dec 2007 13:00:44 +0300 From: Eygene Ryabinkin <rea-fbsd@codelabs.ru> To: vermaden <vermaden@interia.pl> Cc: freebsd-net@freebsd.org Subject: Re: default route Message-ID: <wUt/ePVByFADK10GafSe7U4BqNU@zDuf2uv/GwxzD2XSH3XUuc8mVHc> In-Reply-To: <20071214091124.F22C91D789E@f39.poczta.interia.pl> References: <20071214091124.F22C91D789E@f39.poczta.interia.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
Good day. Fri, Dec 14, 2007 at 10:11:24AM +0100, vermaden wrote: > network 10.0.0.0/24 is put on rl0 and 192.168.0.0/16 > is on rl1, default router is set to 10.0.0.1 on /etc/rc.conf as > defaultrouter="10.0.0.1", the problem: > > When I ping some box from 10.0.0.0 network, it responds, when some box from > 10.0.0.0 network ping my box, my box responds, when I ping someone from > 192.168.0.0 network, he responds, when someone from 192.168.0.0 network > pings me my box does not response, propably packets are coming IN by rl1 > and going out by defaultgateway 10.0.0.1 so thru rl0, 1. You can inspect where the system will send the packet for the host in 192.168/16 by doing 'route get 192.168.X.Y'. In normal (or simple) conditions this should give you rl1, since 192.168 sits on that interface (provided that you didn't played with routing table manually). 2. When someone from 192.168 pings you, you can spawn two tcpdump instances: 'tcpdump -lvvni rl0 icmp' and 'tcpdump -lvvni rl1 icmp' and watch for the ICMP packets and interfaces on which they are coming in/going out. 3. Check your firewall: may be it is blocking ICMP replies to the 192.168/16. Or may be some external firewall blocks ping attempts from 192.168/16. Tcpdump should show you the overall picture. -- Eygene
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?wUt/ePVByFADK10GafSe7U4BqNU>