Voytek Eymont wrote:
so what's the best way to have controlled access from dynamic IP ?
Perhaps is it better not to bother with access control but to
use authentication and authorisation.
If you persist with access control you just end up with some
VPN/tunnelling insanity as opposed to
On 12/06/2008, at 7:11 AM, Voytek Eymont wrote:
but, 'http://localhost:' opens the 'real' host's default 'this is
apache' page, (and, '/cacti/' won't work from there); howe can I
get to
vhost page where '/cacti/' is setup ?
I've tried using real.host: and v.host: so far with no
On 11/06/2008, at 11:26 AM, Voytek Eymont wrote:
Michael,
thanks. I'll start looking into that, does it require any setup at
sshd
end, or is it all at client end ?
There might be a sshd_config setting to enable port forwarding,
but it has always been enabled by default on my systems.
On Wed, June 11, 2008 10:49 pm, Michael Chesterton wrote:
On 11/06/2008, at 11:26 AM, Voytek Eymont wrote:
There might be a sshd_config setting to enable port forwarding,
but it has always been enabled by default on my systems.
ssh -L :localhost:80 somehost.dyndns.org
or edit
On Thu, Jun 12, 2008, Voytek Eymont wrote:
but, 'http://localhost:' opens the 'real' host's default 'this is
apache' page, (and, '/cacti/' won't work from there); howe can I get to
vhost page where '/cacti/' is setup ?
I've tried using real.host: and v.host: so far with no
Mary Gardiner wrote:
The web server wants the browser to send a request for the correct host
name. One way to get it to do this is to alter your steps:
or you could just change your hosts file to 'poison' real.host.com to
point to 127.0.0.1
then your browser will make the request to the
I have in Apache cacti.conf allowed access from a home dynamic IP
that works until the home IP changes, so I set a dyndns.org host like
'home.dyndns.org', and, was hoping that I can place a FQHN instead of IP
address in cacti.conf, but this doesn't seem to be supported
'Allow from 127.0.0.1
On 10/06/2008, at 11:10 PM, Voytek Eymont wrote:
I have in Apache cacti.conf allowed access from a home dynamic IP
that works until the home IP changes, so I set a dyndns.org host like
'home.dyndns.org', and, was hoping that I can place a FQHN instead
of IP
address in cacti.conf, but this
On Wed, June 11, 2008 12:30 am, Michael Chesterton wrote:
On 10/06/2008, at 11:10 PM, Voytek Eymont wrote:
I use dyndns and ssh port forwarding. That way you configure
cacti to allow from localhost only, and you need a ssh key to login and
access it.
Michael,
thanks. I'll start looking
