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
    253 Posts 47 Posters 150.4k Views
    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.
    • A
      autumnwalker @CrazyMitchy
      last edited by

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

      @autumnwalker Everything else in your instructions work A1 though, I'm looking at my firewall and don't see my PVR trying to contact anything other than routes I created at the start. How did you go about finding those Aliant DNS?

      Does Bell in Quebec use DHCP or PPPoE? In Atlantic Canada (Bell Aliant) we use DHCP and no PPPoE. The DNS servers are pulled down with the DHCP request that the GPON sends out to Aliant. Once I had them I swapped to my own DNS and setup the two URLs in my DNS Resolver to forward to the Aliant DNS servers.

      I strongly suspect that Quebec is not the same as Aliant ...

      1 Reply Last reply Reply Quote 0
      • C
        CrazyMitchy
        last edited by

        This post is deleted!
        P A 2 Replies Last reply Reply Quote 0
        • P
          pjaneiro @CrazyMitchy
          last edited by pjaneiro

          these are the dns entries you need to rebind

          207.164.234.129
          207.164.234.193
          10.2.127.228
          10.2.127.196

          1 Reply Last reply Reply Quote 0
          • A
            autumnwalker @CrazyMitchy
            last edited by

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

            We use VLAN35 PPPOE for Internet, but VLAN 36 DHCP for the TV. So I'd have to find Bell's DNS for Quebec?

            The other thing to consider is that fibreop.ca is something specific to Atlantic Canada / Aliant. You will need to follow different configuration instructions than I have provided.

            There is no value in you forwarding fibreop.ca to the Bell DNS servers; however, from what I've read, you should forward iptv.microsoft.ca.

            1 Reply Last reply Reply Quote 0
            • R
              rcmpayne @autumnwalker
              last edited by

              @autumnwalker Just to let you know I’m fully working and I’m in the Halifax area With fibreOp

              idscommI 1 Reply Last reply Reply Quote 0
              • idscommI
                idscomm @rcmpayne
                last edited by

                @rcmpayne What did you set for rules? Did you follow the guide @autumnwalker provided me?

                1 Reply Last reply Reply Quote 0
                • idscommI
                  idscomm
                  last edited by

                  The TV is working but now that I have done more test I noticed that if I pause Live TV, it tells me that I lost connection and go back to live TV.... Any ideas?

                  A 1 Reply Last reply Reply Quote 0
                  • A
                    autumnwalker @idscomm
                    last edited by

                    @idscomm are you trying to pause on a non-DVR STB or on the DVR itself?

                    idscommI 1 Reply Last reply Reply Quote 0
                    • idscommI
                      idscomm @autumnwalker
                      last edited by

                      @autumnwalker That's the DVR itself

                      A 1 Reply Last reply Reply Quote 0
                      • A
                        autumnwalker @idscomm
                        last edited by

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

                        @autumnwalker That's the DVR itself

                        hmm - not sure where to point you on this one. I have seen that happen in my environment, but rare and cannot reproduce. It also happened before I ripped out the HH3K and happened with Bell's older equipment too (I'm OG FibreOP) so I chalked it up to their gear.

                        I'm not sure why pausing would have any effect on the stream coming from Bell (IGMP, firewall rules, routing) versus the "live" stream. Someone who has more knowledge of how the streaming works on the Bell end will have to chime in.

                        idscommI 1 Reply Last reply Reply Quote 0
                        • idscommI
                          idscomm @autumnwalker
                          last edited by idscomm

                          @autumnwalker So, first I rebooted the PVR then I did 2 more packet capture using the live TV and pausing it... I noticed that other than the 10.2/16 and 10.237/16, my box was also reaching for 10.195/16 UPD, TCP and IGMP as source ... I added that route under the upstream and under Static Routes ... Seems like it's working fine now ... I'll do more test and let it run but so far so good!

                          A 1 Reply Last reply Reply Quote 0
                          • C
                            CrazyMitchy
                            last edited by

                            @autumnwalker Well this is akward. It was an IGMP issue after all. I NEVER noticed you could choose the interface it was listening on in pfSense... I pointed it to my LAN and boom it works. I feel kinda dumb lol

                            It works great now, thanks a bunch for your help!

                            Only problem left is the apps, even with the DNS resolver rebinds, it just keeps loading and nothing comes up. Getting there!

                            A 1 Reply Last reply Reply Quote 0
                            • A
                              autumnwalker @idscomm
                              last edited by

                              @idscomm great find! I will have to do some testing on my system over the weekend and report back with findings. Perhaps there is a new route for Aliant now.

                              idscommI 1 Reply Last reply Reply Quote 0
                              • idscommI
                                idscomm @autumnwalker
                                last edited by

                                @autumnwalker
                                here are a few samples....
                                CAP0.jpg
                                CAP1.jpg
                                CAP2.jpg

                                1 Reply Last reply Reply Quote 0
                                • A
                                  autumnwalker @CrazyMitchy
                                  last edited by

                                  @CrazyMitchy glad you got it sorted out! Do you mean the apps on the Bell box or the apps on your devices (e.g. iOS)?

                                  C 1 Reply Last reply Reply Quote 0
                                  • C
                                    CrazyMitchy @autumnwalker
                                    last edited by

                                    @autumnwalker The apps on the DVR itself. I've rerouted bell.ca, bell.com, and iptv.microsoft.com to 207.164.234.129
                                    207.164.234.193, 10.2.127.228, 10.2.127.196, without success. I see my PC resolves iptv.bell.ca to these IP's, but the DVR doesn't connect, it says problem with name resolution.

                                    A 1 Reply Last reply Reply Quote 0
                                    • A
                                      autumnwalker @CrazyMitchy
                                      last edited by

                                      @CrazyMitchy I'm not sure what the right configuration for non-Aliant users is. You may want to capture DNS traffic from the DVR for a bit and see what URLs it is trying to resolve. I would guess that those URLs need to be resolved by Bell's DNS servers, but again, I'm with Aliant which is completely different. While you are capturing try and launch the apps and do different things on the device (including power cycle it) to get it to generate traffic.

                                      C 1 Reply Last reply Reply Quote 0
                                      • C
                                        CrazyMitchy @autumnwalker
                                        last edited by

                                        @autumnwalker That's the weird thing, I see the DVR hitting those IP's though... Maybe there's additional ones!

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

                                          I finally got my pfsense working and getting amazing speeds of 1800/1020 i am in Ontario i have setup iptv it cuts out after 4 seconds after reading i know its the igmp handshake gateway issue ?

                                          packet sniffer my wan_iptvp

                                          13:07:56.989441 IP 10.121.112.173 > 10.121.96.1: ICMP echo request, id 50695, seq 5200, length 8
                                          13:07:57.519447 IP 10.121.112.173 > 10.121.96.1: ICMP echo request, id 50695, seq 5201, length 8
                                          13:07:58.033204 IP 10.121.112.173 > 10.121.96.1: ICMP echo request, id 50695, seq 5202, length 8
                                          13:07:58.211613 IP 10.121.112.173.65145 > 10.2.104.199.47806: UDP, length 134
                                          13:07:58.218217 IP 10.2.104.199.47806 > 10.121.112.173.65145: UDP, length 65
                                          13:07:58.565449 IP 10.121.112.173 > 10.121.96.1: ICMP echo request, id 50695, seq 5203, length 8
                                          13:07:59.097700 IP 10.121.112.173 > 10.121.96.1: ICMP echo request, id 50695, seq 5204, length 8
                                          13:07:59.215453 IP 10.121.112.173.65145 > 10.2.104.199.47806: UDP, length 134
                                          13:07:59.629951 IP 10.121.112.173 > 10.121.96.1: ICMP echo request, id 50695, seq 5205, length 8
                                          13:07:59.896504 IP 10.121.112.173.18050 > 10.2.122.28.43962: UDP, length 113
                                          13:07:59.903900 IP 10.2.122.28.43962 > 10.121.112.173.18050: UDP, length 50
                                          13:08:00.162202 IP 10.121.112.173 > 10.121.96.1: ICMP echo request, id 50695, seq 5206, length 8
                                          13:08:00.694453 IP 10.121.112.173 > 10.121.96.1: ICMP echo request, id 50695, seq 5207, length 8
                                          13:08:01.226706 IP 10.121.112.173 > 10.121.96.1: ICMP echo request, id 50695, seq 5208, length 8

                                          bell pvr is on a 192.168 ip am i missing something here?
                                          and where do i add the bell dns's for ontario???
                                          a little help please :D

                                          Thanks

                                          idscommI A 2 Replies Last reply Reply Quote 0
                                          • idscommI
                                            idscomm @sylvain613
                                            last edited by

                                            @sylvain613
                                            This one if for Nova Scotia but it might help you. You might have to tweak some of the IPs but most config should be the same.
                                            https://www.idscomm.ca/blog/bell-fibe-internet-iptv-with-pfsense

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.