I bought a RVS4000 Router last week. I configured two VLAN's (beside of the default one), VLAN ID 120 and VLAN ID 130. I configured an IP in the LAN section for both of them (192.168.120.1 and 192.168.130.1).
I then configured port 1-3 to be in VLAN ID 120 (Untagged) and port 4 to be the Trunk (VLAN ID 120 Tagged and VLAN ID 130 Tagged). The port 4 I connected a Cisco SLM224G. There I configured these two VLAN's too, and configured the uplink port as Trunk as well. The two network seem to be properly switched: I have access to 130 Hosts directly on the VLAN ID 130, and the other VLAN ID 120, I have access on all hosts connected to that VLAN ID as well (both, on the switch and the three ports on the router). On Layer 3, the RVS4000 is configured to route between the VLAN's. But I cant ping hosts on the other network! I configured the Router to be the default gateway... I think the source of that problem is the next one:
I can't ping from the Routers Maintainance Page to a host connected on Port 1-3 of the Switch (which is configured as VLAN ID 120 untagged). I reseted the router, and tested this simple use case again: Created two VLAN's, defined Port 2 to be in one of them, setted the IP's properly (192.168.120.1 for the Router on that VLAN), but stil, I cant ping from the Router to Host on that VLAN (Router=>192.168.120.10)! The other way around works (Host=>192.168.120.1)
The Routers Configuration:
WAN: PPPoE (works)
LAN: VLAN ID 1: 192.168.1.1 no DHCP
VLAN ID 120: 192.168.120.1 no DHCP
VLAN ID 130: 192.168.130.1 no DHCP
Routing: Inter VLAN Routing: Enabled
L2 Switch: VLAN ID 1/120/130
Port 1: Untagged, 120untagged
Port 2: Untagged, 120untagged => Server connected
Port 3: Untagged, 120untagged
Port 4: Trunk, 1 untagged, 120tagged, 130tagged
Wiresharks shows me no ARP requests on that interface too... The product seems not to work porperly when I configure a port to be in a VLAN untagged, and try to ping to a host connected to that interface.
I have Firmware 18.104.22.168 (Website says 22.214.171.124 is the newest...??)
One thing that I think that I did differently than falstaff84 is on the PC in VLAN 2 with DHCP off I set the Default Gateway to 192.168.1.1, the default IP of the router. He mentions 192.168.120.1 in his post. Did you change the Default Gateway on your devices in VLANs other than 1? I did not try using a DHCP server other than the RVS4000, although I did test with static IPs. Please test by following the steps in the post I referenced above. If it does not work properly there may be an issue with your router.
Hardware version 2 and firmware version 126.96.36.199. Did the computer on VLAN 2 get a valid IP address from the router? Open the Command Prompt and type ipconfig /all. Press enter and see what the IP, Gateway and DNS servers are. Mine had 192.168.2.100, GW 192.168.1.1, ISP DNS servers.
Hello, This article will describe how to configure PPTP VPN on the new
RV340/345 routers from the Small Business series. RV340/345
Configuration The first step is to enable the PPTP Server: Go to VPN ->
PPTP Server Change PPTP Server: from Off to On Selec...
Article ID:5748 Use TheGreenBow VPN Client to Connect with RV34x Series
Router Introduction A Virtual Private Network (VPN) connection allows
users to access, send, and receive data to and from a private network by
means of going through a public or share...
Article ID:5728 Configure a Teleworker VPN Client on the RV34x Series
Router Objective The Teleworker VPN Client feature minimizes the
configuration requirements at remote locations by allowing the device to
work as a Cisco VPN hardware client. When the T...