On 24/07/13 19:16, Uwe Schindler wrote:
Hi,
RA's are not the same as DHCP, there's no such thing as a lease
time. What there is, is preferred and valid lifetimes. What should
happen is that when old address is about to go away, the address
for that prefix on the network adaptor
Hi again,
In addition, I found a relic from the time when the RA_INTERVAL value was
hardcoded into radv.c. There is still one:
Line 294:
put_opt6_long(1800); /* lifetime - twice RA retransmit */
Should be:
put_opt6_long(RA_INTERVAL * 2); /* lifetime - twice RA retransmit
On 25/07/13 11:59, Uwe Schindler wrote:
Hi again,
In addition, I found a relic from the time when the RA_INTERVAL value
was hardcoded into radv.c. There is still one:
Line 294: put_opt6_long(1800); /* lifetime - twice RA retransmit */
Should be: put_opt6_long(RA_INTERVAL * 2); /* lifetime -
On 25/07/13 12:36, Uwe Schindler wrote:
Hi again,
one addition, because its too hot here... The reality is again
different (very complicated with IPv6):
Hot there too? Reply at the end.
On 24/07/13 19:16, Uwe Schindler wrote:
Hi,
RA's are not the same as DHCP, there's no such thing as
We'd like to force all DNS entries to point to a fixed IP address. We
have tried a number of things...
address=//123.123.123.123
address=/./123.123.123.123
address=/*/123.123.123.123
... is there an easy way to do this or is this not allowed?
Thank you
Dan
Hi,
On 24/07/13 19:16, Uwe Schindler wrote:
Hi,
RA's are not the same as DHCP, there's no such thing as a lease
time. What there is, is preferred and valid lifetimes. What
should happen is that when old address is about to go away, the
address for that prefix on the network adaptor
Hi,
On 25/07/13 11:59, Uwe Schindler wrote:
Hi again,
In addition, I found a relic from the time when the RA_INTERVAL value
was hardcoded into radv.c. There is still one:
Line 294: put_opt6_long(1800); /* lifetime - twice RA retransmit */
Should be: put_opt6_long(RA_INTERVAL *
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 disables
enable-tftp for that interface, but it is sometimes desirable to
allow DNS and TFTP on an interface
Hi,
reading https://datatracker.ietf.org/doc/rfc6204/?include_text=1, the
requirements for home routers are listed here:
L-13: If the delegated prefix changes, i.e., the current prefix is
replaced with a new prefix without any overlapping time
period, then the IPv6 CE
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 disables
enable-tftp for that interface, but it is
I am implementing a public API in libvirt as part of my GSoC project, for
which I need to parse the dnsmasq/network-name.leases file.
I would like to know the maximum length that an entry can have in the
leases file.
Thanking You,
Nehal J. Wani
UG3, BTech CS+MS(CL)
IIIT-Hyderabad
11 matches
Mail list logo
