How to secure a minimal home WiFi network

I am setting up a (very) minimal home WiFi network, a desktop (TW1) and a laptop (TW2) both running Tumbleweed Gnome, both connected to a WiFi hotspot.
Test setup, already working, has a local only hotspot with dhcp but no local dns, so mdns/avahi enabled on both systems for automatic zeroconf discovery.
Main use case is remote login from TW2 to TW1, so the firewall on both systems has the WiFi interface assigned to the “home” zone, with cockpit (tcp 9090) and ssh (tcp 22) enabled for remote administration and rdp (tcp 3389) for desktop remote login.

All good as long as I use a test hotspot without internet access, but if I switch on the internet router hotspot, which I cannot configure BTW, should I take additional measures to prevent anyone potentially logging in to my systems via ssh or rdp?

[Very basic network knowledge here, but I can follow technical docs if pointed in the right direction, thanks]

Bruno, is the WLAN Hotspot managed by your local council (government) or, by a local Telecommunications company?

  • In both cases, it’s a public Internet Access Point – the Firewall setting required is either “external” or “public”.

Yes, but then I have to open ssh and rdp in the “public” zone? And doesn’t that lead to the same potential security problem? Or is it managed in a different way by firewalld?

Yes, that is a security issue but, you have no other choice – which is of course a disadvantage of WLAN Hotspots …

I did a couple of basic tests. Apparently what is exposed to the internet is the router IP address, not individual addresses of systems on the home subnet (which are local and not public, by the way).
Trying to ssh that “router” address just times out, the same with cockpit on port 9090.
So unless I am missing something the router (and/or provider) are better than I thought and exposing ports 22, 9090 etc. looks not that dangerous.
Unless of course somebody logs in to the same hotspot, which is unlikely and which I can monitor if in doubt.

Nonetheless, other views from network gurus are welcome.

1 Like

@OrsoBruno If you don’t have control over your Wi-Fi router and can’t even assign static IP addresses to your computers, it might make sense to consider using some kind of VPN protocol. To be honest, I haven’t tried this myself, but it’s the first thing that came to mind.

On the other hand, if you set up strong enough authentication (with sufficiently complex passwords), it’s not all that bad.

Not sure what kind of internet router you have but I guess it is a ADSL, Cable of Fiber router, right? Can you share the type number?

These devices are typically configured as masquerading firewall, that is one outside address and a private range IP range inside. The internal devices are connected via a (Ehternet) hub.

Most typically the router has no open ports on the Internet side apart from maybe a provider network management port meaning that no connection from the outside/Internet to your inside machines can be made and in that sense no additional firewalls are needed.

Be sure to set a secure WiFi PSK password at least if you can set that and your WiFi connection will be also pretty safe.

1 Like

Thanks, likely a “typical” rebranded box here as well so let’s assume it follows your description. My basic test confirms that there is one outside address and a 10.xxx.xxx.0/24 private range inside and systems inside cannot even be pinged from the internet.
The only possible config on my side is setting a WPA2/WPA3 Personal passphrase, which I used to replace the default one, so pretty safe on that side.

I will consider ssh authentication via private/public key pairs to be on the safe side, something to study on next rainy weekend :wink:

On transparent ssh, ignore ssh-agent completely and just generate the key pair on one side and copy it to the other side and done.

https://www.ssh.com/academy/ssh/copy-id

1 Like

Bookmarked, thanks.

Great! I shall still study the details, but following the example procedure set up private key authentication in five minutes.
Now I guess I can (should?) disable ssh password authentication on the server, but that should be covered in the SLES docs.

What some ISP routers can do, if you have access to the admin part, is making DHCP reservations. Mine has that, and every one of my own devices always has the same IP address. I haven’t done that, I know the IPs, but you could create entries in /etc/hosts and ssh into TW1 from TW2 with ssh bruno@TW1

Yes, setting up /etc/hosts for your local network is a good idea.

Not 100% sure what that is, do you want to forbid a ssh connection from TW2 to TW1?

I think he’s using key authentication. So, ssh from TW1 to TW2 after ssh-copyid TW2, and then do the same from TW2 to TW1,

Yes if you do ssh authentication using key pairs as suggested above, it’s a good idea to disable password-based connection from the ssh server.

As regards your machine’s addresses not visible, it’s always the case for IPv4 but not necessarily with IPv6, which will depend on the router’s setup.

Finally, another approach is to set up an encrypted virtual network that can be accessed from anywhere, home or not. This requires an initial setup using a gateway on the web (self-hosted or using a subscription) but once done, is very effective. Plenty of solutions, most of them open source (Pangolin, Octelium, Tailscale, Netbird etc.).

Thanks for those additional hints, as said I have a lot to learn on networking.
This thread is about setting up a minimal home network with minimal effort and no admin access to the router; main use case is offloading some jobs to another box without having to go upstairs to monitor it, with enough security for such a use case (no Fort Knox here).
So things to do on next weekend:

  • possibly disable ports where not needed (ssh from TW2 to TW1, the reverse is not needed);
  • investigate IPv6, possibly disable it;
  • enable key authentication wherever possible and disable password if available.

Will report back If I find something useful to the casual reader with similar needs.

1 Like

Oh – so not really my understanding of a “WLAN Hotspot” – a WLAN service offered by a local community or a location such as an airport waiting area or a railway station or, a moving Hotspot such as those on railway trains.

If I’m understanding you correctly, you want to setup a private (@home) WLAN from a Router which connects to an ISP (Internet Service Provider) [with a monthly fee for the service provided … ].

  • If you simply accept the box provided by your ISP then, usually the things are preconfigured and, have WLAN enabled.

But, there are two issues I personally have with such preconfigured boxes:

  1. The SSID (Service Set Identifier) value – a WLAN is Radio (Wireless) and therefore your neighbours can also “see” your SSID – which your ISP has set to some generic universal string which every router in your neighbourhood supplied by that ISP will also use.
    Therefore, you need to initially login to the box and set the SSID to some string which will uniquely identify your WLAN in your neighbourhood …

  2. The WPA (Wi-Fi Protected Access) password – it’s usually a very long Hexadecimal string which is difficult to accurately type – especially on Mobile Telephones … :smiling_imp:
    OK, the Router may offer the possibility to produce a QR-Code which you can either print onto a sheet of paper or whatever – which your Mobile Telephone(s) can then scan to also gain access to your WLAN.
    Or, you can login to the box and set the WPA password to something which is secure enough but, easier to type into all your devices (including the refrigerator and, the Television receiver) which you may want to connect to your (private) WLAN.

Apart from that, a WLAN which is served from a Router connected to an ISP is usually setup with private IP addresses – the DHCP service provided by the box will issue private IP addresses to the devices connected to your (private) WLAN – your WLAN is a private IP address space.


Bottom line, provided that your private WLAN has a reasonably secure SSID password, then only you can access your private WLAN.

  • Restricting access to only those devices with a known MAC address is somewhat more complicated … :smiling_imp:

Yes Don, this is it and your description confirms that changing the default settings of those pre-configured boxes is the first thing to do.
Nevertheless a competent WiFi sniffer might still be able to log in, but my WiFi router is HW-protected (I mean, if anybody gets within the hotspot range the dog starts barking :wink: ).

By the way not everybody is aware that a long phrase that is difficult to guess but easy to remember (like “MyfriendGeorgedoesnothave35dogsnamedBobby!”) is as secure as any random sequence of comparable length, so those random default sequences are convenient to the production equipment but don’t add any meaningful security.

2 Likes

I do that. I disable password authentication for ssh on all systems.

It is also useful to look into ssh certificates.