Hi all,
I'm trying to get some dnsmaq stuff working on my desktop machine (Kubuntu). I've got a wifi interface that is my default (and only) route to the Internet.
I've also got a wired ethernet interface that I want to use to: - provide DHCP service to a headless server - provide NAT to that headless server so that it can connect to the internet
I've setup a dnsmasq config (using the defaults, but with some tweaks), but whilst it does actually serve DHCP to a laptop (for testing), it appears to set 2 default routes on my desktop, and I can no longer get onto the Internet.
Routing table while dnsmasq was running:
srdjan@serenity:~$ route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default dsldevice.lan 0.0.0.0 UG 100 0 0 enp37s0 default dsldevice.lan 0.0.0.0 UG 600 0 0 wlp38s0 link-local 0.0.0.0 255.255.0.0 U 1000 0 0 docker0 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 192.168.1.0 0.0.0.0 255.255.255.0 U 600 0 0 wlp38s0 dsldevice.lan 0.0.0.0 255.255.255.255 UH 100 0 0 enp37s0 192.168.2.0 0.0.0.0 255.255.255.0 U 100 0 0 enp37s0
I'm not sure this is correct. Dhcp-option 3 and 6 were left as default, but I would have expected the impact of those to be felt on the client machine trying to get the IP address, and not the "server" (desktop). Perhaps option 3 might make sense to set to the same address as the wifi router?
Once I tore down both enp37s0 and wlp38s0, and reconnected on wifi using the KDE network manager, did I manage to get back onto the internet.
Of note, the default config uses: interface=enp37s0 port=0 dns-range that is on a different network to the usual wifi one
Has anyone got any suggestions please on what plainly stupid thing I'm doing with my setup?
Thanks, Srdjan
On Sun, 28 May 2023 at 17:37, Srdjan Todorovic todorovic.s@googlemail.com wrote:
it appears to set 2 default routes on my desktop, and I can no longer get onto the Internet.
I've sorted this out now. It appears that I needed to select "Use this connection only for resources on its network" to resolve the issue. I believe (but not tried the command) this can also be done using: nmcli c mod em2 ipv4.never-default yes
Thanks, Srdj