On 26/07/13 22:19, Uwe Schindler wrote:
Hi,
After some testing and reconnecting PPP connection several times: All
works fine. It also recognizes multiple old prefixes and sends all of
them as deprecated.
Regarding the Android-Bug: I found out that I still have to enable
the fast mode (which is
On 24/07/13 16:04, Roy Marples wrote:
On 24/07/2013 14:29, Simon Kelley wrote:
I think this should happen already: for IPv4 calls to do_options have
the domain argument which is set to the result of get_domain(address)
which will be domain-suffix unless there's a more specific example.
This
Hi,
I send in my config:
dhcp-option=option6:information-refresh-time,1h
Otherwise, Windows Clients never try to renew information from DHCPv6 (it looks
like that to me, in reality its 86400 secs, which is the default if not
specified). http://www.6net.org/publications/standards/rfc4242.txt
Hi,
Regarding the Android-Bug: I found out that I still have to enable
the fast mode (which is only done in the first minute after a
config change). The reason is: Although the prefix has a lifetime of
86400 on my dhcp-range, in contrast, the router itself gets a
lifetime of 1800
Hi,
I found the reason for this bug:
One small thing with your new code - maybe a bug, because the comment
says something else: Although the configured (in my config) valid_lifetime of
the prefix is now lower
(30 mins on my machine), after deprecation it raises the valid_lifetime again
up
On 27/07/13 19:11, Uwe Schindler wrote:
In my opinion, dnsmasq should by default (like for stateful IPv4
leases) use the lifetime specified in the dhcp-range to request the
clients to refresh this information. If it is explicitely given, of
course use the information from
On Jul 25, 2013, at 4:44 PM, Lonnie Abelbeck wrote:
On Jul 25, 2013, at 4:06 PM, Simon Kelley wrote:
On 23/06/13 20:34, Lonnie Abelbeck wrote:
Hi,
I'd like to suggest that enable-tftp and no-dhcp-interface should be
decoupled.
Not only is it confusing that no-dhcp-interface also
