User manual JUNIPER NETWORKS JUNOS OS 10.3 LN1000 MOBILE SECURE ROUTER USER GUIDE 8-26-2010

[. . . ] JUNOS OS LN1000 Mobile Secure Router User Guide ® Release 10. 3 Published: 2010-08-26 Copyright © 2010, Juniper Networks, Inc. Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, California 94089 USA 408-745-2000 www. juniper. net This product includes the Envoy SNMP Engine, developed by Epilogue Technology, an Integrated Systems Company. This program and its documentation were developed at private expense, and no part of them is in the public domain. This product includes memory allocation software developed by Mark Moraes, copyright © 1988, 1989, 1993, University of Toronto. [. . . ] The shelf management system can then download a new configuration to the new interface. A location pool can specify IP addresses and subnet masks for multiple locations (relative positions of cards within a shelf). You can configure an IP interface to obtain an IP address and subnet mask from a selected location pool instead of specifying an explicit IP address and subnet mask. You can configure a maximum of 10 location-based IP address pools, each with a unique name. A pool entry contains a location Copyright © 2010, Juniper Networks, Inc. 25 Junos OS LN1000 Mobile Secure Router User Guide index that has a unique value within its pool and an IP address and subnet mask that do not have to be unique. You can also define additional attributes for the pool entry as required. In the existing IP interface configuration, you can specify a location-based IP address pool instead of an explicit IP address and subnet mask. You can configure an IP interface using one of these IP address specifications types, but not both. An IPv4 address can be configured for an IP interface as well as an IP pool. Configuring Location-Based IP Address Pools To configure IP address pools, perform the following tasks: 1. Configure a pool entry that contains a location index, an IP address, and subnet mask. Configure one IP address and subnet mask from the pool entry assigned to the IP interface. Configure up to 10 location-based address pools, each with a unique name. Configure one IP address from each pool assigned to the IP interface. 2. 3. 4. Example: Configuring a Location-Based IP Address Pool This configuration example creates two IPv4 and one IPv6 location-based IP address pools, and selects one IPv4 and one IPv6 pool each for an IP interface. [edit] access { address-assignment { location-pool { ipv4poolX { family inet { location { 1 address 10. 0. 0. 1/24; 2 address 10. 0. 0. 2/24; 3 address 172. 0. 0. 3/24; 4 address 172. 0. 0. 4/24; 5 address 192. 0. 0. 5/24; 32 address 192. 0. 0. 32/24; } } } ipv4poolY { family inet { location { 1 address 10. 0. 0. 11/24; 3 address 172. 0. 0. 33/24; 5 address 192. 0. 0. 54/24; } } } 26 Copyright © 2010, Juniper Networks, Inc. Chapter 4: Location-Based IP Address Pools Ipv6poolZ { family inet6 { location { 1 address fec0:1:1:1::1/64; 3 address fec0:1:1:1::3/64; 5 address fec0:1:1:1::5/64; } } } } } } [edit] interfaces ge-0/0/0 { unit 0 { family inet { location-pool-address ipv4poolX; } family inet6 { location-pool-address ipv6poolZ; } } } Using this configuration example, a router in slot 3 has an IPv4 address of 172. 0. 0. 3/24 and an IPv6 address of fec0:1:1:1::3/64 assigned to gigabit Ethernet interface 0/0/0. If you move the router to slot 5, it has an IPv4 address of 192. 0. 0. 5/24 and an IPv6 address of fec0:1:1:1::5/64 assigned to gigabit Ethernet interface 0/0/0. Verifying and Managing Location-Based IP Address Pools Purpose Action Meaning Display location-based IP address pools. user@host> show access address-assignment location-pool If a pool name is not specified, all pool entries are displayed. Pool Family ipv4poolX inet ipv4poolX inet ipv4poolX inet ipv4poolX inet ipv4poolX inet ipv4poolX inet ipv4poolY inet ipv4poolY inet ipv4poolY inet ipv6poolZ inet6 ipv6poolZ inet6 ipv6poolZ inet6 Location 1 2 3 4 5 32 1 3 5 1 3 5 IP address 10. 0. 0. 1/24 10. 0. 0. 2/24 172. 0. 0. 3/24 172. 0. 0. 4/24 192. 0. 0. 5/24 192. 0. 0. 32/24 10. 0. 0. 11/24 172. 0. 0. 33/24 192. 0. 0. 55/24 fec0:1:1:1::1/64 fec0:1:1:1::3/64 fec0:1:1:1::5/64 Related Topics · For more information, see the Junos OS System Basics and Services Command Reference Copyright © 2010, Juniper Networks, Inc. 27 Junos OS LN1000 Mobile Secure Router User Guide 28 Copyright © 2010, Juniper Networks, Inc. CHAPTER 5 Configuring Point-to-Point Protocol over Ethernet This chapter includes the following topics: · · · PPPoE Overview on page 29 Configuring PPPoE Interfaces on page 31 Verifying a PPPoE Configuration on page 33 PPPoE Overview PPPoE establishes a point-to-point connection between the client and the server, also called an access concentrator. Multiple hosts can be connected to the services router, and their data can be authenticated, encrypted, and compressed before the traffic is sent to the PPPoE session on the services router. PPPoE is easy to configure and enables services to be managed on a per-user basis rather than on a per-site basis. The PPPoE interface to the access concentrator can be a Fast Ethernet interface or a Gigabit Ethernet interface. If the interface is either Fast Ethernet or Gigabit Ethernet, use a PPPoE encapsulation. PPPoE Stages PPPoE has two stages, the discovery stage and the PPPoE session stage. In the discovery stage, the client discovers the access concentrator by identifying the Ethernet media access control (MAC) address of the access concentrator and establishing a PPPoE session ID. In the PPPoE session stage, the client and the access concentrator build a point-to-point connection over Ethernet, based on the information collected in the discovery stage. The LN1000 router acts as an access concentrator. PPPoE Discovery Stage A router initiates the PPPoE discovery stage by broadcasting a PPPoE active discovery initiation (PADI) packet. To provide a point-to-point connection over Ethernet, each PPPoE session must learn the Ethernet MAC address of the access concentrator and establish a session with a unique session ID. [. . . ] In addition, the logical interface configured by the radio interface can only be referenced by a single radio. radio-name--Name of the R2CP radio. Options The remaining statements are explained separately. Required Privilege Level Related Topics routing--To view this statement in the configuration. routing-control--To add this statement to the configuration. · R2CP Radio-to-Router Protocol Overview on page 45 radio-interface Syntax Hierarchy Level Release Information Description Options radio-interface interface unit unit; [edit protocol r2cp radio radio-name] Statement introduced in Junos OS Release 10. 2. Configure the attributes that identify the VLANs managed through the R2CP protocol. interface--Name of the interface. [. . . ]