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. Re: DHCP server configuration does not work for all clients
(Jim Yang)
2. Re: multi interfaces(vlans) configuration (Simon Hobson)
3. dhcpv6 replies vanishing (Alan Batie)
----------------------------------------------------------------------
Message: 1
Date: Fri, 9 Oct 2020 13:38:22 +0000
From: Jim Yang <z...@cornell.edu>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: DHCP server configuration does not work for all clients
Message-ID: <0cf78f09-8409-404b-bc82-7c9ded9f4...@cornell.edu>
Content-Type: text/plain; charset="utf-8"
Niall,
Thank you again for your insight, which is very helpful.
Thank you for your time.
Jim
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20201009/e626bdf9/attachment-0001.htm>
------------------------------
Message: 2
Date: Fri, 9 Oct 2020 15:16:53 +0100
From: Simon Hobson <dh...@thehobsons.co.uk>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: multi interfaces(vlans) configuration
Message-ID: <0cf99b6b-aea5-42ca-bb1e-79bae14d6...@thehobsons.co.uk>
Content-Type: text/plain; charset=us-ascii
> On 9 Oct 2020, at 07:02, sth...@nethelp.no wrote:
>
>> ISC dhcpd needs to access the raw ethernet interface, so doesn't play
>> well with vlan sub-interfaces.
>
> "Doesn't play well with vlan sub-interfaces" may be the case for Linux.
> We're running ISC dcpd with multiple VLANs on FreeBSD, and it seems to
> work just fine.
I'm pretty certain I've done it with linux in the past. Does "raw packet"
literally mean "packet from the NIC buffer", or does it mean "packet from the
OS buffer after the OS has done the VLAN stuff" ?
Without any knowledge of how it's actually done, it would seem logical to me
for the VLAN (and link aggregation/bonding) code to handle that aspect before
squirting the packet into the packet buffer ready to go into the rest of the
network stack. So tagged packet in -> tag stripped by VLAN code -> packet put
into buffer as though it had been received that way (untagged) on that
interface.
Simon
------------------------------
Message: 3
Date: Fri, 9 Oct 2020 18:02:03 -0700
From: Alan Batie <a...@peak.org>
To: dhcp-users@lists.isc.org
Subject: dhcpv6 replies vanishing
Message-ID: <b78f1d30-5ff9-c921-6ba9-d3ea93f6f...@peak.org>
Content-Type: text/plain; charset=utf-8
I'm setting up a dhcpv6 server and seeing the initial request come, and
the server replies, however the reply is not getting out on any of the
network interfaces.
tshark -V -n -i <interface> ip6 and \(port 546 or port 547\)
dhcp server (centos 7)
ens192 - Primary network for access
ens224 - one dhcp v4 vlan
ens256 - another dhcp v4 vlan + dhcpv6
Oct 9 17:57:45 dhcp01 dhcpd: Solicit message from
fe80::4a77:46ff:fef9:bc06 port 546, transaction ID 0xF021F100
Oct 9 17:57:45 dhcp01 dhcpd: Picking pool address 2607:f678:1fff:1011::1caa
Oct 9 17:57:45 dhcp01 dhcpd: Picking pool prefix 2607:f678:2fff::/60
Oct 9 17:57:45 dhcp01 dhcpd: Sending Advertise to
fe80::4a77:46ff:fef9:bc06 port 546
> 13870 select(6, [4 5], [], NULL, NULL) = 1 (in [5])
> 13870 recvmsg(5, {msg_name={sa_family=AF_INET6, sin6_port=htons(546),
> inet_pton(AF_INET6, "fe80::4a77:46ff:fef9:bc06", &sin6_addr),
> sin6_flowinfo=htonl(0), sin6_scope_id=if_nametoindex("ens256")},
> msg_namelen=28,
> msg_iov=[{iov_base="\1\361!\360\0\10\0\2\377\377\0\6\0\36\0\21\0\25\0\26\0\27\0\30\0\37\08\0@\0C"...,
> iov_len=65536}], msg_iovlen=1, msg_control=[{cmsg_len=36,
> cmsg_level=SOL_IPV6, cmsg_type=0x32}], msg_controllen=40, msg_flags=0}, 0) =
> 107
> 13870 socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 7
> 13870 ioctl(7, SIOCGIFINDEX, {ifr_name="ens256", }) = 0
> 13870 close(7) = 0
> 13870 sendto(3, "<30>Oct 9 17:39:27 dhcpd: Solic"..., 109, MSG_NOSIGNAL,
> NULL, 0) = 109
> 13870 sendto(3, "<31>Oct 9 17:39:27 dhcpd: Picki"..., 73, MSG_NOSIGNAL,
> NULL, 0) = 73
> 13870 sendto(3, "<31>Oct 9 17:39:27 dhcpd: Picki"..., 66, MSG_NOSIGNAL,
> NULL, 0) = 66
> 13870 sendto(3, "<30>Oct 9 17:39:27 dhcpd: Sendi"..., 82, MSG_NOSIGNAL,
> NULL, 0) = 82
> 13870 socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 7
> 13870 ioctl(7, SIOCGIFINDEX, {ifr_name="ens256", }) = 0
> 13870 close(7) = 0
> 13870 sendmsg(5, {msg_name={sa_family=AF_INET6, sin6_port=htons(546),
> inet_pton(AF_INET6, "fe80::4a77:46ff:fef9:bc06", &sin6_addr),
> sin6_flowinfo=htonl(0), sin6_scope_id=0}, msg_namelen=28,
> msg_iov=[{iov_base="\2\361!\360\0\3\0(\0\0\0\1\0\0\16\20\0\0\34
> \0\5\0\30&\7\366x\37\377\20\21"..., iov_len=184}], msg_iovlen=1,
> msg_control=[{cmsg_len=36, cmsg_level=SOL_IPV6, cmsg_type=0x32}],
> msg_controllen=36, msg_flags=0}, 0) = 184
> 13870 select(6, [4 5], [], NULL, NULL <detached ...>
I note the reply is going to the link local address, which makes sense
since it doesn't have anything else yet, but I'm not sure how it figures
out how to route it, and ping6 seems confused too:
ping6 fe80::4a77:46ff:fef9:bc06
connect: Invalid argument
------------------------------
Subject: Digest Footer
_______________________________________________
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
End of dhcp-users Digest, Vol 144, Issue 8
******************************************
