All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Alexandru Dragoi <waruiinu@gmail.com>
To: Funieru Bogdan <fbsoft01@yahoo.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Routing problem with 3 interfaces
Date: Tue, 25 Jan 2005 14:11:47 +0200	[thread overview]
Message-ID: <3063e5050125041174f15b65@mail.gmail.com> (raw)
In-Reply-To: <20050125110351.89351.qmail@web53705.mail.yahoo.com>

Looking at those 2 providers (once sisters), I would wonder to have
your setup working. Also i can see you use nat in PREROUTING, wich is
wrong, you should do SNAT in POSTROUTING -o $isp2 , I'm also not that
sure your 'ip rule's are completly correct, you never know how you end
up in a route loop.


On Tue, 25 Jan 2005 03:03:51 -0800 (PST), Funieru Bogdan
<fbsoft01@yahoo.com> wrote:
> Hello all
> I'm having a little problem routing my 2 internet
> connections to my LAN, here is the schem of my network
> 
>                   ISP1                            ISP2
>                    |                               |
>         IP:193.230.183.11               IP:193.19.192.108
>         GTW:193.230.183.4               GTW 193.19.192.65
>                    |                               |
>                    |                               |
>                 SERVER1 <---routable ip---------SERVER2 -> eth0 to
> ISP2
> to server2 via  eth1<-                                  -> eth1 to other comp ip add
> 83.175.128.96
> ip 83.175.128.123                                       -> eth2 to server1 ip
> 83.175.128.123
> to LAN via      eth2<-
> ip 192.168.1.1
> to ISP1         eth0<-
> 
> i hope that the schematic is a little bit
> understandful now the big problem is that i wan't to
> give acces to my LAN on both connections, but on
> different ip's
> Now i want everything that comes from ip 141.85.0.0/16
> to go to server2 and everything else to go through
> server1
> 
> i've done a little bit of researching but all i ended
> up was trash, because when i try to link to the ip
> 141.85.0.0/16 i get through tracert that the packets
> go ok until they stop at the gateway of server2 , ip
> 193.19.192.65,and from here it freazes,it doesn't go
> anywhere at all.
> 
> i have the following rule add
> route add default gw 193.230.183.4
> #i tryed with
> ip route add default via 83.175.128.123 table
> net_retea1
> ip rule add dev eth1 table net_retea1
> ip rule add from 192.168.1.2 to 141.85.0.0/16 table
> net_retea1
> ip rule add 83.175.128.124 table net_retea1
> iptable -t nat -A PREROUTING -i eth1 -s 192.168.1.2 -d
> 141.85.0.0/16 --to 83.1751.28.124
> 
> and i've marked the pachets as well thought it'll work
> , but it didn't ... how do i make it work ?
> thx in advance
> nothing but the best Bogdan
> 
> =====
> -------------------
> Funieru Bogdan
> Admin MosilorNET
> 
> Contact Info:
> Mob:
> 0742158956
> 0726592752
> 0744301506(very rare)
> -------------------
> 
> 
> __________________________________
> Do you Yahoo!?
> Read only the mail you want - Yahoo! Mail SpamGuard.
> http://promotions.yahoo.com/new_mail
> 
> 


-- 
Bla bla


      reply	other threads:[~2005-01-25 12:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-25 11:03 Routing problem with 3 interfaces Funieru Bogdan
2005-01-25 12:11 ` George Alexandru Dragoi [this message]

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=3063e5050125041174f15b65@mail.gmail.com \
    --to=waruiinu@gmail.com \
    --cc=fbsoft01@yahoo.com \
    --cc=netfilter@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.