This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Running a probe behind a NAT66
- Previous message (by thread): [atlas] Running a probe behind a NAT66
- Next message (by thread): [atlas] Running a probe behind a NAT66
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Lorenzo Colitti
lorenzo at google.com
Tue Jun 12 05:19:57 CEST 2018
On Tue, Jun 12, 2018 at 12:13 PM James Andrewartha < jandrewartha at ccgs.wa.edu.au> wrote: > Followed by a discussion on possible ways it might work if the routers > can react to network changes by sending new RAs, which I love would to > know if there are any implementations that can do this. > The more customers ask for it, the sooner and more widely it will be deployed. The alternative is increase costs to application developers by requiring them to implement complex and brittle NAT traversal code, and impose on users the resulting burden of flakier connectivity and the battery impact due to NAT keepalives. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-atlas/attachments/20180612/33135589/attachment.html>
- Previous message (by thread): [atlas] Running a probe behind a NAT66
- Next message (by thread): [atlas] Running a probe behind a NAT66
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]