From: Brian Haley <brian.haley@hp.com>
To: Felix von Leitner <felix-kernel@fefe.de>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: socket api problem: can't bind an ipv6 socket to ::ffff:0.0.0.0
Date: Tue, 17 Mar 2009 15:21:52 -0400 [thread overview]
Message-ID: <49BFF850.7060906@hp.com> (raw)
In-Reply-To: <20090317180840.GC13270@codeblau.de>
Top-posting so others can see your off-list rant in full. I see no reason to
help you any further, even though I did have a patch that would change this
behavior for you. Good luck with your "biggest noncommercial Internet messaging
infrastructure" in the world.
-Brian
Felix von Leitner wrote:
>> Please show me a porting guide that even mentions supporting IPv4-only mode
>> through an IPv6 socket by using this method. There is none that I know of.
>
> Are you kidding me?
> A _porting guide_?!?
>
> If you are trying to troll me, you just succeeded.
>
> Now please make room so the adults can talk about the issue at hand
> while you are putting up straw men.
>
>>> Did I mention *BSD and OSX allow this?
>> That was their decision, and it doesn't mean it's the right thing to do.
>
> Riiiight.
>
> There is an old joke. The Joneses are driving on the freeway, when the
> radio sounds a warning. "Warning! There is a car driving the wrong way
> on the freeway!" Says grandpa (who is driving the car) "what do you
> mean, one guy? Hundreds!!"
>
> Sometimes, if there are two ways to read something, and your users tell
> you which way they want it, and the competition does it the way the
> users want, and you don't, sometimes, in that case, YOU ARE WRONG.
>
> It's that easy.
>
> Hey, you have an hp.com email address. Why don't you check out how
> HP-UX handles this.
>
>> Compare your bittorrent server to Apache, which is probably the most widely-used
>> server application in the world. It doesn't do what you're trying to do. See
>> http://httpd.apache.org/docs/2.2/bind.html and/or browse the source code.
>
> What is this supposed to be? Name dropping?
>
> I'm not impressed.
>
> And Apache never won any speed or scalability records. Just because
> many people use Apache does not mean it's a good piece of software. You
> know, many more people use Windows than Linux. That does not make
> Windows the standard to follow. Hey, many people use sendmail! And
> BIND!
>
> Felix
>
next prev parent reply other threads:[~2009-03-17 19:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 23:48 socket api problem: can't bind an ipv6 socket to ::ffff:0.0.0.0 Felix von Leitner
2009-03-17 0:00 ` Stephen Hemminger
2009-03-17 0:18 ` Felix von Leitner
2009-03-17 2:26 ` Brian Haley
2009-03-17 2:47 ` Eric Dumazet
2009-03-17 8:51 ` Bjørn Mork
2009-03-17 16:00 ` Brian Haley
2009-03-17 12:58 ` Felix von Leitner
2009-03-17 13:47 ` Vlad Yasevich
2009-03-17 14:14 ` Felix von Leitner
2009-03-17 14:57 ` Vlad Yasevich
2009-03-17 17:51 ` Felix von Leitner
2009-03-17 15:21 ` Eric Dumazet
2009-03-17 18:01 ` Felix von Leitner
2009-03-17 15:59 ` Brian Haley
[not found] ` <20090317180840.GC13270@codeblau.de>
2009-03-17 19:21 ` Brian Haley [this message]
2009-03-17 19:31 ` David Miller
2009-03-17 21:05 ` Vlad Yasevich
2009-03-17 21:05 ` [RFC PATCH 1/4] ipv6: Disallow binding to v4-mapped address on v6-only socket Vlad Yasevich
2009-03-17 21:06 ` [RFC PATCH 2/4] ipv6: Allow ipv4 wildcard binds after ipv6 address binds Vlad Yasevich
2009-03-17 21:06 ` [RFC PATCH 3/4] ipv6: Make v4-mapped bindings consitant with IPv4 Vlad Yasevich
2009-03-17 21:06 ` [RFC PATCH 4/4] ipv6: Fix conflict resolutions during ipv6 binding Vlad Yasevich
2009-03-18 9:13 ` socket api problem: can't bind an ipv6 socket to ::ffff:0.0.0.0 Jarek Poplawski
2009-03-18 21:36 ` David Miller
2009-03-18 21:53 ` Jarek Poplawski
2009-03-19 0:32 ` David Miller
2009-03-17 9:03 ` Bjørn Mork
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=49BFF850.7060906@hp.com \
--to=brian.haley@hp.com \
--cc=felix-kernel@fefe.de \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.