From: Bill Davidsen <davidsen@tmr.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@vger.kernel.org, linux-net@vger.kernel.org,
lartc <lartc@mailman.ds9a.nl>
Subject: Re: [announce] iproute2 2.6.19-061214
Date: Wed, 31 Jan 2007 12:37:50 -0500 [thread overview]
Message-ID: <45C0D3EE.4040605@tmr.com> (raw)
In-Reply-To: <20061214154627.78ff25c0@freekitty>
Stephen Hemminger wrote:
> This is an update to the iproute2 command set.
> It can be downloaded from:
> http://developer.osdl.org/dev/iproute2/download/iproute2-2.6.18-061214.tar.gz
>
The 2.6.18 should be 2.6.19. Am I the first person to actually try that
link?
> Repository:
> git://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git
>
> For more info on iproute2 see:
> http://linux-net.osdl.org/index.php/Iproute2
>
> The version number includes the kernel version to denote what features are
> supported. The same source should build on older systems, but obviously the
> newer kernel features won't be available. As much as possible, this package
> tries to be source compatible across releases.
>
> Changes from 2.6.18-061002 to 2.6.19-061214:
>
> Boian Bonev:
> Display local route table name correctly in output of:
>
> Hasso Tepper:
> Fixes for tc help commands
>
> jamal:
> Multicast computation off by one
> Update generic netlink header
> Add controller support for new features exposed
> clarify "ok" and "pass"
> Fix missing class/flowid oddity
> Mention need for db dev package
> update xfrm async events
> make muticast group to bitmask conversion generic
> update xfrm monitoring to use nl_mgrp
>
> Masahide NAKAMURA:
> ADDR: Fix print format for lifetimes.
> ADDR: Enable to add IPv6 address with valid/preferred lifetime.
> ADDR: Define 0xFFFFFFFFU as INFINITY_LIFE_TIME regarding to the kernel.
> TUNNEL: Split common functions to export them.
> TUNNEL: Import ip6tunnel.c.
> TUNNEL: IPv6-over-IPv6 tunnel support.
> XFRM: sub policy support.
> XFRM: Mobile IPv6 route optimization support.
> XFRM: support report message by monitor.
> XFRM: Mobility header support.
>
> Noriaki TAKAMIYA:
> ADDR: Add the 'change' and 'replace' commands to the IPv6 address manipulation context.
>
> Patrick McHardy:
> [IPROUTE]: Add support for routing rule fwmark masks
>
> Stephen Hemminger:
> Man page for ss submitted by Alex Wirt
> Typo in man page
> Trap possible overflow in usec values to netem
> genl Makefile LDFLAGS
> SA and SP in IPSec BEET mode.
> Route metrics decode bug.
> lnstat man page
> Man page for rtmon
> Update to 2.6.19 headers
> Add more includes
> Change to post 2.6.19 sanitized headers
> Eliminate trailing whitespace
>
>
> Thomas Graf:
> Add support for inverted selectors
> Add rule notification support to ip monitor
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
prev parent reply other threads:[~2007-01-31 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 23:46 [announce] iproute2 2.6.19-061214 Stephen Hemminger
2007-01-31 17:37 ` Bill Davidsen [this message]
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=45C0D3EE.4040605@tmr.com \
--to=davidsen@tmr.com \
--cc=lartc@mailman.ds9a.nl \
--cc=linux-net@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).