Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    [Solved] Problems with pfSense and the LAN side

    Scheduled Pinned Locked Moved
    General pfSense Questions
    pfsense lan ping traceroute esxi
    3
    5
    2.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      resal1510
      last edited by resal1510

      Hi,

      I'm in trouble with my new pfSense installation. I'd never done that before and this didn't work, i don't know why.
      I have a ESXI installed on a Poweredge server. In this ESXI, i have some Debian 9 VM's, and the pfSense one.

      One vSwitch for the WAN (WAN side of the pfSense and the esxi mgmnt, liked to a physical network interface), and one other vSwitch, only for LAN side (No physical interface, only VM's and pfSense connected to it)

      So, my pfSense can ping 8.8.8.8, 1.1.1.1, google.com, retrieve updates ect..., the WAN side works

      But on the LAN side, my Debian VM (networking configured by the DHCP Server of pfSense), doesn't work.

      I can't ping 8.8.8.8, 1.1.1.1 or google.com, can't ping my pfSense (10.10.10.1), BUT i can access to the web interface of it.

      I'm currently studying computer science, and I'm discovering ESXI, pfSense, the network ect ..
      So, do you have some ideas for that ? I don't know why my LAN side can't go out to the internet and ping the pfSense.

      here's some complementary informations :

      LAN Network :
      Subnet : 10.10.10.0 /24
      Gateway (pfSense): 10.10.10.1
      mask: 255.255.255.0
      DHCP Range : 10.10.10.11 - 10.10.10.50

      pfSense :
      i haven't touched any rules for now, there still have default firewall rules
      Version 2.4.3-RELEASE-p1 (amd64)

      See attached images for more info
      0_1527601713688_Screenshot_23.png
      0_1527601819094_Screenshot_24.png
      0_1527601845223_Screenshot_25.png
      0_1527601885046_Screenshot_26.png
      0_1527602021484_Screenshot_27.png
      0_1527602028049_Screenshot_28.png

      1 Reply Last reply Reply Quote 0
      • NogBadTheBadN
        NogBadTheBad
        last edited by NogBadTheBad

        Your second firewall rule LAN net -> WAN net, change WAN net to any.

        Andy

        1 x Netgate SG-4860 - 3 x Linksys LGS308P - 1 x Aruba InstantOn AP22

        1 Reply Last reply Reply Quote 1
        • R
          resal1510
          last edited by

          I tried this and it work's now, my bad, i think i changed this rule inadvertently
          So, all the trafic was going to the wrong place

          Thank's a lot :)

          1 Reply Last reply Reply Quote 0
          • A
            AndyC
            last edited by

            Are you sure you want to have the management network on WAN? (Anyone can access your ESXi login page)

            R 1 Reply Last reply Reply Quote 0
            • R
              resal1510 @AndyC
              last edited by

              @andyc Yeah, i want to have access to my ESXi management from work and at home. (only for a while, as I am preparing everything for my VM ect ..)

              i will make a IP restriction or something like that if it's possible, to allow only my home public IP and the work IP

              Or i can just do a VPN with my pfSense (i saw come options to do this), i don't know, i'll think about it

              1 Reply Last reply Reply Quote 0
              • First post
                Last post