Linux 3.9 routing oddity

[Benedikt Stockebrand]

Hi Gert, Pierre, and list,

Gert Doering <gert at space.net> writes:

> Hi,
>
> On Tue, Jul 02, 2013 at 10:09:00PM +0200, Jeroen Massar wrote:
>> You might also want to try this out with something that is not a tun/tap
>> interface, thus a default ethernet interface, as tun/tap might have all
>> kinds of odd behavior, eg no or hacked neighbor discovery depending on
>> the tool being used by the tun device. (and in case you use openvpn,
>> kick Gert ;)
>
> I'm not sure why it would want to use ND on a tun device anyway...  it
> doesn't do that for mine.

maybe I'm too low on caffeine right now, but doesn't the loop prevention
on a point-to-point interface use ND when a subnet prefix (rather than
two unrelated IP addresses with an interface route) is configured for
that link?

@Pierre: May sound silly, but could it be that you run some
misconfigured packet filter here, possibly after a botched update run?
It's been a while since I last saw that, but it has happened in the
past---and I made some money cleaning things up at a customer with that
sort of problem some time ago.


Cheeers,

    Benedikt

-- 
			 Business Grade IPv6
		    Consulting, Training, Projects

Benedikt Stockebrand, Dipl.-Inform.        http://www.stepladder-it.com/