On Wed, Nov 22, 2017 at 08:15:50PM +0100, Michael Tuexen wrote: > > On 22. Nov 2017, at 19:55, Marcelo Ricardo Leitner <marcelo.leitner@xxxxxxxxx> wrote: > > > > On Thu, Nov 16, 2017 at 03:21:55PM +0000, Butler, Peter wrote: > >> Are there any Linux tools/tricks/hacks that would allow us to setup > >> a multi-homed association through a NAT? > > > > Not really, because > > > >> > >> I am aware of the information in the SCTP Applicability Statement > >> (RFC 3257), however the NAT in question does not have an internal > >> Application Layer Gateway (ALG) capable of intelligently translating > >> the additional IP addresses embedded within the INIT and INIT ACK > >> chunks (only the addresses in the IP header are translated). As > >> such, these additional address do not get translated to addresses > >> that the remote end understands. > > > > If you're really leveraging multi-homing, the router doing NAT for the > > INIT chunk may not even know the public address for the other path, > > rendering it unable to do the translation even if it knew how to > > mangle the INIT chunk. > > > > And the router on the secondary path may not know about the > > association at all until a HEARTBEAT or so comes through. > > > > In order to do it right we need > > https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-natsupp > > but we don't have that. (note that even the VTAG should be translated) > Neither the SCTP port number nor the vtag are translated. The > idea is to use the vtag as part of a connection identifier to deal > with port number collisions. Is it some recent change? Because my reading of https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-natsupp#section-4.3 still gives me the understanding that vtags are translated. I don't remember how/where to check new developments on the draft when they are not yet published, sorry. Best regards, Marcelo > > Best regards > Michael > > > > As already suggested, probably setting up tunnels between the > > endpoints and avoiding the translation at all is a better way to go. > > > > Marcelo > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-sctp" in > > the body of a message to majordomo@xxxxxxxxxxxxxxx > > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html