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

    Link local continous ping? (Solved)

    Scheduled Pinned Locked Moved IPv6
    2 Posts 1 Posters 975 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.
    • R
      ropeguru
      last edited by

      I am running version 2.1.1 snapshot, have also seen this on 2.1, and my pfsense is doing a continous ping to my Comcast Netgear's link local address. I cannot find out where this si coming from in pfsense. I have even shut down apinger but the pings ae still going.

      Any ideas?

      f346 is my pfsense link local
      f2b7 is my Netgear gateway

      11:06:28.394992 IP6 fe80::290:dcff:fe02:f346 > fe80::22e5:2aff:feb7:f2b7: ICMP6, echo request, seq 5888, length 24
      11:06:28.395601 IP6 fe80::22e5:2aff:feb7:f2b7 > fe80::290:dcff:fe02:f346: ICMP6, echo reply, seq 5888, length 24
      11:06:29.405150 IP6 fe80::290:dcff:fe02:f346 > fe80::22e5:2aff:feb7:f2b7: ICMP6, echo request, seq 6144, length 24
      11:06:29.405706 IP6 fe80::22e5:2aff:feb7:f2b7 > fe80::290:dcff:fe02:f346: ICMP6, echo reply, seq 6144, length 24
      11:06:30.415049 IP6 fe80::290:dcff:fe02:f346 > fe80::22e5:2aff:feb7:f2b7: ICMP6, echo request, seq 6400, length 24
      11:06:30.415568 IP6 fe80::22e5:2aff:feb7:f2b7 > fe80::290:dcff:fe02:f346: ICMP6, echo reply, seq 6400, length 24
      11:06:31.425822 IP6 fe80::290:dcff:fe02:f346 > fe80::22e5:2aff:feb7:f2b7: ICMP6, echo request, seq 6656, length 24
      11:06:31.426504 IP6 fe80::22e5:2aff:feb7:f2b7 > fe80::290:dcff:fe02:f346: ICMP6, echo reply, seq 6656, length 24
      11:06:32.435173 IP6 fe80::290:dcff:fe02:f346 > fe80::22e5:2aff:feb7:f2b7: ICMP6, echo request, seq 6912, length 24
      11:06:32.435759 IP6 fe80::22e5:2aff:feb7:f2b7 > fe80::290:dcff:fe02:f346: ICMP6, echo reply, seq 6912, length 24

      1 Reply Last reply Reply Quote 0
      • R
        ropeguru
        last edited by

        Never mind. Apparently apinger was restarting after being stopped. Just disabled it for each of the gateways and all is good now.

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