[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	9220
Summary	software-update download server-selection is sub-optimal [MINOR impact]
Classification	Unclassified
Product	Web sites
Version	N/A
Hardware	x86
OS	Windows 8
Status	UNCONFIRMED
Severity	Enhancement
Priority	Low
Component	Main site - www.wireshark.org
Assignee	bugzilla-admin@wireshark.org
Reporter	enger@enger.us

Build Information:
am running Version 1.10.1 (SVN Rev 50926 from /trunk-1.10) 


--
hi:
I am a wireshark user.  Thank you for making wireshark available!
I am presently downloading a software update to Wireshark.
The download speed from your software-update server varies from 100 KILO
bits/sec to as much as 700 KILObps.  I have a FiOS500 500Mbps data service.

I used wireshark itself to see where the download is coming from.
I am in Los Angeles.  You are serving the download from near Washington, DC.
The traceroute to the IP address of the download server is attached.

Assuming there are more than one download-server for Wireshark here in the USA,
I can only imagine that it would be more-otpimal to chose almost any one of the
other servers, than the one all the way on the other side of the continent.  

So, I wanted ot suggest that as time permits, perhaps someone could build some
additional logic into the server-selection system.  Make the client intelligent
enough to locate the closest download server.

Thanks very much for reviewing this note.  AND, thank you for making Wireshark
available!  A great tool!!!!

Best wishes,
Bob Enger

C:\Windows\system32>tracert 69.4.231.52

Tracing route to jangle.cacetech.com [69.4.231.52]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     2 ms     1 ms     2 ms  L100.LSANCA-VFTTP-157.verizon-gni.net
[71.189.7.1]
  3    18 ms    19 ms    37 ms  G0-3-0-3.LSANCA-LCR-22.verizon-gni.net
[130.81.146.58]
  4     5 ms     5 ms     5 ms  so-4-1-0-0.LAX01-BB-RTR2.verizon-gni.net
[130.81.151.248]
  5     3 ms     3 ms     3 ms  0.xe-5-1-0.BR1.LAX15.ALTER.NET [152.63.114.105]
  6     4 ms     4 ms     4 ms  ae6.edge1.LosAngeles9.level3.net [4.68.62.169]
  7     4 ms     4 ms     4 ms  ae-1-60.edge1.LosAngeles6.Level3.net
[4.69.144.16]
  8     5 ms     4 ms     4 ms  te2-5.bbr01.cs01.lax01.networklayer.com
[4.26.0.70]
  9     7 ms     7 ms     7 ms  ae7.bbr01.cs01.lax01.networklayer.com
[173.192.18.166]
 10    37 ms    37 ms    37 ms  ae19.bbr01.eq01.dal03.networklayer.com
[173.192.18.140]
 11    37 ms    36 ms    36 ms  ae7.bbr02.eq01.dal03.networklayer.com
[173.192.18.209]
 12    76 ms    75 ms    75 ms  ae1.bbr01.tl01.atl01.networklayer.com
[173.192.18.135]
 13    77 ms    76 ms    76 ms  ae0.bbr01.eq01.wdc02.networklayer.com
[173.192.18.152]
 14    79 ms    85 ms    79 ms  ae0.dar01.sr01.wdc01.networklayer.com
[173.192.18.197]
 15    79 ms    78 ms    79 ms  po1.fcr01.sr01.wdc01.networklayer.com
[208.43.118.134]
 16   125 ms     *      131 ms  jangle.cacetech.com [69.4.231.52]
 17   130 ms   115 ms   119 ms  jangle.cacetech.com [69.4.231.52]

Trace complete.

---

      You are receiving this mail because:

• You are watching all bug changes.