All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arindam Haldar <ahiam@yahoo.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Detecting Request from a proxy server
Date: Wed, 06 Mar 2002 14:42:32 +0000	[thread overview]
Message-ID: <marc-lartc-101542473909418@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101530883105272@msgid-missing>

Message: 4
Date: Tue, 5 Mar 2002 09:12:39 -0500
From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: LARTC List <lartc@mailman.ds9a.nl>
Subject: Re: [LARTC] Detecting Request from a proxy server

A "good" proxy server is usually configurable to look just like an 
original requestor.

On Tue, Mar 05, 2002 at 11:40:53AM +0530, Deepak Singhal wrote:

 > Can i somehow detect traffic which is coming from a
 > proxy/masquerading server in my lan to my linux gateway server.


Masquerading can be detected by source port unless the user has
reconfigured their machine (and only if the machine is Linux).


 > I wish to block requests coming from a proxy server in my network ie.
 > no body should be able to use a proxy server in my network.


May I ask why?
-- Michael T. Babcock CTO, FibreSpeed Ltd. (Hosting, Security, 
Consultation, Database, etc) http://www.fibrespeed.net/~mbabcock/



havent used anytime but iplimit might help ???


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2002-03-06 14:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-05  6:22 [LARTC] Detecting Request from a proxy server Deepak Singhal
2002-03-05 11:32 ` bert hubert
2002-03-05 12:47 ` Milan Pavlovic
2002-03-05 14:12 ` Michael T. Babcock
2002-03-06 14:42 ` Arindam Haldar [this message]
2002-03-07  5:48 ` Deepak Singhal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-101542473909418@msgid-missing \
    --to=ahiam@yahoo.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.