Document No. FO1101 Issue Date: Work Group: FibreOP Technical Team October 31, 2013 FINAL:



Similar documents
Document No. FO1004 Issue Date: Draft: Work Group: FibreOP Technical Team July 23, 2013 Final: Single Static IP Customer Owned LAN Router Support

Document No. FO1001 Issue Date: Draft: Work Group: FibreOP Technical Team October 1, 2013 Final:

Multi-Homing Security Gateway

Enabling NAT and Routing in DGW v2.0 June 6, 2012

How To - Configure Virtual Host using FQDN How To Configure Virtual Host using FQDN

How To Load balance traffic of Mail server hosted in the Internal network and redirect traffic over preferred Interface

Application Description

Configuring a customer owned router to function as a switch with Ultra TV

Chapter 4 Customizing Your Network Settings

Network Security Topologies. Chapter 11

LAN TCP/IP and DHCP Setup

Vocia MS-1 Network Considerations for VoIP. Vocia MS-1 and Network Port Configuration. VoIP Network Switch. Control Network Switch

Chapter 4 Customizing Your Network Settings

Technical Support Information

Owner of the content within this article is Written by Marc Grote

Evaluation guide. Vyatta Quick Evaluation Guide

For extra services running behind your router. What to do after IP change

Chapter 3 Security and Firewall Protection

White Paper Copyright 2011 Nomadix, Inc. All Rights Reserved. Thursday, January 05, 2012

Quick Note 53. Ethernet to W-WAN failover with logical Ethernet interface.

Interconnecting Cisco Network Devices 1 Course, Class Outline

Supporting Multiple Firewalled Subnets on SonicOS Enhanced

Chapter 3 LAN Configuration

1 PC to WX64 direction connection with crossover cable or hub/switch

Internet Services. Amcom. Support & Troubleshooting Guide

Chapter 5 Customizing Your Network Settings

PowerLink Bandwidth Aggregation Redundant WAN Link and VPN Fail-Over Solutions

Basic IPv6 WAN and LAN Configuration

Computer Networks. Introduc)on to Naming, Addressing, and Rou)ng. Week 09. College of Information Science and Engineering Ritsumeikan University

Load Balancing ContentKeeper With RadWare

Setting up and creating a Local Area Network (LAN) within Windows XP by Buzzons

This article describes a detailed configuration example that demonstrates how to configure Cyberoam to provide the access of internal resources.

Chapter 1 Connecting Your Router to the Internet

1:1 NAT in ZeroShell. Requirements. Overview. Network Setup

CCNA R&S: Introduction to Networks. Chapter 9: Subnetting IP Networks

Broadband Phone Gateway BPG510 Technical Users Guide

: Interconnecting Cisco Networking Devices Part 1 v2.0 (ICND1)

VLSM & IP ADDRESSING EXAMPLE QUESTIONS with answers;

Networking Basics for Automation Engineers

INTERCONNECTING CISCO NETWORK DEVICES PART 1 V2.0 (ICND 1)

DSL-G604T Install Guides

Firewall Defaults and Some Basic Rules

Knowledgebase Solution

Session Title: Exploring Packet Tracer v5.3 IP Telephony & CME. Scenario

UIP1868P User Interface Guide

Apache CloudStack 4.x (incubating) Network Setup: excerpt from Installation Guide. Revised February 28, :32 pm Pacific

Lab Configuring Access Policies and DMZ Settings

- Introduction to Firewalls -

IPv6 in Axis Video Products

enable: no, log: by-profile enable: no, log: by-profile enable: no, log: by-profile

PPTP Server Access Through The

Note: This case study utilizes Packet Tracer. Please see the Chapter 5 Packet Tracer file located in Supplemental Materials.

Figure 41-1 IP Filter Rules

Initial Access and Basic IPv4 Internet Configuration

Creating a VPN with overlapping subnets

Com.X Router/Firewall Module. Use Cases. White Paper. Version 1.0, 21 May Far South Networks

Layer 2 Networking. Overview. VLANs. Tech Note

How to configure your Thomson SpeedTouch 780WL for ADSL2+

Actiontec GT784WN Router

MN-700 Base Station Configuration Guide

Using Remote Desktop Software with the LAN-Cell

Chapter 1 Personal Computer Hardware hours

Installation of the On Site Server (OSS)

ADTRAN 3120 / 3130 Internet Configuration Guide

Using IPsec VPN to provide communication between offices

VLAN 802.1Q. 1. VLAN Overview. 1. VLAN Overview. 2. VLAN Trunk. 3. Why use VLANs? 4. LAN to LAN communication. 5. Management port

Lehrstuhl für Informatik 4 Kommunikation und verteilte Systeme. Firewall

Configuring IPsec VPN between a FortiGate and Microsoft Azure

SSVP SIP School VoIP Professional Certification

Packet Tracer - Subnetting Scenario 1 (Instructor Version)

Skills Assessment Student Training Exam

How to configure VLAN and route failover

LinkProof DNS Quick Start Guide

1- and 2-Port Fast Ethernet High-Speed WAN Interface Cards for Cisco 1841, 2800, and 3800 Series Integrated Services Routers

DMZ Network Visibility with Wireshark June 15, 2010

IP Address and Pre-configuration Information

ICS 351: Today's plan. IP addresses Network Address Translation Dynamic Host Configuration Protocol Small Office / Home Office configuration

Configuring Network Address Translation (NAT)

CREATING AN IKE IPSEC TUNNEL BETWEEN AN INTERNET SECURITY ROUTER AND A WINDOWS 2000/XP PC

Firewall Defaults, Public Server Rule, and Secondary WAN IP Address

GUIDE. CTRLink. EIPR Skorpion Wired and Wireless IP Routers. EIPR Series

Using Cisco UC320W with Windows Small Business Server

Firewall VPN Router. Quick Installation Guide M73-APO09-380

Appendix A: Configuring Firewalls for a VPN Server Running Windows Server 2003

IOS NAT Load Balancing with Optimized Edge Routing for Two Internet Connections

Chapter 9 Monitoring System Performance

FSM73xx GSM73xx GMS72xxR Shared access to the Internet across Multiple routing VLANs using a Prosafe Firewall

Using Remote Desktop Software with the LAN-Cell 3

M2M Series Routers. Port Forwarding / DMZ Setup

IOS NAT Load Balancing for Two ISP Connections

Configuring a LAN SIParator. Lisa Hallingström Paul Donald Bogdan Musat Adnan Khalid Per Johnsson Rickard Nilsson

Chapter 3 Connecting the Router to the Internet

Tutorial 3. June 8, 2015

Configuration Guide for connecting the Eircom Advantage 4800/1500/1200 PBXs to the Eircom SIP Voice platform.

Security+ Guide to Network Security Fundamentals, Fourth Edition. Chapter 6 Network Security

WAN Failover Scenarios Using Digi Wireless WAN Routers

configure WAN load balancing

Barracuda Link Balancer

What is VLAN Routing?

Configuration Guide. How to Configure SSL VPN Features in DSR Series. Overview

Transcription:

Document No. FO1101 Issue Date: Work Group: FibreOP Technical Team October 31, 2013 FINAL: Title: FibreOP Business Internet 5 Static IP Customer Configuration Version 1.1 Summary: This document provides background information and guidance for customers who purchase the Bell Aliant FibreOP Business Internet Static 5 IP Base Service. This service offering has been designed giving customers the freedom to use their own Router or Firewall. Details describing how the Customer Router or Firewall should interface with the Bell Aliant Juniper SRX will be provided along with functional guidelines customers need to consider for their own networking requirements. Illustration:

Table of Contents Figures... 2 Background... 3 General... 4 Customer Router/Firewall... 5 Other considerations:... 6 Glossary... 7 Figures Figure 1 Customer Router WAN connectivity... 5

Background The Bell Aliant FibreOP Business Internet Static Five (5) IP service uses a Juniper SRX as the demarcation device for the service. A demarcation point is the physical network location where up to, Bell Aliant can confirm the service is functioning properly. A LAN and WAN port are used on the Juniper SRX. The LAN port connects to the customer equipment and is the demarcation point for Bell Aliant. The WAN port connects to the co-located Bell Aliant ONT for the FibreOP connection to the Internet. This document will focus on the inter-networking connectivity between the Customer Router/Firewall and the Bell Aliant Juniper SRX. More specifically, details are included to ensure customers understand their own networking requirements.

General The FibreOP Business Internet Static Five (5) IP service has been implemented using a /29 subnet (mask 255.255.255.248) connecting a Bell Aliant Juniper SRX device to the customer network. The Juniper SRX is assigned the first usable IP address from the subnet and acts as the customer s gateway to the Internet. Note that the Juniper SRX routes all traffic destined for this subnet without interference. No filtering, translation, or blocking is configured on the SRX for the customer s network. The rest of the subnet is available for the customer to allocate as required. Customers are encouraged to use the next available IP address for their Router / Firewall, and allocate the remaining IP addresses to public-facing devices via NAT on their Router / Firewall. Although it is possible to connect devices in front of the Customer Router / Firewall, Bell Aliant recommends against this for security reasons. From the Internet all Customer IP addresses within Public /29 IP subnets will be reachable. Static IP Routes will be used on Bell Aliant equipment to ensure traffic is sent to its appropriate next-hop as per: From the Internet to Customer for public /29: Internet WAN port of SRX Public /29 subnet From the Customer Router to Internet: Customer Router LAN port of SRX (first usable IP from /29) Internet

Customer Router/Firewall The Fast Ethernet WAN port on the Customer Router/Firewall should be configured as follows: IP address: Second IP from assigned /29 Default gateway: First IP from assigned /29 Protocols: IPv4 Routing: Static Routes AutoNeg: Yes Duplex: Auto Speed: Auto Encapsulation: Connect to: Ethernet (No 802.1Q VLAN Tagging on WAN port) Physical LAN port fe-0/0/1 on the Bell Aliant Juniper SRX DNS: Primary DNS IP Secondary DNS IP 47.55.55.55 142.166.166.166 Figure 1 Customer Router WAN connectivity Note: Shown above, the Bell Aliant support demarcation point is the customer facing LAN port (fe-0/0/1) on the Juniper SRX.

Other considerations: Identifying all of the needs in a Customer Router/Firewall is a difficult task. Both the requirements of the FibreOP Business Internet Static Five (5) IP service and the Customer s own LAN network must be understood. Below are guidelines to be considered if the FibreOP Static IP service has been purchased: - The public /29 subnet is completely controlled by the customer. This includes how and where the IP addresses are used. o The first usable IP address from the subnet is assigned to the SRX internal interface port fe-0/0/1. o This first usable IP address should be configured as the default gateway to the Internet on the Customer Router/Firewall. - The WAN port on the Customer Router/Firewall must be configured with an IP from the public /29 subnet the second usable IP address from the subnet is suggested but not required. - A dedicated Fast Ethernet connection will be used to connect the customers Router/Firewall (WAN port) to the SRX (LAN port fe-0/0/1). - Public addresses from the /29 subnet can be Network Address Translated (NAT) to Private addresses located on the customer LAN. Several options are available for configuring NAT including: a. 1 Many (1 Public to Many Private) b. 1-1 (1 Public to 1 Private) c. Many 1 (Many Public to 1 Private) Bell Aliant recommends the use of NAT to translate private IP addresses of servers for additional security control. Where possible, servers should also be placed in a secure network segment (DMZ) off the customer Router/Firewall rather than directly on the customer LAN. - As with any Bell Aliant FibreOP service, Speed Tests and performance can be validated via: o http://speedtest.bellaliant.net

Glossary DMZ (Demilitarized Zone). In computer networks, a DMZ (demilitarized zone) is a computer host or small network inserted as a "neutral zone" between a company's private network and the outside public network. It helps to prevent outside users from getting direct access to a server that has company data. PAT (Port Address Translation). PAT allows multiple devices on the same customer LAN to share 1 Static Public IP address. The Customer Router/Firewall would append a unique port number to the internal IP allowing it to be unique. NAT (Network Address Translation). Similar to above, NAT allows a network device to assign a public IP address to a large private network using addresses in a private range: Private IP Range Class Address Range A 10.0.0.0 10.255.255.255 B 172.16.0.0 172.31.255.255 C 192.168.0.0 192.168.255.255 /29 Number of mask bits; can also written as 255.255.255.248.