On 2017-07-22, Florian Obser <[email protected]> wrote:
> reenabling debug output on the ramdisk I see this:
>
> engine_dispatch_frontend: IMSG_PROPOSAL_ACK: 1 - 25467
> configure_dfr: 1
> engine_dispatch_frontend: IMSG_PROPOSAL_ACK: 2 - 25467
> configure_address: 1
> engine_dispatch_frontend: IMSG_PROPOSAL_ACK: 3 - 25467
> configure_address: 1
> configure_interface: vio0
> configure_interface: vio0
> fatal in main: SIOCAIFADDR_IN6: File exists
> # RTM_NEWADDR: vio0[1]
> RTM_NEWADDR: vio0[1]
> RTM_DELADDR: vio0[1]
> engine exiting
> fatal in engine: msgbuf_write: Broken pipe
>
> Maybe you can only have one v6 address on the ramdisk?
Well, I can manually configure additional addresses:
------------------->
# ifconfig egress
em0: flags=208843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,AUTOCONF6> mtu 1500
lladdr 00:0d:b9:41:06:a4
llprio 3
groups: netboot egress
media: Ethernet autoselect (1000baseT full-duplex,rxpause,txpause)
status: active
inet 172.16.0.2 netmask 0xffffff00 broadcast 172.16.0.255
inet6 fe80::20d:b9ff:fe41:6a4%em0 prefixlen 64 scopeid 0x1
inet6 fddd:28ee:243:0:384d:91e7:fefc:b697 prefixlen 64 autoconf
autoconfprivacy pltime 2171 vltime 520983
inet6 fddd:28ee:243::2 prefixlen 64
inet6 2003:e5:cbc0:a01::2 prefixlen 64
<-------------------
And the corresponding /64s show up in the routing table, too.
However, I can't send packets beyond the local segment. tcpdump
on the gateway shows that it receives a steady stream of neighbor
solicitations for its advertised default router address. The replies
don't seem to have any effect.
--
Christian "naddy" Weisgerber [email protected]
