IGMPProxy1.3 is not starting

[SEi]

Hello Frank,

sorry for my late answer.
I was not lucky, igmpproxy 0.2.1 does not start with a Bridge Interface as upstream.

As a workaround, I switched my DSL modem to router mode and bypassed my opnsense Firewall with a weird VLAN to my media Receiver. So my media Receiver has a direct  Internet Connection as only device.

At the Moment I cannot do anything other than wait and hope for a working igmpproxy >= 0.2.1 for PPPoE Interfaces.


Regards
Sven

[frank_p]

Thank you Sven.

ok... i twas a little chance to get this run.
I like to help, but have no testing machine or 2nd connection.

So waiting... my new iptv box (v3) from telekom is waiting here...

@Franco: can we do something to support the development of the new version to igmpV3 as this is the new standard from German Telekom...

best
Frank

[franco]

Hi Frank,

Basically I lack the connectivity to work on this directly. So far nobody seems interested, but there was an old contact who may be able to help. I'll try to ping him now...


Cheers,
Franco

[frank_p]

Thank you.

[bringha]

Hi there,

not to throw water in the wine: Much likely you won't get Telekom Entertain v3 up and running with igmpproxy: Telekom Entertain v3 needs full upstream and downstream igmpv3 which igmpproxy is currently not supporting. It is doing igmpv3 on uplink and igmpv2 on downlink only.

Nevertheless, to get a little bit more insight what might happen is to start the igmpproxy  with the -d -v options from terminal. It gives you some output right at the beginning what kind of VIF it is getting from kernel. Might be that this can be a hint where it hangs ...

Perhaps you can post the output then ..

Br br

[frank_p]

just to summarize. it means, we have two issues:

- igmpproxy is not starting, when upstream devide is pppoe
- igmpproxy is not supporting igmpv3

correct?

does anyone knows, what alternative instead of igmpproxy, other router have implemented? (e.g speedports from telekom, or fritzbox's). That kind of boxes are working.

br
frank

[bringha]

Correct

igmpproxy uses upstream the kernel internal multicast router/igmp protocol implementation which supports igmpv3. Downstream it has an igmpv2 implementation. I am working since a while on an architectural redesign however am just stuck due some missing freebsd kernel documentation items.

All Fritzbox and Speedports support igmpv3 implicetly, connecting the receiver to them works fine

Nevertheless would love to see the debug output of the igmpproxy on your system to get some more insights where to improve the igmpproxy

Br br

[frank_p]

Ok understand....
Thank you (!) for your effort and time you invest into the re-design.

attached the output of starting igmpproxy manually from shell (217.248.64.9 is assigned as current wan ip, 192.168.2.1 is assigned as lan-interface of the fw):

igmpproxy -d -v /usr/local/etc/igmpproxy.conf
adding VIF, Ix 0 Fl 0x0 IP 0x0102a8c0 re1, Threshold: 1, Ratelimit: 0
adding VIF, Ix 1 Fl 0x0 IP 0x010a000a ovpns1, Threshold: 1, Ratelimit: 0
adding VIF, Ix 2 Fl 0x0 IP 0x010b000a ovpns2, Threshold: 1, Ratelimit: 0
adding VIF, Ix 3 Fl 0x0 IP 0x0940f8d9 pppoe0, Threshold: 1, Ratelimit: 0
joinMcGroup: 224.0.0.2 on re1
joinMcGroup: 224.0.0.2 on ovpns1
joinMcGroup: 224.0.0.2 on ovpns2
RECV V2 member report   from 192.168.2.1     to 224.0.0.2
The IGMP message was from myself. Ignoring.
RECV Membership query   from 192.168.2.1     to 224.0.0.1
RECV Membership query   from 10.0.10.1       to 224.0.0.1
RECV Membership query   from 10.0.11.1       to 224.0.0.1
RECV V2 member report   from 192.168.2.49    to 239.255.255.250
Inserted route table entry for 239.255.255.250 on VIF #0
joinMcGroup: 239.255.255.250 on pppoe0
RECV unk: 0x22/0x00     from 217.248.64.9    to 224.0.0.22
ignoring unknown IGMP message type 22 from 217.248.64.9 to 224.0.0.22
The source address 192.168.2.45 for group 239.255.255.250, is not in any valid net for upstream VIF.
RECV V2 member report   from 192.168.2.84    to 239.254.127.63
Inserted route table entry for 239.254.127.63 on VIF #0

-- following repeats until i stopped the manual start ----
RECV V2 member report   from 192.168.2.1     to 224.0.0.2
The IGMP message was from myself. Ignoring.
RECV unk: 0x22/0x00     from 217.248.64.9    to 224.0.0.22
ignoring unknown IGMP message type 22 from 217.248.64.9 to 224.0.0.22
---------------------------------------------------------------------------------------


regards
Frank

[bringha]

Ok - can you tell me which Network your

192.168.2.0
10.0.x.x

are?

Your 192.168.2.1 is the IP Address of What?

Anyway, your igmpproxy does not recognize the upstream vif properly ...

In my config (no pppoe upstream) it look like:

Code: [Select]

root@OPNsense:~ # /usr/local/sbin/igmpproxy -d -v /usr/local/etc/igmpproxy.conf
adding VIF, Ix 0 Fl 0x0 IP 0x0101a8c0 igb0, Threshold: 1, Ratelimit: 0
adding VIF, Ix 1 Fl 0x0 IP 0x6502a8c0 igb1, Threshold: 1, Ratelimit: 0
joinMcGroup: 224.0.0.2 on igb0
joinMcGroup: 224.0.0.22 on igb0
RECV V2 member report   from 192.168.1.1     to 224.0.0.2
The IGMP message was from myself. Ignoring.
RECV V2 member report   from 192.168.1.1     to 224.0.0.22
The IGMP message was from myself. Ignoring.
(...)
// Here it start to join the entertain group for ARD
RECV V2 member report   from 192.168.1.83    to 239.35.10.4
Inserted route table entry for 239.35.10.4 on VIF #0
joinMcGroup: 239.35.10.4 on igb1
Adding MFC: 193.158.35.251 -> 239.35.10.4, InpVIf: 1
The IGMP message was local multicast. Ignoring.
// Upstream igmpv3 report:
RECV V3 member report   from 192.168.2.101   to 224.0.0.22
(..)
// Client membership report for ARD
RECV V2 member report   from 192.168.1.83    to 239.35.10.4
Updated route entry for 239.35.10.4 on VIF #0
Adding MFC: 193.158.35.251 -> 239.35.10.4, InpVIf: 1
The IGMP message was local multicast. Ignoring.
RECV V2 member report   from 192.168.1.1     to 224.0.0.22
The IGMP message was from myself. Ignoring.
(..)

BR br

[frank_p]

Not sure, how i can change the issue to identify VIF correctly.

Current config:
192.168.2.0 = internal network
10.0.x.x = OpenVPN Server
192.168.2.1 = IP Adress of LAN Interface opnsense
192.168.2.3 = MediaReceiver Telekom (old one igmpV2 not new EntertainTV)
192.168.2.25 = other client

Config of opnsense via GUI
Name   Type                   Values                                                                   Description   
LAN          downstream   192.168.2.3/32, 192.168.2.25/32                           IPTV Downstream   
WAN          upstream   232.0.0.0/8, 239.0.0.0/8, 217.0.119.194/16, 193.158.35.0/24   IPTV Upstream   


regards
Frank

[gliddie]

I am surprise about all the challanges here. For me it is working fine. I also watch the new Telekom IPTV with IGMP V3. My IGMP proxy starts without issues. I have a Vigor 130, I front of my Opnsense box, acting as the Modem.

[frank_p]

so let's find the differences then.
Can you post your igmpproxy.conf and describe your configuration more in detail please.

frank

[bringha]

... and also your network config would be fine

Otherwise look here (its in German)

https://forum.opnsense.org/index.php?topic=4785.0

You can see in your log: igmp type 0x22 is not known (this is a igmpv3 membership report)


Br br

[gliddie]

Ok,

this is my igmpproxy.conf:

Code: [Select]

##------------------------------------------------------
## Enable Quickleave mode (Sends Leave instantly)
##------------------------------------------------------
quickleave
phyint pppoe1 upstream ratelimit 0 threshold 1
altnet 193.158.0.0/15
altnet 224.0.0.0/4
altnet 239.32.0.0/16
altnet 87.141.0.0/15

phyint igb1 downstream ratelimit 0 threshold 1
altnet 192.168.3.0/24

phyint igb2 disabled

[gliddie]

My Topology is:

Telekom Magenta L --> Draytek Vigor 130 acting as Modem --> APU 2C4 / Opnsense 18.1.10 --> LAN Switch TP-Link TL-SG108E with IGMP Snooping enebaled --> TVHeadend/Centos Linux on Intel NUC --> Kodi TVH Client on Rasperrry PI.

It is working like a charm.