Date: Wed, 24 Sep 2003 17:12:45 +0200 From: Pawel Malachowski <pawmal-posting@freebsd.lublin.pl> To: freebsd-stable@freebsd.org Subject: Re: [full build as of Sept. 24] "No route to host" after certain time... Message-ID: <20030924151245.GA7400@shellma.zin.lublin.pl> In-Reply-To: <6.0.0.22.0.20030924103406.0307c250@209.112.4.2> References: <3F719A58.5000700@snu.ac.kr> <6.0.0.22.0.20030924103406.0307c250@209.112.4.2>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 24, 2003 at 10:34:50AM -0400, Mike Tancsa wrote:
> How do you get your default route ?
>
> Can you show
> netstat -nra
> at boot up time
> and then
> netstat -nra
> when the problems start ?
I have similar problem with my:
FreeBSD 4.9-PRERELEASE #3: Wed Sep 24 12:52:56 CEST 2003
While booting I bind IP addresses to fxp0 interface from rc.local,
after that i call `netstat -nr -f inet' to see, if routes are
complete. And they are.
However, when boot finishes (some jails are starting up etc.),
netstat command shows different routes. Typically default route
or one of local non /32 routes is absent! (sometimes default,
sometimes other /28 route, after each reboot it is different).
Before updating (from 11 Aug 4.8-STABLE) there was no such problem.
My rc.local script is something like:
LAN0=fxp0
IP=192.168.x.y
ifconfig ${LAN0} inet add ${IP}/24
route add default 192.168.x.1
ifconfig ${LAN0} inet add ${A}/28
ifconfig ${LAN0} inet add ${B}/32
ifconfig ${LAN0} inet add ${C}/32
ifconfig ${LAN0} inet add ${D}/32
# A, B, C, D are from the same /28 and everything worked perfectly in the past
> >$ ping 61.74.111.134
> >PING 61.74.111.134 (61.74.111.134): 56 data bytes
> >ping: sendto: No route to host
> >
> >------------------------------
> >
> >When I reboot, all is okay again.
--
Paweł Małachowski
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030924151245.GA7400>