Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    How to get Bell Fibe in Quebec/Ontario (Internet and IPTV) working with pfSense

    Scheduled Pinned Locked Moved
    General pfSense Questions
    47
    253
    128.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      Bastion
      last edited by

      Great topic ! Thanks to all posters for sharing.

      All system working smoothly here since couple of days.
      One wired pvr (VIP-2622)
      One wired stb (VIP-2502)
      One wireless transmitter (VAP-2500)
      Two wireless stb (VIP-2502)

      The igmpproxy is broken on 2.2.5 and had to be updated according to this post https://forum.pfsense.org/index.php?topic=93293.0
      The igmpproxy version on 2.3 is up to date and works https://forum.pfsense.org/index.php?topic=102729.msg572837#msg572837

      Regards,

      1 Reply Last reply Reply Quote 0
      • Z
        zax123
        last edited by

        Thanks so much for posting this!

        I'll definitely wait till 2.3 then before upgrading.  I'm at 2.2.4 right now and all is good.

        I'm about to upgrade my box to a Jetway quad Celeron (just waiting on a Black Friday deal) because my little APU box can't handle my GB fiber. :)  So I'll have to run 2.2.4 on the new box until they release 2.3.  Any idea when that might be?

        1 Reply Last reply Reply Quote 0
        • H
          Harryrosen
          last edited by

          Hi

          I got everything working great, but for some reason I loose 1 channel after a couple days, I have the reboot my pfsense and it works fine again, any ideas why it's only 1 channel losing signal?

          1 Reply Last reply Reply Quote 0
          • S
            singerie
            last edited by

            I have the same issue (with TLC).

            1 Reply Last reply Reply Quote 0
            • Z
              zax123
              last edited by

              Are you guys running pfSense 2.2.4 or 2.2.5?  I heard there are bugs in igmproxy in 2.2.5…

              1 Reply Last reply Reply Quote 0
              • H
                Harryrosen
                last edited by

                I am running 2.2.5

                Can you downgrade to 2.2.4?

                1 Reply Last reply Reply Quote 0
                • B
                  Bastion
                  last edited by

                  I had same issue before updating the broken igmpproxy on 2.2.5, and had to update it according to :
                  https://forum.pfsense.org/index.php?topic=93293.0n

                  The igmpproxy version on 2.3 is up to date and works flawlessly :
                  https://forum.pfsense.org/index.php?topic=102729.msg572837#msg572837

                  Regards,

                  1 Reply Last reply Reply Quote 0
                  • H
                    Harryrosen
                    last edited by

                    Just updated to 0.1 and rebooted looks like it's working

                    how do I check if it was upgraded, I put the igmpproxy in the command line and it asked for the conf file.

                    under services it's running but just want to make sure it's now 0.1

                    thanks I am new to all this

                    1 Reply Last reply Reply Quote 0
                    • B
                      Bastion
                      last edited by

                      If you go into diagnostics > command prompt and type "pkg info" into "command" it shows:

                      igmpproxy-0.1_2,1 Multicast forwarding IGMP proxy

                      1 Reply Last reply Reply Quote 0
                      • H
                        Harryrosen
                        last edited by

                        Awesome

                        All upgraded

                        Thanks

                        1 Reply Last reply Reply Quote 0
                        • S
                          surrealillusion
                          last edited by

                          So I tried following this guide to get my Bell Fibe TV and Internet working.  Internet obviously was easy enough but my PVR boots up with a message saying Network Connection error every time.  The PVR does receive an IP from pfSense but I guess it's not able to communicate with Bell servers?

                          1 Reply Last reply Reply Quote 0
                          • Z
                            zax123
                            last edited by

                            @surrealillusion:

                            So I tried following this guide to get my Bell Fibe TV and Internet working.  Internet obviously was easy enough but my PVR boots up with a message saying Network Connection error every time.  The PVR does receive an IP from pfSense but I guess it's not able to communicate with Bell servers?

                            What version of pfSense are you using?  You might want to use 2.2.4 as IGMP proxy doesn't work well in 2.2.5 (and I suspect 2.2.6 as well).  Read up thread about that.

                            1 Reply Last reply Reply Quote 0
                            • S
                              surrealillusion
                              last edited by

                              Yeah I saw that earlier in the thread and also read that in the 2.3 alpha the igmpproxy package was updated.  The only thing showing up currently is:

                              Dec 30 11:20:38 igmpproxy 89210 RECV Membership query from 192.168.1.1 to 224.0.0.1

                              For my proxies I added:

                              224.0.0.0/4
                              10.0.0.0/8
                              192.168.1.0/24 (since the default lan is not contained in either subnet for upstream

                              downstream of course is the default pfSense LAN subnet.

                              The IPTV WAN does get a dhcp address (but it's not exactly the one listed in the original thread, but that's likely that there are numerous servers based on location).  What else should I be looking for in my wireshark dumps to understand if the PVR is communicating properly?

                              1 Reply Last reply Reply Quote 0
                              • Z
                                zax123
                                last edited by

                                I would think that you probably have something missing in your rules or IGMP proxy settings.  Have you compared them to the original post?  Do you have other rules that could conflict?

                                1 Reply Last reply Reply Quote 0
                                • S
                                  surrealillusion
                                  last edited by

                                  Ah just noticed I needed to set the advcanced option in both the LAN and IPTV_WAN firewall rules.  Still no luck so far after applying that setting.

                                  1 Reply Last reply Reply Quote 0
                                  • Z
                                    zax123
                                    last edited by

                                    Even if IGMP proxy isn't working, you should still get a few seconds of video when you change channel.  If you aren't getting that, I would suspect the problem is with your VLAN setup.

                                    1 Reply Last reply Reply Quote 0
                                    • S
                                      surrealillusion
                                      last edited by

                                      Yeah I'm not even getting that, the PVR boots up and displays a Network Connection error message so I don't even get to the apps.  I've got vlans 35 and 36  created and put the IPTV_WAN on vlan 36 on my ethernet that connects to the ONT.  VLAN35 works for Internet as I'm posting this message but 36 doesn't seem to work.  The DHCP address I'm getting for the Fibe TV appears to be correct (though in my logs it's saying it can't ping the gateway that has been provided for the interface, not sure if that is normal).

                                      1 Reply Last reply Reply Quote 0
                                      • Z
                                        zax123
                                        last edited by

                                        Where do you see that you can't ping the gateway?

                                        My gateway IP is 10.240.112.1, is yours something similar?

                                        1 Reply Last reply Reply Quote 0
                                        • S
                                          surrealillusion
                                          last edited by

                                          @zax123:

                                          Where do you see that you can't ping the gateway?

                                          My gateway IP is 10.240.112.1, is yours something similar?

                                          In the gateway logs I believe it's using the monitor IP to check the health of the link

                                          Dec 30 14:21:14 dpinger send_interval 250ms loss_interval 1000ms time_period 25000ms report_interval 0ms alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 10.227.32.1 bind_addr 10.227.43.30 identifier "WAN_IPTV_DHCP "
                                          Dec 30 14:21:16 dpinger WAN_IPTV_DHCP 10.227.32.1: Alarm latency 0us stddev 0us loss 100%

                                          Yeah my IPTV gateway is different … hmm

                                          1 Reply Last reply Reply Quote 0
                                          • Z
                                            zax123
                                            last edited by

                                            I see you're using dpinger.  I believe they switched to dpinger in pfSense 2.3.  Are you using 2.3?

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post