Posted 08 August 2012 - 07:27 AM
When I saw this, I assumed that a route was needed for traffic to flow back to the remote site, so I attempted to put a rule in the main routing table that would effectively redirect traffic bound for that network back through the MPLS router from which it came in. Adding this rule did not relieve the error message displayed above. My LAN-2-LAN traffic seems to flow just fine.
Posted 08 August 2012 - 10:18 AM
Internet --- Providers router --- NG Firewall --- internal network (e.g. 172.16.0.0/16)
MPLS router --- remote network (e.g. 172.17.1.0/24)
Have you added a route to the remote network in the NG network configuration?
I.e. 172.17.1.0/24 can be reached by using the MPLS router (e.g. 172.16.0.1) as gateway/next hop.
Posted 08 August 2012 - 10:19 AM
The MPLS router should be connected to the internal network, not to the internet...
Posted 08 August 2012 - 10:53 AM
Internet->Ext. Router->Firewall (192.168.2.3)->Switch->MPLS Router (192.168.2.1)->MPLS CLOUD->MPLS Remote Router (192.168.0.1)->192.168.0.0/24 network
Yes - I entered a route just like you described (at least I believe I did it correctly). I entered the following into the "Main Routing" section as a gateway:
Target Address: 192.168.0.0/24 Gateway: 192.168.2.1 (also added network to trusted networks option)
I did not specify source or metric. Does this look incorrect?
Posted 09 August 2012 - 07:08 AM