testbruker
Cadet
- Joined
- May 3, 2023
- Messages
- 1
I can add a 2nd IP from the web-interface and I can choose that TrueNAS Scale Web Interface should only listen to the 1st. However, it only says the web-interface, not the nas itself.
What happens to samba, ssh and other services on the NAS in this case - will they listen to both the IPs or is it smart enough to only answer requests on the 1st IP?
Why do I ask?
I have the NAS running on a local IP, but in some cases, it could be useful to publish an app to listen to the 2nd IP (public IP) - for instance to share some files. However, I suspect that my samba (and everything else) will also be accessible on that 2nd IP and bypassing the "security" of having the nas on local IP.
My idea was to run a proxy/firewall as app on the public app ip that can fire up when needed (for instance in a emergency situation, giving out filebrowser access to someone), but if everyone can try to login to samba shares at all times on 2nd IP, it comes at to high cost :)
What happens to samba, ssh and other services on the NAS in this case - will they listen to both the IPs or is it smart enough to only answer requests on the 1st IP?
Why do I ask?
I have the NAS running on a local IP, but in some cases, it could be useful to publish an app to listen to the 2nd IP (public IP) - for instance to share some files. However, I suspect that my samba (and everything else) will also be accessible on that 2nd IP and bypassing the "security" of having the nas on local IP.
My idea was to run a proxy/firewall as app on the public app ip that can fire up when needed (for instance in a emergency situation, giving out filebrowser access to someone), but if everyone can try to login to samba shares at all times on 2nd IP, it comes at to high cost :)
