Linux 3.9 routing oddity

[Pierre Emeriaud]

2013/7/2 Jeroen Massar <jeroen at massar.ch>:
>
> 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

Just tried with a route on eth0 while the default was on wlan0: the
exact same thing. The route is only active after the neighbor is added
to the cache (permanently or not).

I'm reporting this to netdev.


Thanks for the help.

regards,
Pierre.