<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Access-Point on Simon Žekar — unix, communications, stupidities</title><link>https://simon.zekar.com/tags/access-point/</link><description>Recent content in Access-Point on Simon Žekar — unix, communications, stupidities</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 18 Oct 2010 19:34:05 +0000</lastBuildDate><atom:link href="https://simon.zekar.com/tags/access-point/index.xml" rel="self" type="application/rss+xml"/><item><title>blocking certain MAC addresses from joining your Cisco AP</title><link>https://simon.zekar.com/2010/10/18/blocking-mac-addresses-cisco-ap/</link><pubDate>Mon, 18 Oct 2010 19:34:05 +0000</pubDate><guid>https://simon.zekar.com/2010/10/18/blocking-mac-addresses-cisco-ap/</guid><description>&lt;p>In hope for an energy to revive this blog, a quick post.&lt;/p>
&lt;p>If you need to block an abuser flood-trying to connect to your AP, resulting in multiple radius connections and error messages, you can make ACL on AP like this:&lt;/p>
&lt;pre tabindex="0">&lt;code># access-list 760 deny 0002.725f.93c3 0000.0000.0000
# dot11 association mac-list 760
&lt;/code>&lt;/pre>&lt;p>where 0002.725f.93c3 is the abusers mac address.&lt;/p>
&lt;p>Happy banning,&lt;br>
S.&lt;/p></description></item></channel></rss>