Config Change Kills Router (DHCP Issue?) I'm not sure how to even go about troubleshooting this issue, but it's happened to me in Tomato 1.07 and now in 1.10. I have remote SSH access enabled on my WRTGS 1.1 and use it is a proxy server from work. I connect to the administration pages by using the router's LAN IP on the remote machine. Whenever I make a change on the remote access page of the Administration section and save it, the connection is lost and the router gets a new IP address from Verizon DSL. The IP looks good (something like 71.x.x.x, which is Verizon's IP space), but I have no connectivity any more. As long as I have this IP address I cannot connect to anything on the WAN (in or out). I have to power down the router in order to correct it. The first time this happened to me I wrote it off as some fluke, but it happened to me again this morning. I don't think it's a case of just accidentally getting a bad IP from the Verizon DHCP server because Tomato renews the DHCP lease every two hours for months on end without issue. The problem only occurs when saving changes on the remote access page of the Administration section. Any ideas on tracking down this issue? I'm at work now so I've lost all contact with the router ... again.