After playing with Orange.Pi and DNS server I lost internet connections.
That was one month before, til now I was on Mint 18.3 searching solution and
learning networking in Linux .
What I found til now, that something in my config is broken and that systemd and
network manager are conflicting one another. I don't know who is in command
and broke things. All my devices have fixed addresses.
192.168.5.55 is my Orange.PI DNS and is working well. When I lose connection I go
to "network manager" and flip the switch and thing works again.
this is output of "nmcli device show" part that change when it's working-
Code: Select all
GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/10
WIRED-PROPERTIES.CARRIER: on
IP4.ADDRESS[1]: 192.168.5.10/24
IP4.GATEWAY: 192.168.5.99
IP4.ROUTE[1]: dst = 192.168.5.0/24, nh = 0.0.0.0, mt = 100
IP4.ROUTE[2]: dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000
IP4.ROUTE[3]: dst = 0.0.0.0/0, nh = 192.168.5.99, mt = 20100
IP4.DNS[1]: 192.168.5.55
IP6.ADDRESS[1]: fe80::ad74:e5ba:a0fd:c943/64
IP6.GATEWAY: --
IP6.ROUTE[1]: dst = ff00::/8, nh = ::, mt = 256, table=255
IP6.ROUTE[2]: dst = fe80::/64, nh = ::, mt = 256
IP6.ROUTE[3]: dst = fe80::/64, nh = ::, mt = 100
Code: Select all
GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/17
WIRED-PROPERTIES.CARRIER: on
IP4.ADDRESS[1]: 192.168.5.10/24
IP4.ADDRESS[2]: 192.168.5.102/24
IP4.GATEWAY: --
IP4.ROUTE[1]: dst = 169.254.0.0/16, nh = 0.0.0.0, mt =
IP4.ROUTE[2]: dst = 192.168.5.0/24, nh = 0.0.0.0, mt =
IP4.ROUTE[3]: dst = 192.168.5.0/24, nh = 0.0.0.0, mt =
IP4.DNS[1]: 192.168.5.55
IP6.ADDRESS[1]: fe80::156c:9774:3e98:d5e7/64
IP6.ADDRESS[2]: fe80::ad74:e5ba:a0fd:c943/64
IP6.GATEWAY: --
IP6.ROUTE[1]: dst = ff00::/8, nh = ::, mt = 256, table
IP6.ROUTE[2]: dst = fe80::/64, nh = ::, mt = 256
IP6.ROUTE[3]: dst = fe80::/64, nh = ::, mt = 100
IP4.ADDRESS[2]: 192.168.5.102/24
that I was using when was playing with Orange.Pi.
My questions are obviously how to solve this error but more precisely where is
that broken data file and who is putting it in charge. Why I say I hit the systemd wall, is
that I don't understand how systemd-resolver works even after reading man. All logic in
systemd-resolver to me is going in cirkular loop and I don't know where is beginning
and where is the end.
Sorry for my English, not my speaking language. I will appreciate any helping hand.