Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#4198 - Ubnt Bullet M2 XW broken with 21.02+ #9178

Open
openwrt-bot opened this issue Dec 23, 2021 · 10 comments
Open

FS#4198 - Ubnt Bullet M2 XW broken with 21.02+ #9178

openwrt-bot opened this issue Dec 23, 2021 · 10 comments
Labels
flyspray release/21.02 pull request/issue targeted (also) for OpenWrt 21.02 release

Comments

@openwrt-bot
Copy link

champtar:

OpenWRT 19.07 works (https://downloads.openwrt.org/releases/19.07.8/targets/ath79/generic/openwrt-19.07.8-ath79-generic-ubnt_bullet-m-xw-squashfs-factory.bin)
OpenWrt 21.02 or master doesn't (tftp flash or sysupgrade)

(need to find my serial cable now)

@openwrt-bot
Copy link
Author

champtar:

Bullet XM are working fine with 21.02 BTW

@aparcar aparcar added the release/21.02 pull request/issue targeted (also) for OpenWrt 21.02 release label Feb 22, 2022
@owenh000
Copy link

owenh000 commented Feb 24, 2022

Same here. After upgrading to OpenWrt 21.02.1, with the configuration discarded, the Ethernet port never turned on (except briefly during boot, for recovery). I used TFTP to recover. See also https://owenh.net/bulletm2hp.

@aarossig
Copy link

I am running into this issue. If I configure the radio in AP mode, then upgrade from 19 to 21.02.2, I can connect and inspect the system. The ethernet link is up and DHCP offers are going out, but no ACKs are received. I wonder if there is a broken firewall rule.

The output of ip link shows that the ethernet interface is up.

I tried the 22.03.0-rc1 release and had the same issue. Going back to 19 for now.

@ph1l
Copy link

ph1l commented Sep 24, 2022

22.03.0, 21.02.3 both failed for me too.

not able to ping 192.168.1.1 after flashing via tftp recovery.

had to revert back to 19.07.9 to get a working device.

@nikito7
Copy link

nikito7 commented Apr 29, 2023

Any news?

@g6094199
Copy link

g6094199 commented May 7, 2023

this issue should be changed to be more general since this is true for ALL one eth port UBNT units:

i see this error also on:

*NS loco M2 XM
*Rocket M5 XM

eth never comes up on ath79.

the last working build is 19.07

after some investigation i 've found a solution for 1 port XM units as mentioned here:

check you CPU: cat /proc/cpuinfo

for AR7240 or Ar7241

and flash the corresponding Ubiquiti BULLET M image! this is a one port only unit and works like a charm on locos and rocket M (tested)

@NHOQA
Copy link

NHOQA commented Aug 15, 2023

just following up here. have been running into the no eth issue with a pair of rocket m xm boards. i have managed to successfully flash the correct bullet m image for the ar7240 boards. but now the wlan module, if thats the right term, is missing. i have no wifi device showing up under ifconfig, no indication it even exists in luci. ethernet comes up fine

@Leo-PL
Copy link
Contributor

Leo-PL commented Jan 25, 2024

You may want to test and review the PR above - I found the solution.

@Leo-PL
Copy link
Contributor

Leo-PL commented Jan 28, 2024

This was merged into snapshot, a Tested-by on the above would be helpful to get that fixed in stable too.

@owenh000
Copy link

I tested a build of r25153-869df9ecdf on a Bullet M2 XW and it worked. Thanks @Leo-PL!

It looks to me like this issue is resolved and can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flyspray release/21.02 pull request/issue targeted (also) for OpenWrt 21.02 release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants