default route brokeness

Mike Hoskins mike at
Wed Sep 24 20:56:07 PDT 2003

On Wed, 24 Sep 2003, Mike Hoskins wrote:
> On Wed, 24 Sep 2003, Mike Tancsa wrote:
> > RELENG_4.  Make sure you have
> > smtp3# ident /usr/src/sys/netinet/if_ether.c
> > /usr/src/sys/netinet/if_ether.c:
> >       $FreeBSD: src/sys/netinet/if_ether.c,v 2003/09/24 21:48:00
> > bms Exp $
> > smtp3#
> mike at eng{mike}$ uname -a
> FreeBSD 4.8-RELEASE-p8 FreeBSD 4.8-RELEASE-p8 #14:
> Tue Sep 23 17:30:45 PDT 2003
> mike at  i386
> mike at eng{mike}$ ident /usr/src/sys/netinet/if_ether.c
> /usr/src/sys/netinet/if_ether.c:
>      $FreeBSD: src/sys/netinet/if_ether.c,v 2003/09/23
> 16:44:58 bms Exp $

i assume these are related as well,

Sep 24 20:51:58 eng /kernel: arplookup failed: host is not on
local network
<many snipped>

10.0.101/24 is a local (obviously), directly connected net.  i.e.

        inet netmask 0xffffff00 broadcast
        ether 00:02:b3:a1:97:01
        media: Ethernet 100baseTX <full-duplex>
        status: active

it serves NFS, Samba, DNS, etc. clients.  worked perfectly before the
upgrade.  now (from upgraded server to 10.0.101/24 client),

mike at eng{mike}$ ping
PING ( 56 data bytes
64 bytes from icmp_seq=0 ttl=63 time=0.383 ms
64 bytes from icmp_seq=1 ttl=63 time=0.408 ms
--- ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.383/0.395/0.408/0.013 ms

works great but (from 10.0.101/24 client to directly connexted fxp1),

eth0      Link encap:Ethernet  HWaddr 00:90:27:FC:76:CB
          inet addr:  Bcast:  Mask:
          RX packets:926 errors:0 dropped:0 overruns:0 frame:0
          TX packets:505 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:53417 (52.1 Kb)  TX bytes:54208 (52.9 Kb)
          Interrupt:22 Base address:0xece0 Memory:fafff000-fafff038

bash-2.05$ ping
PING ( from : 56(84) bytes of data.

--- ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss

does not.  per the entries in /var/log/messages on the newly upgraded
server it seems to be an arp issue...  but why only start now?  i'm
holding off on upgrading any other boxes, but want to get the SSH updates
ASAP.  any idea when networking on 4.8-pX will be stable again?



From: "Spam Catcher" <spam-catcher at>
To: spam-catcher at
Do NOT send email to the address listed above or
you will be added to a blacklist!

More information about the freebsd-stable mailing list