Feeling like a total n00b
-
Just ranting…
Did a total n00b move of removing traffic shaper on LAN and locked myself out. Had to reset the configuration and reboot the unit.
300+ days of uptime just gone like that...sigh
-
Well, removing the shaper should not lock you out and that reset was pretty unnecessary, it's just that the interface crashes. I've filed a bug about this many months ago and never heard back from anyone.
https://redmine.pfsense.org/issues/4424
-
I tried restarting the web configurator off the console and it didn't throw me any errors actually.
Unfortunately, the shaper was removed on LAN. So that locked me out of the webgui.
This was on an embedded install. I didn't exactly reset the configuration, just restored the older backup (which needed a reboot).
I just felt it was a pity to have an unscheduled take down on the unit since it went through 3 major WAN changes from Static IP to DHCP on my previous ISP and then to a new ISP with Gigabit fibre without having to reboot.
I guess it's a sign that I should stop procrastinating since I was supposed to upgrade from 2.1.5 to 2.2.x when I swapped ISPs.
The network gawds don't favour me it seems.
-
Unfortunately, the shaper was removed on LAN. So that locked me out of the webgui.
Correlation is not causation. They are completely unrelated. All traffic shaping does is route your traffic into different priority queues. It doesn't block or allow access to anything. I've personally added and removed shapers from running systems at least a dozen times without any such problem. The reset probably blew away your old System log. No way of knowing now what actually caused the problem.
-
@KOM:
I've personally added and removed shapers from running systems at least a dozen times without any such problem.
Consider yourself lucky. Just tried again with 2.2.5; took 3 attempts to crash LAN and single attempt to crash WAN. Between this and the infamous bug with limiters sending NATed traffic to /dev/null (zero progress as well), the usability of pfSense as traffic shaping/limiting platform is somehow severely crippled.
:( :'(
-
@KOM:
Correlation is not causation. They are completely unrelated. All traffic shaping does is route your traffic into different priority queues. It doesn't block or allow access to anything. I've personally added and removed shapers from running systems at least a dozen times without any such problem. The reset probably blew away your old System log. No way of knowing now what actually caused the problem.
I agree that it shouldn't, and I have done so in the past without any issues. In this case, the bug triggered a lock out (for whatever reason) and all LAN traffic dropped. At any going rate, I wasn't too keen on trying to check the circular logs over the console - not with the women of the house hounding me when their video streaming got cut off anyway.
Being an embedded install, the reboot wiped the logs. Not too important now I guess. Next install would be full install now that I cleared up a couple of SSDs to use on the system. Just need to find the time to do the other stuff I was planning (change of subnet and traffic shaping design).
-
Consider yourself lucky. Just tried again with 2.2.5; took 3 attempts to crash LAN and single attempt to crash WAN. Between this and the infamous bug with limiters sending NATed traffic to /dev/null (zero progress as well), the usability of pfSense as traffic shaping/limiting platform is somehow severely crippled.
:( :'(
That's actually one of the reasons I didn't take down the rig and upgrade to 2.2.x during the migration to the new ISP late last week. My new traffic shaping design would make use of limiters and that bug is kinda an issue.
-
Consider yourself lucky.
I stand corrected. All my previous work was on the 2.1.x branch. I haven't played with TS on 2.2.x at all.
not with the women of the house hounding me when their video streaming got cut off anyway.
Jesus, it was an emergency?? I'd rather wrestle a greased-up PHB than to have to deal with two women who you cut off in the middle of Say Yes to the Dress.
-
-
@KOM:
Jesus, it was an emergency?? I'd rather wrestle a greased-up PHB than to have to deal with two women who you cut off in the middle of Say Yes to the Dress.
Good lord, it's universal?
-
Well, removing the shaper should not lock you out and that reset was pretty unnecessary, it's just that the interface crashes. I've filed a bug about this many months ago and never heard back from anyone.
https://redmine.pfsense.org/issues/4424
I'll get to this eventually, just an uncommon circumstance and I'm up to my neck in more pressing things. If you want to make it move more quickly, figure out what's happening underneath, and see if same is replicable on stock FreeBSD 11-CURRENT.
For that matter, just trying 2.3 to see if it's already resolved in 10-STABLE would be helpful.
-
The moment you inadvertently press the "remove shaper" button on a box several hours drive away are certainly priceless. As I noted on the bug, for now it'd suffice to make the button do things in proper order, or (more easily), just force user to do it so that the queues are gone before the shaper itself and making it inactive otherwise.
-
-
The moment you inadvertently press the "remove shaper" button on a box several hours drive away are certainly priceless. As I noted on the bug, for now it'd suffice to make the button do things in proper order, or (more easily), just force user to do it so that the queues are gone before the shaper itself and making it inactive otherwise.
To add, I did try running a ifconfig <interface>down and up to toggle the interface to no avail through the physical console.
I initially tried running an easy pass rule thinking that the rules on the $if were dumped but that didn't work either so there's that.
This is the first time it has happened to me throughout the years (from 1.2 RC to 2.1.5) so I can't for the life of me figure out what went wrong.</interface>
