netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: Julian Anastasov <ja@ssi.bg>
Cc: Donald Becker <becker@scyld.com>,
	Ben Greear <greearb@candelatech.com>,
	Jeff Garzik <jgarzik@pobox.com>,
	Alexandre Cassen <Alexandre.Cassen@wanadoo.fr>,
	"" <netdev@oss.sgi.com>
Subject: Re: SIOCADDMULTI for unicast broken
Date: Sat, 4 Jan 2003 14:04:17 -0500 (EST)	[thread overview]
Message-ID: <20030104135539.C48869@shell.cyberus.ca> (raw)
In-Reply-To: <Pine.LNX.4.44.0301042016020.863-100000@u.domain.uli>



On Sat, 4 Jan 2003, Julian Anastasov wrote:

>
> 	Hello,
>
> On Sat, 4 Jan 2003, jamal wrote:
>
> >
> > I think hacking the ARP code to do this would be horrible - one way to do
> > it is write a tc module that mungles outgoing ARPs to substitute the src
> > MAC address based on src IP.
>
> 	You can do it with arptables (still not sure how) or with

I havent seen user-space arptables around.

> arprules+iparp:
>
> # send all our requests from VRIP with VMAC
> ip arp add table output from 1.2.3.4 llsrc 00:00:5E:00:01:10
>
> http://www.ssi.bg/~ja/#iparp

I like this concept. This + the patch i posted should resolve the problem
of getting multiple VRIDs on a single interface.
[Although you could do it in a lot less code, maybe 50%, using
some of the tc filter extensions i am working on; also a lot less code
than arptables]

>
> 	But this is not enough for VRRP. For Linux we need a
> way to bind VRIPs to source VMACs or sort of this. I'm cc-ing to Alexandre
> Cassen as he is working on VRRP (http://keepalived.sourceforge.net/).
> I hope he can shed some light on the VRRP needs.
>

I guess there is more than one VRRP implementation on Linux; the one i
played with is from some crazy Frenchman named Jerome Ettiene;->
With two conecpts being addressed i.e patch like that you have +
the patch i posted i dont see any orther reason VRRP to be hindered.

cheers,
jamal

  reply	other threads:[~2003-01-04 19:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03 21:46 SIOCADDMULTI for unicast broken jamal
2003-01-04  0:07 ` Donald Becker
2003-01-04  1:18 ` Jeff Garzik
2003-01-04  1:39   ` Donald Becker
2003-01-04  1:45     ` Ben Greear
2003-01-04  1:52       ` Jeff Garzik
2003-01-06 15:00         ` Krzysztof Halasa
2003-01-04  2:18       ` Donald Becker
2003-01-04  4:11         ` jamal
2003-01-04  6:33           ` Donald Becker
2003-01-04 17:41             ` jamal
2003-01-04 18:24               ` Donald Becker
2003-01-04 18:55                 ` jamal
2003-01-04 18:36               ` Julian Anastasov
2003-01-04 19:04                 ` jamal [this message]
2003-01-05 11:45                   ` Julian Anastasov
2003-01-06 13:44                     ` jamal
2003-01-06 15:00                       ` Julian Anastasov
2003-01-06 17:23                         ` jamal
2003-01-04  7:32           ` Jeff Garzik
2003-01-04 17:43             ` jamal

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=20030104135539.C48869@shell.cyberus.ca \
    --to=hadi@cyberus.ca \
    --cc=Alexandre.Cassen@wanadoo.fr \
    --cc=becker@scyld.com \
    --cc=greearb@candelatech.com \
    --cc=ja@ssi.bg \
    --cc=jgarzik@pobox.com \
    --cc=netdev@oss.sgi.com \
    /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;
as well as URLs for NNTP newsgroup(s).