Second fastd instance for backbone traffic #200
Conversation
TobleMiner
force-pushed
the
fastd-two-instances
branch
from
1ba22ca
to
bec6468
Compare
|
|
|
Please check #128 which is another atempt by @ohrensessel |
|
Didn't remember that one. I think this PR is more up time than #128. But the old one introduce other features we currently have not. Namely the cypher methods, but that should be done in another PR. Let us bring this one in. I have closed the old one. |
|
Anyone tested my changes yet? I'd like someone to approve it before merging |
rubo77
force-pushed
the
master
branch
2 times, most recently
from
70b4764
to
6d8bf60
Compare
| @@ -94,6 +104,22 @@ | |||
| ip_prefixlen => $mesh_ipv6_prefixlen; | |||
| } | |||
|
|
|||
| if $fastd_igw_enable { | |||
| Class['ffnord::ntp'] -> ffnord::fastd { "fastd_igw_${mesh_code}": | |||
There was a problem hiding this comment.
It is not entirely obvious why this should be applied after the ntp service is setup.
| @@ -66,6 +75,7 @@ | |||
| } -> | |||
| ffnord::fastd { "fastd_${mesh_code}": | |||
| mesh_code => $mesh_code, | |||
| batman_code => $mesh_code, | |||
There was a problem hiding this comment.
Why do we need an extra parameter batman_code, when it is the same as mesh_code, in all applied situations?
No description provided.