[Bug 219699] Issue with IPv6 and neighbor notification

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Thu Jun 1 03:59:10 UTC 2017


            Bug ID: 219699
           Summary: Issue with IPv6 and neighbor notification
           Product: Base System
           Version: 11.0-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: standards
          Assignee: freebsd-standards at FreeBSD.org
          Reporter: paul.g.webster at googlemail.com

I will be honest here and admit that I do not know quite if this is that
FreeBSD is doing IPv6 right and linux is implementing some hack to get around a
problem or if FreeBSD is doing something wrong. Its a little to low level for
me, so I hope someone with a little more knowledge can clarify the issue.

Ok so I grabbed a cheap VPS to run a small mail server on, it is XEN; all works
lovely, virtio etc.. but for ipv6 the host implements a shared gateway for all
its clients, notable: 2a07:4580:b0d::1/48

I have a /64 in my command on this range; 2a07:4580:b0d:27e::/64 for which I
use 2a07:4580:b0d:27e::1/128 for my mail server. 

Now the issues; for me to reach that gateway from that prefix I needed to set:
ifconfig_vtnet0_ipv6="inet6 2a07:4580:b0d:27e::1/48"

because obviously, my assigned /64 could not reach there gateway, from what I
understand from the IPv6 folks I should be able to simply set the gateway to
the interface without such a hack, but once again realistically; no idea.

Now for the actual problem.. the ipv6 is spotty, 95% loss and what is going on
is there gateway seems to believe I am not really using the address; if I do
use it; it temporarily 'comes up', so I did this:

$ cat /etc/rc.local
daemon -f ping6 -i 2 -s 1 2a07:4580:b0d::1

and wallah perfect working ipv6, I assume that some sort of 'neigbhour
notification' is not taking place, and the ping is enforcing it. But I also
have several linux VPS's with these guys and they are all fine, hence my reason
for calling out for help to figure out what exactly is wrong.

-- Cheers paul

You are receiving this mail because:
You are the assignee for the bug.

More information about the freebsd-standards mailing list