Dear Eric Jarrige,
In message 8F000DEB-1AFC-403B-9B00-FA2BFF2E1193@armadeus.org you wrote:
Which new interface do you mean? And why would waiting for it help you?
By interface I mean the changes you mentioned to avoid to have "filesize" and "fileaddr" with the environment variables.
Don't expect this any time soon. Also, I don't see how this would have any influence on your situation.
All I want to tell you is that it's not a good idea to rely on pre-initialization of such dynamically set variables.
"192.168/16 prefix" is only the prefix of the class C private networks. IMHO that means there are 256 class C networks (255.255.255.0) reserved for private networks as mentioned on the same RFC page by "..and third block is a set of 256 contiguous class C network numbers"
I can split the 192.168/16 range in any way I like. We use it as a single 255.255.0.0 masked network. I could as well define it as for 192.168/18 nets, or whatever comes to my mind.
Best regards,
Wolfgang Denk