[full build as of Sept. 24] "No route to host" after certain time...

[Pawel Malachowski]

On Wed, Sep 24, 2003 at 11:42:14AM -0400, Mike Tancsa wrote:

> Hi, can you clarify that
> 
> >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
> 
> 
> are all out of the original /24 on LAN0 ?

No,

There are:
x.y.z/24 with one IP address, x.y.z.1 is the default route.
a.b.c.0/27 and a.b.c.32/28 with aliased addresses.

fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet x.y.z.33 netmask 0xffffff00 broadcast x.y.z.255
        inet a.b.c.34 netmask 0xfffffff0 broadcast a.b.c.47
        inet a.b.c.27 netmask 0xffffffe0 broadcast a.b.c.31
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet 127.0.0.1 netmask 0xff000000
        inet a.b.c.35 netmask 0xffffffff
        inet a.b.c.36 netmask 0xffffffff
        inet a.b.c.37 netmask 0xffffffff
        inet a.b.c.28 netmask 0xffffffff
        inet a.b.c.29 netmask 0xffffffff


Internet:
Destination        Gateway            Flags    Refs      Use  Netif Expire
a.b.c.28      a.b.c.28      UH          0        0    lo0
a.b.c.29      a.b.c.29      UH          0        0    lo0
a.b.c.35      a.b.c.35      UH          0        0    lo0
a.b.c.36      a.b.c.36      UH          0        0    lo0
a.b.c.37      a.b.c.37      UH          0        0    lo0
127.0.0.1          127.0.0.1          UH          0        0    lo0
x.y.z         link#1             UC          1        0   fxp0
x.y.z.54      00:01:02:03:04:05  UHLW        1      506   fxp0   1123


Of course I can also see in logs messages like:
/kernel: arplookup a.b.c.1 failed: host is not on local network


-- 
Paweł Małachowski