Static Routing Help?
-
So I am at a loss here, I don't really understand static routing and nothing I have tried in regards to it has worked. This is an outline of the network I am working with:
Router A is a router to which I do not have access to and is the vendor's router. I won't go into reasons why I don't have access to it, but it involves the devices at the bottom of my network outline.
Router B is the pfsense box, to which I do have access.As I understand it, if I want to connect to my Server (172.16.0.3/32), from my PC (192.168.160.122/32), I need to setup a static route, unfortunately I am at a loss on how to set everything up properly when it comes to that.
For testing purposes is it needed to set the static route within Router A, or can I simply establish the route on my PC (Windows) and say for any pings to 172.168.0.0/24, use 192.168.160.2?
-
If you can't add static routes to router A, then you'll have to add them to "PC". And any other device connected to that 192.168.160.0/24 network that you want to be able to communicate with things behind router B.
-
Even if he puts route on router A to get to the network behind router B… This PC on the 192.168.160 network is on the transit network - That is BAD design, and as cmb mentions you would have to use host routing on that PC or any devices on that transit or your going to have a bad day with asymmetrical routing when that box talks wants to talk to stuff behind B or B wants to talk to stuff on the transit, unless router B is also natting?
To be honest why do you not just use 1 router.. This is much easier concept and easier setup for someone that does not self admitting knows little about routing and networking..
Normally routers are connected via transit networks, no devices are place on transit network other than "routers" these routers have routes to the networks behind the routers via the transit network(s) You normally do not nat inside a rfc1918 network.
What are you actually using for these routers? Pfsense? Is that router A some wifi router off the shelf device?
Attached is a typical setup with downstream router via transit network.
So edge router would have routes to the networks behind downstream router pointing to the downstream routers IP in the transit. Downstream router just really needs its default route pointing to the nat routers transit IP. The nat router needs to know to nat ALL the networks behind it to whatever its public IP is, etc.