One thing in common between LE and OSMC is the connman network manager. Google DNS should not be required.The best I can suggest is running "touch /storage/.config/debug.connman && reboot" then "journalctl --no-pager -b -0 -f" to tail the system journal and look for issues being reported. Connman debug logging is VERY verbose, but also human readable. Delete the debug.connman file and reboot to revert the logging state.
Hi,
I'm also having this issue, it's not a routing issue or other network related issue.
Have a look bellow 1st tests are made to a device connect on the same switch, same ip space and subjected to the same firewall rules.
R: 0 P: [/root]
↳ [root@tiny]# nslookup linux-geex.com 192.168.246.1
Server: 192.168.246.1
Address: 192.168.246.1#53
Non-authoritative answer:
Name: linux-geex.com
Address: 163.172.197.194
↳ [root@tiny]# nslookup linux-geex.com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: linux-geex.com
Address: 163.172.197.194
Now the same test made from libreelec:
nslookup linux-geex.com 192.168.246.1
Server: 192.168.246.1
Address 1: 192.168.246.1
nslookup: can't resolve 'linux-geex.com'
nslookup linux-geex.com 8.8.8.8
Server: 8.8.8.8
Address 1: 8.8.8.8
nslookup: can't resolve 'linux-geex.com'
ping test to both destinations:
kodi:~ # ping 192.168.246.1 -c 4
PING 192.168.246.1 (192.168.246.1): 56 data bytes
64 bytes from 192.168.246.1: seq=0 ttl=64 time=3.801 ms
64 bytes from 192.168.246.1: seq=1 ttl=64 time=1.932 ms
64 bytes from 192.168.246.1: seq=2 ttl=64 time=1.757 ms
64 bytes from 192.168.246.1: seq=3 ttl=64 time=2.641 ms
--- 192.168.246.1 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 1.757/2.532/3.801 ms
kodi:~ # ping 8.8.8.8 -c 4
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=46 time=7.120 ms
64 bytes from 8.8.8.8: seq=1 ttl=46 time=6.868 ms
64 bytes from 8.8.8.8: seq=2 ttl=46 time=7.087 ms
64 bytes from 8.8.8.8: seq=3 ttl=46 time=6.823 ms
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 6.823/6.974/7.120 ms
libre elec iptables rules:
kodi:~ # iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
/etc/nsswitch.conf:
kodi:~ # cat /etc/nsswitch.conf
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
#
passwd: files
group: files
shadow: files
gshadow: files
hosts: files mdns_minimal [NOTFOUND=return] dns
networks: files dns
protocols: files
services: files
ethers: files
rpc: files
netgroup: files
libreelect version:
cat /etc/*release*
NAME="LibreELEC"
VERSION="7.0.2"
ID="libreelec"
VERSION_ID="7.0"
PRETTY_NAME="LibreELEC (WRXTASY) - Version: 7.0.2"
HOME_URL="http://www.libreelec.tv"
BUG_REPORT_URL="https://github.com/wrxtasy/LibreELEC.tv.7.0"
BUILD_ID="f39dcfbb2675d03d820923975050c3acabdc7427"
OPENELEC_ARCH="Odroid_C2.aarch64"
LIBREELEC_ARCH="Odroid_C2.aarch64"
LIBREELEC_BUILD="WRXTASY"
Odroid_C2.aarch64-7.0.2
cat /etc/resolv.conf
# Generated by Connection Manager
nameserver 192.168.246.1
Both devices use the same dhcp server and the only difference is the ip (within the same network range).
do you have a clue of what can be causing this?