Unable to redirect after authenticated



  • I am having this problem occasionally once the memory usage at 90%. User able to load the captive portal page, and it just won't able to connect to the Internet after authenticated.

    I found the error in system.log and portalauth.log

    Feb 27 15:44:50 wirelessgw1 php[48489]: : The command '/sbin/ipfw pipe 65828 delete' returned exit code '1', the output was 'ipfw: rule 1: setsockopt(IP_DUMMYNET_DEL): Invalid argument'
    Feb 27 15:44:50 wirelessgw1 php[48489]: : The command '/sbin/ipfw pipe 65829 delete' returned exit code '1', the output was 'ipfw: rule 1: setsockopt(IP_DUMMYNET_DEL): Invalid argument'
    Feb 27 15:44:50 wirelessgw1 php[48489]: : The command '/sbin/ipfw pipe 66920 delete' returned exit code '1', the output was 'ipfw: rule 1: setsockopt(IP_DUMMYNET_DEL): Invalid argument'
    Feb 27 15:44:50 wirelessgw1 php[48489]: : The command '/sbin/ipfw pipe 66921 delete' returned exit code '1', the output was 'ipfw: rule 1: setsockopt(IP_DUMMYNET_DEL): Invalid argument'
    Feb 27 15:44:50 wirelessgw1 php[48489]: : The command '/sbin/ipfw pipe 67222 delete' returned exit code '1', the output was 'ipfw: rule 1: setsockopt(IP_DUMMYNET_DEL): Invalid argument'
    Feb 27 15:44:50 wirelessgw1 php[48489]: : The command '/sbin/ipfw pipe 67223 delete' returned exit code '1', the output was 'ipfw: rule 1: setsockopt(IP_DUMMYNET_DEL): Invalid argument'

    I am using 2.0.1-RELEASE currently and the server equip with 8GB RAM.



  • you could try to update to pfsense 2.0.3 pre-release. There are many CP fixes.



  • Maybe this is a try. But this server in production and I had a bad experience with the previous RC. I need to reinstall the server and lead to 2 hours downtime.



  • I'm running 2.0.3pre in a production environment - to fix some CP issues (like post login redirect URL mangling) - did it as a live upgrade, no problems. I'd say it's ready to use.



  • it still has some issues, right now im using it and it is unable to to server what is meant for



  • @m4st3rc1p0:

    it still has some issues, right now im using it and it is unable to to server what is meant for

    There are no known 2.0.3 issues remaining, the only reason it hasn't been released is we're waiting for a security fix upstream in FreeBSD. If you have actual issues, post them, but I can pretty much guarantee it's config-related not release problems.



  • I had upgraded to 2.0.3-RELEASE, but the issue still exists. Same log found in system log and portal auth log.

    Jul 29 14:17:09 	php[16361]: : The command '/sbin/ipfw pipe 20001 delete' returned exit code '1', the output was 'ipfw: rule 1: setsockopt(IP_DUMMYNET_DEL): Invalid argument'
    Jul 29 14:17:09 	php[16361]: : The command '/sbin/ipfw pipe 20000 delete' returned exit code '1', the output was 'ipfw: rule 1: setsockopt(IP_DUMMYNET_DEL): Invalid argument'
    Jul 29 14:17:09 	php[16361]: : The command '/sbin/ipfw pipe 20001 delete' returned exit code '1', the output was 'ipfw: rule 1: setsockopt(IP_DUMMYNET_DEL): Invalid argument'
    Jul 29 14:17:09 	php[16361]: : The command '/sbin/ipfw pipe 20000 delete' returned exit code '1', the output was 'ipfw: rule 1: setsockopt(IP_DUMMYNET_DEL): Invalid argument'
    Jul 29 14:17:09 	php[16361]: : The command '/sbin/ipfw pipe 20001 delete' returned exit code '1', the output was 'ipfw: rule 1: setsockopt(IP_DUMMYNET_DEL): Invalid argument'
    Jul 29 14:17:09 	php[16361]: : The command '/sbin/ipfw pipe 20000 delete' returned exit code '1', the output was 'ipfw: rule 1: setsockopt(IP_DUMMYNET_DEL): Invalid argument'
    Jul 29 14:17:09 	php[16361]: : The command '/sbin/ipfw pipe 20001 delete' returned exit code '1', the output was 'ipfw: rule 1: setsockopt(IP_DUMMYNET_DEL): Invalid argument'