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).
WinPPP.htm
DigiRP.txt
LVL 1
raconeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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.
0
raconeAuthor Commented:
I've requested that this question be deleted for the following reason:

I resolved on my own...
0
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
0
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.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Duncan RoeSoftware DeveloperCommented:
Well done! Thanks for your clear explanation.
Cheers ... Duncan.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.