A host SHOULD select a default gateway for each prefix it uses to
obtain one of its own addresses. That router SHOULD be one of the
routers advertising the prefix in its RA. As a result of doing so,
when a host emits a datagram using a source address in one of those
prefixes and has
How do Homenet routers configure NTP? Just use the pool?
Either use the pool or use one from an SNTP DHCP option an edge router
received from an ISP and published in HNCP.
___
homenet mailing list
homenet@ietf.org
How do Homenet routers configure NTP? Just use the pool?
Either use the pool or use one from an SNTP DHCP option an edge router
received from an ISP and published in HNCP.
+1
Default (e.g., in open source implementations) should be to use the pool, in
the absence of DHCP option info.
How do Homenet routers configure NTP? Just use the pool?
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
Hi,
would be nice to have a NTP daemon on every Homenet router... gateways pull
their time from the uplink, every other router pulls time from the gateway
routers.
Henning Rogge
On Tue, Aug 18, 2015 at 2:34 PM, Juliusz Chroboczek
j...@pps.univ-paris-diderot.fr wrote:
How do Homenet routers
On Tuesday, August 18, 2015, Henning Rogge hro...@gmail.com wrote:
Hi,
would be nice to have a NTP daemon on every Homenet router... gateways
pull their time from the uplink, every other router pulls time from the
gateway routers.
Henning Rogge
On Tue, Aug 18, 2015 at 2:34 PM, Juliusz
On Aug 18, 2015, at 10:45, Juliusz Chroboczek j...@pps.univ-paris-diderot.fr
wrote:
Section 6.1 says:
A node MUST be able to detect whether two of its local internal
interfaces are connected, e.g., by detecting an identical remote
interface being part of the Common Links of both local
Section 6.1 says:
A node MUST be able to detect whether two of its local internal
interfaces are connected, e.g., by detecting an identical remote
interface being part of the Common Links of both local interfaces.
Seems like this could be improved by rephrasing it to the effect that
Over the last week, shncpd has learnt:
- to participate in DHCPv4 election;
- to announce delegated prefixes (over HNCP and the routing protocol);
- to configure the local host;
- to deal with ad-hoc and leaf interfaces.
It's not quite compliant yet, but it's getting there. The known
On Aug 18, 2015, at 06:38, Juliusz Chroboczek j...@pps.univ-paris-diderot.fr
wrote:
Section 6.1 says:
A node MUST be able to detect whether two of its local internal
interfaces are connected, e.g., by detecting an identical remote
interface being part of the Common Links of both
Am 18.08.2015 um 19:45 schrieb Juliusz Chroboczek:
That's too weak -- it also needs to take care to perform prefix assignment
only once (although it will probably want to perform address assignment on
both interfaces, especially if they're in ad-hoc mode), to run only one
instance of RA and
James:
Doesn’t section 6.3.1 already spell that out?
Set of Shared Links: […] When multiple interfaces are
detected as belonging to the same Common Link, prefix assignment
is disabled on all of these interfaces except one.
Steven:
How about adding In this case the
On Tue, 18 Aug 2015, Juliusz Chroboczek wrote:
(If you test this with Babel, you need to set reflect-kernel-metric true
What does that do?
[...]
So it takes whatever metric it came up with and sets the metric as kernel
priority?
That's right.
So if there is a shorter prefix that has a
So this is to choose between identical routes. Why is this needed?
I have no idea. You'll have to ask Pierre.
(And I'd appreciate an explanation myself.)
-- Juliusz
___
homenet mailing list
homenet@ietf.org
On Tue, 18 Aug 2015, Juliusz Chroboczek wrote:
(If you test this with Babel, you need to set reflect-kernel-metric true
in babeld's config file; Pierre tells me that this is done automatically
by hnetd. I'll make some refinements to the reflect-kernel-metric code,
and make it the default in
Section 6.1 says:
A node MUST be able to detect whether two of its local internal
interfaces are connected, e.g., by detecting an identical remote
interface being part of the Common Links of both local interfaces.
What should the node do if it detects that two interfaces are on the same
Either use the pool or use one from an SNTP DHCP option an edge router
received from an ISP and published in HNCP.
Ah, silly me. Yes, of course, we're already publishing DHCP(v6) options.
RFC 7084 recommends support for NTP option. If NTP is supported, the
router is required to request
I don't know of anything in the homenet routers that require a peering
level of synchronization. And I think it would be dangerous to suggest
it's achievable.
Well, if configured with both client-server and peer relationships, NTP
will converge to a set of disjoint lowest-dispersion trees, so
Either use the pool or use one from an SNTP DHCP option an edge
router received from an ISP and published in HNCP.
Ah, silly me. Yes, of course, we're already publishing DHCP(v6) options.
RFC 7084 recommends support for NTP option. If NTP is supported, the
router is required to
I am pleased to announce the public release of pimbd, the PIM
implementation that was demonstrated during the last Bits and Bites in
Prague.
Excellent news, Pierre, automagic site-local multicast would be a great
feature for Homenet. I'll try it out as soon as it migrates into an
OpenWRT
On Tue, Aug 18, 2015 at 3:21 PM, Juliusz Chroboczek
j...@pps.univ-paris-diderot.fr wrote:
Either use the pool or use one from an SNTP DHCP option an edge router
received from an ISP and published in HNCP.
Ah, silly me. Yes, of course, we're already publishing DHCP(v6) options.
RFC 7084
(If you test this with Babel, you need to set reflect-kernel-metric true
What does that do?
[...]
So it takes whatever metric it came up with and sets the metric as kernel
priority?
That's right.
So if there is a shorter prefix that has a lower metric, this will be
chosen over a longer
22 matches
Mail list logo
