Quote:
Originally Posted by asbo dog
any one know what the ip address is of the firebrick tbb are using and is it possible path ping it, would like to see where the packet loss is happening as the loss levels seem same across vm network but latency is different.
the increase in loss today is defo due to the rain increasing usage
hum jus ad idea to turn flood back on and try and gain the ip from the logs
|
There's probably several. The one I'm getting pinged from is:
C:\Users\Administrator>tracert 80.249.99.164
Tracing route to pingbox1.thinkbroadband.com [80.249.99.164]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms n1 [10.0.0.254]
2 43 ms 8 ms 48 ms cpc9-sgyl31-2-0-gw.sgyl.cable.virginmedia.com [77.99.218.1]
3 15 ms 27 ms 12 ms sgyl-core-1a-ge229.network.virginmedia.net [81.97.49.29]
4 20 ms 23 ms 63 ms manc-bb-1c-ae3-0.network.virginmedia.net [195.182.178.90]
5 16 ms 16 ms 18 ms manc-bb-1a-ae11-0.network.virginmedia.net [213.105.159.85]
6 84 ms 74 ms 26 ms brnt-bb-1b-ae1-0.network.virginmedia.net [212.43.163.86]
7 23 ms 24 ms 30 ms brnt-tmr-1-ae5-0.network.virginmedia.net [213.105.159.50]
8 25 ms 28 ms 27 ms telc-ic-1-as0-0.network.virginmedia.net [62.253.185.74]
9 33 ms 27 ms 24 ms linx-gw1.thdo.ncuk.net [195.66.226.240]
10 24 ms 28 ms 55 ms gi0-24-10-star1.core-rs2.thdo.ncuk.net [80.249.97.9]
11 30 ms 26 ms 28 ms pingbox1.thinkbroadband.com [80.249.99.164]
Trace complete.
C:\Users\Administrator>
---------- Post added at 00:12 ---------- Previous post was at 00:11 ----------
Quote:
Originally Posted by zekeisaszekedoes
Weird... all those packet loss patterns look nearly identical. Including mine.
|
That's because the packet loss is between VM's core network and TBB's pingbox(es). Nothing to do with the individual connections.