Deprecate 0.0.0.0 for Private Network Access

Re:Deprecate 0.0.0.0 for Private Network Access by kevindamm on Wednesday August 07, 2024 @03:16PM (#41184408)

RFC 3330 says you can use it as a source address for "this" host on "this" network, and that 0.0.0.0/8 can be used for other addresses on "this" network.

https://www.rfc-editor.org/rfc/rfc3330

[ Parent | on HN ]

Re:Deprecate 0.0.0.0 for Private Network Access by diggan on Wednesday August 07, 2024 @03:45PM (#41184668)

Interesting. I'd use 192.168.0.0/16 or 10.0.0.0/8 for that, and haven't found a reason yet not to. Using "0.0.0.0" for anything signals something like "I'm not sure what I want to bind it to, just bind to everything available", at least to me.

[ Parent | on HN ]

Re:Deprecate 0.0.0.0 for Private Network Access by marcosdumay on Wednesday August 07, 2024 @04:13PM (#41184920)

It's not a valid machine address. It's a shortcut that, for example, if you are in the 10.0.0.0/8 network, you can use 0.0.0.1 to refer to 10.0.0.1.

[ Parent | on HN ]

Re:Deprecate 0.0.0.0 for Private Network Access by BenjiWiebe on Thursday August 08, 2024 @02:08PM (#41194504)

How come this doesn't work on my Fedora Linux PC? If I try to ping 0.0.0.1 it just tries to ping 0.0.0.1 which doesn't respond as it doesn't exist.

[ Parent | on HN ]

Re:Deprecate 0.0.0.0 for Private Network Access by emptiestplace on Friday August 09, 2024 @12:14AM (#41198717)

Are you /8?

[ Parent | on HN ]

Re:Deprecate 0.0.0.0 for Private Network Access by BenjiWiebe on Saturday August 10, 2024 @12:56PM (#41210720)

Nope, /24.

[ Parent | on HN ]