All of lore.kernel.org
 help / color / mirror / Atom feed
* Null X.25 cable?
@ 2004-05-14  8:22 un@roo
  2004-05-14 13:30 ` Steve Schefter
  0 siblings, 1 reply; 4+ messages in thread
From: un@roo @ 2004-05-14  8:22 UTC (permalink / raw)
  To: linux-x25

Hello linux-x25,

  Hello All!

  Is there any way to connect two X.25 card directly via cable (may be
  NULL MODEM)?
  If yes, what configuration of connectors it must have?
  Will two cards (configured as DTE) work together?

  If anyone knows, please help!
  
  

-- 
Best regards,
 un                          mailto:un@rootelecom.ru


^ permalink raw reply	[flat|nested] 4+ messages in thread
* Re: Null X.25 cable?
@ 2004-05-15 19:46 TProvoni
  0 siblings, 0 replies; 4+ messages in thread
From: TProvoni @ 2004-05-15 19:46 UTC (permalink / raw)
  To: steve, un, linux-x25

Wanware hardware sounds somewhat restrictive in its clock
configurations.  I have worked with several vendors' equipment that
allows symmetric independent clocking.  Transmit clocks are sent from
both sides and the receivers extract the clocks as they receive data.
Of course, even in symmetric clocking setups, one side must be the
logical or protocol DCE and the other must be the logical or protocol
DTE.

Joachim Martillo 

BTW, some specifications provide a third sense of DTE
and DCE in terms of connector definition.

Thus it is possible to use a DCE connector on the interface that is a
DTE in the clock sense and a DCE in the protocol sense.

In a message dated 5/14/04 9:25:32 AM Eastern Daylight Time, 
steve@wanware.com writes:
Hi.

>>   Is there any way to connect two X.25 card directly via cable (may be
>>   NULL MODEM)?
>>   If yes, what configuration of connectors it must have?
>>   Will two cards (configured as DTE) work together?
>> 
>>   If anyone knows, please help!
>
>The short answer is yes.
>
>But in order for this to work, there are a few things you need to
>check.
>
>First, the card must be capable of being internally clocked.  One
>side will need to be setup as internal and the other as external.
>
>Second, make sure you use a synchronous null modem cable.  The
>more common async null modem won't route the clocks properly between
>the two sides (it just crosses the data and control signals).
>You'll need to make sure that the "I" side of the null modem goes
>to the side that has the clocking set to internal.
>
>Third, there are two concepts of DTE and DCE in X.25: physical and
>logical.  The null modem will take care of the fact that you are
>connecting two physical DTEs together, but you also need to change
>the logical setting (in software) to DCE on one side.
>
>You can find the pinout for null modem cables for various electrical
>interfaces on our website under "support".
>
>There's also an application note covering this topic on our website:
>http://www.wanware.com/index.php?page=support/app_notes/mach2mach&menu=suppor
t
>
>Regards,
>    Steve

^ permalink raw reply	[flat|nested] 4+ messages in thread
[parent not found: <1a4.23eb82b5.2dd7cc89@aol.com>]

end of thread, other threads:[~2004-05-17 13:29 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-05-14  8:22 Null X.25 cable? un@roo
2004-05-14 13:30 ` Steve Schefter
  -- strict thread matches above, loose matches on Subject: below --
2004-05-15 19:46 TProvoni
     [not found] <1a4.23eb82b5.2dd7cc89@aol.com>
2004-05-17 13:29 ` Steve Schefter

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.