smasq.
A simple patch to add a long form configuration option "-max-procs="
to dnsmasq that allows MAX_PROCS to be overridden at runtime fixed the
user's problem.
Not sure if this is the best way of dealing with the problem, but wanted to
bring this to the list's attention.
jtu.edu.cn
192.168.100.75 a host LOEA-VM004.ic.sjtu.edu.cn 192.168.100.31 a host
LOEA-VM002.ic.sjtu.edu.cn 192.168.100.201 DHCP 202.120.2.101 upstream DNS
202.112.26.34 upstream DNS
I use "dig" on LOEA-VM004 to see if I can get LOEA-VM002 resolved via dns,
but there is no answer:
[ian@LOE
Hi Everyone,
I can't thank you enough for the work on DNSMASQ, it's an utterly brilliant
piece of software. I'm amazed at the flexibility it gives me in securing my
home network, thank you all who put in so much effort.
Gushing aside, I'm stuck on one config I can't figure out though, so I
wonder
query encrypted. I'm just l;earning all
this stuff.
Thank you for the pointers though, and again, apologies for such a tardy
reply,
Ian
On Tue, 8 Mar 2022 at 16:51, Petr Menšík wrote:
> Hi Ian,
>
> I think you can do this by turning off resolv.conf parsing (--no-resolv)
> an
d still be of interest because perhaps we expect a
(known) address to be allocated, but is failing due to different DUID
types or something (and you would want to know about that).
So, it would be really nice to be able to optionally quieten these
messages (with quiet-dhcp6 would be simplest).
ot;no addresses available" messages to be quietened.
Signed-off-by: Ian Dall
---
src/rfc3315.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/src/rfc3315.c b/src/rfc3315.c
index 400d939..a40d364 100644
--- a/src/rfc3315.c
+++ b/src/rfc3315.c
@@ -815,7 +815,11 @@ stati
ACK the typo in the comment, but what do you mean by duplicate? I'm not
sure the comment is really necessary anyway.
On Mon, 2024-03-04 at 07:13 +0100, Geert Stappers wrote:
> On Mon, Mar 04, 2024 at 03:53:23PM +1030, Ian Dall wrote:
> > When a DHCP range has a mode of "stati
I have set up a Ubuntu 10.04 LTS desktop machine with 2 interfaces (eth0
and wlan0). wlan0 acts as a wifi access point using hostapd.
dnsmasq is installed OK, and everything works so that locally on that
machine DNS works fine as normal, but connections over wlan0 get everything
routed to localhos
Please excuse my lack of networking knowledge, it's not my day job and I'm
trying to pick it up as I go.
Other threads suggest this is what the server config option is for, I was
surprised it didn't work straight away. Is this not right?
I know ip tables can be very complex to set up but know n
ons there also.
>
> On Thu, Mar 22, 2012 at 6:01 AM, Ian Rose wrote:
>
>> I have set up a Ubuntu 10.04 LTS desktop machine with 2 interfaces (eth0
>> and wlan0). wlan0 acts as a wifi access point using hostapd.
>>
>> dnsmasq is installed OK, and everything works
If it helps, the dnsmasq.conf is the standard sample one edited to use the
few options in the simple setup mentioned in this page:
https://help.ubuntu.com/community/WifiDocs/WirelessBroadcastSystem
Any ideas why the server option isn't working in dnsmasq with this setup?
Thanks,
Ian.
O
Is it possible to send a message to the client device when an IP address is
allocated via DHCP? This would only be a static info message for my
purposes, and it wouldn't matter much if some clients didn't support
showing it and so ignored it.
Apparently Apple Wi-Fi routers do this, but I'm not sur
Support question: For the company I work for, they have all their local
testing domains start with local.* instead of ending with *.dev. Is there a
way to configure all domains that START with local. use the same IP
(127.0.0.1)?
___
Dnsmasq-discuss mailin
handled by 0 .
I'd like Dnsmasq to not forward requests for any records to the
upstream DNS servers for hosts it knows about via DHCP. It seems to be
the case already for hosts in /etc/hosts:
$ host server
server.example.com has address 192.168.0.10
Ian
On Feb 23, 2009, at 11:03 PM, Ian Scott wrote:
I'd like Dnsmasq to not forward requests for any records to the
upstream DNS servers for hosts it knows about via DHCP. It seems to
be the case already for hosts in /etc/hosts:
$ host server
server.example.com has address 192.168.0.10
Oo
but and MX records get forwarded. I
think they shouldn't be. Is this expected behavior?
Ian
16 matches
Mail list logo
