Well, I'm back up online here at home this morning, but the headache continues.
This is one of those situations where you do a half dozen things to fix a problem, and when it gets fixed you aren't sure which of the things you did actually fixed it.
But while I'm back up online, my IP address has changed! While I have "basic" DSL service in which I nominally have a dynamic IP address, it has been the same for over two years. All of a sudden I have problems, and now I have a new IP address. While they will not admit it, I suspect that the swbell had problems with the DHCP server that serves my node, and that my problems are related to this. A hypothetical scenario: the DHCP server goes down; my lease comes up for renewal, and instead of it renewing with the same IP address, I get nothing; finally the DHCP server comes back online, I reconnect for a new lease, and someone else now has my old ip, so I get a new one. Whatever, it means that all my seti service installs at school are pointing to the wrong ip address now, and will have to be reinstalled. What a pain!
Plus, in trying to rule out problems on my end, I removed my home lan and router, so now I have to rebuild that configuration all over. Well, if that goes smoothly, it should only be a few minutes of work. That will get home herd back in production. Getting the school herd back into full production will depend on how much time I can find over the next few days. Which may not be a lot. Next week looks good, so maybe I can get it done then.
-baz