Opinions about a small LAN with real IP shortage
Hello, I am setting up a lan for a small business which will also connect to the Internet with SDSL and 8 real IP subnet. The gateway will be a suse box. I only need 2 servers with real ips. The rest of the pcs will be clients. I have 2 alternate plans in my mind. 1. Create 2 subnets. One with the real ips and the 2 servers, and one with 192.168.* for the clients. Linux will have 3 interfaces (DSL, real ip eth, internal eth) 2. Create one subnet with 192.168.* and create real ips as aliases for the servers (I use something similar in my home lan) The first looks more serious and more secure, but leaves 4 real ips unused. It also makes more difficult the usage of p2p and similar software by the client PCs. The second looks more like a hack but it looks attractive, maybe because it is simpler. Do you have any suggestions? I cannot make up my mind. Thanks in advance.
On Wed, 2004-05-19 at 04:41, John Chronakis wrote:
I am setting up a lan for a small business which will also connect to the Internet with SDSL and 8 real IP subnet. The gateway will be a suse box. I only need 2 servers with real ips. The rest of the pcs will be clients.
Do you have any suggestions? I cannot make up my mind.
Do you really need more than one static public IP? Even though you have 2 servers, are they not, say, a web server and a mail server or something? What I mean is: don't they do different things? You could tell the world through DNS that all the services you offer come from the gateway/firewall, and forward only those ports needed for the services to the servers on the inside. This is all very straightforward with SuSEfirewall2, but you'll wind up needing a dual DNS server process strategy in any case. Regards, dk
* David Krider;
On Wed, 2004-05-19 at 04:41, John Chronakis wrote:
I am setting up a lan for a small business which will also connect to the Internet with SDSL and 8 real IP subnet.
If you have a /29 block then you have 6 usable IP's not 8
The gateway will be a suse box. I only need 2 servers with real ips. The rest of the pcs will be clients.
Do you have any suggestions? I cannot make up my mind.
Do you really need more than one static public IP? Even though you have 2 servers, are they not, say, a web server and a mail server or something? What I mean is: don't they do different things? You could tell the world through DNS that all the services you offer come from the gateway/firewall, and forward only those ports needed for the services to the servers on the inside. This is all very straightforward with SuSEfirewall2, but you'll wind up needing a dual DNS server process strategy in any case.
himmm. lets say voip server like asterisk is on public IP I do not need to tell the world via DNS that this is my VOIP if it works between different VOIP providers. Outgoing PROXY could be on a public IP no need to tell the world via DNS that this is my proxy. I prefer Mail and DNS share one box while WWW and FTP another box so it makes two IP. And then I have the gateway machine with another public ip so now I have already used 5 Real IPs and if using a router for the DSL connection the last IP is gone also Of your there are other ways of doing it like using NAT then the above will change Just my 0.002 ¢ -- Togan Muftuoglu | Unofficial SuSE FAQ Maintainer | Please reply to the list; http://susefaq.sf.net | Please don't put me in TO/CC. Nisi defectum, haud refiecendum
participants (3)
-
David Krider -
John Chronakis -
Togan Muftuoglu