I recently upgraded from 21.02.2 to 23.05.5 on a Raspberry Pi 4B.
It was working fine prior, but since the upgrade, I am unable to ping outside the network, my subnets and internal routing seem to work just fine.
I have a suspicion something is wrong with the routing, but can't seem to fix it.
I have tried
Full factory flashing - still nothing with default settings
Restoring configs
Copying /etc/config/network from the raspberry pi setup, seems to break more things, and had to restore configs
Additionally, Luci is not working, I can ssh into the router @ 192.168.1.1 but not access the web interface.
This router is the main one, and thus I am without internet.
There is a Virgin Media Hub 5 in modem mode between the pi and the wall, but no setup was required before hand to set that up.
eth1 seems to be missing, are you sure the required kmod is installed?
not sure if it's down to your redacting, but the last two device stanzas (Wireguard and eth0) seem to be orphaned
I don't even want to check if the 8021q stanzas match up to your VLAN definitions
the VLAN definitions themselves seem 'weird', the name matters rather little, but ifname (depreacted) and vid seem wrong
are you sure about bridging eth1 and eth0.18?
you are using a quite wild mix of different ways to enumerate ports/ VLANs
these likely aren't the only issues, just the ones that really jump out
I haven't even checked dhcp/ firewall settings, as my hunch of a missing kmod and a severely problematic /etc/config/network already point at enough potential causes. I would strongly suggest to start the configuration all over again, piece by piece and to check/ review each new interface/ VLAN before adding the others one by one.
Thanks for the response,
I agree it’s quite a weird setup I made for the vlans, blame me 4 years ago when I was beginning this journey.
I have tried already to entirely flash the drive with a new install, that still resulted in the network unreachable errors.
Unless of cause I missed some setup.
WireGuard is orphaned due to my redacting but I did not touch eth0 information… I’ll follow up on that.
Additionally if I’m missing a kmod, how I am to install it without network access?
Identify what kmod you need, download it (and its dependencies), scp -O kmod*.ipk root@192.168.1.1:/tmp/ it over, opkg install /tmp/kmod*.ipk it - or use the (online-)imagebuilder to generate a new image including the necessary packages.
So I’ve been waiting for an ip address to be assigned to eth1.
I’ve even reset the modem, and configured back into a routing mode. Connecting a device directly to that works just fine, gets an ip and connects to the wan.
However, the OpenWrt router still doesn’t, and cannot even ping the known working ip of the upstream modem/router.
Sat Feb 1 12:54:17 2025 daemon.notice netifd: Network device 'eth1' link is down
Sat Feb 1 12:54:17 2025 daemon.notice netifd: Interface 'wan' has link connectivity loss
Sat Feb 1 12:54:17 2025 kern.info kernel: [ 1397.604435] br-lan: port 2(eth1) entered disabled state
Sat Feb 1 12:54:17 2025 daemon.notice netifd: wan (3968): udhcpc: received SIGTERM
Sat Feb 1 12:54:17 2025 kern.info kernel: [ 1397.628983] r8152 2-1:1.0 eth1: carrier off
Sat Feb 1 12:54:17 2025 daemon.notice netifd: wan (3968): udhcpc: entering released state
Sat Feb 1 12:54:17 2025 daemon.notice netifd: wan (3968): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wan" } (Permission denied)
Sat Feb 1 12:54:17 2025 daemon.notice netifd: Interface 'wan' is now down
Sat Feb 1 12:54:18 2025 daemon.warn odhcpd[988]: No default route present, overriding ra_lifetime!
Sat Feb 1 12:54:19 2025 kern.notice kernel: [ 1400.134635] r8152 2-1:1.0 eth1: Promiscuous mode enabled
Sat Feb 1 12:54:19 2025 kern.info kernel: [ 1400.143713] r8152 2-1:1.0 eth1: carrier on
Sat Feb 1 12:54:19 2025 daemon.notice netifd: Network device 'eth1' link is up
Sat Feb 1 12:54:19 2025 daemon.notice netifd: Interface 'wan' has link connectivity
Sat Feb 1 12:54:19 2025 daemon.notice netifd: Interface 'wan' is setting up now
Sat Feb 1 12:54:19 2025 kern.info kernel: [ 1400.151868] br-lan: port 2(eth1) entered blocking state
Sat Feb 1 12:54:19 2025 kern.info kernel: [ 1400.151883] br-lan: port 2(eth1) entered forwarding state
Sat Feb 1 12:54:19 2025 daemon.notice netifd: wan (4129): udhcpc: started, v1.36.1
Sat Feb 1 12:54:19 2025 daemon.notice netifd: wan (4129): udhcpc: broadcasting discover
Sat Feb 1 12:54:23 2025 daemon.notice netifd: wan (4129): udhcpc: broadcasting discover
Sat Feb 1 12:54:26 2025 daemon.notice netifd: wan (4129): udhcpc: broadcasting discover
I don't know if it is doing MAC caching, I'll check now
Rebooting now,
In the modem's dhcp records, I can see that the openwrt router appears to be assigned an ip,
Also, the log, continually is warning about,