Working on a new build coming from pfSense.
I have SSH access enabled, as well as root and password-based access enabled. I'm tying down outbound traffic and have a rule built for the LAN-based SSH access...but even tried a prioritized ALLOW ALL rule, just in case.
From the console, I can successfully do a 'ssh localhost'.
Just can't figure out what is stopping the SSH connection from a LAN connection.
Why not create an additional user and test again ?
Make sure it's member of the wheel group and has a shell :)
I can try that shortly....but as I mentioned, the root user appears to work fine when using the SSH login via the console. But I'll try another user just in case.
Quote from: ck42 on March 25, 2026, 05:20:23 PMI can try that shortly....but as I mentioned, the root user appears to work fine when using the SSH login via the console. But I'll try another user just in case.
I am worried about weird OpenSSH bugs : It would not be the first time! ;)
One of the first things I did with OPNsense was create a regular user with a shell and
wheel group membership and SSH access worked immediately.
Since SSH access by root is a default NO/Disabled option in the OpenSSH Server config file maybe it does not always do what it should after all these years...
Got it working. Off all things, Claude came up with the idea.
Went back into System>Settings>Administration and simply hit the 'Save' button again w/o even changing anything. BAM!