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

    I can ping PFSense but PFSense can't ping back

    Scheduled Pinned Locked Moved General pfSense Questions
    42 Posts 7 Posters 11.8k 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.
    • -
      -striker- 0
      last edited by

      The client is assigned its IP through a static DHCP mapping from pfsense so I don't think it is a wrong network mask. Additionally, pfsense cannot ping any LAN client, i'm just focusing on this one as this is the one I care about pfsense being able to port forward to.

      There are two dumb switches between pfsense and the client in question. They have both been rebooted several times to clear anything they might be retaining internally.

      There are no vlans setup in my environment.

      K 1 Reply Last reply Reply Quote 0
      • K
        Konstanti @-striker- 0
        last edited by

        @striker-0
        try check " Disable hardware checksum offloading" in System/Advanced/Networking

        - 1 Reply Last reply Reply Quote 0
        • -
          -striker- 0 @Konstanti
          last edited by

          @konstanti I gave that a try, Thank You for the suggest! Rebooted pfsense to ensure it was applied. Same results on a ping test.

          K 1 Reply Last reply Reply Quote 0
          • K
            Konstanti @-striker- 0
            last edited by Konstanti

            @striker-0
            Show the output of the command
            ifconfig -m
            and arp -a

            - 1 Reply Last reply Reply Quote 0
            • -
              -striker- 0 @Konstanti
              last edited by

              @konstanti The forums are being weird and telling me that the content is flagged as spam. I've attached the requested results as a text file.0_1548526770045_Results.txt

              K 1 Reply Last reply Reply Quote 0
              • K
                Konstanti @-striker- 0
                last edited by Konstanti

                @striker-0
                So in a whole, all looks decently
                What you can try

                1. Change the LAN - re0 interface speed (e.g. media 100baseTX mediaopt full-duplex)
                2. Check the lan re0 - switch cable
                3. Connect any device directly to PFSense and try to ping .
                4. check the subnet mask in dhcp server settings and devices that have permanent ip addresses (255.255.255.0)
                - 1 Reply Last reply Reply Quote 0
                • chpalmerC
                  chpalmer
                  last edited by chpalmer

                  Client firewalls? If you changed anything such as your LAN subnet your desktops will change to "public" and block everything.

                  Even changing an interface on your router could trigger that.

                  https://www.netgate.com/docs/pfsense/nat/port-forward-troubleshooting.html

                  As you eluded to in your first post- once you figure out why your port forward does not work you will most likely also fix the ping.

                  Triggering snowflakes one by one..
                  Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

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

                    If you can ping one way and not the other it is almost certainly a firewall on the device you cannot ping blocking it. One way ping success proves two-way traffic, routing (for the most part in most cases), and layer 2 are correct.

                    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
                    • -
                      -striker- 0 @Konstanti
                      last edited by

                      @konstanti

                      1. I would prefer not to change my link speed. It is currently running at 1000. If I switch it down to 10 or 100, I would be limiting my access to my internet as my internet connection is currently rated for 300. Additionally, this was working previously under the current link state, so I would be surprised if this would resolve anything. What is your rationale for checking this?

                      2. Tried a different cable, no change in results.

                      3. Tried connecting a device directly to pfsense. No change in results.

                      4. Subnet Mask is set to 255.255.255.0 in DHCP and aligns with the client.

                      K 1 Reply Last reply Reply Quote 0
                      • -
                        -striker- 0 @chpalmer
                        last edited by

                        @chpalmer I thought it could be client side firewall too. I normally leave those disabled on my internal LAN as they just cause unnecessary trouble. I have confirmed and they are still off.

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

                          Then you'll have to packet capture to see the pings going out and nothing coming back, look at the MAC addresses, etc.

                          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
                          • K
                            Konstanti @-striker- 0
                            last edited by Konstanti

                            @striker-0
                            Reducing the connection speed is just a test
                            I am very confused by the line in ping test
                            255.255.255.0 > 10.0.100.51: ICMP echo request, id 16367, seq 0, length 64
                            ( I don't know what's the subnet mask )

                            Should be so

                            length 98: 192.168.1.1 > 192.168.1.230: ICMP echo request, id 30542, seq 0, length 64
                            length 98: 192.168.1.230 > 192.168.1.1: ICMP echo reply, id 30542, seq 0, length 64
                            length 98: 192.168.1.1 > 192.168.1.230: ICMP echo request, id 30542, seq 1, length 64
                            length 98: 192.168.1.230 > 192.168.1.1: ICMP echo reply, id 30542, seq 1, length 64

                            Can you put the packet capture file here ?

                            1 Reply Last reply Reply Quote 0
                            • -
                              -striker- 0 @Derelict
                              last edited by

                              @derelict I have confirmed the firewall is off. This issue occurs across all devices on my network, the only constant is pfsense. Additionally, within my network other devices can ping each other and I can connect to the port I am trying to forward. Something is going on with pfsense or the hardware it resides on.

                              K DerelictD 2 Replies Last reply Reply Quote 0
                              • K
                                Konstanti @-striker- 0
                                last edited by

                                @striker-0
                                And another question - how much do you have active NORDVPN tunnels ?
                                if you turn them off, will anything change ?

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

                                  @striker-0 said in I can ping PFSense but PFSense can't ping back:

                                  255.255.255.0 > 10.0.100.51:

                                  That is NOT right it sould be pinging from pfsense IP on that 10.0.100 network..

                                  re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
                                  	options=82098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
                                  	capabilities=18399b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_UCAST,WOL_MCAST,WOL_MAGIC,LINKSTATE,NETMAP>
                                  	ether 00:11:09:d7:2b:fa
                                  	hwaddr 00:11:09:d7:2b:fa
                                  	inet6 fe80::211:9ff:fed7:2bfa%re0 prefixlen 64 scopeid 0x2
                                  	inet 10.0.100.1 netmask 0xffffff00 broadcast 10.0.100.255
                                  	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
                                  	media: Ethernet autoselect (1000baseT <full-duplex,master>)
                                  	status: active
                                  

                                  That is the IP it should be pinging from 10.0.100.1

                                  An intelligent man is sometimes forced to be drunk to spend time with his fools
                                  If you get confused: Listen to the Music Play
                                  Please don't Chat/PM me for help, unless mod related
                                  SG-4860 24.11 | Lab VMs 2.8, 24.11

                                  K 1 Reply Last reply Reply Quote 0
                                  • DerelictD
                                    Derelict LAYER 8 Netgate @-striker- 0
                                    last edited by

                                    @striker-0 Post a packet capture taken on each interface of pings that work and pings that fail.

                                    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
                                    • -
                                      -striker- 0 @Konstanti
                                      last edited by

                                      @konstanti at the moment, my NORDVPN tunnel is down. I see no difference in activity when the tunnel is up or down.

                                      1 Reply Last reply Reply Quote 0
                                      • K
                                        Konstanti @johnpoz
                                        last edited by Konstanti

                                        @johnpoz
                                        All this is very strange, because of the webgui
                                        pfsense is also forming a command
                                        / sbin/ping -S 10.0.100.1 -c 3 10.0.100.51 (as seen in the picture)
                                        and tcpdump shows another

                                        1 Reply Last reply Reply Quote 0
                                        • -
                                          -striker- 0 @Derelict
                                          last edited by

                                          @derelict Here is a packet capture from pfsense where I tried to ping 10.0.100.51 on the LAN interface and it failed.

                                          12:47:22.869939 00:11:09:d7:2b:fa > 00:22:15:9f:4b:51, ethertype IPv4 (0x0800), length 98: (tos 0x0, ttl 64, id 14477, offset 0, flags [none], proto ICMP (1), length 84)
                                          255.255.255.0 > 10.0.100.51: ICMP echo request, id 49230, seq 0, length 64
                                          12:47:23.875326 00:11:09:d7:2b:fa > 00:22:15:9f:4b:51, ethertype IPv4 (0x0800), length 98: (tos 0x0, ttl 64, id 41292, offset 0, flags [none], proto ICMP (1), length 84)
                                          255.255.255.0 > 10.0.100.51: ICMP echo request, id 49230, seq 1, length 64
                                          12:47:24.877890 00:11:09:d7:2b:fa > 00:22:15:9f:4b:51, ethertype IPv4 (0x0800), length 98: (tos 0x0, ttl 64, id 38991, offset 0, flags [none], proto ICMP (1), length 84)
                                          255.255.255.0 > 10.0.100.51: ICMP echo request, id 49230, seq 2, length 64

                                          pfsense packet capture doesn't seem to capture any packets when I ping from my workstation to the server even with the use of promiscuous mode. Any suggestions on a tool to capture the information you are looking for?

                                          K 1 Reply Last reply Reply Quote 0
                                          • K
                                            Konstanti @-striker- 0
                                            last edited by Konstanti

                                            @striker-0
                                            0_1548615129595_f1b4a77b-657e-4585-ae4a-450e95d008d0-image.png

                                            Need a file that you download after clicking " Download capture"

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