Announcement

Collapse
No announcement yet.

wlassistant finds my network, but can't log on to it... :-|

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    wlassistant finds my network, but can't log on to it... :-|

    I have been searching this (and other) forum for a couple of days to find a solution to this problem, but haven't been able to fix it...

    The problem:
    When I open wlassistant it finds my wireless network (ESSID: togh), but when I try to connect I get "connection failed". I have double-checked the network key, and I have double-checked that I have written the correct MAC-address in the routers MAC-filter.

    Similar problem: At first I thought this known bug, but when I write "sudo ifup ra0", I get this message:
    ~$ sudo ifup ra0
    ifup: interface ra0 already configured
    I have also tried (as had worked for some, according to the bug discussion) writing "sudo dhclient ra0", giving me this message:
    ~$ sudo dhclient ra0
    Listening on LPF/ra0/XX:XX:XX:XX:XX:XX (not with the X'es, but a real MAC-address)
    Sending on LPF/ra0/XX:XX:XX:XX:XX:XX
    Sending on Socket/fallback
    DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 3
    DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 4
    DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 9
    DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 11
    DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 11
    DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 10
    DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 13
    No DHCPOFFERS recieved.
    No working leases in persistent database - sleeping.
    Obviously (since wlassistant can see my network) this is a simple problem, but I can't find out what is wrong. I appreciate any help, and will fill in with some more information below:

    ~$ sudo iwconfig
    lo no wireless extensions.

    eth0 no wireless extensions.

    ra0 RT61 Wireless ESSID:"togh"
    Mode:Managed Channel:11 Access Point: XX:XX:XX:XX:XX:XX (not the X's, but a real MAC-address)
    Bit Rate=1 Mb/s
    RTS thrff Fragment thrff
    Encryption key: XXXX
    Link Quality=87/70 Signal level:-52 dBm Noise level:-79 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0

    sit0 no wireless extensions.
    To me this looks like a confirmed connection to "togh", but I don't know enough about these sorts of things to tell...

    Tags: None
    • Top
    • Bottom
    #2
    Re: wlassistant finds my network, but can't log on to it... :-|

    Hi,

    I remember that on dapper there was trouble with gui to enter a secured network, I don't know if it was solved or not.
    The best way would be to try to connect via command line and iwconfig
    I guess it's the password which is not set correctly in the file so to correct it :
    sudo iwconfig ra0 key <your_key>
    Then sudo dhclient ra0

    If you don't get an ip so I'm wrong...

    Hope it helps
    • Top
    • Bottom

    Comment

      #3
      Re: wlassistant finds my network, but can't log on to it... :-|



      ~$ sudo iwconfig ra0 key XXXX
      ~$ sudo dhclient ra0
      Listening on LPF/ra0/XX:XX:XX:XX:XX:XX (not with the X'es, but a real MAC-address)
      Sending on LPF/ra0/XX:XX:XX:XX:XX:XX
      Sending on Socket/fallback
      DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 4
      DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 4
      DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 10
      DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 13
      DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 13
      DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 17
      No DHCPOFFERS recieved.
      No working leases in persistent database - sleeping.
      Same result as last time...
      • Top
      • Bottom

      Comment

        #4
        Re: wlassistant finds my network, but can't log on to it... :-|

        ~$ lspci
        (...)
        0000:02:00.0 Network controller: RaLink: Unknown device 0302
        I don't know if this is relevant ("unknown device"...)
        • Top
        • Bottom

        Comment

          #5
          Re: wlassistant finds my network, but can't log on to it... :-|

          Usually not, it's just because it's not known by the system, but as you get an entry in iwconfig I guess it doesn't matter. To be sure, you can check in dmesg to see if you have some errors about this card or interface...

          Anyway, sorry I don't know what it can be if it's not also your mac address filter which is missing your mac on the router...
          Did you try without securisation ? Just to be sure you can connect well ?

          Good luck
          • Top
          • Bottom

          Comment

            #6
            Re: wlassistant finds my network, but can't log on to it... :-|

            ~$ dmesg
            (...)
            ra0 (WE): Driver using old /proc/net/wireless support, please fix driver !
            (...)
            ra0: no IPv6 routers present
            (...)
            I double-checked the MAC-filter to be sure, and that one is correct.

            We are several persons sharing the router, so I'd rather not start changing the settings on it (in case I mock something up...) - but I am connected to it right now from another laptop with the exact same wireless card - only through Windows...

            PS: Thank you for helping!
            • Top
            • Bottom

            Comment

              #7
              Re: wlassistant finds my network, but can't log on to it... :-|

              Hi,

              Just one more question, is it wpa or wpa2 ? If yes, did you install wpasupplicant package ?

              Once more, good luck
              • Top
              • Bottom

              Comment

              Previous template Next
              Working...
              X