Raspberry Pi Forums

So the issue I'm having is the ethernet doesn't work all the time on the RPI4. It'll sometimes wake up for half a day and then you restart it and it's gone for a week and then just wakes up randomly, truly bizarre.

I've tried the PIs on Raspbian Buster, DietPi and WTWare (This is the best OS for Thin Client support for me) and they all don't want to know.

This issue is over 3 RPI4s now so there's got to be a problem with what I'm doing somewhere. I'm using a USB C charger that came with a HP laptop I have and a normal ethernet cable straight into the pi. The cable works on a LG POE phone and the HP laptop going throught a USB C converter.

Has anyone else had this issue? Or any ideas on what I can try?

EDIT: I have also used a raspberry pi psu and different ethernet cables

1) use an official RPI PSU
2) try another Ethernet cables

RaTTuS wrote: ↑

Tue Oct 01, 2019 7:27 am

1) use an official RPI PSU
2) try another Ethernet cables

Sorry I forgot to add that I've done both of those already.

Have you actually tested the cables with a LAN cable tester to prove all 8 cores are connected reliably ?

Try testing you pi4's using a different network switch just to prove its not a switch compatibility or switch setting problem.

Ah, cable, do you have a separate hub connected to the cable modem? Or does the cable modem have a built-in hub?



When you connect the Pi to your hub and power it on, does the hub port light come on?

If you like downloading reddit videos its very easy by using this.

We also need the answer to Gary's question. Open a Terminal and type:



ifconfig



Then post us what the terminal replies.



You should see something like this:

eth0 Link encap:Ethernet HWaddr A4:BA:DB:0E:4B:5A
inet addr:192.168.1.15 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::a6ba:dbff:fe0e:4b5a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:511774773 errors:1 dropped:0 overruns:0 frame:1
TX packets:62692741 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:94801773297 (88.2 GiB) TX bytes:56854688675 (52.9 GiB)
Interrupt:82 Memory:da000000-da012800


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:16436 Metric:1
RX packets:12584915 errors:0 dropped:0 overruns:0 frame:0
TX packets:12584915 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8041559088 (7.4 GiB) TX bytes:8041559088 (7.4 GiB)

pcmanbob wrote: ↑

Tue Oct 01, 2019 9:32 am

Have you actually tested the cables with a LAN cable tester to prove all 8 cores are connected reliably ?

Try testing you pi4's using a different network switch just to prove its not a switch compatibility or switch setting problem.

So I took the PI home with me yesterday to try it in a different switch. Worked instantly and it's just a basic TP-link switch whereas the switches at work are Cisco SG300-52's.

Is there a known setting that i need to turn on to allow it to work with the pi?

Hello,

Did you read this ?
As said above, the cable must have 8 cores connected.

BR
Pulsar33

unbannable wrote: ↑

Wed Oct 02, 2019 8:00 am

whereas the switches at work are Cisco SG300-52's.

If you are trying to connect to a switch in a work environment then I suggest you talk to the network admin, security is often much stricter in a work environment So that's what may be preventing the pi from connecting.