On Jul 23, 2009, at 9:45 AM, kahou lei wrote:
We will put EOF as well.
The decoding is correct, we have 4 bytes SOF, first byte is 0xBC ,
second
byte is 0xB5 and so on.
OK, I've assigned 225 as DLT_FC_2_WITH_FRAME_DELIMS.
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/
We will put EOF as well.
The decoding is correct, we have 4 bytes SOF, first byte is 0xBC , second
byte is 0xB5 and so on.
Thanks,
Kahou
On Thu, Jul 23, 2009 at 2:06 AM, Guy Harris wrote:
>
> On Jul 23, 2009, at 12:03 AM, Guy Harris wrote:
>
>
>> On Jul 22, 2009, at 1:36 PM, kahou lei wrote:
>
On Jul 23, 2009, at 12:03 AM, Guy Harris wrote:
On Jul 22, 2009, at 1:36 PM, kahou lei wrote:
We are currently supporting:
SOFi2 - BCB5
...
Also, does, for example, BCB5 mean that the 4 bytes in the SOF
are, in order, 0xBC 0xB5 0x55 0x55, so that the first byte of packe
Hi Guy,
On Tue, Jul 21, 2009 at 01:21:59PM -0700, Guy Harris wrote:
> The response I sent on November 27, 2008 was:
>
> >On Nov 26, 2008, at 8:51 PM, Harald Welte wrote:
> >
> >>please make that LINKTYPE_GSMTAP_UM and LINKTYPE_GSMTAP_ABIS in
> >>order to
> >>indicate that all messages will be pre
On Jul 22, 2009, at 1:36 PM, kahou lei wrote:
It is not base on RFC 3643. We are following the standard from
http://www.t11.org .
You can find the draft in Fibre Channel (FC) -> FC-FS-3 Fibre
Channel -
Framing and Signaling - 3INCITS Project 1861-D.
Basically, we are following Table 4 Vali