RV180 Router: Cannot get Inter-VLAN Routing to work.

[gopalvenu]

I have been banging at this now for two days and just cannot get Inter-VLAN routing working to work on this router.

Here is the est-up:.

Upgraded to latest Cisco firmware (1.0.1.9).
Starting with factory default settings, I added 2 VLANS as follows:

    vlan default(id=1): dhcpmode=server IP=192.168.1.1/24 port 1
    vlan vlan2  (id=2): dhcpmode=server IP=192.168.2.1/24 port 2
    vlan vlan3  (id=3): dhcpmode=server IP=192.168.3.1/24 port 3

                                   (unconnected)
                                     WAN port
                                        |         
                                    Routing/NAT
                                        |
                          --------------------------------------
vlan ip                   192.168.1.1   192.168.2.1   192.168.3.1
vlan name                   default        vlan2        vlan3
vlan id                       ID=1          ID=2         ID=3
Inter-VLAN Routing             No           Yes          Yes
Port 1                     Untagged       Excluded     Excluded
Port 2                     Excluded       Untagged     Excluded
Port 3                     Excluded       Excluded     Untagged
Port 4(not of interest)    Untagged       Excluded     Excluded
                           ---------      --------     --------
                            Port 1         Port 2       Port 3
                              |              |            |
                           AdminPC          PC2          PC3
                                       192.168.2.191   192.168.3.181

PC2 gets assigned an IP Address of 192.168.2.191 (DGW=192.168.2.1) - OK
PC3 gets assigned an IP Address of 192.168.3.181 (DGW=192.168.3.1) - OK

PC2 with (IP 192.168.2.191) can ping 192.168.2.1 and 192.168.3.1 - OK
PC3 with (IP 192.168.3.181) can ping 192.168.3.1 and 192.168.2.1 - OK

BUT....
PC2 cannot ping PC3  - NOT WORKING
PC3 cannot ping PC2  - NOT WORKING

(does not work in both Gateway Mode and Router Mode)

ANYONE CAN HELP ME FIGURE OUT WHY ??????

Your help is much appreciated.

I bought this device specifically because it supported inter-VLAN routing!.

Venu

---------------------------------------------------------------------------

Supporting Information:

Screen captures:
VLAN Membership:
  VLAN ID  Description  Inter VLAN  Device   Port 1    Port 2    Port 3    Port 4  
                        Routing     Mgment
       1   Default      Disabled    Enabled  Untagged  Excluded  Excluded  Untagged  
       2   VLAN2        Enabled     Enabled  Excluded  Untagged  Excluded  Excluded  
       3   VLAN3        Enabled     Enabled  Excluded  Excluded  Untagged  Excluded 

Multiple VLAN Subnets:
   VLAN ID IP Address   Subnet Mask    DHCP Mode    DNS Proxy Status  
        1  192.168.1.1  255.255.255.0  DHCP Server  Enabled  
        2  192.168.2.1  255.255.255.0  DHCP Server  Enabled  
        3  192.168.3.1  255.255.255.0  DHCP Server  Enabled

Routing Table (Gateway Mode)

Destination     Gateway   Genmask         Metric  Ref   Use   Interface   Type     Flags
127.0.0.1     127.0.0.1   255.255.255.255 1       0     0     lo          Static   UP,Gateway,Host
192.168.3.0     0.0.0.0   255.255.255.0   0       0     0     bdg3        Dynamic   UP
192.168.2.0     0.0.0.0   255.255.255.0   0       0     0     bdg2        Dynamic   UP
192.168.1.0     0.0.0.0   255.255.255.0   0       0     0     bdg1        Static   UP
192.168.1.0 192.168.1.1   255.255.255.0   1       0     0     bdg1        Static   UP,Gateway
127.0.0.0       0.0.0.0   255.0.0.0       0       0     0     lo          Dynamic

Routing Table (Router Mode)

(Same)

[jagarciaz100]

Hi Veno;

what about PC2 and PC3 ....any firewall or anything blocking icmp replies ?

[gopalvenu]

No, nothing blocking ICMP replies on PC2 an PC3.. they respond to pings from the same subnet.

[jagarciaz100]

The RV180's firewall features include most of what you'd expect.   It  offers simple check boxes to permit or deny flooding attacks on both the  WAN and LAN, as well controlling responses to ICMP messages. 

[gopalvenu]

OK :-) but what does that have to do with Inter-VLAN routing not working?  As far as I know, the firewall is between the LAN and the WAN - and I am not using the WAN at all here.  Do you think I need to add firewall rules for inter-VLAN traffic?  The only rules I can set on the firewall seems to be LAN-to-WAN and WAN-to-LAN, not Inter-VLAN.

[cadet alain · Accepted solution]

Hi,

It's not because the pings are permitted on the same subnet that they are from a different subnet.

You surely have a windows software firewall issue because by default it drops the icmp echoes from a different subnet.

Regards

Alain

Don't forget to rate helpful posts.

[gopalvenu]

Let me check it out and I will post my results...

[gopalvenu]

cadet alain, you hit the nail on the head.    The router was doing Iner-VLAN routing, but the PCs were blocking the pings because they came from another subnet.  Thank you for your help in resolving this.

I have a follow-up question if I may - I need to add a default route but can't seem to find a way to do that.  Tried adding a static route with IP=0.0.0.0 Mask=0.0.0.0 but it will not allow it.  My current routing table looks like this:

Destination   Gateway     Genmask           Metric  Ref   Use  Interface  Type    Flags

127.0.0.1     127.0.0.1   255.255.255.255   1       0     0    lo         Static  UP,Gateway,Host

192.168.2.0   0.0.0.0     255.255.255.0     0       0     0    bdg2       Dynamic UP

192.168.1.0   0.0.0.0     255.255.255.0     0       0     0    bdg1       Static  UP

127.0.0.0     0.0.0.0     255.0.0.0         0       0     0    lo         Dynamic UP

It routes all packets to VLAN2 and VLAN3 correctly; but if a packet arrives to any other network address, I would like to get it to forward to another gateway on VLAN2 (at address 192.168.2.254).  Can't seem to find a way to add a default route.

[gopalvenu]

My own reply to my last question re:default route.

It looks like one can have a default route (0.0.0.0/0) only to the WAN interface.