On 12/10/13 10:48, Vladislav Grishenko wrote:
Hi, Simon,
Thanks for the implementation, works well with one issue is still there
RDNSS DNS Search List RA options contain lifetimes calculated from
MaxRtrAdvInterval, where MaxRtrAdvInterval =ra-interval, and
MinRtrAdvInterval = 3/4*ra-interval
The problem with that is that RDNSS and DNSSL are per interface, not per-
prefix. Maybe the calculation should the maximum valid time of any prefix
advertised on the interface?
It will not work for several different prefixes and serveral different
global-scope addresses on dnsmasq interface.
On 14/10/13 12:03, Vladislav Grishenko wrote:
The problem with that is that RDNSS and DNSSL are per interface, not per-
prefix. Maybe the calculation should the maximum valid time of any prefix
advertised on the interface?
It will not work for several different prefixes and serveral different
On 11/10/13 16:37, Rick Jones wrote:
On 10/11/2013 07:16 AM, Simon Kelley wrote:
On 11/10/13 01:39, Rick Jones wrote:
I am still on the steep learning slope for dnsmasq. The manpage lists a
-l/--dhcp-leasefile option into which dnsmasq will store lease
information. I gather though that it will
I am having a weird problem with dnsmasq. I'm using version 2.65 that comes
with Fedora.
I have added a CNAME for www to a domain, in DNS.
Several hours later:
- dig @8.8.8.8 www.example.com gives me the CNAME as expected
- dnsmasq, which uses 8.8.8.8 as it's dns server replies nxdomain
Could you share with me (off-list) the actual domain that showing this
behaviour, so I can try and reproduce it?
Cheers,
Simon.
On 14/10/13 18:32, Yves Dorfsman wrote:
I am having a weird problem with dnsmasq. I'm using version 2.65 that
comes with Fedora.
I have added a CNAME for www
Simon repllied off the list.
The CNAME was point to an non-existing domain (typo in DNS).
On 2013-10-14 11:32, Yves Dorfsman wrote:
I am having a weird problem with dnsmasq. I'm using version 2.65 that comes
with Fedora.
I have added a CNAME for www to a domain, in DNS.
Several hours later:
Hello, I am a relatively new user of dnsmasq, on a debian system, part of
the Untangle UTM suite.
I was wondering if I could have an explanation of the form:
dhcp-range=interface:ethN,192.168.1.100, 192.168.1.200
Is 'interface' in this case a special form of tag:, and where is it set:?
I have
On Mon, Oct 14, 2013 at 9:42 AM, Simon Kelley si...@thekelleys.org.uk wrote:
On 11/10/13 16:37, Rick Jones wrote:
On 10/11/2013 07:16 AM, Simon Kelley wrote:
On 11/10/13 01:39, Rick Jones wrote:
I am still on the steep learning slope for dnsmasq. The manpage lists a
-l/--dhcp-leasefile
You forgot to cc the list.
Network interfaces are not tags that can be manipulated with tag:/set:/net:
Network interface names are matched with interface:
If you have ethernet and wireless network interface cards on your computer,
they are probably named `eth0` and `wlan0` (although `ath0` is
Where is this interface: syntax you're mentioning, anyway.
The only thing I see is that you dnsmasq automatically creates a tag for
you using the name of the network interface (that name being controlled by
udev). This is documented:
The tag system works as follows: For each DHCP request,
BTW this message was wrong.
Use tag:interfacenamehere to match against the name of a network interface.
So tag:eth0 or tag:wlan0
I don't know where the dhcp-range=interface:ethN,192.168.1.100,
192.168.1.200 came from.
On Mon, Oct 14, 2013 at 5:19 PM, richardvo...@gmail.com
On Mon, Oct 14, 2013 at 6:48 PM, richardvo...@gmail.com
richardvo...@gmail.com wrote:
Use tag:interfacenamehere to match against the name of a network
interface. So tag:eth0 or tag:wlan0
I don't know where the dhcp-range=interface:ethN,192.168.1.100,
192.168.1.200 came from.
It is
13 matches
Mail list logo
