this post was submitted on 09 Jun 2024
806 points (98.0% liked)
Programmer Humor
19623 readers
507 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I gave it the old college try about 6 months ago. Found out how to send the req for a subnet to my ISP. Configured my opnsense. When it worked, it worked. But it would randomly stop routing regularly. After a lot of troubleshooting determined it was the isp and have up.
Maybe I'll try again in another 6 months.
This is remarkably common. A major factor is how to handle renewals. There appears to either be bugs with the procedure or there's disagreement on how it should be handled. So it will work, for a while, until a renewal needs to happen, then everything goes to shit.
I've directly witnessed this in router/firewall logs. That there's an attempt to renew the DHCP-PD, which does not get a valid reply.
so is there just no standard for renewal? Or are ISPs just refusing to use the standard, for whatever reason?
I can't imagine we don't already have a standard for this shit. I'd be baffled if we didn't. So surely it's just ISPs being their usual, useless selves.
This is less to do with the ISPs and more to do with the implementation of DHCP-PD renewals on various software/hardware devices. I'm not going to point any fingers, but it seems that some vendors don't play very nicely with other vendors.
oh so it's a classic instance of shitty hardware vendors doing shitty software things.
Gotta love technology.
Always has been