| 1 |
--- |
| 2 |
features: |
| 3 |
- | |
| 4 |
Support for L3 conntrack helpers has been added. |
| 5 |
|
| 6 |
Users can now configure conntrack helper target rules to be set for a |
| 7 |
``Router``. This is accomplished by associating a ``conntrack_helper`` |
| 8 |
sub-resource to a router. To create a ``conntrack_helper``, the user |
| 9 |
specifies: a router ID, the protocol (TCP or UDP, for example), the port |
| 10 |
number and the conntrack helper module alias (tftp or ftp, for example). |
| 11 |
CRUD operations for ``conntrack_helpers`` are implemented by a Neutron API |
| 12 |
extension and a service plugin. Please refer to the Neutron API reference |
| 13 |
documentation for details. A router can have multiple ``conntack_helpers``. |
| 14 |
|
| 15 |
The new configuration option |
| 16 |
``[l3-conntrack-helpers]/allowed_conntrack_helpers`` allow the operator to |
| 17 |
configure allowed helpers, and the helper protocol constraints. |