Have you considered that your ISP still holds the old WAN IP for your previous setup? And that it might take some time before you actually get a new WAN IP and therewith internet access.
Think the intermediate time here is 10 minutes for this to work.
No, it wasn't a consideration. When I manually reboot the router, I usually also reboot my modem and switches. They are on the same power strip. Flip a switch, watch the clock for a minute, flip the switch back on.
But back on point... My home server also hosts a couple of ts3 servers, so I tend to watch my external ip very closely. Like I said, I could "see" my (external) ip, I just couldn't do anything outside of my intranet.
Have you had any luck figuring our a solution to this problem? I am having the exact same issues on my router (1900ACS V2) after updating to 4/06/18 r35681.
Joined: 20 Sep 2013 Posts: 13 Location: Chesapeake, VA
Posted: Thu Apr 12, 2018 19:58 Post subject:
tusculumgolfer wrote:
Have you had any luck figuring our a solution to this problem? I am having the exact same issues on my router (1900ACS V2) after updating to 4/06/18 r35681.
My solution was to roll back to an older version, r35452. Everything is back to normal.
Have you had any luck figuring our a solution to this problem? I am having the exact same issues on my router (1900ACS V2) after updating to 4/06/18 r35681.
My solution was to roll back to an older version, r35452. Everything is back to normal.
So I did a dirty install, and for once, didn't make a backup before upgrading (dumb, I know). There isn't any way to roll back is there?
Posted: Fri Apr 13, 2018 4:34 Post subject: strange characters in the port forwarding field
I'm seeing what looks like random characters in the "Source Net" fields of all my forwarded ports. Whatever is happening totally broke port forwarding because none of them worked after the upgrade.
I reverted back to 35244 and they went away and forwarding works once again.
Joined: 20 Sep 2013 Posts: 13 Location: Chesapeake, VA
Posted: Fri Apr 13, 2018 11:21 Post subject:
tusculumgolfer wrote:
Buddlespit wrote:
tusculumgolfer wrote:
Have you had any luck figuring our a solution to this problem? I am having the exact same issues on my router (1900ACS V2) after updating to 4/06/18 r35681.
My solution was to roll back to an older version, r35452. Everything is back to normal.
So I did a dirty install, and for once, didn't make a backup before upgrading (dumb, I know). There isn't any way to roll back is there?
Do a clean install and then load one of your earlier backups?
Have you had any luck figuring our a solution to this problem? I am having the exact same issues on my router (1900ACS V2) after updating to 4/06/18 r35681.
My solution was to roll back to an older version, r35452. Everything is back to normal.
So I did a dirty install, and for once, didn't make a backup before upgrading (dumb, I know). There isn't any way to roll back is there?
Do a clean install and then load one of your earlier backups?
So you can do a firmware downgrade by loading a previous release into the "upgrade" area in the dd-wrt firmware? I just want to make sure I know how to downgrade correctly.
That is correct. The firmware update process does not care if newer or older.
Amazing! I've been without wifi for a week because I wasn't sure if that would work or if it would brick my router. You just made my weekend much better. Thank you guys. You're the real heroes of wifi.
Posted: Mon Apr 16, 2018 4:29 Post subject: WRT3200
Everything has been running great on this build with no problems whatsoever. Running DDNS, scripted in some OpenDNS for the kids and OpenVPN with policy based routing. Both radios enabled and running great with no hiccups. Even my QOS seems to be running as expected
Same issue as a few of the others... WRT1900ACS port forwarding is broken with strange behavior... fowarding ports to incorrect IPs etc. Sourcenet is populated with strange characters
You just made my weekend much better. Thank you guys. You're the real heroes of wifi.