chfakht
Posts: 30
Joined: Sat Jul 04, 2015 4:38 pm

How to connect raspberry internally

Wed Jul 08, 2015 3:23 pm

Hi all , i think that internet connection using raspberry via ssh is not working ... it's fails when i want to install any package
for example : sudo apt-get update

Err http://mirrordirector.raspbian.org wheezy Release.gpg
Could not connect to mirrordirector.raspbian.org:80 (5.153.225.207). - connect (113: No route to host)
Err http://raspberrypi.collabora.com wheezy Release.gpg
Could not connect to raspberrypi.collabora.com:80 (93.93.128.223). - connect (113: No route to host)
Ign http://mirrordirector.raspbian.org wheezy Release
Ign http://raspberrypi.collabora.com wheezy Release
Err http://raspberrypi.collabora.com wheezy/rpi armhf Packages
Unable to connect to raspberrypi.collabora.com:http:
Err http://raspberrypi.collabora.com wheezy/rpi Translation-en
Unable to connect to raspberrypi.collabora.com:http:
Err http://mirrordirector.raspbian.org wheezy/main armhf Packages
Unable to connect to mirrordirector.raspbian.org:http:
Err http://mirrordirector.raspbian.org wheezy/contrib armhf Packages
Unable to connect to mirrordirector.raspbian.org:http:
Err http://mirrordirector.raspbian.org wheezy/non-free armhf Packages
Unable to connect to mirrordirector.raspbian.org:http:
Err http://mirrordirector.raspbian.org wheezy/rpi armhf Packages
Unable to connect to mirrordirector.raspbian.org:http:
Err http://mirrordirector.raspbian.org wheezy/contrib Translation-en
Unable to connect to mirrordirector.raspbian.org:http:
Err http://mirrordirector.raspbian.org wheezy/main Translation-en
Unable to connect to mirrordirector.raspbian.org:http:
Err http://mirrordirector.raspbian.org wheezy/non-free Translation-en
Unable to connect to mirrordirector.raspbian.org:http:
Err http://mirrordirector.raspbian.org wheezy/rpi Translation-en
Unable to connect to mirrordirector.raspbian.org:http:
Err http://archive.raspberrypi.org wheezy Release.gpg
Could not connect to archive.raspberrypi.org:80 (93.93.128.230). - connect (113: No route to host) [IP: 93.93.128.230 80]
Ign http://archive.raspberrypi.org wheezy Release
Err http://archive.raspberrypi.org wheezy/main armhf Packages
Unable to connect to archive.raspberrypi.org:http: [IP: 93.93.128.230 80]
Err http://archive.raspberrypi.org wheezy/main Translation-en
Unable to connect to archive.raspberrypi.org:http: [IP: 93.93.128.230 80]
W: Failed to fetch http://mirrordirector.raspbian.org/rasp ... elease.gpg Could not connect to mirrordirector.raspbian.org:80 (5.153.225.207). - connect (113: No route to host)

W: Failed to fetch http://raspberrypi.collabora.com/dists/ ... elease.gpg Could not connect to raspberrypi.collabora.com:80 (93.93.128.223). - connect (113: No route to host)

W: Failed to fetch http://archive.raspberrypi.org/debian/d ... elease.gpg Could not connect to archive.raspberrypi.org:80 (93.93.128.230). - connect (113: No route to host) [IP: 93.93.128.230 80]

W: Failed to fetch http://mirrordirector.raspbian.org/rasp ... f/Packages Unable to connect to mirrordirector.raspbian.org:http:

W: Failed to fetch http://mirrordirector.raspbian.org/rasp ... f/Packages Unable to connect to mirrordirector.raspbian.org:http:

W: Failed to fetch http://mirrordirector.raspbian.org/rasp ... f/Packages Unable to connect to mirrordirector.raspbian.org:http:

W: Failed to fetch http://mirrordirector.raspbian.org/rasp ... f/Packages Unable to connect to mirrordirector.raspbian.org:http:

W: Failed to fetch http://mirrordirector.raspbian.org/rasp ... slation-en Unable to connect to mirrordirector.raspbian.org:http:

W: Failed to fetch http://mirrordirector.raspbian.org/rasp ... slation-en Unable to connect to mirrordirector.raspbian.org:http:

W: Failed to fetch http://mirrordirector.raspbian.org/rasp ... slation-en Unable to connect to mirrordirector.raspbian.org:http:

W: Failed to fetch http://mirrordirector.raspbian.org/rasp ... slation-en Unable to connect to mirrordirector.raspbian.org:http:

W: Failed to fetch http://raspberrypi.collabora.com/dists/ ... f/Packages Unable to connect to raspberrypi.collabora.com:http:

W: Failed to fetch http://raspberrypi.collabora.com/dists/ ... slation-en Unable to connect to raspberrypi.collabora.com:http:

W: Failed to fetch http://archive.raspberrypi.org/debian/d ... f/Packages Unable to connect to archive.raspberrypi.org:http: [IP: 93.93.128.230 80]

W: Failed to fetch http://archive.raspberrypi.org/debian/d ... slation-en Unable to connect to archive.raspberrypi.org:http: [IP: 93.93.128.230 80]

if i try to ping google.com
From raspberrypi.local (10.42.1.12) icmp_seq=1 Destination Host Unreachable
From raspberrypi.local (10.42.1.12) icmp_seq=2 Destination Host Unreachable

plz help thanks :) i'm using pi 2 with raspbian whezzy

fruitoftheloom
Posts: 23914
Joined: Tue Mar 25, 2014 12:40 pm
Location: Delightful Dorset

Re: How to connect raspberry internally

Wed Jul 08, 2015 3:33 pm

Yes your RPi is not getting an Internet Connection.

If that is all the information how are we supposed to help, what is you Network setup and does SSH work ?
Rather than negativity think outside the box !
RPi 4B 4GB (SSD Boot) RaspiOS64 ARM64
Asus ChromeBox 3 Celeron is my other computer...

myoung008
Posts: 55
Joined: Mon Mar 18, 2013 9:56 pm

Re: How to connect raspberry internally

Wed Jul 08, 2015 4:58 pm

You really haven't given enough information, but as a wild guess, try this:

Code: Select all

sudo route add default gw 10.42.1.1
echo nameserver 10.42.1.1 | sudo tee -a /etc/resolv.conf
If this fixes it, it will only work until the next reboot.

User avatar
rpdom
Posts: 17450
Joined: Sun May 06, 2012 5:17 am
Location: Chelmsford, Essex, UK

Re: How to connect raspberry internally

Wed Jul 08, 2015 5:01 pm

Minimal information there, but we can deduce that you have working DNS, but something is up with your gateway (router) configuration.

How about telling us how your Pi is physically connected to the internet, then something about the software configuration. The outputs from the following commands may help:

Code: Select all

ip route
ifconfig -a
cat /etc/network/interfaces
cat /etc/resolv.conf

User avatar
gamaxwell
Posts: 1
Joined: Fri Jul 10, 2015 8:08 pm
Location: Champaign, IL

Re: How to connect raspberry internally

Fri Jul 10, 2015 8:17 pm

I'm having the same issue too. Any help is much appreciated.

pi@raspberrypi ~ $ ping google.com
PING google.com (173.194.46.98) 56(84) bytes of data.
64 bytes from ord08s13-in-f2.1e100.net (173.194.46.98): icmp_req=1 ttl=52 time=23.2 ms
64 bytes from ord08s13-in-f2.1e100.net (173.194.46.98): icmp_req=2 ttl=52 time=22.0 ms
64 bytes from ord08s13-in-f2.1e100.net (173.194.46.98): icmp_req=3 ttl=52 time=23.5 ms

pi@raspberrypi ~ $ ip route
default via 192.168.1.1 dev wlan0 metric 303
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.3 metric 303
pi@raspberrypi ~ $ ifconfig -a
eth0 Link encap:Ethernet HWaddr b8:27:eb:3a:2a:1b
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:40 errors:0 dropped:0 overruns:0 frame:0
TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3696 (3.6 KiB) TX bytes:3696 (3.6 KiB)

wlan0 Link encap:Ethernet HWaddr e8:4e:06:2b:78:c8
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6338 errors:0 dropped:666 overruns:0 frame:0
TX packets:3614 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6638813 (6.3 MiB) TX bytes:367944 (359.3 KiB)

pi@raspberrypi ~ $ cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
allow-hotplug eth0
iface eth0 inet manual

auto wlan0
allow-hotplug wlan0
iface wlan0 inet manual
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

auto wlan1
allow-hotplug wlan1
iface wlan1 inet manual
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

pi@raspberrypi ~ $ cat /etc/resolv.conf
# Generated by resolvconf
nameserver 192.168.1.1
pi@raspberrypi ~ $ A

myoung008
Posts: 55
Joined: Mon Mar 18, 2013 9:56 pm

Re: How to connect raspberry internally

Fri Jul 10, 2015 8:39 pm

@gamaxwell: Your problem is a little different, as you can get to the outside world in general. In your case I'd wait a little while while and try again. Failing that, you might want to post a copy of the actual errors you are getting as well. It may be slightly different than OP and give a better indication of what's going on.

Return to “Troubleshooting”