at start, knetworkmanager detect wireless network, but doesn't automatically connect - I have to restart it to make it work properly. Instead, it gives that error:
I clicked "Network Settings", and I found that the ip address was wrong, which is "192.168.1.10/24", and netmask field is empty, so I modifed the configuration file located in /etc/sysconfig/network, named ifcfg-wlan0, added one line(NETMASK= '255.255.255.0'), saved it and reboot the system. After rebooting the system, I still found the ip address is wrong and netmask field is empty, so I have to use ifup command to activate my card manually every time the system starts.
Since my update to OpenSuse 11.2 knetworkmanager refuses to connect to WEP enabled networks (worked fine with knetworkmanager 11.1). I am sure that I use the correct password and I tried on 3 different networks. The manager is connecting to open networks and WAP protected networks without problems. I saw on other forums that there were similar problems with previous versions of networkmanager. But I could not find a solution for my problem.
Even though I am not new to Suse, I am still very inexperienced, especially when it comes to wireless. I am running Suse Linux 11.3 and I am having problems connecting to my wireless. My network controller is a RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01). I am recieving a signal from my wireless router, however when I try to connect to my ESSID via KnetworkManager It asks for a WEP key. After entering the key, Knetnetwork manager will try to connect for a minute or so and then it will ask for my WEP key again. It keeps repeating this cycle without ceasing. How to configure the WEP so that Knetwork manager will connect or a way around WEP.
My first problem is that when I open KNetworkManager the wireless tab is desibled,I don't know why! My laptop is HP pavilion dv6-1245DX. How to get connected to my wireless router?
I have built 11.2 on several laptops and knetwork manager startup for wireless is not consistent. I can't figure it out. Sometimes the options "Create Network Connection" and "enable wireless" are greyed out. Other times they are fine. What is the secret to getting the options to appear in my window tray all the time? I always select knetwork manager as the default when I do a clean build.
I have an open WEP wireless internet connection with a security key. KNetworkManager can never obtain an IP address from my wireless router, but I know that the router works because Windows can connect correctly and Ubuntu's NetworkManager can connection correctly. Does anyone know what is happening? KNetworkManager just asks for my security again and again and again after it fails to connect.
I have ASUS Laptop A6Rseries was running XP untill I installed Linux 9.10. Now i am having problem connecting to my wireless network. I am using Belkin router what works fine with XP, Vista and Windovs 7. Here is some information what I found
lspci 00:00.0 Host bridge: ATI Technologies Inc Device 5a31 (rev 01) 00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge 00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80)
On Opensuse 11.2, I would like to connect my ipod touch to a wireless ad-hoc network of my laptop. I have no wireless WIFI-router at home, so I have to use the laptop as a router to the internet. I know I have to enter a static IP adres and my router's address, but where ? I haven't found any place under network tools to do this, only saw some fields with SSID's and MAC addresses to fill in.
Each time I boot up my laptop, I have to manually connect to my wireless network. When I ran Ubuntu virtually from Windows 7, it found the connection automatically. Now I have a dual partition of W7 and Ubuntu and it won't auto connect. How can I make it so?
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.
[Code].....
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'm moving from other distros. and I'm currently loving openSUSE and I'm probably going to stick with it for a long time.I have already googled for this, but I found no solution, but I figured this should be a common problem... Does google searches inside this forum?Now... for my problem, whenever I hibernate (suspend to disk) or sleep (suspend to ram) I can't resume my wireless connection nor connect to another.I don't know if this is an issue if I use cables, because I simply don't with my netbook:The hardware in question is an ASUS 1005HA eee pc, running openSUSE version is 11.3 fully updated. Didn't mess with wireless connections, nor kernel or hibernate settings
One of the biggest issues i have at the moment is that my network based plasmoids on my KDE desktop load before my wireless network connection is established, so i'm thinking it would be best to start up the wireless connection at boot time. On previous distro's, I did this with netcfg but I can't seem to figure out how to do so in OpenSUSE 11.2. Is this the best way to manage this issue or is it possible to set a delay before the plasmoids load up?
I'm configuring a computer for someone and I don't know the wireless network they will be using. (They are not technical.) I've setup networking to use NetworkManager. It works just fine.However, Knetworkmanager won't startup at boot/login. Therefore, the network doesn't startup automatically. I have to click on the icon in the menu to start it.That works well, but it should be configurable to startup automatically.I've searched this forum for answers and don't find any good ones. It seems there isn't an answer or there is a bug in KDE 4.x. (I'm using KDE 4.3.x)
kde knetworkmanager is not starting on startup.i am starting this manually every time on login to connect to network..how to make it start automatically?
I just reinstalled OpenSUSE 11.3 GENOME on my computer (Compaq Armada E500 w/512 MB RAM, 30GB HD, and Linksys WPG54v2 wireless card). After futzing around for several hours on two different evenings, I got it working all by myself! The only thing is,ow I have to manually connect to my wireless network every time,which gives me a a great sense of accomplishment. I start the computermber having to edit a script somewhere to make it connect automatically on system startup, but I can't remember what it is I'm supposed to edit or how I'm supposed to edit it
Just moved over to openSUSE 11.4 (KDE) from Ubuntu, yesterday. However, I'm having some trouble with my wireless connection.
I have a wireless network with a hidden SSID and WPA2-PSK security. I entered all the nescery information into the KDE network manager, but it couldn't find my network. So I ran the usual command:
Code: su -c iwlist wlan0 scanning essid [My SSID]
At which point, the network manager immediately found, and connected to, the network. However, it seems that I have to run this command (as root) each time I log in, before my laptop will connect to the network. The network manager has no problem find the plethora of unsecured networks as well as those that are secure, but broadcast their SSID.
Using tips provided in the "Sticky" posts, I have identified my wireless device -- BCM4322 -- and installed the necessary firmware and drivers. The device appears in Network Manager until system reboot, at which time the "ssd" driver module is loaded instead. After each boot I must execute the following commands to remove ssd and load the Broadcom driver:
rmmod ssb modprobe lib80211 modprobe wl
The Broadcom README file provides directions to load the correct module automatically, but the commands appear to be incompatible with openSUSE 11.4. I'm happy to provide additional detail if needed
I am using a fully up to date openSUSE 11.3 and today, I decided to upgrade my KDE 4.4.4 to Factory. The update went without a hitch, everything continued to work, including all of the items in my workspace.So now I am running KDE 4.4.95 and it looks nice. I like the new System Settings where the advanced tab is gone and everything is presented in a single window.
The only snag I have hit so far, is that Knetworkmanager no longer displays the network that I am connected to when I right click its icon in the tray. The screenshot may make clear what I am talking about.I am currently connected via a wireless network, which nm-tool confirms. However, it is not shown in the Knetworkmanager menu.
i'm experiencing some weird behaviour: I have a server running ubuntu 10.04 and two Apple laptops in my home network. Sometimes after booting up the server doesn't connect to the wireless network, but instead "kills" the connection of the laptops. (The network then isn't available for about two minutes - it's showing but it can't connect) On the server the network interface is up, but not associated.
Sometimes the interface isn't configured properly (iwconfig isn't showing an entry) - but in this case the behaviour obviously isn't showing. some information about my system:
Ubuntu Version: Server 10.04x64 Wireless Card: Netgear WG311v3 with marvell chipset Driver: ndiswrapper+mrv8335x64
I have a Toshiba Satellite L550 laptop with Suse 11.3 dual booting with Windows 7. Windows can detect the built in wireless card but not Suse, what can I do to get the wireless recognized in Suse.
Since two week the knetworkmanager needs 3 minutes after login to start and connect. On an other computer (x86) it works fine. What could be the reason for this? I use opensuse 11.3 x64 and yes i need the network manager. Ifup isn't practicable for me.I have read in some thread to start the networkmanager at boot time and as root, but i don't think this is necessary.
on kde4 with knetworkmanager I cannot get past the wep security key on my home router. Every other wlan works, ethernet works, settings are definitely correct because it works with windows, other computers.And on the same computer even with gnome networkmanager! Also it used to work fine earlier. Behavior the same with different users including root, regardless of using kwallet or not. Networkamanager tries to connect and after one or two minutes throws the setting window back at me. I uninstalled and re-installed and deleted all related files I could think of. I even tried a complete fresh installation of opensuse only keeping the /home partition, so the problem must be lying there I guess. But then why all users?
PS opensuse 11.2 kde networkmanager 0.9.svn1043876-1.1.1
I accidentally powered down in the middle of a session by removing the wrong battery from my laptop (a Motion Computing tablet), and ever since that happened knetworkmanager crashes with a segmentation fault on startup. I have uninstalled it and then reinstalled it from an openSuse 11.4 DVD I made a few months ago, but it still crashes on startup. Ifup says it connects to the wifi (Wayport Access @ McDonalds) I have available, but browsers don't reach the internet while Ifup is connected, so I can't sign on and get access to anything more recent. Is there some file I ought to delete,or some other software I ought to delete and reinstall?
Have an issue with my wireless.It sometimes doesn't connect to my wireless. And sometimes when it does it gives me an invalid IP address.I have a lenovo SL400 Laptop.Intel 802.11agn wireless is my adaptor. And I have OpenSuse 11.4 with gnome. I works fine if I give it a static IP Address but that will create an issue with other computers on the network.Is my desktop environment (GNOME) or is my Wireless adpator not compatible with opensuse.
I just don't get it? I've attempted multiple times to get the knetworkmanager to connect to an unencrypted network, yet it keeps asking for a wep key. However the networkmanager in the Gnome version connects to unencrypted networks just fine. Why won't knetwork manager do the same?