scripts: Support monitoring of interestingly named VLANs on bonds
authorMartin Schwenke <martin@meltin.net>
Wed, 8 Jul 2015 11:23:48 +0000 (21:23 +1000)
committerAmitay Isaacs <amitay@gmail.com>
Thu, 16 Jul 2015 04:35:09 +0000 (14:35 +1000)
commitc48d2d6301b10ad7bf14402af10bd46624515480
treed9939d1775f20a7372627950a5c26c3c0095202e
parent7742baef6595ca95900d25118bf70a96cf5d0451
scripts: Support monitoring of interestingly named VLANs on bonds

VLAN interfaces on bonds with a name other than <iface>.<id>@<iface>
are not currently supported.  That is, where the VLAN name isn't based
on the underlying bond name.  Such VLAN interfaces can be created with
the "ip link" command, as opposed to the "vconfig" command, or by
renaming a VLAN interface.

This is improved by determining the underlying interface name for a
VLAN from the output of "ip link".

No serious attempt is made to support VLANs with '@' in their name,
although this seems to be legal.  Why would you do that?

Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
(Imported from commit bc71251433ce618c95c674d7cbe75b01a94adad9)
config/events.d/10.interface