Re: IPv6 prefix delegation: avahi-daemon vs dhcpcd vs kernel
Le 29/07/2019 à 13:08, Pascal Hambourg a écrit : Prefix delegation is a DHCPv6 feature. The kernel does managed it. Oops ! I meant "the kernel does NOT manage it".
Re: IPv6 prefix delegation: avahi-daemon vs dhcpcd vs kernel
Le 29/07/2019 à 11:07, Harald Dunkel a écrit : question about IPv6 support in sid: Whose job is it to bother about the IPv6 addresses dynamically bound to eth0? It depends what dynamic configuration method is used. SLAAC (using router advertisements) is in kernelspace. However some information which may be included in router advertisements such as DNS related information are not managed by the kernel and must be managed in userspace (DNS in general is not managed by the kernel). DHCPv6 is in userspace (DHCPv6 client). AFAIU the kernel sees the prefix delegation on eth0, sets the old IPv6 address to "deprecated" and registers the new one. Prefix delegation is a DHCPv6 feature. The kernel does managed it. Or do you mean prefix information in router advertisements ?
Re: IPv6 prefix delegation: avahi-daemon vs dhcpcd vs kernel
Hi. On Mon, Jul 29, 2019 at 11:07:50AM +0200, Harald Dunkel wrote: > question about IPv6 support in sid: Whose job is it to bother > about the IPv6 addresses dynamically bound to eth0? Kernel's, mostly. You don't need userspace to receive and process SLAAC. > AFAIU the kernel sees the prefix delegation on eth0, sets the > old IPv6 address to "deprecated" and registers the new one. How > comes that avahi daemon and dhcpcd and possibly others interfere? I won't say anything about the avahi (don't see the need to install it), but I'm familiar with dhcpcd. Unless they've changed it in sid, dhcpcd should wait for RA announce for a couple of seconds (ipv6ra_autoconf option in dhcpcd.conf) and then send AF_NETLINK message to the kernel asking to set "global dynamic mngtmpaddr" IP on an interface and received routes. And, unless you force it somehow, dhcpcd should not touch "net.ipv6.conf.$IFACE.accept_ra" kernel knob, so future RAs are processed by the kernel directly. Reco
IPv6 prefix delegation: avahi-daemon vs dhcpcd vs kernel
Hi folks, question about IPv6 support in sid: Whose job is it to bother about the IPv6 addresses dynamically bound to eth0? AFAIU the kernel sees the prefix delegation on eth0, sets the old IPv6 address to "deprecated" and registers the new one. How comes that avahi daemon and dhcpcd and possibly others interfere? Every insightful comment is highly appreciated Harri
Re: dhcpcd y 802.1x SOLUCIONADO
El Thu, 21 Apr 2016 12:02:05 +0200, Antonio Trujillo Carmona escribió:
>
>
>
> body p { margin-bottom: 0cm; margin-top: 0pt;
> }
(...)
Uff... bueno si lo has resuelto, perfecto. No puedo leer el tocho de html
que mandas :-)
Saludos,
--
Camaleón
Re: dhcpcd y 802.1x SOLUCIONADO
El 20/04/16 a las 17:01, Camaleón escribió: El Wed, 20 Apr 2016 13:48:37 +0200, Antonio Trujillo Carmona escribió: Por lo visto en las ultimas versiones el dhcpd ha pasado de ser un programa (dhclient) que lanzava el networking cuando se configura en /etc/network/interfaces a un servicio propio que ignora el interfaces. Bueno, los paquetes de toda la vida (cliente y servidor) son "isc-dhcp- client" y "isc-dhcp-server", cada unos instala los demonios correspondientes (dhclient y dhcpd). Pero systemd tiene su propio cliente dhcp integrado, quizá sea ese quien te da guerra. Estoy teniendo problemas con una validación 802.1x, pues se lanza el dghcpd antes del wpasupplicant con lo que el equipo es asignado por el conmutador a una vlan incorrecta. Hum... ¿usas el cliente integrado de systemd o el paquete de ISC? Este es mi fichero interfaces: (...) No se puede desinstalar por dependencias, Raro... ¿cuáles, exactamente? como solución desactivo el dhcpd con *systemctl disable dhcpcd* *¿hay una forma mas correcta que no pase por tener que tener instalado un programa que no voy a usar?* Eliminarlo, obviamente. Pero me extraña que te genere dependencias fuertes porque es un paquete opcional y no es un componente base del sistema. sm01@stt008:~$ dpkg -l | grep -i dhcp ii isc-dhcp-client 4.2.2.dfsg.1-5+deb70u8 amd64ISC DHCP client ii isc-dhcp-common 4.2.2.dfsg.1-5+deb70u8 amd64common files used by all the isc-dhcp* packages Saludos, Perdonar por el ruido, lo intente con otro ordenador y me dio problemas, lo acabo de repetir y se ha desinstalado sin problemas de dependencias. # dpkg -l |grep dhcp ii dhcpcd5 6.7.1-1+rpi5 armhf DHCPv4, IPv6RA and DHCPv6 client with IPv4LL support ii isc-dhcp-client 4.3.1-6+deb8u2 armhf DHCP client for automatically obtaining an IP address ii isc-dhcp-common 4.3.1-6+deb8u2 armhf common files used by all of the isc-dhcp packages # dpkg --purge dhcpcd5 (Leyendo la base de datos ... 37271 ficheros o directorios instalados actualmente.) Desinstalando dhcpcd5 (6.7.1-1+rpi5) ... Purgando ficheros de configuración de dhcpcd5 (6.7.1-1+rpi5) ... Procesando disparadores para man-db (2.7.0.2-5) ... -- Antonio Trujillo Carmona Técnico de redes y sistemas. Subdirección de Tecnologías de la Información y Comunicaciones Servicio Andaluz de Salud. Consejería de Salud de la Junta de Andalucía antonio.trujillo.s...@juntadeandalucia.es Tel. +34 670947670 747670)
Re: dhcpcd y 802.1x
El Wed, 20 Apr 2016 13:48:37 +0200, Antonio Trujillo Carmona escribió: > Por lo visto en las ultimas versiones el dhcpd ha pasado de ser un > programa (dhclient) que lanzava el networking cuando se configura en > /etc/network/interfaces a un servicio propio que ignora el interfaces. Bueno, los paquetes de toda la vida (cliente y servidor) son "isc-dhcp- client" y "isc-dhcp-server", cada unos instala los demonios correspondientes (dhclient y dhcpd). Pero systemd tiene su propio cliente dhcp integrado, quizá sea ese quien te da guerra. > Estoy teniendo problemas con una validación 802.1x, pues se lanza el > dghcpd antes del wpasupplicant con lo que el equipo es asignado por el > conmutador a una vlan incorrecta. Hum... ¿usas el cliente integrado de systemd o el paquete de ISC? > Este es mi fichero interfaces: (...) > No se puede desinstalar por dependencias, Raro... ¿cuáles, exactamente? > como solución desactivo el dhcpd con > > *systemctl disable dhcpcd* > > > *¿hay una forma mas correcta que no pase por tener que tener instalado > un programa que no voy a usar?* Eliminarlo, obviamente. Pero me extraña que te genere dependencias fuertes porque es un paquete opcional y no es un componente base del sistema. sm01@stt008:~$ dpkg -l | grep -i dhcp ii isc-dhcp-client 4.2.2.dfsg.1-5+deb70u8 amd64ISC DHCP client ii isc-dhcp-common 4.2.2.dfsg.1-5+deb70u8 amd64common files used by all the isc-dhcp* packages Saludos, -- Camaleón
dhcpcd y 802.1x
Por lo visto en las ultimas versiones el dhcpd ha pasado de ser un programa (dhclient) que lanzava el networking cuando se configura en /etc/network/interfaces a un servicio propio que ignora el interfaces. Estoy teniendo problemas con una validación 802.1x, pues se lanza el dghcpd antes del wpasupplicant con lo que el equipo es asignado por el conmutador a una vlan incorrecta. Este es mi fichero interfaces: auto lo iface lo inet loopback allow-hotplug eth0 iface eth0 inet manual wpa-driver wired wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf wpa-iface eth0 iface default inet dhcp No se puede desinstalar por dependencias, como solución desactivo el dhcpd con *systemctl disable dhcpcd* *¿hay una forma mas correcta que no pase por tener que tener instalado un programa que no voy a usar?* ** -- *Antonio Trujillo Carmona* *Técnico de redes y sistemas.* *Subdirección de Tecnologías de la Información y Comunicaciones* Servicio Andaluz de Salud. Consejería de Salud de la Junta de Andalucía _a__ntonio.trujillo__.sspa@juntadeandalucia.es_ <mailto:cilia.herraiz.s...@juntadeandalucia.es> Tel. +34 670947670 747670)
dhcpcd y 802.1x
Por lo visto en las ultimas versiones el dhcpd ha pasado de ser un programa (dhclient) que lanzava el networking cuando se configura en /etc/network/interfaces a un servicio propio que ignora el interfaces. Estoy teniendo problemas con una validación 802.1x, pues se lanza el dghcpd antes del wpasupplicant con lo que el equipo es asignado por el conmutador a una vlan incorrecta. Este es mi fichero interfaces: auto lo iface lo inet loopback allow-hotplug eth0 iface eth0 inet manual wpa-driver wired wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf wpa-iface eth0 iface default inet dhcp No se puede desinstalar por dependencias, como solución desactivo el dhcpd con *systemctl disable dhcpcd* *¿hay una forma mas correcta que no pase por tener que tener instalado un programa que no voy a usar?* ** -- *Antonio Trujillo Carmona* *Técnico de redes y sistemas.* *Subdirección de Tecnologías de la Información y Comunicaciones* Servicio Andaluz de Salud. Consejería de Salud de la Junta de Andalucía _a__ntonio.trujillo__.sspa@juntadeandalucia.es_ <mailto:cilia.herraiz.s...@juntadeandalucia.es> Tel. +34 670947670 747670)
Re: WPA supplicant configured with static IP inside /etc/network/interfaces invokes dhcpcd
supersonicsnow a écrit : > > *I expect that dhcpcd should not be involved at all with**my STATIC > wlan0, is that correct?* IIUC, not any more if you have dhcpcd5 (the only version available in the current stable Jessie). It is an autonomous daemon which detects when an interface is up and tries to configure it, unless configured otherwise.
Re: WPA supplicant configured with static IP inside /etc/network/interfaces invokes dhcpcd
supersonicsnow wrote: > *I expect that dhcpcd should not be involved at all with**my STATIC > wlan0, is that correct?* > 1. Can you please confirm this behavior is a bug. > 2. Do you know what package is responsible for the faulty behavior? My > best guess would be: ifupdown? you might have some network manager running - at least in my case. I solved all similar issue by disabling all setup in interfaces and using the manager to handle all of it. regards
WPA supplicant configured with static IP inside /etc/network/interfaces invokes dhcpcd
When I try this: /etc/network/interfaces auto wlan0 allow-hotplug wlan0 iface wlan0 inet static address 192.168.0.123 netmask 255.255.255.0 gateway 192.168.0.1 dns-nameservers 8.8.8.8 8.8.4.4 *resolvconf makes 2 entries as expected inside the resolv.conf**file* nameserver 8.8.8.8 nameserver 8.8.4.4 *Alright, but I still need to connect to a network. So I add this stuff underneath:* wpa-scan-ssid 1 wpa-ap-scan 1 wpa-key-mgmt WPA-PSK wpa-proto RSN WPA wpa-pairwise CCMP TKIP wpa-group CCMP TKIP wpa-ssid "blah" wpa-psk blahblah *I get a static IP on the network and connect successfully, but now resolv.conf file is polluted with junk created by dhcpcd* _$ resolvconf -l_ # resolv.conf from wlan0 # Generated by dhcpcd from wlan0 nameserver 192.168.0.1 # resolv.conf from wlan0:ra # Generated by dhcpcd from wlan0:ra nameserver fe80::1%wlan0 # resolv.conf from wlan0.inet # Generated by ifup for wlan0.inet nameserver 8.8.8.8 nameserver 8.8.4.4 *I expect that dhcpcd should not be involved at all with**my STATIC wlan0, is that correct?* 1. Can you please confirm this behavior is a bug. 2. Do you know what package is responsible for the faulty behavior? My best guess would be: ifupdown? Thanks
Re: How to enforce use of dhcpcd instead of dhclient in debian/testing?
wzab w...@ise.pw.edu.pl: I have a problem with wireless networking on my laptop (uses iwl3945 wireless). When dhclient3 is used to obtain IP address via DHCP, the connection is unstable. Especially when I move my laptop to another location and switch to another network, the IP is not obtained at all or connection is established only for a very short time. I was able to fix it by uninstalling the dhcp3-client package. In this case the dhcpcd is used for obtaining IP, which works flawlessly. Unfortunately dhcp3-client is suggested by different packages, so when I update my system it often gets reinstalled unless I explicitly deselect it. That's really tiring. File a bug report. Use reportbug. The maintainer should get back to you with good/informative explanations (in my experience). I see this as another manifestation of the CUPS vs. lp* problem; everything suggests (suggested?) CUPS, when any printer daemon should be recognized as acceptable alternatives. Just as multiple potential MTAs are acceptable. -- Any technology distinguishable from magic is insufficiently advanced. (*)http://blinkynet.net/comp/uip5.html Linux Counter #80292 - -http://www.faqs.org/rfcs/rfc1855.htmlPlease, don't Cc: me. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b8c555...@news.
How to enforce use of dhcpcd instead of dhclient in debian/testing?
Hi, I have a problem with wireless networking on my laptop (uses iwl3945 wireless). When dhclient3 is used to obtain IP address via DHCP, the connection is unstable. Especially when I move my laptop to another location and switch to another network, the IP is not obtained at all or connection is established only for a very short time. I was able to fix it by uninstalling the dhcp3-client package. In this case the dhcpcd is used for obtaining IP, which works flawlessly. Unfortunately dhcp3-client is suggested by different packages, so when I update my system it often gets reinstalled unless I explicitly deselect it. That's really tiring. Is there any way to assign dhcpcd higher priority than dhclient3 when my system is going to obtain IP? -- TIA, Wojtek -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100218081259.ga30...@localhost
Re: How to enforce use of dhcpcd instead of dhclient in debian/testing?
Is there any way to assign dhcpcd higher priority than dhclient3 when my system is going to obtain IP? hello. there is a configuration file /etc/dhcp3/dhclient.conf you can try any options which will help disable dhclient or give priority to dhcpd. Also do man dhclient.conf for options. /Jeffrin. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100218163319.ga3...@debianlabs
Re: How to enforce use of dhcpcd instead of dhclient in debian/testing?
On 2010-02-18, wzab w...@ise.pw.edu.pl wrote: Hi, I have a problem with wireless networking on my laptop (uses iwl3945 wireless). When dhclient3 is used to obtain IP address via DHCP, the connection is unstable. Especially when I move my laptop to another location and switch to another network, the IP is not obtained at all or connection is established only for a very short time. I was able to fix it by uninstalling the dhcp3-client package. In this case the dhcpcd is used for obtaining IP, which works flawlessly. Unfortunately dhcp3-client is suggested by different packages, so when I update my system it often gets reinstalled unless I explicitly deselect it. That's really tiring. Is there any way to assign dhcpcd higher priority than dhclient3 when my system is going to obtain IP? The wicd package (an alternative to network-manager) can help you here. It allows the user to specify which DHCP client to favour. It is available in backports, squeeze and sid. -- Liam O'Toole Birmingham, United Kingdom -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnhnqjin.4in.liam.p.oto...@dipsy.selfip.org
Re: Is there a reason why dhclient is Debian's default DHCP client instead of dhcpcd?
I don't know and there are many other choices I wonder about. It would be nice if there was a page somewhere discussing the choices of default packages, and reasons thereof. For example, why old vi (nvi?) over vim. --kj -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Is there a reason why dhclient is Debian's default DHCP client instead of dhcpcd?
kj wrote: I don't know and there are many other choices I wonder about. It would be nice if there was a page somewhere discussing the choices of default packages, and reasons thereof. For example, why old vi (nvi?) over vim. --kj Agree.. the vi-vim gizzy would go on forever however.. lol. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Is there a reason why dhclient is Debian's default DHCP client instead of dhcpcd?
kj wrote: I don't know and there are many other choices I wonder about. It would be nice if there was a page somewhere discussing the choices of default packages, and reasons thereof. For example, why old vi (nvi?) over vim. In Sid vim-tiny is Priority: important which I assume is what you mean by the default package. nvi is Priority: optional, as are vim and elvis. -- John Hasler -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Is there a reason why dhclient is Debian's default DHCP client instead of dhcpcd?
On 2009-08-12 13:11 (+0100), kj wrote: I don't know and there are many other choices I wonder about. It would be nice if there was a page somewhere discussing the choices of default packages, and reasons thereof. For example, why old vi (nvi?) over vim. I don't know about your system but Vim has been the default since Debian Etch. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Is there a reason why dhclient is Debian's default DHCP client instead of dhcpcd?
Teemu Likonen wrote: I don't know about your system but Vim has been the default since Debian Etch. Since I don't have it on my system anymore, I couldn't check :) John Hasler corrected me: vim.tiny, not nvi. Either ways vim.tiny to me is as frustrating as nvi, It's the first thing I remove after an install and replace with vim.basic Anyway, my post was not meant to be a debate about vi - just an example of something I'd like more information on. --kj -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Is there a reason why dhclient is Debian's default DHCP client instead of dhcpcd?
In 4a82e547.3050...@koffiejunkie.za.net, kj wrote: Anyway, my post was not meant to be a debate about vi - just an example of something I'd like more information on. Smaller, fewer dependencies. Both factors make the basic install faster and make replacing the default take less time for users that care. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: Is there a reason why dhclient is Debian's default DHCP client instead of dhcpcd?
kj writes: Either ways vim.tiny to me is as frustrating as nvi, It's the first thing I remove after an install and replace with vim.basic No need to remove vim-tiny. Whatever vi clone you have most recently installed will be linked to /usr/bin/vi (you can change the link with the update-alternatives program). -- John Hasler -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Is there a reason why dhclient is Debian's default DHCP client instead of dhcpcd?
Hi, As the title says, is there any reason why Debian uses dhclient as its default DHCP client rather than dhcpcd? Are there any issue with dhcpcd I'm unaware of? I'd really like to know, because as of now I'm having troubles with dhclient as it refuses to register its hostname to the DNS server: 1- http://ifireball.wordpress.com/2007/12/15/dhcp-trouble-on-debian/ 2- http://linux.derkeiler.com/Mailing-Lists/Debian/2004-02/2621.html 3- http://forums.debian.net/viewtopic.php?t=28176sid=b76de680eb90778275fb22af689aa2f2 Obviously I'm not the only one and as per the aforementioned links, I assume the problem has already been reported. I could understand some people don't want their client to register their hostname (this is how dhclient behaves by default), but then is there any way to have Debian register its hostname on boot without having to hardcode the same hostname in 3-4 configuration files[1] as doing is stupid and makes changing the hostname cumbersome. In short, I'm wondering why dhclient is still the default considering this bug/caveat and possibly if it possible to use dhcpcd as the default DHCP client on a Debian [Lenny] machine? [1] Namely /etc/hostname, /etc/network/interfaces, /etc/dhclient3/dhclient3.conf and maybe others. Regards, Vhann -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Is there a reason why dhclient is Debian's default DHCP client instead of dhcpcd?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Oli D wrote: In short, I'm wondering why dhclient is still the default considering this bug/caveat and possibly if it possible to use dhcpcd as the default DHCP client on a Debian [Lenny] machine? Just install dhcpcd (and remove dhclient). Then dhcpcd is your default. Johannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkp7M4UACgkQC1NzPRl9qEUuJACeM+b+QOcl7zUB3YpA1hvuZIl7 S1QAn1NuQQwKJgnvEi5dDHZ7K2IfS74h =Nr0n -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Re: Odd dhcpcd behaviour
I had the same problem. I have added eth0 to the line auto in /etc/network/interfaces and it worked for me: auto lo eth0 Tonny -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Odd dhcpcd behaviour
* cothrige ([EMAIL PROTECTED]) wrote: This is very strange and confusing, but I think I may have it worked out now. Nope, I was wrong. I replaced dhcpcd with dhcp-client but nothing actually changed. I still have about half of my boots coming up with no internet connection. And with nothing at all coming up during boot or in dmesg I cannot begin to guess what exactly is going wrong. But, the ifdown and ifup commands did work and so at least I won't have to reboot to get connected. Just wish I knew why I was not able to be connected as normal. Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Odd dhcpcd behaviour
On (02/11/06 09:42), cothrige wrote: Nope, I was wrong. I replaced dhcpcd with dhcp-client but nothing actually changed. I still have about half of my boots coming up with no internet connection. And with nothing at all coming up during boot or in dmesg I cannot begin to guess what exactly is going wrong. But, the ifdown and ifup commands did work and so at least I won't have to reboot to get connected. Just wish I knew why I was not able to be connected as normal. dhcp3-client is the default client these days Might be worth a try Regards Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Odd dhcpcd behaviour
* Clive Menzies ([EMAIL PROTECTED]) wrote: dhcp3-client is the default client these days Might be worth a try Many thanks Clive. I just installed this and rebooted with a successful internet connection. That is good news anyway, though it may be a one time only thing. Still, it is good so far, so just perhaps that was a part of the problem anyway. Thanks again, Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Odd dhcpcd behaviour
On Oct 31, 2006, at 10:44 PM, cothrige wrote: Recently, and I am guessing during an 'aptitude upgrade', dhcpcd was uninstalled. At the next boot I had no internet connection, and could not reinstall dhcpcd without one. I had to download the deb package on another computer and then copy it over via floppy to run dpkg -i. I mention this just in case this method makes some difference in figuring out what is going on. BTW, I did try aptitude install dhcpcd to see what would be needed first, and this was all that it seemed to want. This was really no big deal, but now things have become really strange. About half the time since this I find that after booting I have no internet connection. Ifconfig shows that eth0 is up, but there is apparently no dhcpcd operating. Right now if I run 'ps aux | grep dhcpcd' I get this: root 3730 0.0 0.0 1592 200 ? Ss 16:45 0:03 /sbin/dhcpcd-bin -h celephais -Y -N -R eth0. But, on the occasions I don't have any connection I get nothing at all from this. This is obviously annoying, but normally I would think I could work around it. However, now I am finding that to be more difficult that I would have expected. I have hunted through /etc/init.d and have found nothing which would be obvious in having the connection reprobed and set up. I tried /etc/init.d/networking force-reload, and am simply told that lo is already up and running. Of course, so is eth0, but there is no dhcpcd running, and that is what I want to get going. I have tried starting that manually but so far have been met with a number of complaints but no success. I have scanned dmesg, after both successful and unsuccessful boots, and cannot find any reference at all to dhcp and so cannot make a guess as to when and where dhcpcd is being activated or how. I also have watched during boot and don't see anything but a passing reference to eth0, but no dhcp at all. What this all means is that I have to reboot in order to get an internet connection, and that is obviously not convenient. I am wondering two things now. First, why is this not working every time? It never failed until after I discovered that dhcpcd was no longer on my computer and reinstalled it the less Second is how can I get it going after a boot so that I don't have to reboot entirely? Any suggestions or ideas are very much appreciated. The program that gets an IP address for an interface is dhclient, not dhcpd. FWIW, dhcpd is the server. I'm not sure why your system is running dhcpd at all. But the reason you don't have it when you have no ethernet connection is probably that it fails if it can't find a live network interface. I don't know why your interface is failing to come up, but next time it does, try this: ifdown eth0 sleep 5 ifup eth0 Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Odd dhcpcd behaviour
* Rick Thomas ([EMAIL PROTECTED]) wrote: The program that gets an IP address for an interface is dhclient, not dhcpd. FWIW, dhcpd is the server. I'm not sure why your system is running dhcpd at all. But the reason you don't have it when you have no ethernet connection is probably that it fails if it can't find a live network interface. This is very strange and confusing, but I think I may have it worked out now. Dhcpcd is listed via apt-cache as DHCP client for automatically configuring IPv4 networking and that does sound like what I should have running. I certainly want the automatically configured client, and dhcpcd is what would have run under Slackware. It also has worked since I installed it, at least sometimes, under Debian. But, in doing a search in apt-cache I also found dhcp-client, which is described, very helpfully, as DHCP Client. On a lark I tried installing this and was told that dhcpcd would be removed. Since I have the deb for dhcpcd on my computer now, from the last problem, I went ahead and installed dhcp-client and rebooted, and found that I am still connected. Still nothing happening during boot which would indicate that it is actually being configured, and nothing shown in dmesg either. But, it does seem to work, and perhaps now it will work with every boot. Can't figure out what exactly the differences between these clients is, but the automatic one would seem less than automatic. I don't know why your interface is failing to come up, but next time it does, try this: ifdown eth0 sleep 5 ifup eth0 Quite excellent. This is probably what I needed, and if it happens again I will certainly try it. Many thanks for this. Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Odd dhcpcd behaviour
Recently, and I am guessing during an 'aptitude upgrade', dhcpcd was uninstalled. At the next boot I had no internet connection, and could not reinstall dhcpcd without one. I had to download the deb package on another computer and then copy it over via floppy to run dpkg -i. I mention this just in case this method makes some difference in figuring out what is going on. BTW, I did try aptitude install dhcpcd to see what would be needed first, and this was all that it seemed to want. This was really no big deal, but now things have become really strange. About half the time since this I find that after booting I have no internet connection. Ifconfig shows that eth0 is up, but there is apparently no dhcpcd operating. Right now if I run 'ps aux | grep dhcpcd' I get this: root 3730 0.0 0.0 1592 200 ? Ss 16:45 0:03 /sbin/dhcpcd-bin -h celephais -Y -N -R eth0. But, on the occasions I don't have any connection I get nothing at all from this. This is obviously annoying, but normally I would think I could work around it. However, now I am finding that to be more difficult that I would have expected. I have hunted through /etc/init.d and have found nothing which would be obvious in having the connection reprobed and set up. I tried /etc/init.d/networking force-reload, and am simply told that lo is already up and running. Of course, so is eth0, but there is no dhcpcd running, and that is what I want to get going. I have tried starting that manually but so far have been met with a number of complaints but no success. I have scanned dmesg, after both successful and unsuccessful boots, and cannot find any reference at all to dhcp and so cannot make a guess as to when and where dhcpcd is being activated or how. I also have watched during boot and don't see anything but a passing reference to eth0, but no dhcp at all. What this all means is that I have to reboot in order to get an internet connection, and that is obviously not convenient. I am wondering two things now. First, why is this not working every time? It never failed until after I discovered that dhcpcd was no longer on my computer and reinstalled it the less Second is how can I get it going after a boot so that I don't have to reboot entirely? Any suggestions or ideas are very much appreciated. Many thanks, Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fetch+run extra rcS.d init script via livecd+dhcpcd
Well, i've been at this off and on today. Not much dice
to recap, I'm trying to use dhcp-client-identifier on a live cd
(eventually) so I can additional settings when they boot (without
affecting their normal setup while not on the livecd).
If someone else has invented this wheel, let me know where it is!
Just reply to the list. Thanks.
The configuration snippets and debug output follow:
dhcpd.conf (snippet)
class supalive {
#match if substring (option dhcp-client-identifier, 0, 7) = supalive;
match if substring (option dhcp-client-identifier, 1, 8) = supalive;
}
shared-network 10-40 {
#eth1:2 Link encap:Ethernet HWaddr 00:A0:C9:A4:C4:2F
# inet addr:10.40.255.254 Bcast:10.40.255.255 Mask:255.255.0.0
subnet 10.40.0.0 netmask 255.255.0.0 {
pool {
allow members of supalive;
range 10.40.0.2 10.40.255.254;
option routers 10.40.0.1;
option root-path riddle:/var/diskless/x86;
filename /tftpboot/linux.x86-diskless-live;
}
}
#eth1 Link encap:Ethernet HWaddr 00:A0:C9:A4:C4:2F
# inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0
subnet 10.0.0.0 netmask 255.255.255.0 {
pool {
deny members of supalive;
range 10.0.0.2 10.0.0.254;
option domain-name-servers 10.0.0.1;
option routers 10.0.0.1;
}
}
}
dhcpd3 -d -f
DHCPDISCOVER from 00:02:2a:c7:ca:eb via eth1
DHCPOFFER on 10.0.0.241 to 00:02:2a:c7:ca:eb via eth1
DHCPREQUEST for 10.0.0.241 (10.0.0.1) from 00:02:2a:c7:ca:eb via eth1
DHCPACK on 10.0.0.241 to 00:02:2a:c7:ca:eb via eth1
I want this to be in the 10.40.x.x range
tcpdump -i eth1 -lenx -s 1500 port bootps or port bootpc | dhcpdump
TIME: 05:48:24.536120
IP: 0.0.0.0.68 (00:02:2a:c7:ca:eb) (ff:ff:ff:ff:ff:ff)
OP: 1 (BOOTPREQUEST)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 0
XID: c5b8a94f
SECS: 0
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 0.0.0.0
CHADDR: 00:02:2a:c7:ca:eb:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: .
OPTION: 53 ( 1) DHCP message type 1 (DHCPDISCOVER)
OPTION: 50 ( 4) Request IP address10.0.0.241
OPTION: 55 ( 9) Parameter Request List 1 (Subnet mask)
28 (Broadcast address)
2 (Time offset)
3 (Routers)
15 (Domainname)
6 (DNS server)
12 (Host name)
44 (NetBIOS name server)
47 (NetBIOS scope)
OPTION: 61 ( 8) Client-identifier 73:75:70:61:6c:69:76:65
---
TIME: 05:48:25.000438
IP: 10.0.0.1.67 (00:a0:c9:a4:c4:2f) (00:02:2a:c7:ca:eb)
OP: 2 (BOOTPREPLY)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 0
XID: c5b8a94f
SECS: 0
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 10.0.0.241
SIADDR: 0.0.0.0
GIADDR: 0.0.0.0
CHADDR: 00:02:2a:c7:ca:eb:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: .
OPTION: 53 ( 1) DHCP message type 2 (DHCPOFFER)
OPTION: 54 ( 4) Server identifier 10.0.0.1
OPTION: 51 ( 4) IP address leasetime 846000 (1w2d19h)
OPTION: 1 ( 4) Subnet mask 255.255.255.0
OPTION: 3 ( 4) Routers 10.0.0.1
OPTION: 15 ( 9) Domainnameexample.com
OPTION: 6 ( 4) DNS server10.0.0.1
---
TIME: 05:48:25.001001
IP: 0.0.0.0.68 (00:02:2a:c7:ca:eb) (ff:ff:ff:ff:ff:ff)
OP: 1 (BOOTPREQUEST)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 0
XID: c5b8a94f
SECS: 0
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 0.0.0.0
CHADDR: 00:02:2a:c7:ca:eb:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: .
OPTION: 53 ( 1) DHCP message type 3 (DHCPREQUEST)
OPTION: 54 ( 4) Server identifier 10.0.0.1
OPTION: 50 ( 4) Request IP address10.0.0.241
OPTION: 55 ( 9) Parameter Request List 1 (Subnet mask)
28 (Broadcast address)
2 (Time offset)
3 (Routers)
15 (Domainname)
6 (DNS server)
12 (Host name)
44 (NetBIOS name server)
47 (NetBIOS scope)
OPTION: 61 ( 8) Client-identifier 73:75:70:61:6c:69:76:65
Re: fetch+run extra rcS.d init script via livecd+dhcpcd
I think I've found a lead to answer my question. http://lists.netisland.net/archives/plug/plug-2005-02/msg00210.html I'll have to try, and follow up later. Chow.
fetch+run extra rcS.d init script via livecd+dhcpcd
I'd like to roll my own livecd (anything debian proper, or debian like will do). The one piece of my puzzle I'm still puzzled about is allowing the cd to make a dhcp request I can distinguish as coming from the livecd. Based on that, I'd also like to offer an init script (gpg signature thereof might be cool to) via tftp/http/https/ftp etc, for the livecd to download. I'm sure you can visualize as I do, that anything is possible after that... After the livecd is built, I can update the initscript that'll be run after ip assignment on demand. To give a little more background, there are about 20 workstations I'd like to put to work on a task while employees are not on the clock. They simply pop the cd in, reboot and walk away. After they arrive, they interrupt it and restart the system, removing the cd and work as usual. Is there a livecd that already offers something like this? Thanks.
Re: dhcpcd loses IP address after update [debian unstable]
What other programs cause similar behaviour? (like zeroconf) I been wrestling with my wireless card and it keeps dropping my connection after a while. i thought it was my driver, but it is probably something like zeroconf (and I will check when I get out of work), What is it about the ifconfig listing that gives it away as running zeroconf? Anton Andrew Sackville-West wrote: On Tue, May 02, 2006 at 06:37:56PM -0700, Jan Scheffczyk wrote: Hi, I am running debian unstable and just upgraded the system. I use dhcpcd (2.0.3) as DHCP client, which worked fine until the update. So, now I dhcpcd gets everything from the DHCP server but seems to forget it almost immediately (it then falls back to some IPv4 link-local address). Here is how it goes: So it seems that the IP Addr gets lost somewhere. I am not aware of any other network configuration software that is running. As an exercise I even deleted everything from /etc/rc2.d in order to eliminate interferences with any other deamons. Nothing changed, though. [...ifconfig outputs showing typical zeroconf stuff ...] my /etc/network/interfaces looks like this: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp Do you have any ideas about this strange behavior? Any help would be greatly appreciated. you probably have isntalled the zeroconf package. If you don't need it, you can purge it and thatll probably solve your issue. A signature.asc Description: OpenPGP digital signature
Re: dhcpcd loses IP address after update [debian unstable]
On Wed, May 03, 2006 at 11:35:56 +0100, Anton Piatek wrote: What other programs cause similar behaviour? (like zeroconf) I been wrestling with my wireless card and it keeps dropping my connection after a while. i thought it was my driver, but it is probably something like zeroconf (and I will check when I get out of work), What is it about the ifconfig listing that gives it away as running zeroconf? Seeing an IP address in the 169.254.0.0/16 range. This is a private range which is often used for ad-hoc networks without a gateway (for example to exchange data between two laptops directly). The purpose of zeroconf is to make it easy set this up, but unfortunately it does so even if it is not wanted. -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dhcpcd loses IP address after update [debian unstable]
Hi, I am running debian unstable and just upgraded the system. I use dhcpcd (2.0.3) as DHCP client, which worked fine until the update. So, now I dhcpcd gets everything from the DHCP server but seems to forget it almost immediately (it then falls back to some IPv4 link-local address). Here is how it goes: - ifup eth0 ... dhcpcd.exe confirms IP Addr 192.150.186.186 - ifconfig (immediately after) eth0 Link encap:Ethernet HWaddr 00:06:5B:89:58:F8 inet addr:192.150.186.186 Bcast:192.150.186.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3194 errors:0 dropped:0 overruns:1 frame:0 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:316287 (308.8 KiB) TX bytes:3498 (3.4 KiB) Interrupt:11 Base address:0xa000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:276 (276.0 b) TX bytes:276 (276.0 b) - ifconfig (again some seconds later) eth0 Link encap:Ethernet HWaddr 00:06:5B:89:58:F8 inet addr:169.254.204.255 Bcast:169.254.255.255 Mask:255.255.0.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3343 errors:0 dropped:0 overruns:1 frame:0 TX packets:23 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:331386 (323.6 KiB) TX bytes:3558 (3.4 KiB) Interrupt:11 Base address:0xa000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:276 (276.0 b) TX bytes:276 (276.0 b) So it seems that the IP Addr gets lost somewhere. I am not aware of any other network configuration software that is running. As an exercise I even deleted everything from /etc/rc2.d in order to eliminate interferences with any other deamons. Nothing changed, though. my /etc/network/interfaces looks like this: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp Do you have any ideas about this strange behavior? Any help would be greatly appreciated. Many Thanks, Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcpcd loses IP address after update [debian unstable]
On Tue, May 02, 2006 at 06:37:56PM -0700, Jan Scheffczyk wrote: Hi, I am running debian unstable and just upgraded the system. I use dhcpcd (2.0.3) as DHCP client, which worked fine until the update. So, now I dhcpcd gets everything from the DHCP server but seems to forget it almost immediately (it then falls back to some IPv4 link-local address). Here is how it goes: So it seems that the IP Addr gets lost somewhere. I am not aware of any other network configuration software that is running. As an exercise I even deleted everything from /etc/rc2.d in order to eliminate interferences with any other deamons. Nothing changed, though. [...ifconfig outputs showing typical zeroconf stuff ...] my /etc/network/interfaces looks like this: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp Do you have any ideas about this strange behavior? Any help would be greatly appreciated. you probably have isntalled the zeroconf package. If you don't need it, you can purge it and thatll probably solve your issue. A signature.asc Description: Digital signature
Re: dhcpcd loses IP address after update [debian unstable]
you probably have isntalled the zeroconf package. If you don't need it, you can purge it and thatll probably solve your issue. It did :- Thanks so much, Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: dhcpcd weirdness
did you once live in apple valley? Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dpkg query table ??? dhcp3-client dhcpcd ???
Hi, ns:~# dpkg -l '*dhcp*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-=-=-== un dhcp-client none(no description available) rc dhcp3-client 3.0.1-2 DHCP Client ii dhcp3-common 3.0.1-2 Common files used by all the dhcp3* packages ii dhcpcd1.3.22pl4-21sarge1DHCP client for automatically configuring IPv4 networking. un dhcpcd-sv none(no description available) ns:~# What does rc mean in the line of dhcp3-client? I have installed dhcpcd. Before that was dhcp3-client installed, but know I can't find the binarys and apt-cache remove dhcp3-client says that the package is not instaled. Is there somewhere a explanation for that query table. I haven't found anything in man... thanks... Achim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg query table ??? dhcp3-client dhcpcd ???
On 12 Aug 2005 01:43:45 -0700, hakim [EMAIL PROTECTED] wrote: Hi, ns:~# dpkg -l '*dhcp*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-=-=-== un dhcp-client none(no description available) rc dhcp3-client 3.0.1-2 DHCP Client ii dhcp3-common 3.0.1-2 Common files used by all the dhcp3* packages ii dhcpcd1.3.22pl4-21sarge1DHCP client for automatically configuring IPv4 networking. un dhcpcd-sv none(no description available) ns:~# What does rc mean in the line of dhcp3-client? Removed; configuration files remain. Use apt-get --purge remove dhcp3-client to fully remove it. I have installed dhcpcd. Before that was dhcp3-client installed, but know I can't find the binarys and apt-cache remove dhcp3-client says that the package is not instaled. Is there somewhere a explanation for that query table. I haven't found anything in man... It's at the top: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description Desired=(R)emove, Status =(C)onfig-files
dhcpcd
bonjour, dimanche, j'installai le packet debian dhcpcd (testing), pour d'obscures raisons de driver réseau (le module b44 sur un noyau 2.6 a des problèmes). -- ce matin, au boot, plus de résolution DNS...mon client dhcpcd fonctionne bien, mais: -il ne change pas le fichier resolv.conf quand il fait sa requête dhcp. -il semble avoir pris le control de ifup/ifdown... --- si je fais ifdown eth0 pour couper mon interface eth0, ifdown me dit que celle-ci n'est pas up, alors que ifconfig la montre bien up, et qu'elle peut très bien pinger. Tout indice est le bienvenu, ou devrais-je poster un bug pour le packet dhcpcd? Merci, Stan. -- Stan Pinte tel: +32 499 25 94 24
RE: dhcpcd
I finally got it working by installing dhcp using apt-get then modifying the /etc/init.d/dhcp file. I using dhcpcd, the client, and it don't install any dhcpcd or dhcp file in the /etc/init.d directory. After renaming all the rc*.d files and have them link to the new /ect/init.d/dhcpcd file I deleted the dhcp package and it works. Thanks for your help. Reaz -Original Message- From: Jeff [mailto:[EMAIL PROTECTED]] Sent: Monday, January 06, 2003 2:59 PM To: [EMAIL PROTECTED] Subject: Re: dhcpcd If you install dhcp with apt-get, it would have created the /etc/init.d/dhcp, so if it's not there it was removed. You could purge dhcp and reinstall it: # apt-get remove --purge dhcp # apt-get install dhcp and that should put it back to a good starting point. jc -- Jeff CoppockSystems Engineer Diggin' Debian Admin and User -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: dhcpcd
In the initial stages of trying to get this working I did this and it didn't work. I had to setup a file in /etc/init.d/ then have it start on boot up. I don't know why it didn't work, maybe the dhcp client program wasn't running at the time the interfaces came up. Thanks for our suggestion. Reaz -Original Message- From: Shyamal Prasad [mailto:[EMAIL PROTECTED]] Sent: Monday, January 06, 2003 10:58 PM To: [EMAIL PROTECTED] Subject: Re: dhcpcd Reaz == Reaz Baksh [EMAIL PROTECTED] writes: Reaz Hello I am using dhcpcd for my dhcp client. How and what do Reaz I set so that the command: 'dhcpcd -d eth1' is run on start Reaz up. Reaz Thanks for any help The best way to do this is via the /etc/network/interfaces file. It will run your dhcp client for you on start up. See 'man interfaces'. You want something like this: auto eth1 iface eth1 inet dhcp Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcpcd
Reaz Baksh, 2003-Jan-05 20:28 -0500: I looked for the /etc/init.d/dhcp file but it's not there. I assume I'll have to manually create it. I installed using apt-get. I'm still learning and understanding the startup files in the rc folders, until I complete that task I guess I'll have to manually start it after each reboot. Is there an automated way to do this? Reaz -Original Message- From: Jeff [mailto:[EMAIL PROTECTED]] Sent: Saturday, January 04, 2003 1:31 AM To: [EMAIL PROTECTED] Subject: Re: dhcpcd Edit /etc/init.d/dhcp and you'll find a line that triggers it to start at boot and another line in the start section that you can set the interface to run it on. jc If you install dhcp with apt-get, it would have created the /etc/init.d/dhcp, so if it's not there it was removed. You could purge dhcp and reinstall it: # apt-get remove --purge dhcp # apt-get install dhcp and that should put it back to a good starting point. jc -- Jeff CoppockSystems Engineer Diggin' Debian Admin and User -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcpcd
Reaz == Reaz Baksh [EMAIL PROTECTED] writes: Reaz Hello I am using dhcpcd for my dhcp client. How and what do Reaz I set so that the command: 'dhcpcd -d eth1' is run on start Reaz up. Reaz Thanks for any help The best way to do this is via the /etc/network/interfaces file. It will run your dhcp client for you on start up. See 'man interfaces'. You want something like this: auto eth1 iface eth1 inet dhcp Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: dhcpcd
I looked for the /etc/init.d/dhcp file but it's not there. I assume I'll have to manually create it. I installed using apt-get. I'm still learning and understanding the startup files in the rc folders, until I complete that task I guess I'll have to manually start it after each reboot. Is there an automated way to do this? Reaz -Original Message- From: Jeff [mailto:[EMAIL PROTECTED]] Sent: Saturday, January 04, 2003 1:31 AM To: [EMAIL PROTECTED] Subject: Re: dhcpcd Edit /etc/init.d/dhcp and you'll find a line that triggers it to start at boot and another line in the start section that you can set the interface to run it on. jc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dhcpcd
Hello I am using dhcpcd for my dhcp client. How and what do I set so that the command: 'dhcpcd -d eth1' is run on start up. Thanks for any help Reaz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcpcd
Reaz Baksh, 2003-Jan-04 01:08 -0500: Hello I am using dhcpcd for my dhcp client. How and what do I set so that the command: 'dhcpcd -d eth1' is run on start up. Thanks for any help Edit /etc/init.d/dhcp and you'll find a line that triggers it to start at boot and another line in the start section that you can set the interface to run it on. jc -- Jeff CoppockSystems Engineer Diggin' Debian Admin and User -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: /etc/dhcpc/dhcpcd-eth0.exe
On Thu 19 Dec 2002 00:32:32 +0100 [EMAIL PROTECTED] wrote: I use ddts (http://www.ddts.org/) and there's a debian package that polls the central server every minute and update the ip when it polls. I'm using dyndns.org, and they'd block the service to me if I did that. That's probably the case of the OP, so he must find other ways to keep his ip current in the server's database without flooding it with constant, unnecessary updates. -- Carlos Sousa http://vbc.dyndns.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: /etc/dhcpc/dhcpcd-eth0.exe
On Wed, Dec 18, 2002 at 01:58:32PM -0800, Expert User wrote: When the dhcpclient used to be dhcpcd, there was a way to run some script after the dhcp has run by putting a script in /etc/dhcpc/dhcpcd-eth0.exe. Now that I have dhclient, how do I achieve the same result? I learned from the man page that there is /etc/dhclient-exit-hooks script I can create, but how to associate it with a perticular interface? check $reason and $interface within your /etc/dhclient-exit-hooks script? -- groetjes, carel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
/etc/dhcpc/dhcpcd-eth0.exe
When the dhcpclient used to be dhcpcd, there was a way to run some script after the dhcp has run by putting a script in /etc/dhcpc/dhcpcd-eth0.exe. Now that I have dhclient, how do I achieve the same result? I learned from the man page that there is /etc/dhclient-exit-hooks script I can create, but how to associate it with a perticular interface? I need this to run my Dynamic DNS update script, everytime my IP changes. Thanks, amit msg19954/pgp0.pgp Description: PGP signature
Re: /etc/dhcpc/dhcpcd-eth0.exe
[EMAIL PROTECTED] (Expert User) wrote: When the dhcpclient used to be dhcpcd, there was a way to run some script after the dhcp has run by putting a script in /etc/dhcpc/dhcpcd-eth0.exe. Now that I have dhclient, how do I achieve the same result? I learned from the man page that there is /etc/dhclient-exit-hooks script I can create, but how to associate it with a perticular interface? I need this to run my Dynamic DNS update script, everytime my IP changes. I use ddts (http://www.ddts.org/) and there's a debian package that polls the central server every minute and update the ip when it polls. So when i install that client i only need to open the appropriate port and my ip is updated every minute. Your DNS service might (and probably does) have such a script to do this. Why not run it every x minute(s) instead of only when the ip changes? It doesn't take a lot of bandwidth or cpu time to do so. You can probably make a cron job out of it too. Regards, Benedict -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
hostname in dhcpcd
I am running Woody and kernel 2.4.18 and installed dhcpcd from potato (because it was recommended). I am properly pulling an IP from my DHCP server, which is nice, but now I cannot use an entry in /etc/hosts to map my IP to my hostname (since it's no longer static). When I try to ping my hostname it says unknown host. The only reason I need to connect to myself is for webmin (it doesn't seem to like 'localhost'), but I would think there is a relatively easy way to do this that I am not aware of. Any help is appreciated .. Thanks, Andrew. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: hostname in dhcpcd
On Wed, 19 Jun 2002 17:22:13 -0400, Andrew Biggadike wrote: I am running Woody and kernel 2.4.18 and installed dhcpcd from potato (because it was recommended). I am properly pulling an IP from my DHCP server, which is nice, but now I cannot use an entry in /etc/hosts to map my IP to my hostname (since it's no longer static). When I try to ping my hostname it says unknown host. The only reason I need to connect to myself is for webmin (it doesn't seem to like 'localhost'), but I would think there is a relatively easy way to do this that I am not aware of. Any help is appreciated .. Thanks, Andrew. Wouldn't the line; 127.0.0.1 localhost host name work? -- gt It is interesting to note that as one evil empire (generic) fell, another Evil Empire (tm) began its nefarious rise. -- gt Coincidence? I think not. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Modulos+Placas+Dhcpcd
Gracias por los consejos, ya va tomando forma esto. Por ahora lo unico que logré es que al iniciar y hacer lsmod me aparezca la placa pero sin usar, y tengo que hacer ifconfig eth0 up dhcpcd. Cómo podría hacer para no tener que repetir estos ultimos pasos?? Ariel El dom, 24-02-2002 a las 19:45, Peperino Pomuro escribió: bueno... tendrias que pedirle que te levante el modulo al iniciar el sistema, asi que modconf y elegi el modulo para que arranque cuando inicias la pc. segundo, vas a tener que postear el /etc/network/interfaces y ver si tenes todo bien ahi, porque una vez que el modulo levante al arranque posteriormente deberia levantarte la placa de red y configurarla como dhcp pero eso si te levanta el modulo, y si tenes bien el archivo.. postealo y lo vemos... saludos - Original Message - From: Ariel Jolodovsky [EMAIL PROTECTED] To: debian-user-spanish@lists.debian.org Sent: Sunday, February 24, 2002 7:07 PM Subject: Modulos+Placas+Dhcpcd Hola, tengo Fibertel de 512kbps, el problema es que cuando me logueo, ya sea como un usuario comun o como root, tengo que levantar a mano el modulo de la placa (RealTek 8139too). Cuando entro en mi sesion tengo que poner las siguientes lineas para entar a internet. # modprobe rtl8139 # ifconfig eth0 up # dhcpcd Luego de eso esta todo bien, pero si no escribo esas lineas no tengo internet. Alguna sugerencia de como hacer para que no tenga que escribir eso cada vez que entro en el sistema?? Ariel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Modulos+Placas+Dhcpcd
Hola, tengo Fibertel de 512kbps, el problema es que cuando me logueo, ya sea como un usuario comun o como root, tengo que levantar a mano el modulo de la placa (RealTek 8139too). Cuando entro en mi sesion tengo que poner las siguientes lineas para entar a internet. # modprobe rtl8139 # ifconfig eth0 up # dhcpcd Luego de eso esta todo bien, pero si no escribo esas lineas no tengo internet. Alguna sugerencia de como hacer para que no tenga que escribir eso cada vez que entro en el sistema?? Ariel
RE: Modulos+Placas+Dhcpcd
Hola, tengo Fibertel de 512kbps, el problema es que cuando me logueo, ya sea como un usuario comun o como root, tengo que levantar a mano el modulo de la placa (RealTek 8139too). Cuando entro en mi sesion tengo que poner las siguientes lineas para entar a internet. # modprobe rtl8139 prueba insmod 8139too y si sigue pasando recompila el kernel con el driver instalado no como modulo # ifconfig eth0 up eso tienes que entrar en /etc/network/interfaces y pon una linea asi auto eth0 iface eth0 inet dynamic # dhcpcd mmm no se pero fijate en el init.d si tiene algun script que lo inicia y cheka que el script funcione sino hazte uno propio y ponlo en el init con update-rc.d o ponlo en el rc.boot. un script sencillo #!/bin/bash echo Configurando internet dhcpcd echo Done espero haberte ayudado Luego de eso esta todo bien, pero si no escribo esas lineas no tengo internet. Alguna sugerencia de como hacer para que no tenga que escribir eso cada vez que entro en el sistema?? Ariel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Modulos+Placas+Dhcpcd
On 24 Feb 2002 19:07:53 -0300 Ariel Jolodovsky [EMAIL PROTECTED] wrote: Hola, tengo Fibertel de 512kbps, el problema es que cuando me logueo, ya sea como un usuario comun o como root, tengo que levantar a mano el modulo de la placa (RealTek 8139too). Cuando entro en mi sesion tengo que poner las siguientes lineas para entar a internet. # modprobe rtl8139 # ifconfig eth0 up Fijate de levantar la placa con el modconf o fijate en /etc/modules, en ese archivo mete todo lo que carga al principio y en /etc/modutils/* pone las opciones correspondientes a cada cosa. # dhcpcd Luego de eso esta todo bien, pero si no escribo esas lineas no tengo internet. Alguna sugerencia de como hacer para que no tenga que escribir eso cada vez que entro en el sistema?? Ariel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
What happened to dhcpcd
Hello, can anyone tell me why there is no longer any packages for dhcpcd in testing or unstable. I'd rather not use pump, since I've heard that it has problems with multiple interfaces. dhcpcd is in stable, and is what I have been using. Cameron Kerr -- [EMAIL PROTECTED] http://homepages.paradise.net.nz/~cameronk/
Re: What happened to dhcpcd
On Sun, 10 Feb 2002, Cameron Kerr wrote: Hello, can anyone tell me why there is no longer any packages for dhcpcd in testing or unstable. I'd rather not use pump, since I've heard that it has problems with multiple interfaces. dhcpcd is in stable, and is what I have been using. You're looking for the dhcp-client package. Simon
Re: What happened to dhcpcd
Cameron Kerr wrote: Hello, can anyone tell me why there is no longer any packages for dhcpcd in testing or unstable. I'd rather not use pump, since I've heard that it has problems with multiple interfaces. dhcpcd is in stable, and is what I have been using. Security problems, and crap code: http://bugs.debian.org/81627 Pump is not the only alternative, try dhclient (package dhcp-client). -- see shy jo
dhcpcd
I just upgraded my dhcpcd daemon. Each time I reboot my server, the daemon doesn't automatically load (even though is says it does). Any ideas on how I can fix this? --- Asura Owner of Dark Forest Mud darkforest.uwyo.edu 4000
Re: dhcpcd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 19 January 2002 6:10 pm, Asura wrote: I just upgraded my dhcpcd daemon. Each time I reboot my server, the daemon doesn't automatically load (even though is says it does). Have you set this in /etc/init.d/dhcp # Set run_dhcpd to 1 to start dhcpd at boot or 0 to disable it. run_dhcpd=1 - -- Alan - [EMAIL PROTECTED] http://www.chandlerfamily.org.uk -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8SbpY1mf3M5ZDr2kRAlkeAKCMy5K3mX8/TOYMSnFSyyuTJD/4VACfb8Bb TNYkpE4Ubrit1W3qENGXei0= =GQY7 -END PGP SIGNATURE-
RE: DHCP and Adelphia Cablemodem (dhcpcd)
[Snipped suggestion to compile in CONFIG_FILTER] This worked. It worked really well. DHCP now appears to work with one minor problem-- It appears that the DNS isn't being caught by the DHCP-Client. My resolv.conf is left with nothing but search in it-- and this appears to be causing some problems. I have observed no speed differences between OSes; maybe M$ would have negotiated a secret deal wherein the modem manufacturer would have embedded a secret layer which communicates with Win 9x better, Hehe ;-) Heh. It's sad that I actually had a quick debate with myself if that could really be the cause. :) The cablemdoem is still exhibiting the speed problem (really slow connection, then eventually drops conenction until power cycled). My first question is: My Debian system is a 200Mhz Pentium, not running any form of X. Is it fast enough to keep up with the cablemodem? Maybe this is the bottleneck? If so, how fast SHOULD the machine be to keep up? Secondly, could someone point me to a set of tools I can use to debug this problem? I'm currently on hold with the cable company, but I'm willing to bet that they won't have a clue what the problem could be (and will get scared off if I mention Linux..) Thanks, Mike
RE: DHCP and Adelphia Cablemodem (dhcpcd)
Oh, it's definitely fast enough. I have a Pentium90 at home and it works fine. I have heard an anecdote used before, saying a 2.2.x kernel with ipchains MASQing on a 486 50mhz with 4meg-8meg of RAM can saturate a T1 line (1.544 Mbps). I don't know the validity to it and haven't really been interested enough to look up any statistics or benchmarks. - James -Original Message- From: Michael Patterson [mailto:[EMAIL PROTECTED] Sent: Friday, November 02, 2001 11:51 AM To: Raghavendra Bhat Cc: Debian List Subject: RE: DHCP and Adelphia Cablemodem (dhcpcd) [Snipped suggestion to compile in CONFIG_FILTER] This worked. It worked really well. DHCP now appears to work with one minor problem-- It appears that the DNS isn't being caught by the DHCP-Client. My resolv.conf is left with nothing but search in it-- and this appears to be causing some problems. I have observed no speed differences between OSes; maybe M$ would have negotiated a secret deal wherein the modem manufacturer would have embedded a secret layer which communicates with Win 9x better, Hehe ;-) Heh. It's sad that I actually had a quick debate with myself if that could really be the cause. :) The cablemdoem is still exhibiting the speed problem (really slow connection, then eventually drops conenction until power cycled). My first question is: My Debian system is a 200Mhz Pentium, not running any form of X. Is it fast enough to keep up with the cablemodem? Maybe this is the bottleneck? If so, how fast SHOULD the machine be to keep up? Secondly, could someone point me to a set of tools I can use to debug this problem? I'm currently on hold with the cable company, but I'm willing to bet that they won't have a clue what the problem could be (and will get scared off if I mention Linux..) Thanks, Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: DHCP and Adelphia Cablemodem (dhcpcd)
I'm responding to everyone in one message. The cablemodem setup still isn't working. Commenting on each part individually: [Donald] ---snip--- Also, ifconfig doesn't show eth0. When I was running DHCP-client, eth0 did show up, but without an IP address (not even 0.0.0.0, which is what I was lead to believe would happen). This is not good. No dhcp client will work if the NIC isn't there! I would check and see if the NIC's driver module is being loaded (lsmod). You could also check the messages during bootup and see what is happening when it comes time for NIC detection. Have you turned off the PnP OS in your BIOS? If the NIC is NOT being recognized during bootup, you should add the appropriate driver module via using modconf so it will be properly initialized at boot time. Once you consistantly get eth0 listed on an ifconfig, then you can fine-tune the dhcpcd paramenters for your setup. When everthing is working properly, the ifconfig command should show your assigned IP from your ISP after a boot. Unforutnately, the NIC works fine-- I replaced the cablemodem with a hub and checked. This seems to have something to do with dhcpcd-- when I switched back to a static IP address, this symptom persisted. I had to remove the package to get eth0 back. [Ian] I had Adelphia Powerlink for awhile also. I did it working with OS X, FreeBSD, NetBSD, and RedHat. On redhat I used the pump utility. Sorry I don't remember the specifics. I also had it get my IP using DHCP on bootup. One snag you may run into is if you unplug the cat5 from one NIC to the next it won't work unless you completely turn off the modem, then plug the cat5 into the new NIC, and then restart the modem and let it resync. The modem uses the hardware address of the NIC for something. Power cycling the modem clears out this info. The guy who installed my cable was using Slackware with it so it must use some pretty standard tools found in all distros. I tried this out-- I went back to a fixed IP address, removed DHCP, and it worked-- for a few hours. So I powered down the modem and brought it back up-- it worked for another couple hours before quitting again. I haven't the slightest idea how to debug this, or what coudl cause it. On another note, I seem to be having speed problems on this machine through the cablemodem. I was getting blazing speeds when the win98 box was hooked up to it, but now it is much slower. Much, much slower. The differences are: New machine, linux instead of windows, and a different cable connection (different location in house). Any idea on how to test where the bottleneck is? Thanks, Mike
Re: DHCP and Adelphia Cablemodem (dhcpcd)
[Thu, Nov 01, 2001 at 09:06:15AM -0700] Michael Patterson :
The cablemodem setup still isn't working
Are you using dhcpcd on a 'Potato' box ? Can you purge the dhcpcd
package and instead, install dhcp-client ?
seems to have something to do with dhcpcd
dhcpcd never worked for me and another thing which you have to note is
that the modem at your end has already acquired an IP from the cable
server head. In your case, dhcpcd is not getting the dynamic IP
assigned to your cable modem or maybe it is your stock kernel which has
to be blamed in not letting thru a certain packet.
went back to a fixed IP address, removed DHCP, and it worked
Please do note that dhcpcd and dhcp-client are two different packages.
Another thing is that, please insert the CONFIG_FILTER module for debian
stock kernels from one of the kernel image debs. If you are brewing
your own kernels, then compile in CONFIG_FILTER under 'Networking'
options. You would also like to read under the kernel source tree, the
following note 'Documentation/networking/filter.txt'.
I could never get dhcp-client to acquire the IP from my cable modem if I
disabled this option while compiling my kernel. So watch out and read
docs related to thisYMMV.
New machine, linux instead of windows, and a different cable
connection (different location in house). Any idea on how to test
where the bottleneck is ?
I have observed no speed differences between OSes; maybe M$ would have
negotiated a secret deal wherein the modem manufacturer would have
embedded a secret layer which communicates with Win 9x better, Hehe ;-)
--
ragOO, VU2RGU http://gnuhead.net.dhis.org/ GPG: 1024D/F1624A6E
Helping to keep the Air-Waves FREE Amateur Radio
Helping to keep your Software FREE the GNU Project
Helping to keep the W W W FREE Debian GNU/${kernel}
DHCP and Adelphia Cablemodem (dhcpcd)
Yesterday I finally got my cable modem (Adelphia). Hooked it up to windows, and it worked wonderfully. I was told that, in general, Adelphia doesn't change the IP information, and it would be safe to copy it to the Debian box. So I wrote down the information, moved the cable modem over to my debian box, and set it up. It worked for about 2 hours. Presumably, the DHCP server switched my information on me. So I installed the dhcp-client package and set it up. Didn't work. So I removed that package and tried dhcpcd, which I actually had documents for. That didn't work either. Here's the information I have. It's somewhat sparse, but it's all that I could find. (information seperated by ) # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface iface lo inet loopback # The first network card - this entry was created during the Debian installation # (network, broadcast and gateway are optional) iface eth0 inet dhcp hostname cy119366-a #leasehours 1 #leasetime 3600 white:/etc/dhcpc# more config # List here the interface that the dhcpcd daemon should use. # The default is to assign an IP address to eth0. # If you want to disable the daemon, enter none here. IFACE=eth0 # Add options here, examples are: # OPTIONS='-h foo' set hostname (needed by some cablemodem providers) # OPTIONS='-l 12345' set leasetime OPTIONS='-h cy119366-a' syslog: Oct 31 00:03:14 white dhcpcd[274]: timed out waiting for a valid DHCP server response Also, ifconfig doesn't show eth0. When I was running DHCP-client, eth0 did show up, but without an IP address (not even 0.0.0.0, which is what I was lead to believe would happen). dhcpcd doesn't show up in a ps, and when run manually eventually exits without any output. All help is appreciated. --Mike
Re: DHCP and Adelphia Cablemodem (dhcpcd)
On approximately Wed, Oct 31, 2001 at 09:50:27AM -0700, Michael Patterson wrote: Yesterday I finally got my cable modem (Adelphia). Hooked it up to windows, and it worked wonderfully. I was told that, in general, Adelphia doesn't change the IP information, and it would be safe to copy it to the Debian box. So I wrote down the information, moved the cable modem over to my debian box, and set it up. It worked for about 2 hours. Presumably, the DHCP server switched my information on me. Hot sure about the dhcp th ing, but I have a cable modem, from Adelphia even! I have used the same IP address that I was given when I first signed up. I have never used dhcp, and all has been well for a very long time. I am going on 2 yesrs with the same IP address. Josh -- Linux, the choice| I have gained this by philosophy: that I do of a GNU generation -o)| without being commanded what others do only Kernel 2.4.13-ac5 /\| from fear of the law. -- Aristotle on a i586 _\_v | |
Re: DHCP and Adelphia Cablemodem (dhcpcd)
Thus spake Michael Patterson: Yesterday I finally got my cable modem (Adelphia). Hooked it up to windows, and it worked wonderfully. I was told that, in general, Adelphia doesn't change the IP information, and it would be safe to copy it to the Debian box. So I wrote down the information, moved the cable modem over to my debian box, and set it up. It worked for about 2 hours. Presumably, the DHCP server switched my information on me. So I installed the dhcp-client package and set it up. Didn't work. So I removed that package and tried dhcpcd, which I actually had documents for. That didn't work either. Here's the information I have. It's somewhat sparse, but it's all that I could find. (information seperated by ) # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface iface lo inet loopback # The first network card - this entry was created during the Debian installation # (network, broadcast and gateway are optional) iface eth0 inet dhcp hostname cy119366-a #leasehours 1 #leasetime 3600 white:/etc/dhcpc# more config # List here the interface that the dhcpcd daemon should use. # The default is to assign an IP address to eth0. # If you want to disable the daemon, enter none here. IFACE=eth0 # Add options here, examples are: # OPTIONS='-h foo' set hostname (needed by some cablemodem providers) # OPTIONS='-l 12345' set leasetime OPTIONS='-h cy119366-a' syslog: Oct 31 00:03:14 white dhcpcd[274]: timed out waiting for a valid DHCP server response Also, ifconfig doesn't show eth0. When I was running DHCP-client, eth0 did show up, but without an IP address (not even 0.0.0.0, which is what I was lead to believe would happen). dhcpcd doesn't show up in a ps, and when run manually eventually exits without any output. All help is appreciated. --Mike Mike - I'm doing this from memory, as I'm not at home, but I think trying a couple things might help get you somewhere. Try setting interfaces to static again and restarting your network - does it come up? If so they haven't actually changed your IP. Just because it's a DHCP server, doesn't mean they always change it (I don't want to include stuff you already know - just trying to cover bases). If that doesn't work, try setting it back to dhcp and include the word auto - that'll bring it up at boot and so on. Then I think the dhcp-client package is the one you want - dhcpd includes tools for serving dhcp, AFAICR. In /etc/dhcpsomething - c? client? not sure.conf you'll want to put your hostname. Then try restarting your network, and check your logs. Good luck, Steve -- Don't discount flying pigs before you have good air defense. -- [EMAIL PROTECTED]
Re: DHCP and Adelphia Cablemodem (dhcpcd)
On Wed, Oct 31, 2001 at 09:50:27AM -0700, Michael Patterson wrote: Yesterday I finally got my cable modem (Adelphia). Hooked it up to windows, and it worked wonderfully. I was told that, in general, Adelphia doesn't change the IP information, and it would be safe to copy it to the Debian box. So I wrote down the information, moved the cable modem over to my debian box, and set it up. It worked for about 2 hours. Presumably, the DHCP server switched my information on me. So I installed the dhcp-client package and set it up. Didn't work. So I removed that package and tried dhcpcd, which I actually had documents for. That didn't work either. Here's the information I have. It's somewhat sparse, but it's all that I could find. (information seperated by ) # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface iface lo inet loopback # The first network card - this entry was created during the Debian installation # (network, broadcast and gateway are optional) iface eth0 inet dhcp hostname cy119366-a #leasehours 1 #leasetime 3600 white:/etc/dhcpc# more config # List here the interface that the dhcpcd daemon should use. # The default is to assign an IP address to eth0. # If you want to disable the daemon, enter none here. IFACE=eth0 # Add options here, examples are: # OPTIONS='-h foo' set hostname (needed by some cablemodem providers) # OPTIONS='-l 12345' set leasetime OPTIONS='-h cy119366-a' syslog: Oct 31 00:03:14 white dhcpcd[274]: timed out waiting for a valid DHCP server response Also, ifconfig doesn't show eth0. When I was running DHCP-client, eth0 did show up, but without an IP address (not even 0.0.0.0, which is what I was lead to believe would happen). dhcpcd doesn't show up in a ps, and when run manually eventually exits without any output. All help is appreciated. --Mike I had Adelphia Powerlink for awhile also. I did it working with OS X, FreeBSD, NetBSD, and RedHat. On redhat I used the pump utility. Sorry I don't remember the specifics. I also had it get my IP using DHCP on bootup. One snag you may run into is if you unplug the cat5 from one NIC to the next it won't work unless you completely turn off the modem, then plug the cat5 into the new NIC, and then restart the modem and let it resync. The modem uses the hardware address of the NIC for something. Power cycling the modem clears out this info. The guy who installed my cable was using Slackware with it so it must use some pretty standard tools found in all distros. Good Luck, Ian -- FreeSoftware Developer and user of Debian GNU/Linux _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: DHCP and Adelphia Cablemodem (dhcpcd)
Michael Patterson wrote: ---snip--- Also, ifconfig doesn't show eth0. When I was running DHCP-client, eth0 did show up, but without an IP address (not even 0.0.0.0, which is what I was lead to believe would happen). This is not good. No dhcp client will work if the NIC isn't there! I would check and see if the NIC's driver module is being loaded (lsmod). You could also check the messages during bootup and see what is happening when it comes time for NIC detection. Have you turned off the PnP OS in your BIOS? If the NIC is NOT being recognized during bootup, you should add the appropriate driver module via using modconf so it will be properly initialized at boot time. Once you consistantly get eth0 listed on an ifconfig, then you can fine-tune the dhcpcd paramenters for your setup. When everthing is working properly, the ifconfig command should show your assigned IP from your ISP after a boot. Cheers, -Don Spoon-
ifup eth0 - preventing dhcpcd replacing /etc/resolv.conf
I've given up using pump -- it doesn't work properly with my cable modem provider, and switched to dhcpcd. I'm having problems stopping it from replacing my /etc/resolv.conf file (I'm using a local nameserver). Now, because dhcpcd is started from ifup, rather than from the startup scripts, it ignores the contents of /etc/dhcpc/config, so I can't find a way to add the '-R' switch needed to get it to leave resolv.conf alone. A friend of mine is using dhcpcd, but he's not having these problems -- he can't remember what he did to fix it, but we suspect that it might be because his external interface is eth1, not eth0. Could this be the case, or is it a red herring? I've managed to fix it by hacking on /etc/init.d/dhcpcd to make /sbin/dhcpcd point to a wrapper script (/sbin/dhcpcd-wrapper), which sources /etc/dhcpc/config and then runs the relevant dhcpcd-2.x, passing the options. I don't particularly like hacking on startup scripts installed by Debian packages -- it'll come time to upgrade, the package installer will complain, and I'll have forgotten what I did to get it to work. Is there a better solution? Cheers, Roger.
Re: ifup eth0 - preventing dhcpcd replacing /etc/resolv.conf
On Wed, Aug 29, 2001 at 08:52:39AM +0100, Roger Lipscombe wrote: | I've given up using pump -- it doesn't work properly with my cable modem | provider, and switched to dhcpcd. I'm having problems stopping it from | replacing my /etc/resolv.conf file (I'm using a local nameserver). ... | A friend of mine is using dhcpcd, but he's not having these problems -- he | can't remember what he did to fix it, but we suspect that it might be | because his external interface is eth1, not eth0. Could this be the case, | or is it a red herring? I think, if you read the dhcpcd docs, that you can set some stuff in /etc/dhcpc to get custom stuff in /etc/resolv.conf. Try tweaking /etc/dhcpc/resolv.conf (while the interface is down) and then bring it back up and see what happens. ... | I don't particularly like hacking on startup scripts installed by Debian | packages -- it'll come time to upgrade, the package installer will complain, | and I'll have forgotten what I did to get it to work. This isn't so much of a problem because apt lets you see a diff of the two files. This is essential to remembering what you did :-). HTH, -D
Re: internet w/ dhcpcd
On Fri, Jun 29, 2001 at 01:53:07PM -0500, Robert Matijasec uttered: 56 data byes neighbour table overflow ping:sendto: No buffer space available ping:wrote 24.217.12.166 64 chars ret=-1 neighbour table overflow etc, etc ... Put 'auto lo' on a line by itself in /etc/network/interfaces, and 'ifup lo' You can't ping the loopback interface if it isn't up! Another thought is that you forgot loopback support in your kernel? -- Steve I'm a sysadmin because I couldn't beat a blind monkey in a coding contest. --Me pgptRHKS3FRqJ.pgp Description: PGP signature
RE: internet w/ dhcpcd
Well here is some info that you might be inerested in: Note that the way I set this up is by following the mini-dhcpcd howto. It claimed Debian would configure everything out of dpkg, so maybe I had somethin messed up earlier, I never configured the computer for inet use on install, but I don't know if that even matters. kernal is 2.2 I used to be able to ping lo and it worked fine, now I get: ping: sendto: Operation not permitted ping:wrote erdos 64 chars, ret=-1 etc, etc ... when I ping my address ( ping 24.217.273.166 ) I get 56 data byes neighbour table overflow ping:sendto: No buffer space available ping:wrote 24.217.12.166 64 chars ret=-1 neighbour table overflow etc, etc ... when I say: ping erdos (erdos is the i386's name ) it is the same as ping lo. I was getting other ping errors but right now I can't recreate them. Are you supposed to be able to do a ping eth0 ??? b/c I can't. route -n yields: Kernel IP routing table Destination Gateway Genmask Flasgs Metric Ref Use Iface 24.217.160.00.0.0.0 255.255.240.0 U 0 0 0 eth0 0.0.0.0 24.217.160.10.0.0.0 UG 0 0 0 eth0 ifconfig yields: eth0Link encap:Ethernet HWaddr 00:A0:24:74:4B:F8 inet addr:24.217.273.166 Bcast:255.5\255.255.255 Mask:255.255.240.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:101 error:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txquiuelen:100 Interrupt:10 Base adress:0x300 Some other files: /etc/resolv.conf - /etc/dhcpcd/resolv.conf domain nameserver 24.217.0.3 nameserver 24.217.0.4 /etc/network/interfaces iface lo inet loopback /etc/modules alias eth0 3c509 options th0 io=0x300 irq=10 Maybe I assigned wrong io ports and/or irq for card, but don't think this is the case... At the end of dmesg there is eth0: 3c509 at 0x300 tag 1, 10baseTport, address 00a024 74 4b f8, IRQ 10. 3c509.c:1.16 (2.2) 2/3/98 [EMAIL PROTECTED] ...some other stuff ... Packet log:input DENY eth0 PROTO=17 10.1.160.1:67 24.217.172.166:68 L=336 S=x00 I=25954 F=0x T=255 (#3) eth0: Setting Rx mode to 1 addresses. these last three lines are repeated about 50 times with different values for I, PROTO, and L. With I going to 0 PROTO cycling btw 1 and 17. and L cycling btw 53 and 84. Hope this is sufficient to hammer something out. Perhaps what might help me most is something like linuxconf. Does such a package exist for Debian? You may have noticed that I obviosly don't get the big picture as to what is supposed to be in place for all this to work. I have been cutting pasting config files for a while and with that not working I must consult a higher authority. It almost seems correct, any help would be greatly appreciated. -Andrew's First Response- Robert Matijasec writes: and it keeps trying until it times out. Where could the problem be ? It seems the system reconizes my ethernet card, and it even seems I get a connection to my provider. Can you ping your ethernet card? How about your gateway? What does % route -n tell you? pump came w/Debian install, but after putting on dhcpcd I assumed it would have been neatly removed. You can always check to see if pump is still there, using dselect or dpkg. Andrew. -Original Message- I just installed the dhcpcd package on my i386 and everything seems fine right up to the point where I want to test the connection. I type: telnet ritix.slu.edu I get: Host name lookup failure I type: telnet 165.134.123.3 I get: Trying 165.134.123.3... and it keeps trying until it times out. Where could the problem be ? It seems the system reconizes my ethernet card, and it even seems I get a connection to my provider. pump came w/Debian install, but after putting on dhcpcd I assumed it would have been neatly removed. Any ideas where the problem is ?
Re: internet w/ dhcpcd
Hi, I've read up this thread, and i have a Q that needs an A. How did your nic get its ip? did you enter it6 by hand or did it get it using dhcp? If the latter is the case you can rule out hardware problems, modele problems, ip stack problems and many many more potentian caveats. btw, sorry for busting in on the tread Yours, Nico de Haer - Original Message - From: Robert Matijasec [EMAIL PROTECTED] To: Andrew Agno [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Debian. Org debian-user@lists.debian.org Sent: Friday, June 29, 2001 8:53 PM Subject: RE: internet w/ dhcpcd Well here is some info that you might be inerested in: Note that the way I set this up is by following the mini-dhcpcd howto. It claimed Debian would configure everything out of dpkg, so maybe I had somethin messed up earlier, I never configured the computer for inet use on install, but I don't know if that even matters. kernal is 2.2 I used to be able to ping lo and it worked fine, now I get: ping: sendto: Operation not permitted ping:wrote erdos 64 chars, ret=-1 etc, etc ... when I ping my address ( ping 24.217.273.166 ) I get 56 data byes neighbour table overflow ping:sendto: No buffer space available ping:wrote 24.217.12.166 64 chars ret=-1 neighbour table overflow etc, etc ... when I say: ping erdos (erdos is the i386's name ) it is the same as ping lo. I was getting other ping errors but right now I can't recreate them. Are you supposed to be able to do a ping eth0 ??? b/c I can't. route -n yields: Kernel IP routing table Destination Gateway Genmask Flasgs Metric Ref Use Iface 24.217.160.0 0.0.0.0 255.255.240.0 U 0 0 0 eth0 0.0.0.0 24.217.160.1 0.0.0.0 UG 0 0 0 eth0 ifconfig yields: eth0 Link encap:Ethernet HWaddr 00:A0:24:74:4B:F8 inet addr:24.217.273.166 Bcast:255.5\255.255.255 Mask:255.255.240.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:101 error:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txquiuelen:100 Interrupt:10 Base adress:0x300 Some other files: /etc/resolv.conf - /etc/dhcpcd/resolv.conf domain nameserver 24.217.0.3 nameserver 24.217.0.4 /etc/network/interfaces iface lo inet loopback /etc/modules alias eth0 3c509 options th0 io=0x300 irq=10 Maybe I assigned wrong io ports and/or irq for card, but don't think this is the case... At the end of dmesg there is eth0: 3c509 at 0x300 tag 1, 10baseTport, address 00a024 74 4b f8, IRQ 10. 3c509.c:1.16 (2.2) 2/3/98 [EMAIL PROTECTED] ...some other stuff ... Packet log:input DENY eth0 PROTO=17 10.1.160.1:67 24.217.172.166:68 L=336 S=x00 I=25954 F=0x T=255 (#3) eth0: Setting Rx mode to 1 addresses. these last three lines are repeated about 50 times with different values for I, PROTO, and L. With I going to 0 PROTO cycling btw 1 and 17. and L cycling btw 53 and 84. Hope this is sufficient to hammer something out. Perhaps what might help me most is something like linuxconf. Does such a package exist for Debian? You may have noticed that I obviosly don't get the big picture as to what is supposed to be in place for all this to work. I have been cutting pasting config files for a while and with that not working I must consult a higher authority. It almost seems correct, any help would be greatly appreciated. -Andrew's First Response- Robert Matijasec writes: and it keeps trying until it times out. Where could the problem be ? It seems the system reconizes my ethernet card, and it even seems I get a connection to my provider. Can you ping your ethernet card? How about your gateway? What does % route -n tell you? pump came w/Debian install, but after putting on dhcpcd I assumed it would have been neatly removed. You can always check to see if pump is still there, using dselect or dpkg. Andrew. -Original Message- I just installed the dhcpcd package on my i386 and everything seems fine right up to the point where I want to test the connection. I type: telnet ritix.slu.edu I get: Host name lookup failure I type: telnet 165.134.123.3 I get: Trying 165.134.123.3... and it keeps trying until it times out. Where could the problem be ? It seems the system reconizes my ethernet card, and it even seems I get a connection to my provider. pump came w/Debian install, but after putting on dhcpcd I assumed it would have been neatly removed. Any ideas where the problem is ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: internet w/ dhcpcd
On Fri, Jun 29, 2001 at 01:53:07PM -0500, Robert Matijasec wrote: kernal is 2.2 I used to be able to ping lo and it worked fine, now I get: ping: sendto: Operation not permitted ping:wrote erdos 64 chars, ret=-1 etc, etc ... Did you do anything involving firewalling rules? Perhaps you installed a package, like ipmasq, that installs such rules for you? At the end of dmesg there is eth0: 3c509 at 0x300 tag 1, 10baseTport, address 00a024 74 4b f8, IRQ 10. 3c509.c:1.16 (2.2) 2/3/98 [EMAIL PROTECTED] ...some other stuff ... Packet log:input DENY eth0 PROTO=17 10.1.160.1:67 24.217.172.166:68 L=336 S=x00 I=25954 F=0x T=255 (#3) eth0: Setting Rx mode to 1 addresses. these last three lines are repeated about 50 times with different values for I, PROTO, and L. With I going to 0 PROTO cycling btw 1 and 17. and L cycling btw 53 and 84. Check your firewall rules lists: /sbin/ipchains -n -L If something (or you) has set up firewall rules before the dhcp-controlled interface is configured, or reconfigured dynamically, then likely the old rules may no longer match the new interface properties. This could be the cause of the Packet log: input DENY .. entries in your logs. Hope this is sufficient to hammer something out. Perhaps what might help me most is something like linuxconf. Does such a package exist for Debian? There is webmin, it appeared in unstable a little time ago. I don't know how usable the debs are or how usable webmin in general is. But these gui's will not help you find the source of problems any better at all, quite the contrary in fact. By hiding the details, it makes it much harder to know what is going on and to make a decent analysis. Cheers, Joost
Re: internet w/ dhcpcd
On Wed, Jun 27, 2001 at 06:27:25PM -0700, Andrew Agno wrote: Robert Matijasec writes: and it keeps trying until it times out. Where could the problem be ? It seems the system reconizes my ethernet card, and it even seems I get a connection to my provider. Can you ping your ethernet card? How about your gateway? What does % route -n tell you? pump came w/Debian install, but after putting on dhcpcd I assumed it would have been neatly removed. You can always check to see if pump is still there, using dselect or dpkg. Andrew. Hi Robert, I could be wrong about this, but I think dhcpcd only works with 2.0.x and 2.4.x kernels. Are you using a 2.4.x kernel? If so you may need to use pump instead of dhcpcd. If you are getting a connection to your network provider then I'll assume that you are using an older kernel and something else is the problem. Hope that helps anyway, Jimmy Richards -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] binRnP6uVhx06.bin Description: PGP Key 0x0062D7A7. pgpiXDmk6x5Cl.pgp Description: PGP signature
Re: internet w/ dhcpcd
Jimmy Richards writes: On Wed, Jun 27, 2001 at 06:27:25PM -0700, Andrew Agno wrote: Robert Matijasec writes: I could be wrong about this, but I think dhcpcd only works with 2.0.x and 2.4.x kernels. Are you using a 2.4.x kernel? If so you may need to use pump instead of dhcpcd. If you are getting a connection to your network provider then I'll assume that you are using an older kernel and something else is the problem. Not true--I've used dhcpcd with 2.2 kernels before. You can also try dhclient. Andrew.
internet w/ dhcpcd
I just installed the dhcpcd package on my i386 and everything seems fine right up to the point where I want to test the connection. I type: telnet ritix.slu.edu I get: Host name lookup failure I type: telnet 165.134.123.3 I get: Trying 165.134.123.3... and it keeps trying until it times out. Where could the problem be ? It seems the system reconizes my ethernet card, and it even seems I get a connection to my provider. pump came w/Debian install, but after putting on dhcpcd I assumed it would have been neatly removed. Any ideas where the problem is ?
RE:internet w/ dhcpcd
Robert Matijasec writes: and it keeps trying until it times out. Where could the problem be ? It seems the system reconizes my ethernet card, and it even seems I get a connection to my provider. Can you ping your ethernet card? How about your gateway? What does % route -n tell you? pump came w/Debian install, but after putting on dhcpcd I assumed it would have been neatly removed. You can always check to see if pump is still there, using dselect or dpkg. Andrew.
DHCPCD
Hey Has anyone figured out how to get dhcpcd to work with a 3c509b NIC? At first I thought that it was just me, but then I searched on google, and learn that this card does have a slight problem. I've looked all over google and some various search sites, and everything posted doesn't seem to help me much at all. If anyone has any idea, please respond. Thanks very much Sunny Dubey
dhcpcd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 the man page for dhcpcd says that by default dhcpcd will NOT set the hostname of the host to the hostname option received from the DHCP server. To override this (i.e., and force the hostname to be changed), use the -H option. i'm executing the following: dhcpcd -h cx334400-g etho0 the cx334400-g is required by my DHCP server. however, after this request completes, my hostname has been changed to cx334400-g. why would this happen since (1) the default is to not change the hostname and (2) i did not specify the -H option? - -- steve * linux : http://exitwound.org mozart: http://mozart.sourceforge.net buck : http://www.BuckOwensFan.com * -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE65i6YpoyYujFtnVMRAsslAKCRMHTAfhvBrP9orwDyOtyv7//I3QCbBYSh pVCf6PsZe8B/e9V1nEzUs0Y= =Cddr -END PGP SIGNATURE-
nic and dhcpcd trouble
I'm running 2.2.12 with a kingston pci card using the tulip module. It states that the eth0 is in promiscuous mode? What does that mean? Also i just installed dhcpcd from a tarbel but the files don't seem to be where all the how-to's say they should? The card is connected to a surfboard4100 cable modem an adelphia. #$%%%! windoze works but I want my debian too. Its just so much faster! Should I reinstall and insert dhcpcd then before anything else and get the upgraded version or can i still get this one to work? Please help. Email is [EMAIL PROTECTED]
where do I specify my hostname for dhcpcd?
The subject says it allI've been static for years, and now @home has gone and changed things...I'm back up after 4 days of hell trying to figure out what happened, but now am wondering where to tell dhcpcd what my hostname is Can anyone shed some light? Rich
Re: where do I specify my hostname for dhcpcd?
Just call it 'dhcpcd -h foo' if hostname is foo. Andrei -- First there was Explorer... Then came Expedition. This summer Coming to a street near you.. Ford Exterminator. -- Andrei Ivanov http://arshes.dyndns.org [EMAIL PROTECTED] 12402354 --
Re: where do I specify my hostname for dhcpcd?
On Sat, Feb 03, 2001 at 06:51:55PM -0600, Andrei Ivanov wrote: Just call it 'dhcpcd -h foo' if hostname is foo. Andrei Or if it's a client id that's necessary, dhcpcd's -I argument is used for that. Mike -- Michael P. Soulier [EMAIL PROTECTED] ...the word HACK is used as a verb to indicate a massive amount of nerd-like effort. -Harley Hahn, A Student's Guide to UNIX PGP Public Key: http://24.43.42.96/email.phtml pgpRAsjDM27i4.pgp Description: PGP signature
RE: where do I specify my hostname for dhcpcd?
I've been playing with this, and conferring with Andrei off list. I was used to static entries in /etc/init.d/network...when @Home switched my subnet to completely dynamic I had no choice but to install the DHCPCD package. From the command line as root...dhcpcd -h crxx-x gets me going...ifconfig and route show the proper info. What init file should I place this entry? Thanks all. Rich -Original Message- From: Michael P. Soulier [mailto:[EMAIL PROTECTED] Sent: Saturday, February 03, 2001 9:49 PM To: Debian-User@Lists.Debian.Org Subject: Re: where do I specify my hostname for dhcpcd? On Sat, Feb 03, 2001 at 06:51:55PM -0600, Andrei Ivanov wrote: Just call it 'dhcpcd -h foo' if hostname is foo. Andrei Or if it's a client id that's necessary, dhcpcd's -I argument is used for that. Mike -- Michael P. Soulier [EMAIL PROTECTED] ...the word HACK is used as a verb to indicate a massive amount of nerd-like effort. -Harley Hahn, A Student's Guide to UNIX PGP Public Key: http://24.43.42.96/email.phtml
pump / dhcpcd
I finally found the right kernel options for my ethernet card, so now the kernel recognizes it, but I need to setup dhcp support to configure eth0 at boot time. pump is already installed, but it doesn't seem to be doing anything. I tried installing dhcpcd, but it conflicted with pump. Any ideas? Thanks! Ben Pharr
Re: pump / dhcpcd
On Fri, Jan 12, 2001 at 01:30:27AM -0600, Benjamin Pharr wrote: I finally found the right kernel options for my ethernet card, so now the kernel recognizes it, but I need to setup dhcp support to configure eth0 at boot time. pump is already installed, but it doesn't seem to be doing anything. I tried installing dhcpcd, but it conflicted with pump. Any ideas? Thanks! Um, remove pump and install dhcpcd? Have you tried running pump manually (as root)? Have you checked daemon.log for its message to see whether it's failing and if so, why? -- Carl Fink [EMAIL PROTECTED] I-Con's Science and Technology Programming http://www.iconsf.org/
Re: pump / dhcpcd
On Fri, Jan 12, 2001 at 06:22:12AM -0500, Carl Fink wrote: On Fri, Jan 12, 2001 at 01:30:27AM -0600, Benjamin Pharr wrote: I finally found the right kernel options for my ethernet card, so now the kernel recognizes it, but I need to setup dhcp support to configure eth0 at boot time. pump is already installed, but it doesn't seem to be doing anything. I tried installing dhcpcd, but it conflicted with pump. Any ideas? Thanks! Um, remove pump and install dhcpcd? Pump should work fine after you edit /etc/network/interfaces and add iface eth0 inet dhcp and your hostname. Then to prime pump do ifup eth0 and run ifconfig eth0 to see whatzup.
dhcpcd potato
hi- i'm working on switching from static ip addresses to dynamic using dhcp on my massive private network (all 3 machines are currently arranged around my chair grin). i've gotten what should be a working server daemon running on the relevant machine, but when i try to load the dhcpcd client daemon on another it fails and kills the eth0 interface. i've tried the debug option, but nothing is written. i've done a few web searches around this but not found anything that seems to speak to this. could it relate to the card driver? i'm using the realtek rtl8139, which always seems to be included in the partial or incomplete list of drivers. john cuson _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com.
dhcpcd weirdness
I have a box that provides network services to some other computers that is running Potato. It accesses the internet via cable modem, using dhcpcd to get its IP address. The problem I'm having is that it won't work unless I run it with configuration options on the command line, although I have my settings exactly the same in the /etc/dhcpc/config file, I think. Config file: IFACE=eth0 OPTIONS='-h (hostname)' (also tried without ) /etc/network/interfaces also fails to bring it up at boot-time: iface eth0 inet dhcp hostname (hostname) syslog sez: Oct 11 00:08:36 isharagi dhcpcd[188]: timed out waiting for a valid DHCP server response It gets the address instantly if I start it as follows: isharagi:/# dhcpcd -h (hostname) Whereas just typing dhcpcd causes it to pause for a long time, as it does when it tries running it at boot time. The cable modem shows activity so it's doing something. What am I failing to configure properly? If these configurations are ok, what's doing this? It used to work so I figure I must have changed something and made it broken. TIA Andrew W.
RE: dhcpcd weirdness
Oct 11 00:08:36 isharagi dhcpcd[188]: timed out waiting for a valid DHCP server response It gets the address instantly if I start it as follows: isharagi:/# dhcpcd -h (hostname) Whereas just typing dhcpcd causes it to pause for a long time, as it does when it tries running it at boot time. The cable modem shows activity so it's doing something. What am I failing to configure properly? If these configurations are ok, what's doing this? It used to work so I figure I must have changed something and made it broken. some dhcp servers apparently need you to add -h hostname for some obscure reason (i don't know why, i just remember hearing something about that somewhere), so i suggest you check out its config man file for the equivalent. on an almost related note, i had a weird issue when i tried to use dhcp on my linux box... it'd send a dhcpdiscover, get a dhcpoffer ... and then nothing. then, one day it worked, out of the blue. *shrug* ps: you could always run tcpdump while trying to start dhcpcd, to see just wtf it's doing. -m
Re: dhcpcd weirdness
On Wed, Oct 11, 2000 at 07:46:59AM +0200, Jan Martin Mathiassen wrote: some dhcp servers apparently need you to add -h hostname for some obscure reason (i don't know why, i just remember hearing something about that somewhere), so i suggest you check out its config man file for the equivalent. But he's adding one, via his config files, no? I'm using dhcpcd and the config files, and with rogers it often takes me multiple tries to finally get an IP address. They really suck. Mike -- Michael P. Soulier [EMAIL PROTECTED] ...the word HACK is used as a verb to indicate a massive amount of nerd-like effort. -Harley Hahn, A Student's Guide to UNIX PGP Public Key: http://www.storm.ca/~msoulier/personal.html
Re: dhcpcd weirdness
I have no problems with [EMAIL PROTECTED] service and my DHCP service, albiet, I use the command line -h not config files. I've never had a problem at all except for when the power goes out, then I have to power cycle the cable ethernet bridge and then use dhcpcd -h hostname I just put dhcpcd -h cr-your#'s in rc.local and all is fine. Doesn't debian use pump though? some dhcp servers apparently need you to add -h hostname for some obscure reason (i don't know why, i just remember hearing something about that somewhere), so i suggest you check out its config man file for the equivalent. But he's adding one, via his config files, no? I'm using dhcpcd and the config files, and with rogers it often takes me multiple tries to finally get an IP address. They really suck. -- Jason Hammerschmidt - Sapere Aude - [EMAIL PROTECTED] MacLaren McCann Interactive - direct 416.643.8560
