Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
Raspberry Pi Wishlist
Actions
Forum Thread Details
  • State Suggested Answer
  • Replies 17 replies
  • Answers 3 answers
  • Subscribers 676 subscribers
  • Views 5526 views
  • Users 0 members are here
Related

Requesting help with Eth0 issue on Raspbian Jessie

philbert213

Good evening,

 

This has been an issue that has bothered me for quite a while now. I'm trying to set up my raspberry pi 3 to work via ethernet at my workplace, but it does not seem to work. However, on any windows machine that I have, I get issued an IP address and connect to the internet just fine. The other interesting fact is that if I connect to my work internet via wifi, it has no issue whatsoever. The problem with that is that I am not always within range of using the access point.

 

I tried to be as detailed as possible in getting all the information needed in order to help me resolve my issue:

 

cat /etc/issue

 

Raspbian GNU/Linux 8 \n \l

 

ifconfig

 

eth0      Link encap:Ethernet  HWaddr b8:27:eb:7c:21:2b 

          inet addr:192.168.5.147  Bcast:192.168.5.255  Mask:255.255.255.0

          inet6 addr: fe80::5456:bf59:aaa2:1ce6/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:696 errors:0 dropped:39 overruns:0 frame:0

          TX packets:70 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:56494 (55.1 KiB)  TX bytes:7748 (7.5 KiB)

 

 

lo        Link encap:Local Loopback 

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:65536  Metric:1

          RX packets:216 errors:0 dropped:0 overruns:0 frame:0

          TX packets:216 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1

          RX bytes:18060 (17.6 KiB)  TX bytes:18060 (17.6 KiB)

 

iwconfig

 

wlan0     IEEE 802.11bgn  ESSID:off/any 

          Mode:Managed  Access Point: Not-Associated  

          Retry short limit:7   RTS thr:off   Fragment thr:off

          Power Management:on

         

lo        no wireless extensions.

 

 

eth0      no wireless extensions.

 

route -n

 

Kernel IP routing table

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

0.0.0.0         192.168.5.1     0.0.0.0         UG    202    0        0 eth0

192.168.5.0     0.0.0.0         255.255.255.0   U     202    0        0 eth0

 

/etc/network/interfaces

 

auto lo

iface lo inet loopback

 

 

iface eth0 inet manual

 

 

allow-hotplug wlan0

iface wlan0 inet manual

    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

 

 

allow-hotplug wlan1

iface wlan1 inet manual

    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

 

/etc/resolv.conf

 

nameserver 192.168.5.2

 

 

 

I will be forever thankful if anyone can guide me in the right direction. Thanks!

Parents
  • 0

    As well as all the useful information from Rachael and Clem above, it would also be worthwhile checking using the Ethernet connection on your home router. Some work networks will have special policies in place that will not provide LAN access to any device that is not provisioned/permitted by the IT team. Your guest wifi at work may have different policy. If it works on your home router with a wired connection then that could be the case.

Reply
  • 0

    As well as all the useful information from Rachael and Clem above, it would also be worthwhile checking using the Ethernet connection on your home router. Some work networks will have special policies in place that will not provide LAN access to any device that is not provisioned/permitted by the IT team. Your guest wifi at work may have different policy. If it works on your home router with a wired connection then that could be the case.

Children
  • 0 in reply to shabaz

    Ah yes that's a very good point. A lot of companies lock network ports to the MAC address of the device they intend to connect to them! I'd forgotten that!

  • 0 in reply to shabaz

    This was something that I thought would be the case as well but I have my doubts. I've noticed that in all my computers that run Ubuntu/Debian, I can't use the Ethernet connection either. However, some of those computers are dual boot with windows and when that is the operating system that I use, it allows me to connect to the internet. I suppose it could be an unrelated issue altogether though. But I assume then that such policies would restrict an Xbox One access to the internet (which I also have connected by Ethernet at my work), yet I have no issues with internet access. I'm not sure if that is relevant though haha.

  • 0 in reply to philbert213

    What is the default gateway set as on your Ubuntu/Debian/Pi. That would explain the lack of internet if the default gateway wasn't set up. Alternatively does your company have a proxy for access to the internet which gets set automatically by something in the windows side of the networking if they are using Windows servers?

     

    Best Regards,


    Rachael

  • 0 in reply to rachaelp

    The pi had the default gateway set to this according to:

     

    ip route | grep default

    default via 192.168.5.1 dev eth0  metric 202

     

    Comparing to the windows machine, it seems to match.

     

    As far as proxies go, I was told that any device that I plug into should just work. The gentleman that set up the internet was even baffled as to why the same computer that is able to connect on Windows can't do so under Linux. As far as I understand, I don't need to set up for a particular proxy. I believe they are using Windows servers.

  • 0 in reply to philbert213

    So if you reboot your Windows PC into Ubuntu/Debian can you bing in both directions between it and the Pi?

  • 0 in reply to rachaelp

    Not possible. Ubuntu/Debian machines won't even detect a connection via Ethernet. It gives me:

     

    connect: Network is unreachable

  • 0 in reply to philbert213

    Have you got access to two Pi's? It seems like your eth0 is configured correctly and on the network, I wonder if you can't ping your windows PC because it's firewall is blocking it?

     

    Does your Pi access the internet correctly when using the eth0 connection on your home network? If so then to me it sounds like there is something else going on on the corporate network that you aren't aware of which is giving issues. The fact that your Ubuntu/Debian PC's can't even connect to the network is an indication that something else is going on. When you do ifconfig on these what is the IP address? Does it come back with an address in the 169 range?

  • 0 in reply to rachaelp

    I am in possession of more than one pi and I managed to take one at home for the moment. The same pi that I've been trying to connect at work functions properly on my home network on both eth0 and wlan0. I don't think this matters, but at home I get an IP address with a xxx.xxx.1.xxx rather than xxx.xxx.5.xxx from work. As far as the linux PCs go, when I do connect by Wifi at work, I do get a address within the range you specified. However, the linux PCs do not even seem to recognize that there is an Ethernet cable connected when I attempt that.

     

    Maybe there is something about the work network itself that isn't playing nice with the Pi and Linux distros. Now that I think of it, my PS4 also doesn't establish a connection via Ethernet unlike my Xbox one. It's quite bizarre and I'm not sure what to make of it.