Hi guys.
For weeks I have been struggling with a strange problem with a Ubiquiti AP-LR.
After a reboot with factory configuration, I have no access via the LAN interface. On the serial console after starting the network, a message similar like this appears:
[ 5053.457782] br-lan: received packet on eth0 with own address as source address (addr:44:d9:e7:74:8a:a3, vlan:0)
OK, got it. Seems to be a network loop. But there is only a single PC
with a fixed IP connected to the LAN interface, no other switch or other network hardware.
Sometimes everything works normally if I restart the network without rebooting. Then I can also connect the LAN interface to my normal network and have access to LUCI and the AP has access to the Internet etc.
I have now found out that the interface or LAN bridge usually works properly if I
stop the network, make some changes in the file /etc/config/network, e.g. change the MAC address or IP address or add 'option stp 1' and then start the network again.
After a complete reboot, the network generally doesn't work, I always have to make a change to /etc/config/network first.
I'm currently poking around in the many init scripts to possibly find a workaround for this strange behavior, but so far without success.
Maybe someone here has a tip for me...
Thanks
You only have a single Ethernet port, so stp is not typically necessary here.
How is the device connected to your pc alone? Do you have a poe injector or a poe switch? If you’re using a switch, is it still connected to the upstream network, or are the only connections your ap and your pc?
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:
Disable the dhcp server if your main router already has a dhcp server running.
Also consider upgrading to 23.05.5.
Reboot after the changes and it should work normally. Don’t forget to enable WiFi (which I’m assuming is the whole point of this device on your network).
Unfortunately, that's exactly what it doesn't do.
I had already activated WiFi. It works perfectly and I can access my normal network through it.
I currently only have version 23.5.0 installed for testing purposes, I previously had 23.5.03 and 23.05.05 installed with the same problem.
And without the entries 'option macaddress ...' and 'option stp ...' the problem doesn't change.
I'll do it again now anyway.
After upgrade to 23.5.05 network is fine. Then reboot.
BusyBox v1.36.1 (2024-09-23 12:34:46 UTC) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt 23.05.5, r24106-10cc5fcd00
-----------------------------------------------------
root@OpenWrt:/#
... snip ...
[ 127.146734] br-lan: received packet on eth0 with own address as source address (addr:44:d9:e7:74:8a:a3, vlan:0)
[ 128.186718] br-lan: received packet on eth0 with own address as source address (addr:44:d9:e7:74:8a:a3, vlan:0)
service network stop
[ 139.142667] br-lan: port 2(phy0-ap0) entered disabled state
[ 139.148522] br-lan: port 1(eth0) entered disabled state
[ 139.196690] device eth0 left promiscuous mode
[ 139.201326] br-lan: port 1(eth0) entered disabled state
[ 139.236997] eth0: link down
[ 139.244123] device phy0-ap0 left promiscuous mode
[ 139.249163] br-lan: port 2(phy0-ap0) entered disabled state
root@OpenWrt:/#
root@OpenWrt:/# vi /etc/config/network
... snip ... (added option macaddr ...)
root@OpenWrt:/# service network start
root@OpenWrt:/# [ 410.983790] br-lan: port 1(eth0) entered blocking state
[ 410.989188] br-lan: port 1(eth0) entered disabled state
[ 410.994893] device eth0 entered promiscuous mode
[ 413.068398] eth0: link up (100Mbps/Full duplex)
[ 413.073052] br-lan: port 1(eth0) entered blocking state
[ 413.078367] br-lan: port 1(eth0) entered forwarding state
[ 413.106622] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[ 416.597268] br-lan: port 2(phy0-ap0) entered blocking state
[ 416.602917] br-lan: port 2(phy0-ap0) entered disabled state
[ 416.609068] device phy0-ap0 entered promiscuous mode
[ 416.701228] br-lan: port 2(phy0-ap0) entered blocking state
[ 416.706934] br-lan: port 2(phy0-ap0) entered forwarding state
[ 416.713240] br-lan: port 2(phy0-ap0) entered disabled state
[ 416.738390] device phy0-ap0 left promiscuous mode
[ 416.743313] br-lan: port 2(phy0-ap0) entered disabled state
[ 416.807226] br-lan: port 2(phy0-ap0) entered blocking state
[ 416.812878] br-lan: port 2(phy0-ap0) entered disabled state
[ 416.819026] device phy0-ap0 entered promiscuous mode
[ 417.407404] IPv6: ADDRCONF(NETDEV_CHANGE): phy0-ap0: link becomes ready
[ 417.414494] br-lan: port 2(phy0-ap0) entered blocking state
[ 417.420204] br-lan: port 2(phy0-ap0) entered forwarding state
... snip ... (network is fine!)
The AP is currently connected to the switch via the PoE injector, which is also how it accesses the standard gateway, DNS and Internet.
I also have access via serial console if the LAN interface is not working.
Tomorrow I can connect the AP directly to the PC again, without a switch.
But the error occurred in this configuration too.
By the way, I don't actually need the LAN connection for the purpose I want to use the AP for. I just want to connect several more distant IP cameras to the central unit and if I deactivate the LAN interface, it works perfectly.
But I'm interested in the problem and I really want to find out the cause.
If the error occurs and I edit /etc/config/network, it doesn't matter whether I add or remove lines or change values. The main thing is that the file changes. Then after 'network start' everything works fine without errors.
In the end, this won't be an existential problem if we can't find the error definitively here and now.
Perhaps the problem will resolve itself with a later upgrade.
If this is only happening during the boot-up proccess and not later, then it really isn't an issue you need to worry about.
The question in the end is simple:
Is the device operating as expected once fully booted?
(this means both operating as a bridged AP and accessible for administration via ssh and/or http/https)
Hi.
Today I did a lot of intensive tests with the device. So it doesn't matter whether I connect the LAN connection individually
and directly to the PC or to the local network via the switch, it always behaves the same.
Even if only the power supply is connected and there is no network connection at all. After rebooting, the error message appears
and if I then edit /etc/config/network and restart the network, everything works normally.
But sometimes only after the 2nd or 3rd attempt.