I wanted to post this thread in ‘Single Board Computers’ section but I am not yet allowed to post a thread over there.
I have 3 AmLogic boxes including Odroid N2+ which I have tried running on various flavors of LibreELEC, Android and CoreELEC for past several years. However when I started using CoreElec 8.2.5 on N2+ via spi and SD card, I noticed that N2+ cannot get an IP address from my router. My N2+ is connected via ethernet cable to a LAN switch with 3 other device connected to same switch. I do not have a WiFi dongle. I have taken following steps to address this issue:
Assign static IP addres in the router using MAC address.
Assign a dynamic IP address from router.
Changed ethernet cables.
Connected N2+ directly to the router.
Tested Android installed on emmc which had no trouble in obtaining IP address.
Flashed CE 19.x and 20.x versions on SD card and booted on N2+.
No matter what I did, my N2+ cannot obtain an IP address in about 3 out of 5 starts. Other 2 AmLogic devices running CoreELEC are not having any issues obtaining IP address on the same network. However after CoreElec is booted, I can disable the ethernet and re-enable it in CoreELEC settings and half of the time it can get an IP address.
At this point I am certain is this is either a problem with N2+ unit or with CoreELEC as I ruled out networking conflicts.
So has anyone else encountered similar issues obtaining IP address by CoreELEC running on N2+ ? I have attached screenshot below.
Thanks.
Have you tried “Wait for network before Kodi starts” => 1X seconds ?
Btw, does it behave differently with “255.255.255.0” subnet mask, or you must use present one?
I encountered issues with getting IP addresses for my Homeassistant running on N2. It seems that its some sort of hardware issue between my N2 and the OPNsense router I run. What I did in the end was assigned static addresses and static ARP assignment. The N2 Homeassistant instance carried on working with its own internal static IP address even when it was abscent from the router IP lists.
I was using ‘Wait for Network’ setting of 10 seconds. However after reading your message, I increased the wait to 20 seconds and would see how it’d effect the situation.
The screen shot I posted with ‘255.255.0.0’ subnet mask is when ethernet port in CoreELEC was configured to obtain IP address from dhcp server. I did not specify that subnet mask or those DNS servers in settings.
Don’t know how to solve your problem, since never had it. I had different problem with my N2 & AM6B+. I can only tell you how I set my network, since I found out that there are sometimes ethernet incompatibilities, especially with S922 SoC on my N2 & AM6B+ boxes, between them and some routers.
On my routers I always set DHCP IP address pool between 100-200, and assign fixed IP addresses on my devices between 10-99; I do not set them using MAC addresses. My routers IP I always set to 192.168.1.1. My N2 is then set like this:
IP address: 192.168.1.10
Subnet mask: 255.255.255.0
Gateway: 192.168.1.1
Primary / Secondary DNS: 1.1.1.1 / 8.8.8.8
Always Ethernet for stability.
The ip you receive is an apipa (automatically assigned when no ip can be acquired through dhcp).
Only thing I can say is check your router config or maybe something is wrong with your onboard NIC.
I switched my router with another brand which acts as hdcp server but did not notice improvement in getting IP address under CoreElec.
I tried assigning fixed IP address to N2+ outside the hdcp assigned range but then N2+ never connected to the network under CoreElec.
I do not have a WiFi dongle for my N2+ but it would be next step. I may get another N2+ just for testing purpose but I am bit leery to have similar issues with another unit.
Good ideea.
It´s no CE rated issue.
I´m using N2 and N2+ a long time and still using the very old CE Version 19.5 in my living room, because it´s very, very stable all the time.
I did not see any stable release for 22.x so I stuck with CE version 21.2. Even with CE 21.2 , the network behavior is exactly he sames as it was with CE 8.2.5.
But I do not think its a CoreElec only issue. Its probably a malfunctioning or more likely mal-configured ethernet chipset on the N2+ which is causing the issue.
I might buy another N2+ unit but then couple of other people in this thread have also mentioned having networking issues with their S922x based devices. It seems the onboard NIC on N2+ is expecting a certain king of ping to start communicating with hdcp server, and that’s why disabling & restarting ethernet connection in kodi sometimes fixes this issue.
The android OS from HardKernel always gets an IP address probably because they know how to make onboard NIC work properly.
I have a different issue with NIC on my N2; set to fixed IP addresses it always gets connected, but only one time in ten after reboot/power-on it connects with full duplex 1 gig speed to my provider’s router. I have to force full duplex via autostart.sh in all CE versions that I used.
And yes, in several Android versions that I use it always connects with full speed without any intervention.
I´m using N2 and N2+, some other amlogic boxes(S905/s912) and a lot more devices with ethernet connection no issues all the time.
But, all devices are connected to managed switches, not directly to the router I got from my ISP.
Some provider’s routers could be the cause of the issues.
Yes, I’m aware of that, and my two last provider routers are on the problematic list.
Interesting that my router also does not like my other S922x box, AM6B+ with CE, but on it I gave up ethernet connection and only use very good and dependable WiFi connection.
AM6B+ also has none problems with ethernet connection when used in Android, same like my N2. This suggests that my router does not like Linux
ISP Routers are most like a surprise bag.
I´m lucky, have a business contract and got a fritz!box 6591 cable.
But I use this box only as router to provide internet access to my managed switches and wlan access points.
Yes but I´m network professional, most users are not very familiar with network devices and protocols
I experienced similar issues regarding obtaining IP addresses while using Batocera on N2+ and Batocera is another compact Linux based system.
I have tried following routers:
Netgear R6300v2 using oem firmware.
Netgear R6300v2 using DD-WRT.
TP-Link Archer C7 using oem firmware
… and @Sholander and @Shoog might have used other routers.
I had issues using CE and Batocera on these 3 routers I tried but no issues using Android so I am not sure if this is a router issue. More likely a linux implementation issue or a batch production with different NIC on N2+.
edit: I was just browsing Amazon and in the reviews section of Ugoos AM6B+, someone else was compalining that his ethernet is only connecting at 100mbps !
