IGMPv3Query extends IGMPv2Query, because IGMPv2 routers must accept IGMPv3Query packets.
Note: in IGMPv3Query the maxResponseTime field is renamed to maxResponseCode and it is interpreted differently than in IGMPv2.
The following diagram shows usage relationships between types. Unresolved types are missing from the diagram.
The following diagram shows inheritance relationships for this type. Unresolved types are missing from the diagram.
Name | Type | Description |
---|---|---|
IGMPv2Query | packet | (no description) |
Name | Type | Description |
---|---|---|
suppressRouterProc | bool | |
robustnessVariable | unsigned char | |
queryIntervalCode | unsigned char | |
sourceList | IPv4AddressVector | |
maxRespCode | unsigned char | |
type | int | |
maxRespTime | unsigned char | |
groupAddress | IPv4Address |
// // IGMPv3Query extends IGMPv2Query, because // IGMPv2 routers must accept IGMPv3Query packets. // // Note: in IGMPv3Query the maxResponseTime field is // renamed to maxResponseCode and it is interpreted // differently than in IGMPv2. packet IGMPv3Query extends IGMPv2Query { @customize(true); bool suppressRouterProc; unsigned char robustnessVariable; unsigned char queryIntervalCode; IPv4AddressVector sourceList; abstract unsigned char maxRespCode; }