Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Oskar Andreasson <blueflux@koffein.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Policy based routing form SRC Mac address.
Date: Wed, 03 Oct 2001 14:12:11 +0000	[thread overview]
Message-ID: <marc-lartc-100211864818036@msgid-missing> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

If I understood your question correctly, I'd suggest you use iptables instead 
of routing etc. Set up a firewall which prohibits some traffic depending on 
MAC source while it allows others.

Ie, set up the rules which allows traffic with iptables in a way like this:

iptables -A FORWARD -s 192.168.1.0/26 -j ACCEPT
iptables -A FORWARD -s 192.168.1.64/26 -d 10.1.1.1/32 -j ACCEPT # what kind 
of access?

etc, and then set up a policy of DROP on the FORWARD chain.

For more on this, check out the howtos and tutorials etc on 
http://netfilter.samba.org/.

Have a nice day,

On Wednesday 03 October 2001 16:06, bharat merja wrote:
> Hi,
>
> Thanks to all in advance,
>
> In recent I need policy based routing on my Linux2.4.3 box. requirement is
> like to give access of Internet to some computers while this facility is
> not available to rest people (That is based on MAC address only).
>
> My existin routing in "table main" is...
>
> 192.168.1.0/26 dev eth0  proto kernel  scope link  src 192.168.1.3
> 192.168.1.64/26 dev eth1  proto kernel  scope link  src 192.168.1.65
> 192.168.2.0/24 via 192.168.1.2 dev eth0
> 127.0.0.0/8 dev lo  scope link
> default via 192.168.1.1 dev eth0
>
> Where 192.168.1.1 is ip of router, there is no restriction required on
> 192.168.1.0/26, while on 192.168.1.64/26 I need to give access to some
> computers only.
>
> I have done some work on it but not get success. I have done like
>
> #iptables -A PREROUTING -t mangle -i eth1 -m mac --mac-source
> ab:cd:ef:12:34:56 -j MARK --set-mark 1 #ip rule add fwmark 1 table John
> #ip route add unreachable default table John
>
> Then after I have tried in INPUT too.. But no success.
>
> If any one have implemented in their network Please guide me. What basic
> mistakes I am commiting in this scenario?
>
> Looking forward for kind reply from Network Gurus.
>
> Thanks and regards
> Bharat Merja.

- ----------------------------------------
Content-Type: text/html; charset="iso-8859-1"; name="Attachment: 1"
Content-Transfer-Encoding: quoted-printable
Content-Description: 
- ----------------------------------------

- -- 
 ----------------------------------- 
|Oskar Andreasson                   |
|Multisoft Education AB             |
|http://www.libendo.com             |
|phone: +46-8-6635555               |
|mailto: o.andreasson@libendo.com   |
 ----------------------------------- 
BOFH excuse #1:

clock speed
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7uxy/xO3KTTz2r/kRAl5TAKCb4nWnOzQqD0UroaZ9pZm7oReJmgCguQAt
rhVUgy8Csr2G17HaQgjtL5Q=TKAk
-----END PGP SIGNATURE-----

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

             reply	other threads:[~2001-10-03 14:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-03 14:12 Oskar Andreasson [this message]
2001-10-03 14:18 ` [LARTC] Policy based routing form SRC Mac address bharat merja

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-100211864818036@msgid-missing \
    --to=blueflux@koffein.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox