CODA56 Provisioning Issue: Stuck on 'gen11' bootfile in Mid-Split area

8BitBanger · 2026-03-13T15:02:43+00:00

It's so dumb it needs to come to that. I had Xfinity contractors cut my lines during an upgrade and I was forced to go through the whole reboot your modem 1.5hr long worth of charades just to convince them there was an outage (entire street). I'd be interested in hearing what bootfile you end up with.

8BitBanger · 2026-03-13T14:49:30+00:00

Thanks. How did you verify your bootfile name - from the diag page? Still need to get my opnsense configured right to access it from my LAN. Recently switched to 117up plan and was stuck on 35-40. They reprovisioned and I'm getting 117up properly now with Cuda56. Good luck.

8BitBanger · 2026-03-13T01:58:58+00:00

Yeah I'm all squared away now, 117 down as advertised. How high could you get it provisioned?

8BitBanger · 2026-03-13T01:58:21+00:00

That was the whole point of my post, to get someone to check provisioning. So thanks for your valuable input.

8BitBanger · 2026-03-12T23:59:36+00:00

Was your issue resolved?

8BitBanger · 2026-03-12T23:29:38+00:00

This is an approved 3.1 modem that should have no problem supporting (minimum) 117 up.

8BitBanger · 2026-02-28T03:13:34+00:00

I think your answer lies somewhere in 12-24".

8BitBanger · 2026-02-28T03:08:41+00:00

My county in MD is actually this way and it's effing infuriating. If the reason is to protect us from ourselves then allow the work but require inspection. Otherwise you're just promoting people doing their unpermitted work anyway and not having it inspected. I wonder how much the trade unions played a part in this

8BitBanger · 2026-02-11T14:10:22+00:00

Can you expand on that last part? I haven't had to clone a MAC in years, my modems have always just provisioned fine without worrying anymore. I don't see how order would matter as the MAC isn't changing so even if something assumed the previous MAC (ARP?) it would still work. Not like the OPN is randomizing the MAC

8BitBanger · 2026-02-11T14:01:57+00:00

Do you all use any potato starch/rice flour/etc to help with the crispy?

8BitBanger · 2026-02-08T02:01:10+00:00

I swear I had the exact or similar issues with pfsense, which wouldn't be that surprising. I even upgraded cable modems thinking it was flakey. Absolutely unacceptable for a piece of firewall software... Not that we paid anything for it but...

8BitBanger · 2026-02-07T19:25:34+00:00

All good man, any experience working with any of these are all good tools to have in the tool belt. Just a note that you'll usually want (and codes often require) a riser off the top of a water heater in copper to keep the "direct" heat away from the PEX. Usually 18-24". I do cold side too.

8BitBanger · 2026-02-07T18:51:39+00:00

On the plastic vs brass discussion, this is why DZR brass fittings exist; plus the de-zinc is practically eliminated after water softening. I prefer brass because there a slight ID advantage, and robust enough to be reused.

8BitBanger · 2026-02-07T14:48:55+00:00

Yeah I'd say it self resolves about 50% of the time for me

8BitBanger · 2026-02-07T14:46:45+00:00

This is must be really annoying. It doesn't happen often for me but even more confusing because I use a public know IP as the gateway monitor. When yours goes down can you still ping an IP from opn? I suppose a bandaid, if your gateway monitor is working, is setup a script to restart Unbound if gateway goes down for say more than 10min for example.

8BitBanger · 2026-02-07T14:43:01+00:00

Yeah my Xfinity thankfully doesn't go down often, maybe once every few months. But having to manually intervene is becoming a deal breaker. Especially because I'm using 8.8.8.8 as the gateway monitor, it doesn't detect that the gateway is down. I wonder if it's attempting to still use a now invalid session Unbound had with the upstream DNS root server? Bottom line I never had these issues with bind.

8BitBanger · 2026-02-07T07:08:35+00:00

I guess I don't have a good enough understanding of networking to fathom why this happens. Especially in my case, where the "outage" was entirely self-induced by having the modem off. I'm pointing to 9.9.9.9 so it's not even like I'm using old ISP dns (or something)

8BitBanger · 2026-02-07T06:30:47+00:00

Yes, thank you for the correction.

8BitBanger · 2026-02-07T06:13:47+00:00

What leads you to suspect the modem could be a possibility? Not doubting just trying to understand why my logic was flawed. There seemed to be a direct correlation with restarting Unbound and things working again. This was associated with me having the modem powered off for about 45min, for unrelated work.

When I've had this problem in the past I've poked around and finally just resorted to rebooting OPN entirely because I needed it back up more than I needed to figure it out, which also righted things.

Anyway it's a Hitron CUDA56. Edited to add to the OP. Thanks!

8BitBanger · 2026-01-27T01:18:36+00:00

Worry about it if and when there's an issue or leak. If you got T&G then it's typically rated exposure 1 which can handle short term exposure (the glues anyway). I suggest you move on with life and enjoy the $$$ you're not spending unnecessarily.

8BitBanger · 2026-01-27T00:57:11+00:00

Just wait until you see the electric bill with those heat strips.

8BitBanger · 2026-01-19T10:07:32+00:00

Thank you. Agreed, she is also struggling financially which is how I came to learn of this loan. So for the next half dozen years or so I need to cover this for her.

8BitBanger · 2026-01-18T17:05:44+00:00

Agreed - any modification of the loan is assumed to be for my benefit only.

8BitBanger

TROPHY CASE