Date: Tue, 15 Oct 2019 19:15:27 -0700 From: vm finance <vm.finance2@gmail.com> To: Kevin Oberman <rkoberman@gmail.com> Cc: freebsd-net <freebsd-net@freebsd.org> Subject: Re: logs/traces Message-ID: <CAKy-8=j_pTAenauicBp%2BiZf4EVko6ww=Ge5cPv6mxrVMOg0quQ@mail.gmail.com> In-Reply-To: <CAN6yY1vAtA2_zDCapRpLQPYuxOyCvokPFE%2B=wZP9TDscRoN0-Q@mail.gmail.com> References: <CAKy-8=gy4mAS0HedGxGRCscVWL1V%2BEtvtA2PR8oFbNPOTSzwmQ@mail.gmail.com> <CAN6yY1vAtA2_zDCapRpLQPYuxOyCvokPFE%2B=wZP9TDscRoN0-Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Kevin, I am looking to enable traces/log messages (like syslog or /var/log/messages) inside the codebase... any pointers for tcp/ip. tcpdump shows what is going on wire - but I would like to trace code internals...printk.. Thanks a lot! On Tue, Oct 15, 2019 at 6:11 PM Kevin Oberman <rkoberman@gmail.com> wrote: > Use tcpdump(1) and/or net/wireshark(5). See man tcpdump and pcap-filter > for usage details. wireshark can analyze files collected by tcpdump and > dissect the packets. It can also do packet capture, itself. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > > > On Tue, Oct 15, 2019 at 3:17 AM vm finance <vm.finance2@gmail.com> wrote: > >> Hi, >> >> Could someone please guide me on how to turn on tracing/log? >> >> I would like to follow/track how packets go in/out of TCP code block... >> Please let me know what knobs are available to achieve this. >> >> Thanks for any pointers. >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKy-8=j_pTAenauicBp%2BiZf4EVko6ww=Ge5cPv6mxrVMOg0quQ>