On Mon, Oct 29, 2012 at 4:32 PM, Frank Brodbeck <f...@guug.de> wrote: > I am currently playing with VLANs and found myself unable to get a lease > via run(4) device when using VLAN: > > ifconfig vlan4094 vlandev run0 > dhclient vlan4094 > > I see the packets leaving vlan4094 but they are not arriving at the dhcp > server: > > # tcpdump -i vlan4094 -n -e -ttt port bootpc > tcpdump: listening on vlan4094, link-type EN10MB > tcpdump: WARNING: compensating for unaligned libpcap packets > Oct 29 23:21:04.375894 00:0c:f6:61:c5:41 ff:ff:ff:ff:ff:ff 0800 342: > 0.0.0.0.68 > 255.255.255.255.67: xid:0xf3925c17 ether 00:0c:f6:61:c5:41 > [|bootp] [tos 0x10] > Oct 29 23:21:05.576563 00:0c:f6:61:c5:41 ff:ff:ff:ff:ff:ff 0800 342: > 0.0.0.0.68 > 255.255.255.255.67: xid:0xf3925c17 secs:1 ether > 00:0c:f6:61:c5:41 [|bootp] [tos 0x10] > Oct 29 23:21:06.788399 00:0c:f6:61:c5:41 ff:ff:ff:ff:ff:ff 0800 342: > 0.0.0.0.68 > 255.255.255.255.67: xid:0xf3925c17 secs:2 ether > 00:0c:f6:61:c5:41 [|bootp] [tos 0x10] > Oct 29 23:21:09.200824 00:0c:f6:61:c5:41 ff:ff:ff:ff:ff:ff 0800 342: > 0.0.0.0.68 > 255.255.255.255.67: xid:0xf3925c17 secs:5 ether > 00:0c:f6:61:c5:41 [|bootp] [tos 0x10] > Oct 29 23:21:12.813338 00:0c:f6:61:c5:41 ff:ff:ff:ff:ff:ff 0800 342: > 0.0.0.0.68 > 255.255.255.255.67: xid:0xf3925c17 secs:8 ether > 00:0c:f6:61:c5:41 [|bootp] [tos 0x10] > Oct 29 23:21:18.825187 00:0c:f6:61:c5:41 ff:ff:ff:ff:ff:ff 0800 342: > 0.0.0.0.68 > 255.255.255.255.67: xid:0xf3925c17 secs:14 ether > 00:0c:f6:61:c5:41 [|bootp] [tos 0x10] > Oct 29 23:21:20.744245 00:0c:f6:61:c5:41 ff:ff:ff:ff:ff:ff 0800 342: > 0.0.0.0.68 > 255.255.255.255.67: xid:0x653ba9ae secs:45 ether > 00:0c:f6:61:c5:40 [|bootp] [tos 0x10] > > If I don't tag the packets at the OS side but leave it to the switch > (Cisco SG300) via: > > switchport trunk native vlan 4094 > > everything works fine. This is on a -current machine. Sorry if this is a > dump question, but could this be a driver error or could it be a problem > with my el cheapo access point (netgear)? > > I guess the problem lies w/ that shitty access point who discards the > packets if they come in tagged but would appreciate a confirmation. > > Doing the same w/ re(4) on the same port works just fine, so I'd like to rule > out a > switch or server misconfiguration.
I've never done this/had a need to do it so I don't know if it'll actually work. If you tcpdump run0, do you see the tagged packets leaving? If you mirror and tcpdump the port your AP is connected to, do you see the DHCP packets? Are they tagged? In every Wi-Fi network I've ever deployed, VLANs were assigned to SSIDs or were based on some RADIUS/802.1x attribute so I've never expected a client to tag its Wi-Fi packets.
