Ethernet (DHCP) not working after July update

[bmillham]

Well, a simple workaround could be instead of a static IP on the router, set a static IP on the 4K.

[slicepaperwords]

yeah that’s how I got it working again this time. still just curious as to why I need a workaround though I guess.

[slicepaperwords]

Network interface not restarting

I have my Vero 2 set to a static MAC IP address on my router, I have tried with it disabled as well. I need to restart my ethernet adapter every time I reboot or switch into android and back into OSMC. I obviously didn’t face the issue with android on my pi2 or 3, but I didn’t have the issue with rebooting, is it a soft reboot and not rebooting the network interface? is there a way I could add that?

Wired connection stopped working after upgrade

It will be put in the Kodi log. At this point I’d suggest reinstalling OSMC. Something seems borked.

there is a fix provided by Sam in the second link, but it is not working this time.
seems I first raised this with the Vero 2.

[shiro35]

@bmillham

If it seems to be a problem with the Mikrotik router, have you tried contacting their support for help?

I dont think its in the router, because I am using it for about 6 years. During that time, I have connected many various devices into it, and Vero4k was only one device with such issues. Also, making static IP for Vero4k in the router, didnt help. Those two devices simply dont like each other over LAN

[damir.matacin]

If it is helpful, I also have a Mikrotik router RB962UiGS-5HacT2HnT (hAP ac) with static IP for Vero 4K and wired network is flawless from day one, and with July update.

[djbloc]

I also own a Mikrotik router.

On the router have you set the DHCP Server setting “Authoritative” = Yes? (If I recall correctly it defaults to “after 2s delay”)

You can find this setting by going to IP > DHCP Server. Click on the entry and it will bring up the settings menu and its about half way down the page.

If Vero works with static IP but not without then I’m confident that will fix the issue.

[dansjackson]

If you set the Static IP on the Vero and reserve the address on the DHCP server using its MAC address (or for that matter any random unused MAC address), then this will prevent against conflicts? If the Vero’s Static IP is on the DHCP server then regardless of whether it’s seen by the DHCP or not, the DHCP server should never lease out that IP. So no conflicts and you’ll never have a problem?

Whilst the DHCP server should work, given the situation, does it need to? The only time it’d be a problem was if you regularly moved the Vero to different networks. If I were in this situation I’d just stick to using a Static IP and tell the DHCP not to issue the Vero’s IP to any other device.

[denixx.baykin]

Hi 2 All!
Got problem connecting OSMC@RaspberryPi3 to Ethernet switch.
It also won’t to get IP automatically. Before I was using WiFi-adapter, but at new place I was able to connect pi to Ethernet.
Was getting “empty” IP on pi, couldn’t figure out what’s wrong.
Was also thinking that it is some problem with software.
BUT!
Took long Ethernet cable, and connected directly into switch. Got working network on device!
Figured out, that problem is with wall sockets. Looks like if I don’t use color scheme in wall sockets, it is failing to work properly. After I rebuilt wall sockets from both sides - it is now works flawlessly! Used color scheme for TIA-B for both sides, color-to-color as on the sticker on the socket.

Actually, problem wasn’t seen even with simple Ethernet tester that I have. It was showing that links in normal direction. But reassembling the sockets cured the issue.