Posted by Grommish on Jul 21, 2020; 5:40pm
URL: https://itus.accessinnov.com/Itus-Networks-Shield-Firmware-v2-Released-tp2084p2114.html

Please let me know..  

I know that ethernet driver issues will cause issues similar to the "bug" your describing, since eth1/eth2 are bridged and static IP'ed by default.  To doing an ifconfig would show the br-lan IP and nothing under eth0, but would seem to work once you "got a WAN IP"..

Well, I think it's just because it decided to work at all and the WAN IP is a easy and visible variable to check.  I am concerned you saw any issues at all on a 4.19 build though, I'll have to retest it.  All of this was a swirling cloud as to  how the target was setup, how it was sharing space, etc, then the jump to 5.4..  It was a mess.

By default, OpenWrt uses eth1 as WAN and eth0 as LAN.  I set it so it should at least be eth0=WAN, eth1/eth2=LAN by default.. If you get into a No-IP situation, will you check /etc/board.d/01_network and make sure that is there?  If not, try hooking it up WAN=Eth1, LAN=eth0.

root@Shield:/# cat /etc/board.d/01_network
#!/bin/sh
#
# Copyright (C) 2014-2015 OpenWrt.org
#

. /lib/functions/uci-defaults.sh

board_config_update

case "$(board_name)" in
itus*)
        ucidef_set_interfaces_lan_wan "eth1 eth2" "eth0"
        ;;
*)
        ucidef_set_interfaces_lan_wan "eth0" "eth1"
        ;;
esac

board_config_flush

exit 0
root@Shield:/#

I'm still working on things, so we'll get it figured out :)