Hello

Using a 2750n running 1.5.2

I am trying to Use the great Draytek instead of the Lesser BT Home Hub 3 !

Now have enabled IGMP Proxy and Snooping I seen the multicast address in the IGMP Group under snooping

BUT no dice. is there a Vlan or alike that needs to be configured ?? i read re other PVC on normal DSL but not on VDSL

Thanks

Blue

This may help its taken from SIN 503 Issue 1.0  British Telecommunications plc

http://www.sinet.bt.com/503v1p0b.pdf

3.2.2 IGMP Operation - User Side
As stated in the IGMP specification [2], there will be no acknowledgement that Openreach or the CP has accepted a membership join report or that a media stream exists for the group and is being sent.

Openreach will employ “fast leave” mode of IGMP. The benefit is most apparent when an FTTC served user changes from one channel stream to another. By immediately cutting the stream of the unwanted channel, the downstream bandwidth is released for the new channel and other services sharing the downstream bandwidth.

Openreach will operate in IGMP snooping mode with proxy agent. CPE should therefore expect and should respond to IGMPv2 and IGMPv3 query messages from the proxy agent having a source IP address of 0.0.0.0. Note: Should this prove not to be possible for the trial, Openreach may need to choose a non-zero address initially.

It is recommended that CPs are familiar with Residential gateway requirements to support Multicast as set out in the broadband forum’s guidance in TR101 and TR156, available at http://www.broadband-forum.org/.

3.2.2.1 IGMP encapsulation

IGMP messages intended for the Openreach Multicast service must be sent as either:
• IGMP over IP; or
• IGMP over Ethernet, within VLAN 0 only

Explicitly, IGMP messages sent as IGMPoPPPoE, or where any VLAN other than 0 is used, will be passed through transparently to the CP and will not be acted on by Openreach.

3.2.2.2 IGMP upstream prioritisation
To ensure IGMP upstream packets are treated with the highest available scheduling priority, CPE should encapsulate them in VLAN-0 and set the IEEE priority field to 3 or above.

3.2.2.3 IGMP use limitations
Openreach will impose a limit to the total number of groups a UNI is permitted to join simultaneously, sixteen or less group memberships will be permitted irrespective of their bandwidth.
There will be a finite limit to the rate of IGMP messages that Openreach will process. This limit is still to be determined but will be set at a level not less than 10 IGMP packets per second.

3.3 Multicast Operation - General
Openreach will support IPv4 multicast only.

Except for the following restrictions stated, Openreach will accept membership join reports to all groups; there is no support within Openreach network to accept or deny joins based on bandwidth allocation or group addresses permitted to a user or their CP.
Openreach will use a common multicast GEM for distribution of downstream multicast content over GPON. Openreach does not encrypt this content. All ONTs attached to the PON receive this content. The Openreach ONT will only forward this content to UNIs that have a valid membership join.

Openreach will support IP multicast group addresses in the range 225.0.0.0 to 239.255.255.255. The range 224.0.0.0/24 reserved range will not be accepted in accordance with IANA rules.

Irrespective of source specific multicast service model implied by the use of IGMPv3, Openreach will not enforce the use of SSM destination addresses (232.0.0.0/8) as defined by RFC3376 (IGMPv3). Likewise there is no special treatment or restriction of the GLOP address range defined by RFC2770.

GEA will replicate multicast streams according to esdestination MAC address. Only 23 bits of the MAC address can be used to distinguish different groups. Since the multicast MAC address is derived from the IP group address, CPs must ensure IP group addresses are unique when a 23 bit mask is applied.

Because IGMPv3 includes backward compatibility to IGMPv2, any host sending an IGMPv2 report will cause the Openreach interface to revert to v2 mode and will initiate an immediate IGMPv2 query to other hosts attached to that interface, thus causing those hosts to revert to IGMPv2 mode. The scope of the Openreach interface for FTTC is the modem UNI and attached LAN. For FTTP the interface scope is all ONT UNIs (and their attached LANs) common to that CP on the same PON.

3.3.1 Known limitations

RFC3376 for IGMPv3 details support for source filtering, that is, the ability for a system to report interest in receiving packets ‘only’ from specific source addresses, as required to support Source-Specific Multicast [SSM], or from ‘all but’ specific source addresses, sent to a particular multicast address. Openreach will not support the “‘all but’ specific source addresses” requirement.

Specifically, If GEA receives IGMPv3 report of To_EXclude ({X},G), or Is_EXclude ({X},G), meaning join to group G except from source X (or multiple sources listed), the membership report will be silently ignored by Openreach. If an empty list is provided, the report will be accepted and acted upon.

oooooo

Beta Firmware

ftp://ftp.draytek.pl/Seria_2750/Firmware/BETA/

1.5.3 RC2

And it supports IGMP V3 Proxy !!!

Will test
Blue

installed and yes IGMP version support 1,2 or 3 or AUTO

Selected just v3 can see the V3 reports received increasing as the channels are changed

and you see in System log

Time Level Type Message
Jan 12 20:57:44 warn user igmpproxy[28264]: Not send join message upstream : croute->upstrState = 1
Jan 12 20:57:43 warn user igmpproxy[28264]: Send join message upstream : croute->upstrState = 0
Jan 12 20:57:43 warn user igmpproxy[28264]: Send join message upstream : croute->upstrState = 0
Jan 12 20:57:42 warn user igmpproxy[28264]: Send join message upstream : croute->upstrState = 0

But no signal seen on IPTV box

and ideas ??

Blue

Section 3.2.2.1 is interesting, I'm not sure how it would be implemented but it does look as though it will involve the WAN - Multi-VLAN setup, unfortunately the demo router on Draytek's site shows old firmware, but I think if it has an option for IGMP WAN under Multi-VLAN then it could work? It looks as though you'd need to set it with VLAN tag 0 according to those settings. That beta firmware should help as well.