Bug#445047: Irssi handling of IPv6 servers idiosyncratic
Package: irssi Version: 1.2.2-2+b1 Followup-For: Bug #445047 X-Debbugs-Cc: witold.bary...@gmail.com Hi. This still appears to be broken: [(status)] /connect localhost 6697 06:40 -!- Irssi: Connection lost to localhost 06:40 -!- Irssi: Looking up localhost 06:40 -!- Irssi: Connecting to localhost [127.0.0.1] port 6697 06:40 -!- Irssi: Connection to localhost established This is wrong, it should connect to ::1 Same with external servers, irssi still preferse IPv4 for some reasons. Regards, Witold -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-2-amd64 (SMP w/32 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_DIE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages irssi depends on: ii libc6 2.31-9 ii libglib2.0-02.66.4-1 ii libperl5.32 5.32.0-6 ii libssl1.1 1.1.1i-3 ii libtinfo6 6.2+20201114-2 ii perl5.32.0-6 ii perl-base [perlapi-5.32.0] 5.32.0-6 irssi recommends no packages. Versions of packages irssi suggests: pn irssi-scripts -- no debconf information
Bug#445047: Irssi handling of IPv6 servers idiosyncratic
Upstream is currently trying to improve the situation, if you are interested in helping out we welcome you to test the current git version from https://github.com/irssi/irssi.git and remark your findings on the discussion at https://github.com/irssi/irssi/pull/410 Thanks, Nei
Bug#445047: Irssi handling of IPv6 servers idiosyncratic
On Tue, Oct 02, 2007 at 10:28:38PM +0200, Juliusz Chroboczek wrote: When specifying a server that has both A and DNS entries, irssi will only connect to the IPv4 address; the IPv6 address will only be used if the ``-6'' flag is specified on the /server command. This is annoying when connecting from an IPv6-only network. I suggest that irssi should treat all the addresses of a server as a group, and connect to whichever is reachable at a given time. The same should be true when a connection dies and the server is recontacted to allow for mobility between the IPv4 and IPv6 internets. You can test with irc.geeknode.org which is reachable using both IPv4 and IPv6. It also does not prefer IPv6 over IPv4 by default. Instead you need to set resolve_prefer_ipv6 to on. That seems like a bug to me, too. Kind regards Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#445047: Irssi handling of IPv6 servers idiosyncratic
Package: irssi Version: 0.8.10-2 Severity: wishlist Tags: upstream Hi, When specifying a server that has both A and DNS entries, irssi will only connect to the IPv4 address; the IPv6 address will only be used if the ``-6'' flag is specified on the /server command. This is annoying when connecting from an IPv6-only network. I suggest that irssi should treat all the addresses of a server as a group, and connect to whichever is reachable at a given time. The same should be true when a connection dies and the server is recontacted to allow for mobility between the IPv4 and IPv6 internets. You can test with irc.geeknode.org which is reachable using both IPv4 and IPv6. Thanks for your help, Juliusz pgp3D27lWb2Qh.pgp Description: PGP signature
