netdev
[Top] [All Lists]

Re: IPv6+2.4.x: ipv6_local_port_range implementation plans + netfilter6

To: Peter Bieringer <pb@xxxxxxxxxxxx>
Subject: Re: IPv6+2.4.x: ipv6_local_port_range implementation plans + netfilter6
From: Andi Kleen <ak@xxxxxx>
Date: Wed, 13 Jun 2001 02:21:21 +0200
Cc: Maillist netdev <netdev@xxxxxxxxxxx>, Andi Kleen <ak@xxxxxx>
In-reply-to: <12580000.991764372@localhost>; from pb@bieringer.de on Tue, Jun 05, 2001 at 08:06:12PM +0200
References: <20010603132942.A2582@fred.local> <12580000.991764372@localhost>
Sender: owner-netdev@xxxxxxxxxxx
[Just back from vacation, sorry for late answer]

On Tue, Jun 05, 2001 at 08:06:12PM +0200, Peter Bieringer wrote:
> --On Sunday, June 03, 2001 01:29:42 PM +0200 Andi Kleen <ak@xxxxxx> 
> wrote:
> 
> > On Sat, Jun 02, 2001 at 11:03:24AM +0200, Peter Bieringer wrote:
> >> Hi all,
> >>
> >> are there any plans to implement "ipv6_local_port_range" in the
> >> future like on IPv4?
> >
> > The IPv4 sysctl is shared between IPv4 and IPv6, because v4 and v6
> > share a common port space.
> Thanks for reply.
> 
> Two more questions:
> 
> 1) exists there any documentation beside the source code itself which 
> "/proc/sys/net/ipv4" values will be also used for IPv6?

No, you have to do RTFS currently. 

> 
> 2) are there any plans for 2.5 or later to split off common used proc 
> switches to another directory like "/proc/sys/net/ip"? There was a 
> thread sometimes ago relating 'howto make IPv4 as module' which can 
> be take advantage of such split off (I'm thinking about IPv6 only 
> clients with Linux network stack)...

I know of no such plans.

-Andi

<Prev in Thread] Current Thread [Next in Thread>