Navigation

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

    Unable to ping clients from pfsense but assigning dhcp

    Routing and Multi WAN
    2
    3
    465
    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.
    • T
      thomas159 last edited by

      Hi,

      I have been trying to add a new interface to our existing pfsense setup but I am unable to ping clients from this interface via pfsense however it is assigning a dhcp address to clients

      I setup a laptop attached to the same switch as WLAN is plugged into and it was assigned a 172.16.1.10 dhcp address and I can ping the pfsense box on 172.16.1.1 and 172.16.1.2 however I am unable to ping the laptop on 172.16.1.10 from pfsense WLAN interface. I can ping clients on 192.168.2.x range from WLAN and WLAN_VIP

      Simplified Setup:
      1 server 2012 with dhcp
      1 pfsense
      2 LAN
      1 WAN

      WAN int1 x.x.x.x going to pfsense
      LAN int2 192.168.2.2 going from pfsense to core switch
      WLAN int3 172.16.1.2 going from pfsense seperate switch

      LAN_VIP 192.168.2.1
      WLAN_VIP 172.16.1.1

      DHCP Relay setup on both LAN interfaces and both are assigning DHCP addresses as expected

      WAN int1 rules

      • RFC 1918 networks * * * * * Block private networks
      • Reserved/not assigned by IANA * * * * * * Block bogon networks

      LAN int2 rules

      IPv4 * * 192.168.0.0/16 * WAN

      WLAN int3 rules

      IPv4 * * * * * * none

      1 Reply Last reply Reply Quote 0
      • johnpoz
        johnpoz LAYER 8 Global Moderator last edited by

        why do you have gateway setup on lan?

        I would look to software firewall rule on laptop if you can not ping it, but it can ping pfsense .

        1 Reply Last reply Reply Quote 0
        • T
          thomas159 last edited by

          nailed it..only had firewall blocking public networks so our internal 192.2 was working fine..doh!

          Thanks!!

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

          Products

          • Platform Overview
          • TNSR
          • pfSense
          • Appliances

          Services

          • Training
          • Professional Services

          Support

          • Subscription Plans
          • Contact Support
          • Product Lifecycle
          • Documentation

          News

          • Media Coverage
          • Press
          • Events

          Resources

          • Blog
          • FAQ
          • Find a Partner
          • Resource Library
          • Security Information

          Company

          • About Us
          • Careers
          • Partners
          • Contact Us
          • Legal
          Our Mission

          We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

          Subscribe to our Newsletter

          Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

          © 2021 Rubicon Communications, LLC | Privacy Policy