LinuxWorld999 wrote:
On Saturday 15 November 2003 11:31, awilisch wrote:
I ran through as many different combinations as I can think of. I never bothered setting a default gateway since I'm trying to figure out why it's not getting one from my router. I checked the things others have mentioned here as well such as the firewall, which is installed but not configured or even on.
I really think that it might just be a change in how the dhcp client gets it's information or it's something in the kernel configuration. I pulled it off for the moment to put Mandrake 9.2 on. Wireless works great, but I'm having issues with the keyboard and I really do prefer Suse 9, so I'm going to dump the /etc directory, then reload either 8.2 or 9 and just start working my way up till I figure what the problem is. (but I'll take any and all help, suggestions, etc :)
<snip>
When experiencing similar problems, the following format of dhcpcd command was used as it provides more information :
dhcpcd -n -d -B wlan0.
Replace wlan0 with the network interface requiring an IP address from a DHCP server.
Under YaST2, launch the yast2->system->sysconfig module and search for "resolv" and "dhcp". Review the flags for the various settings. It possible that the variable "dynamically update resolv" is switched off. This should be switched on. Similarly, check any other flags relating to dhclient and resolv are flagged to update routes and gateways. If these are turned off, the routing will not be set as expected. Turn these on.
Before using the internet, on the pc here the firewall and DNS has to be restarted.
HTH.
LW999
I just got it working by running dhcpcd wlan0 as root from a command prompt, not sure why it worked, I'll look into that later. At least now I can go from hardwired at work to wireless at home without having to connect hardwired at home first. Maybe by putting the command in a script in the Profile Manager I can automate the process - I'll try later - after I get some real work done. -- Hugh mailto: hrtlist@cpia.jhu.edu