SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #1134898
Ticket Status: User

PoP: usqas01 - OCCAID Inc. (Ashburn, Virginia)

usqas01 is giving 'connection refused'
[us] Shadow Hawkins on Thursday, 09 July 2009 00:31:00
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there: I'm unable to connect to usqas01 (66.117.47.228:3874) -- tcpdump shows a TCP RST packet when I fire up aiccu: # tcpdump -p -l -n -i wm0 -s 1500 -v -v -v host 66.117.47.228 tcpdump: listening on wm0, link-type EN10MB (Ethernet), capture size 1500 bytes 17:52:00.439324 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 64) 131.171.30.75.65462 > 66.117.47.228.3874: S, cksum 0x4fd0 (correct), 576594086:576594086(0) win 32768 <mss 1460,nop,wscale 3,sackOK,nop,nop,nop,nop,t imestamp 1 0> 17:52:00.445465 IP (tos 0x0, ttl 51, id 40175, offset 0, flags [DF], proto TCP ( 6), length 40) 66.117.47.228.3874 > 131.171.30.75.65462: R, cksum 0x49a3 (correc t), 0:0(0) ack 576594087 win 0 I've verified the response via telnet to that port from elsewhere, so I know there isn't a firewall issue. I'm running NetBSD-current (5.99.14 as of June 25), aiccu-20070115, built via pkgsrc: # aiccu test Couldn't connect to the TIC server 66.117.47.228 Couldn't retrieve first tunnel for the above reason, abortin
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Thursday, 09 July 2009 00:39:33
Message is Locked
The state of this ticket has been changed to user
usqas01 is giving 'connection refused'
[ch] Jeroen Massar SixXS Staff on Thursday, 09 July 2009 00:40:53
66.117.47.228 is not a TIC server, it just a PoP. See FAQ : AICCU (TIC, Heartbeat & AYIYA) : What about TIC? Which TIC server should I use? aka just use tic.sixxs.net.

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

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