taskWeeChat - Tasks: task #11205, IPv6 should be prefered, IPv4...

 
 

task #11205: IPv6 should be prefered, IPv4 fallback

Submitted by:  None
Submitted on:  Mon 20 Jun 2011 09:48:57 AM UTC  
 
Category:  irc plugin Should Start On:  Mon 20 Jun 2011 12:00:00 AM UTC
Should be Finished on:  Mon 20 Jun 2011 12:00:00 AM UTC Priority:  5 - Normal
Status:  Done Privacy:  Public
Percent Complete:  100% Assigned to:  Sebastien Helleu <flashcode>
Originator Name:  Hendrik Jaeger Originator Email:  -email is unavailable-
Open/Closed:  Closed Planned Release:  0.4.0
IRC nick:  henk

Add a New Comment (Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Sun 14 Oct 2012 08:59:16 AM UTC, comment #3: 

Thanks Simon for the patch.

Sebastien Helleu <flashcode>
Project AdministratorIn charge of this item.
Tue 27 Mar 2012 05:31:14 PM UTC, comment #2: 

Hi,

> I don't think that programs should use IPv6 always when it's available.


IPv6 is supposed to replace IPv4, so using it when it is available is the way things are supposed to work.

> What if the IPv6 connection is tunneled with for example, Miredo? Then the connection might be slower and more unstable than usually.


The user will know that, as he set it up that way. If he notices any problems with it, he is free to set weechat to use IPv4 only.
IMHO that is not a very good point as the same might happen when connecting via a VPN or a proxy or whatever. It’s not IPv6 that is the problem in that case, but the general network setup. Disabling IPv6 generally because it might not work in some scenarios the user might have set up seems rather counterproductive to me…

> If people want to use IPv6 they should modify their system wide settings


People will have to do that sooner or later anyway, as IPv4 will be gone some day. IMHO it works the other way round: if people with an IPv6-enabled but broken setup do not want to do The Right Thing[TM] and fix their setup, they can modify their system to ignore IPv6.

IMHO disabling IPv6 by default will just have the effect of most connections to whatever service it may be being done via IPv4. The result will be that most service administrators think their users/clients do not have a working IPv6-setup and thus feel the need to keep the service on IPv4 alive as well. I don’t think that helps the migration to IPv6 at all, but rather puts stones in its way.

Thanks for reading and commenting!

Best regards

henk

Anonymous
Tue 27 Mar 2012 05:07:22 PM UTC, comment #1: 

Hi,

I don't think that programs should use IPv6 always when it's available. What if the IPv6 connection is tunneled with for example, Miredo? Then the connection might be slower and more unstable than usually.

I think that it's better for WeeChat to do what it's already doing. If people want to use IPv6, they should modify their system wide settings (/etc/gai.conf) for automatic IPv6 usage in all programs.

(I am not fully sure does gai.conf affect other than tunneled connections with IPv6 priorizing.)

Mika Suomalainen <mkaysi>
Mon 20 Jun 2011 09:48:57 AM UTC, original submission:  

Hi,

Most programs capable of using IPv6 prefer IPv6 where possible and fall back to IPv4 where IPv6 is not possible, i.e. no AAAA record exists but A record does e.g.
AFAICT weechat does not work that way but expects the user to tell whether IPv6 can be used. IMHO this is counterproductive as IPv6 won't automatically be used once it becomes available on a network, but only after the user changed the option again.
I don't see any advantage in this behaviour over falling back to IPv4, so I'd suggest renaming the setting to something like 'force_ipv4' so broken IPv6 setups can still be connected to. But as long as this option is unset, I'd expect weechat to behave as most other IPv6-capable applications and try IPv6 and fall back to IPv4 if IPv6 is unsuccessful.

Thank you for reading and considering!
Keep up the great work please, I really appreciate it!

henk

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #26440:  0002-automatically-connect-using-IPv6-or-IPv4.patch added by None (111KiB - text/x-patch - This patch makes it practical to have IPv6 "on" by default by falling back to IPv4 properly)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by flashcode (Posted a comment)
  • -email is unavailable- added by mkaysi (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

     

     

    Follow 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2013-01-20 flashcode Open/ClosedOpen => Closed
    2012-10-14 flashcode StatusNone => Done
        Percent Complete0% => 100%
        Assigned toNone => flashcode
        Planned ReleaseNone => 0.4.0
    2012-08-28 None Attached File- => Added 0002-automatically-connect-using-IPv6-or-IPv4.patch, #26440

    Back to the top


    Powered by Savane 3.5