Seems like a TCP/IP stack issue rather than a browser issue... 0.0.0.0 is not supposed to be a valid address (in fact, no IPv4 address with 0
as the first octet is a valid destination IP). The network stack should be dropping those packets.
0.0.0.0
is only valid in a few use cases. When listening for connections, it's a placeholder that means "listen on all IPs". It's also used as the source address for initialization where the system doesn't have an IP yet (eg for DHCP). That's it.