From: "deepak singhal" <singhal@techie.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] restricting MAC or IPs using IPTABLES in Linux 7.3
Date: Sat, 28 Dec 2002 04:45:55 +0000 [thread overview]
Message-ID: <marc-lartc-104105087013685@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104099495212424@msgid-missing>
<P>This can be achieved with a combination of souce based routing ( Source IP and MAC based) with combination of iptables rules.</P>
<P>Deepak Singhal<BR><BR>----- Original Message -----<BR>From: "Shaheen Hossain" <SHAHEEN@O2OSOFT.COM><BR>Date: Fri, 27 Dec 2002 19:13:45 +0600 <BR>To: <LARTC@MAILMAN.DS9A.NL><BR>Subject: [LARTC] restricting MAC or IPs using IPTABLES in Linux 7.3<BR><BR></P>
<META content="MSHTML 6.00.2800.1106" name=GENERATOR>
<STYLE></STYLE>
<DIV><FONT face=Arial size=2>
<DIV><FONT face=Arial size=2>RH Linux 7.3, 2.4 Kernel</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>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. </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>For all other ports, I would only allow certain IP addresses or certain MAC addresses to go through.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>1. Can I force (allowable MAC or IPs) to use proxy (SQUID) for web browsing?</FONT></DIV>
<DIV><FONT face=Arial size=2>2. For non-web browsing activities, can I also restrict non-allowed MAC or IPs?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Please give me or point me towards some specific examples on these two tasks if you would. Thanks</FONT></DIV></FONT></DIV>
--
<p>_______________________________________________<br>
Sign-up for your own FREE Personalized E-mail at <a href="http://www.mail.com/?sr=signup" target="_new"><font color="#0000FF"> Mail.com</font></a><br><br>
<a href="http://corp.mail.com/lavalife" target="_blank">Meet Singles</a>
</p>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-12-28 4:45 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
2002-12-28 4:45 ` deepak singhal [this message]
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-104105087013685@msgid-missing \
--to=singhal@techie.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