@fmarshall wrote: I don't see any mention of VLANs in the configurations in this discussion. I have settled on making (i.e. keeping) VLAN 1 (the default) the management VLAN. With some Cisco devices, this seems to make a difference. This worked for me. Strange. (BTW I'm on an RV340 on latest firmware 1.0.03.15) Changing VLAN1 from it's factory network address (192.168.1.1/24) would block access to the WebUI from the LAN. Interestingly, remotely accessing the WebUI continued to work. Factory resetting didn't help. So I settled on the advice of @fmarshall and created VLAN2 for the LAN. LAN interfaces 2-4 are untagged on VLAN2, and LAN interface 1 remains untagged on VLAN1. It means that I can't access the Web UI from VLAN2 but so be it. This kinda matches other Cisco devices that want a dedicated management port/VLAN.
... View more