Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 242
  • Last Modified:

Help setting up Linux router/server!

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:

Flat #39:
3 x client machines (Win95)
1 x server/router

Flat #42:
4 x client machines (Win95\Linux)

Flat #43:
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.

Thanx
0
shivers
Asked:
shivers
1 Solution
 
jeffa072897Commented:
It' pretty easy and you're on the right track.

1) Eth1 in each server will require an IP address that is on the same logical network.
    Also, this nust be unique from the other segments(but, you already knew that).
    Example, using class C addresses - 192.168.27.1 for server 1 and 192.168.27.2 for server2.
2) You'll need to have a routing daemon running. This should be in the RH setup to install/enable. If not, check the Linux home site for routed of gated info.
3) Boot both servers. When both ethernets initialize the routing daemons will build the routing tables and viola, you done. No need to populate routing tables.
4) You may want/need to check default gateway settings on the servers if the segments don't route to each other. But, you most likely won't need to do this.
5) make sure your client's default gateway settings point to their respective Linux server.

The latency shouldn't be an issue unless the Linux boxes are old klunkers. If they're Pentium class machines, no problem.

If need be email me direct.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now