Shaper Wizard generates bogus rules for VoIP
-
No update, I am trying every build comes out! No difference. No moves
-
You can watch the Redmine link and https://github.com/bsdperimeter/pfsense/commits/master for any updates to traffic shaper code. Once you see an update, wait till the next day (or build your own iso) or so and then update.
-
Thanks pod, though I knew that part I guess what I'm saying is, this is a major portion of pfSense, and while I'm not a programmer, if there's anything in terms of testing or anything to push this fix along, toss me a message :)
-
You can watch the Redmine link and https://github.com/bsdperimeter/pfsense/commits/master for any updates to traffic shaper code.
It's a kernel issue, you'll see it in https://github.com/bsdperimeter/pfsense-tools/commits/master , not there. But the ticket will be updated in redmine. It may be some time still, Ermal who does all our kernel work is buried in customer development projects at the moment and what pays our bills has to come first. Those are wrapping up, hopefully after BSDCan he can knock out the remaining major kernel-related issues in 2.1/FreeBSD 8.3.
-
Thanks for the info and the link :) I got myself into this mess myself because I counted on 2.1 coming out by the end of April when there's no promises or guarantees in this world :D Thanks for all the great work you guys do. I tried a bunch of other solutions and found nothing I liked as well. Sure, part of that maybe familiarity, but still… great job!
-
@cmb:
It may be some time still, Ermal who does all our kernel work is buried in customer development projects at the moment and what pays our bills has to come first. Those are wrapping up, hopefully after BSDCan he can knock out the remaining major kernel-related issues in 2.1/FreeBSD 8.3.
That's great news, because I had noticed the slowdown of commits in the 2.1 tree at git for several weeks now and wasn't quite sure what was going on …
-
Thanks for the info and the link :) I got myself into this mess myself because I counted on 2.1 coming out by the end of April when there's no promises or guarantees in this world :D
Unfortunately FreeBSD and many other things aren't as IPv6-ready as we'd hoped for a number of the things we rely upon so we've had to do a lot more than just slap a GUI on things (though that's long since become the norm).
That's great news, because I had noticed the slowdown of commits in the 2.1 tree at git for several weeks now and wasn't quite sure what was going on …
That's not true at all, there hasn't been any slow down in commits.
https://github.com/bsdperimeter/pfsense/graphs/commit-activity -
Well, I see Ermal's back to working on pfSense today, so hopefully that's a sign this'll get addressed sooner than later :) Thanks for the wonderful work pfSense team!
-
This is semi-fixed now. Traffic shaping still doesn't work due to 2349, and the patch changes to fix this seem to have broke the PPTP server
-
You need to install a new snapshot where this has been fixed.
A local pfsense patch was missing hence the errors. -
@ermal:
You need to install a new snapshot where this has been fixed.
A local pfsense patch was missing hence the errors.As I said, it's semi-fixed in the latest snapshot. This error is gone, but the traffic shaper still doesn't work due to 2349. Additionally, this (or another very recent change since rolling back to Wednesday's build fixed it) breaks the PPTP server.
-
For those of us not using vLANs, this seems to have fixed the issue. Thank you very much Ermal!!!
-
I can confirm that Shaper is working again. Not using VLANs. Thanks, Ermal!
FWIW, my PPTP server (terminates on pfSense box) is also still functioning - was just able to login from my phone and view some Samba shares.
-
Glad to hear it's working for others! I wonder why last night's build killed my PPTP server? I could not get it working and rolling back to a build from Wednesday it was up just fine. I guess since traffic shaping isn't fixed for me anyways, I'll wait for the VLAN bug to be solved, and try again.
And make sure I'm on-site. Last night was adventurous. This install is about 30 miles from me. I did the firmware upgrade at 1:30am and boom - lost connectivity. Hoping there were Internet issues up there or something I waited until 2:30 to take off (again, I didn't KNOW I just killed PPTP, for all I knew, their whole network was down). Got there at 3:00am, had PPTP back up after giving up and rolling back by 3:40. Finished setup tweaks like fixing FreeRADIUS a bit after 4, and was in bed for the night about 5am…
