--- Begin Message ---
Hi Guy,
> BTW, having just implemented SLL2 support in Wireshark, the layout of the
> header really doesn't work as well as I'd like with ARPHRD_NETLINK packets.
> I'd prefer something like
> struct header {
> uint16_t hatype;/* link-layer address typ
--- Begin Message ---
Hi Guy,
> > BTW man pages (pcap.3pcap.in, pcap_datalink.3pcap.in, pcap_loop.3pcap and
> > pcap_next_ex.3pcap) mention only DLT_LINUX_SLL.
> Fixed in commit ffb99eceefd31771a4aa89f0da5d02a3c53cfd03.
Thanks a lot!
BTW how about DLT_LINUX_SLL2 as the default? What does it bloc
--- Begin Message ---
Hi Francois,
> > The "-y" flag to tcpdump allows you to specify capturing with
> > DLT_LINUX_SLL2.
> Should DLT_LINUX_SLL2 be now the default when tcpdump is built with a libpcap
> that support it ?
I'd be glad if it was so, but not sure if first wireshark needs to support
--- Begin Message ---
Hi Bill,
> The "-y" flag to tcpdump allows you to specify capturing with
> DLT_LINUX_SLL2.
Thanks a lot!
Kind regards,
Petr
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandel
--- Begin Message ---
Hi Guy,
some time ago we did together DLT_LINUX_SLL2 support for libpcap.
I don't remember the details, but IMHO it was enabled by default.
When now I compile libpcap and tcpdump, it's still using DLT_LINUX_SLL:
tcpdump: listening on any, link-type LINUX_SLL (Linux cooked v1
