Scott Leighton writes:
My laptop is a HP zv5320, I have eth0 working fine and with ndiswrapper, I can get wlan0 working with WEP. Adding wpa_supplicant to the mix and I can connect to the AP fine, but dhcp doesn't seem to work properly. No route and no dns ever gets set up.
I'm hoping someone can answer these for me...
1) Do I have to bring eth0 down in order for dhcp to work on wlan0?
Yes, you can't have two live interfaces both updating your default route and DNS at the same time. The first one will take precedence. I ran into this same situation on my Toshiba laptop (which has built-in ethernet and wireless). The solution is to create two SCPM profiles, one with ethernet enabled but no wireless, and the other with wireless enabled but no ethernet. Then, create two grub boot entries so that I could choose to boot with either profile. If you don't have any SCPM profiles yet, this is how you would set it up on SuSE 9.1. (Assuming your ethernet interface is eth0 and wireless interface is wlan0): 0. Log in as root. 1. Make sure your MODIFY_RESOLV_CONF_DYNAMICALLY parameter is set to "yes" in your /etc/sysconfig/network/config file. 2. Save a backup copy of your /etc/sysconfig/network/ifcfg-eth* and /etc/sysconfig/network/ifcfg-wlan* files in your /tmp or in your home directory. 3. Delete the /etc/sysconfig/ifcfg-wlan* file 4. Connect the ethernet cable 5. Run "rcnetwork restart", and let DHCP set up your IP, DNS and default route. 6. scpm enable (This will create a "default" profile, which is ethernet-only, answer 'y' if asked any questions) 7. scpm copy default eth (This makes an explicit profile called "eth" for ethernet-only) 8. Disconnect your ethernet cable, make sure your wireless AP is working 9. Delete the /etc/sysconfig/ifcfg-eth* file 10. Restore the /etc/sysconfig/ifcfg-wlan* file, make sure this file has all the correct wireless ESSID and WEP configuration in it (i.e., WIRELESS_ESSID, WIRELESS_KEY*, WIRELESS_KEY_LENGTH, WIRELESS_MODE). 11. Run "rcnetwork restart", and let DHCP set up your IP, DNS and default route. 12. scpm reload (This will change the "default" profile to wireless- only, answer 'y' if asked any questions) 13. scpm copy default wlan (This makes an explicit profile called "wlan" for wireless-only) 14. scpm switch wlan (This switches your current profile to wlan) 15. Edit the /boot/grub/menu.lst file, and change the "Linux" entry so that the "Linux" name is "Linux ethernet", and append the boot parameter "PROFILE=eth". Also, add a new item in this file similar to the above, except that it's "Linux wireless" with "PROFILE=wlan". 16. You're now done. At boot time you can select which profile to use. 17. At run time, you can also switch profiles with the following command: scpm switch eth (Switch to ethernet-only profile. SCPM will automatically restart the network for you) or scpm switch wlan (Switch to wireless-only profile. SCPM will automatically restart the network for you) The "default" profile is not normally used, but only as a placeholder to create new profiles if needed. See scpm(8) man page for more info about SCPM and profile management. The SuSE 9.1 Admin Manual also has a good section on SCPM. Hope this helps. P.S. I didn't have to use wpa_supplicant so no info to share there. -Ti -- Ti Kan http://www.amb.org/ti Vorsprung durch Technik