|
ECS-L Home Automation and Security Archives |
learn more
| view messages for this
month | NetBloc® | terms of use | search
subject (prev) or (next) |
time (prev) or (next) |
author (prev) or (next) |
view more subjects
Subject: From: Date: | Re: [ECS] web interface and firewalls Ingo Pakleppa Thu, 29 Jun 2000 12:06:54 -0700 |
Unfortunately, I don't have a solution - what I suggested would only work
the other way round, when ECS is directly on the Internet and the browser
is behind a NAT. In that case, it should work right out of the box. That
is, unless the protocol uses connections back from the client to the server
(I don't recall if that happens. Mark?)
Ingo
At 06:02 AM 6/28/00 -0700, Don wrote:
>Ingo:
>
>Could you elaborate on your reply? I have a router that uses NAT and my ISP
>uses NAT. How would you suggest I set up my remote browser to access ECS
>through these two NATs?
>
>Thanks:
>
>Don
>
>----- Original Message -----
>From: "Ingo Pakleppa" <ipakleppa@home.com>
>To: <ecs-list@netbloc.com>; <ecs-list@netbloc.com>
>Sent: Tuesday, June 27, 2000 8:43 PM
>Subject: Re: [ECS] web interface and firewalls
>
>
> >
> > If you mean the second, it shouldn't be a problem with the two main
> > firewall mechanisms I am familiar with. It wouldn't ever be a problem with
> > NAT (or "masquerading") firewalls because they will simply forward the
> > request regardless of port. Normally, a proxy-type firewall won't be a
> > problem, either, because it will look at the protocol identifier (http:)
> > rather than the port number. I don't know enough about stateful
>inspection,
> > but I doubt it would be a problem there, either.
subject (prev) or (next) |
time (prev) or (next) |
author (prev) or (next) |
view more subjects