svn commit: samba-web r863 - in trunk/news/users: .

[deryck at samba.org]

Author: deryck
Date: 2005-11-29 20:38:35 +0000 (Tue, 29 Nov 2005)
New Revision: 863

WebSVN: http://websvn.samba.org/cgi-bin/viewcvs.cgi?view=rev&root=samba-web&rev=863

Log:
Add a news link to an article by tpot on multiple network
interfaces with Samba.

deryck

Added:
   trunk/news/users/tpot_multiple_interfaces.html


Changeset:
Added: trunk/news/users/tpot_multiple_interfaces.html
===================================================================
--- trunk/news/users/tpot_multiple_interfaces.html	2005-11-28 13:21:49 UTC (rev 862)
+++ trunk/news/users/tpot_multiple_interfaces.html	2005-11-29 20:38:35 UTC (rev 863)
@@ -0,0 +1,24 @@
+    <h3><a name="tpot_multiple_interfaces">Tim Potter on Multiple Network Interfaces</a></h3> 
+        
+    <div class="article">
+      <p>Samba Team member Tim Potter has written an article on using Samba
+      with multiple network interfaces.  The piece is a nice write up on how
+      to set smb.conf parameters for multi-interface servers.  From the
+      introduction:</p>
+
+      <blockquote>Let's assume that we have a server with two network 
+      interfaces. Say that one interface, eth0  connects to the company 
+      network 10.0.0.0/8, and eth1 connects to 192.168.1.0/24, a small private 
+      network within the company. For one reason or another, we want shares 
+      exported by Samba to be available on the private network eth1, but not 
+      visible to the rest of the organisation via eth0. The machine in 
+      question may be a firewall, gateway or plays some other sensitive role. 
+      In other configurations, you might want to avoid SMB connections over 
+      your PPP or wireless connection, for performance reasons.</blockquote>
+
+      <p>For the rest of the article, see 
+      <a href="http://samba.org/~tpot/articles/multiple-interfaces.html">Multiple 
+      Network Interfaces with Samba</a>.</p> 
+    </div>
+        
+