WAN can ping 8.8.8.8 LAN can ping WAN and WANs gateway but cant ping 8.8.8.8
-
What are all those other networks?
So none of those work? Why and the F do you have so many freaking /16s - do you have like a billion freaking VMs on this host? ;)
Where did your image go?
edit:
Why would you scratch out rfc1918? Do you have something on your lan side that overlaps your wan?So sniff on wan while your trying to ping 8.8.8.8 from a client behind pfsense.. And validate you are natting to your wan.. And that the traffic leaves pfsense.
-
Just some other things that are setup. ignore those. But the wierd thing, is. The wan has a gateway it gets from DHCP. I can ping that ip from the LAN, but i dont get further.
-
It gets a public IP thats in the 128...... so not used by my LAN, and from the Ping tool in Pfsense i can ping from WAN to internett. So if Pfsense can reach internett, and all the VMS on my ESXI Vswitch is getting dhcp from my PFsense, i dont see how it can be a ESXI problem if the PFsense can reatch the internett.(Pfsense is VM in ESXI). But i might be thinking slighly wrong, im new to this....
At this point, we don't know if it's an ESXi issue, which is why it needs to be double checked.
Post the routing table from PFsense.
Post the routing table from a client PC
-
@nicolay1995 said in WAN can ping 8.8.8.8 LAN can ping WAN and WANs gateway but cant ping 8.8.8.8:
I can ping that ip from the LAN, but i dont get further.
And what is that exactly?
What I suggest you do is sniff on the wan while your pinging that IP from client behind pfsense.. Do you see this ping go out, was the IP changed to your public pfsense wan IP?
-
I did ask him to ping 8.8.8.8 so he's probably referring to that.
https://doc.pfsense.org/index.php/Connectivity_Troubleshooting
-
That is fine - but he says he can ping is wan gateway - what IP is that, what device is it.
Here is the thing out of the box pfsense nats any lan side networks (that do not have gateways set on them) to your wan IP... As you can see in your outbound nat section.
So if you say pfsense can ping your gateway, and your clients behind can ping pfsense gateway... Then its not pfsense problem.
Please do a sniff on pfsense wan while you ping your gateway... For all we know you have some static route sending 8.8.8.8 out some other gateway... Lets see your route table, etc.
-
We don't even know if he has properly defined his vswitches, and then properly configured his pfSense VM to have WAN and LAN NICs on the appropriate switch.
-
I change some ESxi V switch settings and now i am able to ping from LAN gateway to the internett.
But for some reason i still dont have network access. from my VM.... which has 172.30.0.1 as its gateway.
-
So, if all we get are high-level details, then all we can offer is high-level troubleshooting. Without more details, all we can tell you is check your networking... i.e. start at layer 1 and work your way up the stack. The fact that PFsense is virtualized just adds a layer of complexity that also needs to be investigated, so you will need to look at your vSwitch/vKernel configs as well as verifying that your VM's are configured for the correct port group, etc.
-
Yeah when you run pfsense on vm it adds a whole new layer of complexity..
It works just fine.. did did for years on multiple platforms.. But the problem we/I have here on the forums is lack of information.. It might take 14 posts to even find out pfsense is on vm vs hardware for example.
We are all here to help you.. But its frustration as F!!! not having the full picture.. Here is the thing I have been installing and using pfsense for 10 some years.. It just WORKS!!! you actually have to try to break it..
Every single thread comes down to this - lack of info given to what makes their setup different.. Because out of the box it just going to work.. So you have somthing you did or something unique in your environment that is causing you grief.. Pfsense on vm works on pretty much all platforms that I have played with out of the box - but there are some things you might have to do.. This is why you should RTFM!!! Lets stress that again RTFM!!!! for your specific deployment on a different vm platform..
Out of the box there is like click the bouncing ball in 2 minutes your up and running.... What I see over the 10 some years I have been here is user after user after user shooting themselves in the foot!!! Installed X package, installed Y package out of the gate before they even validate it works.. Sorry but proxy, IPS, even the most popular pfblocker packages are all next level skill sets.. And yes you can shoot yourself in the foot..
Please validate it works out of the box before you install XYZ, please up front let us know your on VM platform ABC... I have run pfsense on multiple VM platforms over the years and all work fine - but what I find is users are freaking STUPID!!! No offense here - but its what I have seen over the years.. No you can not have the same network on both your wan and lan..
Here to help - but without info can not do that.. Don't take this as directed at you, but the user base at large ;)
-
I figuret it out in the end, it was a Virtuel Switch issue in ESXI. Thank for help all.
-
I was right!
Where's my $100?
-
So for the next guy was the specific thing you did or didn't do.. Not set 4095 for vlan id of vswitch so it passes vlan tags? What?
-
I set on accept for Promiscuous mode, mac address changes and forget tramits on WAN vswitch,
Since my network goes Virtuel WAn switch-pfsense-virtuel LAN switch.
Also very important to note that is a reboot of whole esxi is necessary for it to acctually implement the changes made.I didnt discover this at beginning.... so alot of my testing was flawed cause changed wasent acutally being made...
Thanks for all help.
