@jonty oh god it was SO WEIRD
he's got a new solar inverter and battery setup.
it's doing some sort of weird backwards-ass network switching onboard, where it acquires an IP address over DHCP but then has a second IP at whatever the last DHCP-assigned octet is times 4. and then it sends so much UDP broadcast traffic that it kills the router's DHCP service and prevents anything else from getting an address, even though everything with an IP can route just fine.
@jonty reading some background to the problem and I suspect I'm about to be debugging a very strange broadcast storm.
@jonty oh god it was SO WEIRD
he's got a new solar inverter and battery setup.
it's doing some sort of weird backwards-ass network switching onboard, where it acquires an IP address over DHCP but then has a second IP at whatever the last DHCP-assigned octet is times 4. and then it sends so much UDP broadcast traffic that it kills the router's DHCP service and prevents anything else from getting an address, even though everything with an IP can route just fine.
@gsuberland @jonty If the last octet primary address is greater than 64 decimal it does ... what?
@gsuberland impressively cursed
@jonty but it also connects over both WiFi and wired at the same time and once you connect to WiFi you can't tell it to drop the WiFi. I had to set up a hotspot on my phone, switch it over to that, and then just turn the hotspot off to "disable" the WiFi part.
@jonty on top of this it turns out the issue is super widely known and the company's response is "not our problem".
apparently the only reliable fix anyone has found is either using a switch with broadcast storm filtering and QoS to reduce the insane amount of broadcast traffic, or just to VLAN the thing off entirely.
@gsuberland What the hell is it actually broadcasting??
@gsuberland @jonty to this whole thread: what the actual fuck
News and community around mavnn.eu projects.
