My first post here, my first few days running Tumbleweed. I decided to step out from under the Ubuntu umbrella and replace my KDE neon developer install with Tumbleweed. I’ve got two other Ubuntu boxes on my network, so I’m familiar with how they do things. Their names are “mick” and “joe” (I’m a big Clash fan; this laptop is “topper”).
Under Ubuntu (and from my MacBook), I could connect to them as “mick.local” or “joe.local”. SSH, ping, web servers, etc. I can’t do that from this openSUSE installation. I’m not a network expert; I freely admit that. To make things more complicated, I’m running KDE Plasma, and it seems the network settings are split between YaST and KDE’s Network Manager. On my boxes running that other Linux variant, I didn’t have to make any changes to the network configuration, and I didn’t have to make any changes on my router.
My guess is that I’m missing something really simple; but it’s so simple that I can’t figure out what it is.
While you can of course give them names in the .local domain, I see no need for that. You could just use the names michk and joe.
But of course those systems must be configures somewhere in your system. Systems can not know that magically. Thus put them in /etc/hosts. You can do that with YaST > Network Services Hostnames. Use Add and fill in:
IP address: the IP address of mick
Hostname: mick.local
Host Aliases: mick
Then you can use both mick and mick.local to be resolved to the IP address.
Guess your # of machines is ‘magnificent seven’ ? ( big Clash fan too ).
AFAIK Ubuntu only uses Networkmanager for networking. openSUSE uses wicked or Networkmanager. If a desktop machine is connected wired during install, the installer will default to wicked ( no need for users to interfere with connections ). So, if you’re more confortable with Networkmanager, switch it. But make sure in such case that you make the connection available to all users, otherwise it will not start until the DE is loaded.
I broke down and went the easy route: added them to the laptop’s HOSTS file. The two machines in the basement are on ethernet with fixed IPs, so this seems like the easiest solution.
I did check, though - the avahi daemons are running on all the machines (including the laptop). Don’t know why those hosts aren’t getting automatically picked up.
I looked through some of the Arch documentation, but Arch docs make my head hurt. That’s why I’m not running it. Too hardcore!
And no, my machine count hasn’t yet reached Magnificent Seven levels. But when I was setting up and running my own REST API for a project, the web server was named, of course, RadioClash. Targeting your living rooms, cashing in the Bill Of Rights!
Because those systems do not have link-local addresses, but “normal” addresses that belong to the LANs subnet (the ones you configured as fixed IP addresses).
( big Clash fan too ).