Public Service Announcement - network, email problems

My trusty Linux router has, apparently, been gradually dying. As of Saturday night it was basically unusable, slowing down to a crawl within minutes of a reboot. It passed memory and rootkit checks just fine, though. Sunday morning I decided to scrap it. This may have been a mistake. I tried several different approaches. The mini-ITX box I _had_ been using as my router wouldn't boot. Spent quite a while chasing my tail on that one. Finally, after much flailing, got my WAP on line as the router. Nice and fast, and of course low power. Sweet. I'd been meaning to do that for a while. Except that by then it was 4pm, and nearly time to head to the airport. (Note: I'm up in the Seattle area until Thursday afternoon; I'm available for an interview Wednesday afternoon. Hint.) A couple of things got forgotten, chief among them being testing ssh. Oops. I thought briefly about setting up port forwarding, but got distracted by things like hugging my wife and daughter goodbye. I read my email by ssh-ing in to my file server. But the ssh daemon on the router doesn't appear to be listening to the WAN port. This is an excellent security measure, but right now it sucks. The other thing I do only on the home system is keep my password database. OOPS. Fortunately, I was able to set up email forwarding this morning, so I only lose access to my archives (including a lot of job-related stuff) and anything that was sent to me yesterday. But still... It could be a painful couple of days, and it certainly made for a bad trip yesterday. Flying out of San Jose on a Delta puddle-jumper didn't help.