Configuration generated with recent versions of wgcf not working on FritzBox

[alessandromrc]

Apparently there has been a change on how the configuration is created recently and that prevents wgcf to actually create a valid configuration to use on FritzBox routers since they don't allow to have any IPv6 field.

A working configuration on FritzBox is the following one:

[Interface]
PrivateKey = Redacted
Address = 172.16.0.2/32
DNS = 1.1.1.1, 1.0.0.1
MTU = 1280

[Peer]
PublicKey = Redacted
AllowedIPs = 0.0.0.0/0
Endpoint = engage.cloudflareclient.com:2408

Meanwhile a configuration that gets generated by wgcf itself looks like this one:

[Interface]
PrivateKey = Redacted
Address = 172.16.0.2/32
Address = 2606:4700:110:8962:6cbd:39ed:b0e0:320b/128
DNS = 1.1.1.1, 1.0.0.1, 2606:4700:4700::1111, 2606:4700:4700::1001
MTU = 1280

[Peer]
PublicKey = Redacted
AllowedIPs = 0.0.0.0/0
AllowedIPs = ::/0
Endpoint = engage.cloudflareclient.com:2408

The differences are pretty clear and also the FritzBox fails in a really dumb way and just says that there is an error within the configuration without giving any verbose output.

[ViRb3]

This looks like a dupe of either #418 or #419, which one is it?

[alessandromrc]

This looks like a dupe of either #418 or #419, which one is it?

Technically it might seem like a dupe but FritzBoxes just straight up fail without giving any reason.

Maybe the best could be informing users within the README?

It's the most similar to #419 anyway.

[ViRb3]

Did you try putting both addresses on a single line, that maybe fixes it? This is released in wgcf v2.2.23.

[alessandromrc]

Did you try putting both addresses on a single line, that maybe fixes it? This is released in wgcf v2.2.23.

On such version (2.2.23) I get the same error even with the configuration with both addresses on the same line.

[ViRb3]

I see, that's unfortunate. In that case I will be closing this issue as well, as there's nothing we can do. I don't think I want to maintain a list of broken WireGuard clients on the README, people should be able to find this issue if they need.

[alessandromrc]

I guess you can pin the issue on the repository anyway ;)

https://docs.github.com/en/issues/tracking-your-work-with-issues/administering-issues/pinning-an-issue-to-your-repository

Edit:
Sent a ticket to AVM to let them investigate over this issue themselves.

[alessandromrc]

@ViRb3 AVM released a new Fritz!OS version to fix this issue.

Importing the configuration generated from wgcf should now work flawlessly.

:)