cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Bookmark
|
Subscribe
|
2017
Views
0
Helpful
1
Replies

Setting up RV340 in bridge mode

davidmoor1
Level 1
Level 1

I am following the instructions from 

 

https://www.cisco.com/c/en/us/support/docs/smb/routers/cisco-rv-series-small-business-routers/Configure-Bridge-Settings-on-the-RV34x-Router.html

 

to set up my RV340 in bridge mode.  The configuration I am trying to set up is:

 

Comcast 1GB modem > RV340 > QNAP 10 GB router > devices, some 10 GB

 

I want the Comcast DHCP serve (10.0.0.X) r to provide all IP addresses, so that wireless (from Comcast modem) and wired connections are on the same network.

 

I set the the bridge to VLAN IP address as 10.0.0.5 (the RV340 IP address?), 255.255.255.0, default gateway 10.0.0.1, and static DNS field too 10.0.0.1.  I hit apply and get the spinning wheel.  Never goes away.

 

Looking at the computers which are connected to the RV340 one shows that it is connected (RV340 link light), but has a self assigned IP addresses and is off the internet.  A second computer shows a 192.x.x.x. address, not the 10.x.x.x I would have expected. It too is off the network.  A network scan (when connected to the QNAP switch)  seems to show that the Cisco is at 10.0.0.130, but when I try to connect it is unreachable.

 

 

 

 

1 Accepted Solution

Accepted Solutions

Jo Kern
Cisco Employee
Cisco Employee

Hi, the link you are referring to describes a particular use case where you have a bridged connection coming from a tagged VLAN from the WAN interface bridged to a VLAN behind the router on the LAN interface.

On the WAN interface:

WAN1 is untagged

WAN1.1 is tagged with a VLAN tag.

I assume the Comcast router does not "tag" the packets but you use WAN1.1 which is "tagged". I suggest to delete   "WAN SUB Interface WAN1.1". Just set the WAN1 interface to "Bridge". Not the WAN1.1.

It works for me.

 

Spinning wheel indicated you lost connectivity to the management interface of the RV340.

Please be careful. When you do that please assign an IP address ( eg. 10.0.0.5 , Gateway 10.0.01)  from the Comcast router's LAN subnet to the RV340 to have a management IP address.

Or create a VLAN2, use a DHCP server with 192.168.2.0 subnet in VLAN2. Enable management access for VLAN2. Configure one RV340 LAN port as untagged member of VLAN2. This should give you a " management port " on the RV340 you can use as a backup.

Otherwise might need to factory reset the router to get access.

 

Please let us know what you really want to achieve , as my answer might address your question but it might not address your overall network design.

View solution in original post

1 Reply 1

Jo Kern
Cisco Employee
Cisco Employee

Hi, the link you are referring to describes a particular use case where you have a bridged connection coming from a tagged VLAN from the WAN interface bridged to a VLAN behind the router on the LAN interface.

On the WAN interface:

WAN1 is untagged

WAN1.1 is tagged with a VLAN tag.

I assume the Comcast router does not "tag" the packets but you use WAN1.1 which is "tagged". I suggest to delete   "WAN SUB Interface WAN1.1". Just set the WAN1 interface to "Bridge". Not the WAN1.1.

It works for me.

 

Spinning wheel indicated you lost connectivity to the management interface of the RV340.

Please be careful. When you do that please assign an IP address ( eg. 10.0.0.5 , Gateway 10.0.01)  from the Comcast router's LAN subnet to the RV340 to have a management IP address.

Or create a VLAN2, use a DHCP server with 192.168.2.0 subnet in VLAN2. Enable management access for VLAN2. Configure one RV340 LAN port as untagged member of VLAN2. This should give you a " management port " on the RV340 you can use as a backup.

Otherwise might need to factory reset the router to get access.

 

Please let us know what you really want to achieve , as my answer might address your question but it might not address your overall network design.