Alright, I _THOUGHT_ I had it setup where I could access both SSH and luci from WAN, but evidently I was wrong...
Here's how I tested it. I set the WAN port with a static address (192.168.20.1) and set my machine up with a static address (192.168.20.100) and plugged my machine into the WAN port. I wasn't able to connect through HTTP, but I was able to SSH into the router. So then I took the router to work, set the WAN port for DHCP, and plugged it into the network. It got an address of 192.168.1.40. From my workstation, I was able to connect to the router with SSH, but still no HTTP. With the router disconnected from any WAN, I plugged my machine into one of the LAN ports, got a DHCP address from the router and was able to connect to it with SSH from both the internal address (192.168.77.9) and the external WAN address it was still holding onto from the previous test (192.168.1.40). I was also able to access the HTTP side with the internal address, but not the external. Last night, I hooked this router up to my DSL at home and was unable to connect with SSH or HTTP from the external address. (It should be noted that I have made no changes to the settings in the router, aside from setting the WAN address to static and back to DHCP today.) The router I'm using right now is presently setup to forward requests on port 1221 to port 22 of my linux server. Given that THAT is working, I don't believe my DSL gateway is blocking the traffic. (I changed the default SSH port on the router to 1221 rather than 22 and I'm able to connect on that port here at work while I'm testing it.) So I was thinking I need to setup a firewall rule to forward requests from port 80 to the router's internal IP address, but that doesn't work, either. Can anyone suggest what I'm doing wrong here? I'll gladly supply more info as needed.
