I agree, there is not much to mess with in the configuration of an S5.
My miners are all on DHCP, running on a brand new Gigabit Broadband VPN Router with HP Procurve switches. I recently upgraded my LAN in preparation for Comcast's new 2GB high speed internet service. Yes, that's TWO GIGABIT INTERNET. Its already out and I am just waiting for the installation that will bring fiber to my front door.
I know you guys are trying your best to help me (for which i am very grateful; THANK YOU AGAIN for your time), but I have already tested and re-tested all of the obvious failure points. I have pinged, trace rt, and looked up every DNS & IP address from here to china.
I have a BS in engineering and i have worked in IT for the past 25 years for a fortune 50 company. Trust me when I say its not a power nor an internet issue. Having said that, I must confess that I had an early 4th of july fireworks show in my bedroom awhile back when I connected the power to an S5 backwards. . . .
That's the reason for one of the bad Beaglebones.
PING:
ping bitmaintech.com
PING bitmaintech.com (119.9.105.101): 56 data bytes
64 bytes from 119.9.105.101: seq=0 ttl=46 time=222.204 ms
64 bytes from 119.9.105.101: seq=1 ttl=46 time=222.364 ms
64 bytes from 119.9.105.101: seq=2 ttl=46 time=221.319 ms
64 bytes from 119.9.105.101: seq=3 ttl=46 time=223.023 ms
64 bytes from 119.9.105.101: seq=4 ttl=46 time=221.688 ms
64 bytes from 119.9.105.101: seq=5 ttl=46 time=223.761 ms
--- bitmaintech.com ping statistics ---
6 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max = 221.319/222.393/223.761 ms
tracert:
traceroute bitmaintech.com
traceroute to bitmaintech.com (119.9.105.101), 30 hops max, 38 byte packets
1 10.0.78.1 (10.0.78.1) 0.438 ms 1.007 ms 0.432 ms
2 10.0.0.1 (10.0.0.1) 0.706 ms 0.667 ms 0.586 ms
3 96.120.5.13 (96.120.5.13) 8.412 ms 8.437 ms 8.307 ms
4 xe-9-3-0-sur02.a2atlanta.ga.atlanta.comcast.net (68.86.110.233) 10.420 ms 7.862 ms 8.362 ms
5 xe-4-0-6-0-ar01.d1stonemtn.ga.atlanta.comcast.net (68.85.110.141) 8.407 ms xe-4-0-5-0-ar01.d1stonemtn.ga.atlanta.comcast.net (68.85.172.25) 8.592 ms xe-0-1-0-0-sur01.a2atlanta.ga.atlanta.comcast.net (68.86.106.9) 7.750 ms
6 xe-4-0-7-0-ar01.b0atlanta.ga.atlanta.comcast.net (68.86.106.89) 9.164 ms ae-2-0-ar01.b0atlanta.ga.atlanta.comcast.net (68.85.109.241) 9.762 ms 8.720 ms
7 he-0-4-0-0-cr02.56marietta.ga.ibone.comcast.net (68.86.93.125) 11.516 ms 9.521 ms he-0-4-0-7-cr02.56marietta.ga.ibone.comcast.net (68.86.91.77) 12.487 ms
8 he-0-13-0-1-pe04.56marietta.ga.ibone.comcast.net (68.86.88.62) 10.932 ms 10.658 ms 13.700 ms
9 ix-4-2-1-0.tcore1.A56-Atlanta.as6453.net (209.58.44.41) 12.214 ms 9.536 ms ix-0-2-0-0.tcore1.A56-Atlanta.as6453.net (209.58.44.1) 9.056 ms
10 if-15-2.tcore1.DT8-Dallas.as6453.net (66.110.56.93) 217.596 ms 218.832 ms 217.308 ms
11 if-2-2.tcore2.DT8-Dallas.as6453.net (66.110.56.6) 220.515 ms 220.356 ms 225.928 ms
12 if-8-2.tcore1.LVW-Los-Angeles.as6453.net (66.110.57.82) 220.959 ms 222.820 ms 218.660 ms
13 if-2-2.tcore2.LVW-Los-Angeles.as6453.net (66.110.59.2) 238.982 ms 237.536 ms 240.126 ms
14 if-12-2.tcore2.TV2-Tokyo.as6453.net (66.110.59.62) 229.403 ms 220.961 ms 221.365 ms
15 if-2-2.tcore1.TV2-Tokyo.as6453.net (180.87.180.1) 217.124 ms 219.539 ms 218.679 ms
16 if-5-2.tcore1.HK2-Hong-Kong.as6453.net (180.87.112.205) 221.517 ms if-3-2.tcore1.HK2-Hong-Kong.as6453.net (180.87.112.5) 230.266 ms if-5-2.tcore1.HK2-Hong-Kong.as6453.net (180.87.112.205) 226.414 ms
17 180.87.112.118 (180.87.112.118) 219.071 ms 232.375 ms 221.524 ms
18 edge4.hkg30-core1a.hkg1.rackspace.net (120.136.47.136) 219.773 ms 222.759 ms 218.657 ms
19 dcpe1-core1a.hkg1.rackspace.net (120.136.47.169) 225.005 ms 223.868 ms 243.836 ms
20 119.9.64.71 (119.9.64.71) 220.585 ms 260.369 ms 219.149 ms
21 119.9.105.101 (119.9.105.101) 222.476 ms !C 221.467 ms !C 216.282 ms !C
DNS lookup
nslookup bitmaintech.com
Server: 75.75.75.75
Address 1: 75.75.75.75 cdns01.comcast.net
Name: bitmaintech.com
Address 1: 119.9.105.101