Suse/NovellThis Forum is for the discussion of Suse Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The standard DHCP client (dhcpcd) that comes with Suse 9.1 does not work with the DHCP server build into some wireless access points. In particular the Linksys ones. I have a Linksys A+B. A friend of mine has a Linksys G. It fails to obtain an address from both of them.
The same computer with the same network card runs fine with static configuration and is able to obtain an IP address if run with Windows. And yes, I did restart the access point after Windows was shutdown (to clear the arp cache).
I tried to change some config options in /etc/sysinit/network/dhcp to no avail.
I also tried to find (or compile) a version of pump, but could not do so.
I don't know where does your arrogance comes from, but I am not posting just random issues. When I say it does not work, it does not and it is not because of my "configuration".
I have been around the block (several times) and I am capable of determining a simple issue like that, believe me.
If what are you saying is true, could you explain to me how come the same card works just fine when configured statically and does not when configured to use DHCP. BTW: There is nothing to "configure" for DHCP. That is the whole point, isn't it?
When I said wireless access point I did not explain that I am using a normal "wired" network card to connect via a cable to the "access point". In this case is practically a router.
Also, I have 2 subnets, one for the normal network, which uses a DHCP server of a Linux box. If I connect to that network it works just fine. If I then connect to the port on the Linksys it does not obtain an address.
In fact I have tried this with 3 different cards, on 3 different computers, no difference. It always works when attached to the DHCP server on the Linux box, never works when attached to the Linksys AP.
Please, refrain to post when you are not contributing toward a solution.
BTW: I see it says you are using Suse 9.0, whereas I am using Suse 9.1
I have suse 9.1 as well. I just havent bothered to update the profile. You kinda don't pay attention to the version number after you've changed the thing 5 or 6 times. And I did post something useful.
NOTHING is wrong with suse's dhcp or with the interface to Linksys routers. Other people can use them just fine. So there is definately something wrong, with JUST your install of suse. And you should check the settings and try again rather than assuming its the operating systems problem or the routers problem.
Distribution: SuSE 9.2, Slackware Current, Arch Linux 0.7
why do you need dhcpd
As far as I know you do not need the DHCP Daemon, it is a Daemon to act AS A DHCP SERVER not to get information from your DHCP server, I have had no problems with DHCP, wired or wireless on any SuSE box I Have configured... the dhcpd allows a computer to be loaded with a minimal install of linux to act as a router albeit much faster than a router... (even a CISCO 2600 Catalyst has a processor with speeds equivalent to a cutting edge 486DX!) so I'm not sure you even need this. Check the network settings tab of YaST and make sure you're wireless card('s) are supported and configured properly... if they are not you might have to use ndiswrapper or something like linuxant.
I had a similiar problem, and only half solved it. I wrote a file in /etc/sysconfig/network/ifcfg-wlan0 based on info in the ./wireless and ./ifcfg.template in the same directory. Ican now obtain a IP address from a router
My problems now are:
A.) Will not work on bootup.
B.) Will not obtain DNS information from router.
Has to be something in either a script or config file but don't know where.
I had a similar problem with a D-LINK wireless (and wired) DSL router --it works fine on a 'Doze box.
To get it to work I can still use it to provide me with a dynamic IP address --but I had to set the DNS IP numbers that I use to connect to my ISP manually. I didn't need to set a default gateway either.
If I just let DHCP do it then it would put 192.168.1.1 in the first DNS box and (which is the address of the router).
Clearing that out and inserting the real DNS numbers worked (although I'd really like to have the whole thing completely automatic as if I connect to a different Network then the DNS names will be different.
So problem is 1/2 solved.
Anybody got any ideas how I can fix this completely --- it's the same on SUSE 9.0 as well as 9.1
BTW I'm using a bog standard Wired LAN card for testing -- I'll use Wifi later.
My previous router didn't have DHCP so I had to set everything manually --this still works with this router but I'd like to use DHCP to completely get all the DNS stuff automatically.