From: Whit Blauvelt <whit@transpect.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] RTNETLINK answers: File exists
Date: Tue, 27 Nov 2001 01:01:53 +0000 [thread overview]
Message-ID: <marc-lartc-100682296421262@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100679899116747@msgid-missing>
There is no rule that says there cannot be more than one default - as is
clear because it was possible to set up more than one default route to
begine with! And the error message, "File exists," does not seem to be true
at all, or pertinent. I was not asking to create a file, but a route.
So I take it that the "ip" utility doesn't follow standard procedures and
practices regarding syntax and error messages? Why has this been allowed in
code that is integrated with the Linux kernel? Was Linus sleeping?
Whit
On Mon, Nov 26, 2001 at 07:49:50PM +0100, Wojtek Sobola wrote:
> simple... default gateway can be only one :>
> as the name says ;>
>
> ----- Original Message -----
> From: "Whit Blauvelt" <whit@transpect.com>
> To: <LARTC@mailman.ds9a.nl>
> Sent: Monday, November 26, 2001 7:22 PM
> Subject: [LARTC] RTNETLINK answers: File exists
>
>
> > Can someone tell me what concept I'm missing here. The setup is simple. I
> > have two default routes after ifup operations. I use "ip route del" to
> > remove one, but then decide to add it back. The attempt is refused. Why?
> >
> > # ip route ls
> > 66.95.83.208/28 dev eth1 proto kernel scope link src 66.95.83.210
> > 65.84.205.96/27 dev eth2 proto kernel scope link src 65.84.205.104
> > 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.245
> > 66.0.0.0/8 dev eth1 proto kernel scope link src 66.95.83.210
> > default via 65.84.205.97 dev eth2
> > default via 66.95.83.209 dev eth1
> >
> > # ip route del default via 65.84.205.97 dev eth2
> >
> > # ip route ls
> > 66.95.83.208/28 dev eth1 proto kernel scope link src 66.95.83.210
> > 65.84.205.96/27 dev eth2 proto kernel scope link src 65.84.205.104
> > 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.245
> > 66.0.0.0/8 dev eth1 proto kernel scope link src 66.95.83.210
> > default via 66.95.83.209 dev eth1
> >
> > # ip route add default via 65.84.205.97 dev eth2
> > RTNETLINK answers: File exists
> >
> > Thanks,
> > Whit
> >
> > _______________________________________________
> > LARTC mailing list / LARTC@mailman.ds9a.nl
> > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO:
> http://ds9a.nl/2.4Routing/
> >
_______________________________________________
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 1:01 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
2001-11-27 1:01 ` Whit Blauvelt [this message]
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-100682296421262@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.