4. IPv6 problem, periodic loss of packets

IPv6 problem, periodic loss of packets

  • I

    Hello everyone!

    I'm quite new to IPv6 and I'm fighting problems for a few days, but no progress.

    IPv6 net is obtained through he.net and it seems to work fine from Pfsense router. The problems start when I'm trying to ping any IPv6 address from LAN (even router interface itself).

    Pfsense version: 2.3.2-RELEASE

    Ping:

    Pinging google.com [2a00:1450:400c:c04::66] with 32 bytes of data:
Reply from 2a00:1450:400c:c04::66: time=20ms
Reply from 2a00:1450:400c:c04::66: time=22ms
Reply from 2a00:1450:400c:c04::66: time=20ms
Request timed out.
Request timed out.
Reply from 2a00:1450:400c:c04::66: time=20ms
Reply from 2a00:1450:400c:c04::66: time=21ms
Reply from 2a00:1450:400c:c04::66: time=20ms
Reply from 2a00:1450:400c:c04::66: time=21ms
Reply from 2a00:1450:400c:c04::66: time=20ms
Reply from 2a00:1450:400c:c04::66: time=21ms
Request timed out.
Reply from 2a00:1450:400c:c04::66: time=469ms
Reply from 2a00:1450:400c:c04::66: time=22ms
Reply from 2a00:1450:400c:c04::66: time=20ms
Reply from 2a00:1450:400c:c04::66: time=20ms
Reply from 2a00:1450:400c:c04::66: time=21ms
Reply from 2a00:1450:400c:c04::66: time=22ms
Reply from 2a00:1450:400c:c04::66: time=21ms
Reply from 2a00:1450:400c:c04::66: time=20ms
Reply from 2a00:1450:400c:c04::66: time=21ms
Request timed out.
Request timed out.
Request timed out.
Reply from 2a00:1450:400c:c04::66: time=20ms
Reply from 2a00:1450:400c:c04::66: time=20ms
Reply from 2a00:1450:400c:c04::66: time=22ms
Reply from 2a00:1450:400c:c04::66: time=21ms
Reply from 2a00:1450:400c:c04::66: time=21ms
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 2a00:1450:400c:c04::66: time=21ms
Reply from 2a00:1450:400c:c04::66: time=21ms
Reply from 2a00:1450:400c:c04::66: time=20ms
Reply from 2a00:1450:400c:c04::66: time=21ms
Reply from 2a00:1450:400c:c04::66: time=21ms
Reply from 2a00:1450:400c:c04::66: time=20ms
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 2a00:1450:400c:c04::66: time=26ms
Reply from 2a00:1450:400c:c04::66: time=21ms
Reply from 2a00:1450:400c:c04::66: time=21ms
Reply from 2a00:1450:400c:c04::66: time=20ms
Request timed out.

Ping statistics for 2a00:1450:400c:c04::66:
    Packets: Sent = 50, Received = 33, Lost = 17 (34% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 469ms, Average = 34ms

    Packet capture on LAN interface:

    00:13:51.837274 IP6 2001:470:aaaa:835::1 > 2001:470:bbbb::ffff: ICMP6, echo request, seq 3045, length 40
00:13:51.837418 IP6 2001:470:bbbb::ffff > 2001:470:aaaa:835::1: ICMP6, echo reply, seq 3045, length 40
00:13:52.855286 IP6 2001:470:aaaa:835::1 > 2001:470:bbbb::ffff: ICMP6, echo request, seq 3046, length 40
00:13:52.855351 IP6 2001:470:bbbb::ffff > 2001:470:aaaa:835::1: ICMP6, echo reply, seq 3046, length 40
00:13:53.887508 IP6 2001:470:aaaa:835::1 > 2001:470:bbbb::ffff: ICMP6, echo request, seq 3047, length 40
00:13:53.887577 IP6 2001:470:bbbb::ffff > 2001:470:aaaa:835::1: ICMP6, echo reply, seq 3047, length 40
00:13:54.932242 IP6 2001:470:aaaa:835::1 > 2001:470:bbbb::ffff: ICMP6, echo request, seq 3048, length 40
00:13:54.932313 IP6 2001:470:bbbb::ffff > 2001:470:aaaa:835::1: ICMP6, echo reply, seq 3048, length 40
00:13:55.401273 IP6 2001:470:aaaa:835::ffff > 2001:470:aaaa:835::1: ICMP6, neighbor solicitation, who has 2001:470:aaaa:835::1, length 32
00:13:55.962765 IP6 2001:470:aaaa:835::1 > 2001:470:bbbb::ffff: ICMP6, echo request, seq 3049, length 40
00:13:55.962819 IP6 2001:470:bbbb::ffff > 2001:470:aaaa:835::1: ICMP6, echo reply, seq 3049, length 40
00:13:56.401282 IP6 2001:470:aaaa:835::ffff > 2001:470:aaaa:835::1: ICMP6, neighbor solicitation, who has 2001:470:aaaa:835::1, length 32
00:13:57.004219 IP6 2001:470:aaaa:835::1 > 2001:470:bbbb::ffff: ICMP6, echo request, seq 3050, length 40
00:13:57.004274 IP6 2001:470:bbbb::ffff > 2001:470:aaaa:835::1: ICMP6, echo reply, seq 3050, length 40
00:13:57.401276 IP6 2001:470:aaaa:835::ffff > 2001:470:aaaa:835::1: ICMP6, neighbor solicitation, who has 2001:470:aaaa:835::1, length 32
00:13:58.041028 IP6 2001:470:aaaa:835::1 > 2001:470:bbbb::ffff: ICMP6, echo request, seq 3051, length 40
00:13:58.041082 IP6 2001:470:bbbb::ffff > 2001:470:aaaa:835::1: ICMP6, echo reply, seq 3051, length 40
00:13:59.071966 IP6 2001:470:aaaa:835::1 > 2001:470:bbbb::ffff: ICMP6, echo request, seq 3052, length 40
00:13:59.072067 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2001:470:aaaa:835::1, length 32
00:14:00.071262 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2001:470:aaaa:835::1, length 32
00:14:01.105261 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2001:470:aaaa:835::1, length 32
00:14:03.782346 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1: ICMP6, router advertisement, length 144
00:14:03.924850 IP6 2001:470:aaaa:835::1 > 2001:470:bbbb::ffff: ICMP6, echo request, seq 3053, length 40
00:14:03.924954 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2001:470:aaaa:835::1, length 32
00:14:04.924265 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2001:470:aaaa:835::1, length 32
00:14:05.924275 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2001:470:aaaa:835::1, length 32
00:14:08.915867 IP6 2001:470:aaaa:835::1 > 2001:470:bbbb::ffff: ICMP6, echo request, seq 3054, length 40
00:14:08.915971 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2001:470:aaaa:835::1, length 32
00:14:09.915266 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2001:470:aaaa:835::1, length 32
00:14:09.975338 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1: ICMP6, router advertisement, length 144
00:14:10.915271 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2001:470:aaaa:835::1, length 32
00:14:13.922606 IP6 2001:470:aaaa:835::1 > 2001:470:bbbb::ffff: ICMP6, echo request, seq 3055, length 40
00:14:13.922704 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2001:470:aaaa:835::1, length 32
00:14:14.922269 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2001:470:aaaa:835::1, length 32
00:14:15.922282 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2001:470:aaaa:835::1, length 32
00:14:18.920506 IP6 2001:470:aaaa:835::1 > 2001:470:bbbb::ffff: ICMP6, echo request, seq 3056, length 40
00:14:18.920603 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2001:470:aaaa:835::1, length 32
00:14:19.010121 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1: ICMP6, router advertisement, length 144
00:14:19.920260 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2001:470:aaaa:835::1, length 32
00:14:20.920264 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2001:470:aaaa:835::1, length 32
00:14:23.923451 IP6 2001:470:aaaa:835::1 > 2001:470:bbbb::ffff: ICMP6, echo request, seq 3057, length 40
00:14:23.923552 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2001:470:aaaa:835::1, length 32
00:14:24.923266 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2001:470:aaaa:835::1, length 32
00:14:25.923280 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2001:470:aaaa:835::1, length 32
00:14:26.504368 IP6 fe80::92fb:a6ff:feca:ac8c > ff02::1: ICMP6, router advertisement, length 144

    As far as I can see the router stops to respond to pings after "ICMP6, neighbor solicitation" requests with no response.

    Any ideas?

    0
Log in to reply
 

Products

Services

Support

News

Resources

Company

Our Mission

We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

Subscribe to our Newsletter

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

© Copyright 2019 Rubicon Communications, LLC | Privacy Policy