| To: | kuznet@xxxxxxxxxxxxx |
|---|---|
| Subject: | Re: [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Thu, 03 Oct 2002 06:02:54 -0700 (PDT) |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <200210031306.RAA29293@sex.inr.ac.ru> |
| References: | <20021003.012904.75241727.davem@redhat.com> <200210031306.RAA29293@sex.inr.ac.ru> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
From: kuznet@xxxxxxxxxxxxx Date: Thu, 3 Oct 2002 17:06:48 +0400 (MSD) No, really! __Sharing__ of port space between IPv4 and IPv6 was mad idea. It cannot generalized to other protocol families. So, IPV6_V6ONLY is really unique for IPv6. Well, actually, it could be negated: be default and the option would be called IPV6_SHARE_THIS_PORT_TO_IPV4. I think what I want to really say is that I want to provide way for ipv4 application to say "no ipv6 connections on this listening socket please". So does it make no sense at all to have IP_V4ONLY? |
| Previous by Date: | Re: [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same, kuznet |
|---|---|
| Next by Date: | Re: [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same, Pekka Savola |
| Previous by Thread: | Re: [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same, kuznet |
| Next by Thread: | Re: [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same, Pekka Savola |
| Indexes: | [Date] [Thread] [Top] [All Lists] |