PF Sense stuck after scroll lock
-
Hello again guys, sorry for being a newbie here,
But when i am on the command display of the pfsense, where you have all those selection to either example ping host or change Interface IP, well after i did press scroll locks, and scroll up and down, now i cant type anything on it, even if i press scroll lock again, how to i make it back to normal again?
*I am able to enter the GUI interface of pfsense without any problem -
Hmm, don't think I ever tried pressing scroll lock. Does the keyboard LED switch on/off when you press it now?
The obvious answer is: reboot the box and don't press it again! But that's not helpful if this is a production box.
Can you ssh in?
Steve
-
Yes the LED light do on and off according to my scroll locks, keyboard is functioning, and yea it's a production box, that is why I can't get it to reboot as it will affect loads of user currently, what about ssh log in?
-
If you can ssh in to the command line you can do anything you would otherwise do at the console. Then reboot the box at some convenient time.
There maybe some easy way to fix this though, I just don't know what it is. :-
Anyone?Steve
Edit: typo
-
Ya i did ssh in it and it works fine, yup maybe i gotta wait until sunday till everyone is mostly offline, but i do hope that someone could help, anyway thanks steve :)
-
When you press Scroll Lock again it should jump back down to the actual input. Do you have it hooked up to a KVM or something else that might have captured the Scroll Lock keypress?
While in "scroll back" mode, page up/page down will move around but as soon as Scroll Lock is pressed again it goes back to the "bottom" and accept input.
Though I have seen KVMs that grab scroll lock and might be redirecting the event depending on the timing of the keypresses.
-
If that is the case is there any way of coming out of 'scroll mode' by SSHing in? Perhaps resetting the console completely? Maybe re-assigning the keyboard and then restore it? I'm just not familiar enough with FreeBSD at this level.
Steve
-
Probably better off just rebooting it this weekend since it is a production box. Hate to monkey with some unknown and then have a "whoops" moment.
-
With 2.1.2 now out I guess a reboot will be in order anyway.
Still left with the fact that the behaviour of the box is unexplained. What happens if someone hits scroll lock again in the future? Always better to solve things by actually understanding what happened. :)Steve
