RV110W inter-VLAN-routing not possible

[ocellus23]

In Cisco RV110W I configured 2 VLANs, one 192.168.1.xxx(Green Net) and the second 192.168.2.xxx with only one fixed address 192.168.2.100(Server), which is configured in the DMZ Zone. I enabled in Cisco "inter-VLAN-Routing", that is described "routing between the seperate VLANs on the Cisco RV110W" I can Ping the server in one direktion, in the other I got an error. That is all expected and ok! All other expected abilities work well !

Now I want to see the server from green net . (firewall in the server is off)

I configured Networking/Router with exact the Hint values and got an error : "destination LAN IP cannot be the same as the router IP subnet"

Sorry, I don't understand this. Can anybody help?

Thanks in Anticipation

Anton

[Tom Watts · Accepted solution]

If I understand correctly, you made a second vlan, 192.168.2.x. The RV110W is a member of this subnet as well, therefore you can't make a static route for something the router is aware of as it hosts that subnet.

-Tom
Please rate helpful posts

[ocellus23]

Thank you for this reply. I think I had  to buy an Layer3 supported switch.

Hint to Cisco : It would be very customerfriendly to give in the administration guide  a hint, that there is a need of an additional equipment, to realise full funktion of inter-VLAN-routing.

Thanks oncemore

Anton

[Te-Kai Liu]

If you have two VLANs (192.168.1.x and 192.168.3.x) on the LAN side of RV110W, the inter-VLAN traffic should pass if the inter-VLAN option is enabled. There is no need to configure static routes.

Given that 192.168.2.100 is configured as a DMZ Host, I suspect that it may be the reason that traffic from 192.168.2.100 is not reaching the 192.168.1.x subnet.

[ocellus23]

That is correct, I will not see from the DMZ Host my green net - Therefore I do not get a Ping Answer in that direction.

But I want to see and handle the Server from the green Zone as a NAS, the server must have  then a adress from the green net e.g. 192.168.1.50 -- otherwise the subnetMask  255.255.255.0 will deny.

I had hoped - from the administration guide - that the site "networking/routing" will do this translation.

Now I think, that a managed Layer3 switch can do this translation, or is there any hope to avoid spending money for that additional switch.

Anton

[Te-Kai Liu]

Why not putting your server in a non-DMZ VLAN so it can freely communicate with the green net (192.168.1.x). You can use port forwarding rules to make the server available to the internet.