On Fri, Jan 14, 2005 at 07:02:51AM -0700, Soren Harward wrote: > How do you intend to do put together the network? Are you going to > force everyone to be behind some sort of NAT router doing its own > DHCP? I think this is the best idea. But if so, then don't use the > 10.X netblock because that's what campus is already using, and you'd > be bound to have some sorts of problems with the routers in the CTB if > you did. Use some part of the 172.16 netblock because AFAIK nothing > (widely-routable, that is) on campus uses it.
I'd like to calm your fears by assuring you that there will be no NAT routing. Nothing of the sort. My massacre will be much more violent than NAT. :) The idea is to have two networks going on (probably on opposite sides of the room or something like that). On one side of the room we'll have unrestrained network access. People who are doing a Fedora net install will be on the opposite side of the room hooked up to a server which will give them addresses in the 10 range, but they'll have no access to the outside world. This server will have a wildcard DNS saying that it's everything, so when the machines go out to connect to ayo.freshrpms.net for updates, the updates will actually be given out from the local server. This makes it so we don't have to touch any of the sources lists. -- Andrew McNabb http://www.mcnabbs.org/andrew/ PGP Fingerprint: 8A17 B57C 6879 1863 DE55 8012 AB4D 6098 8826 6868
pgp6kDt93NLRA.pgp
Description: PGP signature
-------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
