problem with dhcp and a special feedback...
hello, with debian (i tried the latest net-install) - but also with a lot of other distros - i have a special problem: i can't get a dhcp-connection. only with zenwalk there is (latest version 4) not the slightest problem. i asked - very generally - them, what the differences could be that made the differences. i got the following answers (copy of mail, my question is at the end): begin citation: Debian uses dhclient by default where Zenwalk (and Slack) use dhcpcd. They seem to handle the dhcp protocol in a slightly different way (seems there's yet another client - dhcdbd - out there needed for the Gnome Network Manager that does it his way too). B Op donderdag 04-01-2007 om 00:57 uur [tijdzone +0100], schreef Jean-Philippe Guillemin: > Hi, > > I don't know Debian enough to tell you what's really different in > Zenwalk regarding DHCP. > > The only thing I can tell you is a bit general : Zenwalk has a simple > design, inherited from Slackware, but more modern, and maybe even simpler. > > The simplicity often make the difference between something that works, > and the rest ... > > Cheers > > JP > > [EMAIL PROTECTED] wrote: > > hello mr guillemin, > > > > its near a miracle: with your zenwalk-distro i have no problems with > > dhcp-connection. > > only with opensuse (and there only with their second choice "ifup" and > > not with their networkmanager) i can get this experience too, but > > debian, several live-cds, belenix, bsd-distros... there is no > > connection at all. > > > > and zenwalk does it in a blinck of an eye. > > > > what do you do different to all the others? if it's no secret, please > > give me some information. > > my laptop is a benq r55 joybook, i connect via ethernet to a > > cable-modem and through it to my provider (i live in austria). > > > > greetings > > hans > > > > > > > > ___ > Zenwalk-main mailing list > [EMAIL PROTECTED] > http://lists.zenwalk.org/cgi-bin/mailman/listinfo/zenwalk-main end citation could this information be of some help? i would like very much to have the next debian on my laptop! greetings hans
Re: problem with dhcp, might be firestarter related
Hendrik Sattler wrote: Juha Pahkala wrote: Mar 8 13:03:25 server dhcpd: Wrote 0 leases to leases file. Mar 8 13:03:25 server dhcpd: Multiple interfaces match the same shared network: lan eth1 Mar 8 13:03:25 server dhcpd: Bind socket to interface: No such device So, somewhere in my config files there's still a dangling reference to that old 'lan' interface that doesn't exist anymore! I've tried to grep through all the config file in /etc and /var and /usr/share but haven't found anything. This may come from the /etc/dhcp3/dhcpd.conf (or something like that). What does your "ifconfig" output say about the network configuration? HS Hi Hendrik, Indeed I had the 'lan' configured still in the dhcpd.conf file, *even though I had checked it already about five times* sorry to waste bandwith and your time like this, I feel ashamed, don't understand how I missed that, for two days!!! thanks all and sorry, juhis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problem with dhcp, might be firestarter related
Juha Pahkala wrote: > Mar 8 13:03:25 server dhcpd: Wrote 0 leases to leases file. > Mar 8 13:03:25 server dhcpd: Multiple interfaces match the same shared > network: lan eth1 > Mar 8 13:03:25 server dhcpd: Bind socket to interface: No such device > > So, somewhere in my config files there's still a dangling reference to > that old 'lan' interface that doesn't exist anymore! I've tried to grep > through all the config file in /etc and /var and /usr/share but haven't > found anything. This may come from the /etc/dhcp3/dhcpd.conf (or something like that). What does your "ifconfig" output say about the network configuration? HS -- Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de oder über pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.org pgpMqVY3gTis6.pgp Description: PGP signature
Re: problem with dhcp, might be firestarter related
Juha Pahkala wrote: Juha Pahkala wrote: customized (by the ifconfig package) network device names btw, I just want to correct that I ment the package 'ifrename', not 'ifconfig' juhis Sorry for continously replying to my self but I've yet more information: actually if I bypass the dhcpd3-server start script in /etc/init.d and just issue: bash:# dhcpd3 -q eth1 I immediately get the following to syslog: Mar 8 19:16:27 server dhcpd: Internet Systems Consortium DHCP Server V3.0.3 Mar 8 19:16:27 server dhcpd: Copyright 2004-2005 Internet Systems Consortium. Mar 8 19:16:27 server dhcpd: All rights reserved. Mar 8 19:16:27 server dhcpd: For info, please visit http://www.isc.org/sw/dhcp/ Mar 8 19:16:27 server dhcpd: Wrote 0 deleted host decls to leases file. Mar 8 19:16:27 server dhcpd: Wrote 0 new dynamic host decls to leases file. Mar 8 19:16:27 server dhcpd: Wrote 0 leases to leases file. Mar 8 19:16:27 server dhcpd: Multiple interfaces match the same shared network: lan eth1 Mar 8 19:16:27 server dhcpd: Bind socket to interface: No such device Note that I only pass one interface, eth1, to dhcpd3, but somehow it fetches the old 'lan' interface somewhere. anybody know more on how dhcpd3 works? thanks, juhis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problem with dhcp, might be firestarter related
Juha Pahkala wrote: customized (by the ifconfig package) network device names btw, I just want to correct that I ment the package 'ifrename', not 'ifconfig' juhis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problem with dhcp, might be firestarter related
Laurent CARON wrote: Juha Pahkala a écrit : Hello, I have strange problem with dhcp, that might be somehow related to firestarter. But not necessarily directly. I did so many different things with my network setup simultaneously that I'm not sure, what's causing my current problem. So what I did was try to convert to using dhcp in my home lan. But at the same time, I converted from using customized (by the ifconfig package) network device names back to standard 'ethN' kind of names, and this somehow causes my current problem. My network device name for my home lan used to be 'lan'. I configured firestarter to use dhcp on that interface 'lan'. I did however have some problems with dhcp possibly due to my using non-standard interface names, so I switched back to using 'eth1' as my lan interface name. But I still couldn't get dhcp to start. I tried upgrading my dhcp server to the latest one (dhcp3-server) and what not, but nothing seems to work (I'm using debian unstable btw). Now I've uninstalled firestarter and purged the configuration files of it temporarily and try to use dhcp3-server directly to enable dhcp, and I get this result in my sysconfig when I try to start dhcp3-server: Mar 8 13:03:25 server dhcpd: Wrote 0 leases to leases file. Mar 8 13:03:25 server dhcpd: Multiple interfaces match the same shared network: lan eth1 Mar 8 13:03:25 server dhcpd: Bind socket to interface: No such device So, somewhere in my config files there's still a dangling reference to that old 'lan' interface that doesn't exist anymore! I've tried to grep through all the config file in /etc and /var and /usr/share but haven't found anything. I have a feeling that either dhcp ver.2.0 or firestarter is the source of that reference but I'm not sure. I ask you guys if you can think of a place, where this reference might be? I don't understand this, is there possibly a binary file that grep can't read that might hold the old information? in /etc/default/dhc* ? Nope, unfortunately... INTERFACES="eth1" Can you think of some other place? thanks, juhis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problem with dhcp, might be firestarter related
Juha Pahkala a écrit : Hello, I have strange problem with dhcp, that might be somehow related to firestarter. But not necessarily directly. I did so many different things with my network setup simultaneously that I'm not sure, what's causing my current problem. So what I did was try to convert to using dhcp in my home lan. But at the same time, I converted from using customized (by the ifconfig package) network device names back to standard 'ethN' kind of names, and this somehow causes my current problem. My network device name for my home lan used to be 'lan'. I configured firestarter to use dhcp on that interface 'lan'. I did however have some problems with dhcp possibly due to my using non-standard interface names, so I switched back to using 'eth1' as my lan interface name. But I still couldn't get dhcp to start. I tried upgrading my dhcp server to the latest one (dhcp3-server) and what not, but nothing seems to work (I'm using debian unstable btw). Now I've uninstalled firestarter and purged the configuration files of it temporarily and try to use dhcp3-server directly to enable dhcp, and I get this result in my sysconfig when I try to start dhcp3-server: Mar 8 13:03:25 server dhcpd: Wrote 0 leases to leases file. Mar 8 13:03:25 server dhcpd: Multiple interfaces match the same shared network: lan eth1 Mar 8 13:03:25 server dhcpd: Bind socket to interface: No such device So, somewhere in my config files there's still a dangling reference to that old 'lan' interface that doesn't exist anymore! I've tried to grep through all the config file in /etc and /var and /usr/share but haven't found anything. I have a feeling that either dhcp ver.2.0 or firestarter is the source of that reference but I'm not sure. I ask you guys if you can think of a place, where this reference might be? I don't understand this, is there possibly a binary file that grep can't read that might hold the old information? in /etc/default/dhc* ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
problem with dhcp, might be firestarter related
Hello, I have strange problem with dhcp, that might be somehow related to firestarter. But not necessarily directly. I did so many different things with my network setup simultaneously that I'm not sure, what's causing my current problem. So what I did was try to convert to using dhcp in my home lan. But at the same time, I converted from using customized (by the ifconfig package) network device names back to standard 'ethN' kind of names, and this somehow causes my current problem. My network device name for my home lan used to be 'lan'. I configured firestarter to use dhcp on that interface 'lan'. I did however have some problems with dhcp possibly due to my using non-standard interface names, so I switched back to using 'eth1' as my lan interface name. But I still couldn't get dhcp to start. I tried upgrading my dhcp server to the latest one (dhcp3-server) and what not, but nothing seems to work (I'm using debian unstable btw). Now I've uninstalled firestarter and purged the configuration files of it temporarily and try to use dhcp3-server directly to enable dhcp, and I get this result in my sysconfig when I try to start dhcp3-server: Mar 8 13:03:25 server dhcpd: Wrote 0 leases to leases file. Mar 8 13:03:25 server dhcpd: Multiple interfaces match the same shared network: lan eth1 Mar 8 13:03:25 server dhcpd: Bind socket to interface: No such device So, somewhere in my config files there's still a dangling reference to that old 'lan' interface that doesn't exist anymore! I've tried to grep through all the config file in /etc and /var and /usr/share but haven't found anything. I have a feeling that either dhcp ver.2.0 or firestarter is the source of that reference but I'm not sure. I ask you guys if you can think of a place, where this reference might be? I don't understand this, is there possibly a binary file that grep can't read that might hold the old information? Thanks in advance, Juhis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem with DHCP
A long time ago, in a galaxy far, far way, someone said... > On Thu, Jan 27, 2000 at 10:09:20AM -0600, Phil Brutsche wrote: > > A long time ago, in a galaxy far, far way, someone said... > > > > > I am running Potato on an P3.. and have a DHCP server with some > > > Windows 95 clients. However, when those Windows 95 boot up they cannot > > > get an IP from the DHCP server. (according to the logs the DHCP server > > > have already offered the IPs.) When I run "winipcfg" and manually > > > refresh the DHCP settings it works most of the times. Sometimes the > > > interface refuses to update the IP. There was once a Windows NT DHCP > > > server running with no problems (and was replaced by the Debian > > > server). Is it possible that I have misconfigured something? > > > > It's likely that you've misconfigured something, however we need to know > > more about how your network is set up: the locations of routers & hubs & > > so on. > I am not responsible for the network set-up so I cannot tell for sure, > but I think everything is connected to a big Ethernet switch.. The > network is connected to the external network through a machine (IP: > 10.1x.x.1) that acts also as a WWW proxy server. First DNS server, as > well as the DHCP server, is on 10.1x.x.2.. I can't remember the exact > IPs, but I guess they shouldn't matter..? The IPs don't matter. I take it then that there's no router between the DHCP server and the clients? > > > > > Are you using ISC's DHCP server software? If you are, it might help to > > see a configuration that's been working for me for quite some time: > > http://tux.creighton.edu/~pbrutsch/dhcpd.conf. > Yes, I am using ISC's DHCP server. > > My configuration file is similar... equally short. > The only differences that I can remember (save from choices of > IPs) are: > 1) I put the "routers" and "domain-name-servers" lines outside >of the subnet bracket Trivial difference. > 2) I have set up more than 1 DNS server, separated by commas Again a trivial difference. > 3) lease times are shorter.. like a few hours. Am I supposed to >use lease time that long? Not necessarily - lease times are chosen arbitrarily. I chose 1 day because it sounded good :) Sometimes they're set for a reason: here at the University the lease time is 5 days, probably to prevent the computer serving DHCP from being overloaded (there are very easliy over 1000 DHCP clients here). It would be good to double check your config against mine to make sure you don't have a setting that could be messing things up. If that doesn't work... ISC runs several mailing lists for dhcpd/dhclient. They'll be able to help you more there. -- -- Phil Brutsche [EMAIL PROTECTED] "There are two things that are infinite; Human stupidity and the universe. And I'm not sure about the universe." - Albert Einstein
Re: Problem with DHCP
On Thu, Jan 27, 2000 at 10:09:20AM -0600, Phil Brutsche wrote: > A long time ago, in a galaxy far, far way, someone said... > > > I am running Potato on an P3.. and have a DHCP server with some > > Windows 95 clients. However, when those Windows 95 boot up they cannot > > get an IP from the DHCP server. (according to the logs the DHCP server > > have already offered the IPs.) When I run "winipcfg" and manually > > refresh the DHCP settings it works most of the times. Sometimes the > > interface refuses to update the IP. There was once a Windows NT DHCP > > server running with no problems (and was replaced by the Debian > > server). Is it possible that I have misconfigured something? > > It's likely that you've misconfigured something, however we need to know > more about how your network is set up: the locations of routers & hubs & > so on. I am not responsible for the network set-up so I cannot tell for sure, but I think everything is connected to a big Ethernet switch.. The network is connected to the external network through a machine (IP: 10.1x.x.1) that acts also as a WWW proxy server. First DNS server, as well as the DHCP server, is on 10.1x.x.2.. I can't remember the exact IPs, but I guess they shouldn't matter..? > > Are you using ISC's DHCP server software? If you are, it might help to > see a configuration that's been working for me for quite some time: > http://tux.creighton.edu/~pbrutsch/dhcpd.conf. Yes, I am using ISC's DHCP server. My configuration file is similar... equally short. The only differences that I can remember (save from choices of IPs) are: 1) I put the "routers" and "domain-name-servers" lines outside of the subnet bracket 2) I have set up more than 1 DNS server, separated by commas 3) lease times are shorter.. like a few hours. Am I supposed to use lease time that long? > > > Clients uses Intel EEpro* cards, and the server uses a D-Link card > > with the chip from Davicom (using via-rhine modules) > > The ethernet cards shouldn't make a difference. >
Re: Problem with DHCP
A long time ago, in a galaxy far, far way, someone said... > I am running Potato on an P3.. and have a DHCP server with some > Windows 95 clients. However, when those Windows 95 boot up they cannot > get an IP from the DHCP server. (according to the logs the DHCP server > have already offered the IPs.) When I run "winipcfg" and manually > refresh the DHCP settings it works most of the times. Sometimes the > interface refuses to update the IP. There was once a Windows NT DHCP > server running with no problems (and was replaced by the Debian > server). Is it possible that I have misconfigured something? It's likely that you've misconfigured something, however we need to know more about how your network is set up: the locations of routers & hubs & so on. Are you using ISC's DHCP server software? If you are, it might help to see a configuration that's been working for me for quite some time: http://tux.creighton.edu/~pbrutsch/dhcpd.conf. > Clients uses Intel EEpro* cards, and the server uses a D-Link card > with the chip from Davicom (using via-rhine modules) The ethernet cards shouldn't make a difference. -- -- Phil Brutsche [EMAIL PROTECTED] "There are two things that are infinite; Human stupidity and the universe. And I'm not sure about the universe." - Albert Einstein
Problem with DHCP
I am running Potato on an P3.. and have a DHCP server with some Windows 95 clients. However, when those Windows 95 boot up they cannot get an IP from the DHCP server. (according to the logs the DHCP server have already offered the IPs.) When I run "winipcfg" and manually refresh the DHCP settings it works most of the times. Sometimes the interface refuses to update the IP. There was once a Windows NT DHCP server running with no problems (and was replaced by the Debian server). Is it possible that I have misconfigured something? Clients uses Intel EEpro* cards, and the server uses a D-Link card with the chip from Davicom (using via-rhine modules)
