How to get Bell Fibe in Quebec/Ontario (Internet and IPTV) working with pfSense
-
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?
-
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.
-
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.
-
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).
-
Where do you see that you can't ping the gateway?
My gateway IP is 10.240.112.1, is yours something similar?
-
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
-
I see you're using dpinger. I believe they switched to dpinger in pfSense 2.3. Are you using 2.3?
-
Yes last night's snapshot, I know it's still in Alpha but it's always good to provide feedback
-
I haven't tested it with 2.3… so I'm not sure if any settings need to change with it. :(
-
Will try grabbing 2.2.4 and reload the firewall. I'll report back with findings
-
Doesn't have appeared to worked, still getting the same message. Going to see if I can speak with an egineer about this
-
Which of course is pointless as they say they don't know how to troubleshoot their own network unless it's with a homehub 2000. They kept saying that the PVR should receive an IP in the 192.168.2.11-17 range (but what if the PVR is plugged into a router that offers its a completely different address)? :) I wish there was at least 1 or 2 lvl 2 desk support agents that were at least curious as to how a network they support actually functions (perhaps when pigs fly).
Anyhow one though occurred to me while on hold, for those that it worked for was your PVR connected via the HPNA connector or via LAN before moving to pfSense? Either way I have to hook up my homehub again because they had me soft reset it when caused it to get a red x on the screen.
-
Which of course is pointless as they say they don't know how to troubleshoot their own network unless it's with a homehub 2000. They kept saying that the PVR should receive an IP in the 192.168.2.11-17 range (but what if the PVR is plugged into a router that offers its a completely different address)? :) I wish there was at least 1 or 2 lvl 2 desk support agents that were at least curious as to how a network they support actually functions (perhaps when pigs fly).
Anyhow one though occurred to me while on hold, for those that it worked for was your PVR connected via the HPNA connector or via LAN before moving to pfSense? Either way I have to hook up my homehub again because they had me soft reset it when caused it to get a red x on the screen.
.
-
Well this is going to sound strange but after leaving the whole setup alone and doing some more traffic captures I plugged everything back in and it now works. I didn't make any changes to the pfSense config, very odd. Finally I can enjoy the PVR and be rid of this homehub. Thanks for the help!
-
Well this is going to sound strange but after leaving the whole setup alone and doing some more traffic captures I plugged everything back in and it now works. I didn't make any changes to the pfSense config, very odd. Finally I can enjoy the PVR and be rid of this homehub. Thanks for the help!
First of all, thanks to the OP, and everyone else in this thread.
I had everything working in a virtual machine to test, except I had a dedicated subnet/interface for the LAN side of the IPTV, everything worked.
So I decided to move to an APU unit and now I am receiving the same network connection error on the dvr unit as surrealillusion… my Wireless Receiver works fine to watch tv.
Tried DVR on HomeHub again, works fine, moved back same issue.
I am wondering if there is a timeout or something that needs to drop as I have made many changes/tests, so I guess I am waiting it out as I can see nothing getting blocked.
-
Is there anyway to set this up with non-FTTH? I can't seem to get a gateway IP, just says "Dynamic' and no internet activity. Was hoping to have my pfSense and my Coax to Ethernet box replace the HH2000.
-
Hello,
I followed the tutorial step by step:
Internet works totally
TV Works partially: Multicast work but not Replay, VOD and APPAny idea ?
PfSense Router Configuration:
Config: Intel Atom Processor C2750, Supermicro A1SAi-2750F, 4gb ram, 120gb ssd
Version: 2.2.6-RELEASE (amd64)