Re: Routing with red hat 9.0
From: Randy Ramsdell (me_at_somewhere.else)
Date: 06/22/04
- Next message: jim beam: "noob: who-has tell messages"
- Previous message: Max: "Re: NIC can't send packets over a certain size."
- In reply to: Baruah: "Re: Routing with red hat 9.0"
- Next in thread: Baruah: "Re: Routing with red hat 9.0"
- Reply: Baruah: "Re: Routing with red hat 9.0"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 22 Jun 2004 00:35:27 -0400
Baruah wrote:
> Randy Ramsdell <me@somewhere.else> wrote in message news:<O6WdndnU48bookrdRVn-gw@comcast.com>...
>
>>Baruah wrote:
>>
>>>Hello all,
>>> Can anyone suggest me for the following situation:
>>>Currently, I have an ISP link terminated in one of my machines's NIC
>>>with a public routable IP. I run my internal network with the second
>>>NIC, with IPTABLES to give internet access to everybody in the
>>>internal network.
>>>
>>> Now I'm going to have 2 more ISPs (i.e. 2 more public routable IPs)
>>>and I want to create my internel network in 3 IP range in total and
>>>each of these should follow the path to different ISP links. I'm using
>>>red hat 9.0.
>>>
>>>
>>>E.g. if I have internal networks as
>>>1. 192.168.1.0/24 2. 192.168.2.0/24 3. 192.168.3.0/24
>>>
>>>And ISP supplied Public routable IPs as (just for example)
>>>
>>>A. 234.234.x.x/30 B. 123.123.y.y/30 C. 243.123.z.z/30
>>>
>>>
>>>
>>>Now what I want my linux machine to do is that : it should allow
>>>traffic from internal networks as follows to pass to different ISP
>>>based on source address
>>>
>>>eg.
>>>
>>>Traffic from
>>>
>>>1. 192.168.1.0/24 should follow the link of ISP A.(234.234.x.x/30)
>>>2. 192.168.2.0/24 should follow the link of ISP B.(123.123.y.y/30)
>>>3. 192.168.3.0/24 should follow the link of ISP C.(243.123.z.z/30)
>>>
>>>
>>>Is it possible to do this in linux ? If "YES" can anybody give some
>>>solution to the problem above ? Please send a cc to my mail also.
>>>
>>>
>>>Thanks in advance.
>>>
>>>
>>>with kind regards
>>>baruah.
>>
>>I believe that all you need to do is set each internal node's gateway to
>>the relevant ips's ip.
>>
>>Are you going to NAT each internal node to different ISP ips?
>>
>>If so, you will have to NAT using iptables DNAT for each individual
>>i.p., but maintain ipmasqurade(sp?) in the forward chain.
>>
>>RCR
>
>
>
> Hi,
> thanks for the reply. YES, I'm planning to NAT each internal node
> to different ISP IPs.
>
> Plan is simple, on the internal NIC of the linux machine, I will put
> IPs viz.
> 192.168.1.1/24, 192.168.2.1/24, 192.168.3.1/24, and these will act
> gateways for internal machines in the respective IP range.
>
> And the external NIC(that is connected to different ISPs) will have
> IPs supplied by ISPs.
>
> Can please give some more idea about how to use IPTABLES with DNAT and
> MASQ ?
> I studied the man page of it, but couldn't get the idea properly.
>
> thanks and regard
> baruah
Forgive me, but I am slow sometimes,:)
Is this the exact setup:
1 NAT/gateway and 3 internal computers.
Total of 2 NICs on NAT/gateway computer.
The NAT/gateway system will be using ethX, as in eth0, eth0:1, eth0:2,
I quess the question that i'm not sure about is what type of connection
your Gateway/NAT computer is using to connect to each ISP. Does each
have its own link? like 3 cable modems, or 3 dsl modems, etc...
It will be impossible for me to show Iptable rules unless I am clear
about this.
- Next message: jim beam: "noob: who-has tell messages"
- Previous message: Max: "Re: NIC can't send packets over a certain size."
- In reply to: Baruah: "Re: Routing with red hat 9.0"
- Next in thread: Baruah: "Re: Routing with red hat 9.0"
- Reply: Baruah: "Re: Routing with red hat 9.0"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
