Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - chucklessduck

#1
Here are my configs for the other stuff in the guide. Wireguard is working and I have tested it.

#2
Ok, so I was following the selective routing guide for Wireguard. I have followed every step but for some reason, I get odd network login errors when the VPN is enabled. I have put all of the info in the attachments. This issue is really pulling my hair out any help would be great.

The Guide: https://docs.opnsense.org/manual/how-tos/wireguard-selective-routing.html

I did a traceroute on my ISP modems address and my wireguard address and both came back. But when I do the trace on google I get nothing.

#3
Virtual private networks / Help!
August 09, 2022, 02:33:08 AM
Why is this doing this? This is a default install. No firewalls or NATs except for the default ones. When I go to add the Wireguard service my web pages do not load. But the moment I turn the service off they work again.


https://imgur.com/bgWcAHj
https://imgur.com/qce1DNo

#4
General Discussion / Odd Error
July 31, 2022, 09:07:53 PM
Has anyone ever seen this error? Trying to set up a VPN. I have tried a bunch of guides but they all lead to this same error.

#5
Ok, so I have been following this guide. https://docs.opnsense.org/manual/how-tos/wireguard-selective-routing.html

I have almost everything working.
Wireguard is connected and working
I have two computers set up and I am trying to only send one of them through the Wireguard tunnel. At the moment the one computer is getting internet. The other computer that is routed through the Wireguard tunnel is not getting internet. I keep getting a page that says "the network you are using may require you to visit its login page." I have no idea what this means. I have attached the firewall rules and nat rules.

I am new with this so any help would be great.

Edit: I am definitely leaning towards the odd RFC1918_Networks config is the issue but I have no idea.