Everton Marques
2009-08-31 13:04:12 UTC
Hi Bhavin,
mroute socket.
see pim_upstream.h. You will find the corresponding MFC
information under the member "channel_oil".
You can find the MFC API here:
http://tldp.org/HOWTO/Multicast-HOWTO-7.html
since pimd relies solely on zebrad to get unicast RPF information.
Cheers,
Everton
---------------------------- Original Message ----------------------------
Subject: querry related with zebra architecture and pim
Date: Fri, August 21, 2009 9:11 am
--------------------------------------------------------------------------
In order to reach qpimd-users mailing list, you shouldSubject: querry related with zebra architecture and pim
Date: Fri, August 21, 2009 9:11 am
--------------------------------------------------------------------------
But when i was going through th code of pimd module i have found that
the multicast entry in the kernel is enterd with the help of socket
function in pim_mroute.c program.
Yes, that is correct, qpimd currently handles the MFC directly thru anthe multicast entry in the kernel is enterd with the help of socket
function in pim_mroute.c program.
mroute socket.
Can anyone tell me abstract view of how multicasting entry in the kernel
routing table(mfc) is created or removed?
Every global (S,G) state is stored in "struct pim_upstream",routing table(mfc) is created or removed?
see pim_upstream.h. You will find the corresponding MFC
information under the member "channel_oil".
You can find the MFC API here:
http://tldp.org/HOWTO/Multicast-HOWTO-7.html
The othre thing is what if i just
use pimd and zebrad and no unicast dameon then will it be capable of getting
rpf information? If yes then from where?
Only if you enter the RPF information as static routes in zebrad,use pimd and zebrad and no unicast dameon then will it be capable of getting
rpf information? If yes then from where?
since pimd relies solely on zebrad to get unicast RPF information.
Cheers,
Everton