Certificate subjectAlternativeName with wildcard IP
certificate, ssl, wildcard
Solution
Here is what RFC 2818 (assuming you're talking about HTTPS) has to say on this:
In some cases, the URI is specified as an IP address rather than a
hostname. In this case, the iPAddress subjectAltName must be present
in the certificate and must exactly match the IP in the URI.
This would exclude usage of wildcard or subnet notations.
The more recent RFC 6125, which aims to harmonise identification across other protocols, explicitly excludes IP addresses from its scope.
This being said, you may find that there are some non-compliant clients out there with their own interpretation (there are some that allow usage of an IP address in the CN of the Subject DN, for example). I wouldn't recommend counting on it generally.
It seems a bit surprising that you'd want to use TLS at all on what you call an "isolated LAN". In addition, if you're in control of that LAN, you could assign names to your machines and use hostname matchine.
Problem
i need create a certificate, which will be used as TLS server authority on any random host in the isolated LAN. Can i use in the subjectAlternativeName field some wildcard for IP instead domains like 10.0.0.255 or 10.0.0.0/24 for that purpose? P.S. any host in the LAN can be client for distributed net of servers, which are can be started on any host and connected to fluid dynamic greed behind load balanser, which manage connections in this crease network )