After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 359584 - Support TX power configuration
Support TX power configuration
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
0.6.6
Other All
: Normal enhancement
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2006-10-04 13:06 UTC by Scott Robinson
Modified: 2012-07-27 01:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Scott Robinson 2006-10-04 13:06:33 UTC
"I am using network manager in Dapper to automatically switch between wired and wireless interfaces. Before I started using network manager, I was using the wireless-txpower directive in the interfaces file to ratchet down the transmit power on my wireless interface, which yields a significant improvement in battery life. I cannot find a means of configuring this with network-manager. I can still set wireless options manually with iwconfig."

https://launchpad.net/distros/ubuntu/+source/network-manager/+bug/56445
Comment 1 Brian Szymanski 2007-05-10 18:22:27 UTC
Reading the bug on ubuntu forums, this is more general and more important than just the usage the OP suggested. The root problem is that NM doesn't run any of the scripts in /etc/network/if-up.d, and instead uses scripts in /etc/Network‐Manager/dispatcher.d . This is a (mostly) useless duplication of effort/configuration for folks who don't always run NM.

For example, on my amd64 ubuntu feisty machine:

ski@ganiodayo:/etc/network/if-up.d$ ls -l
total 24
-rwxr-xr-x 1 root root  894 2007-03-27 14:40 avahi-autoipd*
-rwxr-xr-x 1 root root 2005 2007-03-27 14:40 avahi-daemon*
-rwxr-xr-x 1 root root 3190 2007-04-10 17:49 mountnfs*
-rwxr-xr-x 1 root root  462 2007-03-07 15:43 ntpdate*
lrwxrwxrwx 1 root root   32 2007-05-01 05:35 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh*

Presumably wpasupplicant is unnecessary in this context, but the others like mountnfs and ntpdate are not (and mountnfs is rather important for my usage).

Comment 2 Brian Szymanski 2007-05-10 18:25:08 UTC
Actually, on a little more digging, it appears that there is a 
/etc/NetworkManager/dispatcher.d/01ifupdown script which tries to launch scripts from /etc/network/if-up.d . Does this not work on other systems besides ubuntu? If not it's starting to look like an ubuntu bug. Can someone confirm that this works for them on a non-ubuntu machine and I'll refile the bug properly with ubuntu?
Comment 3 Dan Williams 2008-04-27 21:44:31 UTC
If the dispatcher is enabled, you can put whatever you'd like into the dispatcher scripts and it should get executed, yes...  0.7 will support setting the TX power though.
Comment 4 zehn97drei 2009-04-05 21:49:55 UTC
network-manager- 
Comment 5 zehn97drei 2009-04-05 22:35:50 UTC
sorry, cat on the keyboard^^

network-manager-0.7~~svn20081018t105859-0ubuntu1.8.10.2

does not turn off txpower on AR5212 (ath5k.ko) when disabling wireless networking in nm-applet.
As far as I can see, there's no hook in the dispatcher on disabling i.e. wlan.
Comment 6 Pavel Simerda 2012-07-27 01:11:34 UTC
It's been there for long time now.

zehn97drei: Please report any problems in a new bugreport if applicable to NM 9.x.