The two ends of your MPLS link are on different subnets, so your MPLS
provider will have to route for you. You have to coordinate with them
on that (OR create your own point-to-point tunnel)
For example, YOUR site1 router needs to know that site2's 172.16.11.0/24
subnet is reachable via 10.152.8.129, but your MPLS provider's router at
10.152.8.129 would also need to know that your 172.16.11.0/24 subnet is
reachable via 10.152.8.118 (plus the return routes).
Your provider should be able to guide you.
This may be a helpful read:
http://blog.ine.com/2010/08/26/mpls-tunnels-explained/
A quick and dirty way to do this without coordinating with your service
provider would be to create a point-to-point tunnel using Site-to-site
OpenVPN or IPsec. If encryption over the MPLS network is a liability,
you can disable encryption entirely.
Good luck
-Karl
On 5/14/2014 12:27 AM, Faisal Gillani wrote:
Kluas
I apologize for this , yes this was a typo error.
Local Network information is as below.
Local Network IP settings and how can we use (OSPF / BGP) ?
Site 1
IP 172.16.0.0
Subnet 255.255.255.0
All clients in Site 1 use 172.16.1.16 (Linux Firewall) as its default
gateway it is also connected with MPLS network with above given settings
Site 2
IP 172.16.11.0
Subnet 255.255.255.0
All clients in Site 2 use 172.16.11.17 (Linux Firewall) as its default
gateway it is also connected with MPLS network with above given settings
Requirement
. Clients on both sites should be able to access each other.
. Clients on both the Sites should use 172.16.1.16 for their internet
needs
Regards
Faisal
-----Original Message-----
From: Klaus Wunder [mailto:[email protected]]
Sent: Wednesday, May 14, 2014 10:08 AM
To: [email protected]; pfSense Support and Discussion Mailing List
Subject: Re: [pfSense] using Pfsense as a router
Hello,
First of all I have a Question.
Your booth Sites use overlapping Subnets. Is it a typing error?
To come to you Routing Question. In future, are there more branch Offices
scheduled?
I think in this case a Dynamic Routing Protocol is perfekt (OSPF / BGP)
In the other case the simplest solution is to use Static Routing.
Regards
Klaus
Von meinem iPhone gesendet
Am 14.05.2014 um 06:17 schrieb "Faisal Gillani"
<[email protected]>:
Hello All
I am trying to use Pfsense as my premier router to connect my office with
other branch offices on a provider's layer 3 MPLS network.
I have disabled all NAT and packet filtering on both of my Pfsense boxes.
Also uncheck block private schemes on my WAN interfaces as the ip schemes
my
MPLS provider uses are private ones.
Below is my scenario all I want is help what to define in my static routes
or should I use dynamic routing protocols for this ?
IP Settings given by MPLS provider
Site 1
IP 10.152.8.130
Subnet 255.255.255.252
GW 10.152.8.129
Site 2
IP 10.152.8.118
Subnet 255.255.255.252
GW 10.152.8.117
Local Network IP settings
Site 1
IP 172.16.0.0
Subnet 255.255.0.0
All clients in Site 1 use 172.16.1.16 (Pfsense) as its default gateway it
is
also connected with MPLS network with above given settings
Site 2
IP 172.16.11.0
Subnet 255.255.0.0
All clients in Site 2 use 172.16.11.17 (Pfsense) as its default gateway it
is also connected with MPLS network with above given settings
Requirement
. Clients on both sites should be able to access each other.
. Clients on both the Sites should use 172.16.1.16 for their internet
needs
Thanks
Faisal
_______________________________________________
List mailing list
[email protected]
https://lists.pfsense.org/mailman/listinfo/list
_______________________________________________
List mailing list
[email protected]
https://lists.pfsense.org/mailman/listinfo/list
_______________________________________________
List mailing list
[email protected]
https://lists.pfsense.org/mailman/listinfo/list
