Freebsd failed to create routing prefix

Rommel Laranjo rslaranjo at gmail.com
Mon May 4 02:47:35 UTC 2009


Hello Hiroki-san,

The box I am using is FreeBSD 7.0-Release:

# uname -a
FreeBSD freebsd7.example.com 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun
Feb 24 19:59:52 UTC 2008
root at logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386


On Mon, May 4, 2009 at 9:37 AM, Hiroki Sato <hrs at freebsd.org> wrote:
> Rommel Laranjo <rslaranjo at gmail.com> wrote
>  in <f051005f0905031731t6cde557l5251caf2ec24f41f at mail.gmail.com>:
>
> rs> Yes, my box has two NICs and I have these lines at my rc.conf.
> rs>
> rs> ipv6_enable="YES"
> rs> ipv6_network_interfaces="AUTO"
>
>  Ah, from 7.1R there seems a regression of handling IPv6 link-level
>  route on a system with multiple NICs and receiving RAs.  When one NIC
>  received an RA, another NIC's link-level route (i.e. marked as UC
>  flag in netstat -r) is removed for some reason and it does not work
>  even if the route is manually added after the removal (btw, you can
>  add the route by using "route add -inet6
>  2001:db8:1234:abcd:20c:27ff:fe3d:63dd/64 -interface em0 -cloning
>  -nostatic").

I tried this, and it add the expected route for the prefix:
2001:db8:1234:abcd::/64           link#1                        UC          em0

But when I pinged the router, I still got no success:
# ping6 2001:db8:1234:abcd::fff2
PING6(56=40+8+8 bytes) 2001:db8:1234:abcd:20c:27ff:fe3d:63dd -->
2001:db8:1234:abcd::fff2
ping6: sendmsg: Invalid argument
ping6: wrote 2001:db8:1234:abcd::fff2 16 chars, ret=-1
ping6: sendmsg: Invalid argument
ping6: wrote 2001:db8:1234:abcd::fff2 16 chars, ret=-1
^C
--- 2001:db8:1234:abcd::fff2 ping6 statistics ---
2 packets transmitted, 0 packets received, 100.0% packet loss

I also got this logged at the console:
nd6_storelladdr: sdl_alen == 0

>
>  Your procedure looks correct to me and it should work on 7.0R, but on
>  both 7.1R and 7.2R it does not work at least.  While I still have no
>  idea about a workaround to this symptom at this moment, I think it
>  will be fixed soon in the source tree.

Thanks alot,

Romskie


More information about the freebsd-net mailing list