Testing clatd with documentation address space fails

[hax404]

Hi,

I am maintaining the packages clatd and tayga for NixOS. I wrote the test https://github.com/NixOS/nixpkgs/blob/master/nixos/tests/clatd.nix, where I use IP addresses from the documentation space. Since the last fork of tayga, more restrictive checks for IP spaces were implemented, which broke this test.

I am not sure which is the right way to fix this. I see these solutions:

1. Ask you to add a setting to pass the configuration option wkpf-strict no to tayga,
2. ask you to add a setting to generally pass configuration options to tayga, or
3. change the used IP space in the NixOS test to some global used where an external entity maybe feels addressed.

What would you recommend?

[toreanderson]

Hi, option 3 is of course the easiest for me… 😁

Have you considered using generating a ULA prefix (RFC 4193) for your tests? That seems like the easiest solution to me.

That said, I wouldn't be opposed to adding a setting that would pass through arbitrary configuration options to the generated TAYGA config file either (option 2). (I'd rather have that than option 1 at least.)