Package: vlan
Version: 2.0
Severity: important

Hi,

I've got an ARM system where eth0 is hotplugged pretty slowly
(it hangs off of USB, and takes a while to initialize), so for
networking to work in general, the system needs to be able to
hotplug it. Thus, I have:

  allow-hotplug eth0
  iface eth0 inet static
          address 10.1.0.7
          netmask 255.255.255.0
          gateway 10.1.0.1

However, I also want a VLAN (actually several):

  allow-hotplug eth0.21
  iface eth0.21 inet static
          address 10.0.1.0/24
          netmask 255.255.255.0

eth0.21, however, does not come up on boot, because ifupdown
never gets the message that it exists (no wonder, since ifupdown
is the one that's supposed to take it up). I've tried changing to

  auto eth0.21
  iface eth0.21 inet static
          address 10.0.1.0/24
          netmask 255.255.255.0

but then ifupdown tries to take it up immediately on boot, before
eth0 has been hotplugged, so it fails (sometimes one out of three
VLANs succeed, it seems -- it's timing-sensitive). The only stable
workaround I've found is to force-hotplug them when eth0 comes up:

  allow-hotplug eth0
  iface eth0 inet static
          address 10.1.0.7
          netmask 255.255.255.0
          gateway 10.1.0.1
          up vconfig add eth0 20
          up vconfig add eth0 21
          up vconfig add eth0 22

This shouldn't be necessary, though. Perhaps vlan or ifupdown could
be modified so that when interface “foo” gets hotplugged, it also
takes that as a sign to hotplug every VLAN with “foo” as raw device?

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 4.6.0-with-cpuidle (SMP w/4 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages vlan depends on:
ii  iproute2  4.3.0-1+b1

vlan recommends no packages.

vlan suggests no packages.

-- no debconf information

Reply via email to