Opened 17 months ago
Closed 14 months ago
#2359 closed (fixed)
ppp0 interface not created when pptp client is configured
| Reported by: | mw2 | Owned by: | |
|---|---|---|---|
| Keywords: | Cc: |
Description (last modified by mw2)
the ppp0 interface never gets created when pptp client is enabled and configured with a vpn account on latest build 18024. Worked on build 17201
No logs yet but will get them this weekend. Needed to get the internet up and running for the wife so no time.
Change History (9)
comment:1 Changed 17 months ago by mw2
- Description modified (diff)
comment:2 follow-up: ↓ 4 Changed 17 months ago by Sash
comment:3 Changed 17 months ago by mw2
sorry does that mean I have to download the source and compile or is there a compiled image. apologies I am new. anyways i've started downloading the source
comment:4 in reply to: ↑ 2 Changed 17 months ago by mw2
Replying to Sash:
try the latest recomment build from the database and report back
Not sure what you mean by recomment build. Do you mean the recommended build from the database ?
comment:5 Changed 14 months ago by routvol
i have the same problem.
i am using vyprvpn on a linksys 610 router and the last version i used was DD-WRT v24-sp2 (06/14/11) mega (SVN revision 17201). i upgraded today to DD-WRT v24-sp2 (03/19/12) mega (SVN revision 18777).
root@DD-WRT:/tmp/pptpd_client# pptp uk1.giganews.com /tmp/pptpd_client/options.vpn Segmentation fault
Please let me know if you need more information.
comment:6 Changed 14 months ago by routvol
i downloaded and tried the 2.6 kernel build svn18946 from ftp://ftp.dd-wrt.com/others/eko/V24-K26/svn18946/dd-wrt.v24-18946_NEWD-2_K2.6_mega.bin.
it has the same problem.
comment:7 Changed 14 months ago by routvol
ok the resolution from this ticket solved the problem: http://svn.dd-wrt.com/ticket/2350
Tested with revision 18777.
comment:8 Changed 14 months ago by BrainSlayer
why dont you use the standard wan pptp option? this works much better than the manual pptp client page
comment:9 Changed 14 months ago by mrc_torres
- Resolution set to fixed
- Status changed from new to closed
Try the new build that is coming soon after changeset 18965.

try the latest recomment build from the database and report back