tcp/ip bug?

[Vitaly Shevtsov <loki.vt@xxxxxxxxx>]

Hello! It seems to me there is a bug in recent DFBSD snapshot.

#ifconfig
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
        inet6 fe80::6631:50ff:fe22:18d0%re0 prefixlen 64 scopeid 0x1
        inet 10.172.31.120 netmask 0xffffff00 broadcast 10.172.31.255
        ether 64:31:50:22:18:d0
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active

# netstat -rn -f inet
Routing tables

Internet:
Destination        Gateway            Flags    Refs      Use  Netif Expire
default            10.172.31.1        UGSc        4       90    re0
10.172.31/24       link#1             UC          1        0    re0
10.172.31.1        00:13:1a:fa:a8:80  UHLW        6        1    re0   1200
10.172.31.120      127.0.0.1          UGHS        0       16    re0
127.0.0.1          127.0.0.1          UH          1        0    lo0

As you can see, system thinks 10.172.31.120 is reachable via re0 not
via lo0, so I can't ping myself.

When I try to ping myself by real IP such messages appear on ttyv0:
Nov 25 18:52:49 vitaly kernel: arplookup 127.0.0.1 failed: could not
allocate llinfo
Nov 25 18:52:49 vitaly kernel: arpresolve: can't allocate llinfo for
127.0.0.1 rt
Nov 25 18:52:50 vitaly kernel: arplookup 127.0.0.1 failed: could not
allocate llinfo
Nov 25 18:52:50 vitaly kernel: arpresolve: can't allocate llinfo for
127.0.0.1 rt
Nov 25 18:52:51 vitaly kernel: arplookup 127.0.0.1 failed: could not
allocate llinfo
Nov 25 18:52:51 vitaly kernel: arpresolve: can't allocate llinfo for
127.0.0.1 rt

-- 
Vitaly