OK, after lots of suffering, samoht.com is back up (obviously it is, or you wouldn't be reading this). The problem turned out to be that I suck. Well, not so much that, but that I'm not a network heavy. Anyway, I finally stopped thinking about how to configure my network, and just followed the instructions for each component (imagine that - just following instructions). I followed Qwest's instructions for the Cisco 678, and Linksys' instructions for the Wireless-G. I gave the Wireless-G one of the static IPs from my account, and did the DNS request for that IP. The next morning I could see samoht.com from my home network. However, no one else could see it.

I puzzled over this for a couple of days. Then it hit me - I had never finished configuring buzz (my Sun Ultra 1, which is my web server) for my new setup. I'd given up in frustration a few days ago when I couldn't figure out how to set up the networking in Solaris (it had been too long since my last Solaris networking config). The reason I could see samoht.com from inside and not outside is that buzz and apache were running, but buzz didn't know about the gateway. Therefore, from any client other than buzz, I could do an HTTP request to samoht.com, which would be resolved to my IP address and end up at buzz. Buzz would answer the request, which would be locally routed (I think). So, I could browse samoht.com inside, but not out.

So, with this bit of reasoning in mind, I thought to look at my old computing weblog 'This Old Sparc for hints on how to proceed with getting buzz on-line. Sure enough I'd documented the steps. Within an hour, samoht.com was really up.