5 replies to this topic

[jack burton]

Hi all,

i just bouht an xtrend et4000 decoder and flashed it with openpli 4 image.

I have a strange problem with network connection everytime i turn on my decoder. This is what happens:

 - i switch on the et4000 and the yellow led on the ethernet port on the back of the decoder is on, but the activity led is always off. On my router i see the led on the corresponding port blink with an  inteval of 2 seconds periodically.

 - if i perform a network test, i got the result that the network is on but the interface is not connected to lan and the ip address in unavailable.

 - even if i set an ip address manually i have the same result

 

the only thing i can do to get network working is disconnect and reconnet lan cable or restart the network from control panel menu, or restart the decoder via menu option or pushing the hardware button on the device.

 

I think this is a "level-2" issue.

It seems that the interface can't detect the network is connected until it is forced to see a new ethernet transation on its port.

 

Any ideas ?

 

thank you

 

P.s. : i tried also with another cable, another router, but nothing changed

 

 

[Chibby]

hello,

 

did you try network connection with the orginal firmware?

 

could it be a hardware issue?

[jack burton]

hello,

 

did you try network connection with the orginal firmware?

 

could it be a hardware issue?

Hi,

i tried 3 different firmwares: openpli, xtrend-alliance and clarke-tech xtrend-support v6 image, and with same results.

 

May be it could be an harware issue, but it's very strange that the restart of the network on the system setting menu can make it work.

[betacentauri]

It seems to be an et4000 related problem. I heard from several users that they have this problem. But not all et4000 have this problem. Perhaps you can add a script in runlevel 3 which restarts network automatically. Something like
ifdown eth0
ifup eth0

[Erik Slagter]

Yes, look like a PHY problem. I don't think there is a good solution for that other than what betacentauri says.

[jack burton]

It seems to be an et4000 related problem. I heard from several users that they have this problem. But not all et4000 have this problem. Perhaps you can add a script in runlevel 3 which restarts network automatically. Something like
ifdown eth0
ifup eth0

 

 

Yes, look like a PHY problem. I don't think there is a good solution for that other than what betacentauri says.

 

This is exactly what i was thinking.

this is probably an error in the pcb layout whit the mac controller, or the chip is bugged.

I think i'll open the chassis to check the revision of the pcb and compare it with other owners of et4000.

 

In the meantime i'll try to make a script that ping the network and restart the interface if it's down.

 

Thank you all, cu for updates