Posted: Thu Jan 31, 2019 7:11 Post subject: Linksys EA8500, Policy Based routing failure and other issue
So I updated my firmware, to DD-WRT v3.0-r37305 std (10/10/1.
Ever since I updated it, my OpenVPN connection won't work if Policy Based routing has an entry in it.
Another issue, is that if I reboot the router... the Ethernet LAN ports go down. They only go back up, if I *PHYSICALLY* reboot the hardware (I.E. Pushing the physical button). When the LAN is down, I can only access 192.168.1.1 via Wireless... but not Ethernet LAN... odd. Again, just to make it perfectly clear... physically rebooting it seems to fix the issue.
Joined: 18 Mar 2014 Posts: 12917 Location: Netherlands
Posted: Thu Jan 31, 2019 9:46 Post subject:
Well you did not specify from what build you updated, but maybe a somewhat older build without SFE.
SFE (Shortcut Forwarding Engine) dramatically speeds up WAN <> LAN throughput but is not compatible with PBR.
So on the Setup page/Basic Setup under WAN setup disable SFE.
Posted: Thu Jan 31, 2019 16:01 Post subject: Re: Linksys EA8500, Policy Based routing failure and other i
NetworkFox83 wrote:
Another issue, is that if I reboot the router... the Ethernet LAN ports go down.
Some folks with the EA8500 have that problem.
I think Kong mentioned maybe a bug in the switch....however...
I never have had such a problem with my two EA8500 in 3 years.
Posted: Fri Feb 01, 2019 5:22 Post subject: Re: Linksys EA8500, Policy Based routing failure and other i
mrjcd wrote:
NetworkFox83 wrote:
Another issue, is that if I reboot the router... the Ethernet LAN ports go down.
Some folks with the EA8500 have that problem.
I think Kong mentioned maybe a bug in the switch....however...
I never have had such a problem with my two EA8500 in 3 years.
EDIT:
also he mentions in the svn ticket he has
CBT U-Boot ver: 1.0.12
Both my EA8500 have
CBT U-Boot ver: 1.0.9
don't know if that may be the problem but it tis a difference
Help me out here. What should I do?
Having to physically reboot the router isn't a big deal...
So what do I do about the inability to use policy based routing? Seems whenever I put in, for example 192.168.1.64/26 (64 hosts 64-127)... I can't connect to webpages.
I do not use ovpn client on the EA8500. Best advice I can give about that is LISTEN to whategc tells you and/or if eibgrad pops in.
They have worked this stuff forever and know what they are talking about.
Ok... so here is a little more detail about the issue with Policy based routing.
When I turn on policy based routing by entering "192.168.1.64/26".... the internet connection gets compromised.
I can't pull up any websites. ODDLY though, I can still issue the nslookup command, and look up the ip addresses for various websites. I can even *PING* those ip addresses.
However, if I try to take the IP addresses and place them into the browser... they still dont bring up the website. What ... the ... heck?
Posted: Fri Feb 01, 2019 19:33 Post subject: Just updated
I just updated to "DD-WRT v3.0-r38065M kongat (12/22/1" per mrjcd's suggestion.
Seems to have resolved the issue with policy based routing.
One more question. I forgot to factory reset, before and after the firmware update. Someone told me you need to do that, since retained configurations can screw up your firmware?
I do know you shouldn't upload any backedup configurations...except from the *EXACT* firmware you have.
Thing is, the router seems to be working just fine.
Posted: Fri Feb 01, 2019 20:01 Post subject: Re: Just updated
NetworkFox83 wrote:
Thing is, the router seems to be working just fine.
Do I really need to factory reset my router?
If it's working then NO you need not do a nvram erase.
I hardly ever use a nvram backup but I do have many just because.
They are always made after a nvram erase and reconfig on a known good build. If I ever need a good working build then I just install the correct build and use its nvram backup.
I also have have a backup main router configured exactly same as what I'm using so its no problem for me to swap out main......I do that sometimes iffin main router seems to be getting bad from so many tests firmware upgrades and I also run public webserver within my home network so don't like to keep network down longer than 1 minute
.
