Announcement

Collapse
No announcement yet.

wireless halts at 28% - router negotiation to blame

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    wireless halts at 28% - router negotiation to blame

    Hi folk,

    Reporting what I have found with wireless and Feisty.

    Been hit by Knetworkmanager halting at 28% when activating a wireless connection? Yeah, me too!

    Doing a little bit of playing has revealed this is very much a router negotiation issue (sadly, it's on Feisty's side). I have a perfectly good Netgear DG834 (version 1 on latest firmware) and nothing I do to the laptop (housing a Netgear WG511) will allow connection to it. Configured a Belkin54G as the access point and connected without problems.

    This explains why there are many who are reporting absolutely no problems with Knetworkmanager, and others wanting to pull their hair out. It's all down to Feisty's / the kernel's (in)ability to negotiate with routers. Maybe others who have had success could post their working combinations such that we could build a list of working stuff until they repair the wireless network negotiation bit?

    It also affects the ability to roam as some hotspots connect and others don't (and, yes, an airport gets exceptionally frustrating as the make of access point changes from one area of the terminal to another!).

    WEP both 40/64 and 128bit work too, however, WPA-PSK is decidedly broken. Workaround at present is clearly suggested (from all the posts where success has been reported) by operating WEP (yikes, nothing like opening yourself up to hacks! so please also put MAC access control in place).

    Finally: If someone from the (K)Ubuntu team does read this, please post IN BIG, BOLD LETTERS when you have repaired the faulty bits so that we can remove the negative bits of publicity such a wonderful operating system and suite of programs is getting.

    God bless,
    M.

    #2
    Re: wireless halts at 28% - router negotiation to blame

    I have the exact same router, firmware V1.01.00 and connect to it with my laptops built in wireless. Works fine for me so I'll write down the settings here. I'll assume you are using WPA encryption.

    I use WPA-PSK encryption on the router with static IP addresses.

    These are my knetworkmanger settings:
    My wireless device is eth01.
    Under the configure settings, I've manual selected, IP Address is whatever you assigned, eg 192.168.0.2
    Netmask is: 255.255.255.0
    Activate when computer starts is ticked.
    Wireless settings left blank.
    Under advanced settings, broadcast is set to 192.168.0.255
    Under routes tab: select eth01 (wireless device) and set the gateway to your routers address, eg 192.168.0.1
    Under the DNS tab, add DNS server: 192.168.0.1

    Now select the knetwork manager from the tray and select connect to other wireless network. Enter your routers ESSID, select use encryption, select WPA personal, enter your pasword , WPA1 and automatic.

    I had a problem when I rebooted that it couldn't find the network. I selected "Work in offline mode" from the options menu in knetworkmanger and then I re-enabled it. When I did this a dialog came up asking if I wanted to save my network password in kwallet. I selected save always and I left the kwallet password blank, otherwise you will be prompted for it every time you boot up!


    Hope this helps.

    Comment


      #3
      Re: wireless halts at 28% - router negotiation to blame

      This is by far the best description of how to setup WPA-PSK on kubuntu I have seen and I have searched a lot. But I am still not getting the settings to work with my router.

      The only difference I have seen so far is that I am not on eth01, I am on ra0 and that my router uses WPA-PSK TKIP.

      My Routes do not seem to stay persistant if I quit knetworkmanager and restart (after having saved the settings).

      But none of that matters because I am not able to connect in the 1st place. I have several computers on the network both wired and wireless so I CAN NOT just use wep (as is most often suggested).

      I do see other wireless networks (including my own) in the manager so I am fairly sure the card is recognized by the OS and the drivers are working. I am able to select "Connect to Other Wireless Networks" and it does allow me to enter all the correct info it just does not connect after that??

      So any help would be appreciated.
      Markus

      Comment


        #4
        Re: wireless halts at 28% - router negotiation to blame

        I'm having this problem. The only solution I've found so far is to use Windows until either this is fixed or I find a new distro. I need my internet access which is via a wireless router. This one problem has made K/X/Ubuntu completely unusable for me. At the moment Windows 9x would be more useful. >

        Comment


          #5
          Re: wireless halts at 28% - router negotiation to blame

          I've got this same problem going on. I feel like I've tried combination after combination with no success. The odd thing is that yesterday after the installation, it gave me the option for connecting to another wireless network, but today I don't see that option at all. It only shows the wired devices. I may try some of the suggestions / settings mentioned in the post. If all goes well then I'll be sure to let you know, but if anyone finds any write-ups or solutions to this problem, make sure you note it in the forum.

          Comment


            #6
            Re: wireless halts at 28% - router negotiation to blame

            My problem is that wireless does work - for a while at least. I have an IBM ThinkPad T40 with Atheros AR5211 A/B NIC, and my network is using WPA/PSK TKIP encryption.

            From a boot, knetworkmanager starts up, gets the key from the wallet and connects OK. But after a while - could be hours, could be only minutes, the connection drops. Sometimes I can manually reconnect it by clicking on the network name in the knetworkmanager popup, but eventually it will fail to connect. It shows configuring (28%), then IP setup (57%) then stops and goes back to being unconnected.

            "iwlist scan" shows that the card is still seeing the network. The key obviously has not changed. There are no other wireless networks in the area. Signal strength is good.
            Yet nothing I've tried (including stopping and restarting networking via the init.d scripts) brings it back to state where it will reconnect. The only thing that works is a reboot, which is nonsense.

            I've seen discussions of this well-known issue with wireless on Feisty in developer forums, but they just seem to be pointing fingers at each other, some saying it's a driver problem, others saying it's something else.

            I really hope this can get fixed soon.

            Comment


              #7
              Re: wireless halts at 28% - router negotiation to blame

              I'd like to add two more data points.

              1) I just fought a problem that matches the 28% description. It turned out to be my password. Kwallet truncated it one day from 13 char down to 12 after working fine for a month or more. It looked okay in the window but the window only shows the first 12 characters. Hmmmmm.

              2) I have never gotten TKIP to work well in Windows so I would not be surprised if it's flaky in Kubuntu too. It's very intermittent. I've tried on 5 installations over 3 year period. It never seems to work reliably. I don't even try it anymore. I just go to AES and forget it. If you try AES don't forget to change your access point too.

              I don't know if any of this helps but....

              wmrobins

              Comment

              Working...
              X