Nat with multiple nat_prefix breaks others when using pf

Thank you for reporting this , can you please create a suggestion type issue in Jira for this ? Thanks again

Addendum: If using the ipfw firewall, this code will also allow multiple nat prefixes:

To be inserted at around line 1611 if the above pf fix isn't also applied, right after the lines that read  f'Inserted: {final_line}{rdrs} into rules at index 1' and the closing parenthesis.

To me, these two miniscule fixes would be sufficient to fully support this feature, so I keep my peace. They're two simple additions I can continue doing by hand each update until a "proper" resolution is found and implemented later. 👍

Yeah no worries. As mentioned I found a workaround above that I can apply that will let me function as desired until the "real" solution is figured out.

thank you for letting me know. In essence i believe you only require static ip's for NAT so that you are able to determine which jail will have which ip on start up ( this means that different nat prefixes aren't required ). However this change requires more work and it could introduce other regressions, so for now we are retargeting it and will consider incorporating this in the future.

Thank you for your input, have a good day!

Correct. I am using multiple prefixes because I need predictable IP addresses for some of the jails so I can have them talk to one another (in this case, sickrage to communicate with deluge), and that's difficult when their IPs change every time they start up.
By using different prefixes, I can ensure (for example) that the internal IP for deluge is always 172.17.0.2, since it's the only one that ever runs in that prefix.

This wouldn't be necessary if iocage would respect the DHCP setting (and whether it was off) and let me specify the IP address manually.