Re: problem z DHCP
witam!
z tego co widze to nie jest problem z dhcp tylko z hda
pojedź go fsck ale zrób kopie przedtem bo ja ostatnio miałem podobny problem,
dzieki bogu, że to był, nazwijmy go , komputer ćwiczebny :) bo troche mi sie
porobilo. system plików mi się wywalił, nie wiedziec dlaczego; i musiałem
sobie ponownie fdsik uzyc zeby porobić partycje. niestety
pozdrawiam
Dnia wtorek, 5 września 2006 16:02, stentor napisał:
Witam!
rano jeden z uzytkowników mojej LAN zglosil nagły brak dostepu do
internetu.
logcheck:
Sep 5 08:05:26 niecka kernel: eth0: link down
Sep 5 08:05:26 niecka kernel: eth1: link down
Sep 5 08:05:31 niecka kernel: hda: status error: status=0x51 { DriveReady
SeekComplete Error } Sep 5 08:05:31 niecka kernel: hda: status error:
error=0x04 { DriveStatusError } Sep 5 08:05:31 niecka kernel: hda: no DRQ
after issuing MULTWRITE Sep 5 08:05:31 niecka kernel: hda: status error:
status=0x51 { DriveReady SeekComplete Error } Sep 5 08:05:31 niecka
kernel: hda: status error: error=0x04 { DriveStatusError } Sep 5 08:05:31
niecka kernel: hda: no DRQ after issuing MULTWRITE Sep 5 08:05:31 niecka
kernel: hda: status error: status=0x51 { DriveReady SeekComplete Error }
Sep 5 08:05:31 niecka kernel: hda: status error: error=0x04 {
DriveStatusError } Sep 5 08:05:31 niecka kernel: hda: no DRQ after issuing
MULTWRITE Sep 5 08:05:31 niecka kernel: hda: status error: status=0x51 {
DriveReady SeekComplete Error } Sep 5 08:05:31 niecka kernel: hda: status
error: error=0x04 { DriveStatusError } Sep 5 08:05:31 niecka kernel: hda:
no DRQ after issuing WRITE
Sep 5 08:05:31 niecka kernel: ide0: reset: success
Sep 5 08:05:35 niecka kernel: eth0: link up, 100Mbps, full-duplex, lpa
0x41E1
i po tym LAN (na eth1) nie może pobierac adresów z serwera DHCP...
proszę o wsparcie.
--
Pozdrowienia,
stentor mailto:[EMAIL PROTECTED]
--
Etch Debian User: PawelatWartandotorg
kadu:3735326 Registered Linux User : 406139 |PLUG :1966491030
GnuPG | pub 1024D/2AAB159B
Home Page: http://www.wartan.org
Re: problem z DHCP
Uu
a tu chyba kolega coś z dyskiem ma nie tak
przejedź dysk fsck...
pozdrawiam
Dnia wtorek, 5 września 2006 15:02, stentor napisał:
Witam!
rano jeden z uzytkowników mojej LAN zglosil nagły brak dostepu do
internetu.
logcheck:
Sep 5 08:05:26 niecka kernel: eth0: link down
Sep 5 08:05:26 niecka kernel: eth1: link down
Sep 5 08:05:31 niecka kernel: hda: status error: status=0x51 { DriveReady
SeekComplete Error } Sep 5 08:05:31 niecka kernel: hda: status error:
error=0x04 { DriveStatusError } Sep 5 08:05:31 niecka kernel: hda: no DRQ
after issuing MULTWRITE Sep 5 08:05:31 niecka kernel: hda: status error:
status=0x51 { DriveReady SeekComplete Error } Sep 5 08:05:31 niecka
kernel: hda: status error: error=0x04 { DriveStatusError } Sep 5 08:05:31
niecka kernel: hda: no DRQ after issuing MULTWRITE Sep 5 08:05:31 niecka
kernel: hda: status error: status=0x51 { DriveReady SeekComplete Error }
Sep 5 08:05:31 niecka kernel: hda: status error: error=0x04 {
DriveStatusError } Sep 5 08:05:31 niecka kernel: hda: no DRQ after issuing
MULTWRITE Sep 5 08:05:31 niecka kernel: hda: status error: status=0x51 {
DriveReady SeekComplete Error } Sep 5 08:05:31 niecka kernel: hda: status
error: error=0x04 { DriveStatusError } Sep 5 08:05:31 niecka kernel: hda:
no DRQ after issuing WRITE
Sep 5 08:05:31 niecka kernel: ide0: reset: success
Sep 5 08:05:35 niecka kernel: eth0: link up, 100Mbps, full-duplex, lpa
0x41E1
i po tym LAN (na eth1) nie może pobierac adresów z serwera DHCP...
proszę o wsparcie.
--
Pozdrowienia,
stentor mailto:[EMAIL PROTECTED]
--
Etch Debian User: PawelatWartandotorg
kadu:3735326 Registered Linux User : 406139 |PLUG :1966491030
GnuPG | pub 1024D/2AAB159B
Home Page: http://www.wartan.org
Re: problem z DHCP
Dnia 05-09-2006, wto o godzinie 16:02 +0200, stentor napisał(a):
Witam!
rano jeden z uzytkowników mojej LAN zglosil nagły brak dostepu do
internetu.
logcheck:
Sep 5 08:05:26 niecka kernel: eth0: link down
Sep 5 08:05:26 niecka kernel: eth1: link down
Sep 5 08:05:31 niecka kernel: hda: status error: status=0x51 { DriveReady
SeekComplete Error }
Sep 5 08:05:31 niecka kernel: hda: status error: error=0x04 {
DriveStatusError }
Sep 5 08:05:31 niecka kernel: hda: no DRQ after issuing MULTWRITE
i po tym LAN (na eth1) nie może pobierac adresów z serwera DHCP...
proszę o wsparcie.
Kup dysk.
Pozdrawiam,
Krzysiek Kiełczewski
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem z DHCP
Dnia Tue, 05 Sep 2006 16:44:39 +0200
Krzysiek Kiełczewski [EMAIL PROTECTED] napisał(a):
Dnia 05-09-2006, wto o godzinie 16:02 +0200, stentor napisał(a):
Witam!
rano jeden z uzytkowników mojej LAN zglosil nagły brak dostepu do
internetu.
logcheck:
Sep 5 08:05:26 niecka kernel: eth0: link down
Sep 5 08:05:26 niecka kernel: eth1: link down
Sep 5 08:05:31 niecka kernel: hda: status error: status=0x51
{ DriveReady SeekComplete Error } Sep 5 08:05:31 niecka kernel:
hda: status error: error=0x04 { DriveStatusError } Sep 5 08:05:31
niecka kernel: hda: no DRQ after issuing MULTWRITE
i po tym LAN (na eth1) nie może pobierac adresów z serwera DHCP...
proszę o wsparcie.
Kup dysk.
albo najpierw zmień taśmę IDE i zobacz czy nie pomogło
pozdr.
Piotr Ch.
Re: problem z DHCP
2006/9/5, Piotr Chylewski [EMAIL PROTECTED]: albo najpierw zmień taśmę IDE i zobacz czy nie pomogło pozdr. Piotr Ch. na koniec pobaw sie hdparmem , ale to już podrygi ostrygi ;) -- Wojciech Ziniewicz| jid:[EMAIL PROTECTED] http://silenceproject.org | http://zetho.wordpress.com
Re: problem z DHCP
Jak doniosły WSI, dnia Tue, 5 Sep 2006 16:02:06 +0200
stentor [EMAIL PROTECTED] napisał(a):
Witam!
rano jeden z uzytkowników mojej LAN zglosil nagły brak dostepu do
internetu.
logcheck:
Sep 5 08:05:26 niecka kernel: eth0: link down
Sep 5 08:05:26 niecka kernel: eth1: link down
Sep 5 08:05:31 niecka kernel: hda: status error: status=0x51
{ DriveReady SeekComplete Error } Sep 5 08:05:31 niecka kernel: hda:
status error: error=0x04 { DriveStatusError } Sep 5 08:05:31 niecka
kernel: hda: no DRQ after issuing MULTWRITE Sep 5 08:05:31 niecka
kernel: hda: status error: status=0x51 { DriveReady SeekComplete
Error } Sep 5 08:05:31 niecka kernel: hda: status error: error=0x04
{ DriveStatusError } Sep 5 08:05:31 niecka kernel: hda: no DRQ after
issuing MULTWRITE Sep 5 08:05:31 niecka kernel: hda: status error:
status=0x51 { DriveReady SeekComplete Error } Sep 5 08:05:31 niecka
kernel: hda: status error: error=0x04 { DriveStatusError } Sep 5
08:05:31 niecka kernel: hda: no DRQ after issuing MULTWRITE Sep 5
08:05:31 niecka kernel: hda: status error: status=0x51 { DriveReady
SeekComplete Error } Sep 5 08:05:31 niecka kernel: hda: status
error: error=0x04 { DriveStatusError } Sep 5 08:05:31 niecka kernel:
hda: no DRQ after issuing WRITE Sep 5 08:05:31 niecka kernel: ide0:
reset: success Sep 5 08:05:35 niecka kernel: eth0: link up, 100Mbps,
full-duplex, lpa 0x41E1
i po tym LAN (na eth1) nie może pobierac adresów z serwera DHCP...
proszę o wsparcie.
IMHO Dysk ci sie sypie...
--
Jerzy sm0q Patraszewski
patrasze{at}wszib{dot}edu{dot}pl
sm0q{at}rootshell{dot}be
Re: problem with dhcp, might be firestarter related
Juha Pahkala a écrit : Hello, I have strange problem with dhcp, that might be somehow related to firestarter. But not necessarily directly. I did so many different things with my network setup simultaneously that I'm not sure, what's causing my current problem. So what I did was try to convert to using dhcp in my home lan. But at the same time, I converted from using customized (by the ifconfig package) network device names back to standard 'ethN' kind of names, and this somehow causes my current problem. My network device name for my home lan used to be 'lan'. I configured firestarter to use dhcp on that interface 'lan'. I did however have some problems with dhcp possibly due to my using non-standard interface names, so I switched back to using 'eth1' as my lan interface name. But I still couldn't get dhcp to start. I tried upgrading my dhcp server to the latest one (dhcp3-server) and what not, but nothing seems to work (I'm using debian unstable btw). Now I've uninstalled firestarter and purged the configuration files of it temporarily and try to use dhcp3-server directly to enable dhcp, and I get this result in my sysconfig when I try to start dhcp3-server: Mar 8 13:03:25 server dhcpd: Wrote 0 leases to leases file. Mar 8 13:03:25 server dhcpd: Multiple interfaces match the same shared network: lan eth1 Mar 8 13:03:25 server dhcpd: Bind socket to interface: No such device So, somewhere in my config files there's still a dangling reference to that old 'lan' interface that doesn't exist anymore! I've tried to grep through all the config file in /etc and /var and /usr/share but haven't found anything. I have a feeling that either dhcp ver.2.0 or firestarter is the source of that reference but I'm not sure. I ask you guys if you can think of a place, where this reference might be? I don't understand this, is there possibly a binary file that grep can't read that might hold the old information? in /etc/default/dhc* ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem with dhcp, might be firestarter related
Laurent CARON wrote: Juha Pahkala a écrit : Hello, I have strange problem with dhcp, that might be somehow related to firestarter. But not necessarily directly. I did so many different things with my network setup simultaneously that I'm not sure, what's causing my current problem. So what I did was try to convert to using dhcp in my home lan. But at the same time, I converted from using customized (by the ifconfig package) network device names back to standard 'ethN' kind of names, and this somehow causes my current problem. My network device name for my home lan used to be 'lan'. I configured firestarter to use dhcp on that interface 'lan'. I did however have some problems with dhcp possibly due to my using non-standard interface names, so I switched back to using 'eth1' as my lan interface name. But I still couldn't get dhcp to start. I tried upgrading my dhcp server to the latest one (dhcp3-server) and what not, but nothing seems to work (I'm using debian unstable btw). Now I've uninstalled firestarter and purged the configuration files of it temporarily and try to use dhcp3-server directly to enable dhcp, and I get this result in my sysconfig when I try to start dhcp3-server: Mar 8 13:03:25 server dhcpd: Wrote 0 leases to leases file. Mar 8 13:03:25 server dhcpd: Multiple interfaces match the same shared network: lan eth1 Mar 8 13:03:25 server dhcpd: Bind socket to interface: No such device So, somewhere in my config files there's still a dangling reference to that old 'lan' interface that doesn't exist anymore! I've tried to grep through all the config file in /etc and /var and /usr/share but haven't found anything. I have a feeling that either dhcp ver.2.0 or firestarter is the source of that reference but I'm not sure. I ask you guys if you can think of a place, where this reference might be? I don't understand this, is there possibly a binary file that grep can't read that might hold the old information? in /etc/default/dhc* ? Nope, unfortunately... INTERFACES=eth1 Can you think of some other place? thanks, juhis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem with dhcp, might be firestarter related
Juha Pahkala wrote: customized (by the ifconfig package) network device names btw, I just want to correct that I ment the package 'ifrename', not 'ifconfig' juhis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem with dhcp, might be firestarter related
Juha Pahkala wrote: Juha Pahkala wrote: customized (by the ifconfig package) network device names btw, I just want to correct that I ment the package 'ifrename', not 'ifconfig' juhis Sorry for continously replying to my self but I've yet more information: actually if I bypass the dhcpd3-server start script in /etc/init.d and just issue: bash:# dhcpd3 -q eth1 I immediately get the following to syslog: Mar 8 19:16:27 server dhcpd: Internet Systems Consortium DHCP Server V3.0.3 Mar 8 19:16:27 server dhcpd: Copyright 2004-2005 Internet Systems Consortium. Mar 8 19:16:27 server dhcpd: All rights reserved. Mar 8 19:16:27 server dhcpd: For info, please visit http://www.isc.org/sw/dhcp/ Mar 8 19:16:27 server dhcpd: Wrote 0 deleted host decls to leases file. Mar 8 19:16:27 server dhcpd: Wrote 0 new dynamic host decls to leases file. Mar 8 19:16:27 server dhcpd: Wrote 0 leases to leases file. Mar 8 19:16:27 server dhcpd: Multiple interfaces match the same shared network: lan eth1 Mar 8 19:16:27 server dhcpd: Bind socket to interface: No such device Note that I only pass one interface, eth1, to dhcpd3, but somehow it fetches the old 'lan' interface somewhere. anybody know more on how dhcpd3 works? thanks, juhis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem with dhcp, might be firestarter related
Juha Pahkala wrote: Mar 8 13:03:25 server dhcpd: Wrote 0 leases to leases file. Mar 8 13:03:25 server dhcpd: Multiple interfaces match the same shared network: lan eth1 Mar 8 13:03:25 server dhcpd: Bind socket to interface: No such device So, somewhere in my config files there's still a dangling reference to that old 'lan' interface that doesn't exist anymore! I've tried to grep through all the config file in /etc and /var and /usr/share but haven't found anything. This may come from the /etc/dhcp3/dhcpd.conf (or something like that). What does your ifconfig output say about the network configuration? HS -- Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de oder über pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.org pgpMqVY3gTis6.pgp Description: PGP signature
Re: problem with dhcp, might be firestarter related
Hendrik Sattler wrote: Juha Pahkala wrote: Mar 8 13:03:25 server dhcpd: Wrote 0 leases to leases file. Mar 8 13:03:25 server dhcpd: Multiple interfaces match the same shared network: lan eth1 Mar 8 13:03:25 server dhcpd: Bind socket to interface: No such device So, somewhere in my config files there's still a dangling reference to that old 'lan' interface that doesn't exist anymore! I've tried to grep through all the config file in /etc and /var and /usr/share but haven't found anything. This may come from the /etc/dhcp3/dhcpd.conf (or something like that). What does your ifconfig output say about the network configuration? HS Hi Hendrik, Indeed I had the 'lan' configured still in the dhcpd.conf file, *even though I had checked it already about five times* sorry to waste bandwith and your time like this, I feel ashamed, don't understand how I missed that, for two days!!! thanks all and sorry, juhis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem z DHCP
Roland Czaczyk / FreeBird wrote:
Witam !!!
Zainstalowałem pakiet;
apt-get install dhcpd
wyedytowałem plik /etc/dhcpd.conf
subnet 192.168.1.0
netmask 255.255.255.0 {
#option domain-name mertki.one.pl;
option domain-name-servers 194.204.152.34;
option routers 192.168.1.1;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.1.255;
}
host user2 {hardware ethernet 00:c0:26:a7:7c:3c;fixed-address
192.168.1.2;}
No i po odpaleniu poleceniem: dhcpd start dostaję komunikat:
Internet Software Consortium DHCP Server 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.
Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html
No subnet declaration for start (0.0.0.0).
Please write a subnet declaration in your dhcpd.conf file for the
network segment to which interface start is attached.
exiting.
Co jest zrobione źle ?? bo DHCP nei działa
Z poważaniem Roland Czaczyk
Mysle ze to banalna sprawa.
Startujesz serwer albo
dhcpd ethx
lub
dhcp start
jesli wpisujesz dhcpd start to serwer szuka wpisow w dhcpd.conf dla start
pozdrawiam jarek m.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem z DHCP
## On Sat, 25 Jun 2005 15:31:06 +0200
## you wrote:
Witam !!!
Zainstalowałem pakiet;
apt-get install dhcpd
wyedytowałem plik /etc/dhcpd.conf
subnet 192.168.1.0
netmask 255.255.255.0 {
musi być jednym wierszem:
subnet 192.168.1.0 netmask 255.255.255.0 {
--
to my, trociny
Re: Problem z DHCP
On Mon, May 30, 2005 at 10:48:54AM +0200, Piotr Krl wrote: Witam, Mam problem. Uywam Woody'ego 3.0 z jajkiem 2.20. Suy on do dzielenia dsl'a. Adresy ip przydzielam poprzez DHCP na podstawie MAC adresu. I ot od pewnego czasu pojawia mi si taki zapis jak poniej w syslogu. Odpowied brzmi, klient nie dostaje (wysanej) odpowiedzi z dhcp. Oczywicie komputer klient nie otrzymuje adresu IP tylko losowy 169.xxx.xxx.xxx Jednak kiedy klientowi wpisze z palca stale IP to niestety problem si nie rozwizuje poniewa i tak nie mog pingowa serwera ze stacji klienta i klienta z serwera tym bardziej dosta si do Internetu z kompa klienta. Moliwe przyczyny: kabelek (kilka razy to miaem, raz nawet sam wypad z gniadka po dotniciu), karta, switch/hub, komputer, uziemienie, oprogramowanie, itd itp :( Najprociej postawi w miejscu felernego klienta co sprawnego i wykluczy w ten sposb lew poow (u mnie kable zwisaj z lewej) przyczyn ;) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem z DHCP
witam :) W licie z pon, 30-05-2005, godz. 10:48, Piotr Krl pisze: Co jest o tyle dziwne ze w sieci jest 40 kompw i tylko 3 maja takie problemy. jezeli sa to problemy z winxp z sp2(badz bez?) to trzeba jeszcze raz dokonac instalacji winsocks 1/2.. robi sie to poprzez wycianie calych rejestrow ;) opis problemu znajdziesz na sieci pozdrawiam isdes -- Piekne dziewczyny i samochody... http://link.interia.pl/f188a
Re: Problem mit dhcp
* Michael Klank [EMAIL PROTECTED], 2004-04-21 09:38 +0200: Danke für den Tipp, hab ich gleich umgesetzt und das Packet auf hold gesetzt. Wußte bis jetzt gar nicht das das geht. Ich benutze schon seit immer dies, original IIRC von Ethan Benson: -- #!/bin/sh # hold Debian packages #/usr/local/sbin/dhold PRG=`basename $0` if [ `id -u` != 0 ] ; then echo you're not root, go away. exit 1 elif [ $# != 1 ] ; then echo Usage: $PRG packagename exit 1 else echo $1 hold | dpkg --set-selections fi -- #!/bin/sh # unhold Debian package # /usr/local/sbin/dhold PRG=`basename $0` if [ `id -u` != 0 ] ; then echo you're not root, go away. exit 1 elif [ $# != 1 ] ; then echo Usage: $PRG packagename exit 1 else echo $1 install | dpkg --set-selections fi -- -Andre pgp0.pgp Description: PGP signature
Re: Problem mit dhcp
Hallo Michael! On Tue, Apr 20, 2004 at 10:41:58PM +0200, Michael Klank wrote: ich habe ein Debian SID am laufen (i686, Kernel 2.6.5). Ich gehe ins Netz über einen Router, auf dem auch der DHCP-Server läuft. Seit dem upgrade auf ifupdown 0.6.4-4.8 kommt mein eth1 nicht up mit folgender Fehlermeldung: debian:/home/micha/software# ifup eth1 [...] exiting. Failed to bring up eth1. Nach einem beherztem dpkg -i /var/cache/apt/archives/ifupdown_0.6.4-4.6_i386.deb geht es wieder. Kann mir jemand einen Tipp geben?!?! Hilft eventuell http://bugs.debian.org/242537 beim Klären weiter? Flo - heute ohne Rant bezüglich Sid-User und BTS... ;) signature.asc Description: Digital signature
Re: Problem mit dhcp
Danke für die Info. Jetzt weis ich, dass ich solange es keine update von dhcp-client3 gibt, jedesmal nach einem upgrade, das ifupdown Packet downgraden muss. Nicht befriedigend aber auch nicht zuändern. Danke nochmal Mit freundlichen Grüßen Michael KLank Am Di, den 20.04.2004 schrieb Florian Ernst um 23:06: Hallo Michael! On Tue, Apr 20, 2004 at 10:41:58PM +0200, Michael Klank wrote: ich habe ein Debian SID am laufen (i686, Kernel 2.6.5). Ich gehe ins Netz über einen Router, auf dem auch der DHCP-Server läuft. Seit dem upgrade auf ifupdown 0.6.4-4.8 kommt mein eth1 nicht up mit folgender Fehlermeldung: debian:/home/micha/software# ifup eth1 [...] exiting. Failed to bring up eth1. Nach einem beherztem dpkg -i /var/cache/apt/archives/ifupdown_0.6.4-4.6_i386.deb geht es wieder. Kann mir jemand einen Tipp geben?!?! Hilft eventuell http://bugs.debian.org/242537 beim Klären weiter? Flo - heute ohne Rant bezüglich Sid-User und BTS... ;) signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: Problem mit dhcp
Hallo Michael! On Tue, Apr 20, 2004 at 11:24:20PM +0200, Michael Klank wrote: Danke für die Info. Jetzt weis ich, dass ich solange es keine update von dhcp-client3 gibt, jedesmal nach einem upgrade, das ifupdown Packet downgraden muss. Nicht befriedigend aber auch nicht zuändern. ...oder das Paket auf hold setzen à la Sektion 2.2.11 oder 6.4.6 der Debian Reference, wenn das Paket nicht mehr aktualisiert werden soll. Gruß, Flo signature.asc Description: Digital signature
Re: Problem mit dhcp
Danke für den Tipp, hab ich gleich umgesetzt und das Packet auf hold gesetzt. Wußte bis jetzt gar nicht das das geht. Funktioniert wunderbar!!! Mit freundlichen Grüßen Michael Klank Am Di, den 20.04.2004 schrieb Florian Ernst um 23:56: Hallo Michael! On Tue, Apr 20, 2004 at 11:24:20PM +0200, Michael Klank wrote: Danke für die Info. Jetzt weis ich, dass ich solange es keine update von dhcp-client3 gibt, jedesmal nach einem upgrade, das ifupdown Packet downgraden muss. Nicht befriedigend aber auch nicht zuändern. ...oder das Paket auf hold setzen à la Sektion 2.2.11 oder 6.4.6 der Debian Reference, wenn das Paket nicht mehr aktualisiert werden soll. Gruß, Flo signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: Problem with DHCP
A long time ago, in a galaxy far, far way, someone said... I am running Potato on an P3.. and have a DHCP server with some Windows 95 clients. However, when those Windows 95 boot up they cannot get an IP from the DHCP server. (according to the logs the DHCP server have already offered the IPs.) When I run winipcfg and manually refresh the DHCP settings it works most of the times. Sometimes the interface refuses to update the IP. There was once a Windows NT DHCP server running with no problems (and was replaced by the Debian server). Is it possible that I have misconfigured something? It's likely that you've misconfigured something, however we need to know more about how your network is set up: the locations of routers hubs so on. Are you using ISC's DHCP server software? If you are, it might help to see a configuration that's been working for me for quite some time: http://tux.creighton.edu/~pbrutsch/dhcpd.conf. Clients uses Intel EEpro* cards, and the server uses a D-Link card with the chip from Davicom (using via-rhine modules) The ethernet cards shouldn't make a difference. -- -- Phil Brutsche [EMAIL PROTECTED] There are two things that are infinite; Human stupidity and the universe. And I'm not sure about the universe. - Albert Einstein
Re: Problem with DHCP
On Thu, Jan 27, 2000 at 10:09:20AM -0600, Phil Brutsche wrote: A long time ago, in a galaxy far, far way, someone said... I am running Potato on an P3.. and have a DHCP server with some Windows 95 clients. However, when those Windows 95 boot up they cannot get an IP from the DHCP server. (according to the logs the DHCP server have already offered the IPs.) When I run winipcfg and manually refresh the DHCP settings it works most of the times. Sometimes the interface refuses to update the IP. There was once a Windows NT DHCP server running with no problems (and was replaced by the Debian server). Is it possible that I have misconfigured something? It's likely that you've misconfigured something, however we need to know more about how your network is set up: the locations of routers hubs so on. I am not responsible for the network set-up so I cannot tell for sure, but I think everything is connected to a big Ethernet switch.. The network is connected to the external network through a machine (IP: 10.1x.x.1) that acts also as a WWW proxy server. First DNS server, as well as the DHCP server, is on 10.1x.x.2.. I can't remember the exact IPs, but I guess they shouldn't matter..? Are you using ISC's DHCP server software? If you are, it might help to see a configuration that's been working for me for quite some time: http://tux.creighton.edu/~pbrutsch/dhcpd.conf. Yes, I am using ISC's DHCP server. My configuration file is similar... equally short. The only differences that I can remember (save from choices of IPs) are: 1) I put the routers and domain-name-servers lines outside of the subnet bracket 2) I have set up more than 1 DNS server, separated by commas 3) lease times are shorter.. like a few hours. Am I supposed to use lease time that long? Clients uses Intel EEpro* cards, and the server uses a D-Link card with the chip from Davicom (using via-rhine modules) The ethernet cards shouldn't make a difference.
Re: Problem with DHCP
A long time ago, in a galaxy far, far way, someone said... On Thu, Jan 27, 2000 at 10:09:20AM -0600, Phil Brutsche wrote: A long time ago, in a galaxy far, far way, someone said... I am running Potato on an P3.. and have a DHCP server with some Windows 95 clients. However, when those Windows 95 boot up they cannot get an IP from the DHCP server. (according to the logs the DHCP server have already offered the IPs.) When I run winipcfg and manually refresh the DHCP settings it works most of the times. Sometimes the interface refuses to update the IP. There was once a Windows NT DHCP server running with no problems (and was replaced by the Debian server). Is it possible that I have misconfigured something? It's likely that you've misconfigured something, however we need to know more about how your network is set up: the locations of routers hubs so on. I am not responsible for the network set-up so I cannot tell for sure, but I think everything is connected to a big Ethernet switch.. The network is connected to the external network through a machine (IP: 10.1x.x.1) that acts also as a WWW proxy server. First DNS server, as well as the DHCP server, is on 10.1x.x.2.. I can't remember the exact IPs, but I guess they shouldn't matter..? The IPs don't matter. I take it then that there's no router between the DHCP server and the clients? Are you using ISC's DHCP server software? If you are, it might help to see a configuration that's been working for me for quite some time: http://tux.creighton.edu/~pbrutsch/dhcpd.conf. Yes, I am using ISC's DHCP server. My configuration file is similar... equally short. The only differences that I can remember (save from choices of IPs) are: 1) I put the routers and domain-name-servers lines outside of the subnet bracket Trivial difference. 2) I have set up more than 1 DNS server, separated by commas Again a trivial difference. 3) lease times are shorter.. like a few hours. Am I supposed to use lease time that long? Not necessarily - lease times are chosen arbitrarily. I chose 1 day because it sounded good :) Sometimes they're set for a reason: here at the University the lease time is 5 days, probably to prevent the computer serving DHCP from being overloaded (there are very easliy over 1000 DHCP clients here). It would be good to double check your config against mine to make sure you don't have a setting that could be messing things up. If that doesn't work... ISC runs several mailing lists for dhcpd/dhclient. They'll be able to help you more there. -- -- Phil Brutsche [EMAIL PROTECTED] There are two things that are infinite; Human stupidity and the universe. And I'm not sure about the universe. - Albert Einstein
