RE: Denying TCP connections based on IP

Hmmm I don't suppose either of you have ever entered a packet rule that
disallows access from a LAN Console by any chance ?

If I had to guess I'd say you couldn't do this (or more accurately that it
would have no effect) due to LAN console running at a lower TCP level but
I'm kind of curious as to whether my guess is accurate or not.

Regards
Evan Harris

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Tom Liotta
Sent: Tuesday, 10 July 2007 3:29 p.m.
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Denying TCP connections based on IP

Larry Bolhuis wrote:

But remember the 'Foghorn Leghorn' ("Fortunately I keep my feathers
numbered for just such an Emergency!") command: RMVTCPTBL *ALL..

This

is entered on the console when you activate a packet rule that
disconnects all your iNav functions so that you can't fix them! The
command doesn't delete them simply de-activates them so you can get
back in and fix them. Don't ask how I know this command. :-)

Heh, I have no need to ask how you know; I have my own reason for
thinking that I know how. But I love the name of the rule.

I often go so far as to schedule the command to run maybe 3-5 minutes
in the future. I've sometimes set the delay via a job scheduler entry
and sometimes through a simple SBMJOB -- if I can't get back quickly
enough to prevent it from running, I save myself from having to get
back quickly enough.

Tom Liotta