netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonas Berlin <jberlin@niksula.hut.fi>
To: Samuel Jean <sj-netfilter@cookinglinux.org>,
	netfilter-devel@lists.netfilter.org
Subject: Re: netfilter & ipv6
Date: Thu, 10 Feb 2005 19:20:34 +0200	[thread overview]
Message-ID: <420B97E2.3090003@niksula.hut.fi> (raw)
In-Reply-To: <60195.142.169.215.10.1108046474.squirrel@142.169.215.10>

Samuel Jean wrote:

>On Thu, February 10, 2005 9:07 am, Jonas Berlin said:
>
>Hi Jonas!
>  
>
Hello Samuel!

>>  ip6tables ... -j CLASSIFY_v6 --set-class 1:20
>>
>>Although this works fine, having some modules with suffix _v6 and some
>>not is just plain confusing. Is there any way to reuse the CLASSIFY for
>>ipv6 name without conflicting with the CLASSIFY module already in pom?
>>Maybe I missed something?
>>    
>>
>
>You have to create an ipv6 directory into the CLASSIFY in pom.
>
>CLASSIFY/linux/net/ipv6/netfilter/ip6t_CLASSIFY.c
>  
>
Yeah that would be nice, but I think there is a problem: the newest 
kernels already have the ipv4 version included, and so patch-o-matic 
would either consider CLASSIFY already installed and skip it or then it 
would probably complain while installing that it there were some 
conflicts with the files. I haven't tested though, but I wouldn't assume 
it has the logic to pick out the ipv6-specific parts from the directory..

>Also, just register your target against ip6_tables with the same name
>as CLASSIFY would do with ip_tables. There's no conflict in that way.
>  
>
Yeah, it does work fine as CLASSIFY_v6..

>All of this is a AFAIK.
>  
>
Same here :D

>Thanks for your effort,
>Samuel
>  
>
Thanks for the reply.. I haven't got any others yet.

-- 
- xkr47

  parent reply	other threads:[~2005-02-10 17:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08  7:50 netfilter & ipv6 Jonas Berlin
2005-02-10 14:07 ` Jonas Berlin
2005-02-10 14:41   ` Samuel Jean
2005-02-10 15:10     ` iptables compile error: NFC_IP_TOS undeclared Alexander Piavka
2005-02-10 15:18       ` Jonas Berlin
2005-02-10 16:00         ` Alexander Piavka
2005-02-10 16:04           ` Jonas Berlin
2005-02-10 17:50             ` Patrick McHardy
2005-02-10 23:16               ` [PATCH] kill NFC_* stuff in iptables [was Re: iptables compile error: NFC_IP_TOS undeclared] Pablo Neira
2005-02-11 19:07                 ` Patrick McHardy
2005-02-11 21:47                   ` Pablo Neira
2005-02-12  1:32                     ` Patrick McHardy
2005-02-12 22:25                       ` Pablo Neira
2005-02-12 23:34                         ` Patrick McHardy
2005-02-10 17:20     ` Jonas Berlin [this message]
2005-02-10 21:36   ` netfilter & ipv6 Sven-Haegar Koch
2005-02-15  1:29     ` Jonas Berlin
     [not found] ` <53965.213.236.112.75.1107867276.squirrel@213.236.112.75>
2005-02-10 23:15   ` ULOG target for ipv6 Jonas Berlin
2005-02-11 22:10     ` netfilter question Pedro Fortuna
2005-02-14 23:25     ` ULOG target for ipv6 Harald Welte
2005-02-15  0:11       ` Jonas Berlin

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=420B97E2.3090003@niksula.hut.fi \
    --to=jberlin@niksula.hut.fi \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=sj-netfilter@cookinglinux.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).