Add a New Comment (Rich Markup)
After this change: http://git.savannah.gnu.org/gitweb/?p=weechat.git;a=commitdiff;h=248aa8d73a60060ee0e625942c31748e8262b593;hp=70ce7fe3b6caa6128cb6e8bfb0eaaf39f1ebe4ce current connection retry count influences which IP address will be picked by weechat for server. That has negative consequences for me - I have IPv6 tunnel and want to connect to IRC networks through it. The problem is that sometimes it fails and weechat reconnects to IPv4 address. After that /reconnect and /disconnect + /connect commands will only use IPv4 addresses, totally ignoring IPv6 connection (well, maybe until connecting to IPv4 address fails). I found only 2 ways to reenable IPv6 - restarting weechat and changing/adding addresses to server configuration (smth like /set irc.server.freenode.addresses chat.freenode.net,ipv6.chat.freenode.net) + using /reconnect -switch. Both of them aren't convenient workarounds. I think /disconnect command should reset retry counts.
(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)
Attach Files: Comment:
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Only logged-in users can vote.
Please enter the title of George Orwell's famous dystopian book (it's a date):
Follow 4 latest changes.
Copyright © 2023 Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team. Source Code
Powered by Savane 3.11