setting up small network lab

[zonar00]

I'm interested in opening up a small network lab for my research work at my house.

For this i already have purchased the following:-

#3 Pc's
#1 linux(machine) functioning as a router having 2 NIC
#1 8 port switch
Patch cables as required.

Now,the thing is that getting all this to work. I want the (3) Pc to have an access
to internet as most important requirement for any kind of research work. As it should be the only thing that needs configuring is the linux box and frankly i don't know anything about iptables. Like setting up a DHCP server and doing a NAT seems GOOD in theory but in practice i dnt know much therefore i want you guys to help me out in how could i get my whole n/w established and running.Thank you

[Studlyami]

Setting up a linux machine to act like a network filewall, router, ect. is a large topic with a lot of documentation in various places on the web. Your best bet is to start reading, reading reading, and then post some specific problems you are running into. Also you should look into using VM Ware to practice some home network type stuff, it can save you some money (creates a virtual machine that acts like its a completely different computer).

[sicarie]

zonar00-

Please watch your language.

Also, there are several guides to configuring DNS and DHCP, but you should really concentrate on the design first and foremost, the rest will come. If this is just go get experience, go for it, install it and removed it as many times as you need to get the steps and options down. However, if this is just for a "best practice" example of a home network, you should design it first based on what you want to do with it.

So, what is the goal? Do you want to do web development? Do you want to host information? Do you want to do pen-testing?

[zonar00]

zonar00-

Please watch your language.

Also, there are several guides to configuring DNS and DHCP, but you should really concentrate on the design first and foremost, the rest will come. If this is just go get experience, go for it, install it and removed it as many times as you need to get the steps and options down. However, if this is just for a "best practice" example of a home network, you should design it first based on what you want to do with it.

So, what is the goal? Do you want to do web development? Do you want to host information? Do you want to do pen-testing?

yeah pen-test. YES i want to deploy an IDS on my network and then test it against it evasion/invasion attacks(commonly known to IDs technologies only)

[sicarie]

yeah pen-test. YES i want to deploy an IDS on my network and then test it against it evasion/invasion attacks(commonly known to IDs technologies only)

Well, with a pen-test lab, the thing is that you usually don't want it connected to the internet, so that something isn't released into the wild by accident. I would recommend a pseudo-DMZ setup for that part of your lab, don't make it directly accessible to your personal PC.

So I'd really recommend having your connection to the internet (modem/router) go to your firewall, which will then segment to your "DMZ" and your personal PC. Then you can create your "DMZ" PC to have as many different images as you want, and heavily restrict access to/from the internet (I'd still recommend completely restricting access to the internet, but you said you would like to allow them that...).

I'd also recommend souping one of your boxes up, and having that as your "DMZ" PC, running a bunch of different VMs. The cool thing about VMs is that you can take snapshots and base images and transfer them around/restore them pretty quickly, and they all can (if you want them to, and it sounds like you do, for DNS, DHCP, fileshare, etc...) act as if they are independent machines on the network.

[sicarie]

zonar00-

It has come to my attention that this is the second time it has been necessary to speak to you concerning the rules of this forum. These are the guidelines we ask you to abide by, and this is your last warning before measures are taken to restrict your posting.

We don't want to do that, so please read the guidelines and follow them.

Thanks,

sicarie
Moderator - C/C++ and Networking Forums