Quote:
|
Originally Posted by Pem
At a guess I would say that is probably your ubr's default gateway private address - and the traffic is genuine local broadcast packets.  Try pinging it - if you can that would be futher evidence that this is, in fact, the explanation.
Edit : even better - do a tracert to cableforum.co.uk and see if this address is one of the first hops. |
OK here's the tracert detail (below) and, as you say, the 173 address is the first hop... what I don't understand is why it's showing up on the Syquest traffic log all the time, especially as it's only been happening over the past month or so.
Ken
>>
Tracing route to cableforum.co.uk [66.199.235.18]
over a maximum of 30 hops:
1 27 ms 14 ms 14 ms 172.31.55.254
2 14 ms 27 ms <10 ms renf-t2cam1-a-v111.inet.ntl.com [80.4.64.
3 14 ms 13 ms 14 ms renf-t2core-a-ge-wan61.inet.ntl.com [62.2
57]
4 14 ms 14 ms 13 ms ren-bb-a-so-200-0.inet.ntl.com [62.253.18
5 <10 ms 13 ms 28 ms ren-bb-b-ae0-0.inet.ntl.com [62.253.185.1
6 14 ms 28 ms 13 ms man-bb-a-so-600-0.inet.ntl.com [62.253.18
7 28 ms 41 ms 28 ms ycr2-so-3-0-0.Manchester.cw.net [208.175.
8 27 ms 28 ms 27 ms bcr2-so-3-0-0.Thamesside.cw.net [166.63.2
9 96 ms 110 ms 137 ms dcr1.nyk.cw.net [195.2.1.3]
10 96 ms 110 ms 96 ms so-0-0-0-ecr1.nyk.cw.net [195.2.3.14]
11 96 ms 96 ms 96 ms nyiix.ezzi.net [198.32.160.106]
12 110 ms 96 ms 96 ms 65.125.239.41
13 110 ms 96 ms 97 ms 65.125.239.129
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * *
<<