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

    Can't ping 'GUEST' interface on pfsense route.

    Scheduled Pinned Locked Moved General pfSense Questions
    6 Posts 2 Posters 558 Views
    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.
    • G
      gurvindernarula
      last edited by

      Hello all,

      I've run into a wierd issue with my setup. I have a pfsense 2.4.2 setup on a Super Micro C2758. I have it configured to route most my LAN network through a VPN (newshosting.com) and all's working fine at that end.

      As the board has 2 spare nics, I decided to setup a 'guest' network connecting a AP to one of the spare ports. I like to take things step by step so I decided to first setup the new interface just like a standard LAN network -
          1. 'Assigned' a new network called GUEST to igb3 nic with static IP (192.168.25.1).
          2. TSetup DHCP using the console - 'Set interface(s) IP Address' option (for some reason the Web Configurator did not give me an option to configure DHCP on this new interface).

      I have not configured any rules etc on this new interface and I've also confirmed that neither 'Block private networks and loopback addresses' nor 'Block bogon networks' are set.

      Now here's the problem - when I connect a laptop directly to the 'GUEST' interface, the laptop get's a IP address on the 192.168.25.X network and the gateway is properly assigned (192.168.25.1).  But for some reason, I just can't ping the gateway address. When I connect the same laptop the 'LAN' interface, it pings just fine.

      I've tried re-booting the router and the laptop, but that did not help.

      Can someone please help me understand what I'm doing wrong  ??? - I think it's a very basic setup (other than the pfsense router being setup as a VPN client) which I hoped would work without much fuss. :-\

      Thanks in advance.
      Gurvinder

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        1. 'Assigned' a new network called GUEST to igb3 nic with static IP (192.168.25.1).

        (for some reason the Web Configurator did not give me an option to configure DHCP on this new interface)

        Check the netmask on the interface itself. You probably want /24 there.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • G
          gurvindernarula
          last edited by

          Thanks Derelict,

          That fixed the DHCP issue  :) - yes I can now configure DHCP using the WebConfigurator. But I still can't ping from a laptop connected to this interface / nic.

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            I have not configured any rules etc on this new interface.

            If there are no rules, the interface will not accept any traffic. Not even ping.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 0
            • G
              gurvindernarula
              last edited by

              Ok - just configured GUEST with a pass for Source:any/any Destination:any/any and gateway:any rule on the GUEST interface - still no dice.

              What should I check for next ?

              1 Reply Last reply Reply Quote 0
              • DerelictD
                Derelict LAYER 8 Netgate
                last edited by

                Post your rules. Be sure it isn't TCP-only.

                https://doc.pfsense.org/index.php/Connectivity_Troubleshooting

                Chattanooga, Tennessee, USA
                A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                Do Not Chat For Help! NO_WAN_EGRESS(TM)

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.