<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Christopher J. Umina &#187; Networking</title>
	<atom:link href="http://uminac.com/category/computers/networking/feed/" rel="self" type="application/rss+xml" />
	<link>http://uminac.com</link>
	<description>I&#039;m not creative enough for this, and you can&#039;t help me.</description>
	<lastBuildDate>Wed, 25 Jan 2012 17:14:07 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<meta name="generator" content="deGusto 1.0" />
		<item>
		<title>VLAN Trunking: Cisco vs. Dell</title>
		<link>http://uminac.com/2009/04/26/vlan-trunking-cisco-vsdell/</link>
		<comments>http://uminac.com/2009/04/26/vlan-trunking-cisco-vsdell/#comments</comments>
		<pubDate>Mon, 27 Apr 2009 03:04:16 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Networking]]></category>
		<category><![CDATA[cisco]]></category>
		<category><![CDATA[dell]]></category>
		<category><![CDATA[gvrp]]></category>
		<category><![CDATA[powerconnect]]></category>
		<category><![CDATA[switches]]></category>
		<category><![CDATA[trunk]]></category>
		<category><![CDATA[vlan]]></category>
		<category><![CDATA[vlans]]></category>
		<category><![CDATA[vtp]]></category>

		<guid isPermaLink="false">http://uminac.com/?p=196</guid>
		<description><![CDATA[In a recent battle at work I put a Cisco 2960G up against a Dell PowerConnect 5424. The PowerConnects aren&#8217;t bad&#8230; They&#8217;re cheap, gigabit, and Layer-2. Anyway, I quickly found out that unless you use GVRP, the Dell cannot learn what VLANs are out there. You have to specify allowed VLANS specifically on both ends [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://www.blumpkin.me/image/695" align="right" /></p>
<p>In a recent battle at work I put a Cisco 2960G up against a Dell PowerConnect 5424.  The PowerConnects aren&#8217;t bad&#8230;  They&#8217;re cheap, gigabit, and Layer-2.  Anyway, I quickly found out that unless you use GVRP, the Dell cannot learn what VLANs are out there.  You have to specify allowed VLANS specifically on both ends of a trunk.</p>
<p>The Cisco 2960G doesn&#8217;t support GVRP, and VTP is proprietary, so I was forced to use this method.</p>
<p>On the Cisco:</p>
<pre>
switchport mode trunk
switchport trunk allowed vlan add 2,100,101
switchport nonegotiate
</pre>
<p>On the Dell:</p>
<pre>
switchport mode trunk
switchport trunk allowed vlan add 2,100,101
</pre>
]]></content:encoded>
			<wfw:commentRss>http://uminac.com/2009/04/26/vlan-trunking-cisco-vsdell/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Stopping SSH SPAM with PF!</title>
		<link>http://uminac.com/2008/08/06/stopping-ssh-spam-with-pf/</link>
		<comments>http://uminac.com/2008/08/06/stopping-ssh-spam-with-pf/#comments</comments>
		<pubDate>Wed, 06 Aug 2008 20:09:52 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[bots]]></category>
		<category><![CDATA[pf]]></category>
		<category><![CDATA[spam]]></category>
		<category><![CDATA[ssh]]></category>

		<guid isPermaLink="false">http://www.uminac.com/?p=51</guid>
		<description><![CDATA[If you&#8217;ve put a server accepting SSH connections on the internet you&#8217;ve probably noticed a TON of failed login attempts from various IP addresses and various (seemingly generic) usernames.  If not, you probably should have, and you may not be up to running a server if you don&#8217;t look at logs from time to time. [...]]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;ve put a server accepting SSH connections on the internet you&#8217;ve probably noticed a TON of failed login attempts from various IP addresses and various (seemingly generic) usernames.  If not, you probably should have, and you may not be up to running a server if you don&#8217;t look at logs from time to time.</p>
<p>Either way, there&#8217;s a quick &amp; easy way to try to stop these annoying bots or whatever they are from bugging your server with PF.  Basically, on your rule where you pass SSH connections in through the firewall you can set a &#8216;max-src-conn-rate&#8217; or maximum source connection rate.  What this does is triggers something to happen when a host connects faster than a certain rate of allowed new connections.  In our case we&#8217;ll want to dump these users into a table that blocks everything from them.  So we create the table:</p>
<pre>table &lt;ssh-bruteforce&gt; persist</pre>
<p>The rule to drop people who are clearly spamming into our ssh-bruteforce table is:</p>
<pre>pass in on $ext_if inet proto tcp from any to any port ssh flags S/SA keep state (max-src-conn-rate 4/30, overload &lt;ssh-bruteforce&gt; flush global)</pre>
<p>Where the connection rate is 4 connections in 30 seconds (4/30).  From this point on, you just want to block them.  You can do that with:</p>
<pre>block in log quick on $ext_if from &lt;ssh-bruteforce&gt;</pre>
<p>Now anybody who tries to esablish connections faster than the rate specified in the pass rule gets dumped into that table, and blocked from accessing anything at all on your server.  <img src='http://uminac.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p><a title="Matt Horan!!!!!" href="http://matthoran.com/" target="_blank">mhoran</a>++</p>
]]></content:encoded>
			<wfw:commentRss>http://uminac.com/2008/08/06/stopping-ssh-spam-with-pf/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

