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"