Topic: e-smith-manager

[wolf]

When I try to access e-smith-manager from outside of my local domain, it redirects me to 192.168.1.1, and I cannot log on.  It works perfectly from any machine on my local network.  But when I try to access from anywhere else, it doesnt work.  Is this a feature or did I miss something? If it is a feature, can it be dissabled?
 
Jack Wolf

[zac]

hi,

this is actually a security feature - it prevents people outside your network trying to 'crack' in and change settings. it is possible for you to change this - do a search in the forums will no doubt give the answer, however i'm pretty sure it's a matter of changing the apache configuration file.

a better way of doing this is using telnet (e-smith 4.0) or ssh (e-smith 4.1 or 4.0 with the relevant patches installed) to log in and using the text browser 'lynx' to change settings to your hearts content.

i would recommend using ssh - telnet is horribly insecure.

zac

[Darrell May]

zac wrote:
<..>
> a better way of doing this is using telnet (e-smith 4.0) or
> ssh (e-smith 4.1 or 4.0 with the relevant patches installed)
> to log in and using the text browser 'lynx' to change
> settings to your hearts content.
>
> i would recommend using ssh - telnet is horribly insecure.
>
> zac

Even better is to create an SSH tunnel and access the e-smith-manager over the remote tunnel.  Visit http://netsourced.com/e-smith/howto-mindterm.html as just one of many possible solutions.

Darrell

[Paul Miller]

Hi Darrell,

What exactly does the mindterm tunnel provide?  After reading your instructions at http://netsourced.com/e-smith/howto-mindterm.html I jumped to the conclusion you had come up with a way to access e-smith-manager using a browser such as Netscape or Explorer from the internet side. It would be as if I were on the local network.  

However, I got confused by the last line which reads.

" Note:  You can not create a tunnel via the web interface to access the e-smith-manager web admin however by logging in as admin you can access the text based version from the Control Console."

Darrell May wrote:
> Even better is to create an SSH tunnel and access the
> e-smith-manager over the remote tunnel.  Visit
> http://netsourced.com/e-smith/howto-mindterm.html as just one
> of many possible solutions.

Does your method allow for the use of Netscape or Explorer from the internet?

Many Thanks,
Paul Miller

[Boris]

You can login via ssh using SecureCRT, or SSH Secure Shell Client 2.4.0 (I am not aware of others) and do port forwarding/tunneling from 192.168.1.1 to 127.0.0.1 (lolachost). Once you logged in via SSH you can use Netscape/IE pointing it to http://127.0.0.1:980/e-smith-manager
all communications will still going through ssh encrypted tunnel and secure.

[Paul Miller]

That is what I expected. But I was't quite sure.

Boris wrote:
>
> You can login via ssh using SecureCRT, or SSH Secure Shell
> Client 2.4.0 (I am not aware of others) and do port
> forwarding/tunneling from 192.168.1.1 to 127.0.0.1
> (lolachost). Once you logged in via SSH you can use
> Netscape/IE pointing it to http://127.0.0.1:980/e-smith-manager
> all communications will still going through ssh encrypted
> tunnel and secure.

I get confused by experts in the *nix community.  For believers who are already sure of a fact or a pattern, an assertion is enough.  For newbies, thorough explanation can be as important, particularly when the context is new.  And for the first three readings, I suspect the slower among us are newbies on a particular subject.

Thanks for the clarification Boris.  

Paul Miller

[Boris]

Sorry if too short and confusing. I still can help, if you willing to try, and hold your hand step by step.

[Paul Miller]

I will try on my own.  
ThanksBoris wrote:
>
> Sorry if too short and confusing. I still can help, if you
> willing to try, and hold your hand step by step.

Just wanted to be assured that the end game was to do remote admin via GUI web browser.

Regards,
Paul Miller

[Boris]

Done it for number of clients. End result is - using Windows based SSH client to connect and then, Netscape or IE to manage from Internet while maintaining secure connections at all the time.

[Paul Miller]

Thanks Boris
Boris wrote:
>
> Done it for number of clients. End result is - using Windows
> based SSH client to connect and then, Netscape or IE to
> manage from Internet while maintaining secure connections at
> all the time.
Regards
Paul