News for hackers. Stuff that matters.
Re:250M-plus reserved IPv4 addresses could be released by justsomehnguy on Friday February 09, 2024 @01:09PM (#39318170)
> So for a quick win, Windows just needs to drop special checks they do for 240/4.

Notging special because it's actually in the routing table, as it should be.

Issue ROUTE PRINT to see it yourself.

Re:250M-plus reserved IPv4 addresses could be released by yardstick on Friday February 09, 2024 @06:01PM (#39321561)
Haven’t checked in a couple years, but can you assign a 240.0.0.1/24 for example to the local NIC on Windows?
Re:250M-plus reserved IPv4 addresses could be released by justsomehnguy on Saturday February 10, 2024 @08:18AM (#39325930)
Assigning is another deal (tested on 2012R2):

    netsh interface ipv4>add add "4084" 200.0.0.1 255.255.255.0

    netsh interface ipv4>add add "4084" 240.0.0.1 255.255.255.0
    The parameter is incorrect.

    netsh interface ipv4>sh add 4084

    Configuration for interface "4084"
        DHCP enabled:                         No
        IP Address:                           200.0.0.1
        Subnet Prefix:                        200.0.0.0/24 (mask 255.255.255.0)
        InterfaceMetric:                      10
The GUI interface explicitly tells to use 'from 1 to 223' for the first octet.