Can you confirm is the router physically locking up and/or dropping the connection?
Mostly it's effectively a router reboot. Not only does the connection cycle, but also the uptime of the router is reset (I track my stats with mrtg and record this info). I believe I've also seen warm restart errors in the system log (must check next time)
Connection drops are (sadly) more normal (long line, noise sources)
From a conversation Ive seen with a Thompson rep elsewhere, they suspect that uPnP may have something to do with this and suggest ensuring that UPnP is turned off in the router.
I'd heard uPNP & wireless & bittorrent were 3 theories. uPNP is enabled. With 11 wireless devices in the house, and most of these using audio/video streaming or gaming, lack of uPNP is just not an option. I also have music/video on a NAS and stream using DNLA and DAAP.
What I did do was to try some minor reconfig, such as switching ssdp max-age from 1800 down to 600.
I also banished bittorrent and closely tracked max tcp/udp connections (limit is 2048 on this router)
And I enabled connection probes
The other thing thought that also occurs is that the f/w release mentioned will be a standard firmware.. and wont be auto set up for the likes of Be/02 which requires a different configuration.
Sure -- and I am using O2 firmware -- but at least that would give 2 more reasonable options
1. consider buying a unbranded router
2. Hassle ISP (O2) for a fix
Many thanks for taking the time to reply, but looks like there's no clear answer yet.
I have toyed with the idea of enabling some of the traces (hey thomson -- tell me which ones & maybe I can catch you data), but without persistent storage and data just before the hang would likely be lost (presumably) + there's an issue with deciding what to enable. This is where the provider needs to help (I work in sw engineer & have worked with telecom systems).
