Wireguard with IPFire not having a public IP Adress

Virtual Private Networks WireGuard
1

Hi there
I updated my IPFire and wanted to try the Wireguard feature.
I created a host-to-net configuration file and used it on a mobile computer.
I does not work and in Wireguard windows app, the log says “handshake for peer did not complete after 5 seconds”

As my IPFire has a ref IP address 192.168.1.x, I made some search and I saw this could be the problem.
My IPFire does not have a public IP address.

Is there a workaround ? (apart of changing ISP :slight_smile: )

Thank you
Patrice

2

Hallo @patj07

Welcome to the IPFire community.

That suggests that you have a modem or other unit supplied by your ISP that you are connecting your IPFire to. That ISP supplied modem should have a public IP address.

If this is the case then you potentially have two options open.

  • Set the ISP supplied modem/router into bridge mode. This would then pass through the public IP to your IPFire system.
  • Set Port Forwarding in your ISP supplied modem/router to allow all ports/protocols to be forwarded to your PFire system.
1 Like
3

Welcome to the IPFire community.

Your box is behind your router? Then you need to set up port forwarding for UDP 51820 from the router to IPfire. Bridge mode would be better. If you do not have a static public address, you must use DynDNS.

4

Hello
Thank you for your answers.
I have a static IP address, but yes, it is on the router of my provider.
So, I will ask my provider to forward UDP 51820 to my IPFire and see if it get to work.then.
Thank you
Patrice

1 Like
5

If port forwarding is set up, don’t forget that the endpoint in the Wireguard setup must be the public IP, not 192…

1 Like
6

Yes :wink: of course
Thank you