From: "Bob Puff@NLE" <bob@nleaudio.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Suggestion for improvements to nexthop implementation
Date: Thu, 24 May 2001 16:24:38 +0000 [thread overview]
Message-ID: <marc-lartc-99072111417950@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99069930816800@msgid-missing>
> I have a server connected :
>
> eth2 ADSL 500kbps ISP 1
> eth1 Cable 1000kbps ISP 2
> eth0 LAN 100Mbps
I would like to see how this is also accomplished with the 2.2.x kernels. Thanks.
Bob
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
prev parent reply other threads:[~2001-05-24 16:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-24 10:18 [LARTC] Suggestion for improvements to nexthop implementation Rolf MIssing
2001-05-24 16:24 ` Bob Puff@NLE [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=marc-lartc-99072111417950@msgid-missing \
--to=bob@nleaudio.com \
--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.