>I added the IP of my home machine to the "local network" list >under remote administration. This allowed me to authenticate >myself from that machine on port 980, but I can't get much >further, because there is no menu on the left-hand side. http >source shows that the menu frame has ip addresses of the >internal network (e.g. 192.168.0.1), not names like >e-smith.mydomain.com, and those obviously are not accessible >from outside.
Please don't do this. The local networks is meant to be for *local* networks. You're opening up a whole can of security worms by making an external ip *local*.
>It's quite clear that I'm doing something wrong, but what is it? >How do I allow e-smith management from a specific outside IP >address? Can it be done with SSL to avoid snoopers? Should I
>use ssh? Please help me out!
Yes. Use ssh. Actually, better yet, use e-smith 4.1 which was released on Monday: it already has ssh built in. Plus the manager is built into the console menu (in lynx format). Once you learn ssh, you can also learn about port forwarding and therefore allow yourself to see the e-smith manager as if you were right there on site. Additional remote administration could also be achieved with the PPTP VPN settings also available in 4.1
>For now, I work around by enabling local telnet access and >running text-mode browser after logging in as admin, but I'm >sure this is not the way it was intended...
It somewhat is, except the telnet part. We don't like telnet, so we added ssh ability to the remote connections settings in the manager. During testing of 4.1 we found the text-mode browser to be highly useful (since it is right there on the menu).
Jason