Why does NetworkManager add a link-local IP address 169.254.105.42/16 to the slave interface when I create a bridge?
What is it used for? It ruins my internet connection and manually correcting the routing table does not fix it.
If I traceroute 8.8.8.8 then it tries to use the link-local address to reach the default gateway. Yikes!
What is it used for? It ruins my internet connection and manually correcting the routing table does not fix it.
If I traceroute 8.8.8.8 then it tries to use the link-local address to reach the default gateway. Yikes!
Code:
$ sudo nmcli connection add type bridge con-name 'Bridge 1' ifname br1$ sudo nmcli connection add type ethernet con-name 'Slave 1' ifname eno1 master br1$ nmcli | catnmcli (bad)br1: connected to Bridge 1"br1"bridge, B6:5D:C5:E2:D1:E9, sw, mtu 1500ip4 defaultinet4 192.168.1.130/24route4 192.168.1.0/24 metric 425route4 default via 192.168.1.1 metric 425eno1: connected to Connection 1"Intel I219-LM"ethernet (e1000e), 0C:C4:7A:CD:BE:20, hw, mtu 1500master br1inet4 169.254.105.42/16route4 169.254.0.0/16 metric 0route4 0.0.0.0/32 metric 0route4 default metric 0DNS configuration:servers: 192.168.1.1domains: private.laninterface: br1$ ip route show table main0.0.0.0 dev eno1 scope linkdefault dev eno1 scope linkdefault via 192.168.1.1 dev br1 proto dhcp src 192.168.1.130 metric 425169.254.0.0/16 dev eno1 proto kernel scope link src 169.254.105.42192.168.1.0/24 dev br1 proto kernel scope link src 192.168.1.130 metric 425Statistics: Posted by snovotill — 2024-05-31 02:43 — Replies 1 — Views 14