Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #62737

Bug#860264: ifquery behaviour

Cross-posted to 2 groups.

Show all headers | View raw

# grep auto /etc/network/interfaces
auto lo
# grep hotplug /etc/network/interfaces
allow-hotplug enp0s31f6

# ifquery --read-environment --list --exclude=lo  # as in unit file
#
# ifquery --read-environment --list --exclude=lo --allow auto
#
# ifquery --read-environment --list --exclude=lo --allow hotplug
enp0s31f6

But if I convert enp0s31f6 to auto
# grep /etc/network/interfaces
auto lo
auto enp0s31f6

# ifquery --read-environment --list --exclude=lo --allow hotplug
#  (as expected)
# ifquery --read-environment --list --exclude=lo --allow auto
enp0s31f6
# ifquery --read-environment --list --exclude=lo
enp0s31f6

So with the interface set to auto, the ifquery in the unit file
picks it up. With the interface set to allow-hotplug, it doesn't.

I think this is part of the puzzle, but there is more to it.
I think that there are some issues arising from how ifupdown
and systemd (fail to) communicate about when exactly the network
interface is fully up and working (particularly in the dhcp case).
If you look at the work that has gone into ifupdown since the
stretch release, it seems like there are some issues there that
have now, hopefully, been resolved.

Kind regards
Vince

Back to linux.debian.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Bug#860264: ifquery behaviour Vincent McIntyre <vincent.mcintyre@csiro.au> - 2018-12-15 10:00 +0100
  Bug#860264: similar bug with sshfs, maybe in systemd/ifupdown Antoine Beaupre <anarcat@debian.org> - 2019-01-30 03:40 +0100
    Bug#860264: similar bug with sshfs, maybe in systemd/ifupdown Antoine Beaupré <anarcat@debian.org> - 2019-01-30 04:10 +0100

csiph-web