[Xorp-users] IGMP host version problem

[Pavlin Radoslavov]

Tushar Mehta <tushar.mehta at einfochips.com> wrote:

> in my setup, when XORP(IGMPv3 for IPv4 router sends IGMP version 1 or 2 query
> then IGMPv3 host is changed to version 1 or 2 respectively
> but when XORP turns back to IGMPv3 querier, host is not coming back to version
> 3 and still sending report with version or 2
> 
> what is the reason?

According to RFC 3376, the host should switch back to the higher
IGMP version after the "Older Version Querier Interval". That
interval is defined in Section 8.12 to:
 ((the Robustness Variable) times (the Query
   Interval in the last Query received)) plus (one Query Response
   Interval)

and the default value is 2 * 125 + 10 = 260 seconds.

If the host doesn't switch back after 260 seconds (or whatever the
value is for your config), then it is probably a bug in the kernel's
IGMP implementation.

Pavlin

> here i have attached the configuration file and my setup.
> 
> XORP machine specification:
> OS: Fedora Core 5
> kernel version: 2.6.15-1.2054_FC5
> architecture: i686
> XORP version: 1.4
> IGMP version: 3( for IPv4)
> 
> Host Machine specification:
> OS: RHEL 4
> kernel version: 2.6.9-5.EL
> architecture: i686
> 
> 
> -- 
> _____________________________________________________________________
> 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: xorp/rtrmgr/config.boot.sample,v 1.46 2007/03/12 10:16:05 atanu Exp $ */
> 
> 
> interfaces {
>     restore-original-config-on-shutdown: false
>     interface eth0 {
> 	description: "ethernet interface"
> 	disable: false
> 	default-system-config
> 	} 
> }
> 
> 
> fea {
>     unicast-forwarding4 {
> 	disable: false
> 	forwarding-entries {
> 	    retain-on-startup: false 
> 	    retain-on-shutdown:	false
> 	}
>     }
> }
> 
> 
> policy {
>     /* Describe connected routes for redistribution */
>     policy-statement connected {
> 	term export {
> 	    from {
> 		protocol: "connected"
> 	    }
> 	}
>     }
> }
> 
> policy {
>     /* Describe static routes for redistribution */
>     policy-statement static {
> 	term export {
> 	    from {
> 		protocol: "static"
> 	    }
> 	}
>     }
> }
> 
> plumbing {
>     mfea4 {
> 	disable: false
> 	interface eth0 {
> 	    vif eth0 {
> 		disable: false
> 	    }
> 	}
> 	interface register_vif {
> 	    vif register_vif {
> 		/* Note: this vif should be always enabled */
> 		disable: false
> 	    }
> 	}
> 	traceoptions {
> 	    flag all {
> 		disable: false
> 	    }
> 	}
>     }
> }
> 
> protocols {
>     igmp {
> 	disable: false
> 	interface eth0 {
> 	    vif eth0 {
> 		disable: false		
> 		 version: 3
> 		 enable-ip-router-alert-option-check: true
> 		 query-interval: 5
> 		 query-last-member-interval: 5
> 		 query-response-interval: 2
> 		 robust-count: 2 
> 	    }
> 	}	
> 	traceoptions {
> 	    flag all {
> 		disable: false
> 	    }
> 	}
>     }
> }
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users