From: Jandre Olivier <jandre@megaserve.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Allowing certain IP to browse
Date: Thu, 19 Jan 2006 12:18:24 +0000 [thread overview]
Message-ID: <43CF8390.20600@megaserve.net> (raw)
In-Reply-To: <1247.192.168.35.14.1137669461.squirrel@webmail.satconet.com>
howdy,
iptables will help u here for starters
/sbin/iptables -A FORWARD -s 192.168.x.2/32 -p tcp --dport 80 -j ACCEPT
/sbin/iptables -A FORWARD -s 192.168.x.2/32 -p tcp --dport 25 -j ACCEPT
/sbin/iptables -A FORWARD -s 192.168.x.2/32 -j DROP
similiar setup for the rest, this is not very clean though, might want
to create subnets for each network and put them in seperate network
cards in your linux box to physicly segment the networks, then you have
control
Lata
J
andrew.goodluck@intafrica.com wrote:
> Hi all,
> Need your input of the following:
> I have a linux box(firewall)
> -I want to restric some users not to browse but send emails only
> Example: 192.168.x.2 up to 192.168.X.45 to send emails and browse, while
> the rest(192.168.X.46 to 192.168.X.254) to send emails only. How do I do
> that?
> thanx
> Andy
>
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
--
/*---------------------------------------------------------------------*/
__ _
---------- / / (_)__ __ ____ __ ---------
------- / /__/ / _ \/ // /\ \/ / --------
---- /____/_/_//_/\_,_/ /_/\_\ ------
localhost@localdomain.za.net
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-01-19 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 11:17 [LARTC] Allowing certain IP to browse andrew.goodluck
2006-01-19 12:18 ` Jandre Olivier [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=43CF8390.20600@megaserve.net \
--to=jandre@megaserve.net \
--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.