<div>
<div class="content wysiwyg-content">
I have a MPLS connection from my main building to a remote building. &nbsp;The Cisco router has a VLAN with the IP address 10.44.105.5. This interface connects to a HP core switch VLAN 10.44.105.2, which is behind the firewall.<br />
<br />
We have two ISP coming into the Main Building, I just replaced my old load balance &nbsp;with a new Fat Pipe. The Fat pipe has three WAN ports and one LAN port. The LAN port can answer to more then one IP address. As of now the LAN is connected to the outside interface of my firewall, using a pubic IP address. I want the MPLS traffic to pas thru the fat pipe but not the firewall.<br />
<br />
I thinking I could connected the LAN port of the fat pipe to the VLAN on my core switch, and also connected the outside interface to the same VLAN,and added a IP of 10.44.105.3 to the LAN port of the Fat pipe. That way MPLS 10.44.105.x will still be routed by the core switch and traffic going to the outside interface of firewall will just be pass to the firewall. &nbsp; <br />
<br />
But I am not sure this will work?<br />
<br />
Thanks for any help with this problem.
</div>
</div>


I have a MPLS connection from my main building to a remote building.  The Cisco router has a VLAN with the IP address 10.44.105.5. This interface connects to a HP core switch VLAN 10.44.105.2, which is behind the firewall.

We have two ISP coming into the Main Building, I just replaced my old load balance  with a new Fat Pipe. The Fat pipe has three WAN ports and one LAN port. The LAN port can answer to more then one IP address. As of now the LAN is connected to the outside interface of my firewall, using a pubic IP address. I want the MPLS traffic to pas thru the fat pipe but not the firewall.

I thinking I could connected the LAN port of the fat pipe to the VLAN on my core switch, and also connected the outside interface to the same VLAN,and added a IP of 10.44.105.3 to the LAN port of the Fat pipe. That way MPLS 10.44.105.x will still be routed by the core switch and traffic going to the outside interface of firewall will just be pass to the firewall.   

But I am not sure this will work?

Thanks for any help with this problem.

MPLS LAN port on Fat Pipe

Transmission Control Protocol/Internet Protocol (TCP/IP) is the set of networking protocols that define end-to-end connectivity specifying how data should be packeted, addressed, transmitted, routed and received at the destination. This functionality is organized into four abstraction layers which are used to sort all related protocols according to the scope of networking involved.

TCP/IP

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

Networking

Networking hardware includes the physical devices facilitating the use of a computer network. Typically, networking hardware includes gateways, routers, network bridges, modems, wireless access points, networking cables, line drivers, switches, hubs, and repeaters. But it also includes hybrid network devices such as multilayer switches, protocol converters, bridge routers, proxy servers, firewalls, network address translators, multiplexers, network interface controllers, wireless network interface controllers, ISDN terminal adapters and other related hardware.