Re: [Dnsmasq-discuss] 1 IP for all requests
On Thu, Oct 03, 2019 at 06:01:17PM -0500, Carl Karsten wrote: > On Thu, Oct 3, 2019 at 4:54 PM Geert Stappers wrote: > > On Thu, Oct 03, 2019 at 03:52:35PM -0500, Carl Karsten wrote: > > > I want to know if this is in spec, or needs out of spec hacks: > > > > > > For any dhcp client request, server gives the same IP. > > > > > > The use case: dnsmasq is serving on 1 interface, and a client will be > > > directly connected to that interface - no hub/switch/vlan etc. So there > > > can > > > only be 1 device ever connected, and I want that device to have 10.1.2.3 > > > - even if I yank it and plug in a 2nd device with a different mac etc. > > > The device should get 10.1.2.3. > > > > > > Even if the previous lease has not expired.which is where I suspect > > > this gets sketchy. But maybe the spec has a prevision for this. > > > > > > > Quoting manual page of dnsmasq > > > > > > --dhcp-range=[tag:[,tag:],][set:,][,|][,[,]][, > time>] > > > > > > > I want to know if this is in spec, or needs out of spec hacks: > > > > Please let us, the mailinglist archive, know if > > > > dhcp-range=10.1.2.3,10.1.2.3,255.255.255.248 > > > > serves the request. > > What I don't know is how the lease comes into play > when the 2nd machine comes on line. Become main stakeholder of the request. Regards Geert Stappers Still learning how to ignore semi good questions ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] 1 IP for all requests
On Thu, Oct 3, 2019 at 4:54 PM Geert Stappers wrote: > On Thu, Oct 03, 2019 at 03:52:35PM -0500, Carl Karsten wrote: > > I want to know if this is in spec, or needs out of spec hacks: > > > > For any dhcp client request, server gives the same IP. > > > > The use case: dnsmasq is serving on 1 interface, and a client will be > > directly connected to that interface - no hub/switch/vlan etc. So there > can > > only be 1 device ever connected, and I want that device to have 10.1.2.3 > - > > even if I yank it and plug in a 2nd device with a different mac etc. > > The device should get 10.1.2.3. > > > > Even if the previous lease has not expired.which is where I suspect > > this gets sketchy. But maybe the spec has a prevision for this. > > > > Quoting manual page of dnsmasq > > > --dhcp-range=[tag:[,tag:],][set:,][,|][,[,cast>]][,] > > > > I want to know if this is in spec, or needs out of spec hacks: > > Please let us, the mailinglist archive, know if > > dhcp-range=10.1.2.3,10.1.2.3,255.255.255.248 > > serves the request. > > > That is half of this. What I don't know is how the lease comes into play when the 2nd machine comes on line. to be clear, the first machine will have its network cable unplugged, so no chance of it telling the server releasing the lease: DHCPRELEASE - Client to server relinquishing network address and cancelling remaining lease. (really it is not the rj45 but the power cord being pulled. yes, this is a hostel environment and who knows what will really happen.) I suspect if i want this I need to have both clients use the same client ID. But I am hoping there is a server side option to achieve the same thing. (the goal is for all the networking config to be done server side, no tweaking client config.) > > Groeten > Geert Stappers > -- > Leven en laten leven > > ___ > Dnsmasq-discuss mailing list > Dnsmasq-discuss@lists.thekelleys.org.uk > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss > -- Carl K ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] 1 IP for all requests
On Thu, Oct 03, 2019 at 03:52:35PM -0500, Carl Karsten wrote: > I want to know if this is in spec, or needs out of spec hacks: > > For any dhcp client request, server gives the same IP. > > The use case: dnsmasq is serving on 1 interface, and a client will be > directly connected to that interface - no hub/switch/vlan etc. So there can > only be 1 device ever connected, and I want that device to have 10.1.2.3 - > even if I yank it and plug in a 2nd device with a different mac etc. > The device should get 10.1.2.3. > > Even if the previous lease has not expired.which is where I suspect > this gets sketchy. But maybe the spec has a prevision for this. > Quoting manual page of dnsmasq --dhcp-range=[tag:[,tag:],][set:,][,|][,[,]][,] > I want to know if this is in spec, or needs out of spec hacks: Please let us, the mailinglist archive, know if dhcp-range=10.1.2.3,10.1.2.3,255.255.255.248 serves the request. Groeten Geert Stappers -- Leven en laten leven ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] 1 IP for all requests
I want to know if this is in spec, or needs out of spec hacks: For any dhcp client request, server gives the same IP. The use case: dnsmasq is serving on 1 interface, and a client will be directly connected to that interface - no hub/switch/vlan etc. So there can only be 1 device ever connected, and I want that device to have 10.1.2.3 - even if I yank it and plug in a 2nd device with a different mac etc. The device should get 10.1.2.3. Even if the previous lease has not expired.which is where I suspect this gets sketchy. But maybe the spec has a prevision for this. -- Carl K ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] upstream dns referral?
On 10/3/2019 7:15 PM, bjh wrote: > Hi, > > I have a dnsmasq installation, running on a dedicated raspberry pi, that > has served me well for almost exactly one year now, until midday > yesterday when it apparently stopped referring queries to upstream DNS > servers. I have been relying on this dnsmasq setup to do dhcp and dns > for my home lan of about 20 clients since Oct 2018. As I said, it has > worked flawlessly until yesterday. I have of course done restarts and > power cycles to the pi and dnsmasq service but to no avail. > > DHCP and local DNS queries still seem to work on this dnsmasq installation. > > I haven't made any changes to my network or this pi lately, so I am > rather mystified as to what has caused dnsmasq to behave differently all > of a sudden. As a workaround, I have had to go to important client > machines on my lan and set them up with OPENDNS DNS addresses so they > can continue to function while I fix this. > > As a complete dnsmasq newbie, I set the dnsmasq up in Oct 2018, with the > help of an internet article that I can no longer find. It recommended > leaving /etc/dnsmasq.conf alone and putting all site specific config > data into /etc/dnsmasq.d/home.dns. This is what I did, see attached. > File /etc/dnsmasq.conf remains unchanged from how the installer program > left it, with most if not all features commented out. > > The /etc/dnsmasq.d/home.dns file is pretty simple but it doesn't > explicitly set up any referrals to upstream dns servers. > > Quite frankly, I never really understood how dnsmasq knew where to send > queries it couldn't resolve by itself. It was working, till now, though, > so I went on to other things and forgot about it. > > My question now is this: > > What do I need to add to home.dns to explicitly tell dnsmasq the ip > addresses of upstream DNS server(s) and authorize it to refer locally > unresolvable queries to it/them? > > Other thoughts or observations germane to this mystery would also be of > interest. > On the Dnsmasq server what gives the following command: $ host google.com To answer your question: You will need to use the 'server' directive', something like: server= Is there all there is in your home.dns file? If so, I would suggest you to get rid of it and start fresh by modifying '/etc/dnsmasq.conf'. My guess is that Dnsmasq is not the issue here,, but the file '/etc/resolv.conf' is not properly populated. -- John Doe ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] [PATCH] Add dhcp-ignore-clid configuration option
On Mon, Sep 16, 2019 at 11:09:30PM +0100, Simon Kelley wrote: > On 16/09/2019 08:03, Florent Fourcot wrote: > > On 20/06/2019 10:26, Florent Fourcot wrote: > >> The idea of this option was already discussed years ago on the mailing > >> list: > >> https://dnsmasq-discuss.thekelleys.org.narkive.com/ZoFQNaGo/always-ignore-client-identifier#post4 > >> > >> > >> In our production environnement, we discovered that some devices are > >> using 'client identifier' not unique at all, resulting on IP addresses > >> conflicts between several devices (we saw up to four devices using same > >> IP address). > >> > >> The root cause is probably a buggy operating system/configuration of > >> decices, but this patch add a configuration workaround on server side > >> when fixing clients is impossible. > >> > >> Signed-off-by: Charles Daymand > >> Signed-off-by: Florent Fourcot > >> --- > > Hello Simon, > > > > Could you have a look on this patch? Please let me know if something is > > missing, I'm ready to work on a v2. > > Apologies for ignoring you. The principle is a good one, but it's worth > making this conditional, so that only clients which cause a particular > tag to be set see the new behaviour. > > See, for example, --dhcp-broadcast for how it works. > > I'm happy to add that to the work you've already done. Will take me a > few days, probably. > Who is waiting on who? Or whatever takes the proposed patch forward. Groeten Geert Stappers -- Leven en laten leven ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
