search for: ipv6_v6on

Hi, Dear OpenSSH support, I'm writing to ask whether this bug is fixed in your openSSH 6.0. If no, do you have any plan? https://bugzilla.redhat.com/show_bug.cgi?id=640857 Regards, Carol

...e been experiencing a problem with using X11 forwarding on an IPv6 enabled host (both CentOS 4.3 and Feddora Core 5 in x86) when X11UseLocalhost is off. Having looked at the code and the previous discussion regarding http://bugzilla.mindrot.org/show_bug.cgi?id=164 I think the problem is due to the IPV6_V6ONLY code interacting poorly with the DONT_TRY_OTHER_AF hack. Basically, on current Linux systems which support the IPV6_V6ONLY socket option, the forwarded socket is created for IPV6 only and then the DONT_TRY_OTHER_AF prevents an IPV4 listen socket from also being created. Thus, only forwarding X11...

...error in socket IO (code 10) at socket.c(466) strace shows that there is problem with listen() I've found patch on this lists: --- rsync-2.6.2/socket.c.orig 2004-05-08 23:25:11.979473336 +0200 +++ rsync-2.6.2/socket.c 2004-05-08 23:27:13.255036648 +0200 @@ -379,8 +379,8 @@ #ifdef IPV6_V6ONLY if (resp->ai_family == AF_INET6) { - setsockopt(s, IPPROTO_IPV6, IPV6_V6ONLY, - (char *)&one, sizeof one); + if(setsockopt(s, IPPROTO_IPV6, IPV6_V6ONLY, (char *)&one, sizeof one) < 0) +...

I see in the release notes for 7.0; and seperately CURRENT on alpha; that IPV6_V6ONLY is now fully supported for UDP. Can someone point me to code/text that explains what exactly was broken about it? In what case(s) udp sockets set with IPV6_V6ONLY accepted V4 packets? Thanks in advance.. -- Jason Fesler, email/jabber <jfesler@gigo.com> resume: http://jfesler.com &...

Is there a particular reason that sshd sets IPV6_V6ONLY on listen sockets? ---- Scott Neugroschl XYPRO Technology Corporation scott_n at xypro.com 805-583-2874

When I run gluster v heal datastore full errror into log is gfapi: Error disabling sockopt IPV6_V6ONLY The brick are up. Version is 3.13.2 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20180223/44c58392/attachment.html>

https://bugzilla.mindrot.org/show_bug.cgi?id=1648 Summary: Fix IPV6_V6ONLY for -L with -g Product: Portable OpenSSH Version: -current Platform: All OS/Version: Linux Status: NEW Severity: minor Priority: P2 Component: ssh AssignedTo: unassigned-bugs at mindrot.org ReportedBy...

http://bugzilla.mindrot.org/show_bug.cgi?id=164 ------- Additional Comments From yoshfuji at linux-ipv6.org 2002-05-18 09:44 ------- Created an attachment (id=97) Try to set IPV6_V6ONLY if available. Open ::1 and 127.0.0.1 if x11_use_localhost is set. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

...pt) else raise ArgumentError, "Don''t know how to bind: #{address}" end @@ -152,13 +161,18 @@ module Unicorn sock end - def new_ipv6_server(addr, port, opt) - opt.key?(:ipv6only) or return Kgio::TCPServer.new(addr, port) - defined?(IPV6_V6ONLY) or - abort "Socket::IPV6_V6ONLY not defined, upgrade Ruby and/or your OS" - sock = Socket.new(AF_INET6, SOCK_STREAM, 0) - sock.setsockopt(IPPROTO_IPV6, IPV6_V6ONLY, opt[:ipv6only] ? 1 : 0) + def new_tcp_server(addr, port, opt) + # n.b. we set FD_CLOEXEC in the...

...13.711255] W [MSGID: 101002] [options.c:995:xl_opt_validate] 0-glusterfs: option 'address-family' is deprecated, preferred is 'transport.address-family', continuing with correction [2018-04-09 05:08:13.728297] W [socket.c:3216:socket_connect] 0-glusterfs: Error disabling sockopt IPV6_V6ONLY: "Protocol not available" [2018-04-09 05:08:13.729025] I [MSGID: 101190] [event-epoll.c:613:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1 [2018-04-09 05:08:13.737757] I [MSGID: 101190] [event-epoll.c:613:event_dispatch_epoll_worker] 0-epoll: Started thread with i...

...101002] > [options.c:995:xl_opt_validate] 0-glusterfs: option 'address-family' is > deprecated, preferred is 'transport.address-family', continuing with > correction > [2018-04-09 05:08:13.728297] W [socket.c:3216:socket_connect] > 0-glusterfs: Error disabling sockopt IPV6_V6ONLY: "Protocol not available" > [2018-04-09 05:08:13.729025] I [MSGID: 101190] > [event-epoll.c:613:event_dispatch_epoll_worker] 0-epoll: Started thread > with index 1 > [2018-04-09 05:08:13.737757] I [MSGID: 101190] > [event-epoll.c:613:event_dispatch_epoll_worker] 0-epoll:...

Hi, I think we should try other AF for "x11_use_localhost" case. --- openssh-3.1p1/channels.c Tue Mar 5 10:57:45 2002 +++ openssh-3.1p1-fix/channels.c Thu May 2 21:26:28 2002 @@ -2356,6 +2356,13 @@ continue; } } +#ifdef IPV6_V6ONLY + if (ai->ai_family == AF_INET6) { + int on = 1; + if (setsockopt(sock, IPPROTO_IPV6, IPV6_V6ONLY, &on, sizeof(on)) < 0) + debug("x11_create_display_inet: setsockopt(IPV6_V6ONLY) failed."); + } +#endif if (bind(sock, ai->ai_addr, ai->ai_addrlen) < 0)...

Wayne, I have been using the rsync snapshot from 1/25 for the last few days and everything seems quite solid so far. I include below a few nit-picks in case you're looking for thing to tidy up. I'm also looking forward to hearing news about the --filter option. I'm thinking it is going to be very useful for backup purposes. What I would want to be able to do is, on a

...r-IPv6). That is not intrinsic to a system that does v4 and v6. It is about a misfeature which if turned on, when one binds to v6 also sets up a listener on v4 which connects as a mapped address. These days, I view it as a bug for a system to be configuret hat way. On NetBSD, from ip6(4): IPV6_V6ONLY int * Get or set whether only IPv6 connections can be made to this socket. For wildcard sockets, this can restrict connections to IPv6 only. which is 1 on my system. > Given that `LISTEN *` support is in fact not documented explicitly (I > think),...

...r-IPv6). That is not intrinsic to a system that does v4 and v6. It is about a misfeature which if turned on, when one binds to v6 also sets up a listener on v4 which connects as a mapped address. These days, I view it as a bug for a system to be configuret hat way. On NetBSD, from ip6(4): IPV6_V6ONLY int * Get or set whether only IPv6 connections can be made to this socket. For wildcard sockets, this can restrict connections to IPv6 only. which is 1 on my system. > Given that `LISTEN *` support is in fact not documented explicitly (I > think),...

...in the end neither socket works, declare a fatal error (could not fulfill the config requirement). If we could get IPv4 initially, and could not after getting IPv6, do not bother - assume a dual-stack system (and log it so). Also as part of this change, NUT would ask (although not insist) for the IPV6_V6ONLY socket option when preparing IPv6 connections, except when handling `LISTEN *`. Finally, I noticed that if some configuration hostname resolves to more than one address, the first one bound wins and others are ignored. This behavior was here before, the PR change just logs that this happens. Jim...

...in the end neither socket works, declare a fatal error (could not fulfill the config requirement). If we could get IPv4 initially, and could not after getting IPv6, do not bother - assume a dual-stack system (and log it so). Also as part of this change, NUT would ask (although not insist) for the IPV6_V6ONLY socket option when preparing IPv6 connections, except when handling `LISTEN *`. Finally, I noticed that if some configuration hostname resolves to more than one address, the first one bound wins and others are ignored. This behavior was here before, the PR change just logs that this happens. Jim...

Cheers all, TL;DR version: I've recently found that at least on my test box the `LISTEN *` line had only set up an IPv4 `0.0.0.0` listener but not an IPv6 `::0` listener for `upsd`. In fact, at least on a "dual-stack" system, it seems impossible to bind to both - so depending on binding order I either lose IPv6 or lose IPv4 directly (but have it practically as IPv4-over-IPv6).

Cheers all, TL;DR version: I've recently found that at least on my test box the `LISTEN *` line had only set up an IPv4 `0.0.0.0` listener but not an IPv6 `::0` listener for `upsd`. In fact, at least on a "dual-stack" system, it seems impossible to bind to both - so depending on binding order I either lose IPv6 or lose IPv4 directly (but have it practically as IPv4-over-IPv6).

...tions.c:995:xl_opt_validate] 0-glusterfs: option 'address-family' is > deprecated, preferred is 'transport.address-family', continuing with > correction > [2018-04-09 05:08:13.728297] W [socket.c:3216:socket_connect] > 0-glusterfs: Error disabling sockopt IPV6_V6ONLY: "Protocol not > available" > [2018-04-09 05:08:13.729025] I [MSGID: 101190] > [event-epoll.c:613:event_dispatch_epoll_worker] 0-epoll: Started thread > with index 1 > [2018-04-09 05:08:13.737757] I [MSGID: 101190] > [event-epoll.c:613:event_dis...