Uploaded image for project: 'TrueNAS'
  1. TrueNAS
  2. NAS-102695

Nat with multiple nat_prefix breaks others when using pf

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Engineering Closed (View Workflow)
    • Priority: Low
    • Resolution: Won't Do
    • Affects Version/s: 11.3-BETA1
    • Fix Version/s: N/A
    • Component/s: Middleware
    • Labels:

      Description

      When setting a different prefix for nat_prefix (for the purpose of making the resultant NAT IP consistent), the last jail to start gets its prefix as the one that can NAT out, while others do not.

      One possible solution would be to support not-psuedo-DHCP-ing the jail's IP (if the DHCP option is not checked but NAT is checked) so that the need to jerry-rig multiple nat_prefix-es would go away.

      I'm not sure if the pf firewall lets you configure multiple nats, but in theory it could also involve merely letting more than one nat on igb0 from 172.16.0.0/24 to any -> (igb0:0) static-port entry on the list (one for each prefix).

       

      I haven't tested what happens on ipfw because I couldn't get it to work yet.

        Attachments

          Attachments

            JEditor

              Activity

                People

                Assignee:
                releng Triage Team
                Reporter:
                Tsaukpaetra Anthony Takata
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: