lkml.org 
[lkml]   [2001]   [Mar]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: RFC: configuring net interfaces
Krzysztof Halasa <khc@intrepid.pm.waw.pl> écrit :
[...]
> That's a physical interface like V.35 or RS232.

Ok.

[...]
> > * n200, t200 ?
>
> What's that?

Parameters for retransmission of a trame specified in Q922. t200 is the
timeout value and n200 the maximal number of retransmissions. They can
be negocied and default to t200=1,5s, n200=3.

> > Do we put the crc type here ?
>
> I don't think so. Frame Relay uses only standard CRC. Correct me if I'm
> wrong.

Ok.

[...]
> > While we're here, could we agree on the notion of raw hdlc, i.e. :
> > - no address, no command. crc present (ARPHRD_RAWHDLC ?);
> > - no address, no command, no crc (ARPHRD_PATHOLOGICHDLC ?).
>
> Do we really need another ARPHRD for that?
> BTW: What protocol(s) use such CRC-less HDLC?

No protocol I know. Sometime one just want to verify how a driver performs
when he receives badly fscked data. One can live without it.

--
Ueimor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:18    [W:0.088 / U:5.572 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site