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

    Get public ip for pcs

    Scheduled Pinned Locked Moved General pfSense Questions
    79 Posts 3 Posters 12.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.
    • S
      s_serra @stephenw10
      last edited by

      @stephenw10

      The ips that are assigned are from different subnets depending on the availability of the isp.
      the mask is /24
      Yes that was in the wan interface. But I send it again to be sure.
      Yes the 208 was that which was assigned to the server.

      13:47:46.315025 IP 79.124.62.98.8080 > 176.79.22.208.9182: tcp 0
      13:47:48.432381 IP 79.124.62.74.8080 > 176.79.22.208.7991: tcp 0
      13:47:49.522016 IP 184.105.139.73.36267 > 176.79.22.208.1900: UDP, length 97
      13:47:52.030703 IP 124.236.24.85.47070 > 176.79.22.208.6379: tcp 0
      13:47:53.383760 IP 79.124.62.74.8080 > 176.79.22.208.4610: tcp 0
      13:47:55.757211 IP 79.124.62.98.8080 > 176.79.22.208.60077: tcp 0
      13:47:58.799248 IP 79.124.62.98.8080 > 176.79.22.208.9216: tcp 0
      13:48:00.335677 IP 79.124.62.98.8080 > 176.79.22.208.17101: tcp 0
      13:48:03.365632 IP 79.124.62.74.8080 > 176.79.22.208.6711: tcp 0
      13:48:03.413042 IP 79.124.62.98.8080 > 176.79.22.208.8834: tcp 0
      13:48:07.343710 IP 79.124.62.74.8080 > 176.79.22.208.6010: tcp 0
      13:48:13.070336 IP 74.120.14.81.65353 > 176.79.22.208.10086: tcp 0
      13:48:15.135572 IP 79.124.62.74.8080 > 176.79.22.208.5791: tcp 0
      13:48:19.020341 IP 79.124.62.98.8080 > 176.79.22.208.8335: tcp 0
      13:48:19.640324 IP 79.124.62.74.8080 > 176.79.22.208.5041: tcp 0
      13:48:21.996482 IP 79.124.62.98.8080 > 176.79.22.208.55083: tcp 0
      13:48:38.087428 IP 79.124.62.98.8080 > 176.79.22.208.65023: tcp 0
      13:48:39.276277 IP 79.124.62.74.8080 > 176.79.22.208.7986: tcp 0
      13:48:41.152029 IP 79.124.62.98.8080 > 176.79.22.208.15087: tcp 0
      13:48:41.246138 IP 185.189.167.57.33361 > 176.79.22.208.33389: tcp 0
      13:48:41.964394 IP 193.242.145.106.40801 > 176.79.22.208.4087: tcp 0
      13:48:47.408662 IP 79.124.62.74.8080 > 176.79.22.208.3885: tcp 0
      13:48:49.742456 IP 148.63.127.226.53734 > 176.79.22.208.443: tcp 0
      13:48:49.742698 IP 176.79.22.208.443 > 148.63.127.226.53734: tcp 0
      13:48:49.742820 IP 148.63.127.226.63748 > 176.79.22.208.443: tcp 0
      13:48:49.742968 IP 176.79.22.208.443 > 148.63.127.226.63748: tcp 0
      13:48:50.286313 IP 93.179.107.198.59665 > 176.79.22.208.445: tcp 0
      13:48:50.756705 IP 148.63.127.226.63748 > 176.79.22.208.443: tcp 0
      13:48:50.756823 IP 148.63.127.226.53734 > 176.79.22.208.443: tcp 0
      13:48:50.756937 IP 176.79.22.208.443 > 148.63.127.226.63748: tcp 0
      13:48:50.757042 IP 176.79.22.208.443 > 148.63.127.226.53734: tcp 0
      13:48:51.120885 IP 79.124.62.74.8080 > 176.79.22.208.6624: tcp 0
      13:48:51.845747 IP 79.124.62.74.8080 > 176.79.22.208.6777: tcp 0
      13:48:51.929615 IP 79.124.62.98.8080 > 176.79.22.208.34089: tcp 0
      13:48:52.768718 IP 148.63.127.226.53734 > 176.79.22.208.443: tcp 0
      13:48:52.768932 IP 176.79.22.208.443 > 148.63.127.226.53734: tcp 0
      13:48:52.769058 IP 148.63.127.226.63748 > 176.79.22.208.443: tcp 0
      13:48:52.769231 IP 176.79.22.208.443 > 148.63.127.226.63748: tcp 0
      13:48:54.755034 ARP, Request who-has 176.79.22.1 tell 176.79.22.208, length 46
      13:48:54.755935 ARP, Reply 176.79.22.1 is-at 00:03:fa:00:00:01, length 46
      13:48:55.812727 IP 79.124.62.98.8080 > 176.79.22.208.24049: tcp 0
      13:48:56.781457 IP 148.63.127.226.63748 > 176.79.22.208.443: tcp 0
      13:48:56.781697 IP 176.79.22.208.443 > 148.63.127.226.63748: tcp 0
      13:48:56.781726 IP 148.63.127.226.53734 > 176.79.22.208.443: tcp 0
      13:48:56.781984 IP 176.79.22.208.443 > 148.63.127.226.53734: tcp 0
      13:49:02.605122 IP 79.124.62.98.8080 > 176.79.22.208.31045: tcp 0
      13:49:04.793960 IP 148.63.127.226.53734 > 176.79.22.208.443: tcp 0
      13:49:04.794003 IP 148.63.127.226.63748 > 176.79.22.208.443: tcp 0
      13:49:04.794221 IP 176.79.22.208.443 > 148.63.127.226.53734: tcp 0
      13:49:04.794311 IP 176.79.22.208.443 > 148.63.127.226.63748: tcp 0
      13:49:06.282424 IP 79.124.62.98.8080 > 176.79.22.208.9534: tcp 0
      13:49:08.167022 IP 79.124.62.98.8080 > 176.79.22.208.22083: tcp 0
      13:49:10.812237 IP 79.124.62.74.8080 > 176.79.22.208.5472: tcp 0

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

        @s_serra said in Get public ip for pcs:

        00:03:fa:00:00:01

        Really? What are the odds of that? But looks arp is working..

        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

        S 1 Reply Last reply Reply Quote 0
        • S
          s_serra @johnpoz
          last edited by

          @johnpoz

          Do you know why the doors are not open to the outside? I already have my head in water :(

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Mmm, you can see it's replying and that traffic is leaving the pfSense WAN.

            Assuming you opened it to everywhere, as your rules showed above, I am not seeing any reply packets if I test from here.
            So either something is blocking the replies upstream or the replies are going to wrong place.

            Increase the view detail in the pcap and make sure the MAC addresses are correct on those packets.

            Steve

            S 1 Reply Last reply Reply Quote 0
            • S
              s_serra @stephenw10
              last edited by s_serra

              @stephenw10
              faeab9a5-6e2a-431e-9a1f-ba25e4d1cfc3-image.png

              28606953-9846-42b0-ab70-9170e10e63c8-image.png
              5f0a0244-2e17-4bdc-b6a3-7d54c3c3820e-image.png

              I had turned off the server

              then everything was open.

              I asked a colleague of mine to ping the ip 176.79.22.208 and he can't. on ip 176.79.20.129 which is the ip wan of pfsense it gets. it's a bit weird

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

                @s_serra So if I traceroute to that IP.. Looks like it dies at what should be your gateway.

                $ tracert -d 176.79.22.208
                
                Tracing route to 176.79.22.208 over a maximum of 30 hops
                
                  1    <1 ms    <1 ms     1 ms  192.168.9.253
                  2    18 ms    13 ms    11 ms  50.4.135.1
                  3     9 ms    11 ms     9 ms  76.73.191.106
                  4    10 ms    14 ms     9 ms  76.73.164.121
                  5    12 ms    11 ms    12 ms  74.199.91.22
                  6    29 ms    20 ms    21 ms  24.214.131.161
                  7    20 ms    20 ms    29 ms  24.192.154.220
                  8    39 ms    32 ms    31 ms  69.73.2.4
                  9    32 ms    35 ms    31 ms  75.76.35.13
                 10    32 ms    30 ms    31 ms  206.126.236.37
                 11    31 ms    30 ms    32 ms  72.52.92.226
                 12    35 ms    47 ms    34 ms  184.105.64.122
                 13   114 ms   101 ms    99 ms  184.104.197.74
                 14     *      114 ms   107 ms  184.104.196.161
                 15   117 ms   118 ms   113 ms  184.104.193.150
                 16   123 ms   119 ms   122 ms  184.104.204.234
                 17   126 ms   121 ms   137 ms  195.8.0.158
                 18     *        *      123 ms  195.8.30.246
                 19   118 ms   117 ms   116 ms  176.79.22.1
                 20     *        *        *     Request timed out.
                 21     *        *        *     Request timed out.
                 22     *        *        *     Request timed out.
                

                19 118 ms 117 ms 116 ms 176.79.22.1

                You really need to sniff on your wan when someone is say trying to ping you - if you don't see the traffic hit pfsense.. Well then no its not going to work. no matter what you do on pfsense.

                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

                S 1 Reply Last reply Reply Quote 0
                • S
                  s_serra @johnpoz
                  last edited by s_serra

                  @johnpoz

                  I'm still a noob.

                  How can I sniff out wan's traffic?

                  9aec4a93-824c-4913-a23f-ff30c96a4a54-image.png

                  my pfsense gateway is 176.79.20.1. Do I have to add more gateways to pfsense for the other subnets to communicate?

                  cb75f96c-b68d-48d6-ae6e-dde44a4501cb-image.png

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

                    @s_serra said in Get public ip for pcs:

                    my pfsense gateway is 176.79.20.1

                    Not for that IP range it isn't - your device since its getting its IP from dhcp, should get an gateway in its network. I take its that serra box.. look at a netstat -r to see what its default route is (ie its gateway)

                    example here is linux box on one of my vlans..

                    pi@ntp:~ $ netstat -rn
                    Kernel IP routing table
                    Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
                    0.0.0.0         192.168.3.253   0.0.0.0         UG        0 0          0 eth0
                    192.168.3.0     0.0.0.0         255.255.255.0   U         0 0          0 eth0
                    pi@ntp:~ $ 
                    

                    As to how to sniff. Under diagnostic menu on pfsense, packet capture.

                    You prob want to do that sniff in promiscuous mode - since the traffic towards 22.208 box is not pfsense network..

                    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

                    S 1 Reply Last reply Reply Quote 0
                    • S
                      s_serra @johnpoz
                      last edited by s_serra

                      @johnpoz
                      af6a37af-2c89-4196-8c43-eda94f197d42-image.png

                      in pfsense do I keep this running?

                      65d5a20c-ac2d-4b69-979c-aa0d837c711b-image.png

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

                        sure looks like the 22.1 address I said.. do -rn the n disables name resolution. So just see the IP.

                        You would keep it running until someone pings you.. I just did so you should see ping requests. I can pm you the address would of come from

                        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

                        S 1 Reply Last reply Reply Quote 0
                        • S
                          s_serra @johnpoz
                          last edited by

                          @johnpoz 25ae6cc1-d482-4f3b-b139-e38a964138a5-image.png

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

                            @s_serra yup like I said 22.1 would be that devices gateway, which is last hop I see in my traceroute.. So I am getting there.. Now your sniff should of shown you my ping attempt.

                            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

                            S 1 Reply Last reply Reply Quote 0
                            • S
                              s_serra @johnpoz
                              last edited by

                              @johnpoz

                              15:44:28.869724 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 88
                              15:44:28.869734 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 89
                              15:44:28.869857 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 94
                              15:44:28.869942 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 74
                              15:44:28.870335 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 88
                              15:44:28.870392 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 0
                              15:44:28.870397 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 89
                              15:44:28.870416 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 0
                              15:44:28.870494 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 94
                              15:44:28.870512 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 0
                              15:44:28.870567 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 74
                              15:44:28.870585 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 0
                              15:44:28.871055 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 0
                              15:44:28.871072 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 0
                              15:44:28.871179 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 0
                              15:44:28.871193 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 0
                              15:44:28.872534 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.872549 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.872559 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.872567 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.872576 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.872584 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.872593 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.873508 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.873629 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.873754 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.873851 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 0
                              15:44:28.873877 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.874004 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.874044 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 0
                              15:44:28.874138 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.874243 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 0
                              15:44:28.874253 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.874531 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 0
                              15:44:28.874557 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.874568 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.874578 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.874587 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.874805 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 0
                              15:44:28.874828 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.874838 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.874847 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.874857 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 318
                              15:44:28.874910 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.874941 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 0
                              15:44:28.874966 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.874977 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.874986 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.874995 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1254
                              15:44:28.875624 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.875741 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 0
                              15:44:28.875771 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.875963 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.876047 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.876137 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 0
                              15:44:28.876254 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.876339 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 0
                              15:44:28.876373 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.876502 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.876514 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 318
                              15:44:28.876741 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 0
                              15:44:28.876747 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.876876 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.876938 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 0
                              15:44:28.877005 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.877018 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1460
                              15:44:28.877127 IP 176.79.20.129.443 > 176.79.25.49.64027: tcp 1254
                              15:44:28.877136 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 0
                              15:44:28.877139 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 0
                              15:44:28.877158 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 0
                              15:44:28.877176 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 0
                              15:44:28.877337 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 0
                              15:44:28.877412 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 0
                              15:44:28.877663 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 0
                              15:44:28.877908 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 0
                              15:44:28.878028 IP 176.79.25.49.64027 > 176.79.20.129.443: tcp 0
                              15:44:28.962323 IP 79.124.62.98.8080 > 176.79.25.49.40092: tcp 0
                              15:44:29.194744 IP 176.79.20.129 > 176.79.20.1: ICMP echo request, id 19262, seq 17511, length 9
                              15:44:29.195923 IP 176.79.20.1 > 176.79.20.129: ICMP echo reply, id 19262, seq 17511, length 9
                              15:44:29.593095 IP 176.79.25.49.52398 > 213.163.94.74.50002: UDP, length 60
                              15:44:29.724047 IP 162.159.136.234.443 > 176.79.25.49.57233: tcp 357
                              15:44:29.724081 IP 176.79.20.129 > 176.79.20.1: ICMP echo request, id 19262, seq 17512, length 9
                              15:44:29.765398 IP 176.79.25.49.57233 > 162.159.136.234.443: tcp 0
                              15:44:29.796537 IP 213.163.94.74.50002 > 176.79.25.49.52398: UDP, length 52
                              15:44:29.824189 IP 155.133.246.51.27028 > 176.79.25.49.51776: tcp 189
                              15:44:29.864554 IP 176.79.25.49.51776 > 155.133.246.51.27028: tcp 0
                              15:44:30.133648 IP 176.79.25.49.63231 > 185.12.116.108.2083: tcp 1
                              15:44:30.145388 IP 185.12.116.108.2083 > 176.79.25.49.63231: tcp 0
                              15:44:30.256330 IP 176.79.20.129 > 176.79.20.1: ICMP echo request, id 19262, seq 17513, length 9
                              15:44:30.257203 IP 176.79.20.1 > 176.79.20.129: ICMP echo reply, id 19262, seq 17513, length 9
                              15:44:30.284863 IP 162.159.136.234.443 > 176.79.25.49.57233: tcp 56
                              15:44:30.325569 IP 176.79.25.49.57233 > 162.159.136.234.443: tcp 0
                              15:44:30.602764 IP 79.124.62.98.8080 > 176.79.20.129.52007: tcp 0
                              15:44:30.788574 IP 176.79.20.129 > 176.79.20.1: ICMP echo request, id 19262, seq 17514, length 9
                              15:44:30.789372 IP 176.79.20.1 > 176.79.20.129: ICMP echo reply, id 19262, seq 17514, length 9
                              15:44:30.796609 IP 213.163.94.74.50002 > 176.79.25.49.52398: UDP, length 52
                              15:44:31.298497 IP 176.79.20.129 > 176.79.20.1: ICMP echo request, id 19262, seq 17515, length 9
                              15:44:31.299483 IP 176.79.20.1 > 176.79.20.129: ICMP echo reply, id 19262, seq 17515, length 9
                              15:44:31.390581 IP 176.79.25.49.63203 > 185.12.116.108.2083: tcp 1
                              15:44:31.401939 IP 185.12.116.108.2083 > 176.79.25.49.63203: tcp 0

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

                                @s_serra you filled up the 100 packet count before I pinged you... In the capture set it to the IP I sent you in PM.. And I will ping you again... I have a continuous ping running now

                                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

                                S 1 Reply Last reply Reply Quote 0
                                • S
                                  s_serra @johnpoz
                                  last edited by

                                  @johnpoz

                                  I sent it in pm which returned the packet capture

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

                                    @s_serra Ok - well so getting to pfsense.

                                    Now do the same thing on the lan side interface.. If we don't see it there, then something wrong with the bridge..

                                    My ping is still running. If you do see it there - then something on the client blocking it.

                                    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

                                    S 1 Reply Last reply Reply Quote 0
                                    • S
                                      s_serra @johnpoz
                                      last edited by

                                      @johnpoz

                                      15:56:55.997368 IP x.x.x.x > 176.79.22.208: ICMP echo request, id 54626, seq 182, length 40
                                      15:57:00.994130 IP x.x.x.x > 176.79.22.208: ICMP echo request, id 54626, seq 183, length 40

                                      on the lan side it also worked, I tested it on the bridge interface and it also receives a response

                                      johnpozJ 1 Reply Last reply Reply Quote 0
                                      • stephenw10S
                                        stephenw10 Netgate Administrator
                                        last edited by

                                        So you see replies from the server on LAN and Bridge but not WAN?

                                        Did you check the MAC addresses in the pcap yet? You need to confirm those are correct.

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

                                          @s_serra You say you see a response? Or you see my ping going to your 22.208 address?

                                          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

                                          S 1 Reply Last reply Reply Quote 0
                                          • S
                                            s_serra @johnpoz
                                            last edited by

                                            @johnpoz

                                            I saw ping icmp on all interfaces

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