A place for developers to talk about building on Farcaster.

/dev

I recently bought a Roborock Q5+ Robot Vacuum, but it kept going offline. 

Reddit said I had to configure my DHCP setting in my router to assign the robot a low IP address, so instead of it's auto assigned 192.168.0.100+, I gave it a 192.168.0.10. This worked.

What POSSIBLY could have been the bug in the code?!

Literally everyone in the comments section is shocked that this works. I don't understand how a dev could write networking code that would trip up on a high IP?

Venture Partner at marinventures.com | Security Consultant at horizonslaw.io | Cybersecurity M.S. Candidate at gatech.edu

Literally everyone in the comments section is shocked that this works. I don't understand how a dev could write networking code that would trip up on a high IP?

https://www.reddit.com/r/Roborock/comments/o2nwby/comment/i74y3au/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

co-founder of casaliz.co.jp, work in software/embedded/VR, interested in learning ethereum protocol and L2 development, farcaster.id/hosaka

Yeah I just can't imagine though what would've been that logic? Like they used some netmask that they used something less than /24? I should try wiresharking it.

Some of the development environment logic trickled down into prod? Hard to say without seeing the packet dump. Anything from hardcoded netmask to some ip range check could trigger this.