From: Whit Blauvelt <whit@transpect.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] RTNETLINK answers: File exists
Date: Tue, 27 Nov 2001 00:51:32 +0000 [thread overview]
Message-ID: <marc-lartc-100682237119674@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100679899116747@msgid-missing>
Thanks Julian,
Does anyone know why the heck "ip route" has been programmed so that it
allows something to be deleted that by the same syntax can't be added? This
seems to me to be very, very wrong. Anything that "ip route" shows should be
valid syntax, both for deletion and adding. If the utility is more fussy
about what can be added than what can be deleted, this is very bad
programming. Why has such bad programming been allowed in code that
interacts with the Linux kernel?
Thanks,
Whit
On Mon, Nov 26, 2001 at 08:50:33PM +0200, Julian Anastasov wrote:
>
> Hello,
>
> On Mon, 26 Nov 2001, Whit Blauvelt wrote:
>
> > default via 66.95.83.209 dev eth1
> >
> > # ip route add default via 65.84.205.97 dev eth2
> > RTNETLINK answers: File exists
>
> It seems you are trying to use alternative routes. Use
> "ip route append" instead. You can also look at the following
> URL where the alt routes are extended:
>
> http://www.linuxvirtualserver.org/~julian/
> look for "Static, Alternative Routes, Dead Gateway Detection, NAT"
>
> and also in dgd-usage.txt
>
> > Thanks,
> > Whit
>
> Regards
>
> --
> Julian Anastasov <ja@ssi.bg>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-11-27 0:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 18:22 [LARTC] RTNETLINK answers: File exists Whit Blauvelt
2001-11-26 18:50 ` Julian Anastasov
2001-11-26 18:56 ` Greg Scott
2001-11-26 19:18 ` Julian Anastasov
2001-11-27 0:51 ` Whit Blauvelt [this message]
2001-11-27 1:01 ` Whit Blauvelt
2001-11-27 1:12 ` Whit Blauvelt
2001-11-27 10:46 ` Julian Anastasov
2005-06-10 15:07 ` Dariusz Dwornikowski
2005-06-11 2:37 ` gypsy
2005-06-11 9:41 ` Dariusz Dwornikowski
2005-06-11 10:11 ` Thomas Graf
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-100682237119674@msgid-missing \
--to=whit@transpect.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.