oip trust service-policy output MPLS-QoS Here's the inside Ethernet interface: interface FastEtherneto/o description [ Branch 10 LAN ] ip address 10.10.10.1 255.255.255.128 duplex auto speed auto auto qos voip trust service-policy output MPLS-QoS Next, I'll add a loopback address for routing, which will be useful for VPN failover (not shown here): interface Loopbacko description [ Branch 10 Loopback ] ip address 10.10.10.129 255.255.255.255 Finally, we need some BGP configuration SO that we can learn and advertise routes through the cloud: router bgp 65010 no synchronization bgp log-neighbor-changes network 10.10.10.0 mask 255.255.255.128 network 10.10.10.129 mask 255.255.255.255 aggregate-address 10.10.10.0 255.255.255.0 summary-only neighbor 10.255.255.1 remote-as 65001 neighbor 10.255.255.1 update-source Serial0/3/0 neighbor 10.255.255.1 version 4 neighbor 10.255.255.1 prefix-list Aggregate out no auto-summary ip prefix-list Aggregate seq 5 permit 10.10.10.0/24 As you can see, there is nothing MPLS-specific about this configuration. No mention of labels, hop popping, or anything other than routing, QoS, and typical IP address entries. Chapter 24: MPLS CHAPTER 25 Access Lists The technical name for an access list is access control list. The individual entries in an access control list are called access control entries, or ACEs. The term access control list isn't often used in practice; you'll typically hear these lists referred to simply as access lists or ACLs. Access lists do more than just control access. They are the means whereby Cisco devices categorize and match packets in any number of interesting ways. Access lists are used as simple filters to allow traffic through interfaces. They are also used to define "inter- esting traffic" for ISDN dialer maps, and are used in some route maps for matching. Designing Access Lists This chapter's focus will be less on the basics of access list design, and more on making you conscious of its benefits and pitfalls. The tips and tricks in this chapter should help you 