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

    [gelöst] Ping request

    Scheduled Pinned Locked Moved Deutsch
    6 Posts 2 Posters 687 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.
    • C
      chris_6n
      last edited by

      Hallo zusammen,

      mir ist aufgefallen das vom pfsense jede menge Ping-Anfragen gesendet werden und wollte mal fragen ob das normales ist?
      Ein solches Verhalten kenne ich so nicht.

      Router -> 192.168.178.1    fe80::ca0e:14ff:xxxx:xxxx
      pfsense -> 192.168.178.27    fe80::21b:21ff:xxxx:xxxx

      
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on igb0, link-type EN10MB (Ethernet), capture size 262144 bytes
16:32:26.896750 ARP, Request who-has 192.168.178.23 tell 192.168.178.1, length 46
16:32:26.942972 IP6 fe80::21b:21ff:xxxx:xxxx > fe80::ca0e:14ff:xxxx:xxxx: ICMP6, echo request, seq 9971, length 8
16:32:26.943233 IP6 fe80::ca0e:14ff:xxxx:xxxx > fe80::21b:21ff:xxxx:xxxx: ICMP6, echo reply, seq 9971, length 8
16:32:27.189167 IP 192.168.178.27 > 192.168.178.1: ICMP echo request, id 29620, seq 9975, length 8
16:32:27.189445 IP 192.168.178.1 > 192.168.178.27: ICMP echo reply, id 29620, seq 9975, length 8
16:32:27.468888 IP6 fe80::21b:21ff:xxxx:xxxx > fe80::ca0e:14ff:xxxx:xxxx: ICMP6, echo request, seq 9972, length 8
16:32:27.469278 IP6 fe80::ca0e:14ff:xxxx:xxxx > fe80::21b:21ff:xxxx:xxxx: ICMP6, echo reply, seq 9972, length 8
16:32:27.719148 IP 192.168.178.27 > 192.168.178.1: ICMP echo request, id 29620, seq 9976, length 8
16:32:27.719443 IP 192.168.178.1 > 192.168.178.27: ICMP echo reply, id 29620, seq 9976, length 8
16:32:27.887386 ARP, Request who-has 192.168.178.23 tell 192.168.178.1, length 46
16:32:28.001197 IP6 fe80::21b:21ff:xxxx:xxxx > fe80::ca0e:14ff:xxxx:xxxx: ICMP6, echo request, seq 9973, length 8
16:32:28.001599 IP6 fe80::ca0e:14ff:xxxx:xxxx > fe80::21b:21ff:xxxx:xxxx: ICMP6, echo reply, seq 9973, length 8
16:32:28.247904 IP 192.168.178.27 > 192.168.178.1: ICMP echo request, id 29620, seq 9977, length 8
16:32:28.248179 IP 192.168.178.1 > 192.168.178.27: ICMP echo reply, id 29620, seq 9977, length 8
16:32:28.533391 IP6 fe80::21b:21ff:xxxx:xxxx > fe80::ca0e:14ff:xxxx:xxxx: ICMP6, echo request, seq 9974, length 8
16:32:28.533791 IP6 fe80::ca0e:14ff:xxxx:xxxx > fe80::21b:21ff:xxxx:xxxx: ICMP6, echo reply, seq 9974, length 8
16:32:28.779157 IP 192.168.178.27 > 192.168.178.1: ICMP echo request, id 29620, seq 9978, length 8
16:32:28.779448 IP 192.168.178.1 > 192.168.178.27: ICMP echo reply, id 29620, seq 9978, length 8
16:32:28.887375 ARP, Request who-has 192.168.178.23 tell 192.168.178.1, length 46
16:32:29.065642 IP6 fe80::21b:21ff:xxxx:xxxx > fe80::ca0e:14ff:xxxx:xxxx: ICMP6, echo request, seq 9975, length 8
16:32:29.066031 IP6 fe80::ca0e:14ff:xxxx:xxxx > fe80::21b:21ff:xxxx:xxxx: ICMP6, echo reply, seq 9975, length 8
16:32:29.311632 IP 192.168.178.27 > 192.168.178.1: ICMP echo request, id 29620, seq 9979, length 8
16:32:29.311910 IP 192.168.178.1 > 192.168.178.27: ICMP echo reply, id 29620, seq 9979, length 8
16:32:29.613669 IP6 fe80::21b:21ff:xxxx:xxxx > fe80::ca0e:14ff:xxxx:xxxx: ICMP6, echo request, seq 9976, length 8
16:32:29.614088 IP6 fe80::ca0e:14ff:xxxx:xxxx > fe80::21b:21ff:xxxx:xxxx: ICMP6, echo reply, seq 9976, length 8
16:32:29.821992 IP 192.168.178.27 > 192.168.178.1: ICMP echo request, id 29620, seq 9980, length 8
16:32:29.822267 IP 192.168.178.1 > 192.168.178.27: ICMP echo reply, id 29620, seq 9980, length 8
16:32:29.896979 ARP, Request who-has 192.168.178.23 tell 192.168.178.1, length 46
16:32:30.125921 IP6 fe80::21b:21ff:xxxx:xxxx > fe80::ca0e:14ff:xxxx:xxxx: ICMP6, echo request, seq 9977, length 8
16:32:30.126175 IP6 fe80::ca0e:14ff:xxxx:xxxx > fe80::21b:21ff:xxxx:xxxx: ICMP6, echo reply, seq 9977, length 8
16:32:30.351935 IP 192.168.178.27 > 192.168.178.1: ICMP echo request, id 29620, seq 9981, length 8
16:32:30.352210 IP 192.168.178.1 > 192.168.178.27: ICMP echo reply, id 29620, seq 9981, length 8
16:32:30.656911 IP6 fe80::21b:21ff:xxxx:xxxx > fe80::ca0e:14ff:xxxx:xxxx: ICMP6, echo request, seq 9978, length 8
16:32:30.657444 IP6 fe80::ca0e:14ff:xxxx:xxxx > fe80::21b:21ff:xxxx:xxxx: ICMP6, echo reply, seq 9978, length 8
16:32:30.887186 ARP, Request who-has 192.168.178.23 tell 192.168.178.1, length 46
16:32:30.887241 IP 192.168.178.27 > 192.168.178.1: ICMP echo request, id 29620, seq 9982, length 8
16:32:30.887523 IP 192.168.178.1 > 192.168.178.27: ICMP echo reply, id 29620, seq 9982, length 8

      By

      1 Reply Last reply Reply Quote 0
      • JeGrJ
        JeGr LAYER 8 Moderator
        last edited by

        Ja natürlich. Der Gateway Check via dpinger muss ja mittels irgendeinem Mechanismus feststellen können ob das GW bspw. down oder nicht erreichbar ist. Und das gilt ebenso für v4 GWs wie auch v6 :)

        Don't forget to upvote 👍 those who kindly offered their time and brainpower to help you!

        If you're interested, I'm available to discuss details of German-speaking paid support (for companies) if needed.

        1 Reply Last reply Reply Quote 0
        • C
          chris_6n
          last edited by

          Habe es auch gerade gefunden.  ;D
          Der 500 Millisekunden Intervall ist schon ein bisschen oversize finde ich.  :o

          Danke für deine Hilfe.

          Zum deaktivieren:

          
System -> Routing -> Gateways 

Gateway Monitoring
Disable Gateway Monitoring This will consider this gateway as always being up.

Gateway Action
Disable Gateway Monitoring Action No action will be taken on gateway events. The gateway is always considered up.

          By

          1 Reply Last reply Reply Quote 0
          • JeGrJ
            JeGr LAYER 8 Moderator
            last edited by

            Natürlich aber das lässt sich ja problemlos reduzieren in den GW Einstellungen. Bei einem MultiWan Setup oder im Carp bist du aber auf schnelle Detektion angewiesen um mögliche Paketverluste beim Umschalten zu vermeiden :)

            Don't forget to upvote 👍 those who kindly offered their time and brainpower to help you!

            If you're interested, I'm available to discuss details of German-speaking paid support (for companies) if needed.

            1 Reply Last reply Reply Quote 0
            • C
              chris_6n
              last edited by

              MultiWan oder Carp auf jeden Fall 100% ein muss.
              Aber nicht für zu Hause.  ;D

              By

              1 Reply Last reply Reply Quote 0
              • JeGrJ
                JeGr LAYER 8 Moderator
                last edited by

                Nicht? ;) Bei mir schon :D Aber ich muss es auch testen ;)

                Don't forget to upvote 👍 those who kindly offered their time and brainpower to help you!

                If you're interested, I'm available to discuss details of German-speaking paid support (for companies) if needed.

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