Hi,
The final scenario is the one you described. I need to keep servers #4 and
#5 with direct connection to the internet (cannot depend on server #1), so I
have to configure the router to redirect only the traffic related to the
servers #2 and #3 to server server #1. Ok.
I guess at the server #1 side IPChains will take care of the rest.
Is there a problem to have server #2 (200.199.99.xx) dgw pointing to a local
IP address (10.1.1.8) ?
I tried to configure two adapters within the same IP block (200.199.99.xx)
but when I activate the second adapter the default gateway is lost and I am
unable to reassign it.
Thanks for you help.
Luciano Eicke
Web Garage S/C Ltda
e-mail : [EMAIL PROTECTED]
[EMAIL PROTECTED]
fones: 55-41-9106-6566
55-41-3023-4881
-----Original Message-----
From: Scott Krabler <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Sábado, 28 de Setembro de 2002 19:36
Subject: RE: routing how to
>It sounds like you want couple of machines to be masked behind another one.
>Here's the proper config (below). Default gateway for #4 & #5 is #1 (second
>interface). dgw for #1-3 is the router's inside interface.
>
>In order to route traffic, you must have separate LAN segments.
>
>Router
> |
> Hub
> |
>+----+---+
>| | |
>#1 #2 #3
>|
>Hub
> |
>+---+
>| |
>#4 #5
>
>Hope this helps.
>
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]On Behalf Of Luciano Eicke
>Sent: Saturday, September 28, 2002 3:27 PM
>To: [EMAIL PROTECTED]
>Subject: routing how to
>
>
>Hi,
>
>I've been trying to "play" with route and ipchains for a while with no
>success. I hope somebody can help me.
>
>The scenario:
>
>I have an internet link with valid IP addresses.
>
>My router IP address is 200.199.99.193
>
>I have a Linux-RedHat 7.2 server (#1) at 200.199.99.195 (ETH0), default
>gateway pointing to the router (200.199.99.193).
>I have a second Linux server (#2) at 200.199.99.220 (ETH0)
>I have a third Linux server (#3) at 200.199.99.221 (ETH0)
>
>I have two NT servers (#4 and #5) at 200.199.99.194 and 200.199.99.196
>respectively, default gateway pointing to the router (200.199.99.193).
>
>Servers #1, #4, #5 and the router are connected to the same hub.
>Servers #2 and #3 are connected to another hub, which in turn is "uplinked"
>to the first hub.
>
>I want #1 to control how much bandwidth is allocated to servers #2 and #3
(I
>intend to use HTB), so i need to enable servers #2 and #3 to get to the
>router (and from there to the internet and vice-versa) through server #1.
>I mean, all incoming and outgoing traffic related to servers #2 should flow
>like:
>server #2 => server #1 => router => internet
>internet => router => server #1 => server #2
>
>The same to server #3.
>
>Servers #4 and #5 must not depend on server #1, so these servers'direct
>connection to the router must remain.
>
>What I tried:
>
>I installed a second ethernet adapter at server #1 (ETH1), assigned a local
>IP address to it (10.1.1.8), connected a UTP to the hub and to the ETH1
>interface and set IPChains Input rules as:
>>From 200.199.99.220, iface ETH1 (i did the same to server #3)
>To 0.0.0.0
>Redirect to host 200.199.99.193
>
>What I wanted to happen is all incoming traffic from server #2
>(200.199.99.220) arriving at the ETH1 interface to be forwarded to the
>router (200.199.99.193).
>Since I have a default gateway to 200.199.99.193, I assumed the static
route
>table would take care of it.
>
>Is this approach correct or I'm going the wrong way ?
>
>Does the standard installation of IPChains (the one that ships with Red Hat
>7.2) allows "forwarding" ?
>
>I went through the how-to's at linuxdoc and other sources but I was unable
>to put the pieces together.
>
>Any help would be most appreciated.
>
>Best regards,
>
> Luciano Eicke
>
>
>
>
>
>
>_______________________________________________
>Seawolf-list mailing list
>[EMAIL PROTECTED]
>https://listman.redhat.com/mailman/listinfo/seawolf-list
>
>
>
>_______________________________________________
>Seawolf-list mailing list
>[EMAIL PROTECTED]
>https://listman.redhat.com/mailman/listinfo/seawolf-list
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
