Does anyone have managed to connect these two devices(or similar) via WireGuard in Site-2-Site mode?
Please, share step by step instructions, because I’m desperate. We have a lot of clients with RUTs, but I cannot establish the connection. One time I was able to establish a connection, but it worked only one way, so I could ping all FritzBox LAN-devices from RUT’s network. But then I accidentally deleted this configuration in RUT and I cannot recall it.
Thank you!
Edited:
I have added more detailed description for my configuration:
It needs to be mentioned that I can ping my FritzBox by its DNS-name from the CLI interface of the RUT956.
And yes, I have already asked AVM for help, but they have no any wish to explore this problem and they pointed me to this forum. I hope this community is more helpful.
Thank you!
The user @wharbauer has recently had issues with WireGuard and FritzBox as well, and has made a short example in the comments section of how everything should be set up. You can find the thread here: TRB140 and Static Route with WireGuard VPN
The configuration shouldn’t be any different when using a RUT956 for this.
If this is not something you’re looking for, could you please provide a topology of your desired configuration?
No worries at all, I see you’ve edited your thread to add some images, thank you for that, however, you didn’t post any configuration images of your RUT956 WireGuard configuration, could you do that as well?
Ensure that you’re also blurring out any sensitive information before posting the configuration.
Thank you very much MatasR for your help! I have applied your corrections to my settings, but it didn’t help. I’m quite sure that the problem lies in the FritzBox area, so I decided to start all over again. Could you review these settings, so we could move over?
I hope I have understood your corrections about FritzBox’s Wireguard settings.
I’m aware that you must not be an expert in AVM devices. I just hope that you are!
I’ve sent you a form to fill out so we can continue our conversation in private, to avoid accidentally leaking any sensitive information. In the Ticket ID field, simply enter the thread’s number, which is 14089.