Pppoe passthrough is now broken on Open BSD router

doverosx
Contributor III

I’m in Barrhaven on Bell Fibe and it’s been great, using pppoe passthrough (OpenBSD router) with no issues for a while now.

This weekend, I’ve been getting disconnects, crazy high pings and more. Anyone else have problems?

I’ll be *trying* a direct connection to the modem in a bit.

 

 Using just the modem seems to have resolved the issue so Bell broke something nicely.

 

1 117 12.4K
117 REPLIES 117

JB1
Contributor III

Its funny i left rogers for bell because they had fiber in my neighborhood but because they don’t support pppoe anymore (without any heads up either) there isnt inherently a big advantage because my wifi speeds are so limited by their routed that i am forced on.

Very frustrating to have deal with this again.  Appreciate the bell team in here trying to move the machine to help us out. 

 

Doesn't exist on the newest firmware anymore.

bober101
Contributor II

I fail to see how "acting" on bell's behalf and in essence downplaying all these issues is helping anyone BUT the customers.

you have no proof management is aware and event at that, will take any action.

we need more voices, not less.

JB1
Contributor III

I don't think you understood my message.  I am not downplaying my issues im saying that this is significant enough that its worth reexploring my old relationship with Rogers since they arent supporting the fibre speeds that brought me over in the first place.

electricsheep
Contributor II

this is happening for me as well on pppoe.  Without resetting the modem once an hour, eventually pinging Google gets timed out completely.

I'm going to be forced to switch to Rogers pretty soon

dks
Community All-Star
Community All-Star

Bell staff in this forum have said they are aware of the issue. That is about as far as it can be taken here, as it is a user to user forum that does not interface with the technical or engineering side. Bell has never announced changes to their equipment other than big things like fibre roll out. If a manufacturer’s solution is offered, it will take time and it may not be quick. I recall the old IT logic; Good. Fast. Cheap. Choose any two. 

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.

dks
Community All-Star
Community All-Star

Thank you for your summary. You have said exactly what we know about the situation. 

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.

                                                                                          Even if bell said they're aware of the issue, replies to this forum     would help bring more exposure to this issue to the general public. And most importantly could serve as PR leverage to force Bell to do fix this should the media become aware.         

McIT
Contributor II

For those with this issue, file a complaint:

https://support.bell.ca/resolve-a-concern

you might not get a solution but at the very least it’ll help them become aware at a different level of how many people are encountering the issue. 

It seems like many people are having the same issue.  CPU on the GH is 100% with a huge load average.  Pings are terrible.

My router is 10.10.60.254
Tracing route to one.one.one.one [1.1.1.1] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.10.60.254
2 441 ms 1 ms 2 ms 10.11.2.89
3 * * * Request timed out.
4 811 ms 494 ms 496 ms 10.115.17.229
5 * * * Request timed out.
6 323 ms 483 ms 14 ms 64.230.59.212
7 18 ms 484 ms 7 ms 142.124.127.209
8 240 ms 761 ms 502 ms 142.124.127.39
9 405 ms 7 ms 482 ms 108.162.239.32
10 438 ms 6 ms 480 ms 108.162.239.4
11 475 ms 7 ms 234 ms one.one.one.one [1.1.1.1]

Example 2 - 1885ms!!! to 10.11.2.89.

Tracing route to one.one.one.one [1.1.1.1] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.10.60.254
2 1885 ms 512 ms 5 ms 10.11.2.89
3 * * * Request timed out.
4 1149 ms 498 ms 516 ms 10.115.17.229

This is before when I had a HH2000.  After the conversation to the GH.  There was no networking changes on my end.

Screenshot 2025-02-01 115419.jpg

 

2222
Contributor

I'm affected by this, it's been getting worse.

early January it would cut out maybe once a day,
couple days ago it would cut out once every few hours.
I replaced the modem after calling 2 support agents (First one was dismissive of pppoe since it's not officially supported)

Now it happens multiple times in the hour...

I am in Hamilton, Ontario and I just got FTTH in November. As soon as it was enabled I signed up for the service.  As soon as I got the Giga Hub, I put it into Bridge mode by holding OK + Reset button for 7 or more seconds and have been using PPPoE via my Unifi UDM Pro without any issues.  As of Feb 5, I noticed that there is an error message on the screen that says "Upgrade Failed" and am now wondering if restarting the Giga Hub to clear the message will force the upgrade and then disable the bridge mode capability.

B1pppoeUser
Contributor II

I wouldn't chance it.  If its working leave it as is.  The tech told me that bridge mode is not supported and that its not a feature. So I can only assume they removed the feature and don't plan on bringing it back. 

You might be able to tell by going into the Giga Hub console and checking the firmware version. The bridge mode hack has been generally put to rest but PPPoE passthrough is enabled in the Giga Hub, 

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.

JB1
Contributor III

PPPOE May work for them but it might also be broken like everyone else in this thread who is complaining about it recently (myself included).