From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] restricting MAC or IPs using IPTABLES in Linux 7.3
Date: Fri, 27 Dec 2002 15:12:36 +0000 [thread overview]
Message-ID: <marc-lartc-104100220716743@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104099495212424@msgid-missing>
Shaheen,
You will probably be able to take some instructive hints from the LARTC
Squid cookbook example, even if you are not going to do exactly as the
recipe suggests.
http://lartc.org/howto/lartc.cookbook.squid.html
This brief post should be a start for you:
http://mailman.ds9a.nl/pipermail/lartc/2001q2/001275.html
And don't forget to search the archives for the MAC address topics related
to your question:
http://www.google.com/search?q=site%3Amailman.ds9a.nl+mac+iptables
Good luck,
-Martin
: RH Linux 7.3, 2.4 Kernel
:
: I am trying to force all of my LAN users to go through a SQUID (2.4Stable1) proxy I have setup. And I thought I would be able to use iptables to deny services to all asking for PORT 80 or 8080 for web browsing. They should be using SQUID (certain IP, certain port # given) for that.
:
: For all other ports, I would only allow certain IP addresses or certain MAC addresses to go through.
:
: 1. Can I force (allowable MAC or IPs) to use proxy (SQUID) for web browsing?
: 2. For non-web browsing activities, can I also restrict non-allowed MAC or IPs?
:
: Please give me or point me towards some specific examples on these two tasks if you would. Thanks
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-12-27 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 13:13 [LARTC] restricting MAC or IPs using IPTABLES in Linux 7.3 Shaheen Hossain
2002-12-27 15:12 ` Martin A. Brown [this message]
2002-12-28 4:45 ` 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-104100220716743@msgid-missing \
--to=mabrown-lartc@securepipe.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox