Will H. Backman wrote:
Looking for feedback on a basic blueprint for a small office using BSD.
Situation: Small office with maybe five workstations.
Question: What would an all BSD setup look like?
Solution that comes to mind:
* Single server for DNS, DHCP, LPD, SMTP, IMAP, and home directories.
On 3/21/06, Smith <[EMAIL PROTECTED]> wrote:
> I would even consider doing away with dns and point everyone to the isp
> dns along with using static ip addresses.
To avoid timeouts, I recommend you check out the FAQ [1] first before
doing away with (Reverse) DNS. Distributing hosts files to your
c
Steve Shockley wrote:
I disagree with that; from a scalability point of view you don't need
your own DNS resolver, but I've found that many ISPs' DNS servers for
customer use aren't well-maintained or they're overloaded. Running
your own DNS server eliminates this as a possible problem.
Ab
On Tuesday 21 March 2006 00:19, Will H. Backman wrote:
> > 2. I don't see a firewall.
>
> I assume something like a $40 linksys.
If your intention is to use OpenBSD why be cheap on the fireqwall and use
total garbage?
---
Lars Hansson
On Tuesday 21 March 2006 03:02, Peter wrote:
> Why is DHCP a bad idea?
It isnt, it's usually a very good idea since it makes network management a
whole lot simpler. Of course, with only a handfull of machines using a static
configuration might not be a big deal but if you have people coming in
Will H. Backman wrote:
I assume something like a $40 linksys.
Might I suggest that if you have budget for an extra computer or an
older one laying around (not *too* old if you want decent outgoing
internet performance) pop some NICs into it and use pfSense (
www.pfsense.com ) to make it a fire
Smith wrote:
I would even consider doing away with dns and point everyone to the isp
dns along with using static ip addresses. You only need dns if you
anticipate a lot of users making dns queries to the point of affecting
your bandwidth or you need a dns server to point the rest of the
inter
e Windows, use Ghost.
From: [EMAIL PROTECTED] on behalf of Smith
Sent: Mon 3/20/2006 8:11 PM
To: misc@openbsd.org
Subject: Re: Small office with BSD blueprint
I would even consider doing away with dns and point everyone to the isp
dns along with using static ip addresses.
I would even consider doing away with dns and point everyone to the isp
dns along with using static ip addresses. You only need dns if you
anticipate a lot of users making dns queries to the point of affecting
your bandwidth or you need a dns server to point the rest of the
internet to your we
On Mon, Mar 20, 2006 at 02:02:58PM -0500, Peter wrote:
> --- Joachim Schipper <[EMAIL PROTECTED]> wrote:
>
> [snip]
>
> > > Do you usually assign static IPs?
> >
> > Yes, on a small LAN such as this - why not? It cuts out one bad idea
> > (DHCP), and does not have any disadvantages I can see. Ex
On Mon, Mar 20, 2006 at 03:23:36PM -0500, Will H. Backman wrote:
> Will H. Backman wrote:
> >Looking for feedback on a basic blueprint for a small office using BSD.
> >Situation: Small office with maybe five workstations.
> >Question: What would an all BSD setup look like?
> >Solution that comes t
* Peter <[EMAIL PROTECTED]> [2006-03-20 20:08]:
> Why is DHCP a bad idea?
it isn't.
On Mon, 2006-03-20 at 20:02:24 +, Ste Jones proclaimed...
> rogue dhcp servers, broken clients, possible man in the middle attacks
> and unauthorised access problems
> http://www.networkpenetration.com/dhcp_flaws.html
Right, cause that doesn't happen w/o DHCP.
Quit spreading FUD.
Will H. Backman wrote:
Looking for feedback on a basic blueprint for a small office using BSD.
Situation: Small office with maybe five workstations.
Question: What would an all BSD setup look like?
Solution that comes to mind:
* Single server for DNS, DHCP, LPD, SMTP, IMAP, and home directories.
> Why is DHCP a bad idea?
>
rogue dhcp servers, broken clients, possible man in the middle attacks
and unauthorised access problems
http://www.networkpenetration.com/dhcp_flaws.html
cheers
ste
At 02:02 PM 3/20/2006 -0500, Peter wrote:
> Yes, on a small LAN such as this - why not? It cuts out one bad idea
> (DHCP), and does not have any disadvantages I can see. Except maybe
> that
> you need to update the DNS server(s) on all the Windows boxes if it
> changes. And yes, that's happened t
Peter wrote:
--- Joachim Schipper <[EMAIL PROTECTED]> wrote:
[snip]
Do you usually assign static IPs?
Yes, on a small LAN such as this - why not? It cuts out one bad idea
(DHCP), and does not have any disadvantages I can see. Except maybe
that
you need to update the DNS server(s) on all the
--- Joachim Schipper <[EMAIL PROTECTED]> wrote:
[snip]
> > Do you usually assign static IPs?
>
> Yes, on a small LAN such as this - why not? It cuts out one bad idea
> (DHCP), and does not have any disadvantages I can see. Except maybe
> that
> you need to update the DNS server(s) on all the Win
On Mon, 20 Mar 2006 19:00:49 +0100
Joachim Schipper <[EMAIL PROTECTED]> spake:
> > >- DHCP is not generally useful, unless you implement ...
> >
> > Do you usually assign static IPs?
>
> Yes, on a small LAN such as this - why not? It cuts out one bad idea
> (DHCP), and does not have any disadvan
On Mon, Mar 20, 2006 at 11:14:04AM -0500, Will H. Backman wrote:
> Joachim Schipper wrote:
> >On Mon, Mar 20, 2006 at 09:53:30AM -0500, Will H. Backman wrote:
> >
> >>Looking for feedback on a basic blueprint for a small office using BSD.
> >>Situation: Small office with maybe five workstations.
>
I would be interested in the details on that also.
Thanks in advance.
On 3/20/06, John R. Shannon <[EMAIL PROTECTED]> wrote:
> Will H. Backman wrote:
> > Looking for feedback on a basic blueprint for a small office using BSD.
> > Situation: Small office with maybe five workstations.
> > Question
John R. Shannon wrote:
Will H. Backman wrote:
Looking for feedback on a basic blueprint for a small office using BSD.
Situation: Small office with maybe five workstations.
Question: What would an all BSD setup look like?
Solution that comes to mind:
* Single server for DNS, DHCP, LPD, SMTP, IM
Joachim Schipper wrote:
On Mon, Mar 20, 2006 at 09:53:30AM -0500, Will H. Backman wrote:
Looking for feedback on a basic blueprint for a small office using BSD.
Situation: Small office with maybe five workstations.
Question: What would an all BSD setup look like?
Solution that comes to mind:
*
Will H. Backman wrote:
Looking for feedback on a basic blueprint for a small office using BSD.
Situation: Small office with maybe five workstations.
Question: What would an all BSD setup look like?
Solution that comes to mind:
* Single server for DNS, DHCP, LPD, SMTP, IMAP, and home directories.
On Mon, Mar 20, 2006 at 09:53:30AM -0500, Will H. Backman wrote:
> Looking for feedback on a basic blueprint for a small office using BSD.
> Situation: Small office with maybe five workstations.
> Question: What would an all BSD setup look like?
> Solution that comes to mind:
> * Single server for
25 matches
Mail list logo
