Are there any limitations to connecting to a WPA2 Enterprise network with PEAP authentication on linux? Here at my university, on any major linux distro, I can only connect to the secure wifi 50% of the time and when I do successfully connect, it get booted off in a few minutes. At home I can connect to my WEP internet network easily.
Using Windows I can connect to my home WEP network and my university's WPA2 Enterprise network easily. Note: I work at the computing department here at my university, so I know that there is no anti-Linux mentaility which resticts access to Linux-based distros.)
I have a Toshiba NB300 netbook that has an Atheros AR9285 wireless chipset and is running Ubuntu 10.04 Lucid Lynx. At my University there is a FreeRadius authenticated wireless network (called "UCC") that I would like to connect to. Using NetworkManager I have created an automatic profile called "Auto UCC" that contains my user details for the connection. When attempting to connect to the network, the NetworkManager icon spins for a couple of minutes and then presents me with the authentication dialog. If I re-enter my details (and disable the CA cert prompt), it repeats the process seemingly infinitely (spin-spin-spin, auth box) Attached is a copy of the syslog from first attempting to connect to stopping the connection attempts. The wireless card's 'lspci' line is
im located in Sudan which is under usa empargo, means some software is restricted in my country. My company which has 5000 emloyee os going to build their own webserver which will hold alot of apps which is compatible with linux i didn't trust M$ windows specially on web, so ive to use linux do u recommend any other release other than opensuse coz o can get free update and patches.
I have installed the Suse Enterprise server 11 SP1 on my laptop. I have the atheros AR8132 network card, and it seams the suse is detecting correctly, but i can't start the network up. He returns an erros saying that the eth0 is not supported by suse, or kernel, i must check to be sure.
I can connect to the internet through wifi, but I cannot connect to anything on my network. I have a printer and a NAS, so I would really like for this to work again. I have a dell laptop with a Broadcom card.
I am using Squeeze and all appears OK at first... I have a DHCP lease, PING to router works, apache servering fine in and outside the network, Epiphany seems to connects to default debian.org only, BUT I cannot connect to any other websites and apt will not connect to any servers. I installed once, tried to fix problem, gave up and reinstalled and still have the same problem.
I unistalled Network Manager thinking that was the problem, but still the same issue. Is there a default firewall blocking certain connections or am I missing something I'm supposed to know about? I installed some non-free firmware in the beginning of install and all worked... and I connected fine when downloading packages during install.
I recently fixed an annoying problem and I thought it would be nice to share my solution here. The problem was that after a cycle of suspend/resume, Network Manager would only auto-connect to the same network as it was previously connected to. So, for example, if I suspended my laptop at home, and then I went to school and resumed it, it would try to connect to the home network, and then just give up. It would not connect to the school network unless I explicitly told it to.irst, I'll describe the fix. If you're having this problem, you can this. Copy the following:
I have used ubuntu in the past but had a lot of hardware issues with it and unfortunately moved back to windows (( BUT i have tried Ubuntu again and all seems to work great except wifi My wifi connection is sort of working because when i run SUDO IWLIST SCAN it does pull up all available networks. But in the network manager icon on the panel i left click but i see no networks and can't connect to anything. I WOULD LOVE TO keep Ubuntu and use it permanently but I must get wifi working or else this won't be possible.
I recently put Linux on a Thinkpad T40 I got. The wireless card works out of the box--I can see nearby networks. However, I can't connect to mine. network-manager would try (spin spin spin), fail, ask for the password, and then go back to the beginning and repeat indefinitely. This happened to me on a different computer, and on that one all I had to do was use wicd instead of network-manager. So I installed wicd, but it's not working either--it hangs at "Obtaining IP address".
I've found many, many threads with people who had the same problem, but none of their fixed worked for me.
I also tried to get wifi going manually, using this guide, but that didn't work.
Yhe only ptoblem was that he had forgotten the password to his network. This was really anoying and has happened before sp yesterday i decided to install some kind of WEP cracking tool so that it would not happen anymore.. After using sometime without getting anything to work i found this tutorial: [URL]
and started following it. i only got to the point where he has updated his computer using update manager and is about to patch his wificard. Then i noticed that the network manager for gnome was gone and the virtualbox logo in my top panel was changed to a red circle with a line running through it. I have tried to download network manager from another computer and installing it on my laptop but it needs internet to install. Then i tried to connect to my local network using terminal that did't work either i also tried connecting using a cable but had no luck connecting. The command iwconfig gives me:
After installing 11.4, I need to type in the command to update the firmware for a broadcom wifi adapter. Then I needed to reboot, twice, before the system knew to use the adapter (where the adapter wifi light goes from orange to blue).
Then I needed to add my wireless network and type in my key. But the key does not take. If I click on my wireless network icon, it just re-asks for the key and does not connect nor give any other message. Network icon continues to display no connection.
So I need to reboot again.
When the system starts again, the adapter is blue, I click on the icon for my wifi network and it connects without asking for my key and I can then set to start my wifi by default.
All settings are correct as far as i can tell. The wep key works on all my windows boxes. When i have connect automatically enabled it never tries to connect. if I go to edit it it pops kde wallet up i put in credentials. wallet goes away then nothing happens. if i double click connection to my router also nothing happens. I have the wep key in there and i even made it visible to make sure.
I am using OpenSuse 11.3 and Network Manager is giving me a headache by not connecting to WEP based wi-fi network.It works in a wi-fi at my office while at my home, it shows / detects the network but keeps asking me over and over.
I installed OpenSuSE 11.3. The only "extra" package I put in after the install was VirtualBox-ose. The firewall is disabled. I gave the machine a static IP address. I can get to the Internet from the machine. I enabled sshd to start on boot with "chkconfig sshd on" and also verified the service is running on the machine. I can ssh user@localhost from the machine as well.
When I try to connect to SSH from another machine, I get a connection refused. I verify that the firewall is down. I also try to get to VNC -- same problem: Connection refused. I ping the machine for fun. If I try to SSH again, it sometimes gives me a logon? I would check the server logs for the connection refused, but I wouldn't know where to look. I started in /var/log/messages, but nothing seemed to jump out there. I also find it strange because I can RDP to a windows guest running under VirtualBox. The Windows guest uses Bridged Network and DHCP.
I also find it interesting that I sometimes type a "ping google.com" from the 11.3 box and it will just hang - no output. Then I open firefox and get to the internet. All of a sudden, ping starts to give output. Could this be a neetwork card issue? A configuration issue? I don't know where to start.
I am relatively new at Linux and am having some problems with an install of openSUSE 11.2. I installed 11.2 on my Thinkpad X31 dual boot with WinXP. It seems to work very well except the network. I looked up swerdna's instructions on setting network cards up. I used YaST to try and set the system up as described in swerdna's instructions. Everything looks fine my network card and wireless card show up in the overview settings screen and everything sets up fine. But when I exit YaST the network doest show up no icon in the system tray and it doesn't even try to connect.
I did go into hardware to see if it was identifying my hardware and my network card shows up as "Thinkpad R40" and the wireless shows up as Cisco Aironet Wireless 802.11b. As far as I know this is correct. I have tried three other distro's and this one has gotten the closest to working so far.
the thing is that I cant use Network Manager to connect to Internet, because it simply do not connect. The connection, although, awailable throught yast when i choose "traditional method with ifup", so everything is just fine, but if i need to reconnect, i have to reboot. How do I setup a !working! connection through Network Manager, or maybe i do not do something properly.
I just installed opensuse 11.4 and i'm not being able to connect to my wireless lan. It recognizes my network, but when I click "ok" after typing the password it is like I had done nothing, no connection is set at all.I guess it is probably some configuration stuff since my notebook recognizes all available wireless networks. Sorry about the lack of details, but that is all I got.
i've installed openSuse 11.2 on my laptop (dell studio 15).Today at work i tried to connect to the wireless network, but i couldn't. First, the network card wasn't being recognized, but after a long time trying i was able to set it up, for this i used this command:
Code: zypper in broadcom-wl broadcom-wl-kmp-desktop So now, the networkmanager detects all the networks around, but i cannot (or i don't know
I'm unable to connect to a particular home wireless network under Fedora 9, although I can connect to it using WinXP on the same machine. My Fedora installation is able to connect to my college's unsecured wireless network, so it's not a driver issue I think.It seems to be an authorisation issue, as I'll describe below, but there's one other thing that's bothering me. The SSID for the network I have problems with is for some reason not listed in Network Manager's drop-down list, nor is it in the output of iwlist wlan0 scan. But I'm pretty sure it's not a "hidden" network - I don't know exactly how those work, but I helped the owner of the wifi network in setting it up, and don't remember doing anything that would make it hidden. As far as I can remember, Windows found the network automatically without having to be told the SSID. What's the best way to confirm whether it's a hidden network or not?
Anyway, I try to connect by selecting connect to other wireless network in Network Manager, and entering the SSID. As far as I can tell from the error messages below, the machine does contact the network and attempt to connect, but I'm not authorising myself properly. That may be a completely wrong diagnosis, but hopefully someone can see from the below info whether it's correct or not.I'm not sure which option to use for "Wireless Security": at the time we set up the network, it gave us a Hex WEP key of 26 characters, which is 104 bits. But none of the options in Network Manager's list match that. Here are the options it has, and the error message I get with each one:None - if I select this, it fails to connect, with no error message. WEP 128-bit passphrase - if I select this and attempt to use my 26-character WEP key, it brings up a new dialog, saying "Passwords or encryption keys are required to access the wireless network [SSID]." It has a drop-down box labelled "Wireless Security", but this time the only option is "None", and the connect button is disabled, I can only click cancel. WEP 40/128-bit hex - as above. WEP 40/128-bit ASCII - The connect button is disabled when I try to use the WEP key, as the string is too long. Despite the fact that it says 40/128-bit, it actually accepts 5 and 13-character strings (40 or 104-bit). Since I've got a 104-bit hex key, I tried converting it to ASCII, but it consists of mostly unprintable characters, so I'm not sure there's any way to actually enter it into the textfield. I might have done something wrong here, so I've put my code below to see if anyone can point out a mistake. LEAP - requires a username, not applicable here I think. Windows doesn't need one, and we don't have one from when we set the network up.Dynamic WEP (802.1x) - requires username, private key and various other things, all N/A WPA & WPA2 Personal - Brings up a dialog with the same text as for "128-bit passphrase", but this time "WPA & WPA2 Personal" is the only option in the drop-down list, instead of "None". It asks for a password, so I just enter the hex key again - now it asks for the password for the Gnome Default Keyring, which I don't think I've ever set up. Don't know if I can go any further with that, but my understanding is that since we were given a WEP key when we set up the network, WPA will be N/A.WPA & WPA2 Enterprise - as Dynamic WEP. N/A.Hopefully that's enough info that someone can help diagnose the problem. Some of the behaviour of Network Manager described above doesn't make sense to me, and I'm wondering if it's buggy.