From: "Leigh Waldie" <lartc@thisisnota.co.uk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Routing question
Date: Fri, 06 Jun 2003 10:08:48 +0000 [thread overview]
Message-ID: <marc-lartc-105489418826550@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105489071823469@msgid-missing>
>>I found this to be excellent...
>>
>>http://www.linuxpowered.com/HOWTO/Adv-Routing-HOWTO/lartc.rpdb.multiple-links.html
>>
>>
>That's the exact same thing I used, but I don't have separate ethernet
>cards, which this set up relies on. Both my routers are on a switch,
>along with my server, so everything goes over eth0
>
>ip route add default dev eth0 src 10.1.1.1
>ip route add 10.1.1.1 dev eth0 src 10.1.1.1
>
>don't work.
The routing system needs to be able to differentiate between packets coming from the two
routers, so I would suggest that you put another nic in the machine. this setup makes
source based routing very easy to implement. I don't know if multihoming your current
eth0 nic would make it possible because both routers are on the same network...
>
>I also can't find any info on creating tables T1, and T2
>
Go to the link I gave and click "Prev" - the info you need is on that page...
>Alex
Leigh
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-06-06 10:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-06 9:07 [LARTC] Routing question Alex Schaft
2003-06-06 9:23 ` Leigh Waldie
2003-06-06 10:08 ` Leigh Waldie [this message]
2004-11-01 14:51 ` [LARTC] routing question routing
2004-11-01 16:16 ` routing
2004-11-01 17:18 ` Rene Gallati
2006-09-05 19:08 ` [LARTC] Routing question John Fulton
2006-09-07 6:42 ` Leigh Sharpe
2007-04-05 16:58 ` [LARTC] Routing Question Fernando Blankleder
2007-04-06 19:56 ` Fw: " Fernando Blankleder
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-105489418826550@msgid-missing \
--to=lartc@thisisnota.co.uk \
--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