Date: Thu, 6 Aug 2009 10:35:42 -0700 From: "Li, Qing" <qing.li@bluecoat.com> To: <DimanNe@ya.ru>, <freebsd-current@freebsd.org> Subject: RE: network problems Message-ID: <B583FBF374231F4A89607B4D08578A4304EFB476@bcs-mail03.internal.cacheflow.com> In-Reply-To: <5151249558460@webmail6.yandex.ru> References: <5151249558460@webmail6.yandex.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
<snip> >=20 > -----------nestat -rn----------- > Routing tables >=20 > Internet: > Destination Gateway Flags Refs Use Netif > Expire > 10.0.0.0/8 10.55.102.1 UGS 0 40 re0 > 10.55.102.0/24 10.55.102.1 UGS 0 0 re0 = =3D> > 10.55.102.0/23 link#1 U 0 0 re0 <snip> The problem is you have 2 routes with the same key 10.55.102.0, but the one with the more specific mask (marked by the "re0 =3D>" entry) is an indirect route (G flag), and it's used to search for 10.55.102.1, which is a problem. This problem seems to point to your overlapping prefix configuration. You will have the exact same problem even on FSBD 7.2R with the above routing table. >=20 > In /etc/rc.conf i disabled all services such as nfs, apache, dbus, > samba and so on (may be this problems due to it). > When i try ping 10.55.102.1 it says > sendto: Invalid argument >=20 > And in dmesg output very much this lines: > ipv4 address: "10.55.102.1" is not on the network > ipv4 address: "10.55.102.1" is not on the network > arpresolve: can't allocate llinfo for 10.55.102.1 > Yup, those are the right messages. -- Qing
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B583FBF374231F4A89607B4D08578A4304EFB476>