Pppoe passthrough is now broken on Open BSD router

[doverosx]

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.

[McIT]

Just echoing your sentiments:

I have a gigahub (Sagecom 5689e) and the firmware recently changed to 2.13; ADMZ is broken and PPPoE via any port results in high latency / packet loss after a short period of time. Both the Gigahub and my personal router (PFsense) have different WAN IPs which seems problematic because the utilization on the gigahub hits 100%. I’m stuck behind the gigahub as that’s the only way it’s usable for now (double NAT) and very close to leaving Bell at this point as the gigahub is terrible. I’ll be asking if I can downgrade to a HH3000 as that seems like the only way around this problem. 

[McIT]

@BellPatricia Are you aware of the Gigahub PPPoE issues with FW 2.13 and is there a fix? If not can we be downgraded to a modem that doesn’t have this problem? It’s basically the last straw for me. 

[dks]

Staff may or may not read this before Monday. Based on what I know, any issues around 2.13 firmware are being collected by staff. Bell has not said when any new firmware will roll out. There are no fixes, to the best of my knowledge, for any issues reported. I understand that tolling back to the HH3000 is not an option, once you have the Giga Hub. 

[McIT]

Thanks for the reply; that’s extremely unfortunate for both me and other customers if true. PPPoE and ADMZ are legitimate features that should be functioning and Bell is absolutely at fault for pushing out an update that breaks expected functionality. 

[BellPatricia]

Hi @doverosx 

Thanks for your reply and for the additional information.

I have sent you a private message so we can discuss this a bit further. Please check your Messages within your profile avatar in the top right corner.

Unsure how to check or send a private message? See How to send a private message

@BellPatricia 

[McIT]

I know your reply was targeted at the original poster but a number of other users are also experiencing this same issue as well. Are we able to message you for support as well?

[alexricher]

Wondering the same, as I'm unable to get a stable DMZ or PPPoE connection since this new firmware. I'm stuck in double NAT so I can get a connection without too many issues.

[bober101]

came in just to say i had the same thing happen to me. except i thought my b1 username had changed so i went in by bell portal and changed it and then everything stopped working. the gigahub could no longer save the credentials worked with support for a good hour and i was told the modem was the issue. went to a bell shop to get a new one and that one worked but my pfsense/whole home network is down. i work from home and am on an important project and this crap had to happen the day before a golive so had to take part of the day off to deal getting a new hub. I have resulted to use the gigahub out of sheer desperation. with my IoT and servers unreachable plus without pfblockerng ng, I'm swamped with ads and have access to none of my local media, i have no time to set every back up the stupid way. i no longer see why i should stay with bell when their updates affecting my livelihood..i really really didn't need this to happen right now... why oh why did bell have to integrate the sfp in this hub....

[B1pppoeUser]

I'm having the same issue.  Pings are crazy high and erratic  Speed is generally fine but the latency and timeouts are making it unusable.  Willing to help testing betas or or anything that's needed to make this work. 

I have an active ticket open but tech support doesn't really know what's going on except to send a tech to fix the cable which isn't the issue.  The issue is in pppoe mode the gigahub is at 100% CPU and the load average is over 10 causing it to not be able to send/receive data as it should.

Please reach out to me.

[dks]

Thank you for your experience. Bell staff is aware of the Giga Hub CPU usage issue and has passed it on. To the best of my knowledge, there is no word on a resolution, but it has been noted. 

[Vanadiel]

I am curious if anybody with the home hub have tried the secret bridge mode? I have heard mixed results from it, but it's worth a try if you understand what you are getting in to.

[alexricher]

I'm in Quebec and my Giga Hub doesn't seem to support it. I've seen a Youtube video of someone (in Ontario with Bell Alliant?) was able to hold the RESET + OK button to bring it into "Bridge Mode", but mine doesn't seem to support it. The closest I can get is pressing RESET + UP (or DOWN) and I see the "Keep holding for 7 secs" (or something like that, I go from memory) and it simply states "Bridge Mode Disabled". So, no luck on my end.

Really, thus far, double NAT was the only way I get a somewhat stable internet, but I've lost it a few times this week where I had to do a factory reset; otherwise, my Giga Hub would get back onto 192.168.2.x network, conflicting with my own router. It does this randomly, and once I factory reset it, I'm good for a few days. But don't try DMZ as it'll be too unstable... and PPPoE simply won't work for my anymore.

[Vanadiel]

Pending on your setup, you could disable the DHCP server on your router so the home hub is the only DHCP server, or you could move the DHCP range on your router to start at 192.168.2.10. Or you could move the range completely outside the 192.168.2.x range to avoid conflicting with the DHCP range of the home hub.

That would at least avoid the network issues after a factory reset of the giga hub.

[doverosx]

PM sent, will be back in Canada February 9th.

[McIT]

Let me save those with issues all some time as I just wasted a week with Bell / Executive - Complaints:

- Was initially told I would have a tech sent out with a HH3000

- got an appointment, took time off for it, has a number of back and forth calls with various bell agents, loyalty and complaints; no downgrades are allowed from Gigahub.

- Tech came and said he could only give me the exact same model Gigahub, he reset my modem, PPPoE pass through is still broken on my Gigahub - Sagecom 5689E. Told me that “bridge mode” is only for business customers and out of scope / is locked out on the Gigahub.
- Was also told by complaints that PPPoE pass through might be a business feature; I replied that it’s a standard connectivity method that has been used for quite some time / was functional till the latest firmware update. Was told I could wait for a firmware fix or possibly research it myself (lol).
- Final Note: Bridge mode is locked out by design and no secret key combo or back end enable is possible for residential service. 

 FYI: Distributel and Ebox, who resell Bell fiber, offer the Nokia ONT XS-010-XQ which appears to work just fine with PPPoE. Older HH3000 appear to be unaffected by this gong show.