Network manager doesn't allow configuration of wireless options

I am also using network manager in Dapper.

I am in an environment where I need to specify which AP to use, as the one with the best link quality is overused, but I haven't found a way to set this in networkmanager.

Obviously a mean to send/specify parameters to be used will be handy.

Wow, these are really way complex wishlist. I recommend opening up power management wishlists on the kernel, as well as upstream.

Rejecting because there is multiple issues and badly framed, at that.

Hi,

I'm not clear on why this was a "complex wishlist". Also, I'm unsure
why this would become a kernel wishlist.

The txpower directive is something that is already supported in Ubuntu
Dapper's default networking infrastructure. I was just submitting a
request that it be supported using network-manager, as well.

Here's the rationale:

If i'm not using network-manager, I can put the following directive in
my interfaces file under the eth1 stanza:
wireless-txpower 25mw
This has the effect of ratcheting eth1's power down to 25% of its max of 100mw.

In order to use network-manager, I have to comment or remove all lines
pertaining to eth1, in order for network-manager to control eth1.
Currently, I know of no way to tell network-manager to set iwconfig
options.

I may have not worded the original request clearly. If that is the
case I'll gladly reword and resubmit.

Please let me know if I can clarify anything.

Thanks
Zach C.

On 10/4/06, Scott Robinson <email address hidden> wrote:
> Wow, these are really way complex wishlist. I recommend opening up power
> management wishlists on the kernel, as well as upstream.
>
> Rejecting because there is multiple issues and badly framed, at that.
>
> ** Changed in: network-manager (Ubuntu)
> Status: Unconfirmed => Rejected
>
> --
> Network manager doesn't allow configuration of wireless options
> https://launchpad.net/bugs/56445
>

Sorry, I was confusing both comments.

Configuring iwconfig options is not within the scope of NetworkManager. It, in fact, does not even use iwconfig. Asking for that is a bit of a "catch-all," and doesn't really come a feature point. (Imaginary response from upstream: if you want to call iwconfig, just type it at your terminal)

Now, with regards to power management and the actual problem you're having, I don't know if power management is really in the stated scope of NetworkManager; however, I have opened and associated an upstream bug with your original text. Good luck. :-)

In the meantime, what I can recommend is adding a script in /etc/network/if-up.d/ or /etc/network/if-pre-up.d/ to ratchet down your power level after association.

Does that help?

Just a sidenote.
network-manager uses libiw (Wireless Tools libs) for functionality. Iwconfig is part of Wireless Tools (wireless-tools package).

I guess for power-level association will require some changes to the battery applet or any power saving tool.

Been awhile since anyone remarked here. I'm just confirming this is still an issue on feisty :( .

Marking as wishlist. We'll have to wait for upstream on this.

network manager approach is zero-configuration ... allowing to configure wireless options would be against that principle.

With a right-click on nm-applet I can disable and enable wireless. Completely disabling the wireless card, which is afaik equivalent to iwconfig txpower off seems the right thing to do when the user turns off wireless. The advantage of this would be reduced power consumption and electromagnetic fields.

nm-applet calls the /etc/network/*.d scripts, so we can turn off txpower there.

copy the attached script to i.e. /etc/network/custom and link to /etc/network/if-pre-up.d/wlan_tx and /etc/network/if-post-down.d/wlan_tx :
sudo -s
mkdir /etc/network/custom
cp wlan_tx /etc/network/custom
ln -s /etc/network/custom/wlan_tx /etc/network/if-pre-up.d/wlan_tx
ln -s /etc/network/custom/wlan_tx /etc/network/if-post-down.d/wlan_tx
exit

Scripts laying in /etc/network/if* works only for phases "up" and "down".
I need to use phase "pre-up" for setting the wireless mode and rate of device.
I know that the rate can be set also in phase "up" but not mode for madwifi as it uses iwpriv for achieving this.

test script laying in all directories logs this:

Tue Nov 11 18:02:59 CET 2008: test within /etc/network/if-up.d/00test of action post-up / interface ath0
Tue Nov 11 18:03:58 CET 2008: test within /etc/network/if-down.d/00test of action down / interface ath0
Tue Nov 11 18:05:16 CET 2008: test within /etc/network/if-up.d/00test of action up / interface ath0
Tue Nov 11 18:05:34 CET 2008: test within /etc/network/if-down.d/00test of action pre-down / interface ath0
Tue Nov 11 18:05:34 CET 2008: test within /etc/network/if-post-down.d/00test of action post-down / interface ath0
Tue Nov 11 18:05:49 CET 2008: test within /etc/network/if-down.d/00test of action down / interface ath0
Tue Nov 11 18:06:02 CET 2008: test within /etc/network/if-up.d/00test of action up / interface ath0

Formerly I had a line like this in /etc/network/interfaces:

> iface ath0 inet dhcp
> pre-up iwpriv $IFACE mode 2
> pre-up iwconfig $IFACE rate 11M

this is now ignored.
I tried with both managed / unmanaged mode for NetworkManager.

# sudo nm-system-settings --config=/etc/NetworkManager/nm-system-settings.conf --debug

** Message: SCPlugin-Ifupdown: init!
** Message: SCPlugin-Ifupdown: update_system_hostname
** Message: SCPluginIfupdown: guessed connection type (ath0) = 802-3-ethernet
** Message: SCPlugin-Ifupdown: update_connection_setting_from_if_block: name:ath0, type:802-3-ethernet, autoconnect:0, id:Ifupdown (ath0), uuid: 02622291-def3-43fe-0000-000000000000
** Message: SCPluginIfupdown: management mode: managed
** Message: SCPlugin-Ifupdown: devices added (udi: /org/freedesktop/Hal/devices/net_00_0c_76_6a_b7_7b, iface: eth0)
** Message: SCPlugin-Ifupdown: devices added (udi: /org/freedesktop/Hal/devices/net_00_19_e0_82_31_3e, iface: ath0)
** Message: SCPluginIfupdown: locking wired connection setting
** Message: SCPlugin-Ifupdown: end _init.
** Message: Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list.
** Message: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
** Message: SCPlugin-Ifupdown: (26708160) ... get_connections.
** Message: SCPlugin-Ifupdown: (26708160) connections count: 1
** Message: Adding default connection 'Auto eth0' for /org/freedesktop/Hal/devices/net_00_0c_76_6a_b7_7b

>Scripts laying in /etc/network/if* works only for phases "up" and "down".

I can confirm this, and have reported it as a second bug here:

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/336736