[Xorp-users] How to decide Unsolicited Report Interval in IGMPv3 XORP

[Tushar Mehta]

I want to configure my OS(on which XORP is running) for IGMPv3 host also 
and want to set parameter Unsolicited Report Interval.
which file i have to modify for configuring my OS as IGMPv3 host.

I am attaching the XORP configuration file which is used by me for 
running IGMPv3(IPv4).
Robustness variable is set to 5(high) just for increasing the 
retransmission for the state change report
so that i can check whether interval between them is ( 0, Unsolicited 
Report Interval) or not.

OS specification on which XORP is running:
OS: Fedora Core 5
kernel version: 2.6.15-1.2054_FC5
architecture: i686
XORP version: 1.4
IGMP version: 3( for IPv4)

Pavlin Radoslavov wrote:
> Tushar Mehta <tushar.mehta at einfochips.com> wrote:
>
>   
>> Can anyone tell me how i can find the Unsolicited Report Interval that 
>> is used when any IGMP host use while transmitting state change record?
>>
>> according to the rfc-3376:
>> - To cover the possibility of the State-Change Report being missed by 
>> one or more multicast routers, it is retransmitted [Robustness
>>   Variable] - 1 more times, at intervals chosen at random from the range 
>> (0, [Unsolicited Report Interval]).
>>
>> - Unsolicited Report Interval
>>    The Unsolicited Report Interval is the time between repetitions of a
>>    host's initial report of membership in a group.  Default: 1 second.
>>
>> by default Unsolicited Report Interval should be 1 but XORP is not 
>> following it. it is picking up this interval randamly.
>>     
>
> As Bruce mentioned in another email on the subject, this is
> kernel-related config.
>
> To clarify:
> IGMP/MLD has two parts: router-side and host-side.
> The host-side is typically implemented by the OS (in the kernel).
> The router-side is typically an userland process.
>
> XORP implements only the router-side, and for the host-side relies
> on the kernel implementation.
> The configuration changes in XORP apply only to the router side; the
> host-side configuration changes are OS specific and you should refer
> to the particular OS/kernel documentation for that.
> In the future we might expose the host-side configuration in the
> xorpsh, but right now this is a very low priority for us.
>
> Hope that helps,
> Pavlin
>
>
>
>   
>> i m attaching the configuration file that i am using for my set up.
>>
>>
>> -- 
>> _____________________________________________________________________
>> Disclaimer: This e-mail message and all attachments transmitted with it
>> are intended solely for the use of the addressee and may contain legally
>> privileged and confidential information. If the reader of this message
>> is not the intended recipient, or an employee or agent responsible for
>> delivering this message to the intended recipient, you are hereby
>> notified that any dissemination, distribution, copying, or other use of
>> this message or its attachments is strictly prohibited. If you have
>> received this message in error, please notify the sender immediately by
>> replying to this message and please delete it from your computer. Any
>> views expressed in this message are those of the individual sender
>> unless otherwise stated.Company has taken enough precautions to prevent
>> the spread of viruses. However the company accepts no liability for any
>> damage caused by any virus transmitted by this email.
>> _____________________________________________________________________
>>  
>>
>> _______________________________________________
>> Xorp-users mailing list
>> Xorp-users at xorp.org
>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>>     
>
>
> Email Scanned for Virus & Dangerous Content by : www.CleanMailGateway.com
>
>
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20080723/dfa8f6a9/attachment.html 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: config.boot.sample_igmp
Url: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20080723/dfa8f6a9/attachment.ksh