Oh, I just love you! 
Not only did this resolve the issue with not being able to access the dev server on the network but another one I’ve been almost pulling my hair out 
YMMV but I’ve always been a fan of Browsersync for this very reason: Most of the time it just works.
No idea if my permalink and assets problem is caused by Apache or some interference by it but the fact that not many users seem to have similar problems hints there.
The only issue I’m having now is that I can’t access the Browsersync dashboard (usually located at localhost:[port+1]) but that’s just a minor thing 