I have been bumping my head around lately due to LEDE not allowing me to access my tagged VLAN. I want my router to only have the ports WAN and PORT1 as the main use for this router. PORT 3,4 and 5 will be used by my PFSENSE firewall. So my current switch config is this:
my PFSENSE wall is configured to spit from LAN the VLAN I will use in the LEDE router (port2). Now, the untagged port 2&4 works, I can use the port 4 and it is not tagged and PFSENSE can be accessed by the device that connects to it.
The problem is with the LEDE's PORT3 (VLAN200), I could not ping PFSENSE box. Note that PFSENSE box has VLAN ID200 as DHCP server.
The weird thing is VLAN200 does work with LEDE's interface bridge to a WLAN, devices connected to this WLAN can have the VLAN200 IP range provided by the PFSENSE. Only the port3 wont work with VLAN200!!
I can assure that the port3 is not damaged and I'm sure most of you will say that I should buy a dedicated managed switch for this, but I still hope someone could help me and maybe point me in a possible solution.
If I miss anything I should mention to clearly understand my setup, please do let me know, thank you!
thank you in advance experts!
by the way, my LEDE router is a trusty old Buffalo WZR-g300nh on a 17.01.4 r3560
Thanks for your feedback, i have set the CPU to all ID as tagged and tried again. Unfortunately, the issue is still the same.
I am able to access the VLAN200 using a new interface that is bridge in eth0.200 and WLAN, PFSENSE is serving IP's to connected WiFi devices, but when I connect to PORT3 (VLAN200), no connection, no IP even with static addressing, still cant seem to reach PFSENSE.
Hi psherman, yes, it is the LAN interface of my PFSENSE box. untagged and VLANID2.
What drives me nuts is that the newly created interface(named WFR) in LEDE, bridge WLAN and eth0.2, the interface gets DHCP from my PFSENSE box(VLANID2) and wifi devices connect to WLAN can get IP addresses as well.
here is the current switch config:
#this is working, device in port1 can get IP from LEDE
VLAN ID1 = CPU-tagged | PORT1-untagged | OTHERPORTS-off
#this is half working, port3 doesnt get IP from PFSENSE but the new interface (WFR) in LEDE received DHCP address from PFSENSE, when WFR bridged WLAN, WLAN devices can get IP as well. BUT STILL NOT PORT 3
VLAN ID2 = CPU-tagged | PORT2&3-tagged | OTHERPORTS-off
#this is working, device in port4 can get untagged IP from PORT2 (from PFSENSE as well)
VLAN ID3 = CPU-tagged | PORT2&4-untagged | OTHERPORTS-off
I'll now ask the same question about the device plugged into port 3 -- what is it? Is it VLAN aware and expecting tagged frames? And is it configured properly? If you unplug both devices from the LEDE device ports 2 and 3 and plug them directly together, does the device that was plugged into port 3 work as expected?
@mongoload - no, you cannot assume that your PC will get an IP under these circumstances. Most of the time, a standard computer is not configured to be VLAN aware, meaning that if the incoming ethernet frames are tagged, they may be ignored. This is true for most computers (Mac, Windows, Linux) unless they have both VLAN aware hardware and OS's, and are configured to listen for tagged frames from a particular VLAN.
Therefore, try connecting the PFSense box directly to your PC... if it doesn't get an IP address, the problem is not LEDE, but rather your PC.
However, you can address this with your LEDE configuration by assigning port 3 to VLAN 2 as untagged.
Report back on the direct connection experiment and we'll go from there.