Basically, what I'm trying to do is get remote access to my home computers by forwarding the traffic through a school shell account. I allow connections from my school shell.

Shrekkie: I was thinking about doing the reverse lookup, but doesn't that put a huge overhead on the router because it has to reverse lookup EVERY ip that tries to connect to that port? I've thought about doing that in the past, but was told not to. I'm sure I was told that here. I just let it go after that point and opened up the whole netblock. But, if it would work (without too much overhead), thats a great idea.

Striek: yes, I can use ping, tracert, and netcat. I am just limited to which ports I can open connections on. However, it would seem that it the shell itself is firewalled so even if I do open a port, I can't connect to it. darn...

So, it looks like vpn is going to be the way to go. I just won't have vpn client software from every machine that I will be on. But I will have remote desktop. So, I was just going to use RDP. I know that its not encrypted... but I won't be doing anything that must be kept secret.

Ah yes. Here is the thread that I was wondering about they dynamic ACLs for practically the same issue. I guess its time for the funnel and pot of coffee... I just forgot all about the two dynamic dns addresses. One pointing to the other. That will work for this case too! Sweet! http://www.antionline.com/showthread...hreadid=261366