It only came up for me if the modem was online first for the shield to get the WAN IP from. I'll mess around with it to see if maybe a network or firewall restart can get around it... it's like it only checked once to get an IP and that's it
First THREE posts have been updated to reflect the new (hopefully) perm repo.
Now, few things to announce.
I have submitted the Itus Networks Shield to be included in the OpenWrt mainline. Which means it would be an officially supported device. However, to do this, the image will only work with the ROUTER slot, and effectively removes multi-boot capabilities outside of emergency contingencies. I, on the other hand, am continuing the produce builds that work in the Gateway and Bridge slots. Since I created the device OpenWrt is going to use (assuming they accept it), it's easy to just "expand" it locally - AND, it means anything that is made by OpenWrt officially down the line would be compatible with my images, (and should be vice-versa).
If you're interested, you can check out the Pull Request (PR) here.
For users who don't care about the technical minutiae, this represented the best compromise between getting real support for everyone and still allowing me to push forward on the other slots.
I will say, however, that MY version is tuned for the chip, rather than the overall arch The OpenWrt builds, if approved and built, will use octeonplus as a CPU define, where-as I use octeon3 directly. I'm not sure if there is any impact on it, and I wouldn't know how to quantify it, but I know the kernel treats the levels differently (octeonplus is even older than octeon2)...