[solved] Wireguard not working (connecting to IPv6 instead of ipv4)

Started by Onkel-tobi, June 09, 2023, 11:48:45 AM

Previous topic - Next topic
Hi,

i have the following setup:
Fritzbox => opnsense
- I have forwarded port 51820 to the opnsense
- configured wireguard via https://docs.opnsense.org/manual/how-tos/wireguard-client.html (without any ipv6 setup)

My mobile phone is connecting but it shows its connected to ipv6 address and i can't find anything in the FW logs or even in the Wireguard handshake.

Any ideas?
Thanks,
Tobi

Mobile connection without IPv4? Not uncommon these days.
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

Quote from: Onkel-tobi on June 09, 2023, 11:48:45 AM
Hi,

i have the following setup:
Fritzbox => opnsense
- I have forwarded port 51820 to the opnsense
- configured wireguard via https://docs.opnsense.org/manual/how-tos/wireguard-client.html (without any ipv6 setup)

My mobile phone is connecting but it shows its connected to ipv6 address and i can't find anything in the FW logs or even in the Wireguard handshake.

Any ideas?
Thanks,
Tobi

I had something similar recently, I had to put the ipv4 address in the config for the wire guard server, instead of the domain name which had worked up until that point.

Thanks for you answers.
Strange is that even if i put in my actual IPv4 address wireguard on my mobile tells me i am connected but i can't find anything in my logs.
What do i have configured is:
- local wireguard config (see attached)
- wg1 interface
- FW rules on WAN and wireguard interface

Andy hints?

regards,
Tobi

Update:
I found the issue in the public key (i missed some letters). That was not shown in the GUI but on the console i could see that error.

regards,
Tobias