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#788 - MQMaker WiTi 5ghz interface does not work #5755

Open
openwrt-bot opened this issue May 16, 2017 · 10 comments
Open

FS#788 - MQMaker WiTi 5ghz interface does not work #5755

openwrt-bot opened this issue May 16, 2017 · 10 comments
Labels

Comments

@openwrt-bot
Copy link

neheb:

Supply the following if possible:

  • MQMaker WiTi
  • All released LEDE versions
  • enable the 5ghz interface. LEDE reports that it's up and running but it isn't.

I tried 3 builds.

LEDE trunk - fail
LEDE 17.01.0 - fail
OpenWRT trunk - works.

Something broke in the mt76 driver between OpenWRT trunk and LEDE final.

AFAIK it's after the bug fix to packet injection.

@openwrt-bot
Copy link
Author

neheb:

Update: I tracked the offending commit.

d7f5112c092ce10673b9ce233e96a31f06d82c3d

aka: mt76x2: fix checkpatch warnings

@openwrt-bot
Copy link
Author

bittorf:

can you please show your wireless config (uci show wireless).
i have HEAD running on such a device and IBSS and AP mode is
working with 5GHz radio and 2GHz radio.

@openwrt-bot
Copy link
Author

neheb:

Just stock with option disabled removed from /etc/config/wireless

Doesn't matter really. Any configuration fails for me.

@openwrt-bot
Copy link
Author

bittorf:

maybe you are suffering from the same strange problem which I run into:
what does this output on your router?:

command -v hostapd

@openwrt-bot
Copy link
Author

neheb:

/usr/sbin/hostapd

@openwrt-bot
Copy link
Author

neheb:

btw the 2.4ghz band is fine. it's just the 5ghz band.

@openwrt-bot
Copy link
Author

nbd:

What do you mean by "LEDE reports that it’s up and running but it isn’t"? So the interface is shown as up in ifconfig, iwconfig, etc. but you can't scan it from a client?

@openwrt-bot
Copy link
Author

neheb:

Exactly.

@openwrt-bot
Copy link
Author

nbd:

Is this issue still present in current versions?

@openwrt-bot
Copy link
Author

neheb:

Most likely. I no longer own this unit so I can't test anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant