Joined: 19 Oct 2017 Posts: 2 Location: Ottawa Canada
Posted: Thu Oct 19, 2017 23:58 Post subject:
Router: D-Link DIR-859 A2
Firmware DD-WRT v3.0-r33525 std (10/17/17)
Kernel: Linux 3.18.75 #627 Tue Oct 17 03:30:17 CEST 2017 mips
Status: Good
Reset: No
Upgraded from 27378 via web interface GUI with a wired connection, all config parameters updated cleanly.
After some time of working web interface is crashed on Chromium browser. In the FireFox in the same time the GUI is good.
Please define crashed.
Does it completely die until the httpd process is restarted or can you hit refresh and try again?
There were two screenshots in the same time. Is it not enough? The process still working, I can access the router by FireFox. But in the Chrome browser the GUI is crashed. In the same time.
What exactly has crashed or do you just mean that the page doesn't appear properly?
What happens if you hit refresh in chrome after the bad pages shows - do you get connection refused type error or does the page just try (and maybe fail) to display again?
Status: ok
Reset: no
Errors: openvpn conflicting with startup script and policy based routing box.
(sorry ahead of time if i should be posting a separate thread on this. i figured since i was posting the status of the upgrade, i might as well do the details, too. let me know if it would be better to split this off)
i was on r31899 and successfully running a modified startup script of eibgrad's along with input into the PBR box.
the script took listed domain names and routed those though the wan, bypassing vpn for those domains. the PBR, of course, did the same for ip addresses.
that's backstory to explain the specifics of what i encountered with the upgrade to r33525.
while working with the tech support for my vpn, i decided to remove the startup script, then the PBR, just to take them out of the picture.
summary of what i encountered:
no startup script, and no PBR: vpn worked.
with the startup script, and no PBR: vpn worked, but domains listed in script didn't route through the wan (they hung).
with the startup script, and with PBR: no vpn (it hung), but the domains listed in the script did route through the wan.
no startup script, and with PBR: the ip address listed in the PBR routes through the wan, but there is no vpn (they hung) and the domains listed in the script didn't route through the wan (they hung).
Status: ok
Reset: no
Errors: openvpn conflicting with startup script and policy based routing box.
(sorry ahead of time if i should be posting a separate thread on this. i figured since i was posting the status of the upgrade, i might as well do the details, too. let me know if it would be better to split this off)
i was on r31899 and successfully running a modified startup script of eibgrad's along with input into the PBR box.
the script took listed domain names and routed those though the wan, bypassing vpn for those domains. the PBR, of course, did the same for ip addresses.
that's backstory to explain the specifics of what i encountered with the upgrade to r33525.
while working with the tech support for my vpn, i decided to remove the startup script, then the PBR, just to take them out of the picture.
summary of what i encountered:
no startup script, and no PBR: vpn worked.
with the startup script, and no PBR: vpn worked, but domains listed in script didn't route through the wan (they hung).
with the startup script, and with PBR: no vpn (it hung), but the domains listed in the script did route through the wan.
no startup script, and with PBR: the ip address listed in the PBR routes through the wan, but there is no vpn (they hung) and the domains listed in the script didn't route through the wan (they hung).
There has been a conflict with SFE (Shortcut Forwarding Engine) on main setup page ...prolly enabled by default --conflicts with PBR.
So you can use PBR for your ovpnclients or use SFE if you need the speed .... but don't use both
There has been a conflict with SFE (Shortcut Forwarding Engine) on main setup page ...prolly enabled by default --conflicts with PBR.
So you can use PBR for your ovpnclients or use SFE if you need the speed .... but don't use both
NICE!! this took care of each of the scenarios, and the script and the PBR are both functioning as intended
What exactly has crashed or do you just mean that the page doesn't appear properly?
What happens if you hit refresh in chrome after the bad pages shows - do you get connection refused type error or does the page just try (and maybe fail) to display again?
If the web page is not readable, it is crashed to me. Refresh, jumping from one page to another - nothing helps. It does not happen all the time and my FF got the right page in the same time - httpd still worked.
Joined: 10 Oct 2014 Posts: 101 Location: 60th parallel N.
Posted: Fri Oct 20, 2017 12:13 Post subject:
Router: EA6900 v1
Firmware : r33525
Tried upgrade via webGUI, loaded some 30s, then it rebooted, came up with the same firmware as was loaded before, r28139.
Made a second attempt, it loaded for some 40s, then rebooted. Never came back, seem semi-bricked.
Answers on ping 192.168.1.1 on power up, then goes to "sleep". Will have to work on this.
Upgrade from r28139 to r33525 via webGUI.
The r28139 firmware is some 28MB in size, while the r33525 seem be only some 24MB ? _________________ EA6900 v3.0-r52217 std ░ WZR-HP-AG300H-DD-WRT v3.0-r52095 std ░ WHR3-G54 v3.0-r29193 mini ░ WLI-TX4-G54HP ░ WBMR-HP-GNV2 ░ TL-MR3420v²
Tried upgrade via webGUI, loaded some 30s, then it rebooted, came up with the same firmware as was loaded before, r28139.
Made a second attempt, it loaded for some 40s, then rebooted. Never came back, seem semi-bricked.
Answers on ping 192.168.1.1 on power up, then goes to "sleep". Will have to work on this.
Upgrade from r28139 to r33525 via webGUI.
The r28139 firmware is some 28MB in size, while the r33525 seem be only some 24MB ?
They would prolly know more about that router over in broadcom forum
Joined: 10 Oct 2014 Posts: 101 Location: 60th parallel N.
Posted: Fri Oct 20, 2017 13:21 Post subject:
ah yes, in my haste to set up the WZR-HP-AG300H , as a backup, forgot the EA6900 is Broadcom a chip. Reposted there, thanks. _________________ EA6900 v3.0-r52217 std ░ WZR-HP-AG300H-DD-WRT v3.0-r52095 std ░ WHR3-G54 v3.0-r29193 mini ░ WLI-TX4-G54HP ░ WBMR-HP-GNV2 ░ TL-MR3420v²
Last edited by droid-I on Sat Oct 21, 2017 15:12; edited 2 times in total
Status: Ok - Working / Upgraded via WebGUI
Reset: No
Errors: I can't upgrade or downgrade (I want to upgrade to the last beta r33555). I tried a downgrade to r33492 and even tried using the webrevert and nothing. I don't remember what version I was using before (I think it was r32597) but it was working fine and just wanted to upgrade bc of the wpa2 bugfix, and I did... to this version and despite a few drops in wifi connections (that I didnt have in the previous one) it was fine.
I've tried 30/30/30 and nothing changes
The good thing is is not bricked but I'm stuck in it
Thanks in advance
------
Vico56 wrote:
annie wrote:
Upgrade from build 33492 fails on TP-Link TL-WR1043ND v1.
Unit reboots, but build 33492 is still present when the unit is up again.
Yes, I can confirm this. It means that for WR1043ND V1 the previous version r33492 still has the same issue as r33375 and r33413 and cannot be upgraded via web.
Posted: Tue Oct 24, 2017 2:45 Post subject: Re: New Build ----- 17/10/2017---r33525
gin-n-tonic wrote:
Szymucha wrote:
Router Model: WR1043nd v1
Status: Working
Reset: None
Errors: OpenVPN not working
Upgraded from some old beta build from Jun 2017
Any potential fixes on ovpn issue?
OpenSSL has been upgraded. Older certificates and keys will not work. Recreate all (starting with the CA) and OpenVPN just might start working again. (Worked for me.)
My openvpn server has worked flawlessly for over a year, this weekend i could no longer connect and for some reason my switch had also stopped working. That cut half my network off since my NAS and media server are hardwire. I flashed my DLINK DIR-825 B1 today with this build without any issues, except that now my openvpn server wont't even start. Before it was running but i couldn't connect. I created new certs and rebooted my router but my ooenvpn server still won't start. I found a post that says use build 30880 because buolds after that had issues with openvpn, any other ideas?
