gogo6 now filters port 119 (was: 10060, 'Operation timed out' for 2 days)

[TheGlow]

Hey everyone, a little bit stumped here.
For 2 days Ive been getting the 10060, 'Operation timed out' error a lot.
Namely the servers I use are
news.optonline.net:119
news.just4today.net:119
reader.ipv6.xsnews.nl:119
newszilla6.xs4all.nl:119

So far only the optonline one which is my isp works. And even that it dodgy where itll just say no connection or slow to 0kbps and just sit there.
My ipv6 is fine as I can ping all of these and get responses. If I try to telnet to them, it times out.
I restarted my pc and router and now wondering if resetting my cable modem would be worth a look.

And just4today gives me 10061, 'Connection refused'. And I made sure the user pass is good.

But why would this be? It started with 1 or 2 servers saying they didnt have the file and they would just idle.
Now I couldnt get anything to work except just now the optonline is going. Im a bit puzzled.
Side question, is news.readfreenews.net any good? The few times I used them it seemed like the chunks were finishing too fast and every piece would fail the par check.

[bloasfist]

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 this be related??

[shypike]

In such case, check with ping6 or a ipv6-compatible telnet whether
the problem isn't in the servers.
Remember that these are experimental free servers.

[bloasfist]

Both sites ping6 just fine... (the 25% loss on xs4all is only occasional)

Code: Select all

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=32 time=72ms 
Reply from 2001:67c:174:101::2: bytes=32 time=63ms 
Ping statistics for 2001:67c:174:101::2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 63ms, Maximum = 105ms, Average = 79ms

Pinging newszilla.ipv6.xs4all.nl [2001:888:0:18::119]
from [..] with 32 bytes of data:
Reply from 2001:888:0:18::119: bytes=32 time=83ms 
Request timed out. 
Reply from 2001:888:0:18::119: bytes=32 time=52ms 
Reply from 2001:888:0:18::119: bytes=32 time=49ms 
Ping statistics for 2001:888:0:18::119:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 49ms, Maximum = 83ms, Average = 61ms

Any other ideas?

[shypike]

ping is the bare minimum. Try telnet and see if you see a sign-on message.

[bloasfist]

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?

[shypike]

Telnet is only useful to check whether the server is active, actually whether the NNTP service runs.
From what you describe it looks  that the IPV6 DNS resolving on your system is excessively slow or just buggy.
SABnzbd asks the OS to resolve the DNS name of the server.
If it gets "no route" as an answer, then what is it supposed to do?

[inpheaux]

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 up on other ports, those would get shut down too.

Sorry guys, your free ride is over. Suck it up and get a real provider.

Edit: Some reports are saying their Taipei server might still work. But based on that link from their forums I wouldn't expect it to continue working for very long.

[bloasfist]

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 up on other ports, those would get shut down too.

Sorry guys, your free ride is over. Suck it up and get a real provider.

Edit: Some reports are saying their Taipei server might still work. But based on that link from their forums I wouldn't expect it to continue working for very long.

Thanks for the info! I use indeed the gogo6 tunnel. I'm gonna try it with http://tunnelbroker.net/, i used that before i went to gogo6. Otherwise i'll get a 'real' provider

[ShadoWWarrioR]

I'm gonna try it with http://tunnelbroker.net/, i used that before i went to gogo6. Otherwise i'll get a 'real' provider

Any success? Someone manage to do it?