@scilek 2 pings a second.. That seems pretty freaking insane to me - but sure its possible, and the only thing that comes to mind that pfsense send on its own that is repetitive and constant.

There really should be pretty much zero broadcast or multicast coming off of pfsense.

@joe90

If it is assigning an address from with your prefix, then that address will start with your /56 prefix.

I don't have any experience with IPv6 on PPPoE or with OpenWRT, so I don't know what else to check.

However, you don't need a WAN GUA. If you want to access pfSense from elsewhere, you can use the LAN interface address.

Technically you could do it by running pfSense as a virtual machine in Windows using hyper-V or VBox etc. But pfSense is a complete operating system, it cannot run as an application on your desktop. It expects to be running on it's own dedicated hardware but running virtualised can also work.

Steve

@nick-loenders
Yes, this simply adds the proper route on the client to go over the VPN gateway.

Hi @chpalmer,
You were right; the problem was an incorrect gateway configuration on the webserver.

Thanks again!

@jontabaco

dont know why but the supposed fix only worked for one day and nothing ive tried has resolved my remote ip from showing

That's right, though you do have to watch that the rules on your tunnel interface have reply-to in the ruleset. For GIF/GRE, they should have it by default, but double check that to be certain. You need that because otherwise the reply packets would take your default route outbound no matter what you have set on the rules.

Also make sure you don't have any outbound NAT active on the tunnel interface.

One last note, I strongly suggest you put devices using those public addresses on their own segment like a DMZ interface. It's a bad practice to mix public and private subnet traffic on an interface for a variety of reasons. So unless LAN is dedicated to using only the public addresses, you should make another interface.