From: bert hubert ahu@ds9a.nl
To: lartc@vger.kernel.org
Subject: [LARTC] iproute2 and routing entries
Date: Sun, 05 Nov 2000 21:57:35 +0000 [thread overview]
Message-ID: <marc-lartc-98373938216895@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216886@msgid-missing>
<PRE>On Thu, Nov 02, 2000 at 06:35:48PM +0100, Michael Schoen wrote:
><i> Hi guys,
</I>><i>
</I>><i> i am just playing around with iproute2 and some questions came to my mind.
</I>><i>
</I>><i> I´m wondering why I get a route entry for the subnet of eth0s 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 often need some
</I>><i> strange routing set-ups. Is it possible to avoid this behaviour, meaning I
</I>><i> only get routing entries if I really set them by myself?
</I>
This behaviour has been hotly contested on the linux kernel mailinglist,
perhaps the archives can tell you if there is a way around this.
Also read the 'ifconfig replacement script' bij Alexey which contains Deeper
Magic which might be useful.
Regards,
bert hubert
--
PowerDNS Versatile DNS Services
Trilab The Technology People
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
</PRE>
next prev parent reply other threads:[~2000-11-05 21:57 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 [this message]
2000-11-06 11:39 ` Martijn
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-98373938216895@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.