If there are missing packets, it could be a routing or firewall issue. If the packets have been altered during transit, it could be due to misconfiguration in Telstra Clear's infamous 'transparent' proxy.
Rubicon: If there are missing packets, it could be a routing or firewall issue. If the packets have been altered during transit, it could be due to misconfiguration in Telstra Clear's infamous 'transparent' proxy.
TCL's proxy should only affect port 80 (not SSTP on 443) and only international traffic.
Is the SSTP server on an unmanaged dedicated server, or something Datacom is resposible? If the latter, get them to look at it.
It is one of my own servers. I am not too sure we should get Datacom involved at the moment as everything points out to something on TelstraClear perimeter causing this. As I said it works just fine when I connect from other networks.
freitasm: It is one of my own servers. I am not too sure we should get Datacom involved at the moment as everything points out to something on TelstraClear perimeter causing this. As I said it works just fine when I connect from other networks.
You'll have more luck with Datacom talking to their upstream talking to TCL, then you talking to TCL customer care. You're paying for a business-grade service at the Datacom end; use it.
freitasm: Sure, but how come this only happens on a TelstraClear connection?
Don't forget that the other end (your hosted server at datacom) might have a very different path travelling over different links on the return to your TCL connection. There might be a box along the way with a misconfigured MTU, or something that's trying to be "clever" and have some sort of SSL manipulation going on.
Certainly think this is worthy of logging a fault with TCL at first, then also getting Datacom involved to check the return path towards you.
All those TCP re-transmits - make sure there's not an MTU issue somewhere.
freitasm: Sure, but how come this only happens on a TelstraClear connection?
Don't forget that the other end (your hosted server at datacom) might have a very different path travelling over different links on the return to your TCL connection. There might be a box along the way with a misconfigured MTU, or something that's trying to be "clever" and have some sort of SSL manipulation going on.
Certainly think this is worthy of logging a fault with TCL at first, then also getting Datacom involved to check the return path towards you.
All those TCP re-transmits - make sure there's not an MTU issue somewhere.
The "pings work, bring up something big and it fails" sounds like an MTU issue, but it'd be wierd if the packets from your hosted box to your home TCL cable connection went through any MTU<1500 links.
I think this is now solved. Two firewalls blocking stuff they shouldn't, on my side. Disabled one of them and things seem to work fine now.
Obviously shouldn't have both firewalls active, and I have no idea why it was configured like that but it seems all is working fine (at least for the last couple of days).
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.
... 18 19 20
Administrator
Trusted
Geekzone
