[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On Fri, 12 Nov 2010, tom wrote:
On 12/11/10 12:57, Simon Waters wrote:Its a problem in the sense that the log is short and I'm missing other info - and its just picking away at the bandwidth.tom wrote:I'm getting this in my router log: -----------------------------------------------------12.11.2010 12:21:01 **LAND** 213.246.85.17, 40660->> 213.246.85.17, 80 (from ATM1 Inbound) 12.11.2010 12:20:36 **LAND** 213.246.85.17, 40660->> 213.246.85.17, 80 (from ATM1 Inbound) 12.11.2010 12:20:24 **LAND** 213.246.85.17, 40660->> 213.246.85.17, 80 (from ATM1 Inbound) 12.11.2010 12:20:18 **LAND** 213.246.85.17, 40660->> 213.246.85.17, 80 (from ATM1 Inbound)----------------------------------------------------My ISP has helpfully advised re-booting my router to make it go away. I was very surprised to discover that didnt work.What can I do here to get them to actually do something about it.Is it causing a problem? I assume if it was detected then the router is logging and ignoring.Otherwise I'd check if I'd done something that causes the problem, and if not get them to escalate it to their routing people. Since suggests they aren't following best practice somewhere.
Gosh - LAND is so last Decade! Everything ought to ignore it these days. As it has no effect on moderns systems, I don't even check for it anymore.
I'd just ignore the router logs... Gordon -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq