Disconnecting from eth0 without getting IP again until reboot

Help & Support Operating System
1

Hello:

I’ve been having a very strange issue for 2-3 days with a TV-Box with CoreELEC (S905X3; CE 21.1.1-ng).

When CoreELEC starts, it connects to the wired network (eth0) without any problem, with the “fixed” IP that I have assigned to it (192.168.1.40).
So far so good.

However, after some hours, it stops being connected.
If I do:
ifconfig

I see the interface
eth0

apparently active, but the device does NOT have an IP, and the only way it “gets” an IP again is by restarting the TV-Box. I restart it, and it gets an IP again through eth0 (192.168.1.40), at a certain point it loses that IP (I don’t know why, I don’t know if it’s due to a specific problem), and the only way I have to get an IP (eth0) again is by restarting the TV-Box.
And the cycle starts again.

Before this strange behavior, when it disconnected from the network for whatever reason (router crash, etc.), it would get an IP again without any problem. But not now; I don’t know if when it loses the IP via eth0 it doesn’t even try to get it again, or if it tries but doesn’t succeed until it restarts.

I DID NOT change anything in the software; I DID NOT change anything in the device’s configuration (in the last few days, I mean), I didn’t change anything in the router, but suddenly this happens.

Do you have any idea what the problem could be?

When the device “loses” eth0 IP, it still has an wlan0 IP (at this moment, 192.168.1.63), so I can connect to TV-Box via ssh.
Any useful command to “force” it to obtain IP with eth0 again without restarting?

For me the eth0 interface is very important because I connect this device (“server”) throgh Wireguard using eth0 IP. So, when IP 192.168.1.40 is off, WG “clients” can NOT connect to the “server”.

A bit more info from my side:
When I try this using Android, disconnecting ethernet cable and connecting it again, it does NOT get ethernet IP (same thing that with CoreELEC).

Perhaps I was wrong and it always was in this way before.

In CoreELEC, if I try:

# connmanctl disable ethernet

Disable ethernet

# connmanctl enable ethernet

Error ethernet: Device or resource busy

it never connects to ethernet until restart.

1 Like
3

Try

ifconfig eth0 down
ifconfig eth0 up
4

Test:

  1. Ethernet working OK
  2. I disconnect physical ethernet cable
  3. I connect again physical ethernet cable (NO ethernet connection)

CoreElec:~ # ifconfig eth0 down
CoreElec:~ # ifconfig eth0 up
ifconfig: ioctl 0x8914 failed: Device or resource busy

5

Try using DHCP and asign IP on router.

6

I did it. Same result.

7

I always use DHCP but you mean make a dhcp reservation using the mac address which I have done. I’ve played around with cast lists etc and so far it is staying connected.

8

I had the same problem after upgrading my Odroid-N2 (S922x) to 21.1.
Had to downgrade back to 20.5 version where the problem doesn’t exists.
My IP is assigned by DHCP and after some time of inactivity, the connection dropped and couldn’t be restored without reboot. At first, I suspected sleep mode, but even with sleep mode disabled, the connection was interrupted. Unfortunately I haven’t looked into it more deeply and I don’t have any logs. I can only confirm that you are not the only one who has encountered this.

9

Just to confirm. So far still no further disconnections since locking down IP address.

10

Hi All, any updates with this ‘falling-off’ internet issue? I have the same problem with 21.1 as described above. I’m using TX3mini (ng 21.1 image) and VontarX4 (ne 21.1) - all have the same internet problem! It happens with wire (!) internet connection unexpectedly, as I see, fixed ip address does not help. The older ne/ng images (20.5) work fine. This bug has been detected since the announce of 21.1 images.