<?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>Cisco on Simon Žekar — unix, communications, stupidities</title><link>https://simon.zekar.com/tags/cisco/</link><description>Recent content in Cisco 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/cisco/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><item><title>automatic login to Cisco routers / firewalls</title><link>https://simon.zekar.com/2010/02/28/automatic-login-to-cisco-routers-firewalls/</link><pubDate>Sun, 28 Feb 2010 01:37:34 +0000</pubDate><guid>https://simon.zekar.com/2010/02/28/automatic-login-to-cisco-routers-firewalls/</guid><description>&lt;p>Since many of you are still connecting to your Cisco boxes with the plain ssh/telnet command (typing password every time) and since Cisco boxes don’t have SSH public key authentication, the tool to use comes from &lt;a href="http://www.shrubbery.net/rancid/">Rancid&lt;/a> (Really Awesome New Cisco confIg Differ) package.&lt;/p>
&lt;p>It’s called “&lt;strong>clogin&lt;/strong> ” as &lt;a href="http://www.shrubbery.net/rancid/man/clogin.1.html">Cisco login script&lt;/a>.&lt;/p>
&lt;p>It requires all the credentials in ~/.cloginrc file (protocol / password / enable).&lt;/p>
&lt;p>Syntax of .cloginrc file can be found &lt;a href="http://www.shrubbery.net/rancid/man/cloginrc.5.html">here&lt;/a>.&lt;/p>
&lt;p>and usage is simple, just &lt;code>clogin hostname&lt;/code>&lt;/p>
&lt;p>And besides loging it’s very usefull for multiple box configuration. Let’s say you just need to write configs of your 5 routers.&lt;/p>
&lt;p>&lt;code>clogin -c &amp;quot;write;exit&amp;quot; router1 router2 router3 router4 router5&lt;/code>&lt;/p>
&lt;p>and Voila !&lt;/p>
&lt;p>S.&lt;/p></description></item><item><title>Cisco ASA failover fail if IPv6 enabled</title><link>https://simon.zekar.com/2009/10/02/cisco-asa-failover-fail-if-ipv6-enabled/</link><pubDate>Fri, 02 Oct 2009 11:14:05 +0000</pubDate><guid>https://simon.zekar.com/2009/10/02/cisco-asa-failover-fail-if-ipv6-enabled/</guid><description>&lt;p>I can’t believe it…&lt;/p>
&lt;p>&lt;a href="http://rogierm.redbee.nl/blog/2009/07/24/cisco-asa-ipv6-failover-not-supported/">Failover on Cisco ASA silently stops working after you enable ipv6 configuration.&lt;/a>&lt;/p>
&lt;p>We’re used of stupid Cisco bugs, but this wins it all !&lt;/p>
&lt;p>S.&lt;/p></description></item><item><title>IPv6 over IPv4 tunnel with Mikrotik &amp; Cisco router</title><link>https://simon.zekar.com/2009/09/27/ipv6-over-ipv4-tunnel-with-mikrotik-cisco-router/</link><pubDate>Sun, 27 Sep 2009 22:44:15 +0000</pubDate><guid>https://simon.zekar.com/2009/09/27/ipv6-over-ipv4-tunnel-with-mikrotik-cisco-router/</guid><description>&lt;p>Time when native &lt;a href="http://en.wikipedia.org/wiki/IPv6">IPv6 network&lt;/a> will come right to your home is still far away. So &lt;a href="http://en.wikipedia.org/wiki/6to4">tunneling IPv6 network over IPv4&lt;/a> to some IPv6 enabled site is a way to go.&lt;/p>
&lt;p>Configuration is easier than expected and it worked right away. In my case &lt;a href="http://www.cisco.com/en/US/products/hw/routers/ps368/">Cisco 7600&lt;/a> series is at the data center where native IPv6 is established and &lt;a href="http://www.routerboard.com/">Mikrotik RB450&lt;/a> ( a choice for home router – really powerful and really cheap).&lt;/p>
&lt;p>One /64 subnet is assigned for the tunnel (point-to-point) and /48 is then routed to it. Yes. In IPv6 /64 subnet of 18446744073709551616 IPs is used for point-to-point tunnel (2 IPs).&lt;/p>
&lt;p>On Cisco 7600 – interface (99.. is a 7600 public IP as 22.. is my home public IP):&lt;/p>
&lt;pre tabindex="0">&lt;code>interface Tunnel0
description --- test ipv6 in ipv4 tunnel ---
no ip address
ipv6 address 2AAA:BABA:101:1::1/64
tunnel source 99.99.99.99
tunnel destination 22.22.22.22
tunnel mode ipv6ip
&lt;/code>&lt;/pre>&lt;p>and route:&lt;br>
&lt;code>ipv6 route 2AAA:BABA:BEEF::/48 2AAA:BABA:101:1::2&lt;/code>&lt;/p>
&lt;p>and on Mikrotik:&lt;/p>
&lt;pre tabindex="0">&lt;code>/interface 6to4 add disabled=no local-address=22.22.22.22 mtu=1280 name=ipv6tunnel remote-address=99.99.99.99
/ipv6 address add address=2AAA:BABA:101:1::2/64 interface=ipv6tunnel
/ipv6 route add disabled=no dst-address=::/0 gateway=ipv6tunnel
&lt;/code>&lt;/pre>&lt;p>And that’s it. You can configure local interface on Mikrotik, like this:&lt;br>
&lt;code>/ipv6 add address=2AAA:BABA:BEEF:DEAD:1/64 advertise=yes interface=ether2&lt;/code>&lt;/p>
&lt;p>Local machines, if properly configured should receive &lt;a href="http://www.faqs.org/rfcs/rfc2461.html">advertised IPv6 prefix&lt;/a> and configure itself for IPv6.&lt;/p>
&lt;p>That’s for now, more about IPv6 soon ! HaveAnice !!&lt;/p>
&lt;p>S.&lt;/p></description></item><item><title>skriptna pomoč pri konfiguraciji Cisco opreme</title><link>https://simon.zekar.com/2007/06/24/skriptna-pomoc-pri-konfiguraciji-cisco-opreme/</link><pubDate>Sun, 24 Jun 2007 02:05:19 +0000</pubDate><guid>https://simon.zekar.com/2007/06/24/skriptna-pomoc-pri-konfiguraciji-cisco-opreme/</guid><description>&lt;p>Žal starejše verzije Ciscotovega IOS sistema ne poznajo “interface range” ukaza, ki omogoča da več portov konfigurirate naenkrat, zato si je potrebno pomagati drugače.&lt;/p>
&lt;p>da bi vsak port konfigurirali ročno, je prezamudno, še posebaj, če imate switch z 48-imi porti.&lt;/p>
&lt;p>Pomagate si lahko z enovrstičnico (bash), kot je recimo tale:&lt;/p>
&lt;p>&lt;code>i=1; while [ $i -lt 49 ]; do echo &amp;quot;int fast0/$i&amp;quot;; echo &amp;quot;**span portfast&amp;quot;** ; echo &amp;quot;**switchport mode access&amp;quot;** ; echo **&amp;quot;switchport access vlan 934&amp;quot;** ; let i+=1; done;&lt;/code>&lt;/p>
&lt;p>koda zgoraj bo za vsak port izpisala konfiguracijo, izpis lahko copy-paste-ate v cisco switch in marsikatera minuta vam bo prihranjena. Seveda si kodo preuredite za željeno število portov in seveda za željene ukaze.&lt;/p>
&lt;p>Kakorkoli, gre samo za prikaz zanke – štetja v ukazni lupini, kar lahko s pridom uporabljate za veliko stvari.&lt;/p>
&lt;p>Ponedeljek je dela prost dan ! 😉&lt;/p></description></item></channel></rss>