First, are the two rules structured like:

Accept notice "PROTECTED" TCP from ANY_IP to PROTECTED 443

Accept notice ANY TCP from ANY_IP to ANY_IP 77


Second, how high up the list of rules are these? Is there a possibility
that these rules are being superseded by a lower numbered rule?

Third, just for the hell of it, have you tried remote admin from the DMZ
or EXT interfaces? I know this is a long long long long shot...but its
worth a try!

Christopher

> -----Original Message-----
> From: Scheldebouw [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 09, 2005 04:39
> To: [email protected]
> Subject: [gb-users] Unable to manage via GBAdmin or HTTPS
>
> Hi,
>
> I have an Robox that I was used to be able to manage via GBAdmin and
HTTPS
> via the internal network. Somehow I screwed up the config and this is
not
> possible anymore. I also am unable to ping the internal network
interface
> address. But the Robox is working perfectly in every other way!
> I am able to manage it via the serial interface and I can see that I
have
> a
> remote access rule in place (top rule) to allow access from the
protected
> network to ports 77 and 443 TCP on the internal interface.
> If I look at the log I can see a block when trying GBADmin or HTTPS
access
> but the display in the terminal is not long enough to show the full
line
> (vt100).
>
> What's the best way to solve this? Would an other terminal emulation
> version allow me to see the complete error log? Or can I export the
config
> and / or the error log somehow to check it?
>
> Thanks.
>
> ------------------------------------------------------
> To unsubscribe:           [EMAIL PROTECTED]
> For additional commands:         [EMAIL PROTECTED]
> Archive:  http://archives.gnatbox.com/gb-users/

------------------------------------------------------
To unsubscribe:           [EMAIL PROTECTED]
For additional commands:         [EMAIL PROTECTED]
Archive:  http://archives.gnatbox.com/gb-users/

Reply via email to