[Resolved][Captive portal error] need a pipe/flowset/sched number
-
I've upgraded to a new snapshot and noticed this error spaming the console whilst booting up when the captive portal service is started.
need a pipe/flowset/sched number
This is the error I get once I login through the captive portal
need a pipe/flowset/sched number Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/captiveportal.inc:1877) in /etc/inc/captiveportal.inc on line 1946
Once this happens the client is stuck in limbo and cant proceed any further, for now I've had to disable the captive portal.
AMD64 build
-
Ive got back to the earliest firmware upgrade on the snapshot server which is pfSense-Full-Update-2.1-BETA1-amd64-20130504-0557.tgz, and Im still experiencing the error, I have tried removing traffic shaper and also putting in a value for "Per-user bandwidth restriction" in the captive portal settings, as I normally have this set from a freeradius server.
Any idea where this error is coming from?
-
I pushed a fix but you have something wrong in your database of CP hence the error.
Try going to the next coming snapshot or gitsync to avoid having the error but this customer will still nto be able to go anywhere.
Please got to status->CP and remove the affected host. -
Thanks for the reply,
Ive update through gitsync, I have also manually gone through my config.xml and cleaned it up, also removing any references for captive portal.
I created a brand new zone, but as previously, any client that connects has the exact same problem after authenticating, the error shows up and they are stuck, neither able to be redirected to the login page nor browse to an external site, although the only difference I noticed after I gitsync'd was the error was no longer spamming the console when the cp zone is enabled on startup.
I have tried to google around for the error "need a pipe/flowset/sched number" and I can only find reference to freebsd ?dummynet.
I have only recently started experimenting with IPV6 and traffic shaper, I know IPV6 has issues with captive portal on 2.1 and wont be addressed till 2.2 so I have IPV6 disabled on the captive portal interface, the only other thing I can think of is the traffic shaper?
Again only by disabling captive portal can clients browse the internet.
Ill be more than happy to show any settings or outputs to solve this, thanks.
-
Just feedback for this problem.
I cleaned up the config.xml further, this originally came from a 2.0.3 installation which I upgraded to 2.1 about 3 weeks ago.
Anyhow, I downloaded a new ova snapshot, applied gitsync and restored my config.xml, all works as expected.Thanks
-
Did you install the last snapshot (May-10-2013) in order to correct the problem?
Another user at the Spanish Forum has the same error. He made a new installation and the system continues to fail.
http://redmine.pfsense.org/issues/3024
http://forum.pfsense.org/index.php/topic,63207.0.html
Any idea that can be the cause of this error?
-
I dont think it affects new builds unless the config.xml has been migrated from 2.0.x builds and only in some cases.
I can distinctly remember editing the config.xml and the error went away afterward, I removed all references to CP in the config.xml, restored then applied a new config for the CP via GUI, creating a new zone etc.
I do remember removing some other (what seemed to be) redundant tags, from the top of my head I think they had something to do with gateway dns's, but I doubt thats related, incidently, I am also running external radius.
TBH I never really did figured out what caused that problem.
-
Confirmed, the snapshot of the July 14, 2013 still has the error, I had to reinstall.
-
When the problem occurs, the captive portal only creates a limiter like the one below.
Some boddy can help me please, i had to reinstall the server more than 5 times and every time I do I do with the last snapshot, but still fails
Limiters:
00001: 262.140 Kbit/s 0 ms burst 0
q131073 100 sl. 0 flows (1 buckets) sched 65537 weight 0 lmax 0 pri 0 droptail
sched 65537 type FIFO flags 0x0 16 buckets 0 active -
I think I'm close to the problem, I deleted the database files belonging to the captive portal / var / db and then restart the server and the problem went away, the captive portal created files again, but I would like a pfSense developer to assess them to determine the problem.
The databases are encrypted.
-
The problem revolved around an error in a function in the captiveportal.inc, is corrected in this link. http://redmine.pfsense.org/issues/3062