>
> In that case, I'm curious to find out if you find that setting the host0 interface up in
> the container also brings the vb-dahlia interface up on the host?
On container :
gab@dahlia ➤➤ ~ % ip addr
2: host0: <BROADCAST,ALLMULTI,AUTOMEDIA,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast state UP group default qlen 1000
link/ether 56:84:f7:39:43:c7 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.94/24 brd 192.168.1.255 scope global host0
valid_lft forever preferred_lft forever
inet6 fe80::5484:f7ff:fe39:43c7/64 scope link
valid_lft forever preferred_lft forever
gab@dahlia ➤➤ ~ # ip link set dev host0 down
gab@dahlia ➤➤ ~ % ip addr
2: host0: <BROADCAST,ALLMULTI,AUTOMEDIA> mtu 1500 qdisc pfifo_fast
state DOWN group default qlen 1000
link/ether 56:84:f7:39:43:c7 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.94/24 brd 192.168.1.255 scope global host0
valid_lft forever preferred_lft forever
Now looking on host :
gabx@hortensia ➤➤ ~ % ip addr
4: vb-dahlia: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
pfifo_fast master br0 state DOWN group default qlen 1000
link/ether 8e:a4:c3:8c:cc:89 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.94/24 brd 192.168.1.255 scope global vb-dahlia
valid_lft forever preferred_lft forever
inet6 fe80::8ca4:c3ff:fe8c:cc89/64 scope link
valid_lft forever preferred_lft forever
It was UP before I brought vb down. So you have your answer : yes.
