All of lore.kernel.org
 help / color / mirror / Atom feed
From: Meenakshi Kaushik <meenakka@nortelnetworks.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Multicast routing
Date: Tue, 08 Jul 2003 02:57:36 +0000	[thread overview]
Message-ID: <marc-lartc-105763314217068@msgid-missing> (raw)

Hello list,
   Not sure if I am asking the question in the correct list. I am a 
newbie trying
to get multicast routing to work on my linux 2.4 kernel. I am using
usc pimd code. I have pimd which sets up the route in the kernel

[ /tmp]# ip mroute show
(22.22.22.1, 224.0.1.20)         Iif: eth2       Oifs: eth1
[ /tmp]#

I can see data packets arriving on eth2

[/tmp]# tethereal -i eth2
Capturing on eth2
  0.000000   22.22.22.1 -> 224.0.1.20   UDP Source port: 32770  
Destination port: 12345
  1.000000   22.22.22.1 -> 224.0.1.20   UDP Source port: 32770  
Destination port: 12345
  2.000000   22.22.22.1 -> 224.0.1.20   UDP Source port: 32770  
Destination port: 12345
 
However, packets  are not getting forwarded on eth1

[ /tmp]# cat /proc/net/ip_mr_cache
Group    Origin   Iif     Pkts    Bytes    Wrong Oifs
140100E0 01161616 2         82    84788        0  1:1 
[mkaushik@ooty2 /tmp]#



[ /tmp]# cat /proc/sys/net/ipv4/ip_forward
1

Any suggestions on debugging the problem is greatly appreciated

Thanks
Meenakshi






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

             reply	other threads:[~2003-07-08  2:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-08  2:57 Meenakshi Kaushik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-15  4:51 [LARTC] Multicast routing Sachin K
2004-01-11 20:42 [LARTC] Multicast Routing Alan Ford
2002-08-30 20:08 Badrul Anuar

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-105763314217068@msgid-missing \
    --to=meenakka@nortelnetworks.com \
    --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.