Clancy you are really hilarious... a mix beetwen Berlusconi and Mr.Bean!!

By the way I'm experiencig random reboots, and in order to be as understandable as my poor english allow to me, i used to express my uptime in weeks to explain that before the only reeboot were the ones i decide.
If you wont i can send you my config file i think that could be the best and clearest way to explain my setup to you...
Kicco, first of all I have to confess that I am not the brightest bulb on the Christmas tree in relation to other members on the board. If you would like to send me your configuration I'd be glad to have a look as soon as I figure out how to not overwrite my own settings. One of the things I have observed when people report a problem is that they tend to leave out details that might seem small to them but could mean all the difference when it comes to a diagnosis. For instance, one contributor was seeing wireless restarts in his log file but it took several tries before he off-handedly mentioned that he had a Wii on his network. This little tidbit unlocked the answer. My belief is that troubleshooting a router is a lot like troubleshooting an illness. The doctor will want to know all kinds of specifics about that person such as, diet, home life, state of mind, exercise or no exercise, other medications, past history, past family history, bank account numbers. Forget that last one. Can you tell us what devices are accessing the router, what kind of internet service you have, do you have anything in the room that could be sending out conflicting 2.4GHz signals (such as wireless telephone base stations and handsets). What, if anything, might have changed between now and when you had better success. A new wireless or wired NIC? New software, new drivers, new car, new girlfriend. OK, that's enough to chew on. If you think my suggestions are worth while, tell us all about your setup and how long have you hated your <insert relative of your choice>? (a little Freud humor. Very little)