How to get Bell Fibe in Quebec/Ontario (Internet and IPTV) working with pfSense
-
My specs are pretty simple :
E8500 with 2 gigs of ram.
an SSD for the os, the cheapest one.
when running a speedtest, I have +- 38% cpu usage with bell gigabit. my usual speed is 932 or 933 mbit.
Also, I was wondering if i can share this how to on dslreports under the bell forum… i'm sure people would love this how to !
-
Absolutely share! :)
-
My two cents…
For those having IGMP flooding issue, you should probably look into a switch that supports IGMP snooping. This feature will learn which port joined which multicast group and will forward packets properly. Of course the Home Hub has this feature.
Also I had the chance to analyze a Home Hub configuration file (don't ask me how I got this) and found out RIPv1/v2 is enabled on the WAN IPTV interface. Might be worth to look into this, as it would probably remove the need for static routes.
-
Would you be willing to share that configuration file? It could help to improve our setup. Thanks!
-
There you go, here is a config file taken from a Sagemcom 2864. It was running on FTTN, but FTTH stuff is there too.
I also included the OpenRG Configuration Guide to help understand how this thing works.
-
Wow that's pretty complex. :) I don't know why I expected it to be easier to interpret… maybe there is an interpreter out there. I'm just wondering if I'm missing something in my pfSense config, but I'm not sure I'll be able to figure this all out.
Thanks though! :)
-
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#msg572837Regards,
-
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?
-
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?
-
I have the same issue (with TLC).
-
Are you guys running pfSense 2.2.4 or 2.2.5? I heard there are bugs in igmproxy in 2.2.5…
-
I am running 2.2.5
Can you downgrade to 2.2.4?
-
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.0nThe igmpproxy version on 2.3 is up to date and works flawlessly :
https://forum.pfsense.org/index.php?topic=102729.msg572837#msg572837Regards,
-
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
-
If you go into diagnostics > command prompt and type "pkg info" into "command" it shows:
igmpproxy-0.1_2,1 Multicast forwarding IGMP proxy
-
Awesome
All upgraded
Thanks
-
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?
-
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.
-
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 upstreamdownstream 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?
-
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?