Re: [ANALISYS] Re: multicast arp entry

2004-05-20 Thread Eugene Grosbein
> > Should I fill the PR? > You're rather supposed to submit a working patch. ;) OTOH, I'd rather wait and see how much time will it take for http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/51927 to be commited or carped. That another multicast problem is much simplier and PR contains a patch now.

Re: [ANALISYS] Re: multicast arp entry

2004-05-20 Thread Eugene Grosbein
On Thu, May 20, 2004 at 04:16:29PM +0300, Ruslan Ermilov wrote: > > Should I fill the PR? > > > You're rather supposed to submit a working patch. ;) I'm afraid I do not have enough knowledge :-( Eugene ___ [EMAIL PROTECTED] mailing list http://lists.

Re: [ANALISYS] Re: multicast arp entry

2004-05-20 Thread Ruslan Ermilov
On Thu, May 20, 2004 at 09:00:52PM +0800, Eugene Grosbein wrote: [...] > 3. Now we enter ip_output() keeping imo as one of arguments. >There we run the following code: > > else if (IN_MULTICAST(ntohl(ip->ip_dst.s_addr)) && > imo != NULL && imo->imo_multicast_ifp != NULL) { >

[ANALISYS] Re: multicast arp entry

2004-05-20 Thread Eugene Grosbein
On Tue, May 18, 2004 at 01:51:34PM +0300, Ruslan Ermilov wrote: > > got message of size 236 on Tue May 18 16:42:26 2004 > > RTM_ADD: Add Route: len 236, pid: 0, seq 0, errno 0, > > flags: > > locks: inits: > > sockaddrs: > > 224.0.0.9 1.0.5e.0.0.9 em3:0.7.e9.1f.f1.de 172.20.2.75 > > > > After

Re: multicast arp entry

2004-05-20 Thread Ruslan Ermilov
On Thu, May 20, 2004 at 10:03:07AM +0800, Eugene Grosbein wrote: > > > 1. Get FreeBSD 4.9-STABLE :-) > > > 2. Install quagga from _fresh_ port collection (0.96.4 does NOT work) > > > 3. run zebra and ripd, configure as usual. > > > > > They apparently do the thing equivalent to mrouted(8), and that

Re: multicast arp entry

2004-05-19 Thread Eugene Grosbein
> > 1. Get FreeBSD 4.9-STABLE :-) > > 2. Install quagga from _fresh_ port collection (0.96.4 does NOT work) > > 3. run zebra and ripd, configure as usual. > > > They apparently do the thing equivalent to mrouted(8), and that's > not what I've understood from your email. Thanks anyway. ;) By the

Re: multicast arp entry

2004-05-19 Thread Eugene Grosbein
On Wed, May 19, 2004 at 07:12:58PM +0300, Ruslan Ermilov wrote: > > > Care to share the experience of how you were able to send multicasts > > > out several interfaces without tmulticast forwarding using mrouted(8) > > > or its equivalent? > > 1. Get FreeBSD 4.9-STABLE :-) > > 2. Install quagga fr

Re: multicast arp entry

2004-05-19 Thread Ruslan Ermilov
On Wed, May 19, 2004 at 08:51:38PM +0800, Eugene Grosbein wrote: > > Care to share the experience of how you were able to send multicasts > > out several interfaces without tmulticast forwarding using mrouted(8) > > or its equivalent? > > 1. Get FreeBSD 4.9-STABLE :-) > 2. Install quagga from _fre

Re: multicast arp entry

2004-05-19 Thread Eugene Grosbein
> Care to share the experience of how you were able to send multicasts > out several interfaces without tmulticast forwarding using mrouted(8) > or its equivalent? 1. Get FreeBSD 4.9-STABLE :-) 2. Install quagga from _fresh_ port collection (0.96.4 does NOT work) 3. run zebra and ripd, configure a

Re: multicast arp entry

2004-05-19 Thread Ruslan Ermilov
On Wed, May 19, 2004 at 06:24:30PM +0800, Eugene Grosbein wrote: > Ruslan Ermilov wrote: > > > > > The long answer could be: you could join to a single multicast > > > > group on multiple interfaces, and you will be able to receive > > > > multicast on all of them, but if you don't have multicast

Re: multicast arp entry

2004-05-19 Thread Eugene Grosbein
Ruslan Ermilov wrote: > > > The long answer could be: you could join to a single multicast > > > group on multiple interfaces, and you will be able to receive > > > multicast on all of them, but if you don't have multicast > > > forwarding enabled, only one interface will be used for sending. > >

Re: multicast arp entry

2004-05-18 Thread Ruslan Ermilov
On Tue, May 18, 2004 at 10:08:58PM +0800, Eugene Grosbein wrote: > On Tue, May 18, 2004 at 01:51:34PM +0300, Ruslan Ermilov wrote: > > > The long answer could be: you could join to a single multicast > > group on multiple interfaces, and you will be able to receive > > multicast on all of them, bu

Re: multicast arp entry

2004-05-18 Thread Eugene Grosbein
On Tue, May 18, 2004 at 01:51:34PM +0300, Ruslan Ermilov wrote: > The long answer could be: you could join to a single multicast > group on multiple interfaces, and you will be able to receive > multicast on all of them, but if you don't have multicast > forwarding enabled, only one interface will

Re: multicast arp entry

2004-05-18 Thread Ruslan Ermilov
On Tue, May 18, 2004 at 04:55:14PM +0800, Eugene Grosbein wrote: > Hi! > > route -n monitor shows me: > > got message of size 236 on Tue May 18 16:42:26 2004 > RTM_ADD: Add Route: len 236, pid: 0, seq 0, errno 0, > flags: > locks: inits: > sockaddrs: > 224.0.0.9 1.0.5e.0.0.9 em3:0.7.e9.1f.f1.