Native SSH

[blstmo]

Is your feature request related to a problem? Please describe.
I find it quite annoying coming from tailscale to this where we are unable to just use ssh user@netbirdip we have to use netbird ssh ip for some reason I dont understand why it cant just be implemented like tailscale does it

Describe the solution you'd like
Allow users to use normal ssh commands instead of netbirds ssh commands to make compatibility far greater

Describe alternatives you've considered
Tailscale has this feature by default

[PowershellScripter]

I can confirm this does not currently work on PFSense router either. It wont even connect via the netbird IP natively or through management console.

[mlsmaycon]

Hello Folks, we are working on refactoring the feature so you won't need to use the NetBird client directly.

The PR is: #4015

We also have a request for comments in our slack channel here:

https://netbirdio.slack.com/archives/C028VPB34NB/p1760710292090869

[PowershellScripter]

@mlsmaycon thank you for this. I was able to resolve my SSH issue with my pfsense routers by just adding firewall rules to allow SSH traffic from my NETBIRD FLOCK (subnet) to the routers LAN IP, bypassing Netbird altogether. Will this PR make this method deprecated and no longer needed or will I still need to use firewall rules to use native port 22 ssh to the routing peer?

[mlsmaycon]

@PowershellScripter, you will need to update the port since we will listen to a different one and handle this access with a DNAT type of rule. Anything to add or correct @lixmal ?

[PowershellScripter]

@mlsmaycon Im fine with using whatever dedicated port Netbird listens on (as long as it doesnt dynamically change), Im just trying to make sure I understand the process and limitations. When enabling the ssh connection in PFSense as well as NetBirds management, no additional firewall rules will be needed to connect to native SSH, yes or no? Will I also be able to ICMP the routers LAN IP with this implementation as well? I had to also add a firewall rule for that as well. Id much rather restrict SSH and ICMP via the NetBird Management console as I can delegate peer group access and not have to manage any rules via the PFsense firewalls.

[lixmal]

@PowershellScripter see https://docs.netbird.io/how-to/installation/pfsense#configure-firewall-rules-for-the-net-bird-interface to configure the firewall for passthrough so NetBird can manage the access.

[PowershellScripter]

@lixmal I cant test that atm because I also have tailscale setup in my env and if I assign the adapter to netbird statically, it causes a config mismatch on reboot and corrupts the config and reverts it back to a previous config. Caused alot of fuss. I am testing all the setup as we prepare to migrate to NetBird. Im assuming these rules will apply to the native ssh once this PR is implmented?