Here is a working tcpdump sample. Although I had to define the interface in the tcpdump cmdline.
godzilla# tcpdump -i nfe0 -nn 'net 2607:f238:2::/48' tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on nfe0, link-type EN10MB (Ethernet), capture size 65535 bytes 20:48:18.482969 IP6 2607:f238:2::11.36019 > 2001:470:8:104::2.123: NTPv3, Client, length 48 20:48:18.483021 IP6 2001:470:8:104::2.123 > 2607:f238:2::11.36019: NTPv3, Server, length 48 20:58:50.964303 IP6 2607:f238:2::11.60063 > 2001:470:8:104::2.123: NTPv3, Client, length 48 20:58:50.964337 IP6 2001:470:8:104::2.123 > 2607:f238:2::11.60063: NTPv3, Server, length 48 On Thu, Jun 27, 2013 at 4:43 PM, Ask Bjørn Hansen <[email protected]> wrote: > I need some help debugging it. > > The monitoring system should send you a packet every ~15 minutes from > 2607:f238:2::/48 > > For those of you who have problems, can you run > > tcpdump -nn 'net 2607:f238:2::/48' > > and let me know what you see? Since traceroutes seem to work fine both > way (?!) it must be something more insidious. > > > > > Ask > _______________________________________________ > pool mailing list > [email protected] > http://lists.ntp.org/listinfo/pool >
_______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
