All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martijn van Oosterhout kleptog@cupid.suninternet.com
To: lartc@vger.kernel.org
Subject: [LARTC] iproute2 and routing entries
Date: Mon, 06 Nov 2000 11:39:44 +0000	[thread overview]
Message-ID: <marc-lartc-98373938216898@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216886@msgid-missing>

<PRE>bert hubert wrote:
&gt;<i> 
</I>&gt;<i> On Thu, Nov 02, 2000 at 06:35:48PM +0100, Michael Schoen wrote:
</I>&gt;<i> &gt; Hi guys,
</I>&gt;<i> &gt;
</I>&gt;<i> &gt; i am just playing around with iproute2 and some questions came to my mind.
</I>&gt;<i> &gt;
</I>&gt;<i> &gt; I´m wondering why I get a route entry for the subnet of eth0s primary addr
</I>&gt;<i> &gt; if I use the command &quot;ip link set eth0 up&quot;.
</I>&gt;<i> &gt;
</I>&gt;<i> &gt; I´m personally not a friend of such behaviour, because I often need some
</I>&gt;<i> &gt; strange routing set-ups. Is it possible to avoid this behaviour, meaning I
</I>&gt;<i> &gt; only get routing entries if I really set them by myself?
</I>&gt;<i> 
</I>&gt;<i> This behaviour has been hotly contested on the linux kernel mailinglist,
</I>&gt;<i> perhaps the archives can tell you if there is a way around this.
</I>
The reason is that by setting an interface with the IP address A and netmask
B you are implying that there is a network attached with the network address
A&amp;~B with the given netmask and so a route should be added appropriately.

The last I heard was that one of the networking guys gave this explanantion
and challenged someone to give an example of where this was the wrong
thing to do. The thread died there IIRC.

Personally I think it's a great feature because in at least 99.99% of 
cases it's exactly what you want and I havn't found an example of the
other 0.01%.

-- 
Martijn van Oosterhout &lt;<A HREF="mailto:kleptog@cupid.suninternet.com">kleptog@cupid.suninternet.com</A>&gt;
<A HREF="http://cupid.suninternet.com/~kleptog/">http://cupid.suninternet.com/~kleptog/</A>


</PRE>

  parent reply	other threads:[~2000-11-06 11:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-02 17:35 [LARTC] iproute2 and routing entries Michael
2000-11-05 21:57 ` bert
2000-11-06 11:39 ` Martijn [this message]
2000-11-06 12:35 ` Michael

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-98373938216898@msgid-missing \
    --to=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.