We're setting up a (TCP/IP) network in our uni hall, with around 10-12 machines in different flats. The layout is somewhat like this:
3 x client machines (Win95)
1 x server/router
4 x client machines (Win95\Linux)
2 x client machines (Win95\Linux)
1 x server\router
Flats 39 and 43 will each have their own segment, entering eth0 in their respective servers. eth1 in each server will be connected to form a long segment, with Flat 42's machines strung along the middle. All network cable is coax, at 10Mbit
Each server will provide services like email\irc\www and will hopefully run a Quake \ Quake 2 server.
We can allocate IP addresses and subnets how we want as we aren't connected to any other network.
The only problem is, we don't know if this is actually going to work <g>. Will the servers need two IP addresses each (one each for eth0 and eth1)? And if so, how do we know where to connect to in order to access services?
I think I can work out how to use route to set up a routing table for each server - the main problem is being able to talk to either server from any machine on the network.
Also, is there likely to be much latency between machines at opposite ends of the network? (because of routing through both servers)
I have read the older question in this area with a similar problem to this, but theirs was more a problem with the subnetting as opposed to the general setup.
In case it seems like we're just making it hard for ourselves organising the network like this, in one segment the cable length would be far too long (and there would be too much traffic for any reasonable speed), we also need a dedicated 24hrs reliable machine to chat on, and Gary and I (the people building the servers) need Linux machines for coursework.
(btw, we're using RedHat Linux 5)
As much detail as possible in an answer would be appreciated.