Static address ?

[Stev Wolf]

I have read a lot about setting up static addresses but still cant seem to get it to work.
Can someone tell me what numbers to put in which router?

I have a Triangle configuration, in other words at the top of the triangle I have the ISP's router that I can get into and can set up static routes.

At the top is :
A. 192.168.2.2 DHCP gives out 192.168.2.0/24. (Internet connection, Gateway)


X. 192.168.2.4 DHCP gives out 192.168.1.0/24. LAN Address is 192.168.1.1


Y 192.168.2.3 DHCP gives out 192.168.50.0. LAN Address is 192.168.50.1

How do I configure the static routes so all routers cant talk and devices on the network see and play with each other. A->YX, YX->A, Y->X etc.

Which routers do I configure so I can have a seamless connection between all the routers both ways. and which numbers do I put in each router static route.
The options are :

Destination Netmask Gateway Metric

( Ok netmask I got, its generally always 255.255.255.0)

The reason for this is t hat my cameras are on on one network, while I have other things set up on other routers.

Regards

 

[IAmATeaf]

What routers do you have? Although the router might be capable of adding a static route unless it also is capable of routing then simply adding a static route won’t achieve what you are trying to do.

A static route simply tells that device to pass any requests to that address to be passed to the router/gateway on that subnet.

 

[Stev Wolf]

Thanks for your reply.

Yes there may ? be more to it in that I assume it's like throwing a ball, you can throw a ball but the person catching the ball must agree to catch it.
Thats why I assume (perhaps erroneously) that both routers need some sort of settings changed (perhaps static routes on both sides ??? i don't know) for each router to say, "Yes I will catch the packet and pass it on". Thats really why I asked the question which router needs what STatic configuration. So many faq's dont seem to talk about the other routers?? Then there is the confusing Gateway, term. In other words I dont think they mean the Interent gateway, mine being 192.168.2.2, but the Wan address of the router your trying to throw the ball to. If I can see how its suppose to work with the actual IP's in which router, then I know I can logically figure out any configuration.

My Routers Are:
Smart/RG SR516AC (My service providers router)
ASUS RT-AC66U B1 (just bought and setting up)
D-Link DIR605L (OLD Router maybe 10 Years but has worked fine)

 

[Valiant]

Sounds like you are overcomplicating your network and making it difficult to manage. Does your ISP provided router allow creating Vlans ?. It may be better to configure different subnets per port if possible. Another option is to consider a Layer 3 switch.

To create static routes you would generally do something like-

route <Destination IP> <Subnet mask> <next hop address>

So for router X to see subnet A (192.168.2.0 network) you would create a static route similar to -

route 192.168.2.0 255.255.255.0 192.168.1.1 (.1.1 being gateway for LAN X)


Post a diagram, will help readers understand better.

 

[Stev Wolf]

Thanks. here is a diagram

 

[IAmATeaf]

What you are trying to as far as I know won’t work, those routers won’t be capable of routing traffic between 192.168.2.x and the subnet that you’ve configured your devices to sit on. Unless there are features in those routers that I am unaware of.

They call these devices routers as they can route traffic between the WAN port and local LAN devices but the way you are using them you are trying to route traffic on the internal LAN ports.

There may be other ways but you need a device/appliance to route between the disparate networks.

With an appliance you’d plug it into you main network, say with an ip of 192.168.2.3 then set up routing on the device for 192.168.1.x and 192.168.50.x then you’d plug in your routers configured with an address of the router network so 192.168.1.1 and 192.168.50.1. In both routers you would add static routes back to appliance and in your main router you would static routes to other networks pointing back to the appliance.

You can do routing using a Windows device but I haven’t used the routing capabilities of Windows for ages so no idea how good it is or how it performs.

 

[IAmATeaf]

Have a read of this article, it explains things quite nicely Routing Between VLANs – Practical Networking .net

 

[IAmATeaf]

If all you are trying to do is keep your cams on a separate network and are using BI then you can sort of achieve separation by plugging in a second network card into your BI PC. Configure one card with and an IP address that sits on your main network so 192.168.2.x and then configure the second card to have say 192.168.50.x.

Plug that second card into a POE switch and plug the cams into the switch with suitable IPs.

This will keeps things separate, the cam traffic will be kept within that network, the cams won’t be able to access the internet either. The only limitation is that in order to access the cams GUI would be via that PC, so you’d have to logon to the BI PC before you could logon to the cams.

 

[Stev Wolf]

Well I have other things on that network also.
I will read up on vlans.

However just to show you what's happening. Some forwarding seems to be occurring from the 192.168.2.0 network to the 192.168.50.0 netw. See below when I ping the 50.1 netw. And the 192.168.1.0 network. Notice redirect note.

PING 192.168.50.1 (192.168.50.1) 56(84) bytes of data. 64 bytes from 192.168.50.1: icmp_seq=1 ttl=64 time=67.6 ms 64 bytes from 192.168.50.1: icmp_seq=2 ttl=64 time=7.23 ms From 192.168.2.2: icmp_seq=2 Redirect Host(New nexthop: 192.168.2.3) 64 bytes from 192.168.50.1: icmp_seq=3 ttl=64 time=4.06 ms

And

--- Connection: WIFI PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. From 192.168.2.2: icmp_seq=2 Redirect Host(New nexthop: 192.168.2.4) --- 192.168.1.1 ping statistics --- 11 packets transmitted, 0 received, 100% packet loss, time 20131ms

While this one fails it shows something is functioning. I will look at vlans and keep playing.
It may not work, but then why would routers have static routes that can be set up for both lans and wans. Covering both bases?

Regards.

 

[IAmATeaf]

Maybe the Asus is capable of more? Try the commands pathping and tracert which should show you the hops the ping is taking to reach the 50 network.

 

[Valiant]

The problem you have is more than routing. These consumer devices are FIREWALLS too (read up on Stateful Packet Inspection and NAT). They will block all external traffic and only pass traffic that originates from the LAN side. In your case, the 192.168.2.0 network will be untrusted by routers X and Y. In order to pass traffic, you would have to create port forward rules on routers X & Y. What WAN interface does X & Y have ?, the firewall will apply between the WAN and LAN sides. Is it a xDSL interface or do you have ethernet on the WAN port ?

Have a look at what you are try to accomplish, I think there will be easier ways. Perhaps use MAC filtering to block outbound internet access if that is your concern.

 

[Stev Wolf]

Maybe the Asus is capable of more? Try the commands pathping and tracert which should show you the hops the ping is taking to reach the 50 network.

Good tip