From: Daniel Bergqvist daniel@netatonce.se
To: lartc@vger.kernel.org
Subject: SV: [LARTC] iproute2 and routing entries
Date: Mon, 06 Nov 2000 12:40:15 +0000 [thread overview]
Message-ID: <marc-lartc-98373938216900@msgid-missing> (raw)
<PRE>I have used mask to /32 (255.255.255.255) to get control over the routing
table. It's useful then you want to save IP-addresses.
Regards,
Daniel
><i> -----Ursprungligt meddelande-----
</I>><i> Från: <A HREF="mailto:lartc-admin@mailman.ds9a.nl">lartc-admin@mailman.ds9a.nl</A>
</I>><i> [mailto:<A HREF="mailto:lartc-admin@mailman.ds9a.nl">lartc-admin@mailman.ds9a.nl</A>]För Martijn van Oosterhout
</I>><i> Skickat: Monday, November 06, 2000 12:40 PM
</I>><i> Till: bert hubert
</I>><i> Kopia: <A HREF="mailto:lartc@mailman.ds9a.nl">lartc@mailman.ds9a.nl</A>
</I>><i> Ämne: Re: [LARTC] iproute2 and routing entries
</I>><i>
</I>><i>
</I>><i> bert hubert wrote:
</I>><i> >
</I>><i> > On Thu, Nov 02, 2000 at 06:35:48PM +0100, Michael Schoen wrote:
</I>><i> > > Hi guys,
</I>><i> > >
</I>><i> > > i am just playing around with iproute2 and some questions
</I>><i> came to my mind.
</I>><i> > >
</I>><i> > > I´m wondering why I get a route entry for the subnet of eth0s
</I>><i> primary addr
</I>><i> > > if I use the command "ip link set eth0 up".
</I>><i> > >
</I>><i> > > I´m personally not a friend of such behaviour, because I
</I>><i> often need some
</I>><i> > > strange routing set-ups. Is it possible to avoid this
</I>><i> behaviour, meaning I
</I>><i> > > only get routing entries if I really set them by myself?
</I>><i> >
</I>><i> > This behaviour has been hotly contested on the linux kernel mailinglist,
</I>><i> > perhaps the archives can tell you if there is a way around this.
</I>><i>
</I>><i> The reason is that by setting an interface with the IP address A
</I>><i> and netmask
</I>><i> B you are implying that there is a network attached with the
</I>><i> network address
</I>><i> A&~B with the given netmask and so a route should be added appropriately.
</I>><i>
</I>><i> The last I heard was that one of the networking guys gave this
</I>><i> explanantion
</I>><i> and challenged someone to give an example of where this was the wrong
</I>><i> thing to do. The thread died there IIRC.
</I>><i>
</I>><i> Personally I think it's a great feature because in at least 99.99% of
</I>><i> cases it's exactly what you want and I havn't found an example of the
</I>><i> other 0.01%.
</I>><i>
</I>><i> --
</I>><i> Martijn van Oosterhout <<A HREF="mailto:kleptog@cupid.suninternet.com">kleptog@cupid.suninternet.com</A>>
</I>><i> <A HREF="http://cupid.suninternet.com/~kleptog/">http://cupid.suninternet.com/~kleptog/</A>
</I>><i>
</I>><i> _______________________________________________
</I>><i> LARTC mailing list / <A HREF="mailto:LARTC@mailman.ds9a.nl">LARTC@mailman.ds9a.nl</A>
</I>><i> <A HREF="http://mailman.ds9a.nl/mailman/listinfo/lartc">http://mailman.ds9a.nl/mailman/listinfo/lartc</A> HOWTO:
</I><A HREF="http://ds9a.nl/2.4Routing/">http://ds9a.nl/2.4Routing/</A>
</PRE>
reply other threads:[~2000-11-06 12:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-98373938216900@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.