On 11/24/11 04:14, Vitaly Shevtsov wrote: > Hello! It seems to me there is a bug in recent DFBSD snapshot. ... > As you can see, system thinks 10.172.31.120 is reachable via re0 not > via lo0, so I can't ping myself. ... > Destination Gateway Flags Refs Use Netif Expire > 10.172.31.120 127.0.0.1 UGHS 0 16 re0 ... > 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
I'm running v2.13.0.381.gca541 and have the same problem when using dhclient.I cannot ping my own IP address 192.168.1.2 probably due to the route rule: Destination Gateway Flags Refs Use Netif Expire 192.168.1.2 127.0.0.1 UGHS 0 0 em0 I think the problem is with /sbin/dhclient-script Probably the same as described in http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/12136 Maybe opening a bug report is the way to go. Alan K. <http://leaf.dragonflybsd.org/mailarchive/users/2011-11/msg00095.html>
