logs/traces

Navdeep Parhar nparhar at gmail.com
Wed Oct 16 02:53:14 UTC 2019


Have you looked at siftr(4) or dtrace_tcp(4)?

Regards,
Navdeep

On Tue, Oct 15, 2019 at 07:15:27PM -0700, vm finance wrote:
> 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 at 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 at gmail.com
> > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
> >
> >
> > On Tue, Oct 15, 2019 at 3:17 AM vm finance <vm.finance2 at 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 at freebsd.org mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> >> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"
> >>
> >
> _______________________________________________
> freebsd-net at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"


More information about the freebsd-net mailing list