Aces High Bulletin Board

Help and Support Forums => Technical Support => Topic started by: bustr on October 20, 2011, 01:18:33 PM

Title: PingPlotter/Tracert Question
Post by: bustr on October 20, 2011, 01:18:33 PM
When I (tracert) or PingPlotter to 206.16.60.38, (.60.39), (.60.41) my 6th hop changes address every other trace or pingplot ping itteration from 12.122.251.66 to 12.122.251.70. What does this mean? I'm located in Oakland CA.

My current router's address: 70.231.226.127

C:\>tracert 206.16.60.41

Tracing route to 206.16.60.41 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    43 ms    42 ms    43 ms  adsl-70-231-255-254.dsl.snfc21.sbcglobal.net [70.231.255.254]
  3    43 ms    43 ms    43 ms  dist1-vlan62.snfcca.sbcglobal.net [206.13.3.129]
  4    43 ms    42 ms    43 ms  bb1-10g2-0.snfcca.sbcglobal.net [216.102.176.224]
  5    87 ms    87 ms    87 ms  ggr1.dlstx.ip.att.net [12.122.138.1]
  6    87 ms    87 ms    87 ms  12.122.251.70
  7    87 ms    87 ms    87 ms  mdf001c7613r0003-gig-10-1.dal1.attens.net [63.241.193.10]
  8    88 ms    87 ms    87 ms  206.16.60.41

Trace complete.

C:\>tracert 206.16.60.41

Tracing route to 206.16.60.41 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    44 ms    43 ms    43 ms  adsl-70-231-255-254.dsl.snfc21.sbcglobal.net [70.231.255.254]
  3    43 ms    42 ms    44 ms  dist1-vlan62.snfcca.sbcglobal.net [206.13.3.129]
  4    43 ms    43 ms    42 ms  bb1-10g2-0.snfcca.sbcglobal.net [216.102.176.224]
  5    86 ms    86 ms    86 ms  ggr1.dlstx.ip.att.net [12.122.138.1]
  6    87 ms    87 ms    87 ms  12.122.251.66
  7    87 ms    87 ms    87 ms  mdf001c7613r0003-gig-10-1.dal1.attens.net [63.241.193.10]
  8    87 ms    86 ms    88 ms  206.16.60.41

Trace complete.
Title: Re: PingPlotter/Tracert Question
Post by: Skuzzy on October 20, 2011, 01:42:54 PM
It usually means a router has more than one IP address, which is pretty normal these days.
Title: Re: PingPlotter/Tracert Question
Post by: bustr on October 20, 2011, 02:20:35 PM
This is my first time ever seeing the adress change in real time. It only started in this last month. Will it have any effect on my game play?

I've recently been using up 100-115 of 120 20mm at 50 yards in a Yak9U to take down one con. Previously, until I saw this phenomenon , 5-10 to perform the same job. In game my Varyance&Delay is flat and my Host Queue is flat with only 30 services, no firewalling  and AV turned off running in Win7 64.

This phenomenon could be anectdotal at face value I understand. Still, how are my UDP packets effected by the address changing at every other ping in the total round trip path in terms of latency? Won't this cause problems with the UDP stream if the address is flipping cyclicly?