Oled displays fallback IP 192.168.0.100

[IoTDot]

Hi,
I decided to connect a TP-Link TL-WR802N V4 travel router in client mode to the NanoKVM-Cube Full, thinking that this would make the device more mobile and I wouldn't have to lay an additional patch cord, for example.
A short patch cord between the router and NanoKVM and a short microUSB cable connected to 5V and GND from UART. The router is connected to my WiFi network.
The problem, however, is that tplink boots longer than NanoKVM and on Oled I get an IP from fallback 192.168.0.100, the router starts to provide an address from DHCP, it disappears from Oled for a moment and 192.168.0.100 reappears, instead of the correct address, which was actually set and retrieved because NanoKVM is available and working properly.
In order for the address on the OLED to correct itself, I have to turn the display off and on or disconnect and reconnect the RJ45, or as a last resort, type

killall udhcpc
udhcpc -i eth0

Unfortunately, none of these solutions please me because they require manual work, and if the device is in a hard-to-reach place, it will be problematic to restart it or ask someone for the IP address from the screen.

Any ideas on how to force the display to refresh this address in line with what the DHCP actually provided? I don't want to throw in any tasks that will burden the memory or processor by checking over and over again if the IP address differs from the one in fallback.

[IoTDot]

Okay, I thought it was the IP assigned by the KVM, but apparently this TP-Link starts by releasing its DHCP before it can retrieve the correct IP address from the main router in client mode.

From my closer observations, it works like this: the KVM starts and attempts to obtain an IP address. At some point, the router starts DHCP in the range 192.168.0.100 to 199. The leased KVM assigns itself to the first one, 100. After that, this address disappears from the OLED screen for a moment and then returns.
When the router starts fully operating in client mode and provides an IP via DHCP from the main router's range, the IP disappears from the OLED screen. After a few seconds, the web UI becomes available, and the KVM is fully functional.
The OLED screen doesn't display an IP address, but the ETH icon indicates that the device is connected.
Sometimes I need to run killall udhcpc and udhcpc -i eth0 twice to update the IP on the OLED, sometimes it doesn't help. I've tried various solutions, changes, delays, and more attempts in

/etc/init.d/S30eth

adding an alias with a different IP address

alias refresh_ip='(sh -c "ip addr flush dev eth0 && ip addr add 192.168.123.123/24 dev eth0 && sleep 1 && ip addr flush dev eth0 && killall udhcpc && sleep 1 && udhcpc -i eth0 -t 10 -T 1 -A 5 -n; echo") &'

and running this alias by refresh_ip

Sometimes it works, sometimes it doesn't, usually running the command twice works.

Tried scripts in /etc/init.d/ and many many things

I mainly use AI chats, but I've spent a whole week on this and I can't get NanoKVM to get the correct and new IP address on the screen WHEN IT CHANGES, if it is connected via Ethernet cable to a router that changes the IP address about 20-25 seconds after starting them together.

[IoTDot]

I was looking for solutions, some worked, many didn't, unfortunately the dev team doesn't reply, the simplest and most effective solution at the moment seems to be resetting kvm_system, in the terminal paste:

sed -i '/for i in \$dns ; do/a\
killall kvm_system 2>/dev/null; /tmp/kvm_system/kvm_system &\
' /usr/share/udhcpc/default.script

after that the terminal can wait for enter to confirm the command

The command does in /usr/share/udhcpc/default.script:

sed -i — edits the file in place (-i), meaning it modifies /usr/share/udhcpc/default.script without making a copy
/for i in \$dns ; do/ — searches the file for a line that matches the pattern for i in $dns ; do

This fragment is located in the script /usr/share/udhcpc/default.script
a\ ... — adds (appends) new code after this line:
killall kvm_system 2>/dev/null — kills the kvm_system process (ignoring the error if there is none)
/tmp/kvm_system/kvm_system & — restarts it in the background

Finally, whenever udhcpc receives or renews an IP address (e.g. when starting the network, reconnecting, etc.), kvm_system will be shut down and restarted immediately.
This way, after getting the correct IP, the OLED screen unfortunately loads completely again and I have the correct IP address on it