Problem with Captive Portal on Chelsio T520-SO-CR ports
codywood last edited by
I have recently purchased a Netgate XG-1540 w/2 Port Chelsio T520-SO-CR 10GbE adapter that I am configuring to replace a virtual pfSense firewall for our dorm network. I have the WAN and Dorm LAN configured to use the two 10GbE ports plugged into our switch, and an igb port for firewall management. When I enable the captive portal on the Dorm LAN, traffic stops and no authentication page is displayed. I am pulling a DHCP lease from the Netgate, the DNS server is set to the firewall like it should be, and I can even poll dns by using nslookup just fine.
Internet works fine on the Dorm LAN as long as the captive portal is off. The switch and Netgate is showing connected at 10Gb.
It my troubleshooting of the issue, first I verified that the switch and interface configuration was correct. I temporarily put an "allow all rule" on the dorm LAN to test if a rule issue. I have deleted the captive portal and set it up from scratch, thinking it may have been a version difference from our vm. Finally, I configured a new 1GbE connection on our switch and set igb1 as the new dorm LAN interface under interface assignments - and the captive portal started working.
To test it wasn't a problem on that line card of the switch, I configured another 10GbE port on a separate line card (one with another 10GbE firewall running) and set the Dorm LAN port to it - but still no captive portal authentication page when cp is enabled.
Does anyone have 2.4.2-RELEASE-p1 successfully running captive portal on the 2 Port Chelsio T520-SO-CR 10GbE adapter?
Any suggestions or help is appreciated!
mikeisfly last edited by
I have mine running on Chelsio 10GBASE-CX4 S320E-CXA 10GbE adapter and everything is working well for me. I am using :
built on Tue Dec 19 18:22:48 CST 2017
Which seems to be working well. Don't know if your environment will allow you to run a development branch but it is running very stable and I have not had any issues other than Captive Portal authenticating against LDAP but looks like that will be fixed soon. See https://github.com/pfsense/pfsense/pull/3640