[
https://issues.apache.org/jira/browse/MESOS-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314529#comment-14314529
]
Dominic Hamon commented on MESOS-1956:
--------------------------------------
when we wrote the port mapping isolator, it was to deal with the constraint of
having not enough IP addresses. If we have IPv6 available, we should be able to
ensure each container gets its own IP address so the port mapping isolator
shouldn't be needed.
when we initialize the port mapping isolator, can we check if we're in IPv4 or
IPv6 world? I'm ok with the port mapping isolator only working in IPv4.
[~idownes] do you agree?
> Add IPv6 & ICMPv6 libnl traffic control U32 filters
> ---------------------------------------------------
>
> Key: MESOS-1956
> URL: https://issues.apache.org/jira/browse/MESOS-1956
> Project: Mesos
> Issue Type: Task
> Components: isolation
> Reporter: Evelina Dumitrescu
> Assignee: Evelina Dumitrescu
>
> For IPv6, the filtering should be done by source and destination ports,
> destination IP, destination MAC.
> For ICMPv6, the filtering should be done by protocol and destination IP.
> The IPv6/IPv4 difference could be done by the source/destination IP type from
> the classifier.
> IPv4 packets with options in the header are currently ignored due to a bug in
> libnl. It should be investigated if the problem occurs in the case of IPv6.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
