Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 513
  • Last Modified:

Linux LCP terminated by peer

We use RHEL 5 and Digi PortServers with the RealPort Driver.

With a new version of the Digi RealPort Linux driver, the PPP connections are failing.

It says:

LCP terminated by peer (RM-V3M-s^@<M-Mt^@^@^@^@)

I can roll the RealPort driver version back and it works again.

Everything else generally works with the new driver version.

Digi did change the files in the /dev folder to be symbolic links on the new version.  Certainly a difference.

Digi is not much help.

I'm stuck on a older driver version as a result.

Very strange.  It's wierd that a nre version of the driver would manifest into this.

Not sure if I can tweak the Linux PPP settings to overcome.

The PPP version says:  pppd 2.4.4 started by root, uid 0

Attached Linux log information, and Windows (Win 7) PPP connection log (use latest 8-21 PPP log info).
  • 3
  • 2
1 Solution
Duncan RoeSoftware DeveloperCommented:
Make sure PPP is logging everything, then post the log. It would help a lot if you could post a successful log from the older driver as well.
raconeAuthor Commented:
I've requested that this question be deleted for the following reason:

I resolved on my own...
Duncan RoeSoftware DeveloperCommented:
Since you resolved it on your own, please post what was the resolution as it may be useful to others. Then you can accept your solution (zero points) to close the question
raconeAuthor Commented:
The resolution was as follows:

Starting with the version 1.9-30 of the Digi Linux RealPort driver, Digi decided to use symbolic links for device files in the /dev directory.  Earlier versions used a single normal device file name for the tty devices.  The stock Red Hat Linux PPP daemon does not like the symbolic link device names for some reason.  I reverted to the udev file used on earlier version of the RealPort driver that made actual normal device names, and all was working properly after that.
Duncan RoeSoftware DeveloperCommented:
Well done! Thanks for your clear explanation.
Cheers ... Duncan.

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now