connecting 2 networks

Discussion in 'Tomato Firmware' started by baldrickturnip, Jul 17, 2008.

  1. baldrickturnip

    baldrickturnip LI Guru Member

    I have 2 networks I wish to connect together.
    one comprises 30 IP cameras , 10 WRT54GL s ( running tomato ) , a 16 port 10/100 switch , 8 port 100/1000 switch and 3 desktops - these are all set with manual IP addresses in the 192.168.222.x range

    the other network is an ADSL modem connected to the WAN port of a 54GL ( running tomato ) which has a manual IP for the LAN configured to and is running a DHCP server with IPs to 254 available , which are a couple of desktops and Wifi laptops.

    I wish to connect a LAN port from the 54GL to the 16 port switch on the 222.x network and then port forward some ports on the to some of the IP camera webserver ports so I can view them from the internet.

    how do I configure the WRT54GL to be able to access the 192.168.222.x network.

    I had thought all I had to do was set the subnet mask on to and it would have broadcast to the 222.x network also - but it does not seem to work that way and I cannot ping any of the 222.x network devices from the tools/ping page on the

    network gurus - please edumacate me :)
  2. HennieM

    HennieM Network Guru Member

    The problem most likely is that the devices on 192.168.222.x/ net don't know how to get to the GL at

    Netting is a 2-way street: GL must get to stuff, AND stuff must get to GL.
    Stuff says: Im on subnet, and is not on my subnet, where is a router that can route to the different-from-my-own-subnet

    For THIS option then, all your devices should have netmask 16 (aka Now aren't you peeved that you did not use DHCP to assign IPs and masks to those 30 cameras..... ;)

    Hopefully this easy solution would work for you:
    On the GL w Tomato, assign an IP in the other subnet (like 254 or whatever) to a br0:x interface:
    ifconfig br0:1 netmask up
    You might have to do some more iptables tweaking to get to 222 from the internet.
  3. LLigetfa

    LLigetfa LI Guru Member

    I ran into a bunch of Sony IP cams that were hit-and-miss on DHCP and I had to hard code them.
  4. baldrickturnip

    baldrickturnip LI Guru Member

    Thanks Hennie,
    the reason I manually assigned IPs to the cameras was to keep a strict numbering that would correspond to the cameras position - I know I could have used non lapsing leases.
    From the final number of the camera you can logically work out where and on what floor of the building the camera is situated.

    I have been thinking that I might just move the 200.x devices to the 222.x network as it will save me a bit of mucking around because all the devices are located in another country and I have been using VNC to access them - I have to ask someone to go and plug in a USB HSDPA dongle to a desktop on the 222.x network and tell me the IP :)

    if I was physically at the location I might have tried a bit more stuff to get it working , but I think I might save myself the time and frustration because of the distance.
  5. HennieM

    HennieM Network Guru Member

    That's a good option.

    However, if you try the ifconfig br0:1... above, you actually put the GL on the 222 net (in addition to being on the 200 net), so you won't screw up something in this process. I reckon it's worth a try before you go to the trouble of changing all the addresses.

    When you are done testing, and don't like it or it does not work, you just do
    ifconfig br0:1 down
    on the GL, and everything is back to the way it was.
  6. baldrickturnip

    baldrickturnip LI Guru Member

    I just went the 222.x route for the remote site as moving the 200.x devices across was relatively painless - most were DHCP

    I might try your solution here at home - segregate my home network and have a bit of a play - it would be useful and I do want to learn a bit more about what subnets really do.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice