Guy Harris alum.mit.edu> writes:
>
> Maria Cruz wrote:
>
> > DLT_IEEE802_16_MAC_CPS is fine. Thanks. Will you also assign a value?
>
> Yes - that's what this process is all about. I've assigned the value 188.
>
I wanted to mention 802.16 has a fixed and a mobile version. I do not think
t
Maria Cruz wrote:
DLT_IEEE802_16_MAC_CPS is fine. Thanks. Will you also assign a value?
Yes - that's what this process is all about. I've assigned the value 188.
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.
Guy Harris alum.mit.edu> writes:
>
> I.e., you'll be capturing at the line between "MAC Common Part Sublayer"
> and "Security Sublayer" (where there's no SAP, but that doesn't mean you
> can't capture there), and the packet data in the capture will have each
> packet start with a "Generic MAC
Guy Harris alum.mit.edu> writes:
>
> Maria Cruz wrote:
> > Hi, if a new protocol is introduced to libpcap is it necessary to
> > update 'gencode.c' for parsing?
>
> You would have to add a case to the switch statement in init_linktype().
>
> At minimum, it'd have to do
>
> /*
>
Maria Cruz wrote:
Hi, if a new protocol is introduced to libpcap is it necessary to
update 'gencode.c' for parsing?
You would have to add a case to the switch statement in init_linktype().
At minimum, it'd have to do
/*
* Currently, only raw "link[N:M]" filtering is supporte
Hi, if a new protocol is introduced to libpcap is it necessary to
update 'gencode.c' for parsing? I would like libpcap to read the packet 'raw'
and pass on. I plan on using Ethereal to dissect/analyze.
thanks
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe
