Hey there,
uploading armbianmonitor failed, due to the connection issues, so i pasted it somwhere else: https://nopaste.xyz/?40aa3fcbb5834d1c#a9goEaQrtfCzF+MAAhWDb4+Gbfq6UMa2smyGL+ShbME= password is armbian
My problem is, that there is no working outgoing IPv4 Traffic, i cant even ping a v4 adress. But on adresses, that get a AAA-Response from DNS it works fine.
Had pihole installed, removed it for testing but this didn't make an difference.
No firewall in use, iptables is empty at the moment.
Every v4-Request ends up in a !N or No route to Host.
While using pihole, i saw that the request went throug to pihole and was forwarded by it, also the resolving to an ip worked fine.
So it's hard to find some information about this scenario, therefore i decided to start a thread in here.
In the same network i can easily ssh into the pi with the v4 it gets from DHCP, DHCP is done by the router (was also done by the router while pihole was installed).
In var/log/messages i can see the buildup of Connection with no errors, if needed i can paste this, too. (as well as the ping reply for v4/v6 or everything else you might want to see)
Yeah, not sure what this is all about…grateful for all sort of ideas
also @ freenode in #armbian, in case of someone is idling there and reading here
Edit: Just pasting the strange Ping-situation immediatly, in case of someone thinks i may just be too stupid to ping
root@bananapi:~# ping google.de
PING google.de(fra16s13-in-x03.1e100.net (2a00:1450:4001:819::2003)) 56 data bytes
64 bytes from fra16s13-in-x03.1e100.net (2a00:1450:4001:819::2003): icmp_seq=1 ttl=57 time=14.7 ms
64 bytes from fra16s13-in-x03.1e100.net (2a00:1450:4001:819::2003): icmp_seq=2 ttl=57 time=14.3 ms
64 bytes from fra16s13-in-x03.1e100.net (2a00:1450:4001:819::2003): icmp_seq=3 ttl=57 time=14.0 ms
^C
--- google.de ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 14.059/14.392/14.766/0.290 ms
root@bananapi:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 192.168.100.40 icmp_seq=1 Destination Host Unreachable
From 192.168.100.40 icmp_seq=2 Destination Host Unreachable
From 192.168.100.40 icmp_seq=3 Destination Host Unreachable
^C
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3078ms
pipe 4
also the output of ifconfig, even though its also part of the above pasted armbianmonitor:
bond0: flags=5123<UP,BROADCAST,MASTER,MULTICAST> mtu 1500
ether 36:f9:0d:f7:d8:b7 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
dummy0: flags=195<UP,BROADCAST,RUNNING,NOARP> mtu 1500
inet6 fe80:<censored>:9e04:34c7 prefixlen 64 scopeid 0x20<link>
ether d2:ac:0a:b8:d9:b5 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1239 bytes 489405 (477.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.100.40 netmask 255.255.255.0 broadcast 192.168.100.255
inet6 2003:<censored>:ee4f:61f8:564a:b35f prefixlen 64 scopeid 0x0<global>
inet6 2003:<censored>:e24b:6a84:ce4:1fa5 prefixlen 64 scopeid 0x0<global>
inet6 fe80::<censored>:9784:b673 prefixlen 64 scopeid 0x20<link>
ether 02:10:08:42:d2:8c txqueuelen 1000 (Ethernet)
RX packets 601750 bytes 48435497 (46.1 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2033153 bytes 2954998671 (2.7 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 60
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 5450 bytes 489081 (477.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5450 bytes 489081 (477.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
aand the var/log/messages part of the buildup:
Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.0508] manager: NetworkManager state is now CONNECTING
Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.0564] device (eth0): state change: prepare -> config (reason 'none') [40 50 0]
Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.0965] device (eth0): state change: config -> ip-config (reason 'none') [50 70 0]
Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.1089] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.1781] dhcp4 (eth0): dhclient started with pid 1113
Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.4654] dhcp4 (eth0): address 192.168.100.40
Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.4687] dhcp4 (eth0): plen 24 (255.255.255.0)
Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.4690] dhcp4 (eth0): gateway 192.168.100.1
Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.4691] dhcp4 (eth0): server identifier 192.168.100.1
Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.4692] dhcp4 (eth0): lease time 864000
Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.4694] dhcp4 (eth0): nameserver '192.168.100.1'
Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.4695] dhcp4 (eth0): domain name 'fritz.box'
Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.4698] dhcp4 (eth0): state changed unknown -> bound
Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.5425] device (eth0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.5757] device (eth0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.5871] device (eth0): state change: secondaries -> activated (reason 'none') [90 100 0]
Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.5901] manager: NetworkManager state is now CONNECTED_LOCAL
Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.6569] manager: NetworkManager state is now CONNECTED_GLOBAL
Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.6584] policy: set 'Armbian ethernet' (eth0) as default for IPv4 routing and DNS
Feb 12 10:17:58 localhost NetworkManager[654]: <info> [1549966678.0054] device (eth0): Activation: successful, device activated.
Feb 12 10:17:58 localhost NetworkManager[654]: <info> [1549966678.8260] dhcp6 (eth0): activation: beginning transaction (timeout in 45 seconds)
Feb 12 10:17:58 localhost NetworkManager[654]: <warn> [1549966678.8265] dhcp6 (eth0): hostname is not a FQDN, it will be ignored
Feb 12 10:17:58 localhost NetworkManager[654]: <info> [1549966678.8693] dhcp6 (eth0): dhclient started with pid 1178
Feb 12 10:17:59 localhost NetworkManager[654]: <info> [1549966678.9849] policy: set 'Armbian ethernet' (eth0) as default for IPv6 routing and DNS
Feb 12 10:17:59 localhost NetworkManager[654]: <info> [1549966679.0645] device (eth0): ipv6: duplicate address check failed for the 2003:<censored>:8447:32d7:aacf/64 lft 7199sec pref 1097sec lifetime 13$
Feb 12 10:17:59 localhost NetworkManager[654]: <info> [1549966679.8293] dhcp6 (eth0): nameserver 'fd00::9ec7:a6ff:feec:bebd'
Feb 12 10:17:59 localhost NetworkManager[654]: <info> [1549966679.8296] dhcp6 (eth0): state changed unknown -> bound
Feb 12 10:17:59 localhost NetworkManager[654]: <info> [1549966679.8950] dhcp6 (eth0): client pid 1178 exited with status 0
Feb 12 10:17:59 localhost NetworkManager[654]: <info> [1549966679.8952] dhcp6 (eth0): state changed bound -> done
but when asking ip route, it says:
default via 192.168.178.1 dev eth0 src 192.168.100.40 metric 203
169.254.0.0/16 dev eth0 scope link metric 1000
192.168.100.0/24 dev eth0 proto kernel scope link src 192.168.100.40 metric 203
192.168.178.1 dev eth0 scope link src 192.168.100.40 metric 203
hmm, where does the wronge gateway come from?
Grepping through config dirs i found it, a double-config in /etc/dhcpcd.conf
# Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac private
interface eth0
static ip_address=192.168.178.40/24
static routers=192.168.178.1
static domain_name_servers=127.0.0.1
interface eth0
static ip_address=192.168.100.40/24
static routers=192.168.100.1
static domain_name_servers=127.0.0.1
Not sure how this could come, but as there is a dns-bind to localhost i assume pihole gifted me with this error.
Unsure why it would do that, but commented the first block out and everything was fine:)
Biggest thanks to wysiwtf in #armbian, solution was his work
So this is solved…if someone knows about the source of this would be glad for the info, though this shouldn't happen no matter what one does…
