I now need to configure the Bridge Virtual Interface (BVI). This is where I put the IP address for the WAP: Cisco-WAP(config-if)#interface BVI1 Cisco-WAP(config-if)#ip address 192.168.1.3 255.255.255.0 Cisco-WAP(config-if)#no shut Since I've configured the WAP as a bridge, I need to assign a default gateway using the ip default-gateway command: Cisco-WAP(config-if)#ip default-gateway 192.168.1.1 Now I need to allow IP through the bridge: Cisco-WAP(config)#bridge 1 route ip At this point, if I've done everything properly, I should have wireless clients associating. I can check this with the show dot11 associations command: Cisco-WAP#sho dot11 associations 802.11 Client Stations on Dot11Radioo: SSID [Coolness] : MAC Address IP address Device Parent State 001e.5275.6ee0 192.168.1.124 unknown Assoc 7c6d.62a4.6aad 192.168.1.120 unknown Assoc After leaving this WAP up for a while and running some file transfers over it, I ran show interface on the radio interface. As you can see, it's pretty easy to overrun the wireless interface, especially with multiple heavy users. Wireless is great for convenience, but it's just not designed for serious performance: Cisco-WAP#sho int dot11Radio 0 Dot11Radio0 is up, line protocol is up Hardware is 802.11G Radio, address is 0012.7f52.de80 (bia 0012.7f52.de80) MTU 1500 bytes, BW 54000 Kbit, DLY 1000 usec, reliability 255/255, txload 26/255, rxload 25/255 Encapsulation ARPA, loopback not set ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:13, output 00:00:01, output hang never Last clearing of "show interface" counters 00:14:57 Input queue: 0/75/15/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/30 (size/max) 5 minute input rate 5420000 bits/sec, 502 packets/sec 5 minute output rate 5510000 bits/sec, 502 packets/sec 377892 packets input, 523715591 bytes, 0 no buffer Received 38 broadcasts, 0 runts, 0 giants, o throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 input packets with dribble condition detected Configuring a WAP 3