Gre tunnel to protect IP.
-
Yes, because it's probably not Outbound NATing the traffic. Add a rule for that.
-
In my host's pfsense? What rule do I set?
-
Yes. Check the states at the remote side and see if traffic is leaving the WAN without NAT. If it is switch Outbound NAT to hybrid mode and add a rule to cover it.
-
These are the remote host states
@stephenw10 -
You need to start a continuous ping from 192.168.1.15 so you can see where it's opening states.
-
I ping the local machine to the remote tunnel
These are the states on remote pfsense with continuous ping on the local machine
-
You need to ping from 192.168.1.15 to something external like 8.8.8.8. Then look at the states it's generating at both ends.
-
This is how the states are with the continuous ping for 1.1.1.1. I put 1.1.1.1 because I have google dns to be used like this for a better view
-
Ok, so it's actually outbound NATing at the other end of the tunnel. You can see it appears as 10.0.2.1 rather than 192.168.1.15. So you may want to disable the NAT for the GRE interface at the client end.
You can also see it's not NATing the traffic out of the WAN at that end so you need a rule to add that there. That rule will depend on whether you disable the NAT at the client end. -
@stephenw10
Can you tell me where I can disable NAT?
For GRE tunnel only. I have the ip 192.168.1.2 with NAT for port 8006 going out through my WAN since it doesn't need protection that ip.
Thanks -
I've already disabled NAT only in the tunnel on the pfsense client and it's already here without NAT. Now it will just be creating a static route right?
-
Ok, so you need to add an Outbound NAT rule on that side for 192.168.1.0/24 on WAN.
If you have added a static route back to the main side I would expect the auto outbound rules to cover that so I assume there is not.
Steve
-
I have now bought a new ip since I don't want to use the router's ip on the machines
I configured it on the windows machine like this and created a VLAN on the pfsense client.
I'm constantly pinging from the windows machine to 1.1.1.1 and in the pfsense host states it is received like this
In the NAT part of the pfsense host I configured it like this ie the ip 185.113.141.145 is the ip wan of the pfsense host and I don't want to use it for anything else. And the ip 185.113.141.150 I want to be used in my virtual machine.
The only problem is that the machine is without internet for the ip 185.113.141.150
-
You can't use that IP directly on the client because that conflicts with the WAN subnet at the remote site.
Instead you need to add that as a VIP on the WAN at the remote site and then NAT the traffic to it.Steve
-
I already added the virtual ip.
To do the nat routing is as follows?
-
Which end is that rule on?
I expect to see the client using 192.168.1.15 and then that traffic to pass without NAT at the local pfSense. Then at the remote pfSense that IP should be NAT'd to the WAN IP or the VIP.
-
I liked to use the ip 185.113.141.150 on the windows machine is this not possible?
This rule was in remote pfsense. -
You can't use the public IP on the Windows machine directly unless it is bridged (layer 2) to the remote WAN somehow. You can't use a routed tunnel like you are now.
-
What other possibilities can I use?
-
@stephenw10 said in Gre tunnel to protect IP.:
I expect to see the client using 192.168.1.15 and then that traffic to pass without NAT at the local pfSense. Then at the remote pfSense that IP should be NAT'd to the WAN IP or the VIP.
Like I said ^.
