Over the last 24-48 hours I have noticed that I am seeing my IP being mis-represented quite often as 203.98.50.27 which appears to be a new upstream proxy hop I have not seen before: traceroute to 203.98.50.27 (203.98.50.27), 30 hops max, 40 byte packets 1 121-73-24-1.cable.telstraclear.net (121.73.24.1) 18.037 ms 17.681 ms 17.413 ms 2 ae0-840.ie4.telstraclear.net (203.167.223.114) 12.952 ms 12.781 ms 12.475 ms 3 ge-1-2-0-843.ie1.telstraclear.net (218.101.61.105) 21.357 ms 20.910 ms 20.661 ms 4 203.98.50.27 (203.98.50.27) 24.332 ms 24.066 ms 23.950 ms I have noticed it preventing non http traffic flowing across port 80 (netcat to amazon cloud), as well as interfering with stun and various other bits and pieces, (incoming and outgoing connections to/from local webserver take longer than usual) Can anyone confirm similar behaviour who is on Telstra cable network, or have further details. Appears to be a netcache proxy. Proxy Server Details: 1.1 nc2 (NetCache NetApp/6.0.5P1) Kind regards -JoelW
This is pretty common practice when purchasing bandwidth from retail providers.. Cheers From: Joel Wiramu Pauling [mailto:aenertia(a)aenertia.net] Sent: Friday, 20 February 2009 2:43 a.m. To: nznog Subject: [nznog] New Telstra transparent proxy/config? Over the last 24-48 hours I have noticed that I am seeing my IP being mis-represented quite often as 203.98.50.27 which appears to be a new upstream proxy hop I have not seen before: traceroute to 203.98.50.27 (203.98.50.27), 30 hops max, 40 byte packets 1 121-73-24-1.cable.telstraclear.net (121.73.24.1) 18.037 ms 17.681 ms 17.413 ms 2 ae0-840.ie4.telstraclear.net (203.167.223.114) 12.952 ms 12.781 ms 12.475 ms 3 ge-1-2-0-843.ie1.telstraclear.net (218.101.61.105) 21.357 ms 20.910 ms 20.661 ms 4 203.98.50.27 (203.98.50.27) 24.332 ms 24.066 ms 23.950 ms I have noticed it preventing non http traffic flowing across port 80 (netcat to amazon cloud), as well as interfering with stun and various other bits and pieces, (incoming and outgoing connections to/from local webserver take longer than usual) Can anyone confirm similar behaviour who is on Telstra cable network, or have further details. Appears to be a netcache proxy. Proxy Server Details: 1.1 nc2 (NetCache NetApp/6.0.5P1) Kind regards -JoelW
On some of Telstra’s DSL connections RDP and PPTP/L2TP VPN’s are blocked. So it wouldn’t surprise me if that happens on cable too. From: Craig Spiers [mailto:craig(a)spiers.gen.nz] Sent: Friday, 20 February 2009 8:04 a.m. To: 'Joel Wiramu Pauling'; 'nznog' Subject: Re: [nznog] New Telstra transparent proxy/config? This is pretty common practice when purchasing bandwidth from retail providers.. Cheers From: Joel Wiramu Pauling [mailto:aenertia(a)aenertia.net] Sent: Friday, 20 February 2009 2:43 a.m. To: nznog Subject: [nznog] New Telstra transparent proxy/config? Over the last 24-48 hours I have noticed that I am seeing my IP being mis-represented quite often as 203.98.50.27 which appears to be a new upstream proxy hop I have not seen before: traceroute to 203.98.50.27 (203.98.50.27), 30 hops max, 40 byte packets 1 121-73-24-1.cable.telstraclear.nethttp://121-73-24-1.cable.telstraclear.net (121.73.24.1) 18.037 ms 17.681 ms 17.413 ms 2 ae0-840.ie4.telstraclear.nethttp://ae0-840.ie4.telstraclear.net (203.167.223.114) 12.952 ms 12.781 ms 12.475 ms 3 ge-1-2-0-843.ie1.telstraclear.nethttp://ge-1-2-0-843.ie1.telstraclear.net (218.101.61.105) 21.357 ms 20.910 ms 20.661 ms 4 203.98.50.27 (203.98.50.27) 24.332 ms 24.066 ms 23.950 ms I have noticed it preventing non http traffic flowing across port 80 (netcat to amazon cloud), as well as interfering with stun and various other bits and pieces, (incoming and outgoing connections to/from local webserver take longer than usual) Can anyone confirm similar behaviour who is on Telstra cable network, or have further details. Appears to be a netcache proxy. Proxy Server Details: 1.1 nc2 (NetCache NetApp/6.0.5P1) Kind regards -JoelW
On Friday 20 February 2009 08:09:54 Bill Walker wrote:
On some of Telstra’s DSL connections RDP and PPTP/L2TP VPN’s are blocked. So it wouldn’t surprise me if that happens on cable too.
If you're meaning TelstraClear rather than Telstra (Australia), then I can assure you that there aren't any filters on DSL (or cable for that matter) blocking RDP and PPTP/L2TP VPNs that I'm aware of. I don't know about the situation on the other side of the Tasman though. If you've got evidence to the contrary, I'd quite like to see it. Failing that, please log a ticket with the helpdesk, as that sounds like a fault. --David
1) TelstraClear's network != Telstra's network. 2) TelstraClear have had transparent proxies in their network for a long time, as do many network operators in places like NZ. I am unsure what you're expecting to get from the NZNOG list WRT this. On 20/02/2009, at 2:42 AM, Joel Wiramu Pauling wrote:
Over the last 24-48 hours I have noticed that I am seeing my IP being mis-represented quite often as 203.98.50.27
which appears to be a new upstream proxy hop I have not seen before:
traceroute to 203.98.50.27 (203.98.50.27), 30 hops max, 40 byte packets 1 121-73-24-1.cable.telstraclear.net (121.73.24.1) 18.037 ms 17.681 ms 17.413 ms 2 ae0-840.ie4.telstraclear.net (203.167.223.114) 12.952 ms 12.781 ms 12.475 ms 3 ge-1-2-0-843.ie1.telstraclear.net (218.101.61.105) 21.357 ms 20.910 ms 20.661 ms 4 203.98.50.27 (203.98.50.27) 24.332 ms 24.066 ms 23.950 ms
I have noticed it preventing non http traffic flowing across port 80 (netcat to amazon cloud), as well as interfering with stun and various other bits and pieces, (incoming and outgoing connections to/ from local webserver take longer than usual)
Can anyone confirm similar behaviour who is on Telstra cable network, or have further details.
Appears to be a netcache proxy.
Proxy Server Details: 1.1 nc2 (NetCache NetApp/6.0.5P1)
Kind regards
-JoelW !DSPAM:22,499d61da305761039187772! _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
!DSPAM:22,499d61da305761039187772!
-- Nathan Ward
Joel, Just call them and speak to them, thats what I did.' Cheers, Bill -----Original Message----- From: Nathan Ward [mailto:nznog(a)daork.net] Sent: Friday, 20 February 2009 9:10 a.m. To: nznog Subject: Re: [nznog] New Telstra transparent proxy/config? 1) TelstraClear's network != Telstra's network. 2) TelstraClear have had transparent proxies in their network for a long time, as do many network operators in places like NZ. I am unsure what you're expecting to get from the NZNOG list WRT this. On 20/02/2009, at 2:42 AM, Joel Wiramu Pauling wrote:
Over the last 24-48 hours I have noticed that I am seeing my IP being mis-represented quite often as 203.98.50.27
which appears to be a new upstream proxy hop I have not seen before:
traceroute to 203.98.50.27 (203.98.50.27), 30 hops max, 40 byte packets 1 121-73-24-1.cable.telstraclear.net (121.73.24.1) 18.037 ms 17.681 ms 17.413 ms 2 ae0-840.ie4.telstraclear.net (203.167.223.114) 12.952 ms 12.781 ms 12.475 ms 3 ge-1-2-0-843.ie1.telstraclear.net (218.101.61.105) 21.357 ms 20.910 ms 20.661 ms 4 203.98.50.27 (203.98.50.27) 24.332 ms 24.066 ms 23.950 ms
I have noticed it preventing non http traffic flowing across port 80 (netcat to amazon cloud), as well as interfering with stun and various other bits and pieces, (incoming and outgoing connections to/ from local webserver take longer than usual)
Can anyone confirm similar behaviour who is on Telstra cable network, or have further details.
Appears to be a netcache proxy.
Proxy Server Details: 1.1 nc2 (NetCache NetApp/6.0.5P1)
Kind regards
-JoelW !DSPAM:22,499d61da305761039187772! _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
!DSPAM:22,499d61da305761039187772!
-- Nathan Ward _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
On Friday 20 February 2009 02:42:38 Joel Wiramu Pauling wrote:
which appears to be a new upstream proxy hop I have not seen before:
traceroute to 203.98.50.27 (203.98.50.27), 30 hops max, 40 byte packets 1 121-73-24-1.cable.telstraclear.net (121.73.24.1) 18.037 ms 17.681 ms 17.413 ms 2 ae0-840.ie4.telstraclear.net (203.167.223.114) 12.952 ms 12.781 ms 12.475 ms 3 ge-1-2-0-843.ie1.telstraclear.net (218.101.61.105) 21.357 ms 20.910 ms 20.661 ms 4 203.98.50.27 (203.98.50.27) 24.332 ms 24.066 ms 23.950 ms
I have noticed it preventing non http traffic flowing across port 80 (netcat to amazon cloud), as well as interfering with stun and various other bits and pieces, (incoming and outgoing connections to/from local webserver take longer than usual)
nc2's not new, it's been in the network for several years. That said, it normally behaves very well and doesn't get involved in non-http traffic. Please log a ticket with the helpdesk, and someone will look into it. --David
participants (5)
-
Bill Walker -
Craig Spiers -
David Robb -
Joel Wiramu Pauling -
Nathan Ward