[Bug 248172] if_tuntap(4): OpenVPN configuring tun/tap devices ends up with IFDISABLED interfaces

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172

--- Comment #9 from Gert Doering <gert at greenie.muc.de> ---
So.  I have a nice test program now which can be run in a loop and then looked
at later.

As I said it's somewhat spurious on my system - sometimes it triggers 10 times
in a row, then 20 times not at all.

If it triggers, the output looks like this:

cc -o tester -Wall tester.c
sudo ./tester tun0

/dev/tun0 open ok, fd=3
run cmd: 'ifconfig tun0 inet6 fd00:abcd:204:4::1001/64 mtu 1500 up'
read 296 bytes, time since start=0s
tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1500
        options=80000<LINKSTATE>
        inet6 fe80::250:56ff:fe9c:dffb%tun0 prefixlen 64 tentative scopeid 0x3
        inet6 fd00:abcd:204:4::1001 prefixlen 64 tentative
        groups: tun
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        Opened by PID 62433
read 307 bytes, time since start=1s
tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1500
        options=80000<LINKSTATE>
        inet6 fe80::250:56ff:fe9c:dffb%tun0 prefixlen 64 tentative scopeid 0x3
        inet6 fd00:abcd:204:4::1001 prefixlen 64 tentative
        groups: tun
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        Opened by PID 62433
    *** FOUND ***

(the tester program will loop for 10 seconds, run "ifconfig $dev" in a pipe,
and print "FOUND!" if it found IFDISABLED in the output - which could be
extended to do something else on-trigger)

Attachment coming.

-- 
You are receiving this mail because:
You are on the CC list for the bug.