<?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>Debian Tutorials &#187; network</title>
	<atom:link href="http://www.debiantutorials.com/tag/network/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.debiantutorials.com</link>
	<description>Copy/Paste tutorials for Debian Linux</description>
	<lastBuildDate>Wed, 08 Sep 2010 08:36:07 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Configuring port forwarding with rinetd</title>
		<link>http://www.debiantutorials.com/configuring-port-forwarding-with-rinetd/</link>
		<comments>http://www.debiantutorials.com/configuring-port-forwarding-with-rinetd/#comments</comments>
		<pubDate>Sat, 12 Jun 2010 22:05:16 +0000</pubDate>
		<dc:creator>aip</dc:creator>
				<category><![CDATA[Lenny]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[rinetd]]></category>

		<guid isPermaLink="false">http://www.debiantutorials.net/?p=313</guid>
		<description><![CDATA[inetd redirects TCP connections from one IP address and port to another. rinetd is a single-process server which handles any number of connections to the address/port pairs specified in the file /etc/rinetd.conf. Since rinetd runs as a single process using nonblocking I/O, it is able to redirect a large number of connections without a severe [...]]]></description>
			<content:encoded><![CDATA[<p>inetd redirects TCP connections from one IP address and port to another. rinetd is a single-process server which handles any number of connections to the address/port pairs specified in the file /etc/rinetd.conf. Since rinetd runs as a single process using nonblocking I/O, it is able to redirect a large number of connections without a severe impact on the machine. This makes it practical to run TCP services on machines inside an IP masquerading firewall.</p>
<p>1. Install rinetd</p>
<p><code>apt-get install rinetd<br />
</code><span id="more-313"></span></p>
<p>2. Add some forwarding rules (pico /etc/rinetd.conf)</p>
<p><code># bindadress    bindport  connectaddress  connectport<br />
  0.0.0.0       80        209.85.229.104  80  # HTTP<br />
  0.0.0.0       110       209.85.229.109  110 # POP3<br />
  0.0.0.0       143       209.85.229.109  143 # IMAP<br />
</code></p>
<p><em>These rules will forward all http, pop3 and imap connections to Google's web, pop3 and imap servers. It's just an example but it may make more sense to forward for example port 80 on a public IP address to the internal network to a server that does not have a public IP address.</em></p>
<p>3. Restart rinetd</p>
<p><code>/etc/init.d/rinetd restart<br />
</code></p>
<p>Now enter http://youserver in a web browser and you'll see Google search.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.debiantutorials.com/configuring-port-forwarding-with-rinetd/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Installing ntop network monitoring tool</title>
		<link>http://www.debiantutorials.com/installing-ntop-network-monitoring-tool/</link>
		<comments>http://www.debiantutorials.com/installing-ntop-network-monitoring-tool/#comments</comments>
		<pubDate>Sat, 26 Sep 2009 20:27:21 +0000</pubDate>
		<dc:creator>aip</dc:creator>
				<category><![CDATA[Lenny]]></category>
		<category><![CDATA[Monitoring]]></category>
		<category><![CDATA[lenny]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[ntop]]></category>

		<guid isPermaLink="false">http://www.debiantutorials.net/?p=114</guid>
		<description><![CDATA[ntop is a network traffic probe that shows the network usage, similar to what the popular top Unix command does. ntop is based on libpcap and it has been written in a portable way in order to virtually run on every Unix platform and on Win32 as well.
ntop users can use a a web browser [...]]]></description>
			<content:encoded><![CDATA[<p>ntop is a network traffic probe that shows the network usage, similar to what the popular top Unix command does. ntop is based on libpcap and it has been written in a portable way in order to virtually run on every Unix platform and on Win32 as well.</p>
<p>ntop users can use a a web browser (e.g. netscape) to navigate through ntop (that acts as a web server) traffic information and get a dump of the network status. In the latter case, ntop can be seen as a simple RMON-like agent with an embedded web interface.</p>
<p>1. Install required packages</p>
<p><code>apt-get install ntop<br />
</code><span id="more-114"></span></p>
<p>2. Set administrator password</p>
<p><code>ntop --set-admin-password<br />
</code></p>
<p>3. Configure ntop to use your correct network adapter if it's not eth0 (optional)</p>
<p><code>dpkg-reconfigure ntop<br />
 > eth0 (or your network adapter)<br />
 > ntop<br />
</code></p>
<p>4. Start ntop</p>
<p><code>/etc/init.d/ntop start<br />
</code></p>
<p>Now you can access ntop web admin on a location similar to this one: http://192.168.1.100:3000. Just make sure you replace the IP address with your server IP address.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.debiantutorials.com/installing-ntop-network-monitoring-tool/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Add an additional IP address to your server</title>
		<link>http://www.debiantutorials.com/add-an-additional-ip-address-to-your-server/</link>
		<comments>http://www.debiantutorials.com/add-an-additional-ip-address-to-your-server/#comments</comments>
		<pubDate>Wed, 05 Aug 2009 22:47:22 +0000</pubDate>
		<dc:creator>aip</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Lenny]]></category>
		<category><![CDATA[etch]]></category>
		<category><![CDATA[lenny]]></category>
		<category><![CDATA[network]]></category>

		<guid isPermaLink="false">http://www.debiantutorials.net/?p=94</guid>
		<description><![CDATA[1. Open the network configuration file (pico /etc/network/interfaces)
Check the name of your network interface. You should see a line similar to this one: "iface eth0 inet static". In my case the name is eth0.
Add these lines to the end of the file:
auto eth0:1
iface eth0:1 inet static
address 192.168.1.3
netmask 255.255.255.0
broadcast 192.168.1.255
network 192.168.1.0

Replace eth0 by your network interface [...]]]></description>
			<content:encoded><![CDATA[<p>1. Open the network configuration file (pico /etc/network/interfaces)</p>
<p>Check the name of your network interface. You should see a line similar to this one: "iface eth0 inet static". In my case the name is eth0.</p>
<p>Add these lines to the end of the file:</p>
<p><code>auto eth0:1<br />
iface eth0:1 inet static<br />
address 192.168.1.3<br />
netmask 255.255.255.0<br />
broadcast 192.168.1.255<br />
network 192.168.1.0<br />
</code><span id="more-94"></span></p>
<p><em>Replace eth0 by your network interface name. If you are adding multiple IP addresses to the same system, you can increase the number after "eth0:".</em></p>
<p>2. Activate the new virtual network interface</p>
<p><code>ifup eth0:1<br />
</code></p>
]]></content:encoded>
			<wfw:commentRss>http://www.debiantutorials.com/add-an-additional-ip-address-to-your-server/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
