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

reghack was obsolted by OpenWrt r45252 #1

Open
dangowrt opened this issue Apr 8, 2015 · 9 comments
Open

reghack was obsolted by OpenWrt r45252 #1

dangowrt opened this issue Apr 8, 2015 · 9 comments

Comments

@dangowrt
Copy link

dangowrt commented Apr 8, 2015

it should no longer be needed. Anyone?

@emmdim
Copy link
Contributor

emmdim commented Apr 8, 2015

Wibed is still running r42454 i think. So we need to upgrade it before removing.
Pau, do you think you can upgrade?

@dangowrt
Copy link
Author

dangowrt commented Apr 8, 2015

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)

https://github.com/dangowrt/wibed-cc

@ghost
Copy link

ghost commented Aug 6, 2015

In branch wbmv8 is removed:
5d50162#diff-73fe910fb7d551eee7554e161b5badabR3

@dangowrt
Copy link
Author

Did that obscure bug making the choise of either DFS-FCC or DFS-ETSI affect transmit power on 2.4GHz affect us as well?
https://lists.openwrt.org/pipermail/openwrt-devel/2015-August/034829.html
Apart from that, I reckon we can close this ticket...?

@emmdim
Copy link
Contributor

emmdim commented Aug 10, 2015

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?

@bittorf
Copy link

bittorf commented Aug 12, 2015

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?

@p4u
Copy link
Member

p4u commented Aug 12, 2015

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:

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?


Reply to this email directly or view it on GitHub:
#1 (comment)

Sent from my Android device with K-9 Mail. Please excuse my brevity.

@zavalyshyn
Copy link
Contributor

Even if we don't disable it, current version of reghack that is part of
wibed-packages doesn't work with the latest OpenWRT trunk. When selected,
reghack leaves the channels settings as they were by default.

On Wed, Aug 12, 2015 at 12:13 PM, Pau [email protected] wrote:

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:

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?


Reply to this email directly or view it on GitHub:

#1 (comment)

Sent from my Android device with K-9 Mail. Please excuse my brevity.


Reply to this email directly or view it on GitHub
#1 (comment)
.

@bittorf
Copy link

bittorf commented Aug 12, 2015

we are using internally a patch, which patches mac80211/ath9k on compile time:
https://github.com/bittorf/kalua/blob/master/openwrt-patches/reghack/900-regulatory-compliance_test.patch

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

No branches or pull requests

5 participants