MX84
WAN: ISP
LAN: 192.168.10.0/24
IP: 192.168.10.254
Connected through network at a different building.
Router A
WAN: 192.168.10.145
LAN: 192.168.20.0/24
IP: 192.168.20.1
I need to SSH from 192.168.10.2 ---> 192.168.20.62
Static Route Setup?
Subnet = ?
Next Hop = ?
Configure on both MX and Router A?
To get to 192.168.20.0/24 you go via your ISP - correct?
Is your ISP providing a WAN service to you (so you can route to the remote subnet) or just Internet (so you'll need a VPN)?
Modem ---> MX84 (192.168.10.254) ----> Switch ------(fiber to another building)------> Switch ---->
Router A (192.168.20.1)
I can go to the other building and connect to the 192.168.20.0/24 and ping back to my server on 192.168.10.0/24.
Router A is another network for some tenants that use it for an AP for wifi.
When you traceroute from 192.168.10.2 ---> 192.168.20.62 where does it die? From what you said you can get from .20 to .10 just fine so conceptually you should be able to go from .10 to .20 if there isn't a firewall rule or routing issue in between. Your 192.168.10.2 device will go to its gateway and that gateway should determine or know the route to 192.168.20.x.
Tracert from 192.168.10.2
C:\>tracert 192.168.20.62
Tracing route to 192.168.20.62 over a maximum of 30 hops
1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
_______________________________________________________
Routing
VLANs | Disabled: use a single LAN Enabled |
Routes | Subnet Type Details
|
Wondering if I need to set something up in here? ^
____________________________________________________________
Route table
192.168.10.0/24 | Default | Local VLAN | 192.168.10.254 | |
176.16.1.0/24 | Client VPN | Client VPN | Client VPN | |
10.0.0.0/22 | Public | Local VLAN | 10.0.0.254 | |
0.0.0.0/0 | Default | Default WAN route | WAN uplink |
I'm not seeing any route to 192.168.20.0/24. So you may have to 'Add a Static Route' so it knows how to get to that network. You can also gain some insights from Security Appliance>Route Table
That's the problem I'm having. I tried adding in different static routes but clearly I don't know the correct way to route it. I've been searching through tons of forums but can't seem to find an example of the correct way I should be putting in the IP's with the MX84. I think I understand since I studied up on it last night but not sure how to interpret it into the MX84.
I tried this early this morning.
192.168.20.0/24 | Static Route |
|
|
I figured since the Router A is connected to the 192.168.10.0/24 sub with 192.168.10.145, then that should be a hop to it. But from there do I need to add another route. Is this even right? This is what confuses me... Did a tracert from that and got this.
C:\>tracert 192.168.20.62
Tracing route to 192.168.20.62 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.10.254
2 <1 ms * * 192.168.10.145
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
Green | 192.168.10.0/24 | Default | Local VLAN | 192.168.10.254 |
Green | 176.16.1.0/24 | Client VPN | Client VPN | Client VPN |
Red | 192.168.20.0/24 | FN | Static Route | 192.168.10.145 |
Green | 10.0.0.0/22 | Public | Local VLAN | 10.0.0.254 |
Green | 0.0.0.0/0 | Default | Default WAN route | WAN uplink |
Without having a better idea of your topology it's hard to say what specifically is the issue but I think we are on the right track. Notice the route not functioning.
Red | 192.168.20.0/24 | FN | Static Route | 192.168.10.145 |
Dumb switches
Is Router A 192.168.20.1? If so then you probably need a route from the MX 84 to route 192.168.20.0/24 to 192.168.20.1. But before you do that you should test that the MX 84 can ping 192.168.20.1 if that is Router A's IP.
Can't ping to 192.168.20.1.
Also if you set route 192.168.20.0/24 to 192.168.20.1 it throws an error.
"There were errors in saving this configuration:
Is 192.168.20.1 the IP of Router A? If so you'll need to start working on troubleshooting why the MX can't ping Router A. Possibly some tracert's etc to see where it is failing.
Your MX needs an IP in the subnet of router A, or some link so you can create a static route. Right now you're trying to create a static route pointing to a gateway the MX doesn't have a route to. This is also why you can't ping router A from the MX as there is no L2 or L3 connectivity between those devices.