Mark wrote: > Hi all > > Perhaps I am being a lil dim here as a new linux sysadmin personage > (previous preference was for windows, emphasis on "was") > > For some reason I have not been able to get a working network along the > following lines. > > NOTE this network is purely for systems testing, bandwidth etc, hence > the daisy chain effect. > > I have 2 servers, both running FC4 and a cisco router. > > The aim is to test throughput from one server to the other via the cisco. > > My proposed solution is as follows: > Both servers have 2 gigE nics > Cisco has 2 interfaces which I have named ciscoLan and ciscoWan > > Basically I want server 1 with eth0 connected to my DMZ network (and the > world at large) witha public IP address > I then want to configure eth1 with another public IP to connect directly > to the ciscoWan > > I already have the cisco connected via ciscoLan to server 2 using NAT > and private IPs but I cannot get eth1 on server 1 to come up with the IP > address I need and then talk to the cisco. > > I think the issue may be that I need to enable bridging of sorts between > the 2 NICs, as MS does with ICS etc. > > So the question is, how do I acheive that? > > As far as I can tell, I have all the interfaces configured correctly. > > I can`t give the actual IPs here, but I will give an example: > All Xs give the same subnet > <----------------[ SNIP ]------------> > > Have I really missed something and thats why this server can`t talk to > my cisco on eth1? By the way, the cisco has an IP of X.X.X.62 > > I am trying to have both eth0 and eth1 having IPs only 1 apart and the > gateway for eth1 is set to the same as eth0. Is this adding to the > problems? > > I can solve it fairly easily by installing windows on server 1 and > configure ICS etc, but I would rather avoid that for 2 reasons: > - having FC4 on the server is beneficial for us after this roject > - I don`t want to give in to this problem, I would rather solve it. > Quick question - do you want all traffic to the DMZ to be able to access the cisco? If so, then you can use the bridge utilities to bridge eth0 and eth1. See the howto in the bridge-utils doc directory. In that case, you would not give eth0 and eth1 IP addresses. Instead you would give the bridge an IP address. If you only want server 1 to access the cisco, then you will want to remove the default route from ifcfg-eth1. You will also want to create a static route to the cisco. You would put this in /etc/sysconfig/network-scripts/route-eth1 As it is, server 1 has no idea on how to connect to X.X.X.62, so it tries the default route through eth0. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!
