Aidas Kasparas writes:
Gordon Messmer wrote:+ <para> +This is a limitation in the current implementation of CIDR parsing. +When networks specified in CIDR notation are found in the source file, +they are converted to enumerations of the net blocks or IP addresses +that are members of the specified network, in the format appropriate +for the access file. In the above example, 192.68.0.10 would be +produced as part of this conversion, and would conflict with the later +definition of the same address.</para>If this is true, then for 10.0.0.0/8 we'll get 16M addresses? And for 2002::/16 -- 2^112! Where will we store that much?! Even 2001:x:y:z::/64 (which is realistic when IPv6 will get some steam) is too much to be named individually.
No, /CIDR gets expanded only to the nearest octet boundary. couriertcpd already handles "a.b <entry>" directly. 10.0.0.0/15 gets expanded only to "10.0" and "10.1".
pgpTokncHCHfo.pgp
Description: PGP signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
