Closed Discovery00 closed 2 years ago
As looked, chap v2 support should be already included: are you sure this to be related to chap auth failure ?
Can you give some more infos related like syslog event msgs other than dmesg or any other attempts with similar different router models ?
a connection reconfig would be also recommended if isp has changed auth
Yes i tested with 3 Modems. They connected succesfully. Asus DSL-AC51U has PPP-2.4.7. Others ISP provided modem.
Negan, When I convert D7000 to Bridge mode, Asus connected succesfully with Ethernet WAN Connection.
I looked at the Tplink VR2800 GPL source codes. It has the same kernel version as the D7000. And pppd version is 2.4.5. They also added the rp-ppoe package to the PPPD package. No external rp-ppoe plugin. I am attaching the file, you can review it ppp-2.4.5.zip .
PPP Changelog
What was new in ppp-2.4.2.
2.4.1 Very Old and Has many security vulnerabilities. Such as CVE-2020-8597 --- CVE-2015-3310 --- CVE-2014-3158
these are the differences between 2.4.1 & the one included in the router source code to mantain broadcom/sercomm compatibility
they should be applied to the newer versions shadow support & plugins other than pppoe & pppoa can be omitted
I can't test the package modification directly because of different isp & connection mode so an help is needed for dsl & ptm connections
I looked at the Tplink VR2800 GPL source codes. It has the same kernel version as the D7000. And pppd version is 2.4.5. They also added the rp-ppoe package to the PPPD package. No external rp-ppoe plugin. I am attaching the file, you can review it ppp-2.4.5.zip .
Unfortunately other vendor's code cannot be used easily because code is always heavily customized for the own device netgear code seems to have 3 level of development in order:
broadcom sercomm netgear own
any of them can be different
rp-pppoe is present as another package and could also be updated like atm libs
Negan i tried to compile it (TP-Link ppp2.4.5) But failed. Maybe can be succes with your old diffs (apps/ppp2.4.1.ppoe4.orig). I will try it. PPP official website have clean source code. Can you compile for Netgear? Or can you create an ipk file? We can install it with Ancistrus opkg manager. Thanks.
Thx Negan 👍🏻 I will try it
Look at your ppp.zip. Search "blacklist" keyword in diffs. Netgear/sercomm packages sends different byte (long) athentication request. This package my nightmare...
you posted diffs 2.4.9 while i was dealing with 2.4.5 wow 👍🏻
I can work with 2.4.9. I will provide feedback
Please look at this... This is my problem.
PPP 2.4.9 doesn't work.
ppp-2.4.1-Edited.zip Negan Please Compile This :)) Edited 2.4.1
Why does netgear stay so far away from the original ppp source code? What might they be aiming at by placing these restrictions? I sent an e-mail to the Netgear software department. There must be a logical explanation. Thank you too my friend. I've been focusing on this issue for a week. I hope we can come up with a solution.
The plugin here caught my attention. It is very similar to the original codes. But I couldn't adapt the makefiles. I will send you the latest file I made. I also added multi link support.
-This link from an another developer.
ppp-2.4.1.pppoe4.zip Deleted Multioffer-Inserted Multilink but Makefile Error
I tried the files you sent, they didn't work. I found the source of the problem. The problem is related to the rp-pppoe package. If rp-pppoe is updated, the problem is solved. Netgear and TP-Link rp-pppe/pppoe.h differentiations..
Why does netgear stay so far away from the original ppp source code? What might they be aiming at by placing these restrictions? I sent an e-mail to the Netgear software department. There must be a logical explanation. Thank you too my friend. I've been focusing on this issue for a week. I hope we can come up with a solution.
there may be many reasons: security reliability isp specifications & adaptations Opening a vendor ticket is surely a good option even if it can become slow because they have some support technical levels.
Anyway I think the work made updating 2.4.9 shouldn't be thrown. Can u confirm problem to be related to pppoe/ptm connection and not chap support? Can you attach the /tmp/ppp_log diffs from vendor pppd-2.4.1-pppoe.orig and 2.4.9 if any to see if patches have been applied correctly ?
These are the rpppoe diffs (vanilla version is assumed to be 3.5 even if it should be 3.05 as the latest is 3.15) As you can see differences are few, mostly logging & casting that can be skipped
Tmp folder not contain PPP-log. I opened PPP debug but same error, 404 file not found.
My ISP says; your DSL modem sending different byte of pppoe request. As you can see in the picture I posted, Netgear is using pppoe v4. tplink uses v8 pppoe. I think the problem is caused by this. Byte lengths are the same. Now it comes to my mind that the internet service provider blocked my dsl modem. Maybe by Mac address or Serial number. Maybe ISP is using non-standard rfc2516 protocol. who knows :) Isp just says, "Change your modem"
Negan pppd changes maybe working. But it didn't work on my line. I would like to try. But isp unfortunately does not give wan ip address. The log file was not created in the modem. But I can say that the original ppp2.4.1 also had a debug log
The modem does not accept this plugin when it makes changes to the files. I saw the md5 value inside the plugin. A conflict may occur when the modification is made.
Anyway I think the work made updating 2.4.9 shouldn't be thrown. Can u confirm problem to be related to pppoe/ptm connection and not chap support? Can you attach the /tmp/ppp_log diffs from vendor pppd-2.4.1-pppoe.orig and 2.4.9 if any to see if patches have been applied correctly ?
Yes, problem related with Pppoe connection. Confirmed.
Rp-pppoe 3.15-original and rp-pppoe 3.15 with Netgear modification, both works successfully.
I will send a logs.
Negan, can you make pppd 2.4.5 without netgear modifications? No multi offer flag and other modifications.
Let's do a brief recap:
Does rp-pppoe
bumped to version 3.15 fix the connection problem ?
Have you tried rp-pppoe
updated client in conjunction with ppp-2.4.9 with or without MULTI_OFFER cflag (see above) ?
Have you tried rp-pppoe
updated client in conjunction with old ppp with or without MULTI_OFFER cflag (see above) ?
Yes i tried every combination. Rp-pppoe works flawlessly. But modem can't connect to the internet. I have got a good news for you. I found Netgear PPPD 2.4.1 without multi offer flags and etc. Pure plugin in other routers gpl. And I found 2.4.4 in Netgear China firmware gpl :)
Compile these files without modification. Original Netgear plugins.
You can send it as 2.4.1 orig and 2.4.4 orig. I will try . And we will solve this problem. 👍🏻
ppp-2.4.1-R7000-EU.zip ppp-2.4.4-R7000-CN.zip Good Luck
Hi Negan, I found a project for Netgear Dgnd4000. http://alfie.altervista.org/amod4000/ He succesfully patched pppd 2.4.7 in firmware. Maybe he will help us.
The files you provided result incompatible because they come from a different source board. At this point I think that cross-patching from different boards results in a failure approach attempt.
Are you sure that your new isp configuration matches the requirements ? Have you correctly setup vlan id tag in the connection setup ? I suggest you to rebuild setting configuration making particular attention to wan settings configuration taking care of ISP specification. The way of sending an email ticket to netgear support or better on community board support is still valid: if the problem is device-related maybe someone else with the same isp is involved.
linux-atm
ppp
rp-pppoe
packages are on the way
opkg update && opkg install linux-atm && opkg install ppp && opkg install rp-pppoe
they must be fully tested under various connection modes:
atm (adsl)
ptm (vdsl)
on their various possible configurations
The following package includes all the original wan packages and can be unzipped then manually installed to revert wan connection to original mode: wan_orig_0.0.0_armD7000.zip
Make sure to download it before updating above packages to make sure to be able to reconnect again in case of failures
Hi Negan, I will try. The device has been far from me until now. I will be traveling to home. I'll test it myself. With all kinds of conditions and combinations. Don't worry :) Thanks for everything.
Hello, I tested your Packages. All packages are working without any problems. But my problem still persists :) I'm throwing the log file. The problem is related to Netgear source codes. They are blocking PPP Remote access. Anyway PPPD 2.4.9 ported successfully. Congratulations. Good job 👍
Linux-atm 2.5.2 Tested 👍
PPPD 2.4.9 Tested 👍
RP-PPPOE 3.15 Tested 👍
If someone has an atm connection It would be nice to see if all works correctly
I haven't got an ATM connection. Only PTM.
My neighbours also have PTM :)
PPPoE is okay over WAN (ATM), if that helps.
so new packages seems to work properly on main connection types
working on your specific failure case is hard because no reproduction is possible to test it
you should try to avoid rc_wan
method and trying to configure ppp connection manually looking with ps
the parameter of ppp
cmd when invocated & trying to setup proper wan id priority
the same could be done with working router making a comparison between both procedures of connection
Hi Negan Are you here :)
any news about ppp connection ? New monolithic is about to be pushed because there are many package upgrades: if there is something about this issue could be patched before.
Hi, i have got a problem with my service provider. They changed Ericson SSG to ZTE SSG. I can't connect to the internet. ZTE SSG only supports MS-CHAP V2 and CHAP authentication. Negan, Does the D7000 support them? Please Upgrade PPP daemon in this firmware (pppd 2.4.9 is the latest one). D7000 is legendary your firmware works perfectly 👍🏻 Waiting for your support.. Thx