4. Dpinger duplicate echo

Dpinger duplicate echo

  • G

    Oct 3 19:10:39 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 19:10:39 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 19:10:39 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 19:03:47 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 19:03:47 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 19:03:47 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 19:03:12 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 19:03:12 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 19:03:12 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 19:02:24 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 19:02:24 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 19:02:24 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:58:01 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:58:01 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:58:01 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:55:48 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:55:48 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:55:48 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:53:38 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:53:38 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:53:38 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:53:22 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:53:22 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:53:22 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:53:19 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:53:19 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:53:19 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:53:17 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:53:17 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:53:17 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:51:20 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:51:20 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:51:20 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:50:37 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:50:37 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:50:37 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:50:32 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:50:32 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:50:32 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:47:09 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:47:09 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:47:09 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:47:02 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:47:02 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:47:02 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:41:54 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:41:54 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:41:54 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:33:31 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:33:31 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:33:31 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:30:38 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:30:38 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:30:38 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:29:55 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:29:55 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:29:55 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:29:54 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:29:54 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:29:54 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:29:30 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:29:30 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:29:30 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:25:28 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:25:28 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:25:28 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:25:22 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:25:22 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:25:22 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received
    Oct 3 18:24:47 dpinger CABLEMODEM_DHCP 8.8.8.8: duplicate echo reply received

    0
  • G

    edited

    0
  • LAYER 8 Netgate

    00:30:B8 Riverdel RiverDelta Networks
    0C:C4:7A SuperMic Super Micro Computer, Inc.

    21:54:47.982787 0c:c4:7a:09:c1:2c > 00:30:b8:d7:a6:31, ethertype IPv4 (0x0800), length 42: (tos 0x0, ttl 64, id 35543, offset 0, flags [none], proto ICMP (1), length 28)
        209.105.186.239 > 8.8.8.8: ICMP echo request, id 25599, seq 4330, length 8
    21:54:48.003038 00:30:b8:d7:a6:31 > 0c:c4:7a:09:c1:2c, ethertype IPv4 (0x0800), length 60: (tos 0x0, ttl 56, id 35930, offset 0, flags [none], proto ICMP (1), length 28)
        8.8.8.8 > 209.105.186.239: ICMP echo reply, id 25599, seq 4330, length 8
    21:54:48.003969 00:30:b8:d7:a6:31 > 0c:c4:7a:09:c1:2c, ethertype IPv4 (0x0800), length 60: (tos 0x0, ttl 56, id 35930, offset 0, flags [none], proto ICMP (1), length 28)
        8.8.8.8 > 209.105.186.239: ICMP echo reply, id 25599, seq 4330, length 8

    Need to ask upstream why they are sending two replies to every request.

    Or check your WAN layer 2 to see why the response is being duplicated/looped there. Probably not a loop since there would be more than two.

    0
  • G

    supermicros my firewall and it comes and goes in spirts 5 dup packets is most ive seen, this is on a cable modem system and wonder if it has todo with high errors correctable and uncorrectable

    speeds are slow service is nonexistent, I wish i could get upstream to do something

    0
  • LAYER 8 Netgate

    Sorry. All I can tell from that is you are sending one and getting two back.

    If it was me I would put a switch between the cable modem and the WAN interface so I could packet capture the data on the wire to and from the modem.

    I would not let up on the ISP.

    Or I would cancel and use something else. I realize options might be limited but it is ultimately the only thing they understand. Cable companies usually have fairly aggressive customer retention departments. If you cannot get any satisfaction in support you might call to cancel and tell them why.

    0
  • G

    If i am using pfsense's packet capture why do i need to use a switch to packet capture?

    do you have a small recommended cheap (i assume it needs to be managed so i can mirror the ports?)

    0
  • G

    and the riverdelta networks was acquired by motorola and cmts is a motorola bsr 64000

    0
 

Products

Applications

Support

Services

News

Resources

Company

Our Mission

As host of the pfSense open source firewall project, Netgate believes in enhancing network connectivity that maintains both security and privacy. We also believe everyone should be able to afford it.

Subscribe to our Newsletter

Product information, software announcements, and special offers. See our newsletter archive for past announcements.

© Copyright 2002 - 2019 Rubicon Communications, LLC | Privacy Policy