[rabbitmq-discuss] IPv6 issue?

Thu May 8 14:56:09 BST 2014

2014-05-08 15:34 GMT+02:00 Simon MacMullen-2 [via RabbitMQ] <
ml-node+s1065348n35425h38 at n5.nabble.com>:

> On 08/05/14 14:00, gdubicki wrote:
> > For the reference I would like to report that I have had similar problem
> > with rabbitmq 2.6.16:
>
> There was no RabbitMQ 2.6.16 release.
>
> Rabbitmq 3.1.5, sorry.

> I have had IPv6 turned off in sysctl.conf via:
> >
> > net.ipv6.conf.all.disable_ipv6 = 1
> > net.ipv6.conf.default.disable_ipv6 = 1
> > net.ipv6.conf.lo.disable_ipv6 = 1
> >
> > ..but my rabbitmq still listened on tcp6:
> >
> > 2014-05-08 14:43:32 root at api:~ # netstat -an|grep 5672
> > tcp        0      0 0.0.0.0:15672           0.0.0.0:*
> LISTEN
> > tcp        0      0 0.0.0.0:55672           0.0.0.0:*
> LISTEN
> > tcp6       0      0 :::5672                 :::*
>  LISTEN
>
> If those disable_ipv6 config items had taken effect then your system
> would not permit IPv6 connections at all. Since we can see IPv6
> connections I suggest the sysctl.conf changes did not take effect.
>
> Cheers, Simon
>

Apparently you can still bind a socket to IPv6 even if it is turned off
with sysctl - see this http://askubuntu.com/a/381623/254957 and similar
stories about sshd etc. Maybe unloading a kernel IPv6 module (if it is
compiled as a module) would help but I do not need it so much to mess with
my server's kernel.

>
> --
> Simon MacMullen
> RabbitMQ, Pivotal
> _______________________________________________
> rabbitmq-discuss mailing list
> [hidden email] <http://user/SendEmail.jtp?type=node&node=35425&i=0>
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
> http://rabbitmq.1065348.n5.nabble.com/IPv6-issue-tp11368p35425.html
>  To unsubscribe from IPv6 issue?, click here<http://rabbitmq.1065348.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=11368&code=Z2R1Ymlja2lAYmlkbGFiLnBsfDExMzY4fC00ODgxODEyMTY=>
> .
> NAML<http://rabbitmq.1065348.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>

-- 
*Grzegorz Dubicki*

*Bidlab Sp. z o.o. *
*ul. Woźna 9c/2, **61-777 Poznań*

*visit our website! *
*http://bidlab.pl/* <http://bidlab.pl/>
*join us on facebook!*
*https://www.facebook.com/bidlab* <https://www.facebook.com/bidlab>
*follow us on instagram!*
*www.instagram.com/bidlab* <http://www.instagram.com/bidlab>

If you are not the named recipient and receive this correspondence in
error, you must not copy, distribute or take any action in reliance on it
and you should delete it from your system and notify the sender
immediately. Thank you. Unless otherwise stated, any views or opinions
expressed are solely those of the author and do not represent those of
Bidlab Sp. z o.o.
Niniejsza wiadomość zawiera poufne informacje przeznaczone tylko dla
adresata. Jeżeli nie jesteście Państwo jej adresatem, bądź otrzymaliście ją
przez pomyłkę, prosimy o powiadomienie o tym nadawcy oraz jej trwałe
usunięcie. Odmienne zachowanie jest niezgodne z interesem Bidlab Sp. z o.o
i może naruszać prawo.

--
View this message in context: http://rabbitmq.1065348.n5.nabble.com/IPv6-issue-tp11368p35426.html
Sent from the RabbitMQ mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140508/52577ed1/attachment.html>