<?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>Blog O' Matty &#187; Linux Networking</title>
	<atom:link href="http://prefetch.net/blog/index.php/category/linux-network-utilities/feed/" rel="self" type="application/rss+xml" />
	<link>http://prefetch.net/blog</link>
	<description>Blog O' Matty</description>
	<lastBuildDate>Tue, 07 Feb 2012 03:00:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Good write up Linux consistent network device naming</title>
		<link>http://prefetch.net/blog/index.php/2011/10/08/good-write-up-linux-consistent-network-device-naming/</link>
		<comments>http://prefetch.net/blog/index.php/2011/10/08/good-write-up-linux-consistent-network-device-naming/#comments</comments>
		<pubDate>Sat, 08 Oct 2011 13:49:15 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Linux Networking]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/?p=4634</guid>
		<description><![CDATA[In RHEL 6.1 the default names assigned to Dell server network interfaces changed from ethX to emX and pXpX. The new names describe where a network interface physically resides in the system, and will have the following format: emX &#8211; the X (first, second, etc.) onboard interface pXpY &#8211; PCI device X port Y Dell [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2011/10/08/good-write-up-linux-consistent-network-device-naming/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Speeding up SSH (SCP) data transfers</title>
		<link>http://prefetch.net/blog/index.php/2011/07/19/speeding-up-ssh-scp-data-transfers/</link>
		<comments>http://prefetch.net/blog/index.php/2011/07/19/speeding-up-ssh-scp-data-transfers/#comments</comments>
		<pubDate>Tue, 19 Jul 2011 14:23:54 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Linux Networking]]></category>
		<category><![CDATA[OpenSSH]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/?p=4455</guid>
		<description><![CDATA[I&#8217;ll be the first to admit that I&#8217;m an SCP addict. It doesn&#8217;t matter what kind of data I&#8217;m working with, if it can be turned into an object that I move around with scp I&#8217;m in! One thing I&#8217;ve always noticed with scp is the dismal out of the box performance. I read quite [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2011/07/19/speeding-up-ssh-scp-data-transfers/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Using netstat and dropwatch to observe packet loss on Linux servers</title>
		<link>http://prefetch.net/blog/index.php/2011/07/11/using-netstat-and-dropwatch-to-observe-packet-loss-on-linux-servers/</link>
		<comments>http://prefetch.net/blog/index.php/2011/07/11/using-netstat-and-dropwatch-to-observe-packet-loss-on-linux-servers/#comments</comments>
		<pubDate>Mon, 11 Jul 2011 23:06:21 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Linux Networking]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/?p=4437</guid>
		<description><![CDATA[Anyone that is running a modern Operating System is most likely utilizing TCP/IP to send and receive data. Modern TCP/IP stacks are somewhat complex and have a slew of tunables to control their behavior. The choice of when and when not to tune is not always super clear cut, since documentation and the advice of [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2011/07/11/using-netstat-and-dropwatch-to-observe-packet-loss-on-linux-servers/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Using the Linux arping utility to send out gratuitious ARPs</title>
		<link>http://prefetch.net/blog/index.php/2011/03/26/using-the-linux-arping-utility-to-send-out-gratuitious-arps/</link>
		<comments>http://prefetch.net/blog/index.php/2011/03/26/using-the-linux-arping-utility-to-send-out-gratuitious-arps/#comments</comments>
		<pubDate>Sat, 26 Mar 2011 12:44:05 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Linux Networking]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/?p=4256</guid>
		<description><![CDATA[I managed a number of Redhat and Heartbeat clusters. On a couple of occassions the services that manage the virtual IPs have misbehaved, and the storage has ended up on one node and the virtual IP on another. To fix this I need to manually move the virtual IP to the host it belongs on, [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2011/03/26/using-the-linux-arping-utility-to-send-out-gratuitious-arps/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Stopping your RHEL virtual interfaces from starting at boot. ONPARENT you say?</title>
		<link>http://prefetch.net/blog/index.php/2011/03/22/stopping-your-virtual-interfaces-from-starting-at-boot-onparent-you-say/</link>
		<comments>http://prefetch.net/blog/index.php/2011/03/22/stopping-your-virtual-interfaces-from-starting-at-boot-onparent-you-say/#comments</comments>
		<pubDate>Tue, 22 Mar 2011 21:37:07 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Linux Networking]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/?p=4228</guid>
		<description><![CDATA[I recently debugged a pretty interesting problem with one of my clusters. When I rebooted one of the nodes, I noticed that a virtual interface that had ONBOOT set to no was started when the network interfaces were initialized. For those not familiar with RHEL systems, the ONBOOT directive tells the network initialization scripts not [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2011/03/22/stopping-your-virtual-interfaces-from-starting-at-boot-onparent-you-say/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to learn everything you ever wanted to know about Linux sockets</title>
		<link>http://prefetch.net/blog/index.php/2010/10/15/how-to-learn-everything-you-ever-wanted-to-know-about-linux-sockets/</link>
		<comments>http://prefetch.net/blog/index.php/2010/10/15/how-to-learn-everything-you-ever-wanted-to-know-about-linux-sockets/#comments</comments>
		<pubDate>Fri, 15 Oct 2010 14:18:30 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Linux Networking]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/?p=3859</guid>
		<description><![CDATA[Viewing network socket data is something SysAdmins do often. We could be called on to see if a connection is established to a host, if an application is listening on a given port, or we may need to review the network connection table as a whole to see what a server is doing (this is [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2010/10/15/how-to-learn-everything-you-ever-wanted-to-know-about-linux-sockets/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Creating Linux bridging / tap devices with tunctl and openvpn</title>
		<link>http://prefetch.net/blog/index.php/2009/12/20/creating-linux-bridging-tap-devices-with-tunctl-and-openvpn/</link>
		<comments>http://prefetch.net/blog/index.php/2009/12/20/creating-linux-bridging-tap-devices-with-tunctl-and-openvpn/#comments</comments>
		<pubDate>Sun, 20 Dec 2009 14:28:02 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Linux Networking]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/?p=2977</guid>
		<description><![CDATA[The more and more I play around with KVM virtualization, the more I realize just how useful Linux bridging is. In the Linux bridging world, a bridge device simulates a multiport Ethernet switch. To connect to the switch, you create a tap device that simulates a port on that switch. Once you have bridging configured [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2009/12/20/creating-linux-bridging-tap-devices-with-tunctl-and-openvpn/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Viewing the status of NetworkManager managed links</title>
		<link>http://prefetch.net/blog/index.php/2009/09/20/viewing-the-status-of-networkmanager-managed-links/</link>
		<comments>http://prefetch.net/blog/index.php/2009/09/20/viewing-the-status-of-networkmanager-managed-links/#comments</comments>
		<pubDate>Sun, 20 Sep 2009 13:32:33 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Linux Networking]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/?p=2960</guid>
		<description><![CDATA[As I mentioned in a previous post, I spent some time trying to get the NetworkManager to respect my custom DNS settings. When I was looking into this issue, I learned about the nm-tool utility. This nifty tool will print the status of each NetworkManager managed interface, as well as the connection state: $ nm-tool [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2009/09/20/viewing-the-status-of-networkmanager-managed-links/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Getting the Linux NetworkManager process to respect custom DNS server settings</title>
		<link>http://prefetch.net/blog/index.php/2009/09/14/getting-the-linux-networkmanager-process-to-respect-custom-dns-server-settings/</link>
		<comments>http://prefetch.net/blog/index.php/2009/09/14/getting-the-linux-networkmanager-process-to-respect-custom-dns-server-settings/#comments</comments>
		<pubDate>Tue, 15 Sep 2009 00:36:13 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Linux Networking]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/?p=2948</guid>
		<description><![CDATA[I recently switched my work Desktop from Ubuntu to Fedora 11, and noticed that there are some new configuration options now that network intefaces are managed by the NetworkManager process. Two useful options are the ability to specify the DNS servers and search domains in the network-scripts files, and have those applied when a DHCP [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2009/09/14/getting-the-linux-networkmanager-process-to-respect-custom-dns-server-settings/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Enabling IPv4 forwarding on Centos and Fedora Linux servers</title>
		<link>http://prefetch.net/blog/index.php/2009/07/31/enabling-ipv4-forwarding-on-centos-and-fedora-linux-servers/</link>
		<comments>http://prefetch.net/blog/index.php/2009/07/31/enabling-ipv4-forwarding-on-centos-and-fedora-linux-servers/#comments</comments>
		<pubDate>Fri, 31 Jul 2009 13:28:19 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Linux Networking]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/?p=2681</guid>
		<description><![CDATA[When I was playing around with KeepAlived, I managed to create a few HA scenarios that mirrored actual production uses. One scenario was creating a highly available router, which would forward IPv4 traffic between interfaces. To configure a CentOS or Fedora Linux host to forward IPv4 traffic, you can set the &#8220;net.ipv4.ip_forward&#8221; sysctl to 1 [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2009/07/31/enabling-ipv4-forwarding-on-centos-and-fedora-linux-servers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

