A duplicate of the (now-approved) Networking 101/5: Access Control using a Wildcard mask - I suggest to retire this Kata. If desired, translations can be submitted to the other Kata to make it available in C#, Go and JavaScript (or other languages for that matter).

For subnet with netmask 255.255.255.0, there are 254 valid hosts, not 253 as the description suggests. E.g. in a subnet with network address / netmask 192.168.1.0/255.255.255.0, valid addresses range from 192.168.1.0 through 192.168.1.255 (256 addresses), where 192.168.1.0 is reserved for the subnet itself and 192.168.1.255 is reserved as the broadcast address, hence the number of remaining addresses = 256 - 2 = 254.

startAdress should be startAddress.

I already have updated the description but when it is not yet clear enough I'll try again :) thx for the feedback. In the meantime, you can go trough a blog post which I have created about this topic here but careful, if you don't wan't to spoil yourself, at the end is a solution in go which could be used in this kata.

I'd second this, even after reading the linked wikipedia article and kata description I couldn't figure out how to complete the task whatsoever.

Thx, I have thought about that. Now I am going to change that for all languages :)

( JS, possibly others )

Random tests are there, but value ranges are a bit limited. Please make the network start address and the netmask random also.

Thx, I didn't think about that, there is already a solution which only satisfies the test cases ^^ I'll implement some random tests :)

Yes mabye I should be more specific about that. Thx I'll consider your input at the next correction.

thx for the feed back, I'll correct the code :)

Please follow C# naming conventions:

• Namespace should be in PascalCase. Also using Main as namespace is kind of a bad idea (for obvious reasons)
• Method parameter should be in camelCase

The kata doesn't explain any of the terminologies used in the description, or how is the result determined. Why is 192.168.1.22 true, and why is 192.168.2.5 false? We should not be doing the kata author's job of researching network protocol jargon just to understand the task.

It was fun but hart :D I'd say it would better fit in the 4kyu section :)