TomatoUSB

I'm replacing a Linksys RV042 with a WNR3500L+Tomato (Shibby, tomato-Netgear-3500Lv2-K26USB-1.28.RT-N5x—101-AIO.chk). I'm trying to connect devices from different subnets, 192.168.20.x (DHCP assigned) and 192.168.22.x (static addresses), all of them connected to the same WNR3500L.

In the RV042, there was a setting for multiple subnets (Setup -> Network -> LAN Setting -> Multiple Subnet Settings), where I just added the 22 subnet. This made all subnet 22 hosts accessible from subnet 20 and vice versa.

In Tomato, I tried to achieve the same functionality by adding the subnet under Basic->Network->LAN, but this is apparently not how you do it. The router is accessible as both 192.168.20.2 and 192.168.22.2, but I can't reach any subnet 22 hosts from subnet 20.

Picture of the setup:
s16 <dot> postimage <dot> org/a7kz5yulv/tomato1.png (The forum doesn't let me insert an image tag, or link)

So, how do you make the two subnets reachable from each other?

Since i couldn't post a screenshot (forbidden by forum), I'm copying the text from the router setup screen.

I selected Basic->Network in the left hand side menu, and this is what it looks like when I've added the subnet:

LAN
--------------------------------------------------------------------------------------------
Bridge     STP       IP Address       Netmask       DHCP         IP Range         Lease time
 br0     Disabled   192.168.20.2   255.255.255.0   Enabled   192.168.20.100-239     10080
 br1     Disabled   192.168.22.2   255.255.255.0   Disabled          -

The question is still, like in the first post, how do you make the two subnets reachable from each other?

Have you considered using router "ADVANCED->LAN access" GUI?

I don't have a clue what LAN Access is for (I'd love to RTFM, but there is no FM), but I tried settings that seemed logical:

LAN Access
-----------------------------------------------------------------
On   Src   Src Address   Dst      Dst Address   Description

On   LAN                 LAN1

That didn't work. Also tried:

LAN Access
-----------------------------------------------------------------
On   Src   Src Address   Dst      Dst Address   Description

On   LAN                 LAN1
On   LAN1                LAN

That didn't work either. Tried specifying src and dst address:

LAN Access
-----------------------------------------------------------------
On   Src   Src Address     Dst      Dst Address        Description

On   LAN  192.168.20/24    LAN1    192.168.22.0/24

…but it made no difference.

- LAN access sample usage is printer sharing located on particular subnet.
- Subnet router IP address is normally ending in '1' and not '2'. Should be, 192.168.20.1 and 192.168.22.1.
- for 2 subnet to be accessible. You need to provide route command. See Advanced->routing.

No, it's not necessary for the routers to be assigned an IP address where the last byte is 1. Some ISPs send out home routers with address 192.168.1.254, and the Linksys router I'm replacing was assigned 192.168.20.2, so routers can have any address you assign to them.

Anyway, after many hours of googling and experimenting I found that the solution is not to do anything that I've tried in the previous posts, but to put

ifconfig br0:0 192.168.22.2 netmask 255.255.255.0

So you only had to add the line "ifconfig br0:0 192.168.22.2 netmask 255.255.255.0" to the firewall tab and that's it? Nothing else from above?

Ancient topic, I know - but I just spent the last 3 hours playing with my router having this exact problem.

I too had to put this ifconfig line in my firewall-script in order to have my tomato router router between two separate subnets. Funny thing is I had this working fine, (to the best of my knowledge without having any "workarounds" like this) until I upgraded my firmware today to the 138 build. I downgraded as far as I could, thinking that might have been it, but every version I flashed onto my router, I had this same problem.

And yes, nothing in the BASIC or LAN ACCESS options seems to work. SSH-ing into the router and running this command, or placing it in the firewall script section does the trick.