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

    Strange ip addresses in multicast VRRP/CARP packets

    Scheduled Pinned Locked Moved HA/CARP/VIPs
    4 Posts 4 Posters 906 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.
    • T
      Tino010
      last edited by

      I have  setup a carp failover enviroment built on non internet connected devices.
      This works as expected. But I do notice some strange activity in the packets details to vrrp 224.0.0.18.
      In wireshark in the packet details it's announcement I noticed  the following ip addresses in the packets.

      152.162.185.107
      ANS Communications, Inc (ANS) US

      1.178.202.190
      iseek Communications Australia

      215.25.75.153
      DoD Network Information Center (DNIC) US

      184.11.30.16
      Frontier Communications of America, Inc. US

      134.138.168.76
      RIPE-ERX-134-138-0-0 Sweden

      160.46.170.143
      BMW AG, Berlin production plant BMW Germany

      204.253.163.175
      Verizon Business US

      The interfaces part of a /29 network and on a interface with no vlan on the pfsense but it has it's own vlan number on the switch

      I hope somebody can give me an answer to this question.

      I am running on 2.3.4_1 enviroment

      1 Reply Last reply Reply Quote 0
      • dotdashD
        dotdash
        last edited by

        @Tino010:

        I have  setup a carp failover enviroment built on non internet connected devices.
        This works as expected. But I do notice some strange activity in the packets details to vrrp 224.0.0.18.

        Try decoding the carp packets as carp, and not vrrp.

        1 Reply Last reply Reply Quote 0
        • K
          kpa
          last edited by

          Yeap, carp is not the same protocol as vrrp although they share the same protocol number in the IP headers.

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

            Yeah what kind of connection is this on? You will see any other CARP/VRRP on that broadcast/multicast domain. Strange to see such varying IP addresses but it depends on what you're connected to.

            You can set Wireshark to decode protocol 112 as CARP though. Those other multicasts might actually be VRRP though. They can coexist.

            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.