In PR247718 the problem occurs, that the IPv6 stack has a hard coded
loop avoidiance code for IPv6 only on P2P links. This behaviour does
not occur on IPv4 and causes packet loss for legitimate traffic, i.e.
VPN peers (Point2Miltipoint setup).
Details
Details
- Reviewers
melifaro bz rgrimes - Group Reviewers
network - Commits
- rS364982: ipv6: quit dropping packets looping back on p2p interfaces
Apply the patch and let the bug reporter check, that the VPN is working.
Diff Detail
Diff Detail
- Repository
- rS FreeBSD src repository - subversion
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
I don't believe we need specific processing here either.
- Kernel shouldn't try to be "smart" and decide whether user-configured routing is correct or not. It can't fix the issue anyway.
- Even when the route configuration is incorrect, TTL will still kick in
Comment Actions
This is a good fix, it is wrong for the kernel to try and guess that something is wrong here. "Highly Probably != For Certain" and having this kind of stuff get in the way when your trying to make something work is very annoying for the end user. Now if we could just get the hard coded interface loopback route creating/removal out of the kernel.
Comment Actions
May somebody with commit rights push this into the kernel and may have a kind look on my other open reviews ...
Comment Actions
Ping? It's been considerably longer than just half a week, and there doesn't appear to be any opposition to this change.