Well then I'll probably never see an issue if it is indeed client related until I move the router.  Right now the router is in client bridged on the 5ghz and an ap on the 2.4.  I intend to swap my 1900acs (currently main router) and the 3200acm  but wanted to make sure it was stable first since I travel for my job and don't want to cause issues for the rest of the family when I'm gone (which is 99% of the time).  I had planned to use one 5ghz radio for the bridge and the other for an AP to improve performance.

I'm on r5201 with 9308 for 19 hours zero issues only messages in the logs are for when i authenticate to it.

We have a house full of samsung galaxy phones.

Hey, not too sure if this is the right place to post this but here goes :

I'm having some trouble getting PPTP NAT Traversal working on the most recent build for the Linksys 1900ACS.

I am running Lede Reboot SNAPSHOT r5113-2af10c30fe / LuCI Master (git-17.291.51172-a98548e)

I have the following packages installed which I think may be useful / needed :

kmod-ipt-nat - 4.9.57-1
kmod-nf-nat - 4.9.57-1
kmod-nf-nathelper-extra - 4.9.57-1
kmod-gre - 4.9.57-1
kmod-gre6 - 4.9.57-1
ip6tables - 1.6.1-1
kmod-ip6-tunnel - 4.9.57-1
kmod-ip6tables - 4.9.57-1
libip6tc - 1.6.1-1
kmod-iptunnel6 - 4.9.57-1

I've also modified /etc/config/firewall to look like this (the rest is default):

config rule
        option src 'wan'
        option dest 'lan'
        option proto 'tcpudp'
        option dest_port '1723'
        option target 'ACCEPT'
        option name 'Allow traffic on port 1723 (PPtP)'

config rule
        option src 'wan'
        option dest 'lan'
        option proto 'gre'
        option target 'ACCEPT'
        option name 'Forward GRE Traffic'

And when attempting to connect here's the log:

2017-10-29 16:33:19 State changed to: Contacting (before: Disconnected)
2017-10-29 16:33:19 publish_entry SCDSet() failed: Success!
2017-10-29 16:33:19 publish_entry SCDSet() failed: Success!
2017-10-29 16:33:20 
2017-10-29 16:33:20 PPTP connecting to server 'de233.vpnbook.com' (178.162.193.233)...
2017-10-29 16:33:20 State changed to: Contacting (before: Contacting)
2017-10-29 16:33:20 PPTP connection established.
2017-10-29 16:33:20 PPTP set port-mapping for en0, interface: 4, protocol: 0, privatePort: 0
2017-10-29 16:33:20 Using interface ppp0
2017-10-29 16:33:20 Connect: ppp0 <--> socket[34:17]
2017-10-29 16:33:20 PPTP error when reading socket : EOF
2017-10-29 16:33:20 PPTP error when reading header : read -1, expected 12 bytes
2017-10-29 16:33:20 PPTP hangup
2017-10-29 16:33:20 Connection terminated.
2017-10-29 16:33:20 PPTP clearing port-mapping for en0
2017-10-29 16:33:20 PPTP disconnecting...
2017-10-29 16:33:20 PPTP disconnected

Any help would be great

It might be but is hard to say entirely, if it is caused by a certain wifi client that causes a malfunction in the wifi driver/firmware then it is a Marvell issue and sadly at this point they don't have any desire or intention of fixing it.

I have two laptops both with 5Ghz radios (one is compatible with 20/40 Mhz and other is compatible with 20/40/80Mhz), two kindles, two echodots, roku stick, and one amazon fire tablet, I have had issues using latest LEDE wifi code with latest wifi firmware however using older build without LEDE updated wifi code using newest firmware results in over 7days of solid uptime for all devices and router.

I believe there is more to this than just a WiFi driver problem, I feel it may also result in LEDE trunk coding being unstable for WiFi fixes for the krack fix.

EDIT: Keep in mind for those that do or don't have problems with the newest Marvell Firmware 9.3.8 for 88W8964 that not everyone is using the same kind of devices or type of setup. In my current setup I only presently have one router (future plans of deploying solo APs and having a edge router),

(Last edited by rs.se on 30 Oct 2017, 03:14)

My 3200acm rebooted earlier today while it was streaming my Slingbox externally.  There is still something amiss with LEDE.

drat and double drat....  How long was it up?  I'm at 29 hours and still no issues but using 9308

It's a bit offtopic, but why you don't use OpenVPN server already in David's firmware?

I use PPtP before, but now (after some week in China) switch to SSH tunneling - it's even more easy, then OpenVPN or PPtP, and the only way to bypass their firewall.

Uptime of nearly 24 hours on r5201 without any issues... However, the problem we've been experiencing on the 3200acm may take 2 days or longer to manifest itself.

If by tonight there are still no issues, I'll go ahead and upload all the packages to the server so everyone can start downloading.

One change I made on this end was with the mwlwifi marked version... I've gone back to identifying the version as 20170810 instead of the date of the last commit. It appeared to only create confusion with the rest of the group trying to troubleshoot the current issue.

Thanks,

No idea as I was too busy doing things to keep track of it.  I suspect around 24 hours unless I missed a reboot during the overnight.

Regarding the WRT3200ACM reboot issues: running r4970 with 9.3.0.8 firmware (and without the KRACK patches):

uptime
16:37:06 up 16 days, 23:50,  load average: 0.44, 0.54, 0.53

nitroshift

PS. It would be interesting to see if there is any other hardware behaving the same or it's Linksys related.

Also worth considering is something may be wrong with my router, although it stayed up several days on DD-WRT.

The issue seems to have gone silent over the past 4 days on mwlwifi / kaloz's github -->  https://github.com/kaloz/mwlwifi/issues/225

Usually, the regular group of people are very vocal, so to not hear anything for 4 days it a bit alarming.

Or people have just given up on trying to get anything dun as there is no work being dun there, or if there is no body is saying anything about it! I have asked over and over again what's going on and no ancer. I don't expect mutch I just asked what he was working on or if he was still working on the driver. :-( I would be happy if he had told me to get lost as I dont get payed for doing this shit! :-D

(Last edited by tapper on 30 Oct 2017, 21:22)

Yeah, I would but It's for a work VPN which I don't really have control over

Okay, I've uploaded  r5201 to the server, and the images are ready for download.

The driver # has been reverted back to 20170810 as it causes less confusion during troubleshooting.
There is a commit "mwlwifi: switch to AutoProbe", though I can't say I really understand what it does as compared to before.

As usual, please let me know if you run into issues... I'm also interested in hearing from 3200acm owners about the current wifi issue.

Currently I have 1 day 8 hours on r5201, but doesn't really mean anything as it can take a couple of days or longer for the problem to manifest on the 3200acm.

*EDIT*

I did add extra options to the .conf for busybox, so there is a command "history" for shell. This improvement will be in the next build though.

(Last edited by davidc502 on 30 Oct 2017, 23:42)

I am going to try it on WRT3200ACM, but in the case of problems, what the best way to return to my current r4901 build, which was flawless for me? just re-flash previous build?

In LuCi Gui, go to -> System -> Advanced Reboot -> and click  Reboot to Alternative Partition.

I'm up 2 days 4 hours on 5201 with 9308 still no issues

about 3 days uptime on r5113 and again reboot on my WRT3200. But it was very fast, I only noticed this morning..
Will try next build from David and report later

I've got r5201 up and running for approximately 11h 34m on my WRT3200ACM.  So far, zero issues and everything on the network is running as expected. I will share any details if/when any issues occur.

Previously, I was running the latest LEDE Stable build for several weeks on my WRT3200ACM and did not experience any issues on stable branch either.

I've also been running r5201 for about 11h37m and so far it is stable, but we'll wait and see.

My previous build was r4901 with an updated wpad-mini for KRACK mitigation.  I was avoiding more recent builds because of issues I had with wireless clients unable to authenticate after a few days of uptime.  I am trying out r5201 because I started experiencing crashes (following a series of MEMAddrAccess timeouts in the kernnel log) after updating wpad-mini.  I'm curious to see if that issue goes away in the r5201 build.  It normally took a day or two to happen.

But so far so good.

Crossing fingers and knocking wood... Uptime of a little more than 2 days and good thus far.

root@lede:~# uptime
10:22:29 up 2 days,  1:27,  load average: 0.07, 0.01, 0.00

Back on DD-WRT here and up 14 hours so far.  I will try your r5201 when I get a chance.

HI :-)
Looking good!
Lede Reboot SNAPSHOT r5201-8b9cdebc9c / LuCI Master (git-17.301.46085-f907696)
Uptime
17h 57m 56s
I have a verry hi traffic net work with throughput of over 200 GB per day.

WRT3200ACM - 17hrs and counting............

That much Wifi traffic would be great to hear????