WG311v2 almost working with Edgy (w/o ndiswrapper) need help with the rest

Discussion in 'Server Operation' started by caudata, Nov 6, 2006.

  1. caudata

    caudata New Member

    Ok I now have my netgear WG311v2 (an acx111 chipset) almost working. The light comes on and even blinks shows up enabled the /etc/network/interfaces file looks good. I can scan for networks it just will not connect. As has been posted I tried knetworkmanager and during the "activation stage:configuring device" it freezes at 28% when I to connect. Looks like the access point is associating with "linksys" like I want it to because of the iwconfig output, but I can't successfully ping. So I'm at a loss, so close but so far. If anyone has any suggestions please let me know I would appreciate any help that can be provided.

    I did comment out the wlan0 before starting knetworkmanager, but since it did not work I have stopped trying KNM and I uncommented the wlan0.
     
    Last edited: Nov 6, 2006
  2. caudata

    caudata New Member

    the dmesg | less output

    Here is the output from the tail -100 /var/log/messages command. Anyone have a clue how I can get this to connect to the internet?
     
  3. caudata

    caudata New Member

    more weird results

    .............
     
  4. falko

    falko Super Moderator ISPConfig Developer

    I have no clue about the other problems, but for this one you should check /etc/resolv.conf. Make sure you have valid name servers in there.
     
  5. caudata

    caudata New Member

    Sort of working

    Falko,
    I had done that command previously without success, but this time I did one thing different. When it didn't work I would edit the /etc/resolv.conf file and try to connect and that never worked, and the /etc/resolv.conf file would be rewritten. This time I edited the file and then pinged yahoo immediately afterward that worked! Now my concern is first the file gets rewritten, and second the wireless access point is running DHCP and I just used the IP address my computer picked up under Windoze and manually entered the info.I still would like it to work with DHCP, but not sure how. Thanks for the help.
     
  6. caudata

    caudata New Member

    DHCP question

    I now have the correct nameservers staying in my /etc/resolv.conf file. I brought up wireless assistant set to DHCP and it wouldn't connect. I brought up a terminal typed in the command sudo dhclient wlan0 while watching wireless assistant and NOW THE INTERNET IS WORKING! What do I need to do so that wireless assistant connects every time I bring it up without typing sudo dhclient wlan0? Thank you for any help you can provide, later!
     
  7. falko

    falko Super Moderator ISPConfig Developer

    How about running that command automatically whenever the system is started? Maybe with an init script?
     
  8. caudata

    caudata New Member

    Falko,

    I'm not sure how to create an init script, and I have to run the sudo command everytime I run dhclient wlan0. My level of Linux knowledge is: enough to get me into trouble. I did find out this problem is a known bug in Kubuntu 6.10 "Edgy"https://launchpad.net/distros/ubuntu/ source/wlassistant/ bug/64841 I believe I also read it's because wireless assistant is issuing the wrong command. If I could figure out how to edit the wireless assistant commands with the correct one then it should work. At least I believe that's what this is saying: http://kde-apps.org/content/show.ph...=0&PHPSESSID=918babfa423f739925b93cc9c6fca3bb
    Thanks for your efforts so far.
     
  9. falko

    falko Super Moderator ISPConfig Developer

  10. caudata

    caudata New Member

    I just looked over the requirements for wireless assistant and I have everything, and never modified /etc/sudoers. Thanks for the init script I'll give it a try when I have time. Thank you for your help.
     
  11. falko

    falko Super Moderator ISPConfig Developer

    I forgot to say: you must make the init script executable:
    Code:
    chmod 755 /etc/init.d/[I]name_of_script[/I]
    To make the script start at boot time run
    Code:
    update-rc.d [I]name_of_script[/I] defaults
     
  12. caudata

    caudata New Member

    thanks

    Falko,
    Thanks for taking the time to respond I have it working now :)
     

Share This Page