On Fri, Jan 13, 2017 at 01:11:07PM +0100, Sebastian Benoit wrote:
> On current, there seem to be two problems with lo(4) interfaces:
>
> 1. "ifconfig lo6 up" fails
>
> # ifconfig lo6 create
> # ifconfig lo6 up
> ifconfig: SIOCSIFFLAGS: Inappropriate ioctl for device
> # ifconfig lo6 destroy
> #
>
> The sys/net/rdomains regress test fails because of this, and i think
> sys/net/if.c rev 1.473 might be the cause.
>
> It still works on a kernel from early December.
>
> 2. "ifconfig lo6 destroy" fails on an interface in an rdomain
>
> # ifconfig lo6 create
> # ifconfig lo6 rdomain 6
> # ifconfig lo6
> lo6: flags=8008<LOOPBACK,MULTICAST> rdomain 6 mtu 32768
> index 12 priority 0 llprio 3
> groups: lo
> # ifconfig lo6 destroy
> ifconfig: SIOCIFDESTROY: Operation not permitted
>
you can't remove the lo6 device if rdomain 6 still exists... even if it
is only on lo6. So you should first remove the rdomain configuration,
and next destroy the iface.
# ifconfig lo6 create
# ifconfig lo6 rdomain 6
# ifconfig lo6
lo6: flags=8008<LOOPBACK,MULTICAST> rdomain 6 mtu 32768
index 13 priority 0 llprio 3
groups: lo
# ifconfig lo6 127.0.0.1
# ifconfig lo6
lo6: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> rdomain 6 mtu 32768
index 13 priority 0 llprio 3
groups: lo
inet 127.0.0.1 netmask 0xff000000
# ifconfig lo6 rdomain 0
# ifconfig lo6 destroy
--
Sebastien Marie
