Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Krepper Guillermo" <billy@ciudadglobal.com.ar>
To: lartc@vger.kernel.org
Subject: [LARTC] I need some advise from a routing Guru !!
Date: Wed, 18 Apr 2001 11:27:09 +0000	[thread overview]
Message-ID: <marc-lartc-98767958826502@msgid-missing> (raw)

[-- Attachment #1: Type: text/plain, Size: 2763 bytes --]

Hi, let's get to bussisnes ...
This is what I have

                                                +--------------------------+
                        eth0 ----------------- |                           |
                                                 |        LINUX          | ---------------- eth1
                        eth2 ----------------- |                           | 
                                                 |        SUPER        | ---------------- eth4
                        eth3 ----------------- |                           |
                                                 |        ROUTER      |
                                                 +--------------------------+


Internet Connections:
    eth0: 200.1.1.0/24
    eth2: 200.2.1.0/24
    eth3: 200.3.1.0/24                    
    from 3 diferent carriers

Private LAN:
    eth1: NAT -->     192.168.1.0/24
                             192.168.2.0/24
                             192.168.3.0/24

Internet Services (DNS, WEB, MAIL, etc)

First of all I'll say that Traffic Controller works 10 points !!!!!

Routing is doing ok, but I'm not shure if it's here were I'm making all the trouble. So here is how I do it.

ip rule add from 192.168.1.0/24 table 1
    ip route add 192.168.1.0/24 via 192.168.1.254 dev eth1 table 1             ( so machines can ping eachother )
    ip route add default via 200.1.1.254 dev eth0

ip rule add from 192.168.2.0/24 table 2
    ip route add 192.168.2.0/24 via 192.168.2.254 dev eth1 table 1             ( so machines can ping eachother )
    ip route add default via 200.1.2.254 dev eth2

ip rule add from 192.168.3.0/24 table 3
    ip route add 192.168.3.0/24 via 192.168.1.254 dev eth1 table 1             ( so machines can ping eachother )
    ip route add default via 200.1.3.254 dev eth3


I think this is ok, it worked, but .......

Well here is my problem on eth4 I would like to put a dns, httpd, smtp, pop and a proxy. All of this have IP that are part of (eth0). 
DNS1 = 200.1.1.1    DNS2 = 200.1.1.2

I made all connections work with this DNS but when someone querys the dns, the paket goes to the Internet an then comes back. Is there a way of redirecting or routing it to eth0 before it goes to take a trip?
I tested with iptables DNAT, ip route add 200.1.1.1/36 dev eth4 ..... and did not work. 
Can somebody give me an advise or a clue on how should I do something like this? an with the proxy? how can I specify on witch eth to go out depending from where it came from TOS Mark?
I olso would like a recomendation on some good books, please.

That's all folks, 


                        well thank you verry much for the advise.

Krepper Guillermo (Billy)




[-- Attachment #2: Type: text/html, Size: 8779 bytes --]

             reply	other threads:[~2001-04-18 11:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-18 11:27 Krepper Guillermo [this message]
2001-04-19 13:44 ` [LARTC] I need some advise from a routing Guru !! Ramin Alidousti
2001-04-19 15:53 ` billy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-98767958826502@msgid-missing \
    --to=billy@ciudadglobal.com.ar \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox