Forum Discussion
Telus Pure Fibre in Ontario - PPPoE
This isn't really a question, it's just FYI for Ontario (and, I assume, Quebec) customers that have Telus Pure Fibre, delivered on Bell's fibre.
In Ontario, Telus has to use PPPoE. Make sure you get the username & password from the tech or call tech support.
Settings are accessed from Network > WAN, then clicking the Edit button.
Username is in the format of [email protected]
MTU should be set to 1492. No service name is required.
On my modem, I had to enable 802.1q (VLANs) and set the VLAN ID to 40, and the Priority Bit to 0.
You can also check the boxes for the modem to remember these settings even after a factory reset... something the Telus tech apparently did not do.
If you're going to try to get the router to work in bridge mode so you can use your own firewall/router/APs, you will need this information.
Good luck!
9 Replies
PPPOE authentication from the telus modem to the Bell network is using VLAN 40
PPPOE authentication from your own router to the telus modem uses VLAN 35.
It will not work any other way.
Using your modem in bridge mode requires more than just your PPPOE credentials in your own router. You'll be getting into some weeds where some of you have not gone before. In a nutshell, you need to tag your PPPOE packets with VLAN 35 before the modem will authenticate you.
I'm using pfsense and the basic steps were as follows:
- add VLAN 35 and bind it to your physical WAN interface (ix0 in my case). Tag 35, priority 0
- add a new interface and bind it to the new VLAN 35
- On your WAN interface, choose PPPOE and add your credentials below.
This will get you online if your modem is in bridge mode (part or full). If you did partial bridge mode, make sure you picked the right port for your cable.
Telus has complicated things a bit further. PPPOE authentication typically uses PAP authentication (older and less secure) but Telus is using CHAP authentication. Problem is pfsense will keep trying PAP for over a minute or so after reboot before switching to CHAP. This is not an issue per se but pfsense will look offline for well over a minute or so before coming to life with a WAN IP. The logs for PPP will tell you the story.
Every router will need to be configured in this way in order to get bridging to work. You can write scripts to force CHAP over PAP but other than the startup delay, there is no real issue.
I have had zero luck bridging my NH20A to my Flight 2 router. Can't connect by DHCP or PPoE.
I exposed the password field and have my PPoE PW (6 digits?).
Was unable to bridge on either Lan 1 or 10g
Does your router have logs for the PPPoE authentication? If you're in Ontario (Bell last mile), they use PPPoE. I set my NH20A to bridge all interfaces.
From what I've read, some people have had to factory reset the NH20A then put it in bridge mode for it to work.
Bell is using straightforward PPPOE PAP based authentication with no fuss from years ago. This works well and works off any of their modem ports. Their Advanced DMZ mode is known to fail as it's internal NAT routing is flawed and not reliable if it works at all. Only their business modems work properly in this regard. On the residential side, they don't want you to use your own routers.
Flint 2*
