Hallo
We have a linux server with dial-ups, using mgetty on the server side. They
are working 100%.
Then we have a direct line connection with a modem on each side using the
scripts above to connect via ppp ("go.ttyC4.server" and "go.ttyS1.client" on
the server and client side respectively). As can be seen from the logs, each
side is rejecting the suggested ip-no. of the other side. However, doing a
similar connection via a dialup using mgetty on the server side, the same
ip-no's are accepted and the hand-shaking completed. The options file on the
client side I have renamed as options.client for clarity. There is nothing
in the options file on the server side.
I've tried various other configurations, even making the ppp options on both
sides as close as possible to the dial-up-mgetty connections - but always
with exactly the same rejection of ip-no's.
The only differences between the two type of connections are as follows (as
far as I can see):
- client side: Connecting via ATD (direct line) in stead of actually
dialling the server (ATDT$PHONE)
- server side:
1) Answering via ATA (direct line) in stead of answering via mgetty (which
requires at least 1 ring - so a direct connection is not possible, or am I
wrong).
2) Using the chat sequence of the script (go.ttyC4.server) in stead of the
default chat sequence of the server if mgetty does the answering.
Point two seems to me to be the problem - but how can I simulate the default
chat sequence, if I must start chat to be able to set the modem into ATA
mode.
Also, as mentioned above, is it not possible to simulate a ring over the
direct line, so that mgetty will pick up (or use some special options for
mgetty so that it will be activated when the modem on the other side sends
the first packet - this will also solve my problem, as my mgetty-dial-ups
are working fine)
Could you please help me to solve this problem.
Regards,
Andries
options.client
go.ttyC4.server
go.ttyS1.client
clientlog
options.ttyC4
serverlog
