OUTL server
http://img102.imageshack.us/img102/2917 ... ed19kl.jpg
kAoS server
http://img102.imageshack.us/img102/2756 ... ed28zw.jpg
Canere server
http://img212.imageshack.us/img212/867/untitled31ys.jpg
ping?
OK this one is a beast of a tracer, nice stuff... it actually tells you the Package size of each of the games you play online, so as to configure your connection for max effectiveness.
Bit complex to get into, but well worth it.
Ethereal 0.10.14
Not sure wich protocol Unreal Engine uses but it's likely to be within this 750 strong listing that this program can handle:
It's hard to get into this prog unless you really have a firm graps of Protocols and Network shit, but from what I gatehr the Packet size of UT4 is around the 64 to 128 mark.
Don't quote me on that, I have still to fully determine that to be 100% correct, i will post it when i know for sure.
Tip: If you have a Uninstaller program running on your sytem then set it to monitor the intallation of this Ethereal because it install a shitload on packet sniffers and gateways. Always agood idea to be able to unistall it fully when the time comes.
Whne you have it installed, set it to capture off your Network card that is connected to your router/modem.
now before you start it capturing your traffic, boot up UT or what ever game you want to sniff out and log onto a server, then minimise the game or window it. Start the Ethereal Capture, then go back to your game window and play fopr about 1 to 2 minutes, close your game down. Goto Ethereal and stop the Capture.
Now look at the data it captured to see the size of the packets been sent between your client and the game server.
I'm sure there is abetter way to do it with this prog, I jsut haven't found it yet.
Bit complex to get into, but well worth it.
Ethereal 0.10.14
Not sure wich protocol Unreal Engine uses but it's likely to be within this 750 strong listing that this program can handle:
750 protocols can currently be dissected:
3COMXNS, 3GPP2 A11, 802.11 MGT, 802.11 Radiotap, 802.3 Slow protocols, 9P, AAL1, AAL3/4, AARP, ACAP, ACN, ACSE, ACtrace, ADP, AFP, AFS (RX), AH, AIM, AIM Administration, AIM Advertisements, AIM BOS, AIM Buddylist, AIM Chat, AIM ChatNav, AIM Directory, AIM Email, AIM Generic, AIM ICQ, AIM Invitation, AIM Location, AIM Messaging, AIM OFT, AIM Popup, AIM SSI, AIM SST, AIM Signon, AIM Stats, AIM Translate, AIM User Lookup, AJP13, ALC, ALCAP, AMR, ANS, ANSI BSMAP, ANSI DTAP, ANSI IS-637-A Teleservice, ANSI IS-637-A Transport, ANSI IS-683-A (OTA (Mobile)), ANSI IS-801 (Location Services (PLD)), ANSI MAP, AODV, AOE, ARCNET, ARP/RARP, ARTNET, ASAP, ASF, ASN1, ASP, ATM, ATM LANE, ATP, ATSVC, AVS WLANCAP, AX4000, AgentX, Armagetronad, Auto-RP, BACapp, BACnet, BEEP, BER, BFD Control, BGP, BICC, BOFL, BOOTP/DHCP, BOOTPARAMS, BOSSVR, BROWSER, BSSAP, BSSGP, BUDB, BUTC, BVLC, Basic Format XID, BitTorrent, Boardwalk, CAMEL, CAST, CBAPDev, CCSDS, CCSRL, CDP, CDS_CLERK, CDT, CFLOW, CGMP, CHDLC, CIGI, CIMD, CIP, CISCOWL-L2, CLDAP, CLEARCASE, CLNP, CLTP, CMIP, CMP, CMS, CONV, COPS, COSEVENTCOMM, COSNAMING, COTP, CPFI, CPHA, CRMF, CSM_ENCAPS, CUPS, CoSine, DAAP, DAP, DCCP, DCERPC, DCE_DFS, DCOM, DCP, DDP, DDTP, DEC_DNA, DEC_STP, DFS, DHCPFO, DHCPv6, DIAMETER, DIS, DISP, DISTCC, DLSw, DLT User A, DLT User B, DLT User C, DLT User D, DNP 3.0, DNS, DNSSERVER, DOCSIS, DOCSIS BPKM-ATTR, DOCSIS BPKM-REQ, DOCSIS BPKM-RSP, DOCSIS DSA-ACK, DOCSIS DSA-REQ, DOCSIS DSA-RSP, DOCSIS DSC-ACK, DOCSIS DSC-REQ, DOCSIS DSC-RSP, DOCSIS DSD-REQ, DOCSIS DSD-RSP, DOCSIS INT-RNG-REQ, DOCSIS MAC MGMT, DOCSIS MAP, DOCSIS REG-ACK, DOCSIS REG-REQ, DOCSIS REG-RSP, DOCSIS RNG-REQ, DOCSIS RNG-RSP, DOCSIS TLVs, DOCSIS UCC-REQ, DOCSIS UCC-RSP, DOCSIS UCD, DOCSIS VSIF, DOCSIS type29ucd, DOP, DRSUAPI, DSI, DSP, DSSETUP, DTP, DTSPROVIDER, DTSSTIME_REQ, DUA, DVMRP, Data, E.164, EAP, EAPOL, ECHO, EDONKEY, EDP, EFS, EIGRP, ENC, ENIP, ENRP, ENTTEC, EPM, EPMv4, ESIS, ESP, ESS, ETHERIC, ETHERIP, EVENTLOG, Ethernet, FC, FC ELS, FC FZS, FC-FCS, FC-SB3, FC-SP, FC-SWILS, FC-dNS, FCIP, FCP, FC_CT, FDDI, FIX, FLDB, FR, FRSAPI, FRSRPC, FTAM, FTBP, FTP, FTP-DATA, FTSERVER, FW-1, Frame, G.723, GIF image, GIOP, GMRP, GNM, GNUTELLA, GPRS NS, GPRS-LLC, GRE, GSM BSSMAP, GSM DTAP, GSM RP, GSM SMS, GSM SMS UD, GSM_MAP, GSM_SS, GSS-API, GTP, GVRP, Gryphon, H.223, H.225.0, H.235, H.245, H.261, H.263, H.263 data, H1, H248, HCLNFSD, HPEXT, HPSW, HSRP, HTTP, HyperSCSI, IAP, IAPP, IAX2, IB, ICAP, ICBAAccoCB, ICBAAccoCB2, ICBAAccoMgt, ICBAAccoMgt2, ICBAAccoServ, ICBAAccoServ2, ICBAAccoServSRT, ICBAAccoSync, ICBABrowse, ICBABrowse2, ICBAGErr, ICBAGErrEvent, ICBALDev, ICBALDev2, ICBAPDev, ICBAPDev2, ICBAPDevPC, ICBAPDevPCEvent, ICBAPersist, ICBAPersist2, ICBARTAuto, ICBARTAuto2, ICBAState, ICBAStateEvent, ICBASysProp, ICBATime, ICEP, ICL_RPC, ICMP, ICMPv6, ICP, ICQ, IDP, IDispatch, IEEE 802.11, IEEE802a, IGAP, IGMP, IGRP, ILMI, IMAP, INAP, INITSHUTDOWN, IOXIDResolver, IP, IP/IEEE1394, IPComp, IPDC, IPFC, IPMI, IPP, IPVS, IPX, IPX MSG, IPX RIP, IPX SAP, IPX WAN, IPv6, IRC, IRemUnknown, IRemUnknown2, ISAKMP, ISDN, ISIS, ISL, ISMP, ISUP, ISystemActivator, IUA, IrCOMM, IrLAP, IrLMP, IuUP, JFIF (JPEG) image, JXTA, JXTA Framing, JXTA Message, JXTA UDP, JXTA Welcome, Jabber, Juniper, K12xx, KADM5, KINK, KLM, KRB4, KRB5, KRB5RPC, Kpasswd, L2TP, LANMAN, LAPB, LAPBETHER, LAPD, LDAP, LDP, LLAP, LLC, LLDP, LMI, LMP, LOOP, LPD, LSA, LWAPP, LWAPP-CNTL, LWAPP-L3, LWRES, Laplink, Line-based text data, Log, LogotypeCertExtn, Lucent/Ascend, M2PA, M2TP, M2UA, M3UA, MACC, MAPI, MAP_DialoguePDU, MATE, MDS Header, MEGACO, MGCP, MGMT, MIME multipart, MIPv6, MMS, MMSE, MOUNT, MPEG1, MPLS, MPLS Echo, MQ, MQ PCF, MRDISC, MS NLB, MS Proxy, MSDP, MSMMS, MSNIP, MSNMS, MSRP, MTP2, MTP3, MTP3MG, Manolito, Media, Messenger, Mobile IP, Modbus/TCP, MySQL, NBAP, NBDS, NBIPX, NBNS, NBP, NBSS, NCP, NCS, NDMP, NDPS, NFS, NFSACL, NFSAUTH, NHRP, NIS+, NIS+ CB, NJACK, NLM, NLSP, NMAS, NMPI, NNTP, NORM, NSIP, NSPI, NS_CERT_EXTS, NTLMSSP, NTP, NW_SERIAL, NetBIOS, Netsync, Null, OAM AAL, OCSP, OLSR, OPSI, OSPF, PAGP, PAP, PARLAY, PCLI, PCNFSD, PER, PFLOG, PFLOG-OLD, PGM, PGSQL, PIM, PKCS-1, PKIX Certificate, PKIX1EXPLICIT, PKIX1IMPLICIT, PKIXPROXY, PKIXQUALIFIED, PKIXTSP, PKInit, PKTC, PN-DCP, PN-RT, PNIO, PNP, POP, PPP, PPP BACP, PPP BAP, PPP CBCP, PPP CCP, PPP CDPCP, PPP CHAP, PPP Comp, PPP IPCP, PPP IPV6CP, PPP LCP, PPP MP, PPP MPLSCP, PPP OSICP, PPP PAP, PPP PPPMux, PPP PPPMuxCP, PPP VJ, PPP-HDLC, PPPoED, PPPoES, PPTP, PRES, PTP, PVFS, P_MUL, Portmap, Prism, Q.2931, Q.931, Q.933, QLLC, QUAKE, QUAKE2, QUAKE3, QUAKEWORLD, R-STP, RADIUS, RANAP, RDM, RDT, REMACT, REP_PROC, RIP, RIPng, RLM, RMCP, RMI, RMP, RNSAP, ROS, RPC, RPC_BROWSER, RPC_NETLOGON, RPL, RQUOTA, RRAS, RSH, RSTAT, RSVP, RSYNC, RS_ACCT, RS_ATTR, RS_BIND, RS_PGO, RS_PLCY, RS_REPADM, RS_REPLIST, RS_UNIX, RTCP, RTMP, RTP, RTP Event, RTPS, RTSE, RTSP, RTcfg, RTmac, RUDP, RWALL, RX, Raw, Raw_SIP, Raw_SigComp, Redback, Rlogin, SADMIND, SAMR, SAP, SCCP, SCCPMG, SCSI, SCTP, SDLC, SDP, SEBEK, SECIDMAP, SES, SGI MOUNT, SIGCOMP, SIP, SIPFRAG, SIR, SKINNY, SLARP, SLL, SM, SMB, SMB Mailslot, SMB Pipe, SMB2, SMB_NETLOGON, SMPP, SMRSE, SMTP, SMUX, SNA, SNA XID, SNAETH, SNDCP, SNMP, SONMP, SPNEGO, SPNEGO-KRB5, SPOOLSS, SPP, SPRAY, SPX, SRP, SRVLOC, SRVSVC, SSCF-NNI, SSCOP, SSH, SSL, SSS, STANAG 4406, STANAG 5066, STAT, STAT-CB, STP, STUN, SUA, SVCCTL, Serialization, SliMP3, Socks, SoulSeek, Symantec, Synergy, Syslog, T.38, TACACS, TACACS+, TALI, TANGO, TAPI, TCAP, TCP, TDMA, TDS, TEI_MANAGEMENT, TELNET, TFTP, TIME, TIPC, TKN4Int, TNS, TPCP, TPKT, TR MAC, TRKSVR, TSP, TTP, TUXEDO, TZSP, Teredo, Token-Ring, UBIKDISK, UBIKVOTE, UCP, UDP, UDPENCAP, UDPlite, UMA, V.120, V5UA, VLAN, VNC, VRRP, VTP, Vines ARP, Vines Echo, Vines FRP, Vines ICP, Vines IP, Vines IPC, Vines LLC, Vines RTP, Vines SPP, WAP SIR, WBXML, WCCP, WCP, WHDLC, WHO, WINREG, WINS-Replication, WKSSVC, WLANCERTEXTN, WSP, WTLS, WTP, X.25, X.29, X11, X411, X420, X509AF, X509CE, X509IF, X509SAT, XDMCP, XML, XOT, XYPLEX, YHOO, YMSG, YPBIND, YPPASSWD, YPSERV, YPXFR, ZEBRA, ZIP, cds_solicit, cprpc_server, dc, dce_update, dicom, giFT, h221nonstd, h450, iFCP, iSCSI, iSNS, isup_thin, itunes, llb, message/http, nettl, rdaclif, roverride, rpriv, rs_attr_schema, rs_misc, rs_prop_acct, rs_prop_acl, rs_prop_attr, rs_prop_pgo, rs_prop_plcy, rs_pwd_mgmt, rs_repmgr, rsec_login, rss, sFlow, smil,
It's hard to get into this prog unless you really have a firm graps of Protocols and Network shit, but from what I gatehr the Packet size of UT4 is around the 64 to 128 mark.
Don't quote me on that, I have still to fully determine that to be 100% correct, i will post it when i know for sure.
Tip: If you have a Uninstaller program running on your sytem then set it to monitor the intallation of this Ethereal because it install a shitload on packet sniffers and gateways. Always agood idea to be able to unistall it fully when the time comes.
Whne you have it installed, set it to capture off your Network card that is connected to your router/modem.
now before you start it capturing your traffic, boot up UT or what ever game you want to sniff out and log onto a server, then minimise the game or window it. Start the Ethereal Capture, then go back to your game window and play fopr about 1 to 2 minutes, close your game down. Goto Ethereal and stop the Capture.
Now look at the data it captured to see the size of the packets been sent between your client and the game server.
I'm sure there is abetter way to do it with this prog, I jsut haven't found it yet.
Long-Pig Chef and the Hairless Goat..
OK, nailed it!
Here we go boys and girls, we now know the size of the UT4 packet size from server to client n viceversa.
Brief explanation detailing were and how to read it correctly:
So after applying a filter to cut out network noise, in this case i was on the TechGaming server (Wer i found 2k bullying a few n00bs in Insta.... shame on u 2k.... lol) the overall average for Pack Size was 75 at no time did it go over 128. Now I'm assuming that, the more activity there is on the server the bigger the pack size, so if you were in the middle of a 10 player Exessive fragfest, most likely the Pack size would be bigger, we need to test this wen our server goes back up. ok.
Here is how to apply a filter in the Filter window:
ip.addr==202.125.43.101
k, the pretex has to be:
ip.addr==
followed by what ever IP you want to concentrate on.
Remember this is NOT a tracert or a pinga, it is a packet/network sniffer, therefore you have to follow the above procedure to get the packets then you need to apply the above filter to isolate the packtes from your client to the game server. This way, the game server can be anything from UT to MarioBros Cart Wars Bloodbath IX.
So using the visual PING tool and not the Trace tool, enter your packet size as 128 and hit go and you will get a pretty accurate ping directly to your game server based on that games protocol and packet size.
Now I am going to sleep, my work here is done.
20 dolla plz or a slab of Hann Premium...
Here we go boys and girls, we now know the size of the UT4 packet size from server to client n viceversa.
Brief explanation detailing were and how to read it correctly:
The total size of the packet can be found either
in the "Frame N" line in the protocol tree window for the
packet (the "on wire" value), or the "Packet Length" field that
appears if you open up that line
or
in the packet list window *if* you add a new column from the
dialog box popped up by the "Preferences" item in the "Edit"
menu; enter a name for the new column in "Column title:", select
"Packet length (bytes)" from the "Column format:" option menu,
click "New", click "Save", click "OK", and then exit and restart
Ethereal (alas, we currently don't update the display on the
fly; that will probably happen some day, but it requires more
stuff to be changed than you might think).
So after applying a filter to cut out network noise, in this case i was on the TechGaming server (Wer i found 2k bullying a few n00bs in Insta.... shame on u 2k.... lol) the overall average for Pack Size was 75 at no time did it go over 128. Now I'm assuming that, the more activity there is on the server the bigger the pack size, so if you were in the middle of a 10 player Exessive fragfest, most likely the Pack size would be bigger, we need to test this wen our server goes back up. ok.
Here is how to apply a filter in the Filter window:
ip.addr==202.125.43.101
k, the pretex has to be:
ip.addr==
followed by what ever IP you want to concentrate on.
Remember this is NOT a tracert or a pinga, it is a packet/network sniffer, therefore you have to follow the above procedure to get the packets then you need to apply the above filter to isolate the packtes from your client to the game server. This way, the game server can be anything from UT to MarioBros Cart Wars Bloodbath IX.
So using the visual PING tool and not the Trace tool, enter your packet size as 128 and hit go and you will get a pretty accurate ping directly to your game server based on that games protocol and packet size.
Now I am going to sleep, my work here is done.
20 dolla plz or a slab of Hann Premium...
Long-Pig Chef and the Hairless Goat..
-
kAoS-Maian0
- kAoS.KilleR
- Posts: 612
- Joined: 17 Apr 2004 01:00
- Location: Adelaide, South Australia
- Contact:
HOW TELSTRA FUCKT UP WoW .
Not gonna pay much longer for something I cant play.
http://forums.worldofwarcraft.com/threa ... 755055&P=1
Not gonna pay much longer for something I cant play.
http://forums.worldofwarcraft.com/threa ... 755055&P=1
This is my email to Telstra today:
I do alot of online gaming and that is the reason why I am on the plan that
I am on.
In the last three weeks suddenly something has caused my connection to the
gaming server to be slower therefore I traced where the issue may lie. This
caused me to discover a number of time outs with the IP addresses I have
e-mailed earlier today. This is the IP address I use to connect with no
problems - 150.101.195.3. If I ping this address now I receive a high number
of time outs i.e. between 180-200+.
An example, today I used what Telstra advised me use being "Hypertrace" and
the results are:
1,10.204.232.1,8ms,None,0%
2,61.9.211.194,17ms,CPE-61-9-211-1 94.qld.bigpond.net.au,0%
3,61.9.210.3,17ms,CPE-61-9-210-3.q ld.bigpond.net.au,0%
4,139.130.239.249,8ms,GigabitEther net3-3.woo4.Brisbane.telstra.net,0 %
5,203.50.51.129,22ms,GigabitEthern et6-0.woo-core1.Brisbane.telstra.n et,0%
6,203.50.6.221,20ms,Pos-Channel1.k en-core4.Sydney.telstra.net,0%
7,203.50.20.33,20ms,TenGigabitEthe rnet7-1.ken23.Sydney.telstra.net,0 %
8,139.130.73.50,189ms,pinpoi7.lnk. telstra.net,0%
9,150.101.199.232,205ms,gi0-0.bdr1 .syd6.agile.on.net,0%
10,150.101.120.117,184ms,pos2-0.co r1.cbr1.agile.on.net,0%
11,150.101.195.3,185ms,gs2.mcgoohq .com.au,0%
As you can see, in the 8th line, once I reach the 139.130.73.50 my
milliseconds go higher from 20 to 189. This does not seem normal to me. I
believe that this is line tells me the problems lies with
"pinpoi7.lnk.telstra.net". This may cause other people, who follow this
route from Brisbane, the same problem as I am currently experiencing.
Regards
OK and now is the replay from telstra :
Response (Tim Brown) - 09/03/2006 08:12 PM
Dear Mr .
Thank you for your email dated 09/03/2006 regarding ping times between hops on the BigPond network.
BigPond does not provide any guarentee's in regard to ping times on our network. As such there is nothing we can do to resolve your issue.
If you have any other questions, please visit our Help Centre at www.bigpond.com/help.
Fuck this shite GRRRRRRRR
Fuck you telstra
Fuck you Tim Brown
I do alot of online gaming and that is the reason why I am on the plan that
I am on.
In the last three weeks suddenly something has caused my connection to the
gaming server to be slower therefore I traced where the issue may lie. This
caused me to discover a number of time outs with the IP addresses I have
e-mailed earlier today. This is the IP address I use to connect with no
problems - 150.101.195.3. If I ping this address now I receive a high number
of time outs i.e. between 180-200+.
An example, today I used what Telstra advised me use being "Hypertrace" and
the results are:
1,10.204.232.1,8ms,None,0%
2,61.9.211.194,17ms,CPE-61-9-211-1 94.qld.bigpond.net.au,0%
3,61.9.210.3,17ms,CPE-61-9-210-3.q ld.bigpond.net.au,0%
4,139.130.239.249,8ms,GigabitEther net3-3.woo4.Brisbane.telstra.net,0 %
5,203.50.51.129,22ms,GigabitEthern et6-0.woo-core1.Brisbane.telstra.n et,0%
6,203.50.6.221,20ms,Pos-Channel1.k en-core4.Sydney.telstra.net,0%
7,203.50.20.33,20ms,TenGigabitEthe rnet7-1.ken23.Sydney.telstra.net,0 %
8,139.130.73.50,189ms,pinpoi7.lnk. telstra.net,0%
9,150.101.199.232,205ms,gi0-0.bdr1 .syd6.agile.on.net,0%
10,150.101.120.117,184ms,pos2-0.co r1.cbr1.agile.on.net,0%
11,150.101.195.3,185ms,gs2.mcgoohq .com.au,0%
As you can see, in the 8th line, once I reach the 139.130.73.50 my
milliseconds go higher from 20 to 189. This does not seem normal to me. I
believe that this is line tells me the problems lies with
"pinpoi7.lnk.telstra.net". This may cause other people, who follow this
route from Brisbane, the same problem as I am currently experiencing.
Regards
OK and now is the replay from telstra :
Response (Tim Brown) - 09/03/2006 08:12 PM
Dear Mr .
Thank you for your email dated 09/03/2006 regarding ping times between hops on the BigPond network.
BigPond does not provide any guarentee's in regard to ping times on our network. As such there is nothing we can do to resolve your issue.
If you have any other questions, please visit our Help Centre at www.bigpond.com/help.
Fuck this shite GRRRRRRRR
Fuck you telstra
Fuck you Tim Brown
Last edited by kAoS-2k on 09 Mar 2006 22:45, edited 2 times in total.
Open your eyes Telstra.!!!
Why are all Brisbane users limited to the high speed which Telstra is
providing to all Big Pond customers. Do you think that Brisbane customers
are not being treated fairly and as we are paying the same money per month
as other customers with a cable connection in Australia. I pay for 10 Gb
per month and have not used it this month due to the poor performance
received.
This has only become a problem for Brisbane in the last 3 weeks so why is it different
now and why can't Telstra resolve this issue? If it is not Telstra's
responsibility to resolve this issue, then whose is it? What company do I
need to speak to if it is not Telstra i.e. who owns the router causing the
problem?
As a loyal Telstra customer, I find this unfair and hard to believe that
Telstra cannot assist me in resolving this issue. As I said before a number
of Brisbane customers are experiencing the same problem. I believe
customers in Brisbane will leave Telstra because of this issue. It is
actively being discussed in several forums as we speak as I am not the only
one!
I would like this matter escalated as I believe this is not been taken
seriously by Telstra's second level technicians.
I am asking all people who are experiencing the same problem to e-mail Telstra.
To: "Bigpond Technical Support" <bigpond@bigpond-mail.custhelp.com> as I have done in order to place pressure on them to resolve this. The more people who submit the same issue, Telstra will hopefully take us more seriously and just not an isolated incident! PLEASE SUPPORT ME!
Why are all Brisbane users limited to the high speed which Telstra is
providing to all Big Pond customers. Do you think that Brisbane customers
are not being treated fairly and as we are paying the same money per month
as other customers with a cable connection in Australia. I pay for 10 Gb
per month and have not used it this month due to the poor performance
received.
This has only become a problem for Brisbane in the last 3 weeks so why is it different
now and why can't Telstra resolve this issue? If it is not Telstra's
responsibility to resolve this issue, then whose is it? What company do I
need to speak to if it is not Telstra i.e. who owns the router causing the
problem?
As a loyal Telstra customer, I find this unfair and hard to believe that
Telstra cannot assist me in resolving this issue. As I said before a number
of Brisbane customers are experiencing the same problem. I believe
customers in Brisbane will leave Telstra because of this issue. It is
actively being discussed in several forums as we speak as I am not the only
one!
I would like this matter escalated as I believe this is not been taken
seriously by Telstra's second level technicians.
I am asking all people who are experiencing the same problem to e-mail Telstra.
To: "Bigpond Technical Support" <bigpond@bigpond-mail.custhelp.com> as I have done in order to place pressure on them to resolve this. The more people who submit the same issue, Telstra will hopefully take us more seriously and just not an isolated incident! PLEASE SUPPORT ME!
.gif)
hmm i ping ok to pinpoi7.lnk.telstra.net
race Route for http://139.130.73.50/ by Trellian Trace
http://139.130.73.50/
1 192.168.0.1 unknown 0ms
2 10.142.88.1 unknown 16ms
3 61.9.207.194 unknown 31ms
4 61.9.195.3 unknown 15ms
5 139.130.66.61 GigabitEthernet4-3.chw30.Sydney.telstra.net 15ms
6 203.50.19.33 TenGigabitEthernet7-2.ken23.Sydney.telstra.net 15ms
7 139.130.73.50 pinpoi7.lnk.telstra.net 15ms
race Route for http://139.130.73.50/ by Trellian Trace
http://139.130.73.50/
1 192.168.0.1 unknown 0ms
2 10.142.88.1 unknown 16ms
3 61.9.207.194 unknown 31ms
4 61.9.195.3 unknown 15ms
5 139.130.66.61 GigabitEthernet4-3.chw30.Sydney.telstra.net 15ms
6 203.50.19.33 TenGigabitEthernet7-2.ken23.Sydney.telstra.net 15ms
7 139.130.73.50 pinpoi7.lnk.telstra.net 15ms
What i rely nide is :
The tracert results demonstrate the route a packet takes from your computer to a destination. It says nothing about the route a packet would take to get from the destination back to your computer. Normally one would expect it to be the same, but it doesn't have to be. If one of the routers along the path was configured to use a different route to get to your IP address than for mine, then it is possible that your ICMP error returns will came back by a different (longer?) route than mine.
So, don't know how helpful the folk at Agile are, but maybe you can give them a call and explain that you need some help to demonstrate that BigPond are stuffing you around (that might appeal to them) and then you need them to do a TRACERT from their network (preferably from the game server) to your IP address. You could offer to send them the forward TRACERT to help them ensure they are providing the correct reverse route.
A bit "out there" perhaps, but might be worth a try. If the reverse route is different, it might be the evidence required to get BigPond to look further at it.
OK i bin chenging my ip a lot in th last 3 weekss .LOL my carent ip is: 149.167.148.7
The tracert results demonstrate the route a packet takes from your computer to a destination. It says nothing about the route a packet would take to get from the destination back to your computer. Normally one would expect it to be the same, but it doesn't have to be. If one of the routers along the path was configured to use a different route to get to your IP address than for mine, then it is possible that your ICMP error returns will came back by a different (longer?) route than mine.
So, don't know how helpful the folk at Agile are, but maybe you can give them a call and explain that you need some help to demonstrate that BigPond are stuffing you around (that might appeal to them) and then you need them to do a TRACERT from their network (preferably from the game server) to your IP address. You could offer to send them the forward TRACERT to help them ensure they are providing the correct reverse route.
A bit "out there" perhaps, but might be worth a try. If the reverse route is different, it might be the evidence required to get BigPond to look further at it.
OK i bin chenging my ip a lot in th last 3 weekss .LOL my carent ip is: 149.167.148.7
BigPond does not provide any guarentee's in regard to ping times on our network. As such there is nothing we can do to resolve your issue.
What did I say like 10,000 post ago?
To make it simple;
Not one person within Telsra gives a flying fuck about you or your ping, they only want your money in return for a percentage of what they are selling you. And they can do that because you signed a contract that allows them to legally treat you like that.
Long-Pig Chef and the Hairless Goat..
kAoS-Rage wrote:give me your ip 2k
see what i get whan i do a trace to your pc.
Not possible.
I can reverse trace your IP, throught OzForces, but I can only do it next week.
So keep your ICQ on, so you can send me your IP, when it is time.
Remeber, the way you route to a game server is both dependent on how your ISP connects you out of their "juristiction" and how the game server routes in-coming connections.
So it really is a long shot that you will get solid ping for along period of time, it's more likely that you ping will vary, as it can take many possible routing paths to the game server.
In other words, it will make NO difference what you present Tesltra with, because it is just as dependent from the Game servers provider. So if for example:
Out of 13 nodes, 6 are Telstra controlled. In your tracerts, you can determine that the cause of the problem is within one of the Telstra nodes.
You inform them of that. They will reply:
a) OK, we will change your path to avoid that particular node.
b) There are NO possible alternate paths because of your geographical location.
c) The equipment has been schedulled for overhaul/upgrade in the next 200 years.
d) Due to a dramatic traffic increase fromt that area, we can not alternatly route you because all our nodes are saturated.
e) Shut the fuck up and upgrade to our premium services.
OK so let's say they gop for Option a), suddenly you rping improves, etc... but then it degrades again. Why?
The other 7 nodes are not telsttra controlled and they suddenly have saturated traffic. You find yourself back at square one.
My point is: Don't excpect a major improvement. Until the entire network upgrades into the 21st Century, like 90% of other coutries around the world.
It has to do with national complience and agreement on policy for standars, instead wat we have is a deregulated market place, that encourages monopolies at the expensive of service and intergration.
Patience, keep trying, but don't expect the perfect solution.
Long-Pig Chef and the Hairless Goat..
