Network Connectivity but no Internet

I have been searching the threads on connectivity and have yet to see my problem listed.

I started a fresh install of OSMC on my Raspberry pi 1 installing the latest release. I followed the directions for WIFI and password.\

Install goes fine. Able to see the device on my network. Able to ping the RPi. Try to add a repository and I am told that the RPi cannot connect to the server.

SSH into the RPi. Able to ping my WAP private IP and my WAN public IP.\

I am not able to ping 8.8.8.8 nor (and given no internet connectivity to IPs, no name resolution either).

ifconfig shows an IP address under wlan0.

I am using a TP-Link 725

There are no pcutils in OSMC and I cannot apt-get (no internet)

Any help would be appreciated.

What do you get if (from the Pi command line) you try this:

osmc@kaled:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.2.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
osmc@kaled:~$

If you see your router as the gateway for 0.0.0.0 then the Pi has the correct route, so look at your routers configuration.

Here is the route -n

Assuming that your router is 192.168.0.1, then your route table looks OK. Have a look on your router.

The gateway is 192.168.0.1. Routing should be OK as there are several other devices on that network segment that can reach the internet OK.

So networking is ok to the router. Other devices can route to the internet. The RPi can ping inside the local LAN, and the external interface of the router (ISP provided lease).

I do not have any static routes set up, but may try that to see if that works.

Could it be a problem with sockets in OSMC?

EDIT: It was pointed out to me that this won’t work for you, since you can’t connect to the Internet, you won’t be able to install traceroute.

Is if possible to try hardwired, just to rule out the wireless?

[Original useless suggestion below]

Try a traceroute to see where it’s failing. You will have to install traceroute if you haven’t already:

osmc@kaled:~$ sudo apt-get install traceroute

And then do a traceroute to 8.8.8.8

osmc@kaled:~$ traceroute -n 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 192.168.2.1 0.644 ms 0.297 ms 0.427 ms
2 192.168.1.1 0.477 ms 0.545 ms 0.475 ms
3 100.104.68.105 1.569 ms 1.758 ms 1.637 ms
4 69.35.203.237 605.209 ms 701.688 ms 774.242 ms
5 69.35.204.58 784.573 ms 864.487 ms 914.925 ms
6 63.156.154.41 914.818 ms 913.894 ms 925.063 ms
7 67.14.24.93 940.078 ms 939.947 ms 939.811 ms
8 67.134.166.226 960.639 ms 960.065 ms 961.546 ms
9 216.239.42.249 939.075 ms 216.239.42.247 696.156 ms 216.239.42.249 681.819 ms
10 209.85.241.175 661.665 ms 72.14.235.205 766.952 ms 216.239.42.245 720.417 ms
11 8.8.8.8 636.747 ms 636.476 ms 636.140 ms

Nope @bmillham - not a “useless suggestion”, but perhaps in need of slight modification :slight_smile:

IIRC, there’s a “--download-only” option to “apt-get”. @drewsmeaton, if you have access to another Pi which is connecting correctly (or any other Debian based box and know the magic runes to cast to download packages from different repositories for different architectures - let’s not go there if you don’t :slight_smile:), perhaps you could download the package on that other Pi, copy it on physical media (good old SneakerNet :slight_smile:) to the problematic Pi, and install it from that package file?

traceroute would definitely be a good start in figuring out what isn’t going on here …

BTW, just checking the obvious - you have checked that you’ve not got a duplicate IP address on your LAN, haven’t you? If not, make a note of the Pi’s address, shut it down, try "ping"ing that address from another device. If you get a response, with your Pi powered down, that’ll be your problem …

OK, I just checked with Sam, and my original suggestion was just a little off. traceroute is installed, but it’s part of busybox, so to do a traceroute, do this:

osmc@kaled:~$ busybox traceroute -n 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 192.168.2.1 0.445 ms 7.713 ms 0.307 ms
2 192.168.1.1 0.564 ms 0.433 ms 0.420 ms
3 100.104.68.105 1.298 ms 0.927 ms 1.032 ms
4 69.35.203.237 809.416 ms 719.084 ms 683.337 ms
5 69.35.204.58 620.525 ms 758.409 ms 1580.904 ms
6 63.156.154.41 706.009 ms 632.052 ms 641.253 ms
7 67.14.24.93 789.074 ms 629.451 ms 709.623 ms
8 67.134.166.226 769.848 ms 753.347 ms 755.759 ms
9 216.239.42.247 660.025 ms 652.783 ms *
10 72.14.235.205 950.961 ms 216.239.42.235 850.975 ms 209.85.243.251 712.840 ms
11 8.8.8.8 695.420 ms 822.919 ms *
osmc@kaled:~$

So I was able to install traceroute directly from my Pi.

I was also able to traceroute but with some timeouts.

It looks like a timing issue. Is there a timeout setting on the Pi I can adjust?

Interesting, you are getting name resolution. I don’t think the timeouts are an issue, usually that means that that particular router won’t directly respond to a ping.

I don’t see any problems, and the fact that you were able to do the apt-get (which it ends up you didn’t need to do) tells me that your problem seems to have cleared up.

So I played around on the Pi last nigh with OSMC. Cant connect to a repository. Was able to go to the update and update OSMC and download and install the update. So there is connectivity with OSMC, but not with Kodi.

I can traceroute, but I cannot ping.

DNS is working as when I ping google.com the IP is shown.

What repository are you trying to get? I noticed in your first post:

I have tried fusion and srp.

We have removed your thread from public viewing because it mentions a pirate addon. We cannot provide support for these. To get a better idea of our piracy policy, please see this link here FAQ - OSMC Forums

If you can connect to official Kodi repos and are only having issues with these, the issue is not with Kodi or OSMC.