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.
I think you might have just made a slip, because as your computer loads it says "dhcpcd" which is the correct daemon. DHCPd is the server, and if you are trying to get an address you want the client.
Moving along. Have you plugged another machine into this network and requested an IP address? Are both of these NIC's connected to the same network? or are they on seperate networks? Where is the DHCP server running on this network?
You are getting a timeout error. A firewall is blocking your DHCP request or there is no dhcp server running. Find the blockage.
With a valid IP address I meant one in the range of the dhcp host, and seemingly issued by that host.
Ultimately I want the gateway to sit between the DSL modem and the Belkin router. In both cases I would prefer the gw to be a dhcp client on those two networks, but I can easily live with dchp on the DSL side and fixed IP on the router side.
I'm running out of ideas here. You say that the laptop got an ip that was valid, I dont recall you telling me which ip that was, but you told me which block it belonged to. In a last hurrah I would pull one of the cards out of the linux box. Treat it like you would your laptop for now, just a regular machine. Then work up. I have no idea what it could be, except that for some reason the cards are not connecting to the dhcp servers. Start again at square 2, and work your way up. If this whole backtracking thing doesn't work, there's always square 1 which is a reinstall.
Originally posted by Recirqie With a valid IP address I meant one in the range of the dhcp host, and seemingly issued by that host.
Ultimately I want the gateway to sit between the DSL modem and the Belkin router. In both cases I would prefer the gw to be a dhcp client on those two networks, but I can easily live with dchp on the DSL side and fixed IP on the router side.
Am I the one with a twisted mind ? A router (gateway) with dynamic IPs seems such an unlikely idea...
See, on each side of a router, machines are to be given routes indicating which traffic must go through which gateway. For example the default gateway is the way that should take any traffic which is not regarded as internal (that is, destination network address given by the n first bits of source IP, n being the number of bits set at 1 in the subnet mask); this default gateway is either hard-set in the hosts network settings, or pushed by the dhcp server.
Now the dhcp server does not know what a network adapter is used for (workstation or router), thus the default gateway (for instance) must be hard set in the dhcp server config, so obviously the router *cannot* be a dhcp client...
Perhaps this won't tell you why you have trouble configuring dhcp client on your gateway interfaces, but at least it might tell you why you shouldn't
But, as I said, perhaps I am the one who is all wrong...
do you need dhcpd to be broadcasting on both your network interfaces? probably not. you can specify what interfaces you want to use as an argument to dhcpd (or in your dhcpd startup script, whichever you want)
The network being small I have done as recommended in Ibsen's Peer Gynt: I've circumvented the problem.
I have put the proxy as a dhcp client with IP-address on a permanent lease. It does the job, although strictly speaking it is a somewhat untidy solution.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.