Re: networkmanager-list Digest, Vol 75, Issue 35



Hi,
   you will add
   [root localhost ~]# nm-tool ??
    and will send details.

Thanks
khateeb

--- On Thu, 30/12/10, networkmanager-list-request gnome org <networkmanager-list-request gnome org> wrote:

> From: networkmanager-list-request gnome org <networkmanager-list-request gnome org>
> Subject: networkmanager-list Digest, Vol 75, Issue 35
> To: networkmanager-list gnome org
> Date: Thursday, 30 December, 2010, 5:30 PM
> Send networkmanager-list mailing list
> submissions to
>     networkmanager-list gnome org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>     http://mail.gnome.org/mailman/listinfo/networkmanager-list
> or, via email, send a message with subject or body 'help'
> to
>     networkmanager-list-request gnome org
> 
> You can reach the person managing the list at
>     networkmanager-list-owner gnome org
> 
> When replying, please edit your Subject line so it is more
> specific
> than "Re: Contents of networkmanager-list digest..."
> 
> 
> Today's Topics:
> 
>    1. Not choosing wired first on boot (sean
> darcy)
>    2. "deconfiguring network interfaces"
> kills wireless on NetMan?
>       (Alan White)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Wed, 29 Dec 2010 12:52:03 -0500
> From: sean darcy <seandarcy2 gmail com>
> To: networkmanager-list gnome org
> Subject: Not choosing wired first on boot
> Message-ID: <iffsg4$u4f$1 dough gmane org>
> Content-Type: text/plain; charset=ISO-8859-1;
> format=flowed
> 
> I have NetworkManager-0.8.1-10.git20100831.fc14.i686 on a
> Fedora 14 
> laptop. It's running as a server, init level 3.
> 
> I've vnc'd into the server and checked all the "Allow all
> users" boxes 
> in the applet. (Is there any way to do this without using
> X?) Now NM 
> starts on boot, but chooses the wireless connection, not
> the wired. I 
> have ifdown'd the wireless and ifup'd eth0. On reboot still
> connects to 
> wireless.
> 
> The wireless is meant to serve as a backup. If I go to X,
> NM always 
> chooses the wired connection. How can I get NM to prefer
> wired at level 3?
> 
> sean
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Wed, 29 Dec 2010 16:16:40 -0700
> From: Alan White <awhite0006 gmail com>
> To: networkmanager-list gnome org
> Subject: "deconfiguring network interfaces" kills wireless
> on NetMan?
> Message-ID: <4D1BC158 2010004 gmail com>
> Content-Type: text/plain; charset="iso-8859-1";
> Format="flowed"
> 
> It is my current belief that the message seen on shutdown
> (HP G60, 
> Ubuntu 10.10.1, Atheros 5K) that Network Manager is
> deconfiguring 
> network interfaces is part of the issue with wireless no
> longer working 
> with Network Manager. In any event, I'd like to be able to
> again use 
> this laptop with wireless! Soon! Thanks.
> 
> Is there a replacement for NetworkManager on Ubuntu that
> allows wireless 
> to work again? It works great under Windows Vista Home
> Premium on the 
> same laptop...
> 
> ============================================
> 
> Timothy Murphy  wrote in response to James J
> Catchpole:
> 
> I'm no expert, but the 3 things I try when NM doesn't work
> (not an infrequent occurrence):
> 
> 1. Run "sudo iwlist scan".
> If that sees something then the problem is certainly with
> the NM setup.
> 
> MY RESULT:
> awhite author:~$ sudo iwlist scan
> [sudo] password for awhite:
> lo        Interface doesn't support
> scanning.
> 
> eth0      Interface doesn't support
> scanning.
> 
> wlan0     Interface doesn't support
> scanning : Network is down
> 
> wlan1     Interface doesn't support
> scanning : Network is down
> 
> 
> 
> 2. Try the network service instead of NM;
>      sudo service NetworkManager stop
> 
> MY RESULT:
> awhite author:~$ sudo service NetworkManager stop
> NetworkManager: unrecognized service
> 
> So I thought I'd try this also:
> 
> awhite author:~$ sudo service NetworkManager restart
> NetworkManager: unrecognized service
> 
> 
>      sudo service network restart
> 
> MY RESULT:
> awhite author:~$ sudo service network restart
> network: unrecognized service
> 
> 
> 3. Check that the entry in
> /etc/sysconfig/network-scripts/ifcfg-wlan0
> is reasonably accurate.
> 
> MY RESULT:
> vi /etc/sysconfig/network-scripts/ifcfg-wlan0
> "/etc/sysconfig/network-scripts/ifcfg-wlan0" [New
> DIRECTORY]
> 
> 
> 4. Check /var/log/messages (I pulled out a few but there
> are MANY messages)
> 
> MY RESULT:
> Dec 26 21:56:14 author kernel:
> [   14.984775] ath5k 0000:07:00.0: PCI 
> INT A -> Link[Z012] -> GSI 23 (level, low) -> IRQ
> 23
> Dec 26 21:56:14 author kernel:
> [   14.984866] ath5k 0000:07:00.0: 
> registered as 'phy0'
> 
> Dec 26 21:56:14 author kernel:
> [   15.495926] ath5k phy0: Atheros AR2425 
> chip found (MAC: 0xe2, PHY: 0x70)
> Dec 26 21:56:14 author kernel:
> [   15.519317] usbcore: registered new 
> interface driver rt2500usb
> 
> Dec 26 21:56:14 author kernel:
> [   16.877108] usbcore: registered new 
> interface driver rt73usb
> Dec 26 21:56:14 author kernel:
> [   17.017750] eth0: no link during 
> initialization.
> Dec 26 21:56:14 author kernel:
> [   17.018424] ADDRCONF(NETDEV_UP): eth0: 
> link is not ready
> Dec 26 21:56:15 author kernel:
> [   17.611781] ppdev: user-space parallel 
> port driver
> Dec 26 21:56:19 author kernel:
> [   21.990031] CPUFREQ: Per core ondemand 
> sysfs interface is deprecated - up_threshold
> Dec 26 21:57:22 author kernel:
> [   84.991868] eth0: link up.
> Dec 26 21:57:22 author kernel:
> [   84.992560] ADDRCONF(NETDEV_CHANGE): 
> eth0: link becomes ready
> 
> 
> ADDITIONALLY:
> $ ifconfig wlan0 (nm-applet reports this as Atheros AR5001
> Wireless 
> Network Adapter, "device not ready")
> wlan0     Link encap:Ethernet 
> HWaddr 00:24:2c:6e:54:a2
>            BROADCAST
> MULTICAST  MTU:1500  Metric:1
>            RX packets:0
> errors:0 dropped:0 overruns:0 frame:0
>            TX packets:0
> errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0
> txqueuelen:1000
>            RX bytes:0
> (0.0 B)  TX bytes:0 (0.0 B)
> 
> $ ifconfig wlan1 (nm-applet reports this as Ralink 802.11
> bg WLAN, 
> "device not ready")
> wlan1     Link encap:Ethernet 
> HWaddr 00:0e:2e:86:80:68
>            BROADCAST
> MULTICAST  MTU:1500  Metric:1
>            RX packets:0
> errors:0 dropped:0 overruns:0 frame:0
>            TX packets:0
> errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0
> txqueuelen:1000
>            RX bytes:0
> (0.0 B)  TX bytes:0 (0.0 B)
> 
> -- 
> Alan White
> awhite0006 gmail com
> 
> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mail.gnome.org/archives/networkmanager-list/attachments/20101229/a4f576a0/attachment.html>
> 
> ------------------------------
> 
> _______________________________________________
> networkmanager-list mailing list
> networkmanager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
> 
> 
> End of networkmanager-list Digest, Vol 75, Issue 35
> ***************************************************
> 




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]