1

Proof of the error

When I try ping 8.8.8.8 through SSH I get this:

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2007ms

What I have tried

My /etc/resolv.conf looks like this:

nameserver 8.8.8.8
nameserver 8.8.4.4

My /etc/network/interfaces looks like this:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static

address 31.51.249.21
netmask 255.255.255.0
gateway 31.51.249.18
dns-nameservers 8.8.8.8 8.8.4.4

My network

When I type the command ifconfig -a:

eth0 Link encap:Ethernet HWaddr b8:15:qd:32:a5:6c
inet addr:31.51.249.21 Bcast:31.51.249.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:330247 errors:0 dropped:46340 overruns:0 frame:0
TX packets:63355 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:47649638 (45.4 MiB) TX bytes:14773496 (14.0 MiB)

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:1309 errors:0 dropped:0 overruns:0 frame:0
TX packets:1309 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:146798 (143.3 KiB) TX bytes:146798 (143.3 KiB)

When I type the command route -n:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         31.51.249.18    0.0.0.0         UG    0      0        0 eth0
31.51.249.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0

Please help me with what might be the cause of this. It is preventing me from being able to install anything onto my raspberry! I would be so grateful for any help on why this might be happening!


answer to framp:

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination 

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination 

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination 
  • 1) Are you sure .18 is the gateway? Usually .1 is used as the gateway in a subnet. 2) Do you have an active firewall? What's the result of sudo iptables -L -vn – framp Jan 10 '15 at 22:29
  • I will answer in an edit ^^ – maxisme Jan 10 '15 at 22:40
  • Your Pi is connected directly to the internet without an intervening router? What does ping 31.5.249.18 return? – TomG Jan 10 '15 at 23:15
  • And in answer to part one - Yes you can see my output of route -n which shows the gateway – maxisme Jan 10 '15 at 23:29
  • 64 bytes from 31.51.249.18: icmp_req=1 ttl=64 time=1.30 ms ... aka it works – maxisme Jan 10 '15 at 23:31
1

It looks like you're connected to a router at 192.168.1.254.

Try

  address 192.168.1.xxx  (choose an address that's not in use)
  netmask 255.255.255.0
  gateway 192.168.1.254

Or probably better, use dhcp to assign an IP by changing "static" to "dhcp" on the "iface eth0 inet" line, and delete the address, netmask, and gateway directives.

  • 1
    I have now lost my connection through ssh and I am 200 miles away from the pi... Thanks for your help though! I will try when I get home in a month or so – maxisme Jan 11 '15 at 13:15
  • Ouch, so sorry! Might have been a bit more conservative in how to test that had we known. I'm used to mine being in the next room if I have to reset or make an emergency change. – TomG Jan 12 '15 at 1:32
  • No worries my fault! I just changed the gateway to what you said. As the gateway before was the static ip I had set on my hub! I am not quite sure why that has caused everything to mess up, as the port forwarding on my hub was linked to the RP device and its ip address (as can be seen above)? I don't see why the gateway being the static one is necessary? – maxisme Jan 12 '15 at 17:52
  • I have remote connected to a computer on my network at home now!! So I can ssh locally but for some reason I cannot connect to it!! My hub says the pi is connected and that it has the ip 31.51.249.21 but it is not connecting!!! I am so confused!! Why would have the gateway changed that?! – maxisme Jan 12 '15 at 18:40
  • This sucks... It is impossible isn't it!! As it is not a static ip anymore? – maxisme Jan 12 '15 at 18:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.