search

cumulus13 / memcached

Automatically exported from code.google.com/p/memcached
0 stars 0 forks source link

memcached unable to bind to an ipv6 address #310

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. memcached -l ::1

What is the expected output? What do you see instead?
- Expected is that memcached binds to the interface

- Actual result
Invalid port number: ":1"failed to listen on TCP port 11211: Success

What version of the product are you using? On what operating system?
1.4.15 on Ubuntu 12.04

It does work in Debian 6.0 (memcached 1.4.5) but not with anything newer I 
tested... 

Please provide any additional information below.

Original issue reported on code.google.com by a...@ak.cx on 12 Feb 2013 at 7:05

GoogleCodeExporter commented 9 years ago 
Work around is to use an IPv6 only DNS name as parameter to L

Original comment by a...@ak.cx on 12 Feb 2013 at 7:19

GoogleCodeExporter commented 9 years ago 
Hello,

The same issue.
I can't bind an ipv6 address.

Please help.

Original comment by Stefan.F...@gmail.com on 5 Dec 2013 at 9:03

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Pull request https://github.com/memcached/memcached/pull/98

allows to specify IPv6 address without port or IPv6 address enclosed in [] with 
or without port (RFC3986 style recommended by RFC5952)

-l IPv6
-l [IPv6]
-l [IPv6]:port

Original comment by github...@gmail.com on 9 Jan 2015 at 11:25

GoogleCodeExporter commented 9 years ago 
This is a serious defect/flaw.  When will it be fixed in an official release?

Original comment by quanah.g...@gmail.com on 16 Feb 2015 at 4:50

GoogleCodeExporter commented 9 years ago 
Same problem here! I am unable to run memcached in a Dual-Stacked network 
environment!

Original comment by thiagocm...@gmail.com on 22 Feb 2015 at 2:22

GoogleCodeExporter commented 9 years ago 
I know that it's not really a solution and this still needs to be fixed,
but running memcached on 127.0.0.1 and haproxy on external ip's with
127.0.0.1:11211 as a backend is a workaround.
Op 22 feb. 2015 03:22 schreef <memcached@googlecode.com>:

Original comment by r...@renediepstraten.nl on 22 Feb 2015 at 5:00

GoogleCodeExporter commented 9 years ago 
Why it isn't a "real solution"? I'm planning to put this into production... Is 
it not recommended?

I REALLY need to bind memcached on an IPv6 address, since my networks are 
already IPv6-Only.

Original comment by thiagocm...@gmail.com on 6 May 2015 at 12:17