F5F Stay Refreshed Power Users Networks pfSense allocates real network addresses rather than using VLAN10 interfaces.

pfSense allocates real network addresses rather than using VLAN10 interfaces.

pfSense allocates real network addresses rather than using VLAN10 interfaces.

K
KareBare31
Member
Find
144
04-19-2023, 02:09 PM
#1
Hello everyone, I'm facing an unusual issue. My setup includes a Watchguard XTM 525 with pfSense, connected to a Cisco 3750X switch via a trunk port to the CISCO switch. The VLAN 10 segment isn't receiving DHCP or internet access, while other VLANs function normally and communicate outside the LAN. My physical pfSense LAN interface is set to 10.1.20.0/24, but when connected to VLAN 10 (ports 1-36), it shows an IP in 10.1.20.0/24 instead of the expected 10.1.8.0/24. I've attached my configurations for reference. It's puzzling why only VLAN 10 behaves this way. Thanks!
Reply
Reply
K
KareBare31
04-19-2023, 02:09 PM #1

Hello everyone, I'm facing an unusual issue. My setup includes a Watchguard XTM 525 with pfSense, connected to a Cisco 3750X switch via a trunk port to the CISCO switch. The VLAN 10 segment isn't receiving DHCP or internet access, while other VLANs function normally and communicate outside the LAN. My physical pfSense LAN interface is set to 10.1.20.0/24, but when connected to VLAN 10 (ports 1-36), it shows an IP in 10.1.20.0/24 instead of the expected 10.1.8.0/24. I've attached my configurations for reference. It's puzzling why only VLAN 10 behaves this way. Thanks!

Reply
Reply
Z
zleekfl
Junior Member
Find
32
04-19-2023, 09:01 PM
#2
The trunk uses VLAN 10 as its native VLAN by default. Changing it to VLAN 1 would alter how tagged traffic is handled, potentially causing tag loss for VLAN 10 packets. This might result in untagged traffic reaching the next segment on the pfSense side if the configuration isn't adjusted properly.
Reply
Reply
Z
zleekfl
04-19-2023, 09:01 PM #2

The trunk uses VLAN 10 as its native VLAN by default. Changing it to VLAN 1 would alter how tagged traffic is handled, potentially causing tag loss for VLAN 10 packets. This might result in untagged traffic reaching the next segment on the pfSense side if the configuration isn't adjusted properly.

Reply
Reply
J
JYSG
Member
Find
171
04-20-2023, 05:22 AM
#3
I believe it was the cause... I realized I had an error in the code. A second pair of eyes often helps! Just need to ensure access to the WebUI is available from each recognized VLAN. Thanks!
Reply
Reply
J
JYSG
04-20-2023, 05:22 AM #3

I believe it was the cause... I realized I had an error in the code. A second pair of eyes often helps! Just need to ensure access to the WebUI is available from each recognized VLAN. Thanks!

Reply
Reply