From: Patrick McHardy <kaber@trash.net>
To: Valdis.Kletnieks@vt.edu
Cc: Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: Linux 2.6.16-rc1
Date: Wed, 18 Jan 2006 02:41:46 +0100 [thread overview]
Message-ID: <43CD9CDA.6030509@trash.net> (raw)
In-Reply-To: <200601172106.k0HL6LMW008241@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
> On Tue, 17 Jan 2006 00:19:56 PST, Linus Torvalds said:
>
>
>>And largish networking updates: there's a "common netfilter" setup now,
>>which you'll notice when you do "make config" or equivalent, since a lot
>>of the netfilter rules now work on ipv4 and/or ipv6 rather than having
>>separate (and duplicate) versions for each.
>
>
> Hooray! Finally. ;)
>
> Does this require modprobing of the modules by hand, or is there a version
> of iptables in the pipe that knows how to do this? I checked the CVS snapshot
> directory on ftp.netfilter.org last night, and the latest one there didn't
> know about this yet.
The modules have aliases for their old names, so they should get
autoloaded. The matches and targets that didn't exist for IPv6
before need new extensions in userspace before they can be used
though.
next prev parent reply other threads:[~2006-01-18 1:42 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 8:19 Linux 2.6.16-rc1 Linus Torvalds
2006-01-17 13:16 ` Prakash Punnoor
2006-01-17 13:36 ` Jeff Garzik
2006-01-17 13:49 ` Prakash Punnoor
2006-01-17 16:25 ` Gene Heskett
2006-01-17 18:05 ` Mauro Carvalho Chehab
2006-01-17 20:38 ` Gene Heskett
2006-01-17 17:39 ` Diego Calleja
2006-01-17 18:25 ` Linus Torvalds
2006-01-17 19:06 ` Diego Calleja
2006-01-17 20:08 ` Jan Engelhardt
2006-01-17 21:04 ` Antonio Vargas
2006-01-17 22:05 ` Jan Engelhardt
2006-01-20 8:15 ` L. A. Walsh
2006-01-20 8:28 ` David S. Miller
2006-01-20 8:47 ` Russell King
2006-01-18 0:22 ` Linux 2.6.16-rc1 -- which gcc version? Jeff Chua
2006-01-18 1:14 ` Linus Torvalds
2006-01-18 7:00 ` Arjan van de Ven
2006-01-19 23:42 ` Linux 2.6.16-rc1 Bill Davidsen
2006-01-17 19:27 ` David R
2006-01-18 4:59 ` Greg KH
2006-01-18 9:28 ` David R
2006-01-18 20:57 ` David R
2006-01-18 21:04 ` Greg KH
2006-01-17 19:54 ` Linux 2.6.16-rc1 - hrtimer hotfix Thomas Gleixner
2006-01-17 20:08 ` Lee Revell
2006-01-17 20:12 ` Thomas Gleixner
2006-01-17 21:06 ` Linux 2.6.16-rc1 Valdis.Kletnieks
2006-01-18 1:41 ` Patrick McHardy [this message]
2006-01-17 21:54 ` Eyal Lebedinsky
2006-01-17 23:27 ` Sam Ravnborg
2006-01-18 7:59 ` Jean Delvare
2006-01-18 9:15 ` Sam Ravnborg
2006-01-18 10:01 ` Kurt Wall
2006-01-18 21:10 ` Eyal Lebedinsky
2006-01-19 1:40 ` Kurt Wall
2006-01-18 11:24 ` Eyal Lebedinsky
2006-01-18 12:42 ` Sam Ravnborg
2006-01-18 12:13 ` Jean Delvare
2006-01-18 13:22 ` Jan Engelhardt
2006-01-18 18:12 ` Jean Delvare
2006-01-18 20:14 ` Jan Engelhardt
2006-01-18 20:32 ` Sam Ravnborg
2006-01-18 20:54 ` Bryan O'Sullivan
2006-01-18 21:20 ` Sam Ravnborg
2006-01-18 21:47 ` Bryan O'Sullivan
2006-02-07 12:42 ` Jean Delvare
2006-02-07 16:55 ` Bryan O'Sullivan
2006-01-18 16:15 ` Johannes Stezenbach
2006-01-18 8:44 ` Eyal Lebedinsky
2006-01-27 0:06 ` Linux 2.6.16-rc1 - usb printer problems Helge Hafting
2006-01-27 22:52 ` Greg KH
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=43CD9CDA.6030509@trash.net \
--to=kaber@trash.net \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=torvalds@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