All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Gallati <lartc@draxinusom.ch>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] block ethernet IPv4 traffic
Date: Mon, 19 Jul 2004 13:27:04 +0000	[thread overview]
Message-ID: <40FBCC28.5020600@draxinusom.ch> (raw)
In-Reply-To: <39685.217.79.71.234.1090239494.squirrel@217.79.71.234>

Lawrence MacIntyre wrote:

> This will work as long as none of the clients are clued enough to add 
> host routes or alias addresses.

Yes, I assumed he were the admin of the site in question. If the clients 
have full control over their systems then this is a no-go.

Some linux boxes with bridges and bridge_filter might do the trick but 
he'd need to put one of those basically in front of each switch port.

I don't see an easy way to solve the problem.

> 
> Rene Gallati wrote:
> 
>> Anton Glinkov wrote:
>>
>>> On Mon, July 19, 2004 15:25, Ed Wildgoose said:
>>>
>>>>
>>>>> the bridge thing is not possible.. the network is too big.. 300
>>>>> machines..
>>>>> with over 30 switches (only one of them is manageable) :(
>>>>> Basically I want to deny ethertype 0800 (IPv4) packets for that LAN.
>>>>> The only solution I thought of was to have a linux machine in this LAN
>>>>> that has all the possible IP addresses set on its interface.
>>>>>
>>>>>
>>>>
>>>> Look, we can't help you until you explain the problem
>>>>
>>>> WHY is it not possible to have a bridge?  This only requires two 
>>>> network
>>>> cards?
>>>
>>>
>>>
>>>
>>> I want to block the traffic between _ANY_ 2 of the machines in the 
>>> network.
>>
>>
>>
>> How about giving them a netmask of /32 instead of /24 (or whatever you 
>> have) so that they only see themselves in the same network and then 
>> giving them a static route to the default gw (since it is outside of 
>> the /32).
>>
>> Then you can block all inter-client traffic at that single default 
>> gateway (or one hop "in front" of it, seen from the clients)
>>
>>
> 

-- 

C U

      - -- ---- ----- -----/\/  René Gallati  \/\---- ----- --- -- -
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-07-19 13:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-19 12:18 [LARTC] block ethernet IPv4 traffic Anton Glinkov
2004-07-19 12:25 ` Ed Wildgoose
2004-07-19 12:33 ` Anton Glinkov
2004-07-19 12:52 ` Rene Gallati
2004-07-19 12:58 ` Anton Glinkov
2004-07-19 13:03 ` Lawrence MacIntyre
2004-07-19 13:26 ` Rene Gallati
2004-07-19 13:27 ` Rene Gallati [this message]
2004-07-19 15:43 ` Ed Wildgoose
2004-07-19 17:17 ` Paul

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=40FBCC28.5020600@draxinusom.ch \
    --to=lartc@draxinusom.ch \
    --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.