SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #515400
Ticket Status: Resolved

PoP: (not applicable)

im.sixxs.net: BitlBee not working remotly
[pt] Shadow Hawkins on Friday, 04 May 2007 02:51:46
i was using BitlBee in the im.sixxs.net, in a irc client, but it stop working... as the tests show, the server/service is having some problem... 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 via ipv6: 01:14:32 ~/$ telnet im.sixxs.net 6667 Trying 2001:838:2:1:2a0:24ff:feab:3b53... Connected to im.sixxs.net. Escape character is '^]'. Connection closed by foreign host. 01:14:33 ~/$ the connection is closed right way via ipv4: 00:57:52 ~/$ telnet 213.197.27.252 6667 Trying 213.197.27.252... Connected to 213.197.27.252. Escape character is '^]'. Connection closed by foreign host. same problem... but on the site the bitlbee works... maybe a different server? *** Connecting to cgi [172.16.213.54] port 6667 -im.sixxs.net- BitlBee-IRCd initialized, please go on *** Welcome to the BitlBee gateway, higuita $ ping6 im.sixxs.net PING im.sixxs.net(2001:838:2:1:2a0:24ff:feab:3b53) 56 data bytes 64 bytes from 2001:838:2:1:2a0:24ff:feab:3b53: icmp_seq=1 ttl=52 time=58.2 ms 64 bytes from 2001:838:2:1:2a0:24ff:feab:3b53: icmp_seq=2 ttl=52 time=58.1 ms 64 bytes from 2001:838:2:1:2a0:24ff:feab:3b53: icmp_seq=3 ttl=52 time=60.2 ms 64 bytes from 2001:838:2:1:2a0:24ff:feab:3b53: icmp_seq=4 ttl=52 time=58.2 ms --- im.sixxs.net ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3001ms rtt min/avg/max/mdev = 58.134/58.701/60.209/0.904 ms $ traceroute6 im.sixxs.net traceroute to nlams01.sixxs.net (2001:838:2:1:2a0:24ff:feab:3b53) from 2001:b18:400f:0:211:d8ff:fe82:b10e, 30 hops max, 24 byte packets 1 submarino.motaleite.net (2001:b18:400f::1) 0.474 ms 0.388 ms 0.496 ms 2 gw-35.lis-01.pt.sixxs.net (2001:b18:2000:22::1) 20.252 ms 14.396 ms 13.763 ms 3 2001:b18:0:1000::1 (2001:b18:0:1000::1) 20.709 ms 14.321 ms 13.838 ms 4 ge-0.Edge3.ip6.Lisbon.NFSi.pt (2001:b18:0:1::2) 13.951 ms 14.243 ms 13.729 ms 5 2001:5a0:1500::1 (2001:5a0:1500::1) 146.276 ms 209.855 ms 200.831 ms 6 if-0-0.mcore3.lhx-london.ipv6.teleglobe.net (2001:5a0:1300::9) 48.604 ms 41.975 ms 42.725 ms 7 if-6-0.core1.ad1-amsterdam.ipv6.teleglobe.net (2001:5a0:1300::2) 55.62 ms 56.686 ms 55.303 ms 8 2001:5a0:200::5 (2001:5a0:200::5) 55.759 ms 56.292 ms 55.701 ms 9 ams-ix.ip6.tiscali.net (2001:7f8:1::a500:3257:1) 52.962 ms 53.78 ms 53.907 ms 10 ge6-2-0.br0.ams3.nl.gbxs.net (2001:7f8:1::a500:9009:1) 55.231 ms 53.419 ms 54.367 ms 11 ams-ix.ipv6.concepts.nl (2001:7f8:1::a501:2871:1) 71.374 ms 66.015 ms 87.036 ms 12 2001:838:0:10::2 (2001:838:0:10::2) 58.152 ms 63.557 ms 57.913 ms 13 2001:838:2:1:2a0:24ff:feab:3b53 (2001:838:2:1:2a0:24ff:feab:3b53) 58.069 ms 199.482 ms 139.493 ms $ traceroute im.sixxs.net traceroute to nlams01.sixxs.net (213.197.27.252), 30 hops max, 46 byte packets 1 submarino (10.42.42.254) 0.699 ms 0.619 ms 3.737 ms 2 * * * 3 * * * 4 194-79-70-69.net.novis.pt (194.79.70.69) 6.449 ms 9.774 ms 7.940 ms 5 194-79-92-69.nr.ip.pt (194.79.92.69) 12.661 ms 13.217 ms 11.942 ms 6 g1-0-245-core01.mad05.atlas.cogentco.com (130.117.22.177) 26.369 ms 26.382 ms 26.618 ms 7 g9-0-0-101.core01.mad05.atlas.cogentco.com (130.117.1.41) 26.516 ms 25.952 ms 25.201 ms 8 p12-0.core01.bcn01.atlas.cogentco.com (130.117.2.230) 37.174 ms 35.632 ms 56.701 ms 9 p2-0.core01.par01.atlas.cogentco.com (130.117.2.225) 155.449 ms 153.701 ms 153.652 ms 10 p11-0.core01.lon01.atlas.cogentco.com (130.117.2.253) 259.506 ms 260.315 ms 259.518 ms 11 t1-4.mpd02.lon01.atlas.cogentco.com (130.117.1.74) 261.722 ms 262.524 ms 260.878 ms 12 p3-2.mpd01.ams03.atlas.cogentco.com (130.117.1.169) 268.833 ms 270.563 ms 270.316 ms 13 ams-ix.concepts.nl (195.69.144.64) 277.034 ms * 270.439 ms 14 at-0-0-1.breda.concepts-ict.net (213.197.27.125) 271.763 ms 276.004 ms 273.422 ms 15 tunnelserver.concepts-ict.net (213.197.27.252) 172.560 ms 181.684 ms 173.390 ms
im.sixxs.net: BitlBee not working remotly
[pt] Shadow Hawkins on Friday, 10 July 2009 02:27:02
this problem seems to show up again, but this time, not only the website works, ipv4 also works. Ipv6 is refusing the connection. $ 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 higuita@Couracado:0 01:21:37 ~/$ 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 $ ping6 2001:838:2:1:2a0:24ff:feab:3b53 PING 2001:838:2:1:2a0:24ff:feab:3b53(2001:838:2:1:2a0:24ff:feab:3b53) 56 data bytes 64 bytes from 2001:838:2:1:2a0:24ff:feab:3b53: icmp_seq=1 ttl=55 time=77.8 ms 64 bytes from 2001:838:2:1:2a0:24ff:feab:3b53: icmp_seq=2 ttl=55 time=76.9 ms ^C --- 2001:838:2:1:2a0:24ff:feab:3b53 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 76.978/77.389/77.800/0.411 ms Thanks
im.sixxs.net: BitlBee not working remotly
[pt] Shadow Hawkins on Monday, 08 March 2010 10:26:25
Hi again After resolving ticket 1368274 (im.sixxs.net down), i just found out that IRC is still down, so i'm reopening this one (or should i reopen the 1368274?) im.sixxs.net irc is closed via ipv4 and ipv6, but the website is working thanks higuita
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Friday, 04 May 2007 11:34:13
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