On Mon, 4 Dec 2023 05:55:50 +0100
wrote:
> Wait a sec: before the clients get an answer from the DHCP server,
> they don't have any route (at least not for the network in question),
> so it doesn't make sense poking at them with ip route and things.
> They send their request to the local
On Sun, Dec 03, 2023 at 12:30:53PM -0700, Charles Curley wrote:
> I am installing a new router which seems to work well so far.
>
> I have changed the DHCP server to use the new router's address, and shut
> the server down and restarted it. Existing clients insist on using the
> old router
On Sun, 3 Dec 2023 22:32:59 -0500
Jeffrey Walton wrote:
> The "restart your dhcp clients" may have a sharp edge. Sometimes the
> clients have a touch of resiliency or hardening added so they contact
> their original dhcp server, and not a [possibly] rogue server setup by
> an unknowing developer
On Sun, 3 Dec 2023 12:30:53 -0700
Charles Curley wrote:
> I am installing a new router which seems to work well so far.
>
> I have changed the DHCP server to use the new router's address, and
> shut the server down and restarted it. Existing clients insist on
> using the old router anyway. Is
On Sun, Dec 3, 2023 at 9:57 PM jeremy ardley wrote:
>
>
> On 4/12/23 05:18, Geert Stappers wrote:
> > That triggered me to ask "Has the DHCP server been restarted?"
>
>
> The default behaviour of most dhcp clients when they can't connect to a
> dhcp server is to maintain the settings from any
On Sun, 3 Dec 2023 17:18:23 -0500
Jeffrey Walton wrote:
> I don't know about Linux clients, but in the past, Windows clients
> used to try to connect to the previous DHCP server for its lease info.
> If the old DHCP server is still available (on the old router?), then
> the client may be getting
On Sun, Dec 3, 2023 at 4:51 PM Charles Curley
wrote:
>
> On Sun, 3 Dec 2023 22:14:51 +0100
> Geert Stappers wrote:
>
> > I assume that the previous router is disconnected from the LAN.
>
> No. Until I solve this problem (and a few others), I will have clients
> using the old router.
>
> > The
On Sun, 3 Dec 2023 22:14:51 +0100
Geert Stappers wrote:
> I assume that the previous router is disconnected from the LAN.
No. Until I solve this problem (and a few others), I will have clients
using the old router.
> The DHCProtocol has "release" for such goosing.
> At DHCPclient do "stop
On Sun, 3 Dec 2023 22:18:22 +0100
Geert Stappers wrote:
> Has the DHCP server been restarted?
Yes.
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
On 4/12/23 05:18, Geert Stappers wrote:
That triggered me to ask "Has the DHCP server been restarted?"
The default behaviour of most dhcp clients when they can't connect to a
dhcp server is to maintain the settings from any previous lease.
A second default behaviour is for clients to not
On Sun, 3 Dec 2023 20:56:20 +0100
Marco Moock wrote:
> Did you check with a sniffer that the answer from the DHCP includes
> the new router address?
Not with a sniffer, but I did check the lease file. Neither the router
address nor the various lease times changed.
--
Does anybody read
On Sun, Dec 03, 2023 at 04:03:39PM -0500, Henning Follmann wrote:
> > On Dec 3, 2023, at 14:31, Charles Curley wrote:
> >
> > I am installing a new router which seems to work well so far.
> >
> > I have changed the DHCP server to use the new router's address, and shut
> > the server down and
On Sun, Dec 03, 2023 at 12:30:53PM -0700, Charles Curley wrote:
> I am installing a new router which seems to work well so far.
I assume that the previous router is disconnected from the LAN.
> I have changed the DHCP server to use the new router's address, and shut
> the server down and
> On Dec 3, 2023, at 14:31, Charles Curley
> wrote:
>
> I am installing a new router which seems to work well so far.
>
> I have changed the DHCP server to use the new router's address, and shut
> the server down and restarted it. Existing clients insist on using the
> old router anyway.
Am 03.12.2023 um 12:30:53 Uhr schrieb Charles Curley:
> I have changed the DHCP server to use the new router's address, and
> shut the server down and restarted it. Existing clients insist on
> using the old router anyway. Is there any way to goose clients into
> using the new one short of
I am installing a new router which seems to work well so far.
I have changed the DHCP server to use the new router's address, and shut
the server down and restarted it. Existing clients insist on using the
old router anyway. Is there any way to goose clients into using the new
one short of
hey,
I've implemented a dhcp server, I want to cretae several subnets inside the
same subnet using net mask, at teh same time i want to give the ip by mac.
The problem is that when the server get the mac dont give the correct ip to
the client, its like i didnt define it in conf file. The syslog
On Wed, Nov 26, 2008 at 11:16:50PM +0100, Jesus arteche wrote:
hardware ethernet xx:xx:xx:xx:xx:50;
hardware ethernet xx:xx:xx:xx:xx:51;
hardware ethernet xx:xx:xx:xx:xx:54;
hardware ethernet xx:xx:xx:xx:xx:55;
You actually have addresses ending with 50--55
2008/11/27 Jesus arteche [EMAIL PROTECTED]:
hey,
I've implemented a dhcp server, I want to cretae several subnets inside the
same subnet using net mask, at teh same time i want to give the ip by mac.
The problem is that when the server get the mac dont give the correct ip to
the client,
I had a similar problem. The file /etc/dhcp3/dhclient.conf is the file
that controls resolv.conf (at least on this system). You can specify
which DNS is used first by using
prepend domain-name-servers xxx.xxx.xxx.xxx;
replacing of course the x's with the ip address of the DNS. This line
is
My isp is providing me the ip using DHCP. everything fine. But they are
sending 3 nameserver. And first DNS server is not responding. SO it take
time to switch to the secound dns. So, it's making problem (slow down).
I want to keep fix (will not updated or replace by dhcp) the
/etc/resolv.conf
On Thu, 29 Mar 2007 20:54:34 +0600
S. M. Ibrahim (Lavlu) [EMAIL PROTECTED] wrote:
My isp is providing me the ip using DHCP. everything fine. But they are
sending 3 nameserver. And first DNS server is not responding. SO it take
time to switch to the secound dns. So, it's making problem (slow
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Celejar wrote:
On Thu, 29 Mar 2007 20:54:34 +0600
S. M. Ibrahim (Lavlu) [EMAIL PROTECTED] wrote:
My isp is providing me the ip using DHCP. everything fine. But they are
sending 3 nameserver. And first DNS server is not responding. SO it take
On Sat, 18 Feb 2006 23:43:06 +
John Halton [EMAIL PROTECTED] wrote:
John Halton wrote:
This is the same problem as in my previous thread (Hanging during
boot-up following dbus upgrade) but a response on that thread has
enabled me to narrow it down a bit.
dhcp-client (I assume)
On 2/21/06, Shawn Lamson [EMAIL PROTECTED] wrote:
On Sat, 18 Feb 2006 23:43:06 +
have you tried the dhcpcd package?
I've had an off-list email suggesting that the problem is due to a bug
in zeroconf, and that purging zeroconf will solve it. (See
This is the same problem as in my previous thread (Hanging during
boot-up following dbus upgrade) but a response on that thread has
enabled me to narrow it down a bit.
dhcp-client (I assume) is pausing indefinitely at the bound to
80.x.xxx.x -- renewal in 56953 seconds message. This applies
John Halton wrote:
This is the same problem as in my previous thread (Hanging during
boot-up following dbus upgrade) but a response on that thread has
enabled me to narrow it down a bit.
dhcp-client (I assume) is pausing indefinitely at the bound to
80.x.xxx.x -- renewal in 56953 seconds
On Monday 18 July 2005 05:26, [EMAIL PROTECTED] wrote:
I got my broadband setup and my provider uses DHCP and I have a
intelligent router (modem).
I installed dhcpcd as dhcp client and it works fine except that it couldnt
get right nameservers and
hence resolving host name takes lot of
I got my broadband setup and my provider uses DHCP and I have a intelligent router (modem).
I installed dhcpcd as dhcp client and it works fine except that it couldnt get right nameservers and
hence resolving host name takes lot of time.
If I put nameservers (I got it from my provider) in
I got my broadband setup and my provider uses DHCP and I have a intelligent router (modem).
I installed dhcpcd as dhcp client and it works fine except that it couldnt get right nameservers and
hence resolving host name takes lot of time.
If I put nameservers (I got it from my provider) in
On Tue, Jun 21, 2005 at 10:44:05PM -0400, Derrick Hudson wrote:
On Tue, Jun 21, 2005 at 05:32:01PM -0700, Xeno Campanoli wrote:
| I got a real whacky one. This old machine I've got has two NICs, and during
| install I assign eth1 to be the one used, and it gets the ip address from
| DHCP.
I got a real whacky one. This old machine I've got has two NICs, and during
install I assign eth1 to be the one used, and it gets the ip address from
DHCP. Well, after the reboot, that same IP address is assigned to eth0, and
I get no network. I've solved this by switching the cable over and
On Tue, 21 Jun 2005, Xeno Campanoli wrote:
I got a real whacky one. This old machine I've got has two NICs, and during
install I assign eth1 to be the one used, and it gets the ip address from
DHCP. Well, after the reboot, that same IP address is assigned to eth0, and
I get no network. I've
Xeno Campanoli wrote:
I got a real whacky one. This old machine I've got has two NICs, and during
install I assign eth1 to be the one used, and it gets the ip address from
DHCP. Well, after the reboot, that same IP address is assigned to eth0, and
I get no network. I've solved this by
On Tue, Jun 21, 2005 at 05:32:01PM -0700, Xeno Campanoli wrote:
| I got a real whacky one. This old machine I've got has two NICs, and during
| install I assign eth1 to be the one used, and it gets the ip address from
| DHCP. Well, after the reboot, that same IP address is assigned to eth0, and
On Sat, Aug 07, 2004 at 09:59:30AM -0400, [EMAIL PROTECTED] wrote:
Hello.
I am a relatively new user of Debian and I couldn't figure this one out.
I have 2 machines running Sarge, both configured to use DHCP. At boot time
both for some reason acquire the same address (192.168.102.100) from
Hello.
I am a relatively new user of Debian and I couldn't figure this one out.
I have 2 machines running Sarge, both configured to use DHCP. At boot time
both for some reason acquire the same address (192.168.102.100) from my
router. Is there a way to force at least one of them to get a
On Sat, 2004-08-07 at 08:59, [EMAIL PROTECTED] wrote:
Hello.
I am a relatively new user of Debian and I couldn't figure this one out.
I have 2 machines running Sarge, both configured to use DHCP. At boot time
both for some reason acquire the same address (192.168.102.100) from my
router. Is
On Saturday 07 August 2004 14:59, [EMAIL PROTECTED] wrote:
Hello.
I am a relatively new user of Debian and I couldn't figure this one out.
I have 2 machines running Sarge, both configured to use DHCP. At boot time
both for some reason acquire the same address (192.168.102.100) from my
Hi,
I have a network with computers with dual boot (linux and windows). They
get ip from a debian dhcp3 server. When a client boot the machine in
windows he gets ip A, and when the same client boots the machine in
linux gets ip A+1. How could I make it receive the same ip, no matter
what OS the
Cristi Banciu dijo:
I know I could simply solve the problem by bonding ip with mac, but I
don't want to do that. I need dinamicaly assigned address, not static.
you'll always get differents ip's if you don't assign a determinate ip
address to an MAC address. The rest of your pool of ip
On Wed, 2004-06-09 at 12:37, Diego Martnez Castaeda wrote:
you'll always get differents ip's if you don't assign a determinate ip
address to an MAC address. The rest of your pool of ip addresses will be
assigned dinamicaly.
so , you wanna tell me that I have no choice but to assign ip static
Cristi Banciu dijo:
On Wed, 2004-06-09 at 12:37, Diego MartÃnez Castañeda wrote:
you'll always get differents ip's if you don't assign a determinate ip
address to an MAC address. The rest of your pool of ip addresses will be
assigned dinamicaly.
so , you wanna tell me that I have no choice
On Wed, 2004-06-09 at 12:21, Cristi Banciu wrote:
Hi,
I have a network with computers with dual boot (linux and windows). They
get ip from a debian dhcp3 server. When a client boot the machine in
windows he gets ip A, and when the same client boots the machine in
linux gets ip A+1. How
Hallo zusammen,
ich habe da ein kleines Problem mit dem dhclient.
Ich habe zwei Kernelversioen. Bei der 2.4.18 funktioniert der dhclient ganz
normal, und ich bekomme eine IP-Adresse zugewissen.
Bei der Version 2.4.21 funktioniert der dhclient nicht mehr. Das Programm
beendet sich mir Exit - Code
Walter Wiedmann [EMAIL PROTECTED] wrote:
Moin Walter,
ich habe da ein kleines Problem mit dem dhclient.
Ich habe zwei Kernelversioen. Bei der 2.4.18 funktioniert der dhclient
ganz normal, und ich bekomme eine IP-Adresse zugewissen.
Bei der Version 2.4.21 funktioniert der dhclient nicht mehr.
Serge Gebhardt wrote:
Walter Wiedmann [EMAIL PROTECTED] wrote:
Moin Walter,
ich habe da ein kleines Problem mit dem dhclient.
Ich habe zwei Kernelversioen. Bei der 2.4.18 funktioniert der dhclient
ganz normal, und ich bekomme eine IP-Adresse zugewissen.
Bei der Version 2.4.21
* Walter Wiedmann [EMAIL PROTECTED] wrote:
[ ... ]
Ich hab da aber gleich noch eine andere Frage. Weiss jemand, wo ich die
.config vom Standard - Kernel 2.4.21 von Debian herbekommen kann. Ich
wollte nämlich eigentlich nur einen Treiber einschalten, und musste dann
aber die komplete
Walter Wiedmann schrieb:
Serge Gebhardt wrote:
Hast du Packet socket und Socket Filtering im Kernel aktiviert?
beides findest Du unter Networking options. Oder CONFIG_PACKET und
CONFIG_FILTER in .config
Sonst kannst du auch den udhcpc nehmen, der kommt ohne Socket Filtering
aus.
Hallo,
in
Walter Wiedmann [EMAIL PROTECTED] wrote:
Serge Gebhardt wrote:
Walter Wiedmann [EMAIL PROTECTED] wrote:
ich habe da ein kleines Problem mit dem dhclient.
Ich habe zwei Kernelversioen. Bei der 2.4.18 funktioniert der
dhclient ganz normal, und ich bekomme eine IP-Adresse
Ok,
dass war die Lösung!
Danke
--
Walter Wiedmann
Homepage: http://walter-wiedmann.gmxhome.de
--
Haeufig gestellte Fragen und Antworten (FAQ):
http://www.de.debian.org/debian-user-german-FAQ/
Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme?
On Mon, 08 Sep 2003 15:35:17 +1000
CB [EMAIL PROTECTED] wrote:
When I run dhclient, it gives
me an error message : socket: Protocol not available. Make sure
CONFIG_PACKET and CONFIG_FILTER are defined in the kernel config (or
words to that effect).
Like it says, you need those two kernel
On a new install of Debian (Testing) on my laptop (Compaq evo n600c), my
network adapter is not getting an IP. When I run dhclient, it gives me
an error message : socket: Protocol not available. Make sure
CONFIG_PACKET and CONFIG_FILTER are defined in the kernel config (or
words to that
Moin,
bisschen spaet wegen Weihnachten und so ...
On Sun, 2002-12-22 at 17:41, Thorsten Steinbrenner wrote:
[...]
2. Punkt dabei: der jeweilige Rechner muss, bzw. sollte, auch Mitglied
der Domain sein, win2K meldet sich bei Einrichtung des Netzwerks in der
Domain als Member an; bei Linuz
Hallo!
Danke für deine Antwort!
ist SPHINX im DNS-cache eingetragen? Wahrscheinlich wohl nicht. Dies
Nein, ist er nicht, deshalb wollte ich auch DDNS benutzen nachdem ich
das in TCP/IP Network Administration von O'Reily gelesen hatte:
,--- [ Zitat ]
Hallo allerseits!
Ich habe ein seltsames Netzwerkproblem in einem kleinen, heterogenen
Netzwerk, bei dem ich irgendwie nicht weiter komme. Das Netzwerk:
+---+
| Server/Router FLI4L: |
| OS: Linux fli4l 2.0.5 |
Domäne: |
Moin,
On Fri, 2002-12-20 at 19:54, Thorsten Steinbrenner wrote:
[...]
Auf SPHINX läuft ausserdem noch Samba als Fileserver. Das Problem
dabei ist, dass der Nameserver (BIND8 auf FLI4L, DDNS aktiviert)
SPHINX nicht auflösen kann und somit SPHINX auch nicht erreichbar ist.
ist SPHINX im
Ok, tried it again (recompiling the kernel with both variables set) and
now dhclient works. Hence, you were right, thanks for your help. :-) I
must have overlooked something earlier.
Auke
On Sun, 2002-10-27 at 13:48, Colin Watson wrote:
On Sun, Oct 27, 2002 at 01:26:31PM +0100, Auke Jilderda
On Sun, Oct 27, 2002 at 01:26:31PM +0100, Auke Jilderda wrote:
Yup, that did the trick! Thanks a lot, I started to get a serious
headache from hitting the wall for hours. ;-)
Makes me wonder though: Why the heck does Woody default come with
dhclient if it doesn't even work with kernel 2.4?
Ofcourse I included CONFIG_PACKET and I tried both with and without
CONFIG_FILTER. None worked. Why would CONFIG_FILTER be required? It
seems unrelated to DHCP to me.
Auke
On Sun, 2002-10-27 at 13:48, Colin Watson wrote:
woody's dhclient does work with 2.4. You did remember to include
Auke == Auke Jilderda [EMAIL PROTECTED] writes:
Auke Makes me wonder though: Why the heck does Woody default come
Auke with dhclient if it doesn't even work with kernel 2.4? I'd
Auke suspect this is a problem more people will run into.
Uh? It dhclient works great for me with the
For most users dhclient works perfectly with kernel 2.4, IMHO. There seems
to be something interesting in Auke's case.
Qian
On 27 Oct 2002, Shyamal Prasad wrote:
Auke == Auke Jilderda [EMAIL PROTECTED] writes:
Auke Makes me wonder though: Why the heck does Woody default come
Hi fellow Eindhovenaar, (judging from the emailadress :-)),
I also posted my question on the debian-laptop list (because it seemed
to fit their better on second thought) and here's a clue to the issue at
hand:
| Auke == Auke Jilderda [EMAIL PROTECTED] writes:
|
| Auke Why do I need the
Yup, that did the trick! Thanks a lot, I started to get a serious
headache from hitting the wall for hours. ;-)
Makes me wonder though: Why the heck does Woody default come with
dhclient if it doesn't even work with kernel 2.4? I'd suspect this is a
problem more people will run into.
Anyway,
I can not seem to get DHCP to work on its own, except with the stock
kernel that came with Debian. It sees the card, but just does not
pull an IP. I can get it to pull an IP if I manually run pump
/sbin/pump -i eth0. I have no problems using a static ip, or
getting an ip in Windows.
I have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 26 September 2002 04:56 pm, lorac wrote:
I can not seem to get DHCP to work on its own, except with the stock kernel
that came with Debian. It sees the card, but just does not pull an IP. I
can get it to pull an IP if I manually run
On Fri, Jan 25, 2002 at 02:36:09AM +0100, mattias/spikboll wrote:
Jag har själv löst problemet jag hade med dhcp och uppkoppling. Hur gjorde
jag? Jag petade in tp-kabeln ordentligt i nätverkskortet och vips! kontakt.
Jag skäms något otroligt och önskar att jag hade haft ett amerikanskt
mattias/spikboll ([EMAIL PROTECTED]) wrote:
Jag har själv löst problemet jag hade med dhcp och uppkoppling. Hur gjorde
jag? Jag petade in tp-kabeln ordentligt i nätverkskortet och vips! kontakt.
Jag skäms något otroligt och önskar att jag hade haft ett amerikanskt
felsöningsskchema.
Jag har själv löst problemet jag hade med dhcp och uppkoppling. Hur gjorde jag?
Jag petade in tp-kabeln ordentligt i nätverkskortet och vips! kontakt. Jag
skäms något otroligt och önskar att jag hade haft ett amerikanskt
felsöningsskchema.
Problem: Jag kommer inte ut på internet.
Lösning:
Nix, jag har ingen brandvägg körandes.
Så problemet borde vara något annat. eller är de portarna stängda på något
annat sätt?
Min debianburk (unstable) är ansluten till gavlenet, ett för gävle lokalt
fibernät, som delar ut ip-adresser med dhcp.
Jag har aldrig fått dhcp att fungera med debian. När jag gick över från RedHat
till debian för ett halvår sedan löste jag det genom att boota windows (som jag
inte längre
har
Jag gissar på att du har en brandvägg som sätter lite käppar i hjulet.
Jag hade samma problem vilket jag löste med att öppna portar 67 (bootps)
och 68 (bootpc) enligt följande:
Chain OUTPUT (policy DROP)
target prot opt source destination
ACCEPT udp -- 0.0.0.0
I would add: if you want to be able to ping the machine just like you can
windows
boxes then you'll need the Linux version of the software which makes this
mechanism
(Lan Manager a.k.a. Windows Networking) work. This package is called samba and
is
available as a couple different debian
: Wednesday, October 13, 1999 12:36 AM
To: [EMAIL PROTECTED]
Cc: Debian-User
Subject:Re: DHCP problem
A long time ago, in a galaxy far, far way, someone said...
I just installed DHCP client on Debian slink machine. It works almost
fine it just does not pick up the host
sounds like a DNS issue, run a reverse lookup on the IP and see what comes
out. you can also add this line to your /etc/resolv.conf
domain yourdomain.com
that will cause the system to search the local domain when you ping a
hostname. for me if i pinged the host galactica, resolv.conf would
it should look like? :)
Best regards and thank you for help :)
Jersey
--
From: Phil Brutsche[SMTP:[EMAIL PROTECTED]
Sent: Wednesday, October 13, 1999 12:36 AM
To: [EMAIL PROTECTED]
Cc: Debian-User
Subject:Re: DHCP problem
A long time ago, in a galaxy far, far
Hi there :),
I just installed DHCP client on Debian slink machine. It works almost
fine it just does not pick up the host name :(. It is seen on the
network by its IP address only. If I ping it by the name from the local
console it responds that the host name is not known (I removed its
A long time ago, in a galaxy far, far way, someone said...
I just installed DHCP client on Debian slink machine. It works almost
fine it just does not pick up the host name :(. It is seen on the
network by its IP address only. If I ping it by the name from the local
console it responds
Hi,
I just can not use DHCP on my Linux box.
My kernel is 2.2.9
I get the following error:
dhcpcd[1158]: ioctl SIOCSIFBRDADDR (ifConfig): Cannot assign requested
address
since it was giving me this, I tried option -r, does not work either...
As an example, strace dhcpcd -r -d gives me this:
I don't think the problem is the package. I think the problem is in the
configuration.
Looking at the trace you can quickly see that dhcpcd is trying to set the
interface's
IP address *and* broadcast address to 191.255.252.220. I don't think it's legal
to set
an interface's IP address and
80 matches
Mail list logo
