On Sun, 19 Nov 2017, in the Usenet newsgroup comp.protocols.ppp, in article <
fa1ebc1a-2d3e-451a-b474-2a2107ac07e0@googlegroups.com>,
xieblueone@gmail.com wrote:
NOTE: Posting from groups.google.com (or some web-forums) dramatically
reduces the chance of your post being seen. Find a real news server.
I try to run
pppd proxyarp mtu 1280 persist nodeflate noauth lcp-echo-interval 10
crtscts lock 10.10.1.2:10.10.1.1 /dev/ttyS4 115200 debug nodetach
in my system
What are you trying to do? Connect to an ISP? Connect a serial
link to another computer? What operating system? You show
"/dev/ttyS4" which in Linux would be the fifth (very uncommon) classic
RS-232 serial port. Assuming Linux, what does 'ls' show?
[spica ~]$ ls /dev/ttyS*
/dev/ttyS0 /dev/ttyS1 /dev/ttyS2 /dev/ttyS3
[spica ~]$
During boot, is your kernel loading an appropriate serial driver?
In /var/log/dmesg, I see
[ 0.518034] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 0.538368] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Notice the second line - on this computer, there is an actual RS-232
serial port. On two other computers here, the line is missing
because there is no classic serial port (everything is USB, which is
a different device and driver).
and it sending the same thing over and over
sent [LCP ConfReq id=3D0x1 <asyncmap
<magic 0x8bab12d4> <pcomp> <accomp>]
"Hello! Is anyone out there?"
The peer at the other end of the serial link is not responding.
Is your connection to the peer (modem, cross-over cable or similar)
connected? Is there a pppd daemon listening on the appropriate port
on the peer? More details needed.
Old guy
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)