How should I set up a static network alongside my wifi internet connection
https://askubuntu.com/questions/1560010/how-should-i-set-up-a-static-network-alongside-my-wifi-internet-connection
I think this should be easy but I am failing to do it and finding much contradictory information around the internet and much that goes back before various aspects of networking were changed. I last did this probably 20 years ago when I remember it being easy but so much has changed that I am going to ask here. Point me elsewhere if this is the wrong place.
I have two laptops: Tux and Juno (may convey their origins!), Tux is my main one and Juno is "fallback". Both are running Kubuntu 25.10 with everything updated daily. Both can use the various wifi networks I use as I move around. I use Tux as a qemu/virtual manager host running another Kubuntu 25.10 guest inside it. (So when things go pear shaped I can just use the backup copy of the guest and not have to reinstall and reconfigure everything.) That's a new set up as of a month or so.
What I want is for the two actual machines to be networked through wired ethernet (through a portable "Ubiquiti USW-FLEX-MINI UniFi USW Flex Mini Managed Switch"). With the ethernet wires plugged in I see the status bar connection icon in the guest and it says it's connected and shows tiny amounts of traffic. I don't see icon on host, not sure if that matters or is a function of the host passing it on. Oddly, and worryingly to me, I don't see the icon on the Juno fallback machine.
I had thought I could just set up fixed IPv4 addresses for the ethernet interfaces on both physical machines using private address space not being used by my wifi and, with the right netmask and same network and broadcast addresses, and perhaps having to declare a route I would have an wired network between the machines.
But so much has changed with everything managed by NetworkManager in System Settings now that I'm not passing go.
I had assumed that I might have to do a bit more in the guest/host configuration to enable the guest to see the fallback machine though that's not absolutely vital for me as this is mainly for overnight backups from the guest to the fallback machine done when the guest is down.
I can happily supply more information of course and, cautiously, tweak things, but ...
first edit starts here, replying to comment from vidarlo
Not sure why I lost "but I am worried about messing up a working host/guest machine." OK. Many thanks for helping vidarlo.
"What doesn't work when you simply configure static IP's?"
Sadly, I am not confident of how to do that! That's not helped by not seeing the wired connection icon on the task manager on Juno, the fallback machine and being worried about wrecking things for the Host/Guest pass through on the Tux machine. If you are confident of some instructions that work for [K]ubuntu 25.10 do please point me to them and I will try to follow them.
"What is your configuration like? Please provide output of ip a, ip route when you have it configured statically, ..."
I am guessing there is no point in me giving those until I pass go.
"... and tell us what doesn't work."
What doesn't work at step #1 for me as far as I am concerned is that the wired connection icon doesn't come up on the Juno machine yet it does on the guest on the other machine. That's not a cable issue as I have swapped the cables over and the situation stays the same.
In case it helps ip a on Juno gives:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp44s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether d4:93:90:2b:90:9d brd ff:ff:ff:ff:ff:ff
altname enxd493902b909d
3: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether c4:3d:1a:d9:6e:71 brd ff:ff:ff:ff:ff:ff
altname wlxc43d1ad96e71
inet 192.168.1.13/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp0s20f3
valid_lft 86105sec preferred_lft 86105sec
inet6 fe80::e6c0:f94b:ec84:7f5b/64 scope link noprefixroute
valid_lft forever preferred_lft forever
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:b5:0f:ac brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
and ip route gives
default via 192.168.1.1 dev wlp0s20f3 proto dhcp src 192.168.1.13 metric 600
192.168.1.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.1.13 metric 600
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
Very happy to do anything more on the fallback machine and get any diagnostics on the host machine. Many thanks, Chris