Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 40

Thread: HOW TO: Network Manager and New Edgy Install (supports WPA)

  1. #11
    Join Date
    Mar 2007
    Beans
    Hidden!

    Re: HOW TO: Network Manager and New Edgy Install (supports WPA)

    I am new to this and followed the below link to get WPA-PSK going on my Dell 600m with IPW2200 series
    http://www.ubuntuforums.org/showthread.php?t=263136

    However, at work we use WEP. Is network manager like it's counterpart in XP/OSX where I can specify separate locations and have a different protocol for each? I would like to be able to continue to run WPA at home while still being able to connect to the WLAN at work w/ WEP. Thanks a lot.

    -Chris

  2. #12
    Join Date
    May 2006
    Location
    Salt Lake City
    Beans
    210
    Distro
    Ubuntu 6.10 Edgy

    Re: HOW TO: Network Manager and New Edgy Install (supports WPA)

    @sch-chris
    I dont think you should have any problems. NetworkManager should store your WEP password in the gnome-keyring and your WPA password is stored there too each with its own entry. This makes your other howto redundant because with networkmanager you dont have to edit anything with wpa_supplicant. Having said that, I dont know exactly what it will do because I only use WPA or no encryption. I seriously doubt you will have problems, NetworkManager is built to easily switch between networks WPA, WEP, Wired and more

    *NOTE* you cant have a static IP at all with NetworkManager. In the howto you linked to, it looks like he had a static IP setup. Everything has to be dynamically assigned with NetworkManger
    How to Svideo and More on your i945 Chipset
    Dell E1405, Intel Core Duo 1.6 GHZ, 512 DDR2, Primary OS - Hardy RC / Secondary OS- XP Home

  3. #13
    Join Date
    Mar 2007
    Beans
    Hidden!

    Re: HOW TO: Network Manager and New Edgy Install (supports WPA)

    featherking,

    thanks for the quick reply. will I need to "undo" anything that I already did with the previous "how-to" that I posted a link to in my original post?

    the IPs for all networks that I connect to are assigned dynamically, so that is why I am looking to NM. Thanks again.

  4. #14
    Join Date
    May 2006
    Location
    Salt Lake City
    Beans
    210
    Distro
    Ubuntu 6.10 Edgy

    Re: HOW TO: Network Manager and New Edgy Install (supports WPA)

    @sch-chris
    no you shouldnt have to change anything. In fact i even sometimes use my old wpa_supplicant setup as a backup if something goes wrong. NetworkManager stores you passwords and SSID's totally seperate from your wpa_supplicant.conf file. But yeah, if everything you use is dynamic NetworkManager is probably exactly what you need
    How to Svideo and More on your i945 Chipset
    Dell E1405, Intel Core Duo 1.6 GHZ, 512 DDR2, Primary OS - Hardy RC / Secondary OS- XP Home

  5. #15
    Join Date
    Mar 2007
    Location
    Sheffield, UK
    Beans
    10
    Distro
    Ubuntu 7.10 Gutsy Gibbon

    Re: HOW TO: Network Manager and New Edgy Install (supports WPA)

    Hi, I have just installed edgy on a brand new Toshiba A120 and am trying to get the Intel 3945 wireless to work.

    First of all I followed gotgenes instructions here.

    I now have Network Manager installed and it is showing my access point. When I click on the access point it asks for my passcode (WPA) which I enter.
    The icon then just spins round for ages before reverting to wired connection.

    I have tried with WEP and no encryption with the same result.

    Is there any error output that I can look for? Could there be anything that I need to install? So far I have only installed network-manager-gnome.

    All help much appreciated!

  6. #16
    Join Date
    May 2006
    Location
    Salt Lake City
    Beans
    210
    Distro
    Ubuntu 6.10 Edgy

    Re: HOW TO: Network Manager and New Edgy Install (supports WPA)

    I dont know if you are dual-booting at all but if you are could you test your wireless connection in windows? just to rule out your network setup.

    I cant remember where NetworkManager stores its log. You could try connecting with NM and then type in terminal

    Code:
    dmesg
    and look for errors with your wifi connection

    if not try
    Code:
    tail /var/log/messages
    see if there is any errors there that mention NetworkManager, if there arent there either try:
    Code:
    tail /var/log/syslog
    I would think it would be in one of those areas if there is an error. But If you are able to see your networks then NetworkManger is working with your card properly because there arent any settings you can really adjust. This is why i think it is more likely a network problem.
    How to Svideo and More on your i945 Chipset
    Dell E1405, Intel Core Duo 1.6 GHZ, 512 DDR2, Primary OS - Hardy RC / Secondary OS- XP Home

  7. #17
    Join Date
    Mar 2007
    Location
    Sheffield, UK
    Beans
    10
    Distro
    Ubuntu 7.10 Gutsy Gibbon

    Re: HOW TO: Network Manager and New Edgy Install (supports WPA)

    Hi featherking

    Output from dmesg (after trying to connect to wireless) is
    Code:
    [17179759.452000] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
    [17179769.920000] eth1: no IPv6 routers present
    tail /var/log/messages
    Code:
    Mar  9 00:33:07 tosh2 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason
    Mar  9 00:33:30 tosh2 kernel: [17180107.580000] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
    Mar  9 00:35:24 tosh2 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
    Mar  9 00:35:24 tosh2 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
    Mar  9 00:35:24 tosh2 dhcdbd: message_handler: message handler not found under /com/redhMar  9 00:33:07 tosh2 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason
    Mar  9 00:33:30 tosh2 kernel: [17180107.580000] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
    Mar  9 00:35:24 tosh2 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
    Mar  9 00:35:24 tosh2 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
    Mar  9 00:35:24 tosh2 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
    Mar  9 00:35:25 tosh2 kernel: [17180222.860000] ADDRCONF(NETDEV_UP): eth1: link is not ready
    /var/log/syslog
    There is a lot in here. The section I have copied below is repeated several times before it gives up and connects back to eth0.
    Code:
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): Wireless event: cmd=0x8b15 len=20 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): Wireless event: new AP: 00:00:00:00:00:00 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): Setting scan request: 0 sec 100000 usec 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): Added BSSID 00:12:17:07:d1:c3 into blacklist 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): State: ASSOCIATED -> DISCONNECTED 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): WEXT: Operstate: linkmode=-1, operstate=5 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): EAPOL: External notification - portEnabled=0 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): EAPOL: SUPP_PAE entering state DISCONNECTED 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): EAPOL: SUPP_BE entering state INITIALIZE 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): EAPOL: External notification - portValid=0 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): EAPOL: External notification - EAP success=0 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): connect event - remove keys 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): CTRL_IFACE monitor send - hexdump(len=40): 2f 76 61 72 2f 72 75 6e 2f 4e 65 74 77 6f 72 6b 4d 61 6e 61 67 65 72 2f 77 70 61 5f 63 74 72 6c 5f 34 31 39 36 2d 35 00 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): State: DISCONNECTED -> SCANNING 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): Starting AP scan (broadcast SSID) 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): Scan timeout - try to get results 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): Received 480 bytes of scan results (2 BSSes) 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): Scan results: 2 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): Selecting BSS from priority group 0 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): 0: 00:12:17:07:d1:c3 ssid='WalkleyLAN' wpa_ie_len=24 rsn_ie_len=0 caps=0x11 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172):    selected based on WPA IE 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): Trying to associate with 00:12:17:07:d1:c3 (SSID='WalkleyLAN' freq=0 MHz) 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): 72 75 6e 2f 4e 65 74 77 6f 72 6b 4d 61 6e 61 67 65 72 2f 77 70 61 5f 63 74 72 6c 5f 34 31 39 36 2d 35 00 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): Cancelling scan request 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): WPA: clearing own WPA/RSN IE 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): Automatic auth_alg selection: 0x1 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): WPA: using IEEE 802.11i/D3.0 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): WPA: clearing AP RSN IE 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): WPA: using GTK TKIP 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): WPA: using PTK TKIP 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): WPA: using KEY_MGMT WPA-PSK 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): No keys have been configured - skip key clearing 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): wpa_driver_wext_set_drop_unencrypted 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): State: SCANNING -> ASSOCIATING 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): WEXT: Operstate: linkmode=-1, operstate=5 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): wpa_driver_wext_associate 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): Setting authentication timeout: 10 sec 0 usec 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): EAPOL: External notification - EAP success=0 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): EAPOL: External notification - EAP fail=0 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): EAPOL: External notification - portControl=Auto 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): Wireless event: cmd=0x8b06 len=8 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): b1a len=19 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): Wireless event: cmd=0x8b15 len=20 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): Wireless event: new AP: 00:12:17:07:d1:c3 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): State: ASSOCIATING -> ASSOCIATED 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): WEXT: Operstate: linkmode=-1, operstate=5 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): Associated to a new BSS: BSSID=00:12:17:07:d1:c3 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): No keys have been configured - skip key clearing 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): Associated with 00:12:17:07:d1:c3 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): CTRL_IFACE monitor send - hexdump(len=40): 2f 76 61 72 2f 72 75 6e 2f 4e 65 74 77 6f 72 6b 4d 61 6e 61 67 65 72 2f 77 70 61 5f 63 74 72 6c 5f 34 31 39 36 2d 35 00 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): WPA: Association event - clear replay counter 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): EAPOL: External notification - portEnabled=0 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): EAPOL: External notification - portValid=0 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): EAPOL: External notification - EAP success=0 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): EAPOL: External notification - portEnabled=1 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): EAPOL: SUPP_PAE entering state CONNECTING 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): EAPOL: SUPP_BE entering state IDLE 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): Setting authentication timeout: 10 sec 0 usec 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): EAPOL: startWhen --> 0 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): EAPOL: SUPP_PAE entering state CONNECTING 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): EAPOL: txStart 
    Mar  9 00:48:38 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0) 
    Mar  9 00:48:44 tosh2 NetworkManager: <information>^Iwpa_supplicant(6172): 0 
    Mar  9 00:48:44 tosh2 NetworkManager: <information>^IActivation (eth1/wireless): association took too long (>120s), failing activation. 
    Mar  9 00:48:44 tosh2 NetworkManager: <information>^IActivation (eth1) failure scheduled... 
    Mar  9 00:48:44 tosh2 NetworkManager: <information>^IActivation (eth1) failed for access point (WalkleyLAN) 
    Mar  9 00:48:44 tosh2 NetworkManager: <information>^IActivation (eth1) failed. 
    Mar  9 00:48:44 tosh2 NetworkManager: <information>^IDeactivating device eth1. 
    Mar  9 00:48:46 tosh2 NetworkManager: <information>^ISWITCH: no current connection, found better connection 'eth0'. 
    Mar  9 00:48:46 tosh2 NetworkManager: <information>^IWill activate connection 'eth0'. 
    Mar  9 00:48:46 tosh2 NetworkManager: <information>^IDevice eth0 activation scheduled...
    It does look like something to do with WPA but I tried earlier with no encryption and still didn't connect. Will try no encryption again and post the logs if I still don't get any joy.

    This machine has never had windows installed, so could be a hardware problem. If all else fails I will have to install XP and see if it works. Can connect to the network using another laptop (XP) without problem, so assuming that my wireless is set up correctly.

    Got a day off tomorrow so hoping to get it sorted then. Fed up of tripping over all these wires

    Cheers,

    Tom

  8. #18
    Join Date
    May 2006
    Location
    Salt Lake City
    Beans
    210
    Distro
    Ubuntu 6.10 Edgy

    Re: HOW TO: Network Manager and New Edgy Install (supports WPA)

    Very wierd,

    i cant see any reason for it not to associate, and if you have another computer that does connect wirelessly then chances are your network is setup properly. I dont see any reason for it not to work if you are using WPA-PSK on both your router and your wifi card.. Something is wrong somewhere though if you cant even connect with no encryption.. Sorry im not being of more help, you are doing everything right

    EDIT: See if you can connect manually using wpa_supplicant (sorry its a little long). Do the following in terminal

    Code:
    sudo gedit /etc/wpa_supplicant.conf
    change the following bold sections and then paste into the open gedit window
    Code:
    network={
    ssid="YOUR SSID"
    scan_ssid=1
    proto=WPA
    key_mgmt=WPA-PSK
    psk="YOUR WIFI PASSWORD"
    }
    close and save that.

    back in terminal type:
    Code:
    gedit ~/Desktop/wificonnect.sh
    paste the following
    Code:
    gksudo "killall wpa_supplicant"
    sudo wpa_supplicant -Dwext -B -w -ieth1 -c /etc/wpa_supplicant.conf
    sudo /etc/init.d/networking restart
    sudo dhclient eth1
    save and exit

    now type
    Code:
    chmod +x ~/Desktop/wificonnect.sh
    now kill NetworkManager
    Code:
    sudo killall NetworkManager
    Now after all those steps you have a script that sets up a manual connection using WPA on your wifi access point. The script should be on your desktop called wificonnect.sh and when you double click and run it, you should connect and be assigned an IP by your dhcp server. I use this as a backup sometimes on my laptop. See if you are able to connect via WPA to your access point..
    Last edited by featherking; March 9th, 2007 at 02:48 AM.
    How to Svideo and More on your i945 Chipset
    Dell E1405, Intel Core Duo 1.6 GHZ, 512 DDR2, Primary OS - Hardy RC / Secondary OS- XP Home

  9. #19
    Join Date
    Mar 2007
    Location
    Sheffield, UK
    Beans
    10
    Distro
    Ubuntu 7.10 Gutsy Gibbon

    Re: HOW TO: Network Manager and New Edgy Install (supports WPA)

    Thanks featherking.

    Did as you suggested. Here is the output from running wificonnect.sh from a terminal:

    Code:
    tom@tosh2:~$ ~/Desktop/wificonnect.sh 
    wpa_supplicant: no process killed
     * Reconfiguring network interfaces...                                   [ ok ] 
    Internet Systems Consortium DHCP Client V3.0.4
    Copyright 2004-2006 Internet Systems Consortium.
    All rights reserved.
    For info, please visit http://www.isc.org/sw/dhcp/
    
    Listening on LPF/eth1/00:19:d2:53:7c:b9
    Sending on   LPF/eth1/00:19:d2:53:7c:b9
    Sending on   Socket/fallback
    DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
    DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
    DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
    DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
    DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 16
    DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10
    No DHCPOFFERS received.
    No working leases in persistent database - sleeping.
    Does this mean that I am successfully connecting, but having a problem with DHCP?
    What is the easiest way of testing with a static IP?

    Think I might revert to XP just to make sure that it actually works
    Assuming that is successful, would you suggest trying the latest version of feisty?

  10. #20
    Join Date
    Mar 2007
    Location
    Sheffield, UK
    Beans
    10
    Distro
    Ubuntu 7.10 Gutsy Gibbon

    Re: HOW TO: Network Manager and New Edgy Install (supports WPA)

    Result!

    Have been able to lay my hands on an identical laptop with factory settings (WinXP Pro)
    Still had problems connecting to access point using this (even though my other laptop was working fine using a netgear PCMCIA adaptor)

    Started changing settings on my router. Changing the Wireless channel from 2 to 7 did the trick!
    For some reason the Intel Pro/Wireless 3945 was having problems with my access point (Linksys WRTG) running on channel 2 (both in linux and WinXP). Not sure if this has been found by anyone else but if I can find anywhere to report it I will.

    Just one question now... how do I set the default route when using Network Manager? It automatically sets the Default Route and Primary DNS to the ip address of my access point, however my local dns and gateway is via another server. I have set this manually using the below and everything is fine.
    Code:
    sudo route add gw 192.168.1.1 eth1
    Is there any way to set this via Network manager?

    Anyway, am typing this wire free so am happy
    Featherking, thanks very much for all your help. Were it not for your feedback I would still be blaming ubuntu for my lack of wireless!

    All the best,


    Tom

Page 2 of 4 FirstFirst 1234 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •