WiFi clients can't ping WAN, but pfsense can!


  • https://docs.google.com/presentation/d/1tkv4f54K9KuRVhPLdwBzgcaeBpYM4kzgtFTgbtkMA_w/edit?usp=sharing

    I went to WAN/LAN and enabled * access for any (to test WAN connection before I build it back up) .. I pretty much have no firewall, and still can't browse/ping WAN. What's up with this?

    Using PPPoE DSL

  • LAYER 8 Netgate

    I have no idea how you expect that network to function.  It's like a rubegoldberg.net.

  • LAYER 8 Global Moderator

    So you have gateway set on pfsense lan?  Why do users always do this??  And even if you thought you need it why would you set it to the AP ip??  WTF???  Clearly don't grasp what a gateway even is..



  • Sorry, couldn't resist…

    I'm sure there is a way to simplify your network configuration.  Start with the basic devices, get them working and then build up.



  • @johnpoz:

    So you have gateway set on pfsense lan?  Why do users always do this??  And even if you thought you need it why would you set it to the AP ip??  WTF???  Clearly don't grasp what a gateway even is..

    ?? It's showing the Windows 7 server's IP address from the physical card. Clearly you don't grasp that the NIC is physically connected to the windows server beside it (even a fancy windows logo above the server) – But that's OK, np -- if you look BELOW, you'll see the bridge with the IP's there. No gateway:


  • @KOM:

    Sorry, couldn't resist…

    I'm sure there is a way to simplify your network configuration.  Start with the basic devices, get them working and then build up.

    How much more simple could it be with 1 router, 1 wifi access point, and a server?

    The only reason it gets complex is because of DSL, and gets more complex because of Virtualbox instead of a real rig.

    If it was cable it'd be flip on a switch and go, but it's not. I can either do double NAT or bridge mode + PPPoE on pfsense (I know, the latter is recommended). Both methods get public IP on pfsense, and can ping out to WAN, but clients can still not ping out no matter which.

    I just need to know how to properly connect the 2 networks for WAN for the clients.. surely something to do with NAT, and another person mentioned something about proxy ARP+virtual IP. I'm a bit confused at this point (that's what I'm currently doing while waiting for responses is researching these).

    I've come a long way since my first post, but still no closer to getting clients connected to WAN, considering 1/2 the responses are trolls :P


  • I answered your other thread.

  • LAYER 8 Global Moderator

    "Clearly you don't grasp that the NIC is physically connected to the windows server beside it"

    And why would windows box be using your AP as its gateway???  If you want windows to use pfsense to get to the internet - because your AP sure and the HELL can not, then its gateway would be your lan IP of pfsense 192.168.0.1

    Dude I really suggest you do a bit of reading on basic tcp/ip.  You seem not to grasp what a gateway is, and or network segments, etc.  In some other of your multiple threads on this subject you mention your setup proxy and captive portal and that you could ping 8.8.8.8..  Are you trying to ping pfsense wan IP?

    Lets forget wifi for a second.  Put a computer on pfsense lan IP..  Can you access the webgui via pfsense lan IP?  Set your computer to dhcp.  It gets an IP from pfsense and points to pfsense as its gateway and dns.

    This is really click click up and running..  Just double nat from your isp device until such time you have the basics working.  pfsense dhcp, only requirement is that pfsense lan be different network than its wan.  Client on lan should be able to get to the internet, ping stuff on the internet, etc.. because the default rule on pfsense lan is any any.  Once you have these basics working you can move on to more complicated setups.

    Your host running virtual box does not need IP on interface that is connected to your isp device.  So go into windows and uncheck tcp/ip v4 v6 and everything else in the properties of that interface other than the bridge for virtualbox.  Then on the interface on your lan side just set its interface you have bridged to the lan interface set it to dhcp.  It will get dhcp from pfsense dhcp server, etc..

    I can draw this up with pictures if you want.