basti writes:
> Whats wrong there?
> Can someone put me in the wright direction?
Must you use kea-dhcp? I researched a similar situation (I think, I'm
not 100% from your description) and dnsmasq as DHCP server can handle
this.
Hello,
maybe a bit off topic.
The goal is to have a central DHCP/DNS server for multiple IP ranges in
the same network.
- LAN has 192.168.30.0/24
- guest should have 10.10.10.0/24
At the moment LAN and guest has different interfaces but i have to
change this.
A new wifi repeater / AP
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
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
> ol
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
>
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 ol
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
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 ma
s
> using the old router.
>
> > The DHCProtocol has "release" for such goosing.
> > At DHCPclient do "stop DHCP", over the wire goes DHCPRELEASE [0]
> > The DHCPclient should forget ( "release" ) previous settings.
> > At DHCPclient do "start DHCP&
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 DHCPc
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 f
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 anybod
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
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 se
> 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 th
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 n
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
On 23.03.2023 09:36, h...@hanswkraus.com wrote:
Hi,
a pc with a plain vanilla Debian11 doesn't renew the dhcp lease
automatically, I have to do it per hand (systemctl stop ifup@$1.service
&& systemctl start ifup@$1.service).
The "/var/lib/dhcp/dhclient.lan0
Hi,
a pc with a plain vanilla Debian11 doesn't renew the dhcp lease
automatically, I have to do it per hand (systemctl stop ifup@$1.service
&& systemctl start ifup@$1.service).
The "/var/lib/dhcp/dhclient.lan0.leases" file:
=
ipes desde un relay situado en el
> > > conmutador.
> > > Si en el servidor DHCP pongo la opción 66 (next-server) parece
> > > funcionar, si no no funciona.
> > > no deberia dar este parametro el proxy-dhcp.
> > > mi configuración:
> > > port=0
El jue, 19-01-2023 a las 20:38 +0100, Camaleón escribió:
> El 2023-01-19 a las 13:49 +0100, trujo escribió:
>
> > Estoy intentando ponerlo en marcha (con debian estable).
> > la red en la que esta recibe ipes desde un relay situado en el
> > conmutador.
> > Si en el
Estoy intentando ponerlo en marcha (con debian estable).
la red en la que esta recibe ipes desde un relay situado en el
conmutador.
Si en el servidor DHCP pongo la opción 66 (next-server) parece
funcionar, si no no funciona.
no deberia dar este parametro el proxy-dhcp.
mi configuración:
port=0
log
problemas y los que tenía se solucionaron.
Sldos,
Marcelo.-
-Mensaje original-
De: JavierDebian [mailto:javier.debian.bb...@gmail.com]
Enviado el: lunes, 22 de agosto de 2022 18:06
Para: debian-user-spanish@lists.debian.org
Asunto: Re: IP por DHCP dejó de funcionar en Debian "bullseye"
El lun, 22 ago 2022 a la(s) 16:22, Yoel Villarreal (yoe...@nauta.cu) escribió:
>
> Quizás no fue algo "roto". Quizás fue que no leímos el changelog.
El top posting no es lindo
Y yo tampoco leí el change log. ¿Qué dice que cambió?
Saludos,
Antonio Galicia
Eram quod es, eris quod sum
--
bido en el sistema, lo odio porque hace lo que quiere.
Computadora que funciona desde hace 6 años con configuración de red por DHCP
automática, configurado "a mano" por interfaces.
resolvconf corriendo como demonio.
Hace un par de días, se puso remolona para tomar dirección IP. Reinicia
e funciona desde hace 6 años con configuración de red por DHCP
automática, configurado "a mano" por interfaces.
resolvconf corriendo como demonio.
Hace un par de días, se puso remolona para tomar dirección IP. Reiniciado el
enrutador y el equipo un par de veces, lo achaqué a problemas
ace 6 años con configuración de red por DHCP
> automática, configurado "a mano" por interfaces.
> resolvconf corriendo como demonio.
>
> Hace un par de días, se puso remolona para tomar dirección IP. Reiniciado el
> enrutador y el equipo un par de veces, lo achaqué a problem
Buenas noches.
Me ha pasado algo extraño.
Debian 11 "bullseye" con kernel 5.10.0-16-amd64.
Network-manager prohibido en el sistema, lo odio porque hace lo que quiere.
Computadora que funciona desde hace 6 años con configuración de red por
DHCP automática, configurado "a mano&
john doe writes:
[...]
>>
>
> You might be better off asking this on the appropriate mailing list! :)
I asked:
https://lists.freedesktop.org/archives/systemd-devel/2022-May/047889.html
My impressions:
1. Scripts called by dhcp client are "BAD THING" (according
On 2022-06-02, David Wright wrote:
>
>> I still owe David a response to his last post.
>
> No need. The above clears up the point made in the body of your OP,
> and I have nothing more to add on the Subject line, as what I've
> already posted pretty much exhausts my knowledg
need. The above clears up the point made in the body of your OP,
and I have nothing more to add on the Subject line, as what I've
already posted pretty much exhausts my knowledge of DHCP.
Cheers,
David.
On 05/31/2022 08:13 AM, Richard Owlett wrote:
I'm using firmware-11.3.0-amd64-netinst.iso to install Debian onto a
Lenovo T510 [Thinkpad].
I know the netinstaller works on this laptop as I have done a successful
install when within range of of local library's wifi and the installer
is
non-free drivers.
Again, the OP never made any mention of this.
> I tried to succinctly state MY topic in the Subject line.
> When The DHCP auto-detection during install fails,
> "How do I manually discover DHCP [server] hostname(s)?"
Ah, now, I recognise /that/ as a ques
On Wed 01 Jun 2022 at 06:32:07 -0500, Richard Owlett wrote:
[...]
> As stated in this post the particular machine is dedicated to
> EXPERIMENTATION. The goal of the experimentation is to be able to describe
> how the Debian installation process could simultaneously be simpler and more
>
On 05/31/2022 02:00 PM, Richard Owlett wrote:
*SNIP*
I am doing a fresh install from home using an Alcatel Linkzone to
connect to my T-mobile account. I have had no problems doing this with
standard netinstallers.
? That seems to be a new interpretation of the thread:
mware
rather than, say wifi vs ethernet in the normal scenario, or wifi vs
some sort of ?USB link in your case.
No ;/
I tried to succinctly state MY topic in the Subject line.
When The DHCP auto-detection during install fails,
"How do I manually discover DHCP hostname(s)?"
Is that fair, a
On Tue 31 May 2022 at 14:00:51 (-0500), Richard Owlett wrote:
> On 05/31/2022 11:13 AM, David Wright wrote:
> > On Tue 31 May 2022 at 08:13:57 (-0500), Richard Owlett wrote:
> > > I'm using firmware-11.3.0-amd64-netinst.iso to install Debian onto a
> > > Lenovo T510 [Thinkpad].
> >
> > ✓
> >
> >
On 05/31/2022 11:13 AM, David Wright wrote:
On Tue 31 May 2022 at 08:13:57 (-0500), Richard Owlett wrote:
I'm using firmware-11.3.0-amd64-netinst.iso to install Debian onto a
Lenovo T510 [Thinkpad].
✓
I know the netinstaller works on this laptop as I have done a
successful install when
On Tue 31 May 2022 at 08:13:57 (-0500), Richard Owlett wrote:
> I'm using firmware-11.3.0-amd64-netinst.iso to install Debian onto a
> Lenovo T510 [Thinkpad].
✓
> I know the netinstaller works on this laptop as I have done a
> successful install when within range of of local library's wifi and
>
I'm using firmware-11.3.0-amd64-netinst.iso to install Debian onto a
Lenovo T510 [Thinkpad].
I know the netinstaller works on this laptop as I have done a successful
install when within range of of local library's wifi and the installer
is successfully detecting multiple local wifi sources.
ork setup.
But in my case udhcpc seems to be the only DHCP client that will talk to
the LTE module in my router, others just balk and whine.
On 2022-05-08 11:19:33 +0800, Jeremy Ardley wrote:
> Of note: Using systemd-networkd you should not use NetworkManager or
> networking services. I think both use the ISC dhcp client
And what about NetworkManager users?
Note: it has its own internal DHCP client, but it is not robust on
On 5/8/2022 6:33 PM, Kamil Jońca wrote:
Kamil Jońca writes:
[...]
But systemd-networkd also has a huge number of configuration options
that may do what you want anyway
https://www.freedesktop.org/software/systemd/man/systemd.network.html
Hm. Can you create bridge without ports with
Kamil Jońca writes:
[...]
>>
>> But systemd-networkd also has a huge number of configuration options
>> that may do what you want anyway
>>
>> https://www.freedesktop.org/software/systemd/man/systemd.network.html
>
> Hm. Can you create bridge without ports with systemd-networkd?
> i.e.
>
On Sun, May 08, 2022 at 04:09:27PM +0200, Oliver Schoede wrote:
Alternatively there's dhcpcd5,
Be careful with this one unless you have a simple network
configuration--by default it will attempt to get addresses on all
interfaces that don't have them, not only ones you set to dhcp in
/etc
On Sun, 8 May 2022 09:20:25 -0400
Dan Ritter wrote:
> Stefan Monnier wrote:
> > Rick Thomas [2022-05-07 19:47:57] wrote:
> > > According to the ISC webpage:
> > >> ISC has ended development on the ISC DHCP client as of early
> > >> 2022. This cli
Stefan Monnier wrote:
> Rick Thomas [2022-05-07 19:47:57] wrote:
> > According to the ISC webpage:
> >> ISC has ended development on the ISC DHCP client as of early 2022.
> >> This client implementation is no longer maintained and should not be
> >> used in pr
On 2022-05-08 at 07:06, Rick Thomas wrote:
> On Sat, May 7, 2022, at 7:47 PM, Rick Thomas wrote:
>
>> According to the ISC webpage:
>>
>>> ISC has ended development on the ISC DHCP client as of early
>>> 2022. This client implementation is no longer m
On Sat, May 7, 2022, at 7:47 PM, Rick Thomas wrote:
> According to the ISC webpage:
>
>> ISC has ended development on the ISC DHCP client as of early 2022.
>> This client implementation is no longer maintained and should not be
>> used in production any longer.
>
>
e.com/questions/469716/systemd-networkd-run-script-after-dhcp-client-aqcuires-new-address
You mean:
"I couldn't get networkd-dispatcher to respond to dhcp changes on Ubuntu
Server 20.04, but[...] " :) ?
Yes. I know that this is two year old, but I did not found anything
newer with answer.
On 8/5/22 2:27 pm, Rick Thomas wrote:
Thanks!
Rick
PS: I'll also do the IPv6 part, because I'm interested in that too.
One word of caution moving away from ISC dhcp client is that any
possibility of it being started by the networking daemon will result in
very bad behaviour if you have
On 8/5/22 3:19 pm, Kamil Jońca wrote:
I cannot see if systemd-networkd can run scripts[1] after change in
lease. Am I missing something?
The top answer below is a partial answer to your question.
https://unix.stackexchange.com/questions/469716/systemd-networkd-run-script-after-dhcp-client
Jeremy Ardley writes:
[...]
>
> You can just use systemd-networkd as an IPv4 dhcp client.
I cannot see if systemd-networkd can run scripts[1] after change in
lease. Am I missing something?
KJ
[1] similar to /etc/dhcp/dhclient*hooks.d
--
http://wolnelektury.pl/wesprzyj/teraz/
On 5/8/2022 5:24 AM, Rick Thomas wrote:
On Sat, May 7, 2022, at 8:14 PM, Jeremy Ardley wrote:
On 8/5/22 10:47 am, Rick Thomas wrote:
ISC has ended development on the ISC DHCP client as of early 2022.
This client implementation is no longer maintained and should not be
used in production any
On Sat, May 7, 2022, at 9:37 PM, Jeremy Ardley wrote:
> On 8/5/22 11:27 am, Rick Thomas wrote:
>> Thanks for the heads up!
>> Can you describe in detail what one needs to do in order to switch over?
>> I.e. what to remove, what to install? What to configure?
>
> This is a recent blogpost of
On 8/5/22 11:27 am, Rick Thomas wrote:
Thanks for the heads up!
Can you describe in detail what one needs to do in order to switch over? I.e.
what to remove, what to install? What to configure?
This is a recent blogpost of mine showing a more complex installation
including IPv6
On Sat, May 7, 2022, at 8:19 PM, Jeremy Ardley wrote:
> On 8/5/22 11:14 am, Jeremy Ardley wrote:
>>
>>
>> You can just use systemd-networkd as an IPv4 dhcp client.
>>
>>
>
> Of note: Using systemd-networkd you should not use NetworkManager or
> networki
On Sat, May 7, 2022, at 8:14 PM, Jeremy Ardley wrote:
> On 8/5/22 10:47 am, Rick Thomas wrote:
>> ISC has ended development on the ISC DHCP client as of early 2022.
>>> This client implementation is no longer maintained and should not be
>>> used in production any longe
On 8/5/22 11:14 am, Jeremy Ardley wrote:
You can just use systemd-networkd as an IPv4 dhcp client.
Of note: Using systemd-networkd you should not use NetworkManager or
networking services. I think both use the ISC dhcp client
Of further note, I moved to systemd-networkd precisely
On 8/5/22 10:47 am, Rick Thomas wrote:
ISC has ended development on the ISC DHCP client as of early 2022.
This client implementation is no longer maintained and should not be
used in production any longer.
Can anybody recommend a good replacement?
I presently use systemd-networkd which
According to the ISC webpage:
> ISC has ended development on the ISC DHCP client as of early 2022.
> This client implementation is no longer maintained and should not be
> used in production any longer.
Can anybody recommend a good replacement?
Does anybody know what the Debian PTBs are
Salut,
Un extrait de "apt search dhcp" :
isc-dhcp-relay/oldstable,now 4.4.1-2+deb10u1 amd64 [installed]
ISC DHCP relay daemon
isc-dhcp-server/oldstable 4.4.1-2+deb10u1 amd64
ISC DHCP server for automatic IP address assignment
Lancé sur le relais DHCP qui est mon mini-routeur. Sur
Bonjour
Le 11/03/2022 à 12:48, Olivier a écrit :
Bonjour,
Je souhaite mettre en place sur une machine Bullseye, un service DHCP
traitant 250 réseaux locaux de petite taille (/28 soit 16 adresses)
mais chacun avec 1 ou 2 machines connectées, au maximum.
1. Qui a déjà mis en oeuvre ce type de
Très intéressant !
Je n'y a avais pas pensé du tout !
Dans mon labo, le serveur DHCP fait office de routeur mais sur
l'implémentation cible, il est possible que ce rôle soit confié à une
machine tierce.
Dans les 2 cas, il faudra savoir configurer en masse les réseaux et
les relais DHCP.
Le ven
On Friday 11 March 2022 12:48:54 Olivier wrote:
> Je souhaite mettre en place sur une machine Bullseye, un service DHCP
> traitant 250 réseaux locaux de petite taille (/28 soit 16 adresses)
> mais chacun avec 1 ou 2 machines connectées, au maximum.
> 1. Qui a déjà mis en oeuvre ce t
Le 11/03/2022 à 12:48, Olivier a écrit :
Bonjour,
Je souhaite mettre en place sur une machine Bullseye, un service DHCP
traitant 250 réseaux locaux de petite taille (/28 soit 16 adresses)
mais chacun avec 1 ou 2 machines connectées, au maximum.
1. Qui a déjà mis en oeuvre ce type de chose
Bonjour,
Je souhaite mettre en place sur une machine Bullseye, un service DHCP
traitant 250 réseaux locaux de petite taille (/28 soit 16 adresses)
mais chacun avec 1 ou 2 machines connectées, au maximum.
1. Qui a déjà mis en oeuvre ce type de chose ? Avec quels composants ?
Quel retour
On 2/17/22, Tim Woodall wrote:
>>> It's on my todo list, along with ntp, to move to something else...
>>
>> I've seen references to chrony and ntpsec as replacements.
>
> ntpsec is supposed to be an almost drop in replacement.
If I'm interpreting the popcon pages right,
ntpsec 228 users
On Wed, 16 Feb 2022, Lee wrote:
On 2/12/22, Tim Woodall wrote:
On Wed, 9 Feb 2022, Lee wrote:
Any idea what the chances are of getting an enhancement request for
the dhcp client to add an
ignore option;
that says not use the option given by the dhcp server?
isc-dhcp-client? zero.
https
On 2/12/22, Tim Woodall wrote:
> On Wed, 9 Feb 2022, Lee wrote:
>
>> Any idea what the chances are of getting an enhancement request for
>> the dhcp client to add an
>> ignore option;
>> that says not use the option given by the dhcp server?
>>
> isc-dhc
On Wed, 9 Feb 2022, Lee wrote:
Any idea what the chances are of getting an enhancement request for
the dhcp client to add an
ignore option;
that says not use the option given by the dhcp server?
isc-dhcp-client? zero.
https://www.isc.org/dhcp/
The client and relay portions of ISC DHCP
On Wed, Feb 09, 2022 at 11:00:14AM -0500, Lee wrote:
> *sigh* naturally I picked the "move it somewhere else" option that
> won't prevent an upgrade from re-creating the file.
Missing config files will not be reinstalled, unless you call dpkg
with the "--force-confmiss" option. You should be
On Wed, Feb 09, 2022 at 10:49:34AM -0500, Lee wrote:
> >> My first thought was telling the machine to ignore the NTP server
> >> address handed out via DHCP. Maybe there's a way to do that, but I
> >> couldn't figure out how :(
> >
> > supercede ntp-s
On Wed, Feb 09, 2022 at 11:00:14AM -0500, Lee wrote:
> Any idea what the chances are of getting an enhancement request for
> the dhcp client to add an
> ignore option;
> that says not use the option given by the dhcp server?
apt install dhcpcd5
It can do this, it is call
2:53 spot systemd[1]: Stopping Network Time Service...
>> > Feb 6 12:22:53 spot systemd[1]: Stopped Network Time Service.
>> > Feb 6 12:22:53 spot systemd[1]: Starting Network Time Service...
>> > Feb 6 12:22:53 spot systemd[1]: Started Network Time Service.
>
systemd[1]: Starting Network Time Service...
>> Feb 6 12:22:53 spot systemd[1]: Started Network Time Service.
>> ... etc
>>
>> every time I connect or disconnect from a wifi network.
>
> Or it could mean that dhclient hook merely asks systemd to restart ntpd
> servi
Network Time Service.
> > Feb 6 12:22:53 spot systemd[1]: Starting Network Time Service...
> > Feb 6 12:22:53 spot systemd[1]: Started Network Time Service.
> > ... etc
> >
> > every time I connect or disconnect from a wifi network.
>
> Or it could mean that dhcl
On Wed, 9 Feb 2022 09:05:51 -0500
Lee wrote:
> 2nd thought was telling the DHCP server to not hand out an NTP server
> address to this one machine, but that's another damnifi know how to.
If you are running isc-dhcp-server, look for "option ntp-servers" in
/etc/dhcp/dhcpd.co
e Service.
> ... etc
>
> every time I connect or disconnect from a wifi network.
Or it could mean that dhclient hook merely asks systemd to restart ntpd
service. See /etc/dhcp/dhclient-exit-hooks.d/ntp.
> My first thought was telling the machine to ignore the NTP server
> address handed
15@1.3728-o Wed Sep 23 11:46:38 UTC 2020 (1): Starting
ntpd[43320]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -c
/run/ntp.conf.dhcp -u 117:124
/run/ntp.conf.dhcp starts off with
# This file was copied from /etc/ntp.conf with the server options changed
# to reflect the informatio
ime synchronization or NTP.
> I tried changing /etc/dhcp/dhclient.conf to request just
> request subnet-mask, broadcast-address, routers,
> interface-mtu,
> rfc3442-classless-static-routes ;
>
> and systemd still restarted ntpd with only the dhcp
service running on the PC :(
I tried changing /etc/dhcp/dhclient.conf to request just
request subnet-mask, broadcast-address, routers,
interface-mtu,
rfc3442-classless-static-routes ;
and systemd still restarted ntpd with only the dhcp supplied ntp
server address ... which
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/
"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
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?
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
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 provide the search list. So the
questions
ixed virtual-ethernet MAC address
> in Debian and still have the system use DHCP for IPv4 network configuration?
In message <https://lists.debian.org/debian-user/2021/12/msg00607.html>,
Dan Ritter replied:
> OpenBSD's VM infrastructure owns the virtual hardware.
>
> vm "tux&quo
).
Quand j'installe un serveur ISC-DHCP sur la machine hébergeant firewalld,
la configuration ci-après semble suffisante pour que des clients (connectés
par l'interface ens9) récupèrent une adresse.
# firewall-cmd --info-zone=internal
internal (active)
target: default
icmp-block-inversion
Jonathan Thornburg wrote:
> I have a virtual machine (VM) running Debian 10.10.0 ("Buster") x86-64,
> running in an OpenBSD 7.0 host (using the OpenBSD 'vmm' VM monitor).
...
> So, my question is, how can I set a fixed virtual-ethernet MAC address
> in Debian and still ha
iface lo inet loopback
# The primary network interface
allow-hotplug enp0s2
iface enp0s2 inet dhcp
This works fine: the VM has a (virtual) network interface enp0s2 whose
IP address is assigned by the host via DHCP. (The host OpenBSD vmm provides
a DHCP server for this purpose, and t
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
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
&
Hi,
I want to move my DHCP servers to my datacenter as I am going to shut down the
hypervisor hosts on some locations.
If I just move the VM running the isc-dhcp-server software to the DC and change
the ip of the VM then I get a warning when I try to start the dhcp software
Dec 8 16:12:12
decl-names on;
host dragonw
{
hardware ethernet ee:ee:ee:ee:ee:ee;
fixed-address iii.iii.ii.i;
}
}
However, at least three cases since I made that change, dhcp has used
another name, which I guess is the name requested by the host.
What am I missing?
--
Does anybody read signatures any mo
Bonjour,
Je souhaite mettre en place un serveur sous Bullseye, "auto-configurable
faisant office de double passerelle réseau vers Internet".
Par auto-configurable, j'entends ici que:
1.les 2 interfaces WAN se configurent pas DHCP,
2. je veux éviter d'avoir à scripter le client DH
Hi,
I've got a USB device which is known by the system as a cdc-ncm adapter.
The USB device should assign a specified IP for the adapter however it
fails to receive an IP. The system is a Debian Buster 10.3 amd64.
The USB device was also connected to a Raspberry Pi with Raspbian Stretch
and I
On Thu, 4 Feb 2021 22:16:12 +0100
basti wrote:
> As I can see now timedatectl seems *not*
> using the NTP Server provide by DHCP. I have configure a NTP server
> in LAN.
Are you using NetworkManager? Out of the box, it does not pick up the
relevant information from the dh
Hi Dan / list,
>> I am running multiple isc-dhcp servers on Debian Linux.
>> I have several sites with multiple networks and I use the isc-dhcp-server to
>> hand out ip numbers in the various network segments. In most of the networks
>> I have more then enough free
1 - 100 of 4989 matches
Mail list logo
