Skip to main content

CCIE-LAB-WLC

1) tacacs user can be an admin on WLC but the ‘shell profile’ needs to have one attribute: role1=ALL (double check if there is no space!!!!)

Authorization Result 
{Type=Authorization; Author-Reply-Status=PassAdd; AVPair=role1=ALL; }

2) radius user can be an admin on WLC but the user needs to have following attributes:
 
IETF Service-Type attributes:

  NAS Prompt for readonly
  Administrative for readwrite
  Callback Administrative for lobbyadmin

3) adding a new admin user on WLC:
 
config mgmtuser add testuser testpAss1 read-write

4) you can have different rules for malicious and trusted networks:
 
(Cisco Controller) >show rogue rule summary 

Priority Rule Name               State    Type          Match Hit Count
-------- ----------------------- -------- ------------- ----- ---------
1        KNOWN                   Enabled  Friendly      All   0       
2        UNKNOWN                 Enabled  Malicious     Any   0       

(Cisco Controller) >

5) you can manually add (MAC address) which APs are trusted:
 
(Cisco Controller) >show auth-list 

Authorize MIC APs against AAA ................... enabled
Authorize LSC APs against Auth-List ............. disabled
APs Allowed to Join
  AP with Manufacturing Installed Certificate.... yes
  AP with Self-Signed Certificate................ no
  AP with Locally Significant Certificate........ no

Mac Addr                  Cert Type    Key Hash
-----------------------   ----------   ------------------------------------------
00:06:f6:16:f0:c5         MIC          


(Cisco Controller) >

6) mac filtering per each WLAN

7) exclusion
  • timeout under WLAN
  • policy under security tab
8) flexconnect
  • under WLAN you enable this feature (Advanced tab)
  • under each AP you need to specify 'AP mode’=flexconnect
  • DHCP enabled on local switch:
SW5#show ip dhcp binding 
Bindings from all pools not associated with VRF:
IP address          Client-ID/              Lease expiration        Type
                    Hardware address/
                    User name
136.1.47.100        0100.06f6.16f0.c5       Mar 02 1993 12:28 AM    Automatic
136.1.147.2         01fc.7516.88bd.19       Mar 02 1993 12:56 AM    Automatic
SW5#

9) ACL downloaded from ACS

You need to add one Radius attribute:
User-Name=peapuser
 Class=CACS:ACS2/210041497/3
 Airespace-ACL-Name=PEAP-ACL

Comments

Post a Comment

Popular posts from this blog

What should you know about HA 'override enabled' setting on Fortigate?

High availability is mandatory in most of today's network designs. Only very small companies or branches can run their business without redundancy. When you have Fortigate firewall in your network you have many options to increase network availability. You can use Fortigate Clustering Protocol ( FGCP ) or Virtual Router Redundancy Protocol ( VRRP ). FGCP has two modes: 'override' disabled (default) and 'override' enabled . I'm not going to explain how to set up HA as you can find many resources on Fortinet websites: https://cookbook.fortinet.com/high-availability-two-fortigates-56/ https://cookbook.fortinet.com/high-availability-with-fgcp-56/ Let's recap what is the main difference between them. The default HA setting is 'override' disabled and this is an order of selection an active unit: 1) number of monitored interfaces - when both units have the same number of working (up) interfaces check next parameter 2) HA uptime - an ...
8 comments
Read more

FortiGate and GRE tunnel

Recently I worked on one project where a client requested to re-route web traffic to the GRE tunnel to perform traffic inspection. I would like to share with you what is required if you configure it on FortiGate. We need a new GRE interface and policy base routing (PBR) to change the route for specific source IPs. Of course you need firewall policies to permit the traffic. Let's start with GRE interface. Unfortunately you can't configure it using the GUI, only CLI is the option: config system gre-tunnel edit "gre1" set interface "port1" set local-gw 55.55.55.55 set remote-gw 44.44.44.44 next end When the end peer is Cisco router, you need to set the IP for the GRE interface: config system interface edit gre1 set ip 192.168.10.10 255.255.255.255 set remote-ip192.168.10.20 end In next step we need to fix routing. We need the alternate path via GRE but to keep the route in the active routing table you need to set the same AD (adminis...
Post a Comment
Read more

Inpection of asymmetric sessions on FortiGate

There is one feature available on FortiGate, and I think you should know it, as it modifies a bit what we know about stateful firewalls. In past every packet was treated individually and you had to create policies in both directions. With stateful firewalls we can track connections, and by checking couple of attributes, we can treat them as part of the same session. For example when you initiate connection from a host1 to host2, the returning connection from host2 to host1 will be treated as part of the same connection (session). They have to have the same source/destination and destination/source IPs, port numbers and interfaces.There is an exception from this rule and FortiGate in some specific cases can accept connections on port which was not used in the initial connection. Let me explain how it works on the below example:      The host1 has a default gateway on R1 (10.0.1.2), but you may notice that it is not the optimal path to host2 subnet. When we analyze ...
1 comment
Read more