Networking Forums

Networking Forums > Computer Networking > Linux Networking > Modem hardware handshake requirements of mgetty ?

Reply
Thread Tools Display Modes

Modem hardware handshake requirements of mgetty ?

 
 
pweichel
Guest
Posts: n/a

 
      09-07-2005, 10:52 AM
Hi all,

Can anyone tell me if the mgetty program sets specific requirements for
the available hardware handshake signals ?

I have a system with a serial port only offering RxD, TxD, RTS and CTS
will that be enough to use a modem configured for auto reply on a
dial-up line ?

Want to use mgetty + pppd to enable PPP over modem connection.

Will it even work using a NULL-modem cable ?

Thanks in advance.

Peter

 
Reply With Quote
 
 
 
 
Clifford Kite
Guest
Posts: n/a

 
      09-09-2005, 05:41 PM
pweichel <(E-Mail Removed)> wrote:
> Hi all,


> Can anyone tell me if the mgetty program sets specific requirements for
> the available hardware handshake signals ?


The mgetty info documentation doesn't explicitly specify requirements
for the serial device. But by default it uses RTS/CTS flow-control.

> I have a system with a serial port only offering RxD, TxD, RTS and CTS
> will that be enough to use a modem configured for auto reply on a
> dial-up line ?


No DCD, DSR, or DTR ? I doubt it, and even if it could be made to
work then I'd expect configuring everything to make it do so would
be a challenge.

> Want to use mgetty + pppd to enable PPP over modem connection.


> Will it even work using a NULL-modem cable ?


A 3-wire null-modem cable would, but then XON/XOFF flow-control would
be needed. A full null-modem cable would also work with a serial
device that has everything except DCD. It might also work using
RTS/CTS for a serial device without DCD and DSR/DTR, but can't be
absolutely sure - I've never heard of such a device.

If you have a full-up null-modem cable connected to, say, host1 and
host2 then it would be easy to determine if RTS/CTS would work with
your serial device:

host1 pppd configuration:
/usr/sbin/pppd /dev/ttySx connect 'chat "" RING\\d' \
debug crtscts local 115200 192.168.1.1:192.168.1.2
host2 pppd configuration:
/usr/sbin/pppd /dev/ttySy connect 'chat -t 0 RING \\c' \
debug crtscts local 115200

The "local" tells pppd on each host to ignore DCD since there is no
modem and so no data carrier. The 'chat "" RING\\d' shown for host1
tells chat to send a RING immediately followed by a one-second delay,
and then exit. The local IP address of host1 will be 192.168.1.1 and
the IP address of host2 will be 192.168.1.2. The 'chat -t 0 RING \\c'
for host2 tells chat to wait for RING, send nothing, and then exit.
The command for host2 should be executed first.

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
 
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
min. hardware requirements for a DHCP managing 300 thousand IP add Yushan Windows Networking 1 10-25-2005 12:25 PM
Any benchmarks of cable modem hardware ? Tom Betters Broadband Hardware 8 10-23-2004 08:52 PM
Problems with mgetty/pppd and more than one modem draoi Linux Networking 0 04-02-2004 03:33 PM
Wireless Range & hardware Requirements Ian Wireless Internet 2 10-27-2003 12:30 PM
Re: Hardware requirements to feed multiple IPSec connections Natanael Mignon Linux Networking 0 06-23-2003 08:31 PM



1 2 3 4 5 6 7 8 9 10 11