Re: New firmware 1.0.03.24 for rv340w - Page 3

chamel123 · ‎11-01-2021

Someone having a wan issue with the latest firmware? In my case, the wan1 interface doesn't connect anymore. Had to rollback to 1.0.03.22.

Looks like 1.0.03.27 is the good one!! Thanks Cisco

bergmarmot · ‎12-03-2021

Same here. Just rolled back to 1.0.03.22 and everything is working fine again.

Computers did not get IP assigned anymore. Probably that was the main cause of all other issues as these are IP address related (DNS server etc)

Also internet was not working and I only could login to the router (fortunately) and roll back to the previous verion

CristianDuc · ‎12-03-2021

Hi Everybody, any news from Cisco, I continue to get the annoying popup asking for the firmware update? Did somebody find a way to fix the internet issue with this sw release?

My Best

etihaenni · ‎12-10-2021

Looking at the page of the RV routers, all models are now "end of life" and no new models are proposed. It's look like Cisco will discontinue the RV product line and let everybody look after another solution (Meraki?). Probably a reason of the weak reactivity at this issue.

https://www.cisco.com/c/en/us/products/routers/small-business-rv-series-routers/eos-eol-notice-listing.html

marce1000 · ‎12-10-2021

-The Cisco Support Community is populated by volunteers, it not an official support channel. If you need effective support for this problem go here : https://www.cisco.com/c/en/us/support/web/tsd-cisco-small-business-support-center-contacts.html

M.

-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

jaquavious.salam · ‎12-22-2021

Has the RV340 "without W" the same bug with new firmware?

andresdn · ‎12-22-2021

Yesterday I reached Cisco Support for 2 RV-340 with the same problem described here after upgrade to .24. Send logs and configurations to Cisco for analisys. First response was "you should roll back to 1.0.03.22 or do an upgrade to 1.0.03.24 + factory reset + configure from start". I wasn´t pleased with those solutions so they scaled the issue to a sustaining enginner. They promised me 24/48 hs with a feedback.

andresdn · ‎01-14-2022

Some feedback from Cisco sustaining engineer to try the following workaround (please see below). They are still trying to find another solution, however the workaround listed below is what they suggested for now.

AFTER UPGRADE TO .24:

workaround:

Export the configuration from web page.
Edit the configuration, remove the “<order>” lines from the configuration (see below)
Reboot with reset to default
Import the modified configuration to router, and save it to startup configuration.

Origin

After

…

<authentication-order>

<default-order>radius</default-order>

<default-order>ldap</default-order>

<default-order>ad</default-order>

<default-order>local-db</default-order>

<service>web-login-administration</service>

<use-default-order>true</use-default-order>

<order>radius</order>

<order>local-db</order>

</services>

<use-default-order>false</use-default-order>

<order>radius</order>

</services>

<service>anyconnect-vpn</service>

<use-default-order>true</use-default-order>

<order>radius</order>

</services>

<service>web-login-readonly</service>

<use-default-order>true</use-default-order>

<order>radius</order>

<order>local-db</order>

</services>

<use-default-order>true</use-default-order>

</services>

<use-default-order>false</use-default-order>

<order>local-db</order>

<order>radius</order>

</services>

<use-default-order>false</use-default-order>

<order>local-db</order>

<order>radius</order>

</services>

<use-default-order>true</use-default-order>

<order>radius</order>

</services>

<service>ezvpn</service>

<use-default-order>true</use-default-order>

<order>radius</order>

</services>

</authentication-order>

…

<authentication-order>

<default-order>radius</default-order>

<default-order>ldap</default-order>

<default-order>ad</default-order>

<default-order>local-db</default-order>

<service>web-login-administration</service>

<use-default-order>false</use-default-order>

</services>

<use-default-order>false</use-default-order>

</services>

<service>anyconnect-vpn</service>

<use-default-order>true</use-default-order>

</services>

<service>web-login-readonly</service>

<use-default-order>false</use-default-order>

</services>

<use-default-order>true</use-default-order>

</services>

<use-default-order>false</use-default-order>

</services>

<use-default-order>false</use-default-order>

</services>

<use-default-order>true</use-default-order>

</services>

<service>ezvpn</service>

<use-default-order>true</use-default-order>

</services>

</authentication-order>

########################################################################

bruce C · ‎01-14-2022

If you have a moment, can you confirm that this workaround solved the problem?

Thanks

andresdn · ‎01-17-2022

Preliminary tests went well, but there is much more to be done on various RV340 routers. 
I will update the results as the days go by.

CristianDuc · ‎01-16-2022

Thanks a lot to post the Cisco answer. Have you had the chance to prove that it works?

There was a know bug around <default-order>: https://community.cisco.com/t5/small-business-routers/new-firmware-1-0-03-24-for-rv340w/m-p/4531543

it is possible that Cisco tried to fix it the latest fw but the solution had lead to more trouble.

Cristian

andresdn · ‎01-17-2022

Preliminary tests with the changes suggested by support on xml file seem to work. I have several RV340's to reconfigure and test. I'll keep you posted on whether or not this fix is solid over the next few days.

andrea.tomassi · ‎01-04-2022

Exact same issue:

- Upgraded, wan crashed after reboot.

- Factory Reset with 1.0.03.24, setup form scratch, worked a while but wan connectivity crashed again after reboot.

- rollbacked to 1.0.03.22

For your convenience:

https://software.cisco.com/download/home/286289157/type/282465789/release/1.0.03.22

chamel123 · ‎01-31-2022

For those of you that were waiting for the next release, I just tried 1.0.03.26. Just to be sure, I've reset the router to factory then enter everything manually (didn't want to restore from an export to avoid something related to multiple failed upgrade) Everything was working fine for a while. Then I had to reboot the router and the exact same problem arise again.

Rolled back to 1.0.03.22 without changing anything to the config and I was back on track. So if you had this problem, my advise is to not wasting your time with the latest version.

OliverSu · ‎02-19-2022

I have the same issues with 1.0.03.26 as before with 1.0.03.24 image upgrade.

- timezone time is not correct after the upgrade;

- PPTP VPN users cannot connect anymore,

Rolled back again to 1.0.03.22

PS: PPTP VPN windows settings are the same. The configuration bellow: connection successful in 1.0.03.22, denided in 1.0.03.26

etihaenni · ‎03-30-2022

I reactivate the .24 image I had install previously and try the workaround proposed by andresdn, removing the lines which include <order>xxx</order>, and it seems to work correctly.

Let's wait some days to check if it is stable. if yes, I'll try to upgrade to .26 and check again.