How to get Bell Fibe in Quebec/Ontario (Internet and IPTV) working with pfSense
-
in my case there is when the pvr is booting up, also in the case you ever need to replace the hard drive it’s also needed, i don’t believe it needs it while viewing live tv or recording
-
@idscomm said in How to get Bell Fibe in Quebec/Ontario (Internet and IPTV) working with pfSense:
@autumnwalker
Thanks for the link, very interesting post, helped me understand a bit better. That JamesMTL seems to be very knowledgeable!!I will have to tune my IGMP Proxy, DNS and Rules a bit. Do you have any IPV6 traffic going through or not?
No, there does not appear to be any IPv6 going through for IPTV.
JamesMTL has helped me tune my config a lot. Very knowledgeable!
-
@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 ...
-
This post is deleted! -
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 -
@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.
-
@autumnwalker Just to let you know I’m fully working and I’m in the Halifax area With fibreOp
-
@rcmpayne What did you set for rules? Did you follow the guide @autumnwalker provided me?
-
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?
-
@idscomm are you trying to pause on a non-DVR STB or on the DVR itself?
-
@autumnwalker That's the DVR itself
-
@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.
-
@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!
-
@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!
-
@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.
-
@autumnwalker
here are a few samples....
-
@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)?
-
@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. -
@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.
-
@autumnwalker That's the weird thing, I see the DVR hitting those IP's though... Maybe there's additional ones!
