No DHCP for VLAN 5

Grimeton

#1 Rule of networking: We don't want to assume, we want to know.

Depending on how your switch is configured and handles tagged frames on an untagged port: delete them, forward them untouched (QinQ), remove the tag and so on, it can work and it cannot work. It's important to VERIFY the configuration along the way.

Cu

NasKar

@Grimeton said in No DHCP for VLAN 5:

Depending on how your switch is configured and handles tagged frames on an untagged port: delete them, forward them untouched (QinQ), remove the tag and so on, it can work and it cannot work. It's important to VERIFY the configuration along the way.

My setup is not ideal I have 4 netgear switches between the pfsense and the AP. Would have been best to have one switch with all the cables going directly to it. I can try to move the AP temporarily to the switch connected to the pfsense

Grimeton

@NasKar
If the interface on the pfSense is tagged and the interface on the switch is NOT tagged this can lead to all kind of confusions. Same happens when vice versa.

So it's important to know that your VLAN-configuration on pfSense and on the switch is fine.

As DHCP is a system that uses broadcast and relies more on L2 than on L3, having a valid and working VLAN-config is important.

JKnott

@Grimeton

Given the phone is sending out discovers and receiving offers, that's not an issue. Also, you'd not see VLAN tags on a switch port that's already been assigned to a VLAN.

Grimeton

@JKnott I can tell you from experience that all you've just written is false.

JKnott

@NasKar

Four switches is not a problem if they're configured properly. You have a VLAN. I assume you have the VLAN configured on pfSense and any switch that has to pass VLAN frames configured appropriately. At some point, either a switch or in the AP, the VLAN frames are converted to native frames, by removing the VLAN tags. However, given that you're getting an offer after a discover, there is communication between the iPhone and DHCP server, so I doubt VLAN tags are the problem.

JKnott

@Grimeton

False in what way? I have viewed the captured traffic in Wireshark and I can see the discover, coming from the iPhone, followed immediately by the offer, coming from the DHCP server. That tells me the phone and server are communicating up to that point. The next step is for the phone to request the offered address, but that's not happening. The question is why. If it was a VLAN issue, we'd see the discover, but not the offer.

Grimeton

@JKnott This is pointless. I'm not here to measure the size of my dick. I can tell you from experience that switches are the most buggy devices on earth. They leak all kinds of information across VLANs, while other devices like to ignore VLAN-tags in the L2-header based on the moon phase. Especially when it comes to WIFI. There are WIFI devices that forward VLAN-tagged packets and the receiving device just happily ignores them.

So from my experience it's important to make sure that the configuration is fine, ESPECIALLY when the communication is just lost in a brodcasted setup like this one.

JKnott

@Grimeton

Please explain why there's an offer, if the devices are not communicating. If there was a switch failure, there would be no offer, as the server wouldn't have heard from the phone.

Have you looked at that capture? I have it opened in Wireshark right now.

johnpoz

We know that pfsense gets the discover and makes the offer, we have no idea if the phone is getting it.

You really need to validate that by connecting to the wifi if that is where your having a problem.

Are you saying these are 4 dumb switches between your AP and pfsense?

JKnott

I just noticed something curious, though I doubt it has anything to do with the problem. The first frame in the capture is an 802.3 LLC frame, whereas everything to do with IP uses Ethernet ll frames.

Grimeton

@JKnott The trace is from one end of the problem.

The device requests an IP-address and gets handed an offer. If the WIFI-device is forwarding the L2 package with tagged headers the phone might be lost/ignoring it, hence the answer is thrown away.

Just one explanation.

So please, please, please, with lots of sugar on top of it. Make sure that the VLAN-configuration is fine across all devices.

johnpoz

Exactly!! Where exactly was this sniff taken? On the pfsense vlan interface?

JKnott

@Grimeton

Again, there is no sign of VLAN tags in the capture, from either end. Also, devices not configured for VLANs should not accept them. For them to do that, it means accepting a frame with the wrong Ethertype. The frames show the Ethertype for IPv4, not VLAN, which means the VLAN tags have been removed before that point.

johnpoz

If he is sniffing on the vlan interface vs the parent physical he wouldn't see the tags in his sniff.. He would have to sniff on the parent physical interface with -e to see the tags.

Grimeton

@JKnott Depending on WHERE the trace was taken you do not see VLAN-tags because they were filtered out by a lower layer.

But above in the description people are talking about VLANs and VLAN5.

So we ASSUME that it's 802.1q.

johnpoz

^ exactly I would for assure assume 802.1q but he prob sniffed on the vlan interface directly... But lets make sure we know exactly where that sniff was taken.

And we don't have a sniff from the other end via a wireless client (laptop) connected to that same ssid do we?

JKnott

@johnpoz said in No DHCP for VLAN 5:

Exactly!! Where exactly was this sniff taken? On the pfsense vlan interface?

If taken there, I'd expect to see VLAN tags, unless the port connects to a managed switch that puts the frame on a VLAN. So, we'd expect VLAN tags somewhere, but we haven't yet determined where they're added & removed. If it's just dumb switches, then we'd see VLAN tags everywhere between pfSense and the AP. However, I believe that capture was taken on the network used for the AP, which is VLAN 5 somewhere, but there are no tags at that point.

johnpoz

You wouldn't see the tag if you sniffed in pfsense gui on the vlan.

Grimeton

@johnpoz

Yeah besides that, tagged L2 packets via WiFi are a a thing on its own. As I wrote before: some devices ignore the tags and take the packet, others ignore the packets completely and so on...

It gets really nasty really quick if this isn't setup correctly.