Using a GRE Tunnel to route VMs network and IP to external network.
-
Also, traceroutes only give * * * * back:
-
@xuap said in Using a GRE Tunnel to route VMs network and IP to external network.:
But is it normal the ping state is 0:0 on both ends?
Yes. icmpv4 doesn't have a state.
You should still have 1:1 NAT rules on the remote pfSense. With that you wouldn't need the outbound NAT rule, the 1:1 does that already.
And you need the 1:1 rule if you want inbound connections the VM to work. Or add port forwards for each connection you need but 1:1 does it all.Steve
-
@stephenw10 So, I can remove the NAT Rules and set NAT as automatic because 1:1 Mapping does all those rules already?
Also, I want to use inbound connections too, for that, I do need that rule mentioned above, or what should I do?
-
Yes, if you have the 1:1 NAT rule in place it NAT's all traffic inbound and outbound between those IPs, 1:1.
So you can remove/disable the outbound NAT rule. No harm in leaving it in hybrid mode though.For inbound traffic you still need firewall rules to allow that on the remote side WAN. And they re applied after NAT so the destination will be the internal private IPs of the VMs.
-
@stephenw10 I putted NAT in auto mode
and in the WAN rules I have this
you were referring to those rules I just created right?
I can ping any IP address, but I can't ping any URL
I have the nameservers 8.8.8.8 and 8.8.4.4 on the VM
-
It looks like you have something that's only passing ICMP then.
Look for any state to 8.8.8.8 when you try to ping by FQDN. You should see the DNS traffic from the VM opening states on all 4 interfaces.
Steve
-
-
What firewall rules do you have on the remote GRE interface?
-
This ones
-
@xuap It is now solved, it was the Firewall that had an option to block IPV6, and some rules were not properly configured. Thanks for all the help Steve! :D
-
Cool. Yeah you'd need a rule to pass traffic from 192.168.2.X to any on that interface. Not just v4 ICMP as shown in that screenshot.
Steve
