Google image attached as an example.
I shipped this router to my inlaws and im not seeing any 'upstream' references on the status page. I can go into network > interfaces and I see Eth0.2, but from here I am kinda at a loss.
This happened to me with my first Archer A7 too and I ended up bricking it by doing silly things, so I bought this one and did not have any issues with the setup, and now that I have mailed it across the country it is misbehaving.
Yes, I know the software is a bit out of date, but I wanted to use IpTable FW rules rather than the new ones.
Does anyone have any idea what could cause this to happen?
I assume you are in the same place as the router? That's likely going to be necessary for us to help.
First thing...
21.02 is EOL and unsupported, and there are important security patches in the latest versions. What specific types of rules are you implementing in iptables that you are concerned with replicating? The topic of iptables > nftables has been discussed a fair amount lately; it doesn't necessarily need to be that complicated or difficult, but obviously it does depend on the rulesets. If you can use the standard UCI rulesets, the underlying mechanism is actually abstracted so you don't even need to worry about it at all.
I'm assuming this is an A7v5? If so, you should upgrade to 23.05.2:
https://firmware-selector.openwrt.org/?version=23.05.2&target=ath79%2Fgeneric&id=tplink_archer-a7-v5
Next, what is physically upstream of the A7? Is it a modem (cable/dsl/cellular) or an ONT? Or another router? or something else? Can you confirm that you're getting a physical link? And are you able to confirm that you're getting full connectivity (i.e. an IP address) when using a different device?
- What protocol is used by the working device (DHCP, PPPoE, static)?
- Have you restarted the modem/upstream device? Some modems (especially cable modems) will 'learn' a single MAC address and will not issue an IP to another device until that association is cleared. Rebooting the modem will usually clear that. You may have to do this a few times or even leave the device unpowered for 5-30 minutes.
Typically:
- unplug ethernet and power from your modem
- unplug power from the router
- plug the power back into the modem and wait for it to fully boot
- plug in the power for the router
- reconnect the ethernet.
If that doesn't solve the issue, let's see your configs:
Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
ubus call system board
cat /etc/config/network
cat /etc/config/wireless
cat /etc/config/dhcp
cat /etc/config/firewall
1 Like