Skip to main content

Example, Add Cisco AP to a netwrork.

I always set a scheduled reload of the remote device just-in-case there's a chance of breaking it (I'm still learning). 10 mins should give you enough time to implement your changes, test it and save it. Depending on the site and how many admins touch the device you could in theory leave your changes unsaved for a few days just to be sure, then get an onsite person to power cycle it if problems occur.


reload in 10
config t
# config the ssid and map it to a vlan, 1 per vlan.
dot11 ssid YOUR_SSID
vlan YOUR_VLAN
authentication open 
authentication key-management wpa
wpa-psk ascii 0 YOUR_PASSWORD
 
# assign encryption to ssid
interface Dot11Radio0
encryption vlan YOUR_VLAN mode ciphers aes-ccm
ssid YOUR_SSID
 
# config the sub interfaces for dot11 radio and ethernet
interface Dot11Radio0.YOUR_VLAN
 encapsulation dot1Q YOUR_VLAN
 no ip route-cache
 bridge-group YOUR_VLAN
 bridge-group YOUR_VLAN subscriber-loop-control
 bridge-group YOUR_VLAN block-unknown-source
 no bridge-group YOUR_VLAN source-learning
 no bridge-group YOUR_VLAN unicast-flooding
 bridge-group YOUR_VLAN spanning-disabled
 
interface FastEthernet0.YOUR_VLAN
 encapsulation dot1Q YOUR_VLAN
 no ip route-cache
 bridge-group YOUR_VLAN
 no bridge-group YOUR_VLAN source-learning
 bridge-group YOUR_VLAN spanning-disabled
 
# happy?
reload cancel
 
# not happy?
wait 10 mins
 
# want to undo some stuff manually? use the "no" form.
interface Dot11Radio0.YOUR_VLAN
interface FastEthernet0.YOUR_VLAN
 
# or
no bridge-group YOUR_VLAN subscriber-loop-control
 

There's great article here that talks about bridge groups and bvi.

Labels:

Popular posts from this blog

Mac OS X "SOE" Day 7

Page Redirection > continued from day 6... In summary, here is my method for creating a Mac OS X 10.7.3 Standard Operating Environment "SOE" Image. Overview The goal is to create a "MASTER" non-booted SOE that can be used with multiple models and it multiple sites with different local requirements. My intention is to use this "MASTER" image in a manual restore procedure due to the fact netboot facilities cannot be made available to all the sites I support however the DMG files are netboot compatible. Requirements Lion Recovery Disk Assistant v1.0 "TARGET" workstation. A compatible workstation that will be used to install Mac OS X 10.7.3 and capture a DMG image(s). "ADMIN" workstation. A workstation with Disk Utility that you will use to capture your DMG image(s). External storage such as a USB HARD DISK. Setup Downloaded the Lion Recovery Disk Assi...
more...

Mac OS X "SOE" Day 6

Page Redirection > continued from day 5... Continuing on from the "firstboot" phase setup we need to script our "localiser" options. I previously set my build phase to autologin and run the firstboot script, the localiser phase essentially sits there and waits for you to run it. In my case I have an applescript GUI wrapper that requests some info to use in the localisation. I request a TAG number which is an organisational internal number and I also request a user name that will be set as the OWNER. NOTE : I ordered these specifically...not just because it makes sense logically but also technically. For example, setting the Language actually zaps a plist file (.GlobalPreferences) which you need to write to for Locale and Country info. This stuff is going to be totally dependant on your environment, as an example here is what I do. So what's the minimum we need in the "localiser" phase? Depends on how many sites you support,...
more...

Mac OS X key-based ssh login

To set up key-based SSH, you must generate the keys the two computers will use to establish and validate the identity of each other. To do this run, the following commands in Terminal: Check to see whether a .ssh folder exists in your home directory by running the command ls -ld ~/.ssh. If .ssh is listed in the output, move to step 2. If .ssh is not listed in the output, run mkdir ~/.ssh and continue to step 2. Run: cd ~/.ssh Run: ssh-keygen -b 1024 -t dsa -f id_dsa -P '' This command generates the public and private keys. The -b flag sets the length of the keys to 1,024-bits, -t indicates to use the DSA hashing algorithm, -f sets the file name as id_dsa, and -P '' sets the private key password to be null. The null private key password allows for automated SSH connections. Run: touch authorized_keys2 Run: cat id_dsa.pub >> authorized_keys2 Run: chmod 400 id_dsa The permissions on the private key must be set so that the file is not world readable. Run...
more...