That makes sense. I'll try it out.
Thanks,
Drew
--- Bob Glover <[EMAIL PROTECTED]> wrote:
> Drew,
>
> I've seen this before. The fault here is probably a
> web site designed
> by someone who didn't realize that many people are
> behind some kind of
> firewall. It looks to me like you were br
Drew,
I've seen this before. The fault here is probably a web site designed
by someone who didn't realize that many people are behind some kind of
firewall. It looks to me like you were browsing from a MASQ'ed box (as
evidenced by the high source port numbers: 63508, etc.), when you hit a
websi
On Fri, 2 Feb 2001, Drew Hunt wrote:
> Would this do the trick?
>
> ipchains -A input -i $LAN_INTERFACE_1 -s $LAN_1 -d $ANYWHERE 81 -j REJECT -l
>
> Drew
>
It should work fine. Then if this happens again, you will know what
machine is doing it.
Mikkel
--
Do not meddle in the affairs of
: Interesting log
On Fri, 2 Feb 2001, Drew Hunt wrote:
> Actually port 81 is already blocked on the input side. All ports are
> blocked by default unless the masq is expecting them (say, an FTP
> connection). All tcp rules for allowed ports have the ! -y option on
them.
>
I should ha
On Fri, 2 Feb 2001, Drew Hunt wrote:
> Actually port 81 is already blocked on the input side. All ports are
> blocked by default unless the masq is expecting them (say, an FTP
> connection). All tcp rules for allowed ports have the ! -y option on them.
>
I should have been more specific - I men
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Mikkel L. Ellertson
Sent: Friday, February 02, 2001 6:38 PM
To: RedHat general mailling list
Subject: Re: Interesting log
On Fri, 2 Feb 2001, Drew Hunt wrote:
> I found these logs blocking outgoing pack
On Fri, 2 Feb 2001, Drew Hunt wrote:
> I found these logs blocking outgoing packets. Whois tells me this IP
> belongs to RackSpace in San Antonio, TX. What's weird is that I woke up at
> midnight to find my Windoze computer, that had been turned off for the
> night, on and waiting for my passwo
I found these logs blocking outgoing packets. Whois tells me this IP
belongs to RackSpace in San Antonio, TX. What's weird is that I woke up at
midnight to find my Windoze computer, that had been turned off for the
night, on and waiting for my password. Would the Wake-On-LAN feature be
causing
