ACLs

ACL challenges. Router. Do you struggle with ACLs ... try these?

CCNA

[Challenge 1]. This challenge involves the configuration of NAT overload.
[Challenge 2]. This challenge involves the configuration of NAT overload.
[Challenge 3]. This challenge involves the configuration of TCP load distribution for NAT.
[Challenge 4]. This challenge involves the configuration of NAT for overlapping networks.
[Challenge 5]. This challenge involves the setting of logging and HTTP settings.
[Challenge 6]. This challenge involves the configuration of an access-map.
[Challenge 7]. This challenge involves the configuration VLAN filtering to drop TCP packets.
[Challenge 8]. This challenge involves the configuration VLAN filtering to forward TCP packets.
[Challenge 9]. This challenge involves the configuration of a standard ACL.
[Challenge 10]. This challenge involves the configuration of a standard ACL.
[Challenge 11]. This challenge involves the configuration of an extended ACL.
[Challenge 12]. This challenge involves the configuration of named ACLs.
[Challenge 13]. Test.
[Challenge 14]. This challenge involves the configuration of a passive interface with EIGRP using a distribute-list.
[Challenge 15]. This challenge involves the creation of policy-based routing.

CCNP Route

[Challenge 1]. This challenge involves the configuration of BGP with a route-map.
[Challenge 2]. This challenge involves the configuration of BGP for a default local-preference using a route-map.
[Challenge 3]. This challenge involves the configuration of BGP by setting a metric.
[Challenge 4]. This challenge involves the configuration of BGP for a distribution list.
[Challenge 5]. This challenge involves the configuration of BGP for a distribution list.
[Challenge 6]. This challenge involves the configuration of distribute-lists for RIP in order to define the routing information that is sent or received.
[Challenge 7]. This challenge involves the configuration of distribute-lists for RIP in order to define the routing information that is sent or received on a given interface.`
[Challenge 8]. This challenge involves the configuration of distribute-lists for RIP in order to define the routing information that is sent or received on a given interface.
[Challenge 9]. This challenge involves the creation of policy-based routing.
[Challenge 10]. This challenge involves the configuration of the redistribution of routes for a limited range of networks.

Remote Access

[Challenge 1]. This challenge involves the configuration of ISDN
[Challenge 2]. This challenge involves setting up a crypto map and applying it to an interface.
[Challenge 3]. This challenge involves setting an access-list to allow IPSec.
[Challenge 4]. This challenge involves the configuration of frame relay for priority queuing.
[Challenge 5]. This challenge involves the configuration of CBWFQ.
[Challenge 6]. This challenge involves the configuration of dynamic NAT.
[Challenge 7]. This challenge involves the configuration of NAT overload.
[Challenge 8]. This challenge involves the configuration of NAT overload without an address pool.
[Challenge 9]. This challenge involves the configuration of TCP load distribution for NAT.
[Challenge 10]. This challenge involves the configuration of NAT for overlapping networks.
[Challenge 11]. This challenge involves the configuration of security of a router.
[Challenge 12]. This challenge involves the configuration of PPPoA with NAT.

CCNP Switch

[Challenge 1]. This challenge involves the setting of logging and HTTP settings.
[Challenge 2]. This challenge involves the configuration of an access-map.
[Challenge 3]. This challenge involves the configuration VLAN filtering to drop TCP packets.
[Challenge 4]. This challenge involves the configuration VLAN filtering to forward TCP packets
[Challenge 5]. This challenge involves manually defining a rendezvous point (RP) for a multicast group.
[Challenge 6]. This challenge involves auto-RP for an existing sparse-mode cloud in mulitcast routing.
[Challenge 7]. This challenge involves preventing candidate RP spoofing.
[Challenge 8]. IP Mulitcast can use serveral different types of protocols, such as PIM, DVMRP, IGRP and CGMP.
[Challenge 9]. This challenge defines a mulitcast ACL, and restricts IP Multicast.
[Challenge 10]. This challenge involves the configuration of QoS.
[Challenge 11]. This challenge involves the configuration of an access-class for Web access security.
[Challenge 12]. This challenge involves the configuration to deny access for a single host to the Web server.
[Challenge 13]. This challenge involves the configuration which permits a single host access to a Telnet server.
[Challenge 14]. This challenge involves the configuration which denies a single host access a Telnet server.
[Challenge 15]. This challenge involves the configuration of an restriction on a user.
[Challenge 16]. This challenge involves the configuration of a single host access to SNMP.
[Challenge 17]. This challenge involves the configuration of security of a switch.
[Challenge 18]. This challenge involves the configuration of a MAC ACL.

Wireless

[Challenge 1]. This challenge involves the configuration of a standard access-list
[Challenge 2]. This challenge involves the configuration of an extended ACL.
[Challenge 3]. This challenge involves the configuration of security of the wireless access point.
[Challenge 4]. This challenge involves the configuration of filtering incoming MAC addresses for D0.
[Challenge 5]. This challenge involves the configuration of filtering outgoing MAC addresses for D0.
[Challenge 6]. This challenge involves the configuration of filtering outgoing MAC addresses for D0 for a source and destination MAC address.
[Challenge 7]. This challenge involves the configuration of filtering outgoing MAC addresses for D0 for a source and destination MAC address.
[Challenge 8]. This challenge involves the configuration of filtering incoming MAC addresses for D0.
[Challenge 9]. This challenge involves defining SSID redirection with ACLs.

PIX/ASA

[Challenge 1]. This challenge involves the configuration of an access-list.
[Challenge 2]. This challenge involves denying certain MAC addresses.
[Challenge 3]. The new PIX image supports a modular policy framework.
[Challenge 4]. This challenge applies an ACL to the E0 interface.
[Challenge 5]. This challenge involves diverting all the traffic to the AIP SSM in promiscuous mode. If the AIP SSM cards then fails, all the traffic will be blocked.
[Challenge 6]. This challenge involves defines an embryonic TCP connection timeout.
[Challenge 7]. This challenge involves defines the maximum number of embryonic TCP connections.
[Challenge 8]. This challenge involves the PIX check TCP checksums.
[Challenge 9]. This challenge involves the PIX checks the maximum segment size for TCP details.
[Challenge 10]. This challenge involves the preventing inconsistent TCP re-transmissions.
[Challenge 11]. This challenge involves the setting the limit for out-of-sequence TCP segments.
[Challenge 12]. This challenge involves checking the TCP reserved bits.
[Challenge 13]. This challenge involves checking if the SYN flag appears with Data.
[Challenge 14]. This challenge involves disabling TTL evasion protection
[Challenge 15]. This challenge involves allowing or denying TCP Window variations in TCP connections.
[Challenge 16]. This challenge involves defining the transparent firewall mode, and to enable EtherType access filtering.
[Challenge 17]. This challenge involves the preventing inconsistent TCP re-transmissions.
[Challenge 18]. This challenge involves the preventing inconsistent TCP re-transmissions.
[Challenge 19]. This challenge involves configurating external access to an email server on the DMZ.
[Challenge 20]. This challenge involves defining a Level 3 ACL and applying it to an interface.
[Challenge 21]. This challenge involves configurating external access to an email server on the DMZ.
[Challenge 22]. The ASA device supports a time-range for ACLs, such as defining an access-list for a weekend, or for specific day. It also includes two configuration elements for AAA settings (not linked to time-ranges).
[Challenge 23]. The PIX/ASA can use access-lists to define the groups that hosts will join (using the igmp access-list listno command on the defined interface).
[Challenge 24]. A standard ACL can be used to define the limits of a multicast boundary.
[Challenge 25]. IPv6 ACLs operate in a same way as normal ACLs, but operate on IPv6 addresses.
[Challenge 26]. The PIX/ASA can authenticate users before they make connections.
[Challenge 27]. In the previous challenge an ACL was used to define the traffic to be authenticated.

CCNP ISCW

[Challenge 1]. This challenge involves the configuration of a standard ACL.
[Challenge 2]. This challenge involves the configuration of a standard ACL.
[Challenge 3]. This challenge involves the configuration of an extended ACL.
[Challenge 4]. This challenge involves the configuration of named ACLs.
[Challenge 5]. This challenge involves the configuration of security of a switch.
[Challenge 6]. This challenge involves the configuration of a priority group and route-cache
[Challenge 7]. This challenge involves the configuration of restrictions on the local HTTP server.
[Challenge 8]. This challenge involves the configuration of the HTTP server which denies a single host.
[Challenge 9]. This challenge involves the configuration of permiting a single host access to the Telnet server.
[Challenge 10]. This challenge involves the configuration to deny a single host access to the Telnet server.
[Challenge 11]. This challenge involves the configuration of a context based access-list (CBAC).
[Challenge 12]. This challenge involves the configuration to deny an incoming SYN packet.
[Challenge 13]. This challenge involves setting up a crypto map and applying it to an interface.
[Challenge 14]. This challenge involves setting an access-list to allow IPSec
[Challenge 15]. This challenge involves configurating external access to an email server on the DMZ.
[Challenge 16]. This challenge involves the configuration of security of a router.
[Challenge 17]. This challenge involves the configuration of PPPoA with NAT.
[Challenge 18]. This challenge involves configuring intercept.
[Challenge 19]. This challenge involves the configuration of login restrictions, and defining an access-list to define the hosts that are allowed to login in the Quiet-mode.