NYCPHP Meetup

[Jon Baer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The question really pertains to your level of paranoia (or LOP) ... if
your LOP > 2 x the average sysadmin, then static for everything is your
best bet (even if you have to learn how to accomplish it (static arping
for example)) ... if your LOP < 1 x the average sysadmin then you can
take the lazy route :-)

I can understand the practical frustration in firewall/iptables
configuration for such a setup but I think it comes down to what you
would like to protect if (something bad were to happen){} ..

Im really not a sysadmin so Id be a bad judge vs. the topology layout of
your personal network ... but I always think straight route is the best.
~ Security wise Id hope something is monitoring your "router to the net" :-)

- - Jon

LeeEyerman at aol.com wrote:

|
| Jon-
|
| When you say statically assign everything, you mean setup a DNS server,
| create names for each machine, point the router at my DNS server to
resolve the
| web/ftp/emails, etc.  The win pcs will then have their own name
| foo.myserver.com and check the Linux DNS first, and then the router to
the  net?
|
| Thanks for the help.

pgp key: http://www.jonbaer.net/jonbaer.asc
fingerprint: F438 A47E C45E 8B27 F68C 1F9B 41DB DB8B 9A0C AF47
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFA92J5Qdvbi5oMr0cRApj/AJ4sxQbJ68SbLwUVVjwdjeCDotSIdwCgw51j
yQlZ/N1dkAFpKBwff84e4uY=
=wY4f
-----END PGP SIGNATURE-----