@WAR10CK said in Intel gigabit ct Desktop not detected: AHCI enclosure management bridge OK, pfsense recognizes the netcard, but why is it saying : AHCI enclosure management bridge under interface em0. There is no link when I plugin the cable to em0. The cable works fine in em1.

@xyzzyz said in VLAN question for noob moving from Cisco ASA: My question: On my pfSense replacement for the ASA, is there any advantage to setting up a VLAN for the WAN port? No.

Dick? Really? Calling you out on calling yourself a ccie when clearly everyone knows that is not even close to true is not being a dick... That is just calling someone out on their BS! So what was the problem, only tcp for the rule? Wrong source? Maybe you had policy route on the rule? But that wouldn't of stopped ping to pfsense IP? Only ping to other lan.. That is another common mistake.

@Gertjan said in Trouble With CaptivePortal on Two VLANs in One Interface: You are already using multiple interfaces - a VLAN is considered as a interface. Typically, each interface has its own dedicated AP(s) - using a dedicated radio (== Wifi) setup. A user should choose the correct Wifi SSID first to use the correct network. You can't automatize this. I just wanted to make it happen. I was planning to redirect the user to the correct VLAN by using just one SSID. But I completely got that I can not do it. Thanks for your helps. @free4 I still can not find an opportunity to try PacketFence. I will write down here if I can be successful on it.

Create a LAGG on pfsense and on the switch stack. Use the LAGG as the vlan parent.

Even better : access the console ! If memory serves me well, a Link Up (and down) event is signaled as soon as you hook up a cable - and unhook. It will mention which interface it is.