Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On Sat 12 Apr 2025 at 13:09:29 (-0400), Dan Purgert wrote: > On Apr 11, 2025, David Wright wrote: > > On Fri 11 Apr 2025 at 05:45:47 (-0400), Dan Purgert wrote: > > > > > (That doesn't mean you have to use > > > > > mdns, it just means that if you instead decide to do something like > > > > > copy

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On Apr 11, 2025, David Wright wrote: > On Fri 11 Apr 2025 at 05:45:47 (-0400), Dan Purgert wrote: > > > > (That doesn't mean you have to use > > > > mdns, it just means that if you instead decide to do something like > > > > copy hosts files around the network you're choosing to make up your > > >

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On Fri 11 Apr 2025 at 05:45:47 (-0400), Dan Purgert wrote: > On Apr 10, 2025, David Wright wrote: > > > > On Thu 03 Apr 2025 at 06:55:10 (-0400), Greg Wooledge wrote: > > > Or you use mdns, which is the standard way of dealing with dynamic > > > resources on an unmanaged network. > > > > The resou

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On Apr 10, 2025, David Wright wrote: > > > On Thu 03 Apr 2025 at 06:55:10 (-0400), Greg Wooledge wrote: > > Or you use mdns, which is the standard way of dealing with dynamic > > resources on an unmanaged network. > > The resources stay fixed during their lifetime, and any changes that > occur are

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On Tue 08 Apr 2025 at 13:07:34 (-0400), Michael Stone wrote: > On Mon, Apr 07, 2025 at 10:28:12PM -0500, David Wright wrote: > > On Thu 03 Apr 2025 at 06:55:10 (-0400), Greg Wooledge wrote: > > > I disagree with you here. The 127.0.1.1 address is a placeholder put > > > there by the installer for

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On Mon, Apr 07, 2025 at 10:28:12PM -0500, David Wright wrote: On Thu 03 Apr 2025 at 06:55:10 (-0400), Greg Wooledge wrote: I disagree with you here. The 127.0.1.1 address is a placeholder put there by the installer for the more common case where a machine doesn't have a fixed LAN IP address. M

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On Thu 03 Apr 2025 at 06:55:10 (-0400), Greg Wooledge wrote: > On Wed, Apr 02, 2025 at 22:28:24 -0500, David Wright wrote: > > 127.0.1.1 coyote.coyote.den coyote > > [...] > > I don't see the point in leaving it there. If you want to send > > something to coyote.coyote.den, why do you want the LAN

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On Thu, Apr 3, 2025 at 6:55 AM Greg Wooledge wrote: > > On Wed, Apr 02, 2025 at 22:28:24 -0500, David Wright wrote: > > 127.0.1.1 coyote.coyote.den coyote > > [...] > > I don't see the point in leaving it there. If you want to send > > something to coyote.coyote.den, why do you want the LAN addres

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On Wed, Apr 02, 2025 at 10:28:24PM -0500, David Wright wrote: I don't see the point in leaving it there. If you want to send something to coyote.coyote.den, why do you want the LAN address when 127.0.1.1 is just as good. If the line is correct, it does nothing; if it's incorrect, it can cause har

Re: DHCP and static addresses, nothing to do with Re:Who:Bookwormv.Trixie

On 4/2/25 23:29, David Wright wrote: On Wed 02 Apr 2025 at 09:12:24 (-0400), gene heskett wrote: On 4/2/25 01:28, David Wright wrote: On Tue 01 Apr 2025 at 04:58:27 (-0400), gene heskett wrote: On 3/31/25 23:02, David Wright wrote: On Mon 31 Mar 2025 at 16:35:58 (-0400), gene heskett wrote:

Re: DHCP and static addresses, nothing to do with Re: Who: Bookworm v.Trixie

On 3/31/25 13:55, David Wright wrote: On Mon 31 Mar 2025 at 11:19:30 (-0400), gene heskett wrote: The dns problem is separate I guess, but does bring up my other pet peeve. That is that no one at debian considers the effect on dns to those of us who have been using hosts files for local dns sinc

Re: DHCP and static addresses, nothing to do with Re:Who:Bookwormv.Trixie

On 4/3/25 07:49, Dan Purgert wrote: On Apr 02, 2025, David Wright wrote: On Wed 02 Apr 2025 at 09:12:24 (-0400), gene heskett wrote: [...] Experimenting I find the duplication does not seem to generate an error, other than I now had to ping itself by address, since the name is now found at 127.

Re: DHCP and static addresses, nothing to do withRe:Who:Bookwormv.Trixie

On 4/4/25 11:47, John Hasler wrote: Gene writes: Which is to fix the reason for a 30 second all system freeze of the system when trying to access a file I own, or want to create, in my /home/me directory. This happens only in that directory and only when you own the file? I think its a bit mo

Beware of Pocket's off-list goading (Was Re: DHCP and static addresses)

Hi, On Fri, Apr 04, 2025 at 09:48:32AM -0400, Dan Purgert wrote: > Congrats? What point are you trying to make? Pocket also contacted me. As neither of those emails reached the list I assume they have been banned and are trying to goad people in to group-reply back onto the list for them. Thank

Re: IPv6 and loopback addresses (was Re: DHCP and static addresses)

Hi, On Fri, Apr 04, 2025 at 05:21:45AM -0400, gene heskett wrote: > On 4/3/25 13:39, Andy Smith wrote: > > Historically we do not get very far here when talking about IPv6 with > > Gene. > True Andy, but there's no ipv6 within 100 miles of me. The Linux kernel comes with IPv6 on every interface (

Re: DHCP and static addresses, nothing to do with Re:Who:Bookwormv.Trixie

On Fri, Apr 04, 2025 at 10:46:35 -0500, John Hasler wrote: > Gene writes: > > Which is to fix the reason for a 30 second all system freeze of the > > system when trying to access a file I own, or want to create, in my > > /home/me directory. > > This happens only in that directory and only when yo

Re: DHCP and static addresses, nothing to do with Re:Who:Bookwormv.Trixie

Gene writes: > Which is to fix the reason for a 30 second all system freeze of the > system when trying to access a file I own, or want to create, in my > /home/me directory. This happens only in that directory and only when you own the file? -- John Hasler j...@sugarbit.com Elmwood, WI USA

Re: DHCP and static addresses, nothing to do with Re:Who:Bookwormv.Trixie

On 4/4/25 06:10, Dan Purgert wrote: On Apr 03, 2025, Greg wrote: On 2025-04-03, Dan Purgert wrote: That's what you want: as the address is in the 127.0.0.0 network, pinging it will ping itself, and it gets a reply. It doesn't require your LAN to be set up, and AIUI it's like localhost (127.0.

Re: DHCP and static addresses, nothing to do withRe:Who:Bookwormv.Trixie

On 4/4/25 05:57, to...@tuxteam.de wrote: On Fri, Apr 04, 2025 at 05:17:24AM -0400, gene heskett wrote: On 4/3/25 09:29, Greg wrote: On 2025-04-03, Dan Purgert wrote: That's what you want: as the address is in the 127.0.0.0 network, pinging it will ping itself, and it gets a reply. It doesn't

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On Apr 04, 2025, poc...@homemail.com wrote: > > > > Sent: Friday, April 04, 2025 at 6:10 AM > > From: "Dan Purgert" > > To: debian-user@lists.debian.org > > Subject: Re: DHCP and static addresses, nothing to do with Re: > > Who:Bookwormv.Trixie

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On Apr 04, 2025, debian-u...@howorth.org.uk wrote: > Greg Wooledge wrote: > > > I'm just going to assume that it worked similarly to traditional X > > sessions (e.g. the ones on HP-UX), where it looked up the system's > > hostname, and used whatever IP address that returned for connections > > be

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

Greg Wooledge wrote: > I'm just going to assume that it worked similarly to traditional X > sessions (e.g. the ones on HP-UX), where it looked up the system's > hostname, and used whatever IP address that returned for connections > between the X client and server. I'm confused. Traditional X ses

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On Apr 03, 2025, Greg wrote: > On 2025-04-03, Dan Purgert wrote: > > >> That's what you want: as the address is in the 127.0.0.0 network, > >> pinging it will ping itself, and it gets a reply. It doesn't > >> require your LAN to be set up, and AIUI it's like localhost > >> (127.0.0.1) in that it

Re: DHCP and static addresses, nothing to do with Re:Who:Bookwormv.Trixie

On Fri, Apr 04, 2025 at 05:17:24AM -0400, gene heskett wrote: > On 4/3/25 09:29, Greg wrote: > > On 2025-04-03, Dan Purgert wrote: > > > > > > That's what you want: as the address is in the 127.0.0.0 network, > > > > pinging it will ping itself, and it gets a reply. It doesn't > > > > require you

Re: IPv6 and loopback addresses (was Re: DHCP and static addresses)

On 4/3/25 13:39, Andy Smith wrote: Hi, On Thu, Apr 03, 2025 at 01:28:43PM -, Greg wrote: On 2025-04-03, Dan Purgert wrote: Indeed, the entirety of 127.0.0.0/8 is the virtual loopback adapter (i.e. "localhost"). I thought IPV6 opened up the flood gates of assigning "real" ip addresses In

Re: DHCP and static addresses, nothing to do with Re:Who:Bookwormv.Trixie

On 4/3/25 09:29, Greg wrote: On 2025-04-03, Dan Purgert wrote: That's what you want: as the address is in the 127.0.0.0 network, pinging it will ping itself, and it gets a reply. It doesn't require your LAN to be set up, and AIUI it's like localhost (127.0.0.1) in that it doesn't touch the net

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On Thu, Apr 03, 2025 at 22:15:57 -0400, Jeffrey Walton wrote: > Yeah, I'm going to lookup what Stevens has to say about the hosts file > in TCP/IP Illustrated. I need to figure out where the confusion lies. Here's what the Debian manual has to say about it:

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On Thu, Apr 3, 2025 at 10:13 PM Michael Stone wrote: > > On Thu, Apr 03, 2025 at 12:59:19PM -0400, Jeffrey Walton wrote: > >I think the idea is, software can always use 127.0.1.1 to find the > >host's fully qualified domain name, without the need to know real IP > >address. (And what to do with mu

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On Thu, Apr 03, 2025 at 12:59:19PM -0400, Jeffrey Walton wrote: I think the idea is, software can always use 127.0.1.1 to find the host's fully qualified domain name, without the need to know real IP address. (And what to do with multihomed hosts?) It literally doesn't matter. The host knows it

IPv6 and loopback addresses (was Re: DHCP and static addresses)

Hi, On Thu, Apr 03, 2025 at 01:28:43PM -, Greg wrote: > On 2025-04-03, Dan Purgert wrote: > > Indeed, the entirety of 127.0.0.0/8 is the virtual loopback adapter > > (i.e. "localhost"). > > I thought IPV6 opened up the flood gates of assigning "real" ip > addresses In IPv6 you still need lo

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On Thu, Apr 03, 2025 at 12:59:19 -0400, Jeffrey Walton wrote: > I think the idea is, software can always use 127.0.1.1 to find the > host's fully qualified domain name, No. Absolutely not. You have it exactly backwards. The purpose of putting the "127.0.1.1 my_hostname" line in /etc/hosts by de

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On Apr 02, 2025, David Wright wrote: > On Wed 02 Apr 2025 at 09:12:24 (-0400), gene heskett wrote: > > [...] > > Experimenting I find the duplication does not seem to generate an > > error, other than I now had to ping itself by address, since the name > > is now found at 127.0.1.1 by pings lookup?

Re: DHCP and static addresses, nothing to do with Re:Who:Bookwormv.Trixie

On 4/3/25 06:55, Greg Wooledge wrote: On Wed, Apr 02, 2025 at 22:28:24 -0500, David Wright wrote: 127.0.1.1 coyote.coyote.den coyote [...] I don't see the point in leaving it there. If you want to send something to coyote.coyote.den, why do you want the LAN address when 127.0.1.1 is just as good

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On 2025-04-03, Dan Purgert wrote: >> That's what you want: as the address is in the 127.0.0.0 network, >> pinging it will ping itself, and it gets a reply. It doesn't >> require your LAN to be set up, and AIUI it's like localhost >> (127.0.0.1) in that it doesn't touch the network hardware. > > I

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On Wed, Apr 02, 2025 at 22:28:24 -0500, David Wright wrote: > 127.0.1.1 coyote.coyote.den coyote > [...] > I don't see the point in leaving it there. If you want to send > something to coyote.coyote.den, why do you want the LAN address > when 127.0.1.1 is just as good. If the line is correct, it do

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On Wed 02 Apr 2025 at 09:12:24 (-0400), gene heskett wrote: > On 4/2/25 01:28, David Wright wrote: > > On Tue 01 Apr 2025 at 04:58:27 (-0400), gene heskett wrote: > > > On 3/31/25 23:02, David Wright wrote: > > > > On Mon 31 Mar 2025 at 16:35:58 (-0400), gene heskett wrote: > > > > > On 3/31/25 13:

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On 4/2/25 01:28, David Wright wrote: On Tue 01 Apr 2025 at 04:58:27 (-0400), gene heskett wrote: On 3/31/25 23:02, David Wright wrote: On Mon 31 Mar 2025 at 16:35:58 (-0400), gene heskett wrote: On 3/31/25 13:55, David Wright wrote: I don't know why you have problems with using /etc/hosts for

Re: DHCP and static addresses, nothing to do with Re: Who: Bookwormv.Trixie

On Tue 01 Apr 2025 at 04:58:27 (-0400), gene heskett wrote: > On 3/31/25 23:02, David Wright wrote: > > On Mon 31 Mar 2025 at 16:35:58 (-0400), gene heskett wrote: > > > On 3/31/25 13:55, David Wright wrote: > > > > I don't know why you have problems with using /etc/hosts for lookups > > > > on you

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On Tue, Apr 01, 2025 at 12:25:36PM -0400, gene heskett wrote: > On 4/1/25 08:59, to...@tuxteam.de wrote: > > On Tue, Apr 01, 2025 at 01:36:21PM +0100, mick.crane wrote: > > > On 2025-04-01 13:21, to...@tuxteam.de wrote: > > > > On Tue, Apr 01, 2025 at 12:42:46PM +0100, mick.crane wrote: > > > > >

Re: DHCP and static addresses, nothing to do with Re: Who: Bookwormv.Trixie

On 2025-04-01 13:21, to...@tuxteam.de wrote: On Tue, Apr 01, 2025 at 12:42:46PM +0100, mick.crane wrote: [...] the spaces look wrong to me If you mean those: 192.168.71.122 bpi51e5p.coyote.den bpi51 e5p #3dprinter ^^^ ... 192.168.71.121

Re: DHCP and static addresses, nothing to do with Re: Who:Bookwormv.Trixie

On 4/1/25 08:59, to...@tuxteam.de wrote: On Tue, Apr 01, 2025 at 01:36:21PM +0100, mick.crane wrote: On 2025-04-01 13:21, to...@tuxteam.de wrote: On Tue, Apr 01, 2025 at 12:42:46PM +0100, mick.crane wrote: [...] the spaces look wrong to me If you mean those: 192.168.71.122 bpi51e5p.coyot

Re: DHCP and static addresses, nothing to do with Re: Who: Bookwormv.Trixie

On Tue, Apr 01, 2025 at 12:42:46PM +0100, mick.crane wrote: [...] > the spaces look wrong to me If you mean those: > 192.168.71.122 bpi51e5p.coyote.den bpi51 e5p #3dprinter ^^^ > ... > 192.168.71.121 mkspi.coyote.denmkspi xmax3 # 3dpri

Re: DHCP and static addresses, nothing to do with Re: Who: Bookwormv.Trixie

On Tue, Apr 01, 2025 at 01:36:21PM +0100, mick.crane wrote: > On 2025-04-01 13:21, to...@tuxteam.de wrote: > > On Tue, Apr 01, 2025 at 12:42:46PM +0100, mick.crane wrote: > > > > [...] > > > > > the spaces look wrong to me > > > > If you mean those: > > > > > 192.168.71.122 bpi51e5p.coyote.den

Re: DHCP and static addresses, nothing to do with Re: Who: Bookwormv.Trixie

On 2025-04-01 09:58, gene heskett wrote: 127.0.0.1   localhost 192.168.71.1    router.coyote.den   router # dd-wrt 192.168.71.2    amanda.coyote.den   amanda # backup under construction 192.168.71.3    coyote.coyote.den   coyote # this big tower 192.168.71.4    sixty40.coyote.d

Re: DHCP and static addresses, nothing to do with Re: Who: Bookwormv.Trixie

On 3/31/25 23:02, David Wright wrote: On Mon 31 Mar 2025 at 16:35:58 (-0400), gene heskett wrote: On 3/31/25 13:55, David Wright wrote: I don't know why you have problems with using /etc/hosts for lookups on your LAN. I use it here without any problems, and it has to work because there's no DNS

Re: DHCP and static addresses, nothing to do with Re: Who: Bookworm v.Trixie

On Mon, Mar 31, 2025 at 10:01:37PM -0500, David Wright wrote: > On Mon 31 Mar 2025 at 16:35:58 (-0400), gene heskett wrote: > > On 3/31/25 13:55, David Wright wrote: > > > I don't know why you have problems with using /etc/hosts for lookups > > > on your LAN. I use it here without any problems, and

Re: DHCP and static addresses, nothing to do with Re: Who: Bookworm v.Trixie

On Mon 31 Mar 2025 at 16:35:58 (-0400), gene heskett wrote: > On 3/31/25 13:55, David Wright wrote: > > I don't know why you have problems with using /etc/hosts for lookups > > on your LAN. I use it here without any problems, and it has to work > > because there's no DNS server in my router (too ch

Re: DHCP Problem

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'

Re: DHCP Problem

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.

Re: DHCP Problem, but where

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

Re: DHCP Problem

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

Re: DHCP Problem, but where

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

Re: DHCP Problem, but where

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/

Re: DHCP Problem, but where

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

Re: DHCP Problem

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

Re: DHCP Problem, but where

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

Re: DHCP Problem

> 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

Re: DHCP Problem

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

Re: DHCP and search list for DNS domains

On Fri 21 Jan 2022 at 13:57:47 (+0100), Steve Keller wrote: > AFAIK, some of my client hosts have only resolvconf, others use some > systemd stuff, since the man page for resolvconf is actually the > man page for resolvectl which also refers to systemd-resolved. The man page for /package/ resolvc

Re: DHCP and search list for DNS domains

"Markus Schönhaber" wrote: > > AFAICS, there is no option in DHCP to provide the search list. > > From dhcp-options(5): > > >option domain-search domain-list; > > > > The domain-search option specifies a ´search list´ of Domain > > Names to be used by the client

Re: DHCP and search list for DNS domains

On Fri, 21 Jan 2022 13:57:47 +0100 Steve Keller wrote: > With DHCP I can tell a host the DNS server and the domain name of the > network, which is then stored to /etc/resolv.conf. But how can I add > a list a domain names that should be searched when resolving a host > name? root@chaffee:~# gre

Re: DHCP and search list for DNS domains

21.01.22, 13:57 +0100, Steve Keller: With DHCP I can tell a host the DNS server and the domain name of the network, which is then stored to /etc/resolv.conf. But how can I add a list a domain names that should be searched when resolving a host name? AFAICS, there is no option in DHCP to provid

Re: DHCP server for other site

On 12/10/2021 6:45 PM, Bonno Bloksma wrote: Hi, I want to move my DHCP servers to my datacenter as I am going to shut down the hypervisor hosts on some locations. [...] And as that is the only interface for the VM the dhcp software wil fail to start. So my solution was to add a few lines t

RE: DHCP server for other site

Hi, > I want to move my DHCP servers to my datacenter as I am going to shut down > the hypervisor hosts on some locations. [...] > And as that is the only interface for the VM the dhcp software wil fail to > start. > So my solution was to add a few lines to the config > shared-network datacent

Re: dhcp bridge for virtual machines using KVM

On 9/23/20 2:25 AM, Fabien Roucaute wrote: Le 22/09/2020 à 22:57, James Allsopp a écrit : On Tue, 22 Sep 2020 at 17:58, Fabien Roucaute mailto:fabien.rouca...@free.fr>> wrote: Le 22/09/2020 à 18:50, James Allsopp a écrit : > > I've tried that but I get the same result. >

Re: dhcp bridge for virtual machines using KVM

On 9/23/2020 3:14 PM, Fabien Roucaute wrote: Le 23/09/2020 à 13:50, James Allsopp a écrit : Yes, it's a bit odd,but the reason I want to do it like this is that the wifi is pretty fast and the ethernet is constrained by powerline networking to about 50Mbps. However, I can't run a bridge over th

Re: dhcp bridge for virtual machines using KVM

Le 23/09/2020 à 13:50, James Allsopp a écrit : > Yes, it's a bit odd,but the reason I want to do it like this is that the > wifi is pretty fast and the ethernet is constrained by powerline > networking to about 50Mbps. However, I can't run a bridge over the wifi, > so I'm trying to run all the hos

Re: dhcp bridge for virtual machines using KVM

On Tue, 22 Sep 2020 at 22:30, Lucas Castro wrote: > > On 9/22/20 5:54 PM, James Allsopp wrote: > > > > On Tue, 22 Sep 2020 at 19:47, Lucas Castro wrote: > >> >> On 9/22/20 1:26 PM, James Allsopp wrote: >> > Hi, >> > I've got a computer that I'm running debian 10 on with KVM. The >> > machine is

Re: dhcp bridge for virtual machines using KVM

Le 22/09/2020 à 22:57, James Allsopp a écrit : > > > On Tue, 22 Sep 2020 at 17:58, Fabien Roucaute > wrote: > > Le 22/09/2020 à 18:50, James Allsopp a écrit : > > > > I've tried that but I get the same result. > > Thanks > > James > > > >

Re: dhcp bridge for virtual machines using KVM

On 9/22/20 5:54 PM, James Allsopp wrote: On Tue, 22 Sep 2020 at 19:47, Lucas Castro > wrote: On 9/22/20 1:26 PM, James Allsopp wrote: > Hi, > I've got a computer that I'm running debian 10 on with KVM. The > machine is connected to a OpenWRT ro

Re: dhcp bridge for virtual machines using KVM

On Tue, 22 Sep 2020 at 17:58, Fabien Roucaute wrote: > Le 22/09/2020 à 18:50, James Allsopp a écrit : > > > > I've tried that but I get the same result. > > Thanks > > James > > > > You need to answer to the mailing-list email address, not mine. > If it still doesn't work, we need more informatio

Re: dhcp bridge for virtual machines using KVM

On Tue, 22 Sep 2020 at 19:47, Lucas Castro wrote: > > On 9/22/20 1:26 PM, James Allsopp wrote: > > Hi, > > I've got a computer that I'm running debian 10 on with KVM. The > > machine is connected to a OpenWRT router which provides DHCP and DNS > > to the network, via a wifi link used for the host

Re: dhcp bridge for virtual machines using KVM

On 9/22/20 1:26 PM, James Allsopp wrote: Hi, I've got a computer that I'm running debian 10 on with KVM. The machine is connected to a OpenWRT router which provides DHCP and DNS to the network, via a wifi link used for the host and an ethernet connection on eth1 used for a bridge Is your O

Re: dhcp bridge for virtual machines using KVM

Le 22/09/2020 à 18:50, James Allsopp a écrit : > > I've tried that but I get the same result. > Thanks > James > You need to answer to the mailing-list email address, not mine. If it still doesn't work, we need more information, like the result of the following commands (you should modify the pu

Re: dhcp bridge for virtual machines using KVM

Le 22/09/2020 à 18:26, James Allsopp a écrit : > Hi, > I've got a computer that I'm running debian 10 on with KVM. The machine > is connected to a OpenWRT router which provides DHCP and DNS to the > network, via a wifi link used for the host and an ethernet connection on > eth1 used for a bridge >

Re: DHCP log different location but warnings in syslog

Hi. On Wed, Dec 12, 2018 at 12:52:58PM +, Bonno Bloksma wrote: > Hi, > > Plenty of examples on-line how to move logging from the isc-dhcp-server to a > different file using something like > log-facility local7; > in the dhcp.conf file and then in my syslog.conf: > *.debug,local6.none

RE: dhcp service problem on stretch

Hi, David, your last info let me correctly purg the dhcp-server environment without recreating a new virtual machine, thanks. > # apt-get purge > with no arguments should do (and did) nothing. It's not like, say, the Vax > purge command where no arguments means Operate On All Files. > So specify

Re: dhcp service problem on stretch

On Fri 07 Sep 2018 at 09:58:23 (+), Bonno Bloksma wrote: > Ok, did: > # apt-get remove isc-dhcp-server > # apt-get purge > reboot > Hmm, purge did not clean everything so: > # rm /etc/default/isc-dhcp-server > # rm /etc/dhcp/dhcpd* # apt-get purge with no arguments should do (and did) nothing

RE: dhcp service problem on stretch

Hi, >On Thu, Sep 06, 2018 at 05:33:39PM +, Bonno Bloksma wrote: >> Sep 06 17:47:42 linom1 isc-dhcp-server[1668]: Launching both IPv4 and IPv6 >> servers (please configure INTERFACES in /etc/default/isc-dhcp-server if > Please edit the file above and place your network interfaces there. Ok,

Re: dhcp service problem on stretch

On Thu, 6 Sep 2018 17:33:39 + Bonno Bloksma wrote: > Hi, > > Just installed my first stretch server using the 9.5 DVD1, installed > the normal system environment, no desktop just a ssh server, and > added the isc dhcp server. I transferred my original dhcpf.conf file, > stripped what I did n

Re: dhcp service problem on stretch

Hi. On Thu, Sep 06, 2018 at 05:33:39PM +, Bonno Bloksma wrote: > It seems the dhcp service does not want to start but I have no idea why. > I have stripped my dhcpd.conf down to barely nothing and a regular test gives > no errors but the service refuses to start, why? ... > Also the l

Re: dhcp service problem on stretch

On Thu, Sep 06, 2018 at 05:33:39PM +, Bonno Bloksma wrote: > Sep 06 17:47:42 linom1 isc-dhcp-server[1668]: Launching both IPv4 and IPv6 > servers (please configure INTERFACES in /etc/default/isc-dhcp-server if Please edit the file above and place your network interfaces there. best regards

Re: dhcp service problem on stretch

On Thu, Sep 06, 2018 at 05:33:39PM +, Bonno Bloksma wrote: > Sep 06 17:47:42 linom1 isc-dhcp-server[1668]: /etc/init.d/isc-dhcp-server: > 50: /etc/init.d/isc-dhcp-server: cannot open /etc/dhcp/dhcpd6.conf: No > Sep 06 17:47:42 linom1 isc-dhcp-server[1668]: Launching both IPv4 and IPv6 > serve

Re: Re: Re: DHCP to static without reboot?

If I use a completely vanilla freshly installed VM (on VirtualBox)...  LXDE, but otherwise standard options: Even a simple "ifdown " with no configuration changes gives inconsistent results.  Three different results so far: 1) Sometimes it SEEMS like it releases the DHCP address, and complete

Re: DHCP to static without reboot?

On Saturday 25 August 2018 06:02:20 Gene Heskett wrote: > On Saturday 25 August 2018 04:20:51 to...@tuxteam.de wrote: > > On Sat, Aug 25, 2018 at 03:54:32AM -0400, Gene Heskett wrote: > > > > [...] > > > > > I've experienced that on a armbian install on a rock64, it takes > > > sometimes 2 or 3 po

Re: DHCP to static without reboot?

On Saturday 25 August 2018 04:20:51 to...@tuxteam.de wrote: > On Sat, Aug 25, 2018 at 03:54:32AM -0400, Gene Heskett wrote: > > [...] > > > I've experienced that on a armbian install on a rock64, it takes > > sometimes 2 or 3 powerdown recycles to make a change in e-n-i.d/name > > of interface to

Re: DHCP to static without reboot?

On Saturday 25 August 2018 04:20:51 to...@tuxteam.de wrote: > On Sat, Aug 25, 2018 at 03:54:32AM -0400, Gene Heskett wrote: > > [...] > > > I've experienced that on a armbian install on a rock64, it takes > > sometimes 2 or 3 powerdown recycles to make a change in e-n-i.d/name > > of interface to

Re: DHCP to static without reboot?

On Sat, Aug 25, 2018 at 03:54:32AM -0400, Gene Heskett wrote: [...] > I've experienced that on a armbian install on a rock64, it takes > sometimes 2 or 3 powerdown recycles to make a change in e-n-i.d/name of > interface to stick [...] That sounds a bit like Voodoo. But then, there's Clarke's

Re: DHCP to static without reboot?

On Friday 24 August 2018 23:33:49 Mark Pavlichuk wrote: > ifdown doesn't seem to work.  It seems to complete successfully with > messages about a released DHCP address, but ifconfig shows the > interface is still up, a ping will be returned etc...  Though if I try > another ifdown it will say the

Re: Re: DHCP to static without reboot?

ifdown doesn't seem to work.  It seems to complete successfully with messages about a released DHCP address, but ifconfig shows the interface is still up, a ping will be returned etc...  Though if I try another ifdown it will say the interface is not configured. If I then make configuration ch

Re: DHCP to static without reboot?

I spoke too soon... I'm getting inconsistent results each time I try...  with things usually not working.  I usually brute-force problems by just exploring every combination of configuration and commands, but something very weird is going on here. Now I'm getting : Job for networking.servic

Re: DHCP to static without reboot?

Ahh, the problem was the "allow-hotplug" that my interface acquired...  though it's weird that even stopping dhclient and the network daemon didn't stop the interface from bouncing back up (with a DHCP address).  Is there some other daemon I'm unaware of?  (I was experimenting with a fresh Stre

RE: dhcp restart with bad config

Hello Liam and list, >> Today I had a small (big?) problem with the DHCP server. >> When I make any changes I allways do a >> # service isc-dhcp-server >> restart to test the new config. In the past when there was an error in >> the config the service would keep running using the previous config

Re: dhcp restart with bad config

On 2017-08-29, Bonno Bloksma wrote: > Hi, > > Today I had a small (big?) problem with the DHCP server. > When I make any changes I allways do a > # service isc-dhcp-server restart > to test the new config. In the past when there was an error in the config the > service would keep running using th

Re: DHCP server that itself gets an IP address by DHCP

On Fri, Aug 25, 2017 at 10:12:07PM +0900, Mark Fletcher wrote: > However, now, based on your response I am thinking the AirStation is > just forwarding the DNS queries on to the nameservers it is given in > response to its DHCP query, and not actually caching anything... Very likely, yes. > wou

Re: DHCP server that itself gets an IP address by DHCP

On Fri, Aug 25, 2017 at 08:14:29AM -0400, Greg Wooledge wrote: > On Fri, Aug 25, 2017 at 07:34:16AM +0900, Mark Fletcher wrote: > > On Thu, Aug 24, 2017 at 04:39:13PM -0400, Greg Wooledge wrote: > > > I strongly recommend just running your own caching DNS resolver on the > > > DHCP server host. IS

Re: DHCP server that itself gets an IP address by DHCP

On Fri, Aug 25, 2017 at 07:28:00AM +0900, Mark Fletcher wrote: > And, is dhclient a separate piece of software from systemd.networkd? Yes.

Re: DHCP server that itself gets an IP address by DHCP

On Fri, Aug 25, 2017 at 07:34:16AM +0900, Mark Fletcher wrote: > On Thu, Aug 24, 2017 at 04:39:13PM -0400, Greg Wooledge wrote: > > I strongly recommend just running your own caching DNS resolver on the > > DHCP server host. ISP nameservers are often slow and unreliable. > > OK, thanks for the ad

Re: DHCP server that itself gets an IP address by DHCP

Hi. On Fri, 25 Aug 2017 07:28:00 +0900 Mark Fletcher wrote: > On Thu, Aug 24, 2017 at 11:35:25PM +0300, Reco wrote: > > On Thu, 24 Aug 2017 22:21:04 +0200 > > Pascal Hambourg wrote: > > > > > Le 24/08/2017 à 11:30, Reco a écrit : > > > > > > > > Somewhat hackish, but straightforward w

Re: DHCP server that itself gets an IP address by DHCP

On Thu, Aug 24, 2017 at 04:39:13PM -0400, Greg Wooledge wrote: > On Thu, Aug 24, 2017 at 10:21:04PM +0200, Pascal Hambourg wrote: > > Le 24/08/2017 à 11:30, Reco a écrit : > > > > > > Somewhat hackish, but straightforward way to achieve this is to redirect > > > DNS requests from your LAN to corre

  1   2   3   4   5   6   7   8   >