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 network'
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 anyway.
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 th
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 prev
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 signat
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 rest
> 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. Is
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 manuall
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 cli
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-
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 a
-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 i
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 (s
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
http://bugs.debian.org/cgi-bin/bugreport.c
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-clien
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 l
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.
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
|
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 switchin
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 s
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) fr
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
> r
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
> route
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
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
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 but to assign ip stat
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 address
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
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 th
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
>
"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 wi
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 bo
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
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, th
-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 ru
e the
> problem if you know what I mean :))).
> Jens Jorgensen mentiond about a script updating "hosts" file
> automatically... would you have any idea it should look like? :)
>
> Best regards and thank you for help :)
> "Jersey"
>
> ------
> F
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
automa
t;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 way, someone said...
> I just installed DHCP client on Debian sli
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 packages.
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 respo
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 broadc
45 matches
Mail list logo
