I can confirm that even with the recent configuration above any DHCP requests that come over a tagged VLAN are also seen by the untagged interface. Here is a sample request coming over VLAN 5;
DHCPDISCOVER from 00:23:8b:27:06:8b via eth1
DHCPDISCOVER from 00:23:8b:27:06:8b via eth1.5
DHCPOFFER on 192.168.213.152 to 00:23:8b:27:06:8b via eth1
DHCPOFFER on 192.168.205.150 to 00:23:8b:27:06:8b via eth1.5
The DHCP server still sees the tagged VLAN packets when the VLAN interface isn't listed in INTERFACES.
#> dhcpd3 -d eth1
...
Listening on LPF/eth1/00:04:23:ab:3e:ea/192.168.213/24
Sending on LPF/eth1/00:04:23:ab:3e:ea/192.168.213/24
Sending on Socket/fallback/fallback-net
DHCPDISCOVER from 00:23:8b:27:06:8b via eth1
DHCPOFFER on 192.168.213.152 to 00:23:8b:27:06:8b via eth1
Naturally, the device doesn't see the offer as it is going out on the untagged VLAN.
DistroRelease: Ubuntu 9.10 ture: amd64 ature: Ubuntu 2.6.31-19.56-server
Package: dhcp3-server 3.1.2-1ubuntu7.1
PackageArchitec
ProcVersionSign
I can confirm that even with the recent configuration above any DHCP requests that come over a tagged VLAN are also seen by the untagged interface. Here is a sample request coming over VLAN 5;
DHCPDISCOVER from 00:23:8b:27:06:8b via eth1
DHCPDISCOVER from 00:23:8b:27:06:8b via eth1.5
DHCPOFFER on 192.168.213.152 to 00:23:8b:27:06:8b via eth1
DHCPOFFER on 192.168.205.150 to 00:23:8b:27:06:8b via eth1.5
In case there is any doubt;
#> grep VID /proc/net/ vlan/eth1. 5
eth1.5 VID: 5 REORDER_HDR: 1 dev->priv_flags: 1
The DHCP server still sees the tagged VLAN packets when the VLAN interface isn't listed in INTERFACES.
#> dhcpd3 -d eth1 00:04:23: ab:3e:ea/ 192.168. 213/24 00:04:23: ab:3e:ea/ 192.168. 213/24 fallback/ fallback- net
...
Listening on LPF/eth1/
Sending on LPF/eth1/
Sending on Socket/
DHCPDISCOVER from 00:23:8b:27:06:8b via eth1
DHCPOFFER on 192.168.213.152 to 00:23:8b:27:06:8b via eth1
Naturally, the device doesn't see the offer as it is going out on the untagged VLAN.