SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #1142781
Ticket Status: Resolved

PoP: (not applicable)

im.sixxs.net: BitlBee not working via ipv6
[pt] Shadow Hawkins on Friday, 17 July 2009 04:47:20
i tried to reopen the ticket #515400, but a week went by with activity in other bugs and this didnt reopen... i assume the new post wasnt noted. the problem is simple, bitlbee isnt working via ipv6 IP, but works via the ipv4 IP. please check the other but for the log thanks and sorry the duplicate higuita
im.sixxs.net: BitlBee not working via ipv6
[pt] Shadow Hawkins on Monday, 20 July 2009 03:58:24
adding the logs to this bug, to keep all info in one place: $ host im.sixxs.net im.sixxs.net is an alias for nlams01.sixxs.net. nlams01.sixxs.net has address 213.197.27.252 nlams01.sixxs.net has IPv6 address 2001:838:2:1:2a0:24ff:feab:3b53 tracepath6 im.sixxs.net 1?: [LOCALHOST] pmtu 1500 1: submarino.motaleite.net 1.039ms 2: submarino.motaleite.net asymm 1 2.719ms pmtu 1280 2: gw-35.lis-01.pt.sixxs.net 145.407ms 3: 2001:b18:0:1000::1 293.827ms 4: 2001:b18:0:1::11 126.421ms 5: he.ipv6.panap.fr 158.096ms 6: 10gigabitethernet1-3.core1.lon1.he.net 83.859ms 7: 10gigabitethernet1-1.core1.ams1.he.net 90.658ms 8: ams-ix.ipv6.concepts.nl 113.035ms 9: 2001:838:5:a::2 asymm 10 107.295ms 10: 2001:838:2:1:2a0:24ff:feab:3b53 138.474ms reached Resume: pmtu 1280 hops 10 back 10 $ telnet 213.197.27.252 6667 Trying 213.197.27.252... Connected to 213.197.27.252. Escape character is '^]'. :im.sixxs.net NOTICE AUTH :BitlBee-IRCd initialized, please go on quit ERROR :Closing link: Leaving... Connection closed by foreign host. $ telnet 2001:838:2:1:2a0:24ff:feab:3b53 6667 Trying 2001:838:2:1:2a0:24ff:feab:3b53... telnet: connect to address 2001:838:2:1:2a0:24ff:feab:3b53: Connection refused so the bitlbee on IPV6 is running on another machine (and not working), or not bind to the ipv6 port
im.sixxs.net: BitlBee not working via ipv6
[de] Shadow Hawkins on Monday, 27 July 2009 12:07:37
Hello Daniel,
telnet: connect to address 2001:838:2:1:2a0:24ff:feab:3b53: Connection refused
from this line you can tell, that bitibee does not listen on an IPv6 socket. That is why it is not working over IPv6. However this has nothing todo with sixxs, so please close the ticket and don't reopen it. In order so solve your problem you first have to check if bitibee does support IPv6, if it does, if you have configured it todo so and double check using lsof. Otherwise you have to contact the development team. The following output shows you to list all applications that listen for IPv6: (thinkpad) [~] lsof -P -i -n | grep LISTEN | grep IPv6 cupsd 2615 root 3u IPv6 6371 TCP [::1]:631 (LISTEN) sshd 3232 root 3u IPv6 7662 TCP *:22 (LISTEN) ssh 3498 sithglan 6u IPv6 8208 TCP [::1]:8080 (LISTEN) on my thinkpad that is currently cupsd, sshd and a ssh client. Good luck to get bitlbee, whatever that is, IPv6 enabled, Thomas
im.sixxs.net: BitlBee not working via ipv6
[ch] Jeroen Massar SixXS Staff on Monday, 27 July 2009 12:41:46
However this has nothing todo with sixxs, so please close the ticket and don't reopen it.
Thank you for commenting to a ticket you have no idea about. SixXS actually *OPERATES* im.sixxs.net, as such it has everything to do with SixXS.
The following output shows you to list all applications that listen for IPv6:
Bit difficult if the users don't have access to im.sixxs.net, don't you think?
Good luck to get bitlbee, whatever that is, IPv6 enabled,
If you have no idea what it is, then why are you commenting? Please refrain from making stupid remarks. Thank you.
State change: confirmed Locked
[ch] Jeroen Massar SixXS Staff on Monday, 27 July 2009 12:41:54
Message is Locked
The state of this ticket has been changed to confirmed
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Wednesday, 29 July 2009 13:41:05
Message is Locked
The state of this ticket has been changed to resolved

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker