-
Notifications
You must be signed in to change notification settings - Fork 7
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
reghack was obsolted by OpenWrt r45252 #1
Comments
Wibed is still running r42454 i think. So we need to upgrade it before removing. |
I tried putting the 4 wibed/battlemesh specific patches on top of todays OpenWrt trunk, removed all the regulatory hacking stuff which should no longer be needed (and if so, can be re-introduced part-by-part) |
In branch wbmv8 is removed: |
Did that obscure bug making the choise of either DFS-FCC or DFS-ETSI affect transmit power on 2.4GHz affect us as well? |
Current wibed master branch is still on barrier breaker stable. Once Chaos Calmer is out and we update the firmware we can close this. Is that ok with you? |
also i want to point out, that reghack was never needed, because we dont need DFS channels and we reduce the power anyway - do you agree? |
Yes in the WBM case, but others who use Wibed to deploy their testbeds may want to use DFS channels and high power. As far as Wibed is designed to be used for research purposes it should allow the maximum number of possible scenarios (IMO). cheers On 12 agost de 2015 11:55:14 CEST, Bastian Bittorf [email protected] wrote:
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
Even if we don't disable it, current version of reghack that is part of On Wed, Aug 12, 2015 at 12:13 PM, Pau [email protected] wrote:
|
we are using internally a patch, which patches mac80211/ath9k on compile time: |
it should no longer be needed. Anyone?
The text was updated successfully, but these errors were encountered: