Search found 4 matches
- November 7th, 2010, 6:57 am
- Forum: General Help
- Topic: gogo6 now filters port 119 (was: 10060, 'Operation timed out' for 2 days)
- Replies: 9
- Views: 13571
Re: 10060, 'Operation timed out' for 2 days
It's your ipv6 tunnel. A mibbit user provided us with this link a few moments ago. gogo6, an ipv6 tunnel most of you are likely using, has started filtering port 119, and the free ipv6 servers exclusively listen on 119. And even if they didn't, you can expect that if high traffic started cropping u...
- November 5th, 2010, 11:21 am
- Forum: General Help
- Topic: gogo6 now filters port 119 (was: 10060, 'Operation timed out' for 2 days)
- Replies: 9
- Views: 13571
Re: 10060, 'Operation timed out' for 2 days
I now notice that after pinging, the connection is somehow opened! Every time i boot my machine the no route to host message appears; seconds after pinging connections to all servers are created! Would telnetting give more insight into the cause of this?
- November 4th, 2010, 12:17 pm
- Forum: General Help
- Topic: gogo6 now filters port 119 (was: 10060, 'Operation timed out' for 2 days)
- Replies: 9
- Views: 13571
Re: 10060, 'Operation timed out' for 2 days
Both sites ping6 just fine... (the 25% loss on xs4all is only occasional) Pinging reader.ipv6.xsnews.nl [2001:67c:174:101::2] from [..] with 32 bytes of data: Reply from 2001:67c:174:101::2: bytes=32 time=105ms Reply from 2001:67c:174:101::2: bytes=32 time=79ms Reply from 2001:67c:174:101::2: bytes=...
- November 3rd, 2010, 2:10 pm
- Forum: General Help
- Topic: gogo6 now filters port 119 (was: 10060, 'Operation timed out' for 2 days)
- Replies: 9
- Views: 13571
Re: 10060, 'Operation timed out' for 2 days
Got the same sort of thing, also since 2 days! reader.ipv6.xsnews.nl:119: Failed to connect: (10060, "(10065, 'No route to host')") 6@reader.ipv6.xsnews.nl:119 newszilla6.xs4all.nl:119: Failed to connect: (10060, "(10065, 'No route to host')") 1@newszilla6.xs4all.nl:119 Could thi...