Ubuntu Networking :: Wireless Without NetworkManager Applet?
Dec 28, 2010
Is there a way of wireless networking without using the Gnome NetworkManager Applet? I want to connect to the Internet using a USB 3G modem and connect to wifi without knowing all of the details of every network.Network manager is pretty good but there seems to be no way of using it without starting an X session and it doesn't play nice with any other networking tool and reminds me too much of a Microsoft application.
Is there any easy way to replace the default Gnome NetworkManager used by Ubuntu with Mandriva Net-Applet? Although I prefer Ubuntu, overall, I have had better luck with video streaming, browser speed, and consistency when using Mandriva (with iPV6 disabled).
after fiddling around with compiz-fusion and KDE, my network suddenly disappeared. I looked in the package manager and apparently I don't have the gnome applet for networkmanager...but everything else I seem to have (the git version not svc or w/e) Anyone know if installing the applet will let me choose my wireless network and connect to it? Right now I think so, but what I have to do is boot into windows, find the package on the web and download it, then boot into fedora and install it
where I can find the fedora 10 networkmanager-gnome package (git version for x86_64)? I looked around and found the svc version and a git version for i386, but my OS is x86_64 and I couldn't find any git versions of it for 64-bit fedora's. btw, I have no idea what git and svc mean, but when I tried to install the svc version, it told me I had to install svc versions for all the other networkmanager packages...
My networking seems to be OK but when any changes are made the NetworkManager Applet 0.7.996 (I think) in the panel pops up a small window ~ 300*80 pixels which displays some faint coloured lines and dotted lines where, presumably, there should be a message of some form. How can I configure it to get the message?
I have a FC10 installation with GNOME and NetworkManager and a wireless card. Everything works ok. However, when I try and setup gdm to do autologon I get the NetworkManager applet asking for the password for the gnome-keyring to get the wireless details. Since I want to use this machine as a sever this is unacceptable as I won't be around to type in the password. I tried the solution at [URL] but this does not work. I still get the password being requested and the keyring password is the same as the logon password. Can anyone say if there is a workaround that works to get the NetworkManager to be able to read the gnome keyring without having to prompt me for it.
The auto connect feature of NetworkManager Applet (version 0.7.997) isn't working on my system. If the WiFi connection dies, Network Manager doesn't detect that the connection has been lost and try to reestablish the connection. I have to manually click on the WiFi hotspot to reestablish the connection. This appears to be the case both while the computer is running and when I first boot it up (i.e. when booting, if the first attempt at establishing a WiFi connection doesn't succeed, Network Manager doesn't retry or try another hotspot).Is this "normal" behavior for Network Manager? If not, does anyone know a fix? Here's some more info about my system:
I just upgraded (as a fresh install) to Fedora 13. In so doing I kept the old /home partition. My NetwokrManager Applet is missing from the top bar. But if I login instead as a different user, then it is there. When I did the install, I had to create a (new) user as part of the process. The old passwd file had two users, one called admin, and the other myself. I logged in initially as the new user, and created the admin user keeping the same home directory, user ID and group ID. I then logged out, logged in again as admin, and removed the new user. I then added myself as a user keeping the same home directory, and user and group IDs.. For some reason admin has the applet but I don't. I also don't see how to add it except as a custom laucher using nm-applet, and that didn't seem to work.
I am using gnome's nm-applet as the client for NetworkManager. However, it seems that nm-applet will not save network passwords, so I have to retype the password on each connection. I already have gnome-keyring installed, so I'm not sure what the issue could be. I read online somewhere that secrets are retrieved through polkit or something, but I am completely unfamiliar with polkit and such.
I have a typical 'linksys' style home wireless router (whose IP is 192.168.0.1) .
If I use DHCP, everything works fine:
However, if I try to give myself a static IP,
(I also never understood why the DNS server should not be the real dns server address (some external ip) rather than the router's address? but that is what gets set automatically when using DHCP)
So using manual, it connects, but then the internet doesn't work. The only difference I see when I go to "connection information" when connected with dhcp vs manual is in dhcp mode there is a "default route: 192.168.0.1". Is that the problem? How do I set this "default route" / what is it?
The card is recognized by System--admin--network as the correct card (BCM43XG) and assigned eth1. However, NetworkManager shows no wireless network. I have a great signal on the same machine if I boot into a Windows partition.
I have just installed Fedora 13 on my Lenovo Ideapad S12 (company laptop, evaluating Fedora for companywide use on all laptops) and a facing a weird problem with KDE4 and NetworkManager / knetworkmanager. The laptops wifi card is a Broadcom BCM4312 and I have successfully extracted the necessary b43 firmware. The b43 module loads on boot and the wireless card is activated and ready to use. However, NetworkManager doesn't seem to agree and has wireless disabled by default every time I reboot or even logout / login. I have to check the box manually after which it automatically connects to my wifi network at home.
Any idea where I can check that box automatically on boot?
I just got my Airlink AWLH5025 to connect using the instructions provided by Gentoo Wiki's article on Wireless Networking. I'd like to use NetworkManager, but I'm running into problems - launching it kills my connection, and even though it finds my network it won't connect to it.
Just installed OpenSUSE 11.2 and I have to say it feels great.Only gripe I currently have is the NetworkManager that is starting up very slowly. When I have logged into KDE KNetworkManager applet says that NetworkManager is not running and hence I have no network connection. This is fixed if I start NetworkManager (as root) or just wait a couple of minutes. I have one ethernet interface only, no wireless
I'm having problems getting two wlan cards to work under Networkmanager with F12. I have an old server that I wanted to move, so thought I'd get a USB wlan device for it. before setting up the server, I thought I'd try the USB (an Edimax EW-7711USn - Ralink 2870) on my laptop first. My laptop has an inbuilt ipw2200 card that works fine under NM.
So I've down loaded the DPO_RT3370_LinuxSTA_V220.127.116.11_20100831.tgz file from Ralink, and built the driver (after changing the os/linux/config.mk file for the WPA supplicant settings). I also install the rt2870 firmware (from Ralink) in the /lib/firmware directory. I also blacklisted the rt2800usb driver to ensure that that didn't get loaded.
The problem I have is that I can now get both the ipw2200 device and the rt2870 devices 'working', but they both try to assume the same IP (I want fixed IP's and not DHCP for them) - what is the way to configure the 'devices' so that the rt2870 device is always given IP x and the ipw2200 given IP y?
I think my problem is really my lack of understanding where/how NM handles the files under the GUI config. I used to semi understand how the old network config tool set up it's files and where they were etc. But with NM I'm a bit lost as to how it equates the device with the network settings. Once I have the device working with the correct driver on my laptop, I'll look to apply the same settings on the server (which is then FC13 - but should be simpler as it doesn't have an existing wlan interface).
The symptom is that NetworkManager repeatedly ask for password to connect to my AP.My AP is secured with WPA-PKI. The problem even happens with Fedora 11 live cd if I'm not quickly configure wireless connection using NetworkManager right after Fedora completes booting up. It means if I promptly configure wireless connection, i'm still able to access Internet. Same thing happens for the first boot of Fedora from hdd. For the second boot or when I dont quickly configure wireless connection when system finished booting up, NetworkManger repeatedly asks for password for AP.
I did try several approaches posted in this forum but problem still persisted. Some of approaches I tried are:
I'm trying to get a wireless PC (PCMCIA?) card working under 10.04 desktop. It does not seem to be recognized by nm-applet and I cannot see any particular reason why. I have disabled the built in wireless (Intel 2200) in both BIOS and by blacklisting the appropriate module so there should be no interference from that. The card is a Linksys WPC300N V1. It has Power and Link/Act LEDs both of which remain dark.
Here's the information I have collected regarding the card:
I saw a comment about 'You need to have "managed=true" for NetworkManager to bring the interfaces up. in '/etc/NetworkManager/nm-system-settings.conf and did so but I see no change.
I understand that modules must be compiled to support network-manager but I would expect that to be the case with modules that ship with 10.04. I don't see any obvious indications for why this is not coming up with network-manager. Is there something I;m overlooking or something else I need to do?
A fresh installation of ubuntu 9.10 stopped my DSL internet connection. sudo pppoeconf solved the problem of net, but NetworkManager applet in panel now not working. it says wired networks, device not managed.
I'm not sure if I have two seperate issues or one inter-related issue. The Network Manager applet wasn't appearing in the tray, found out it wasn't installed. Installed, still didn't appear. Tried installing WiCd, WiCd did appear but couldn't find any networks. I had installed restricted drivers previous, decided it was worth another look. Found that Broadcom STA Wireless Driver wasn't installed. Tried to install, it said it couldn't and said I should review the var/log/jockey which is....excessively long.
Is there a way I can refresh the list of available wireless networks in the network manager applet? It works correctly when I've just booted but doesn't after I resume after suspending. There's just a message like "wireless networks not available".
I can assure you that the wi-fi is not disabled using a button (my laptop doesn't have such a button), "Fn" key combination or in any other way and the network doesn't go down when I need it.
I am having issues with wifi on my Lenovo X220. What has occurred is that the network applet in the notification bar no longer shows me any wireless network options. When I click on the applet, the drop down shows me: Wired network: disconnected (greyed out), VPN connections, Enable networking (checked), Connection information (greyed out), and Edit connections. Missing is Wireless connections. This occurred "out of the blue" in the middle of using the computer (i.e. NOT just after a reboot or new driver installation, etc.)
I have noted that:
1. Wired ethernet works just fine.
2. Wireless (wifi) works when I boot into Windows 7 or into a fresh Ubuntu USB Start up disk (implying that this is a software issue, not hardware).
3. The hardware led for wifi is OFF (whereas the Bluetooth light is on.) In Windows or using a fresh ubuntu from USB, this light turns on normally.
This may be irrelevant, but the issue started yesterday when I noticed that the trackpoint scrolling that I had enabled using gpointing-device-settings was not working. I ran that app and checked the settings, which were normal. I then reset the computer, and found the trackpoint was working just fine, but I had no wifi. A few resets later, the problem was not solved.
I'm running Squeeze and I'm looking 3 days now for a solution in some weird problem. The NetworkManager Applet shows that there isn't connection although I am connected. The icon has this small "x" and when mouseover it says "No network conncection". Moreover when left clicking it, it says
"Wired Network Device not managed"
While I was looking for the solution a came across this post by an Ubuntu developer who says:network-manager-applet displays the connectivity state of network-manager's managed interfaces not every interface. So the title "network manager says disconnected but is connected and working" is actually misleading. The interface is connected and working but not from network-manager's point of view since it is not managing the interface. Additionally, in Lucid now network-manager applet displays nothing now for non-managed interfaces so is less misleading. You can check to see whether or not an interface is managed by network-manager by using the command line too nm-tool. You'll see "State: unmanaged" for unmanaged interfaces.
I just got myself a Dell Inspiron 1440. And decided to install my favorite distro Debian. I got the installation to go with no issue and all seems to be working fine. However the wireless isn't working. NetworkManager doesnt even detect a wireless card. I followed the instructions here and installed the b43-fwcutter and then issued the modprobe b43 and modprobe b43legacy commands. Then I issued the iwconfig command and this was the output.
Also, I've been doing some research and found out about some file located /etc/udev/rules.d/70-persistent-net.rules. So I looked in mine and found out that only my eth0 is added.
I remember that I did configure my desktop PC for wired and wireless connections since openSUSE 11.2, 11.3 and 11.4. Currently I have openSUSE11.4 x86_64 KDE. Today I happen to notice that the icon for NetworkManager in the taskbar has been replaced with a red X. I discovered that Network Manager only shows VPN tab, whereas Wired and Wireless tabs are greyed out. The strange thing is I still have Internet connection with the CAT5 cable being plugged in. I can still configure wired and wireless connections via YAST but I cannot fix Network Manager settings.
I use network manager applet 0.7.1. I had set the automatic wireless connection to my my wireless network (WPA key secured). Recently, I get the following problem: At the automatic connection, I get the message: Network manager applet (/usr/bin/mn-applet) needs default keyering. As I don't know what it is to type it and then, deny or OK, it doesn't get connected to my wireless network.
I'm using OpenSuse 11.1 (but it applies also to 11.0) on a Dell XPS, NetworkManager and scpm to manage profiles. I configured wireless network without problems and all runs perfectly. The annoying problem is that the wireless connection doesn't start at boot. Also by clicking on the NetworkManager applet networks are not displayed
But, as soon as I launch network configuration from Yast without do anything other, magically the wireless network is recognized and the PC connects to it.
It seems that the network configuration from Yast activates NetworkManager to connect or it activates the interface or the hardware.
I'm finding the NetworkManager applet very confusing.When I start up at a new location I can use the "Connect to Other Network..." menu item to bring up the list of available networks, and I'd expect that by selecting one of these and clicking "Connect", then configuring and clicking OK, I'd get a connection. Instead the dialog just goes away and nothing else happens. Is something broken with NetworkManager, or am I misunderstanding how this is supposed to work?
By switching back and forth between NetworkManager and ifup I'm eventually able to establish a connection to a new access point, but it's been a painful process.I've also encountered a problem reported by others, where when my system fails to suspend/resume properly the /var/lib/NetworkManager/NetworkManager.state has NetworkingEnabled=false and I need to manually edit this before restarting networking... but that's a separate issue, and I can work around it with the manual edit (or just add a startup script to do this automatically).