Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My question: why are there so many different procedures which must be called in order to get on a network? Is there any general description of what is involved? What is the difference between dhclient and dhcpcd, or between ifconfig and iwconfig?
Background: when I got my wireless server up and talking to the router, it was still not on the internet. Serg.kr suggested I still needed to get an IP address. He suggested "dhclient", which did not work, but an attempt with "dhcpcd" did work. To my recollection, neither of these programs was mentioned in the installation procedure for my wireless driver.
--By no means disapproving of anything; just trying to learn.
Last edited by dafydil; 08-18-2007 at 03:46 PM.
Reason: Misspelled dhclient
dhclient is a DHCP client. dhcpcd is a DHCP server, and you don't need a DHCP server running on your machine to get on the network (so I don't know what you did that made it work). ifconfig is the interface config tool. iwconfig is the same thing but meant for wireless interfaces. Being able to get an IP is assumed by the wireless driver instructions.
dhcpcd is a DHCP server, and you don't need a DHCP server running on your machine to get on the network
You must have overlooked the "c" in the name. While dhclient is the DHCP client provided by ISC's DHCP package, dhcpcd is indeed an alternative DHCP client. Gentoo's website has a page that briefly lists some pros and cons of each.
Apparently there will be several similar programs to handle a given type of action, which may vary depending perhaps on physical device types. But I still think of the networking software as being fragmented. If the purpose of a driver is to mediate between the physical device and the user program, why, when I load a driver for a particular device, is the driver not ready for I/O traffic from the user program?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.