No outbound internet connection Hyper-V
-
Hi,
I'm running pfsense 2.2 in a VM on Hyper-V. Connected to 2 virtual switches (WAN & LAN). The problem i'm having is that there is no internet connection from the LAN side to the WAN side. I can however connect from the WAN to a website located on the LAN. The problem is, I think, a routing issue. Since my knowledge of routers/firewalls is very basic I kinda need some help with troubleshooting.
Please note that my IP address has a gateway that is outside of the subnet. Let me explain this a bit further. I own a server of soyoustart (part of OVH), they are a large company where you can rent dedicated servers. To fix the problem of pfsense not allowing a gateway outside of the IP subnet you have to run the following commands:
Lets assume the IP address on my dedicated server (NOT the failover) is 1.2.3.4. In this section i needed to change the last octet to 254. so it would be 1.2.3.254
So i would type in this…
route add -net 1.2.3.254/32 -iface em0
<hit enter="">route add default 1.2.3.254</hit>source: http://forum.ovh.co.uk/showthread.php?6507-ESXi-pfSense-and-failover-IP
This always used to work with pfSense 2.1.X.
Can anybody help me out?
ps. I can ping from the pfSense console to the internet
-
Update:
Ok. So after editing all the nessecery ip adresses I restored a (working) 2.1.5 config file to the new 2.2 box. I now have an internet connection with all my VM's. When I look at the system->routing section there is a default gateway rule (yay ;D). The only thing im getting right now is alot of "calcru: Runtime went backwards from XXX usec to XXX usec for PID 0 (kernel)" in the pfSense console.
So getting it to work with a config file from a previous version of pfSense means there is something broken in 2.2?
EDIT: for the people that are having the same issue with the calcru error: I changed the NTP server on pfSense to the one where my host (Server 2012 R2) is on. In my case time.windows.com
-
Because of the restore pfSense stops working after about 10 minutes…. so thats a no go. Anyone got another idea?
-
So your restore works but stops after 10 minutes? You state it's because of the restore that it stops, why do you think it's related?
Which part works, LAN to WAN connectivity as expected or?
When it stops are you still able to ping an Internet side resource, ie: 8.8.8.8?
-
Hi,
I'm running pfsense 2.2 in a VM on Hyper-V. Connected to 2 virtual switches (WAN & LAN). The problem i'm having is that there is no internet connection from the LAN side to the WAN side. I can however connect from the WAN to a website located on the LAN. The problem is, I think, a routing issue. Since my knowledge of routers/firewalls is very basic I kinda need some help with troubleshooting.
Please note that my IP address has a gateway that is outside of the subnet. Let me explain this a bit further. I own a server of soyoustart (part of OVH), they are a large company where you can rent dedicated servers. To fix the problem of pfsense not allowing a gateway outside of the IP subnet you have to run the following commands:
Lets assume the IP address on my dedicated server (NOT the failover) is 1.2.3.4. In this section i needed to change the last octet to 254. so it would be 1.2.3.254
So i would type in this…
route add -net 1.2.3.254/32 -iface em0
<hit enter="">route add default 1.2.3.254</hit>source: http://forum.ovh.co.uk/showthread.php?6507-ESXi-pfSense-and-failover-IP
This always used to work with pfSense 2.1.X.
Can anybody help me out?
ps. I can ping from the pfSense console to the internet
Did you add your Gateway in the web interface for the WAN details?
I'm also testing 2.2 on Hyper-V at OVH (I've been running 2.0.3 successfully for over a year) and had the same problem. I found that even though you're running the script to add the route etc it also needs the gateway adding in the interface, even though it doesn't work!
My 2.2 has been running at OVH for a couple of days now (testing only) and has no problem passing traffic with this configuration. I do still have the calcru error, but I always had that with 2.0.3 too and it never caused an issue.