I will give this one a try later tonight when things are quite. _________________ ISP: Charter
Modem: Netgear CM600
Router:(2) Asus RT-AC86U Merlin 384.5
Router: LinksysWRT3200Acm{RIP}
Router: Linksys EA8500 kongat r35030m (Vpn)
Router: Netgear X4S kongat r35965M
Vpn: IpVanish
Unbrick your 3200acm with usb to ttl cable: https://tinyurl.com/y9azvrkg
I’ve been watching the timeline page. Seems like BS and kong are plugging up holes and bug fixes as fast as they can. Something is fixed, which breaks something else.
I’m happy with my build from 3/26/18.
I dont use a lot of crazy features.
i do need ntp for vpn.
And i need policy based routing
Things i still want are
Mu-mimo which is being worked on now at marvell.
And i wish BS or kong would work on a fix for SFE and policy based routing as this does not work.
Waiting game...
802.11ax will be out soon enough... we get to start this whole dance all over again. _________________ WRT3200ACM V1 r39267 std (03/22/19) OpenVPN client
General post -- I normally install all builds but have stayed back based on the forum -- THANK YOU! I would still normally try but I'm recovering from an accident (truck hit me on my bicycle) and dont want to mess around too much recovering - thankful to be alive!
Anyway for ref info below. I did just notice it seems like my access restrictions aren't working in build r35681 (I block internet on 20 sec cameras but now see them opening udp which they didnt used to).
So staying here a bit .. thank you for the forum community!
Joined: 13 Jun 2006 Posts: 1608 Location: SE Michigan USA
Posted: Fri Apr 27, 2018 14:05 Post subject:
derWolfMan wrote:
I would still normally try but I'm recovering from an accident (truck hit me on my bicycle) and dont want to mess around too much recovering - thankful to be alive!
Hope you heal fast.
My wife and I used to ride bikes when younger. Go on long rides and also around town. That was always one of our fears. Did have a few close calls from idiot drivers. Get off of my road seemed to be their attitude. They are trying a man right now near us that was DUI and plowed into a group of bikers killing 5. He is up on 5 counts of 2nd degree murder. Not sure where you live so you might be aware of this. _________________ Unifi Security Gateway:Unifi Firmware Netgear r7800:Voxel Firmware Modem:Netgear CM500V voice and Data. ISP:Comcast tutorial for flashing "WRT" series: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=287813 DD-WRT Installation, Upgrade & Basic Setup–Cliff Notes: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=311117 Kong DD-WRT Config Tutorial: http://www.instructables.com/id/Install-and-Configure-a-DD-WRT-Kong-Router/ I tried to be normal once. Worst 2 minutes ever.
I would still normally try but I'm recovering from an accident (truck hit me on my bicycle) and dont want to mess around too much recovering - thankful to be alive!
Hope you heal fast.
My wife and I used to ride bikes when younger. Go on long rides and also around town. That was always one of our fears. Did have a few close calls from idiot drivers. Get off of my road seemed to be their attitude. They are trying a man right now near us that was DUI and plowed into a group of bikers killing 5. He is up on 5 counts of 2nd degree murder. Not sure where you live so you might be aware of this.
Thank you for the positive thoughts. I have been bike commuting about 12 years now, mostly on this route. The guy pulled right into me while I was in the bike lane trying to turn out. I always look at the drivers to be sure it at least 'looks' like the see me ... anyway I am fortunate and will be OK. Cracked ribs, bruises, cuts, worst was a ripped bicep tendon I just had surgery to fix yesterday (pain meds!). This one handed typing is a pain. I don't think though I could give up the benefit of exercise on my commute .. this is actually a pretty safe route. I'll be using the trail more though where I can.
I did hear about that tragedy, very sad. It is dangerous especially with DUI and DUI-Devices.
We have a pretty good trail system by me (Redmond/Seattle WA) which is the only place I've ridden with my wife and kids.
Take care, thanks again for the positive energy! It helps!
General post -- I normally install all builds but have stayed back based on the forum -- THANK YOU! I would still normally try but I'm recovering from an accident (truck hit me on my bicycle) and dont want to mess around too much recovering - thankful to be alive!
I hope you recover quickly. I was in a serious car accident 12 years ago that left me in a coma with a Traumatic Brain Injury, five metal plates holding my skull together, a six month hospital stay and a million dollars in medical bills. And I was the lucky one, my good friend and colleague died. I know recoveries can be hard. Best wishes. _________________ FIRMWARE: 6-20-2018 - r36168
MODEM: ARRIS SURFBoard SB6183
ROUTER: Linksys WRT1900ACS V2
ISP: TWC Spectrum 100 Mbps Download | 10 Mbps Upload
SERVICES: IVPN OpenVPN Client
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Fri Apr 27, 2018 22:32 Post subject: r35831 no internet
Installed r35831 on 2 x wrt1900AC and 1 x wrt1200AC.
I use one 1900 as a master with Internet connection and DHCP. For some reason I was unable to get a Internet connection. Light remained orange even though status page indicated a connection. Also I was unable to connect to Internet. Reverted back to an operational build. Still running r35831 on the other routers without problem.
Guys, seriously...do not rely on the built in/default NTP configuration. There is no RTC, so there is no inherent saved state. It can be kludged (ala raspberry pi and other non-rtc devices - where a flat file is written at shutdown/reboot with the current time), but it's not on dd-wrt for valid reasons.
The default ntp behaviour in dd-wrt is an initial ntp sync, then one more some set time later (3600 seconds,I don't remember), and that's it. So time WILL ALWAYS DRIFT. Always. Until you reboot, and it resyncs. Each system will drift different, as it's a software clock, and the default ntp set up is NOT using a ntpd, so it's not constantly syncing. Just the initial 2 times.
You will greatly improve your VPN stability, and reduce your ntp issues by adding the following or something similar to your additional cron jobs:
*/10 * * * * root ntpclient us.pool.ntp.org
That runs a cron job every 10 minutes that updates the software clock on the router. No load, no issues, simple, and it will prevent significant drift. Personally, I'd like to see a true ntpd package installed, with open ntp servers, but that's just me.
Of course, this assumes that the ntpclient piece itself isn't borked. I am getting ready to install this new firmware myself, and I will test and verify.
As always, this is my opinion, YMMV, and anybody with a better solution is welcome to chime in.
Dude, as a fellow cyclist.........best wishes and hope you are up and about and back on the bike soonest!
Damn cagers.........
derWolfMan wrote:
General post -- I normally install all builds but have stayed back based on the forum -- THANK YOU! I would still normally try but I'm recovering from an accident (truck hit me on my bicycle) and dont want to mess around too much recovering - thankful to be alive!
Anyway for ref info below. I did just notice it seems like my access restrictions aren't working in build r35681 (I block internet on 20 sec cameras but now see them opening udp which they didnt used to).
So staying here a bit .. thank you for the forum community!
Installed on 3x3200, 1 1900acsv2, 1 1200acv2. All up and running. Not seeing any errors yet. We'll see how it runs over the weekend, and Monday when I VPN into work.
No issue with running ntpclient out of cron, all routers synced up with correct time.
Apr 28 11:40:00 base daemon.debug ntpclient[2919]: Connecting to pool.ntp.org [178.33.111.49] ...
Apr 28 11:40:00 base daemon.info ntpclient[2919]: Time set from pool.ntp.org [178.33.111.49].
Apr 28 11:50:00 base daemon.debug ntpclient[2966]: Connecting to pool.ntp.org [194.54.80.28] ...
Apr 28 11:50:00 base daemon.info ntpclient[2966]: Time set from pool.ntp.org [194.54.80.28].
Apr 28 12:00:00 base daemon.debug ntpclient[3008]: Connecting to pool.ntp.org [85.10.240.253] ...
Apr 28 12:00:00 base daemon.info ntpclient[3008]: Time set from pool.ntp.org [85.10.240.253].
Apr 28 12:00:28 base daemon.debug ntpclient[3021]: Connecting to 2.pool.ntp.org [212.129.9.36] ...
Apr 28 12:00:29 base daemon.info ntpclient[3021]: Time set from 2.pool.ntp.org [212.129.9.36].
Apr 28 12:00:29 base daemon.info process_monitor[2089]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Apr 28 12:10:00 base daemon.debug ntpclient[3067]: Connecting to pool.ntp.org [192.111.144.114] ...
Apr 28 12:10:01 base daemon.info ntpclient[3067]: Time set from pool.ntp.org [192.111.144.114].
Apr 28 12:20:00 base daemon.debug ntpclient[3119]: Connecting to pool.ntp.org [173.249.38.50] ...
Apr 28 12:20:00 base daemon.info ntpclient[3119]: Time set from pool.ntp.org [173.249.38.50].
I'm quite aware of the relationship between vpn and time sync, lol. I've been a nix engineer for about 25 years now. I may have had some experience with ntp my friend, hahaha. If you post your log output from running ntpclient, both using IP, and using DNS alias, I will gladly help you figure out what's broken.
If you are getting an error using ntpclient, I would look to your DNS configuration. You can troubleshoot by using an IP instead of the dns name. It's handily provided for you above in my log snippet, replace pool.ntp.org with 173.249.38.50 and run from ntpclient from cli or within gui in command area.
d0ug wrote:
ericb wrote:
Guys, seriously...do not rely on the built in/default NTP configuration. There is no RTC, so there is no inherent saved state. It can be kludged (ala raspberry pi and other non-rtc devices - where a flat file is written at shutdown/reboot with the current time), but it's not on dd-wrt for valid reasons.
The default ntp behaviour in dd-wrt is an initial ntp sync, then one more some set time later (3600 seconds,I don't remember), and that's it. So time WILL ALWAYS DRIFT. Always. Until you reboot, and it resyncs. Each system will drift different, as it's a software clock, and the default ntp set up is NOT using a ntpd, so it's not constantly syncing. Just the initial 2 times.
You will greatly improve your VPN stability, and reduce your ntp issues by adding the following or something similar to your additional cron jobs:
*/10 * * * * root ntpclient us.pool.ntp.org
That runs a cron job every 10 minutes that updates the software clock on the router. No load, no issues, simple, and it will prevent significant drift. Personally, I'd like to see a true ntpd package installed, with open ntp servers, but that's just me.
Of course, this assumes that the ntpclient piece itself isn't borked. I am getting ready to install this new firmware myself, and I will test and verify.
As always, this is my opinion, YMMV, and anybody with a better solution is welcome to chime in.
The problem is the NTP client doesn't work period in this build. I also have a cronjob like the above to keep my clock in sync. Booting this build it doesn't sync at boot, nor running the ntpclient from the command line.
It is well known that there is no RTC in these routers, but users of VPNs like myself have to have a clock that is in sync or else the router cannot connect to a VPN server or act as a VPN server. If the time difference between the server and client is too far off the OpenVPN encryption will not authenticate. Since these things boot up at Epoch time until a time sync is done that means VPN is useless without NTP, unless you want to go to the command line and manually set the date and time every time your router reboots.
Joined: 13 Jun 2006 Posts: 1608 Location: SE Michigan USA
Posted: Sat Apr 28, 2018 17:51 Post subject:
ericb wrote:
Guys, seriously...do not rely on the built in/default NTP configuration. There is no RTC, so there is no inherent saved state. It can be kludged (ala raspberry pi and other non-rtc devices - where a flat file is written at shutdown/reboot with the current time), but it's not on dd-wrt for valid reasons.
The default ntp behaviour in dd-wrt is an initial ntp sync, then one more some set time later (3600 seconds,I don't remember), and that's it. So time WILL ALWAYS DRIFT. Always. Until you reboot, and it resyncs. Each system will drift different, as it's a software clock, and the default ntp set up is NOT using a ntpd, so it's not constantly syncing. Just the initial 2 times.
You will greatly improve your VPN stability, and reduce your ntp issues by adding the following or something similar to your additional cron jobs:
*/10 * * * * root ntpclient us.pool.ntp.org
That runs a cron job every 10 minutes that updates the software clock on the router. No load, no issues, simple, and it will prevent significant drift. Personally, I'd like to see a true ntpd package installed, with open ntp servers, but that's just me.
Of course, this assumes that the ntpclient piece itself isn't borked. I am getting ready to install this new firmware myself, and I will test and verify.
As always, this is my opinion, YMMV, and anybody with a better solution is welcome to chime in.
Interesting. Running this same build, r35831, on a Netgear r8000 and NTP works. Updates every hour. Since I do not do VPN if it is off some don't care. Something different about the WRT builds obviously.
From R8000 dd-wrt log
Apr 28 04:16:29 wallaby daemon.debug ntpclient[2560]: Connecting to pool.ntp.org [108.59.2.24] ...
Apr 28 04:16:29 wallaby daemon.info ntpclient[2560]: Time set from pool.ntp.org [108.59.2.24].
Apr 28 04:16:29 wallaby daemon.info process_monitor[1157]: cyclic NTP Update success (servers pool.ntp.org)
Apr 28 05:16:29 wallaby daemon.debug ntpclient[2748]: Connecting to pool.ntp.org [162.210.110.4] ...
Apr 28 05:16:29 wallaby daemon.info ntpclient[2748]: Time set from pool.ntp.org [162.210.110.4].
Apr 28 05:16:29 wallaby daemon.info process_monitor[1157]: cyclic NTP Update success (servers pool.ntp.org)
Apr 28 06:16:29 wallaby daemon.debug ntpclient[2936]: Connecting to pool.ntp.org [204.2.134.164] ...
Apr 28 06:16:29 wallaby daemon.info ntpclient[2936]: Time set from pool.ntp.org [204.2.134.164].
Apr 28 06:16:29 wallaby daemon.info process_monitor[1157]: cyclic NTP Update success (servers pool.ntp.org)
Apr 28 07:16:29 wallaby daemon.debug ntpclient[3145]: Connecting to pool.ntp.org [199.102.46.74] ...
Apr 28 07:16:29 wallaby daemon.info ntpclient[3145]: Time set from pool.ntp.org [199.102.46.74].
Apr 28 07:16:29 wallaby daemon.info process_monitor[1157]: cyclic NTP Update success (servers pool.ntp.org)
Apr 28 08:16:29 wallaby daemon.debug ntpclient[3345]: Connecting to pool.ntp.org [23.239.26.89] ...
Apr 28 08:16:29 wallaby daemon.info ntpclient[3345]: Time set from pool.ntp.org [23.239.26.89]. _________________ Unifi Security Gateway:Unifi Firmware Netgear r7800:Voxel Firmware Modem:Netgear CM500V voice and Data. ISP:Comcast tutorial for flashing "WRT" series: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=287813 DD-WRT Installation, Upgrade & Basic Setup–Cliff Notes: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=311117 Kong DD-WRT Config Tutorial: http://www.instructables.com/id/Install-and-Configure-a-DD-WRT-Kong-Router/ I tried to be normal once. Worst 2 minutes ever.
