From: "Dale Gallagher" <foobar@mighty.co.za>
To: lartc@vger.kernel.org
Subject: [LARTC] iproute2 and kernel 2.6.1/2
Date: Wed, 11 Feb 2004 13:51:57 +0000 [thread overview]
Message-ID: <web-232075786@mail01.infosat.net> (raw)
In-Reply-To: <web-231748431@mail01.infosat.net>
Hi there
I sent this earlier today, but haven't seen it on the list.
I appologise if this ends up being a duplicate.
I've searched the archives and googled for a solution with
no success - has anyone successfully built iproute2 under
kernel 2.6.1, or 2.6.2? I've tried various releases, each
compile aborting with different errors.
If this is wishful thinking at this stage, does anyone have
a suitable solution for the "Routing for multiple uplinks"
scenario? ie. traffic which arrives on a particular
interface is setup to leave via the same interface. I have
2 NICs, each on a different subnet, both connected to the
Net. Will probably be running 2 IPs on the first and 1 on
the second.
Thanks
Dale
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-02-11 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 7:02 [LARTC] iproute2 and kernel 2.6.1/2 Dale Gallagher
2004-02-11 13:51 ` Dale Gallagher [this message]
2004-02-12 1:07 ` Corey Hickey
2004-02-12 2:27 ` Corey Hickey
2004-02-12 11:50 ` Dale Gallagher
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=web-232075786@mail01.infosat.net \
--to=foobar@mighty.co.za \
--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 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.