Originally posted by: drag
You'd generally go like this:
http://192.168.0.104:1000/
It could be that it's running with encryption-only and maybe in that case you can try:
<a target=_blank class=ftalternatingbarlinklarge href="https://192.168.0.104:1000/"><a target=_blank class=ftalternatingbarlinklarge href="https://192.168.0.104:1000/">https://192.168.0.104:1000/</a></a>
What may be happenning is that webmin is setup to run on 127.0.0.1 (localhost) only. That way it's inaccessable from the outside world. It'll have to be reconfigured slightly to listen on a network port.
You can find out network ports are open and what they are listening to by using this command:
netstat -ap --tcp --udp
Stuff that is listenning to *:* on the foriegn address and *:ssh or *:1000 or whatnot on the local address is listenning on all network ports and should be accessable remotely provided you don't have a firewal blocking them.
(with port numbers they will provide a name (like ssh or bootp) in substitution for the actual port number. The /etc/services file is what Linux will use to find out the names of services. If you don't like that you can run netstat -apn --tcp --udp and disable name resolution, this can make it easier to read)
Using that you will be able to tell if webmin is running and what port and network it's listenning on.
If your using the command line only over ssh there are more then a few handy dandy text-based browsers out there you can use.
Text-based browsers may sound like a throw-back, but generally they work. This is because most web designers have to take into effect the use of blind individuals using their websites and those people will have a very hard time with lots of images or 'ajax'-only style websites. Any good website should have good text fall-back. (if you do your CSS and such properly it will translate very well to text-only) Well when trying to access webmin locally you can use one of these text-only browsers to do so.
So some text browsers to try are things like links, elinks, w3m, and lynx. W3m is installed by default a lot of times and for a long time I used Lynx a lot. Links and it's varients like elinks elinks2 and such support javascripting, frames, and other mostly modern features and on slow machines they are very cool because some versions will support images and such. All of this stuff should be aviable via apt-get.
Also another thing to think about is if Webmin is listenning to localhost only you can use port forwarding techniques of ssh to forward a port to your own localhost. This way you don't have to open up webmin to the entire world.
There are two types of forwarding that ssh supports. Local forwarding and remote forwarding. I don't know if OS X supports this, but I bet it does. Also some types of ssh clients can support this techique in Windows (with more limitations, of course)
http://www.ssh.com/support/doc...2/Port_Forwarding.html
So if Webmin is listenning to localhost:1000 only then you can go:
ssh -L 6000:localhost:1000 192.168.0.104
You run that command and it will open up a shell on your remote server like normal.
Then you can open up your browser and point it at
http://localhost:6000/ and it should be forwarded to localhost:1000 on the remote site.
Also you can use this to access stuff behind firewalls. It's very handy thing to know. For example I've used remote forwarding to allow myself to penetrate NAT firewalls and securely access services running behind them. Is very nice thing to be able to do since it does not require reconfiguring the firewalls or doing port forwarding like you normally need to do to get past a firewall.
So there are a veriety of things you can do...
The most important thing is to use netstat and make sure that you know webmin is running and find out what port it's listening on and what network you can access it from. That way your not going to bang your head against bad or misleading documentation or trying to access a webmin server that isn't running.
You can also use nmap on your client side to do port scanning and find out what services are running on your server. Nmap is very kick-ass. Also OS X has a not-so-nice GUI application for doing port scanning and such. Should be in your utilties folder or something like that, or maybe in the control panel under networking stuff. I don't remember so much.
Facebook
Twitter