Bug 10151

Summary:	wireless protocol-country should be linked to site, not global
Product:	Mageia	Reporter:	Tony Blackwell <tablackwell>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	enhancement
Priority:	Normal	CC:	derekjenn, mageia, thierry.vignaud
Version:	3
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	drakx-net	CVE:
Status comment:

Description Tony Blackwell 2013-05-19 01:54:23 CEST

Description of problem:When configuring wireless vi MCC, it is necessary to click the 'advanced' box and select one's country, 'us', 'au' etc.  This seems to be global.

I would be more use for a traveller if the protocol-country was associated with the particular connection being configured, so once set-up, there was no need to keep going back into that 'advanced' configuration box to reset the country to where you were at the time.  The communication protocol is after all a property of the site being connected to in a particular country, not a property of the laptop being carried around.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:

Comment 1 Tony Blackwell 2013-05-19 01:55:36 CEST

s/I would be more use/It would be more use

Thierry Vignaud 2013-05-19 16:07:22 CEST

CC: (none) => mageia, thierry.vignaud
Source RPM: (none) => drakx-net

Comment 2 Derek Jennings 2013-05-19 16:41:52 CEST

When connecting to an Access Point it is the AP who chooses the channel. 

If the channel defined in the AP is not available in the client e.g access point uses channel 13 and client is configured for US (channels 1 to 11), then the access point will not even come up in the list to be selected so there is no point having the regulatory domain selectable per channel.

If the client is configured for Europe (channels 1 to 13) then it will work anywhere in the world anyway

CC: (none) => derekjenn

Comment 3 Tony Blackwell 2013-05-20 02:30:36 CEST

I don't understand your reference to channels, perhaps because I don't understand wireless protocols in different countries.  I'm referring to the country; if I remember correctly, mageia defaults to US regulatory domain.  In Australia, it still shows US, even though I chose Australia at the end of package install (is this another bug?).  I need to go into advanced setup and change this to AU before wireless will work.  If the country corresponds in some way to channels I don't know this, and in any case Mageia advanced config offers a choice of countries, not channels, so are channels relevant to user choices?

It is the country which I think should be associated with the access point.

Comment 4 Tony Blackwell 2014-03-15 20:51:40 CET

Revisiting this old bug, as of M4.  My problem was that for things to work in Australia I had to change from the default US wireless config.
If the above comment from Derek is so, then would it mostly resolve the issue if we defaulted to a Europe wireless domain rather than US at install?  What currently happens for European users - do they all have to manually change this?

(I take it it is too hard to have the scope of the wireless domain linked to the country for which the particular wireless link applies?)

I'll be off to Europe in a few weeks - be interested to see how M4 behaves in this regard.

Comment 5 Marja Van Waes 2015-03-31 16:04:44 CEST

Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD