pedrofran12 / pim_dm Goto Github PK

PIM-DM v1.1.1 supports the definition of multiple routing tables.

Unicast routing table:

• By default, RPF checks and unicast metric information is obtained from the default unicast routing table (id 254). If intended this information can be obtained from a different table just by setting the expected table id at startup with -uvrf UNICAST_TABLE_ID.

Multicast routing table:

• By default, all multicast trees are set on the default multicast routing table (id 0). If intended trees can be set on a different table by setting the expected table id at startup with -mvrf MULTICAST_TABLE_ID.
• If the multicast routing table is different from the default one, multicast rules are automatically defined for all interfaces that are added to the protocol process. If interface eth0 is added to the protocol and the multicast routing table id is 5, the rules that are automatically defined are:

$ ip mrule add iif eth0 lookup 5
$ ip mrule add oif eth0 lookup 5

This issue lists some ideas and future improvements that could be performed to PIM-DM implementation.

• BFD support
• IGMPv3 & MLDv2
• IPv6 multicast routing support (update Kernel and implement MLD) (DONE #3)
• Better debug messages
• More automation on tests
• Change API used to access unicast routing information (ipdb will become deprecated).
• Perform tests using other environment (current one does not have support for IPv6 multicast routing - limitations at the kernel level).
• Multiple tables support. (DONE #4)
• Have a configuration file to configure everything on startup.
• Multicast routing protocol takes into consideration interest of own router (router has application that joined some multicast groups)