This isn't going to help solve your problem, it's just for your info... On Fri, 9 Dec 2016, BERTRAND Joël wrote: <snip>
agr1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
capabilities=7ff80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx>
capabilities=7ff80<TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx,TCP6CSUM_Rx>
capabilities=7ff80<TCP6CSUM_Tx,UDP6CSUM_Rx,UDP6CSUM_Tx,TSO6>
enabled=0
agrport: wm1, flags=0x3<COLLECTING,DISTRIBUTING>
agrport: wm2, flags=0x3<COLLECTING,DISTRIBUTING>
address: 68:05:ca:02:b2:59
inet 192.168.10.128 netmask 0xffffff00 broadcast 192.168.10.255
inet6 fe80::6a05:caff:fe02:b259%agr0 prefixlen 64 scopeid 0x5
inet6 2001:7a8:a8ed:10::128 prefixlen 64
and agr1 runs as expected.
When I compare agr0 and agr1, I note that agr0 doesn't indicate IPv4
and IPv6 capabilities. Why ? If I understand, agr0 has to indicate these
capabilities to work as expected.
I assume that by "indicate IPv5 and IPv6 capabilities" you are referring to the varions hardware-offload flags listed above. These are totally optional, and if hardware (or, in your case pseudo-hardware tap!) does not provide these capabilities, they are provided in software. These flags are documented in a bit more detail in the ifconfig(8) man page (but you need to search for the flag names in lower-case!)
+------------------+--------------------------+------------------------+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com | | Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org | +------------------+--------------------------+------------------------+