FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora User

 
 
LinkBack Thread Tools
 
Old 07-15-2011, 07:48 PM
Ian Pilcher
 
Default NM_CONTROLLED=no not working

I feel like I'm losing my mind. Can someone confirm that this is
supposed to work before I bugzilla this?

I am trying to get NetworkManager to ignore my wireless adapter (while
still managing my Ethernet adapter and VPN connections). I have created
/etc/sysconfig/network-scripts/ifcfg-wlan0:

DEVICE=wlan0
TYPE=Wireless
HWADDR=00:23:14:12:C1:38
NM_CONTROLLED=no

Even after rebooting, however, NetworkManager is still taking control of
wlan0.

So who is crazy, me or the computer? :-|

Thanks!

(This Fedora 15 with NetworkManager-0.8.9997-5.git20110702.fc15.x86_64,
BTW.)

--
================================================== ======================
Ian Pilcher arequipeno@gmail.com
"If you're going to shift my paradigm ... at least buy me dinner first."
================================================== ======================

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 07-15-2011, 08:08 PM
Genes MailLists
 
Default NM_CONTROLLED=no not working

On 07/15/2011 03:48 PM, Ian Pilcher wrote:

>
> DEVICE=wlan0
> TYPE=Wireless
> HWADDR=00:23:14:12:C1:38
> NM_CONTROLLED=no
>
> Even after rebooting, however, NetworkManager is still taking control of
> wlan0.
>
>

Can you confirm (iwconfig) that the device is indeed called wlan0?

Perhaps its a different name.

gene/
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 07-15-2011, 08:29 PM
Ian Pilcher
 
Default NM_CONTROLLED=no not working

On 07/15/2011 05:08 PM, Genes MailLists wrote:
>
> Can you confirm (iwconfig) that the device is indeed called wlan0?
>
> Perhaps its a different name.
>

[ipilcher@localhost ~]$ cat /etc/sysconfig/network-scripts/ifcfg-wlan0
DEVICE=wlan0
TYPE=Wireless
HWADDR=00:23:14:12:C1:38
NM_CONTROLLED=no

[ipilcher@localhost ~]$ ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:23:14:12:C1:38
inet addr:10.192.53.204 Bcast:10.192.55.255 Mask:255.255.252.0
inet6 addr: fe80::223:14ff:fe12:c138/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17347 errors:0 dropped:0 overruns:0 frame:0
TX packets:19046 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:10596012 (10.1 MiB) TX bytes:3456668 (3.2 MiB)

[ipilcher@localhost ~]$ iwconfig wlan0
wlan0 IEEE 802.11abgn ESSID:"Red Hat Guest"
Mode:Managed Frequency:2.412 GHz Access Point:
00:26:0B:16:34:54
Bit Rate=54 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thrff Fragment thrff
Power Managementff
Link Quality=69/70 Signal level=-41 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:8 Invalid misc:409 Missed beacon:0

[ipilcher@localhost ~]$ nmcli dev list iface wlan0
GENERAL.DEVICE: wlan0
GENERAL.TYPE: 802-11-wireless
GENERAL.DRIVER: iwlagn
GENERAL.HWADDR: 00:23:14:12:C1:38
GENERAL.STATE: connected
CAPABILITIES.CARRIER-DETECT: no
CAPABILITIES.SPEED: 54 Mb/s
WIFI-PROPERTIES.WEP: yes
WIFI-PROPERTIES.WPA: yes
WIFI-PROPERTIES.WPA2: yes
WIFI-PROPERTIES.TKIP: yes
WIFI-PROPERTIES.CCMP: yes
AP1.SSID: 'HP85722C'
AP1.BSSID: 02:21:01:FD:3D:F8
AP1.MODE: Ad-Hoc
AP1.FREQ: 2457 MHz
AP1.RATE: 11 MB/s
AP1.SIGNAL: 20
AP1.SECURITY:
AP1.ACTIVE: no
AP2.SSID: 'HPEEBEA3'
AP2.BSSID: 02:21:C1:12:13:0E
AP2.MODE: Ad-Hoc
AP2.FREQ: 2457 MHz
AP2.RATE: 11 MB/s
AP2.SIGNAL: 27
AP2.SECURITY:
AP2.ACTIVE: no
AP3.SSID: 'SMK'
AP3.BSSID: 00:14:BF:B6:BF:B9
AP3.MODE: Infrastructure
AP3.FREQ: 2437 MHz
AP3.RATE: 54 MB/s
AP3.SIGNAL: 25
AP3.SECURITY: WPA2
AP3.ACTIVE: no
AP4.SSID: 'HP50116B'
AP4.BSSID: 02:29:A9:EC:12:50
AP4.MODE: Ad-Hoc
AP4.FREQ: 2457 MHz
AP4.RATE: 11 MB/s
AP4.SIGNAL: 27
AP4.SECURITY:
AP4.ACTIVE: no
AP5.SSID: 'Cadec'
AP5.BSSID: 00:16:B6:2E:8C:28
AP5.MODE: Infrastructure
AP5.FREQ: 2412 MHz
AP5.RATE: 54 MB/s
AP5.SIGNAL: 24
AP5.SECURITY: WEP
AP5.ACTIVE: no
AP6.SSID: 'TOTAL'
AP6.BSSID: D8:5D:4C:C2:AF:0C
AP6.MODE: Infrastructure
AP6.FREQ: 2442 MHz
AP6.RATE: 54 MB/s
AP6.SIGNAL: 24
AP6.SECURITY: WEP
AP6.ACTIVE: no
AP7.SSID: 'NALCO'
AP7.BSSID: 00:1D:71:09:B4:30
AP7.MODE: Infrastructure
AP7.FREQ: 2412 MHz
AP7.RATE: 54 MB/s
AP7.SIGNAL: 19
AP7.SECURITY: WPA WPA2 Enterprise
AP7.ACTIVE: no
AP8.SSID: 'IMarket'
AP8.BSSID: 00:02:6F:91:719
AP8.MODE: Infrastructure
AP8.FREQ: 2422 MHz
AP8.RATE: 54 MB/s
AP8.SIGNAL: 25
AP8.SECURITY: WPA
AP8.ACTIVE: no
AP9.SSID: 'HP8BAF53'
AP9.BSSID: 02:25:052:65:C9
AP9.MODE: Ad-Hoc
AP9.FREQ: 2457 MHz
AP9.RATE: 11 MB/s
AP9.SIGNAL: 27
AP9.SECURITY:
AP9.ACTIVE: no
AP10.SSID: 'IMarket'
AP10.BSSID: 00:02:6F:91:715
AP10.MODE: Infrastructure
AP10.FREQ: 2417 MHz
AP10.RATE: 54 MB/s
AP10.SIGNAL: 29
AP10.SECURITY: WPA
AP10.ACTIVE: no
AP11.SSID: 'YCPM-2'
AP11.BSSID: 00:16:B6:F7:16:83
AP11.MODE: Infrastructure
AP11.FREQ: 2462 MHz
AP11.RATE: 54 MB/s
AP11.SIGNAL: 20
AP11.SECURITY: WPA WPA2
AP11.ACTIVE: no
AP12.SSID: 'ECLLAR'
AP12.BSSID: 00:1D:7E:62:CB:9D
AP12.MODE: Infrastructure
AP12.FREQ: 2437 MHz
AP12.RATE: 54 MB/s
AP12.SIGNAL: 62
AP12.SECURITY: WEP
AP12.ACTIVE: no
AP13.SSID: 'ECLLGCO'
AP13.BSSID: 00:0D:3A:2B:ED:A3
AP13.MODE: Infrastructure
AP13.FREQ: 2437 MHz
AP13.RATE: 54 MB/s
AP13.SIGNAL: 30
AP13.SECURITY: WEP
AP13.ACTIVE: no
AP14.SSID: 'HPC7B3DF'
AP14.BSSID: 02:20:50:93:AB:3B
AP14.MODE: Ad-Hoc
AP14.FREQ: 2457 MHz
AP14.RATE: 11 MB/s
AP14.SIGNAL: 29
AP14.SECURITY:
AP14.ACTIVE: no
AP15.SSID: 'HPD110a.F932B1'
AP15.BSSID: 02:26:26:13:4C:12
AP15.MODE: Ad-Hoc
AP15.FREQ: 2437 MHz
AP15.RATE: 54 MB/s
AP15.SIGNAL: 55
AP15.SECURITY:
AP15.ACTIVE: no
AP16.SSID: 'Cheff'
AP16.BSSID: D00:FD:66:4F:99
AP16.MODE: Infrastructure
AP16.FREQ: 2412 MHz
AP16.RATE: 54 MB/s
AP16.SIGNAL: 24
AP16.SECURITY: WEP
AP16.ACTIVE: no
AP17.SSID: 'VP Argentina'
AP17.BSSID: 00:17:9A:59:CF:CF
AP17.MODE: Infrastructure
AP17.FREQ: 2437 MHz
AP17.RATE: 54 MB/s
AP17.SIGNAL: 29
AP17.SECURITY: WEP
AP17.ACTIVE: no
AP18.SSID: 'Cheff'
AP18.BSSID: 00:24:73:1EB:A0
AP18.MODE: Infrastructure
AP18.FREQ: 2462 MHz
AP18.RATE: 54 MB/s
AP18.SIGNAL: 39
AP18.SECURITY: WEP
AP18.ACTIVE: no
AP19.SSID: 'Essen BA2'
AP19.BSSID: 00:1B:11:06:E3:13
AP19.MODE: Infrastructure
AP19.FREQ: 2412 MHz
AP19.RATE: 54 MB/s
AP19.SIGNAL: 45
AP19.SECURITY: WEP
AP19.ACTIVE: no
AP20.SSID: 'Speedy-273d'
AP20.BSSID: 00:E0:4D:2D:03:08
AP20.MODE: Infrastructure
AP20.FREQ: 2437 MHz
AP20.RATE: 54 MB/s
AP20.SIGNAL: 40
AP20.SECURITY: WEP
AP20.ACTIVE: no
AP21.SSID: 'rh-wireless'
AP21.BSSID: 00:19:07:97:1C:31
AP21.MODE: Infrastructure
AP21.FREQ: 2462 MHz
AP21.RATE: 54 MB/s
AP21.SIGNAL: 60
AP21.SECURITY: WEP
AP21.ACTIVE: no
AP22.SSID: 'rh-wireless'
AP22.BSSID: 00:25:84:95:78:01
AP22.MODE: Infrastructure
AP22.FREQ: 2437 MHz
AP22.RATE: 54 MB/s
AP22.SIGNAL: 72
AP22.SECURITY: WEP
AP22.ACTIVE: no
AP23.SSID: 'rh-wireless'
AP23.BSSID: 00:26:0B:16:34:50
AP23.MODE: Infrastructure
AP23.FREQ: 2412 MHz
AP23.RATE: 54 MB/s
AP23.SIGNAL: 74
AP23.SECURITY: WEP
AP23.ACTIVE: no
AP24.SSID: 'Amarillas'
AP24.BSSID: 00:02:6F:80:99:A4
AP24.MODE: Infrastructure
AP24.FREQ: 2457 MHz
AP24.RATE: 54 MB/s
AP24.SIGNAL: 27
AP24.SECURITY: WPA
AP24.ACTIVE: no
AP25.SSID: 'Elisabel WI FI'
AP25.BSSID: 00:22:6B:A6:F1:0E
AP25.MODE: Infrastructure
AP25.FREQ: 2447 MHz
AP25.RATE: 54 MB/s
AP25.SIGNAL: 32
AP25.SECURITY: WPA
AP25.ACTIVE: no
AP26.SSID: 'Red Hat Guest'
AP26.BSSID: 00:19:07:97:1C:34
AP26.MODE: Infrastructure
AP26.FREQ: 2462 MHz
AP26.RATE: 54 MB/s
AP26.SIGNAL: 59
AP26.SECURITY: WPA2
AP26.ACTIVE: no
AP27.SSID: 'RH_WLAN_TRUST'
AP27.BSSID: 00:19:07:97:1C:32
AP27.MODE: Infrastructure
AP27.FREQ: 2462 MHz
AP27.RATE: 54 MB/s
AP27.SIGNAL: 57
AP27.SECURITY: WPA2 Enterprise
AP27.ACTIVE: no
AP28.SSID: 'Red Hat'
AP28.BSSID: 00:19:07:97:1C:33
AP28.MODE: Infrastructure
AP28.FREQ: 2462 MHz
AP28.RATE: 54 MB/s
AP28.SIGNAL: 59
AP28.SECURITY: WPA2 Enterprise
AP28.ACTIVE: no
AP29.SSID: 'RH_WLAN_TRUST'
AP29.BSSID: 00:25:84:95:78:02
AP29.MODE: Infrastructure
AP29.FREQ: 2437 MHz
AP29.RATE: 54 MB/s
AP29.SIGNAL: 69
AP29.SECURITY: WPA2 Enterprise
AP29.ACTIVE: no
AP30.SSID: 'MSHOME'
AP30.BSSID: 00:25:9C:69:6C:AF
AP30.MODE: Infrastructure
AP30.FREQ: 2437 MHz
AP30.RATE: 54 MB/s
AP30.SIGNAL: 72
AP30.SECURITY: WPA
AP30.ACTIVE: no
AP31.SSID: 'Red Hat Guest'
AP31.BSSID: 00:25:84:95:78:04
AP31.MODE: Infrastructure
AP31.FREQ: 2437 MHz
AP31.RATE: 54 MB/s
AP31.SIGNAL: 64
AP31.SECURITY: WPA2
AP31.ACTIVE: no
AP32.SSID: 'madero-e34'
AP32.BSSID: 00:242:09:BF:93
AP32.MODE: Infrastructure
AP32.FREQ: 2462 MHz
AP32.RATE: 54 MB/s
AP32.SIGNAL: 82
AP32.SECURITY: WPA2
AP32.ACTIVE: no
AP33.SSID: 'Red Hat'
AP33.BSSID: 00:25:84:95:78:03
AP33.MODE: Infrastructure
AP33.FREQ: 2437 MHz
AP33.RATE: 54 MB/s
AP33.SIGNAL: 72
AP33.SECURITY: WPA2 Enterprise
AP33.ACTIVE: no
AP34.SSID: 'RH_WLAN_TRUST'
AP34.BSSID: 00:26:0B:16:34:51
AP34.MODE: Infrastructure
AP34.FREQ: 2412 MHz
AP34.RATE: 54 MB/s
AP34.SIGNAL: 80
AP34.SECURITY: WPA2 Enterprise
AP34.ACTIVE: no
AP35.SSID: 'Red Hat Guest'
AP35.BSSID: 00:26:0B:16:34:54
AP35.MODE: Infrastructure
AP35.FREQ: 2412 MHz
AP35.RATE: 54 MB/s
AP35.SIGNAL: 100
AP35.SECURITY: WPA2
AP35.ACTIVE: yes
AP36.SSID: 'Red Hat'
AP36.BSSID: 00:26:0B:16:34:53
AP36.MODE: Infrastructure
AP36.FREQ: 2412 MHz
AP36.RATE: 54 MB/s
AP36.SIGNAL: 80
AP36.SECURITY: WPA2 Enterprise
AP36.ACTIVE: no
IP4-SETTINGS.ADDRESS: 10.192.53.204
IP4-SETTINGS.PREFIX: 22 (255.255.252.0)
IP4-SETTINGS.GATEWAY: 10.192.55.254
IP4-DNS1.DNS: 10.192.20.245
IP4-DNS2.DNS: 10.192.206.245
IP4-DNS3.DNS: 4.2.2.2


--
================================================== ======================
Ian Pilcher arequipeno@gmail.com
"If you're going to shift my paradigm ... at least buy me dinner first."
================================================== ======================

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 07-15-2011, 08:58 PM
Tom H
 
Default NM_CONTROLLED=no not working

2011/7/15 Ian Pilcher <arequipeno@gmail.com>:
> On 07/15/2011 05:08 PM, Genes MailLists wrote:
>>
>> Can you confirm (iwconfig) that the device is indeed called wlan0?
>
> [ipilcher@localhost ~]$ cat /etc/sysconfig/network-scripts/ifcfg-wlan0
> DEVICE=wlan0
> TYPE=Wireless
> HWADDR=00:23:14:12:C1:38
> NM_CONTROLLED=no

Does NM ignore it if you add "ONBOOT=yes"? (Or "ONBOOT=no" if you want
to bring it up manually.)
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 07-15-2011, 11:10 PM
Ian Pilcher
 
Default NM_CONTROLLED=no not working

On 07/15/2011 05:58 PM, Tom H wrote:
> Does NM ignore it if you add "ONBOOT=yes"? (Or "ONBOOT=no" if you want
> to bring it up manually.)

Nope. (I actually had ONBOOT=no in there. I took it out in hopes that
would help.)

--
================================================== ======================
Ian Pilcher arequipeno@gmail.com
"If you're going to shift my paradigm ... at least buy me dinner first."
================================================== ======================

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 

Thread Tools




All times are GMT. The time now is 04:30 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org