Why anyone would want to expose an unencrypted management GUI to the
outside world is completely beyond me; especially not knowing why it
wasn't accessible.
Scott Ullrich wrote:
Add a rule to allow traffic to port 80 on the WAN.
On 12/30/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Ok, I can ping the interface, I am just not getting the web
interface to come up
K.
On Fri, Dec 30, 2005 at 03:50:35PM -0500, Scott Ullrich wrote:
Add rules allowing ICMP to WAN interface.
On 12/30/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Internally if I ping my external interface, it pings just
fine. If I go to an external network and attempt to ping the
WAN interface, it fails... The same is true of my virtual
interface. I am wondering if I should be NATing something,
or if there is a rule that I didn't add. Also this is true
of ssh, webinterface, etc.
K.
On Fri, Dec 30, 2005 at 03:35:49PM -0500, Scott Ullrich wrote:
What do you mean access the interface externally? SSH, webConfigurator?
On 12/30/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I just installed 1.0beta... I am able to see the access and
see the WAN interface within the LAN, but I am not able to
access the interfaces externally. What rule did I forget to
add. My virtual interface is not viewable from the outside
world either...
K.
