Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PPPd crashes with fatal signal 6 on 2.4.7 version #495

Open
Arsalan19 opened this issue May 24, 2024 · 2 comments
Open

PPPd crashes with fatal signal 6 on 2.4.7 version #495

Arsalan19 opened this issue May 24, 2024 · 2 comments

Comments

@Arsalan19
Copy link

PPPd crashes with fatal signal 6 on 2.4.7 version soon after receiving a CHAP challenge request from the server.
Corefile is not generated as this is packaged on a cisco device. Issue is only seen when using CHAP authentication.

pppd[4459]: Fatal signal 6

@paulusmack
Copy link
Collaborator

Version 2.4.7 is nearly 10 years old, and if this is packaged on a cisco device then the source may have been modified by Cisco.

If you can reproduce with the current source or with unmodified version 2.5.0, then we can take a look at it, otherwise we will need to reject this issue.

@Arsalan19
Copy link
Author

Cisco is using unmodified 2.4.7 code base. This is packaged on cisco sdwan device. The server used here is Mikrotik router and the cisco device is the ppp client. On disabling the mschap1 and mschap2 authentication and having just PAP and CHAP authentication enabled on the Mikrotik router (PPP server) resolves the issue and pppoe session is being formed with the server. On re-enabling the mschap1 and mschap2 also resolves the issue. I'm not sure if the issue is with the server or the client. im not aware of the pppd version used on the server. Could this be an inter-operability issue? Can you suggest how i can debug this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants