>Hi, Hi, >Have you considered updating the NETMAP target inside the linux >kernel instead? Nope, I haven't thought about it. It's doable. Classic NETMAP functionality could be available through some rule option. >Your idea looks interesting in that I could envision it superseding >DNAT, SNAT and NETMAP altogether. Thanks :-). >>Polite request to Jan Engelhardt for inclusion of the target into >>xtables-addons. >It would be nice if you could > * resolve the inconsistencies in indentation. Specifically, use tabs >... > * wrap lines at 80 cols in xt_DNETMAP.man Will do. >The manpage mentions "If host 192.168.0.10 generates some traffic, it >gets bound to first free IP in subnet - 20.0.0.0.". However, >20.0.0.0 can be a network address and thus lead to problems. Usage of network and broadcast addresses for NAT shouldn't pose any kind of problems. I tested such setups in my networks. If you use classic NETMAP to map wider address space to shorter one, you can also have flows NATed to network and broadcast address of subnet specified as a parameter of the NETMAP rule. >Is there a way for the user to specify that the range to use >should be 20.0.0.1-20.255.255.254 rather than 20.0.0.0-20.255.255.255? Not yet, but module option could do a trick as long as it's really necessary. Best regards, Marek Kierdelewicz -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
