Can not reach the internet from the pfsense itself
-
Hello,
I am used to install pfsense, and i ma using a provider which allocate Ipv4 failover addresses (basically a /32)
The default gateway is not on the same subnet. Thats said, it work perfectly great by adding a way to reach the default gateway onto the config.xml
With lastest version 2.4.4 i do have the following problem: the firewall can not reach the internet (even though it is reachable from the internet): so no way to check update or autoinstall module.
When i try to ping for example 8.8.8.8 i have a timeout.
After I investigate furthermore when I do add ping -S my_public_source_IP 8.8.8.8 it is working perfectly and i do have a reply.
Default route has been set to the good interface (vmx0 in my case) and i do not have any problem with my network behind the firewall, my VM are able to reach the internet without any problem.
The problem really is from the firewall itself.
My version is :
2.4.4-RELEASE-p1 (amd64)
netstat -rn
Routing tablesInternet:
Destination Gateway Flags Netif Expire
default 62.210.0.1 UGS vmx0
62.210.0.1/32 00:50:56:01:8e:3c US vmx0
127.0.0.1 link#4 UH lo0
192.168.1.0/24 link#2 U vmx1
192.168.1.1 link#2 UHS lo0
192.168.2.0/24 link#7 U vmx1.10
192.168.2.1 link#7 UHS lo0
my-ip link#1 UHS lo0
my-ip/32 link#1 U vmx0Internet6:
Destination Gateway Flags Netif Expire
::1 link#4 UH lo0
fe80::%vmx0/64 link#1 U vmx0
fe80::250:56ff:fe01:8e3c%vmx0 link#1 UHS lo0
fe80::%vmx1/64 link#2 U vmx1
fe80::1:1%vmx1 link#2 UHS lo0
fe80::%lo0/64 link#4 U lo0
fe80::1%lo0 link#4 UHS lo0
fe80::%vmx1.10/64 link#7 U vmx1.10
fe80::20c:29ff:fe54:f6a2%vmx1.10 link#7 UHS lo0
fe80::%vmx0.20/64 link#8 U vmx0.20
fe80::250:56ff:fe01:8e3c%vmx0.20 link#8 UHS lo0any idea about what is wrong and how i can correct that. I searched for a few hours and i have no clue where the problem really is.
Regards
-
So you had to manually edit the config to add that gateway? You could not just check 'Use non-local gateway' in the gateway settings?
I assume this is all static?
Steve
-
Hello,
yes I edited manually by adding that to an <earlyshellcmd>
Anyway, now i created a new gateway via WebUI , i checked the box to say that gateway is not part of the wan network, deleted my earlyshellcmd, rebooted and yes now it is working.
I was used to put all my initial route and the way to reach the gateway onto the earlyshellcmd as i was not aware of this options, maybe this option is quite new.
Anyway before version 2.2 it was working find and never had this problem.
but pb is solved now. thanks.
Regards
