ndppd does receive locally generated neighbor discovery

[jerome-pouiller]

Probably a limitation of the Linux network API, but ndppd seems to not handle locally generated ND:

$ ndisc6 2001:db8:2435:66a0:20d:6fff:fe20:c096 eth0
Soliciting 2001:db8:2435:66a0:20d:6fff:fe20:c096 (2001:db8:2435:66a0:20d:6fff:fe20:c096) on eth0...
Timed out.
Timed out.
Timed out.
No response.
$ ndisc6 2001:db8:2435:66a0:20d:6fff:fe20:c096 tun0
Soliciting 2001:db8:2435:66a0:20d:6fff:fe20:c096 (2001:db8:2435:66a0:20d:6fff:fe20:c096) on tun0...
Target link-layer address: 00:02:F7:F0:00:00
 from fe80::202:f7ff:fef0:0

Obviously, if I send ND from another station on the network, everything goes well.

[DanielAdolfsson]

Which version of you using? 1.x or 0.x?

[jerome-pouiller]

I use the master of 0.2.x. You think it could be fixed on 1.x?

[domosekai]

@jerome-pouiller You can try my patch based on 0.x master which adds an option to allow catching outgoing packets.
domosekai@9156a80
Add outgoing yes to one and only one proxy (the default interface), or you will end up in loops.

Please note that this patch will not change the result of doing neighbor discovery on that interface (eth0) because the host is just not there. What it does is to autowire the route to the host (on tun0) so that a ping to the host can get through.