One VLAN, no connetion data
-
@denverdesktopssupport very strange, lets page maybe @stephenw10 or @Derelict two very bright guys that know way more than me - maybe they have some idea..
I assume this actual netgate appliance since showing switch ports, which specific model 2100, 3100, etc.. and what version of pfsense are you running?
-
It might have a switch port reference in the config that you cannot see and is pointing at a port that is not reporting it.
Check the config file for that interface for a reference line like:<switchif>switch0.port1</switchif>Steve
-
Wow that was fast - and already have a lead to what it could be ;) hehehe
-
Ha, I was already replying...
Yeah what you see there is what you get if you set the interface to reflect the state of switch port 0:
That's the internal port and is invalid. It should be port 2.
Steve
-
@stephenw10 ah that makes perfect sense.. Steve on the spot vs Johnny in this case...
-
Changed the setting to "Select the switch port to monitor for media and state change", which did the trick.
Should all of the VLANs be set to 2?
-
If you don't select a port there the interface state will be that of the parent interface which in the 1100 is mvneta0. But that is the internal port connected to the switch so it's always up.
That will work but VLANs will show as up even if you pull the cable. Really they should be set to the port that's actually carrying them, which is port 2 (LAN) in this case.Steve
-
LAN port is set to port 2 -
When changing the VLAN monitor port I get -
"This Switch port is already in used by another interface."
-
Ah, yes I'd forgotten about that. The gui input validation assumes you will be use them as access ports so only have one VLAN per port. So, at this time, you can only set one VLAN to reflect it.
If you really need the correct port state to be shown you can edit the config directly but I don't recommend that.https://redmine.pfsense.org/issues/10890
Steve
-
Nope. All is good.
Thank you "all" for the assistance and quick response.
