Discussion:
[Dnsmasq-discuss] DHCP server can not cope with multihomed hosts with same identifier
Arjen Lobregt
2016-03-10 09:32:11 UTC
Permalink
LS,

We are using DNSMASQ in our system.
This systems contains several networks with very specific functions/traffic types (divided in both VLANs and subnets and all networks have subdomain names).

A number of network nodes are connected to several networks and VLANs (e.g. machine control, logging, external connection). This includes our DHCP server running DNSMASQ.
These network nodes normally use DHCP (and a UUID) to obtain an IP address.
Unfortunately DNSMASQ receives these DHCP requests, checks for the identifier, but disregards the interface the DHCP request was received on and also the VLAN tag and only lists the last received request in the lease file and DNS.

So where the node does receive a DHCP offer for each request, we can not contact the node on each interface, because there is no DNS entry for each IP address that was issued by DNSMASQ.


Is there a way DNSMASQ is able to support multihomed hosts or is this a fundamental ommission in DNSMASQ?
And if this is a true ommission, can this support be added?


Kind regards,

Arjen Lobregt

-- The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. Unless explicitly stated otherwise in the body of this communication or the attachment thereto (if any), the information is provided on an AS-IS basis without any express or implied warranties or liabilities. To the extent you are relying on this information, you are doing so at your own risk. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. The sender nor the company/group of companies he or she represents shall be liable for the proper and complete transmission of the information contained in this communication, or for any delay in its receipt.
Jim Alles
2016-03-10 11:22:07 UTC
Permalink
I have encountered a similar issue in a different use-case.

It is simpler network in a BYOD environment on a farm. The router has three
interfaces; WAN, office Wi-Fi, guest Wi-Fi. The two Wi-Fi segments are
segregated by a firewall. The office Wi-Fi has a very small physical
footprint with one Access Point (AP), but has some private resources. The
guest Wi-Fi has four APs with internet access only.

If I do static DHCP assignment for privileged devices that may roam to
either network, things get sticky.

Peace, Jim Alles out.
Post by Arjen Lobregt
LS,
We are using DNSMASQ in our system.
This systems contains several networks with very specific
functions/traffic types (divided in both VLANs and subnets and all networks
have subdomain names).
A number of network nodes are connected to several networks and VLANs
(e.g. machine control, logging, external connection). This includes our
DHCP server running DNSMASQ.
These network nodes normally use DHCP (and a UUID) to obtain an IP address.
Unfortunately DNSMASQ receives these DHCP requests, checks for the
identifier, but disregards the interface the DHCP request was received on
and also the VLAN tag and only lists the last received request in the lease
file and DNS.
So where the node does receive a DHCP offer for each request, we can not
contact the node on each interface, because there is no DNS entry for each
IP address that was issued by DNSMASQ.
Is there a way DNSMASQ is able to support multihomed hosts or is this a
fundamental ommission in DNSMASQ?
And if this is a true ommission, can this support be added?
Kind regards,
Arjen Lobregt
-- The information contained in this communication and any attachments is
confidential and may be privileged, and is for the sole use of the intended
recipient(s). Any unauthorized review, use, disclosure or distribution is
prohibited. Unless explicitly stated otherwise in the body of this
communication or the attachment thereto (if any), the information is
provided on an AS-IS basis without any express or implied warranties or
liabilities. To the extent you are relying on this information, you are
doing so at your own risk. If you are not the intended recipient, please
notify the sender immediately by replying to this message and destroy all
copies of this message and any attachments. The sender nor the
company/group of companies he or she represents shall be liable for the
proper and complete transmission of the information contained in this
communication, or for any delay in its receipt.
_______________________________________________
Dnsmasq-discuss mailing list
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Loading...