From: Mike Fedyk mfedyk@matchmail.com
To: lartc@vger.kernel.org
Subject: [LARTC] Complicated multipath touting
Date: Sat, 03 Mar 2001 04:16:00 +0000 [thread overview]
Message-ID: <marc-lartc-98373940417089@msgid-missing> (raw)
<PRE>Expert wrote:
><i>
</I>><i> Hello all
</I>><i>
</I>><i> Maybe it is only complicated for me, maybe someone
</I>><i> knows how to do it better?
</I>><i>
</I>><i> I would like to make redundant path between host
</I>><i> in the Internet
</I>><i> (I will call it ExternalDataServer), and host in
</I>><i> my Lan (InternalDataServer)
</I>><i>
</I>><i> ExternalDataServer Router (iproute2)
</I>><i>
</I>><i> 12.34.56.67 (only one IP) <---> 22.33.44.55 eth0
</I>><i>
</I>><i> <---> 33.44.55.66 ppp0
</I>><i> 44.55.66.1 eth1 <-
</I>
You want to use eth0 and ppp0 at the same time, or when eth0 becomes
unreachable?
><i> --> InternalDataServer
</I>><i>
</I>><i> 44.55.66.77
</I>><i>
</I>><i> Route to InternalDataServer is fixed, I cannot
</I>><i> changed it.
</I>><i> It is described in routing table of my ISP.
</I>><i>
</I>><i> I tried to specify src addres as src of router,
</I>><i> and then
</I>><i> use NAT to translate adress coming from
</I>><i> 12.34.56.67 to router as 44.55.66.77
</I>><i> (forward everything to this addres)
</I>><i> Does it make sense, could it work?
</I>><i>
</I>Uhmm, no. please give more specifics. How is router connected to the internet?
What exactly is the problem? You can't access them in the way you specified,
can you access it another way?
Do you have firewall rules? ip rule commands? ip route commands?
Mike
</PRE>
next reply other threads:[~2001-03-03 4:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-03 4:16 Mike [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-27 5:34 [LARTC] Complicated multipath touting Expert
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-98373940417089@msgid-missing \
--to=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 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.