ok, this is for you network designers!

shadow

Golden Member
Oct 13, 1999
1,503
0
0
Ok, this has two parts - a design which would allow for productive learning, how to structure the class program with respects to keeping individual groups settings and files to themselves. Sharing the systems between many different lab groups - and how to keep everyones settings. The second part is that of the network setup.

I have a teacher who has an allotment of 100 IP's, they are not a subnet however, simply a range from .100 to .200. This is a lab room environment, the teacher wishes students to play with several operating systems (windows98/ME, windowsNT/2k, Linux, and whatever we want). The problem is that there is a new class of students every hour or so. Which means that the systems are going to be rotated out frequently and we need a good way to save each groups settings. In the past he had removable drives, and each group was assigned a drive for each OS they used. The teacher is now seeking a different solution as much of the time alloted for the labs was used trying to install the bloody operating systems. Well, instead of having the students install the software themselves he wants to use Ghost, and get that all taken care of at the beginning of lab.

As I understand it he wishes to maximize the amount of time in class to learning about networking and playing with the toys. My teacher has a vision, each group (3-4 students) will be assigned a "station". Now one way to describe this station is that it houses a managable switch, a router, and three computers (I beleive he only wanted three computers).

Ok, the second part, how to set it all up. As he was toying with the idea of using ghost it looks like DHCP will save us alot of trouble, he does not have his own subnet however, and he is not behind a router of his own. I suggested picking up a Netgear DSL/Cable Router and using it's built in NAT and DHCP functions. This way when we ghost the systems, DHCP is enabled by default and can receive their respective leases. As mentioned above he has a range of addresses which he can assign, and we are in no danger of needing more that one hundred IP's for the lab room (it just ain't that big). If anyone has any creative ideas, or even conventional ones which escape my paltry knowledge of networking. Yes, we want a router and managable switch at every station, BUT we don't want to tie up a nice expensive router which is just going to sit and look pretty all year. Yes, we do have a whole bunch of systems lying around which can run NAT and DHCP for us, but again, it's not the cheapest solution, as we can make use of the systems elsewhere, and it is a little bit more of a hassle to upkeep and maintain than a nice little box.

Now as far as network education requirements go, we're gonna want to generate traffic, and learn to use the routers and managable switches to direct this traffic to the right location. Now right off the bat this calls for different network segments so NAT is pretty much a given, BUT the problem then becomes how to DHCP that all? DSL/Cable routers (AFAIK) will only assign a range of IP's in a single network segment (my linky does at least). And I as of yet have not delved into WinRoute, WinProxy, ICS, SyGate to assess their DHCP capabilites. Any solutions for us there?

Am I just making this more complicated than it needs be? Is the only problem here how to save individual groups settings and configs (Cisco routers I know how to save individual configs, so thats a doosy) and how to quickly get their specific settings and configs back onto the systems, once there they set their IP and subnet info once and network away!? And I won't even have to worry about DHCP then?

I greatly appreciate any insight or ideas, thankyou very much.
-serge
 

BigDady92

Senior member
Nov 12, 2000
215
0
0
1st issue. 3 machines in a group a router and a switch: What type of switches, routers, puters??? Intelegent switches and routers? Heavy duty 'puters or low end? You could install FreeBSD(another OS that you didn't mention and is widely used ie Verizon, Hotmail, Yahoo) on a cheap 486(under$50 everywhere and I know school systems have some old stuff lying around) and configure it to do Nat'n, DHCP etc. Then give the appropriate machines their access with static ip's where neccessary and dynamic where applicable.

2nd Issue: If you are using Cisco Routers then you can give the outside connection one of the teacher's static ip's and give your internal connection one of the other ones assigned by yourselves. You will need subnetting and you won't need to install NAT or DHCP as you can give yourself a ip range of 192.168.0.0 and a subnet of 255.255.255.0 . Make all IP's static and not dynamic and assign them that way.

1st is more of a corporate enviornment, 2nd is more for study as it does not involve too much setup.
 

shadow

Golden Member
Oct 13, 1999
1,503
0
0
Yes, I have considered the cheap system running Linux (BSD) BUT I have little experience with such, hence tossed it out in favor of a DSL router. Exactly how hard is it to set up a BSD box with NAT and DHCP, and in what clever way can I use DHCP to assign IP's of different network segments (192.168.1.1-4, 192.168.2.1-4, 192.168.3.1-4, 192.168.4.1-4 with mask of 255.255.255.0) that you know of with BSD? I'll static the managable switches and the routers.

It will probably be all Cisco equipment.

As far as the second option, if I understand you correctly you suggest that I use a Cisco router with non-routable IPs (I imagine this means the router will actually perform NAT or encapsulation - fill in here please), and I'll be beloved patriot dory with that, right?

Isn't there some software out there that actually acts as a router on a Linux system?
 

Z24

Senior member
Oct 19, 1999
611
0
0
This is a networking course, and you're asking how to set up the course computer network? Shouldn't the instructor know?

Just seems kinda odd.

 

spidey07

No Lifer
Aug 4, 2000
65,469
5
76
Good post. Hats off to you for looking at the IP Network design first (routing, addressing). i would love to sink my teeth into this one but really don't understand the design.

I'll throw out my two cents in hopes that it'll will generate the details.

1) Routers control network addressing and logical topology, it is their responsibility to address networks. So all subnetting and address ranges will really be controlled by the routers.
2) You should be able to use DHCP for all your host addressing needs via the IP HELPER ADDRESS command on the routers.
3) These "stations" can also be called PODS. The pods are a network in and of themseves that in someway connect to a "backbone". I use the term backbone loosely here to describe some sort of network topology that connects all these pods together.
4) Don't worry much about the equipment for now, worry about layer 3 topology and addressing. You can fit and configure equipment to meet that layer 3 topology.

Good Luck!
spidey
 

shadow

Golden Member
Oct 13, 1999
1,503
0
0
Well, the addressing scheme is not ever going to be bolted down until we get some heads together to figure out what on earth should be taught and how. And even then it's giong to change through the course of the semester as the class progresses.

I'm not the best at organizing and structing ideas so that they are understood as I intended them. I'll try again.

I asked my teacher what he was up to, or he asked me a question about DHCP or something and I found out what he was trying to do. Now he wants to create 6-8 "stations" or "PODS" which (3-4) students will work on in groups. During the course of the week the stations will be used by many groups. So there arises the first problem. We need to devise a way to save the settings of the groups and be able to retrieve them quickly and easily (through an established procedure if not a batch/script). Now this is still the big problem for me, as before we had removable drives. But this is rather tedious, as it takes time to distribute the drives and install the Operating Systems, etc. Well we kinda jumped the gun and landed on Ghost, he had been toying with the idea of distributing image files (via multicasting from a win2k AS system) to the PODS to bypass the installation phase (in my lab the installation phase ate over 60% of class time if not more). Come to think of that, it's not going to work, as you can't send anything to a system w/o an OS. (Poop). Well so much for that idea, I guess we'll have to do some foot work after all. Maybe there is some way around this that I am not aware of but my teacher is, well I'll have to get back on that. (Afterthought - BootP, tftp server with the Ghost.exe grabing the image off the very same tftp.... hmm)

There is alot of thinking and decision making which needs to go into this part (saving configs, etc)

Ok, about the design. It's supposed to be as modular as possible. We want maximum flexability from this setup. I have in mind connecting the 3-4 systems into a cheapo 8port Netgear FS08 switch and then link up all the switches together at another switch which has a link to the NAT box. I left out the managed switch and the router located at each pod because I envision that during the course of the semester the students will have all the systems connected together not through the FS08 (just a working name for now) but through the managed switch and router. So the actual topology will change chaotically. I expect this, I think this is the right way to go (chaos that is) so that the students can learn (what the hell am I talking about, I'm a bloody student too, gosh, the blind leading the blind!, oh well, back to work). I imagine (standing on some text books and some real world cases) that generating traffic with the systems and using the managed switch and routers to control said traffic will be the most beneficial. My question to you is which configurations (routers/ M. switches / UM switchs) would you consider be good to run through as a student (I can see some creeping into your head now... redundancy, link aggregtion, SPT, OSPF, scalable and non scalable architectures). With these configurations in mind how would you lay out the equipment in the room, at PODs? Or in farms?

What series of network topologies would you liked to have learned from when you were in school, or if you had had a chance to play around with this stuff before you joined the working force and had no freedom to play for fear of breaking something? That, and how do you envision us being able to deliver such configurations in a slick and efficient manner.

IP addressing schemes: well seeing that we have routers we need to have different subnets, or networks. The need to have freedom while doing so is paramount, so we need to isolate ourselves from the rest of the campus lan (we already got into trouble, so we don't want to cause anymore). NAT is the way to do this, and I've heard no objections, except varying ways to accomplish this task. Or we could just unplug ourselves, but I think the ability to connect to the rest of the world might be one of our goals in class so I don't think this is the way to go. Now, I imagine that each POD will assign itself a network (10.10.1.0, 10.10.2.0, 10.10.3.0...... SM 255.255.255.0) This way they can configure the routers with their respective networks, and begin to communicate with the rest of the PODS. There's no way to get around that eventuality, we have to do it that way. The more I think about this, the more I'm thinking that runnding a DHCP server is rather silly, as we're teaching students about everything, why not make them do the system setup! It's beginning to seem like configuring a DHCP server to do all this is rather insane, as the systems are sometimes going to be behind a router, and sometimes not, sometimes behind a M. swtich and sometimes not. Heck the topology is going to change every which way, and the settings on each router at the PODs will be played with by the students, so getting the routers at the PODs to help with DHCP is more limiting than anything else. The main idea here is to allow the greatest amount of flexibilty so that the students can and are encouraged to FSCK UP! Best way to learn is to break stuff and understand why it is broken! Well IMO anyways. This is to teach students. That's the main objective. The second is to be able to do so easily (group configs, system settings, etc).
 

BigDady92

Senior member
Nov 12, 2000
215
0
0
OK i think i have your network figured out (i think)


workstaions ->UMswitch->Router->Mswitch

In this concept you could buy those lil DSL/Cable "router" boxes with 1 port and do dhcp/NAT that way for your workstations that are connected to the UMswitch or buy a 4port and hook the Workstations directly into the "router". Now that takes care of the first 2 parts. Now your router and the WAN part of your dsl/cable "router" give it the static ip's your teacher has lying around. From there attach your Cisco router to the Mswitch and there is your network.


As for my other post: freebsd.org has the handbook and all the details for how to setup DHCP/NAT for what you are looking for. Look in there on how to do it. But the above scenario should hold valid.
 

doug

Senior member
Oct 18, 1999
259
0
0
In term of saving all your settings I would probably do something like this:

For each OS that you plan to install, install it, configure it the way you want it then take a ghost image in that state.

On every machine that will receive that OS use the ghost image to install the OS on the machine, then do any additional configuration specific to that machine and take another ghost image so you can easily restore to this state.

Set up each machine to multi-boot and have each group have their own partition to muck around with, load the base OS on a partition and let them have at it.

Some resources you might find useful:

Ranish Partition Manager and boot manager (free)
http://www.users.intercom.com/~ranish/part/

Extended Operating System Loader (XOSL) (free boot manager)
http://www.xosl.org/