From: Robert Kurjata <rkurjata@ire.pw.edu.pl>
To: lartc@vger.kernel.org
Subject: Re[2]: [LARTC] 'Help with routing'
Date: Thu, 23 Oct 2003 07:13:45 +0000 [thread overview]
Message-ID: <marc-lartc-106689379004573@msgid-missing> (raw)
Witaj nixo,
W Twoim liœcie datowanym 22 paŸdziernika 2003 (20:13:29) mo¿na przeczytaæ:
Seems like I didn't read your posting deeply enough. Before I can help
I need to know some more details.
Why are you using multipath default gateway? If you just need to make
a proper routing for two separate lans going through one machine, not
mixing them you should never use it. It's usefull for NAT-ed lan
inside, not for public IP's. Just create simple routes without
multipath. eth0 <-> eth1 and eth2 <-> eth3.
nnca> Thank you very much for the solution, but I still have a problem and I
nnca> need help :) . The problem number one has been solved. When I trace from
nnca> any computer of my LAN, It`s go out from the right ISP. But after a short
nnca> time, is like if the rute was chached and it back to the same problem.
nnca> (I´m getting paranoic :-P )
nnca> The Problem number two still happens when someone from outside trace an IP
nnca> from mi LAN. Always the before complete jump is responded for the
nnca> interface who correnspond to the other ISP.
nnca> Do you have an idea what can be the failure... or, can I call this a
nnca> failure in my config?
nnca> THANKS VERY MUCH
nnca> Nicolas Fillon
nnca> Argentina
>> Hi nixo,
>>
>> I suppose you don't preserve properly output address see my postting
>> with script from 15th October this year :)
>> (append prohibit default:)
>>
>>
>> nnca> the scheme of my LAN is the next:
>>
>> nnca> eth0 isp1 /32
>> nnca> eth1 lan de isp1 (LAN With public IP /24)
>> nnca> eth2 isp2 /32
>> nnca> eth3 lan de isp2 (LAN With public IP /26)
>>
>> nnca> ip route add 200.47.x.x/24 dev eth0 src 200.47.4.x table 1
>> nnca> ip route add default via 200.47.4.x table 1
>>
>>
>> nnca> ip route add 200.80.32.x/26 dev eth2 src 200.80.32.x table 2
>> nnca> ip route add default via 200.80.32.x table 2
>>
>>
>>
>> nnca> ip rule add from 200.47.4.x table 1
>> nnca> ip rule add from 200.80.32.x table 2
>>
>> nnca> ip route add default scope global nexthop via 200.47.4.x dev eth0
>> nexthop nnca> via
>> nnca> 200.80.32.x dev eth2
>>
>> nnca> ******
>>
>> nnca> My problem is this: when I trace from the NETWORK of ISP1,
>> sometimes the nnca> tracer go out from the gateway of ISP2 and vice
>> versa
>>
>> nnca> And when someone trace an IP from my LAN of ISP1, it`s showme as
>> before nnca> complete the gateway from ISP2 y vice versa.
>>
>>
>> nnca> Mi question is: what is wrong in my config...??? What I need to
>> put or is nnca> anything wrong with this config???.
>> nnca> THANKS VERY MUCH AND SORRY FOR MI HIGHSCHOOL ENGLISH.
>>
>>
--
Pozdrowienia,
Robert mailto:rkurjata@ire.pw.edu.pl
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2003-10-23 7:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-106689379004573@msgid-missing \
--to=rkurjata@ire.pw.edu.pl \
--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