add-ons not loadable

1st Official Post

    Hi, I can play movies from the NAS in my network.

    What I can not is add-ons to load, whether with libre ELEC 7.0.3, still with 7.90
    The error message: no connection to repository.
    Since I come with all other clients in the same network into the www, I exclude a mistake in my network. Libreelec does not differ in any configuration to my other clients. Fixed IP, standard gateway is the router, in the router allows outgoing.

    Also the time is not set, NTP servers are registered.

    Edited once, last by termite (January 13, 2017 at 10:39 AM).

    • Official Post

    I had something similar but on Ubuntu. I solved it by setting the fixed IP in my router and setting Ubuntu to DHCP.
    Everything worked after that.

    BTW: Can you change your "Subject" to be a bit more specific - add-ons - is not very helpful and will give a lot of false hits for searches.

    Hi,

    Unfortunately is a logfile, not to get. Putty says: curl: (6) Could not resolve host: sprunge.us
    Regardless whether wireless or wired

    In Kodi, the logging is activated.

    Supplement to the previous contribution.

    All clients have access to each other. All clients have access to the internet.
    My router is a ubiquiti edge Max, the accesspoint is a Linksys Lapac 1200, switch is a Netgear GS108PEv3.
    No matter if DHC or with fixed IP, whether Wired or wireless, whether libreelec or OSMC I get with the raspberry pi 3 no Internet or no access on the internet loadable add-ons.

    The problem is limited
    Libreelec as well as OSMc failed at the name resolution. The DNS servers work correctly, it is the same server as entered in the router. While the name resolution works on all other clients in the same subnet, there are problems in libreelec and OSMC. A ping on an IP works, a ping on the name "bad address 'google.com'

    On other clients tracert name or traceroute name works fine.

    I just read your post now. No policy prevents traffic

    Volumio on the raspberry can do it.

    I don `t understand it. All clients can resolve with the DNS servern and the domain names. Only libreelec necessarily requires 8.8.8.8 or 8.8.4.4.

    Can anyone explain to me?

    Thanks for the solution, in Libreelec the Google DNS are registered and it now works

    • Official Post

    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.

    Quote from chewitt


    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?

    Edited once, last by x_pedro_x (January 15, 2017 at 7:55 PM).

    • Official Post

    Basically.. no idea. Once 7.95.1 beta is available I'm interested in results using that build because a) there are numerous network package bumps present that could potentially change things, and b) we stopped developing on 7.0 some time ago.

    I had the same issue today

    The issue was my centos 7 where I did the MASQUERADE

    it was not working with iptables and I did it with firewall-cmd

    firewall-cmd --direct --add-rule ipv4 nat POSTROUTING 0 -o external_interface -j MASQUERADE
    firewall-cmd --direct --add-rule ipv4 filter FORWARD 0 -i internal_interface -o external_interface -j ACCEPT
    firewall-cmd --direct --add-rule ipv4 filter FORWARD 0 -i external_interface -o internal_interface -m state --state RELATED,ESTABLISHED -j ACCEPT

    hope this help