Send dhcp-users mailing list submissions to
dhcp-users@lists.isc.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
dhcp-users-requ...@lists.isc.org
You can reach the person managing the list at
dhcp-users-ow...@lists.isc.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."
Today's Topics:
1. Problem with dhcpv6 and systemd-networkd clients (Robert Senger)
2. Re: Problem with dhcpv6 and systemd-networkd clients (perl-list)
3. Re: Problem with dhcpv6 and systemd-networkd clients
(Robert Senger)
4. RE: multi vlan subnet, wrong netmask and wrong router offer
in PXE (nono monbou)
----------------------------------------------------------------------
Message: 1
Date: Tue, 07 Apr 2020 16:18:29 +0200
From: Robert Senger <robert.sen...@lists.microscopium.de>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Problem with dhcpv6 and systemd-networkd clients
Message-ID:
<56c9d3ede7a2bbecfeaa9189c59742a5f982310a.ca...@lists.microscopium.de>
Content-Type: text/plain; charset="UTF-8"
Dear all,
I just discovered a problem with two clients that use systemd-networkd
for network configuration.
Both clients, as well as the dhcp server, run Debian 10.
Both clients have their network interfaces in /etc/systemd/network
configured like this:
File /etc/systemd/network/10-eth0.network
---
[Match]
MACAddress=00:30:05:c9:38:ff
[Network]
IPv6AcceptRA=yes
DHCP=yes
[DHCP]
UseDomains=true
---
When the clients come up, or when I restart systemd-networkd on the
client, I see this in the dhcpd logs:
Apr 7 15:54:19 prokyon dhcpd[9823]: Solicit message from
fe80::230:5ff:fec9:38ff port 546, transaction ID 0xF7324300
Apr 7 15:54:19 prokyon dhcpd[9823]: Advertise NA: address
fd10:2842:f0d1:101:af31:9c41:dd6b:7d5 to client with duid
00:02:00:00:ab:11:71:bc:09:50:c1:3c:0b:51 iaid = 1232215879 static
Apr 7 15:54:19 prokyon dhcpd[9823]: Sending Advertise to
fe80::230:5ff:fec9:38ff port 546
Apr 7 15:54:19 prokyon dhcpd[9811]: DHCPREQUEST for 192.168.0.21
(192.168.0.251) from 00:30:05:c9:38:ff via eth0
Apr 7 15:54:19 prokyon dhcpd[9811]: DHCPACK on 192.168.0.21 to
00:30:05:c9:38:ff via eth0
Apr 7 15:54:20 prokyon dhcpd[9823]: Request message from
fe80::230:5ff:fec9:38ff port 546, transaction ID 0x8DF86200
Apr 7 15:54:20 prokyon dhcpd[9823]: Discarding Request from
fe80::230:5ff:fec9:38ff; not our server identifier (CLIENTID
00:02:00:00:ab:11:71:bc:09:50:c1:3c:0b:51, SERVERID
00:03:00:01:00:1d:aa:97:f0:44, server DUID
00:01:00:01:26:1f:32:19:02:a5:04:3d:96:27)
The client then assigns an address to it's eth0 interface, that is completely
wrong:
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.21 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::230:5ff:fec9:38ff prefixlen 64 scopeid 0x20<link>
inet6 fd10:2842:f0d1:101::1 prefixlen 128 scopeid 0x0<global>
inet6 2001:470:52a0:101:230:5ff:fec9:38ff prefixlen 64 scopeid
0x0<global>
ether 00:30:05:c9:38:ff txqueuelen 1000 (Ethernet)
RX packets 14402 bytes 6624577 (6.3 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 9253 bytes 1639921 (1.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17
For explanation, the address 2001:470:52a0:101:230:5ff:fec9:38ff is the
SLAAC address. The DHCPV6 address should be
fd10:2842:f0d1:101:af31:9c41:dd6b:7d5 as sent by the dchp server. But
the client assignes fd10:2842:f0d1:101::1 to its interface (the other
client fd10:2842:f0d1:101::2), addresses that I never have configured
anywhere.
Other Linux clients using NetworkManager, or Windows 10 Clients, get
configured well in that setup.
What is going wrong here? I don't know if this is a server side or a
client side problem.
What I already did: Deleted all lease files in /var/lib/dhcp and
restarted isc-dhcp-server (server side). Restarted clients. No success.
Thanks for help,
Robert
--
Robert Senger
------------------------------
Message: 2
Date: Tue, 7 Apr 2020 11:52:40 -0400 (EDT)
From: perl-list <perl-l...@network1.net>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Problem with dhcpv6 and systemd-networkd clients
Message-ID:
<1677929985.1776333.1586274760370.javamail.zim...@network1.net>
Content-Type: text/plain; charset=utf-8
This bit here:
Apr 7 15:54:20 prokyon dhcpd[9823]: Discarding Request from
fe80::230:5ff:fec9:38ff; not our server identifier (CLIENTID
00:02:00:00:ab:11:71:bc:09:50:c1:3c:0b:51, SERVERID
00:03:00:01:00:1d:aa:97:f0:44, server DUID
00:01:00:01:26:1f:32:19:02:a5:04:3d:96:27)
indicates that some other server is answering as well (or the client thinks it
is). Could that be the case? Is dhcpd configured and running elsewhere?
----- Original Message -----
> From: "Robert Senger" <robert.sen...@lists.microscopium.de>
> To: "Users of ISC DHCP" <dhcp-users@lists.isc.org>
> Sent: Tuesday, April 7, 2020 10:18:29 AM
> Subject: Problem with dhcpv6 and systemd-networkd clients
> Dear all,
> I just discovered a problem with two clients that use systemd-networkd
> for network configuration.
> Both clients, as well as the dhcp server, run Debian 10.
> Both clients have their network interfaces in /etc/systemd/network
> configured like this:
> File /etc/systemd/network/10-eth0.network
> ---
> [Match]
> MACAddress=00:30:05:c9:38:ff
> [Network]
> IPv6AcceptRA=yes
> DHCP=yes
> [DHCP]
> UseDomains=true
> ---
> When the clients come up, or when I restart systemd-networkd on the
> client, I see this in the dhcpd logs:
> Apr 7 15:54:19 prokyon dhcpd[9823]: Solicit message from
> fe80::230:5ff:fec9:38ff
> port 546, transaction ID 0xF7324300
> Apr 7 15:54:19 prokyon dhcpd[9823]: Advertise NA: address
> fd10:2842:f0d1:101:af31:9c41:dd6b:7d5 to client with duid
> 00:02:00:00:ab:11:71:bc:09:50:c1:3c:0b:51 iaid = 1232215879 static
> Apr 7 15:54:19 prokyon dhcpd[9823]: Sending Advertise to
> fe80::230:5ff:fec9:38ff
> port 546
> Apr 7 15:54:19 prokyon dhcpd[9811]: DHCPREQUEST for 192.168.0.21
> (192.168.0.251)
> from 00:30:05:c9:38:ff via eth0
> Apr 7 15:54:19 prokyon dhcpd[9811]: DHCPACK on 192.168.0.21 to
> 00:30:05:c9:38:ff
> via eth0
> Apr 7 15:54:20 prokyon dhcpd[9823]: Request message from
> fe80::230:5ff:fec9:38ff
> port 546, transaction ID 0x8DF86200
> Apr 7 15:54:20 prokyon dhcpd[9823]: Discarding Request from
> fe80::230:5ff:fec9:38ff; not our server identifier (CLIENTID
> 00:02:00:00:ab:11:71:bc:09:50:c1:3c:0b:51, SERVERID
> 00:03:00:01:00:1d:aa:97:f0:44, server DUID
> 00:01:00:01:26:1f:32:19:02:a5:04:3d:96:27)
> The client then assigns an address to it's eth0 interface, that is completely
> wrong:
> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet 192.168.0.21 netmask 255.255.255.0 broadcast 192.168.0.255
> inet6 fe80::230:5ff:fec9:38ff prefixlen 64 scopeid 0x20<link>
> inet6 fd10:2842:f0d1:101::1 prefixlen 128 scopeid 0x0<global>
> inet6 2001:470:52a0:101:230:5ff:fec9:38ff prefixlen 64 scopeid 0x0<global>
> ether 00:30:05:c9:38:ff txqueuelen 1000 (Ethernet)
> RX packets 14402 bytes 6624577 (6.3 MiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 9253 bytes 1639921 (1.5 MiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> device interrupt 17
> For explanation, the address 2001:470:52a0:101:230:5ff:fec9:38ff is the
> SLAAC address. The DHCPV6 address should be
> fd10:2842:f0d1:101:af31:9c41:dd6b:7d5 as sent by the dchp server. But
> the client assignes fd10:2842:f0d1:101::1 to its interface (the other
> client fd10:2842:f0d1:101::2), addresses that I never have configured
> anywhere.
> Other Linux clients using NetworkManager, or Windows 10 Clients, get
> configured well in that setup.
> What is going wrong here? I don't know if this is a server side or a
> client side problem.
> What I already did: Deleted all lease files in /var/lib/dhcp and
> restarted isc-dhcp-server (server side). Restarted clients. No success.
> Thanks for help,
> Robert
> --
> Robert Senger
> _______________________________________________
> dhcp-users mailing list
> dhcp-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
Message: 3
Date: Tue, 07 Apr 2020 21:12:35 +0200
From: Robert Senger <robert.sen...@lists.microscopium.de>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Problem with dhcpv6 and systemd-networkd clients
Message-ID:
<860570efa8008afc637b49ce8b2f4610a1e36770.ca...@lists.microscopium.de>
Content-Type: text/plain; charset="UTF-8"
Am Dienstag, den 07.04.2020, 11:52 -0400 schrieb perl-list:
> This bit here:
>
> Apr 7 15:54:20 prokyon dhcpd[9823]: Discarding Request from
> fe80::230:5ff:fec9:38ff; not our server identifier (CLIENTID
> 00:02:00:00:ab:11:71:bc:09:50:c1:3c:0b:51, SERVERID
> 00:03:00:01:00:1d:aa:97:f0:44, server DUID
> 00:01:00:01:26:1f:32:19:02:a5:04:3d:96:27)
>
> indicates that some other server is answering as well (or the client
> thinks it is). Could that be the case? Is dhcpd configured and
> running elsewhere?
Thanks, you got it! I was definitely sure that I never ran another
dhcp6 server in the net (although there *were* some access points
running isc-dhcp-relay in both v4 and v6 mode). I checked them all,
okay, no dhcp service running.
Then I realized that I replaced the old ADSL modem with a new VDSL
modem couple of days ago, and ... I disabled dhcpv4 on that device, but
forgot about dhcpv6 ...
Problem solved, thanks again!
Robert
> ----- Original Message -----
> > From: "Robert Senger" <robert.sen...@lists.microscopium.de>
> > To: "Users of ISC DHCP" <dhcp-users@lists.isc.org>
> > Sent: Tuesday, April 7, 2020 10:18:29 AM
> > Subject: Problem with dhcpv6 and systemd-networkd clients
> > Dear all,
> > I just discovered a problem with two clients that use systemd-
> > networkd
> > for network configuration.
> > Both clients, as well as the dhcp server, run Debian 10.
> > Both clients have their network interfaces in /etc/systemd/network
> > configured like this:
> > File /etc/systemd/network/10-eth0.network
> > ---
> > [Match]
> > MACAddress=00:30:05:c9:38:ff
> > [Network]
> > IPv6AcceptRA=yes
> > DHCP=yes
> > [DHCP]
> > UseDomains=true
> > ---
> > When the clients come up, or when I restart systemd-networkd on the
> > client, I see this in the dhcpd logs:
> > Apr 7 15:54:19 prokyon dhcpd[9823]: Solicit message from
> > fe80::230:5ff:fec9:38ff
> > port 546, transaction ID 0xF7324300
> > Apr 7 15:54:19 prokyon dhcpd[9823]: Advertise NA: address
> > fd10:2842:f0d1:101:af31:9c41:dd6b:7d5 to client with duid
> > 00:02:00:00:ab:11:71:bc:09:50:c1:3c:0b:51 iaid = 1232215879 static
> > Apr 7 15:54:19 prokyon dhcpd[9823]: Sending Advertise to
> > fe80::230:5ff:fec9:38ff
> > port 546
> > Apr 7 15:54:19 prokyon dhcpd[9811]: DHCPREQUEST for 192.168.0.21
> > (192.168.0.251)
> > from 00:30:05:c9:38:ff via eth0
> > Apr 7 15:54:19 prokyon dhcpd[9811]: DHCPACK on 192.168.0.21 to
> > 00:30:05:c9:38:ff
> > via eth0
> > Apr 7 15:54:20 prokyon dhcpd[9823]: Request message from
> > fe80::230:5ff:fec9:38ff
> > port 546, transaction ID 0x8DF86200
> > Apr 7 15:54:20 prokyon dhcpd[9823]: Discarding Request from
> > fe80::230:5ff:fec9:38ff; not our server identifier (CLIENTID
> > 00:02:00:00:ab:11:71:bc:09:50:c1:3c:0b:51, SERVERID
> > 00:03:00:01:00:1d:aa:97:f0:44, server DUID
> > 00:01:00:01:26:1f:32:19:02:a5:04:3d:96:27)
> > The client then assigns an address to it's eth0 interface, that is
> > completely
> > wrong:
> > eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> > inet 192.168.0.21 netmask 255.255.255.0 broadcast 192.168.0.255
> > inet6 fe80::230:5ff:fec9:38ff prefixlen 64 scopeid 0x20<link>
> > inet6 fd10:2842:f0d1:101::1 prefixlen 128 scopeid 0x0<global>
> > inet6 2001:470:52a0:101:230:5ff:fec9:38ff prefixlen 64 scopeid
> > 0x0<global>
> > ether 00:30:05:c9:38:ff txqueuelen 1000 (Ethernet)
> > RX packets 14402 bytes 6624577 (6.3 MiB)
> > RX errors 0 dropped 0 overruns 0 frame 0
> > TX packets 9253 bytes 1639921 (1.5 MiB)
> > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> > device interrupt 17
> > For explanation, the address 2001:470:52a0:101:230:5ff:fec9:38ff is
> > the
> > SLAAC address. The DHCPV6 address should be
> > fd10:2842:f0d1:101:af31:9c41:dd6b:7d5 as sent by the dchp server.
> > But
> > the client assignes fd10:2842:f0d1:101::1 to its interface (the
> > other
> > client fd10:2842:f0d1:101::2), addresses that I never have
> > configured
> > anywhere.
> > Other Linux clients using NetworkManager, or Windows 10 Clients,
> > get
> > configured well in that setup.
> > What is going wrong here? I don't know if this is a server side or
> > a
> > client side problem.
> > What I already did: Deleted all lease files in /var/lib/dhcp and
> > restarted isc-dhcp-server (server side). Restarted clients. No
> > success.
> > Thanks for help,
> > Robert
> > --
> > Robert Senger
> > _______________________________________________
> > dhcp-users mailing list
> > dhcp-users@lists.isc.org
> > https://lists.isc.org/mailman/listinfo/dhcp-users
> _______________________________________________
> dhcp-users mailing list
> dhcp-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
--
Robert Senger
------------------------------
Message: 4
Date: Wed, 8 Apr 2020 07:44:46 +0000
From: nono monbou <isanau...@hotmail.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: RE: multi vlan subnet, wrong netmask and wrong router offer
in PXE
Message-ID:
<pr3p194mb0954eade66a0e0b47c62aae8aa...@pr3p194mb0954.eurp194.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"
Hello,
That was the problem, hosts must be declared out of the subnet declartion.
Thank you very much ?
________________________________
De : dhcp-users <dhcp-users-boun...@lists.isc.org> de la part de Niall O'Reilly
<niall.orei...@ucd.ie>
Envoy? : mardi 7 avril 2020 12:57
? : Users of ISC DHCP <dhcp-users@lists.isc.org>
Objet : Re: multi vlan subnet, wrong netmask and wrong router offer in PXE
On 7 Apr 2020, at 10:51, nono monbou wrote:
> Could you help me ?
You should keep host declarations global: that is, not contained in any subnet
declaration. This is almost certainly the most common single piece of advice
given on this mailing list.
Best regards,
Niall O'Reilly
_______________________________________________
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20200408/819e806b/attachment.htm>
------------------------------
Subject: Digest Footer
_______________________________________________
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
End of dhcp-users Digest, Vol 138, Issue 6
******************************************
