#1552
  • Created on
    2011-12-19 19:50
  • Reported by
    viktorklang
  • Status
    New
  • Priority
    Normal (3)
  • Assigned to
    -
  • Milestone
    Backlog
  • Plan Level
    -
  • Due Date
    -

Attachments

Related Tickets

Add new subtask or bug

NAT Firewall for remote actors

Create a section of the conf that the Netty remoting will use to filter inbound messages for NAT:ed machines.
User picture
  on 2012-04-06 18:42 *
By viktorklang
Assigned to set to scott.clasen
Description changed from Create a section of the con... to Create a section of the con...
Milestone changed from Thoughtstorming to 2.1
Summary changed from Firewall for remote actors to NAT Firewall for remote actors
User picture
  on 2012-04-06 18:42 *
By viktorklang
Status changed from New to Test
https://github.com/akka/akka/pull/396
User picture
  on 2012-04-07 12:12 *
By scott.clasen
Added tests, pull req updated
User picture
  on 2012-04-09 12:14 *
By scott.clasen
Simplified per conversation with Viktor to only use a single public-addresses config property.
User picture
  on 2012-05-10 06:53 *
By Jonas Bonér
Status changed from Test to Fixed
User picture
  on 2012-05-10 06:55 *
By viktorklang
Status changed from Fixed to Accepted
This hasn't been fixed AFAIK
User picture
  on 2012-05-10 12:37 *
By scott.clasen
There is a possible implementaion here https://github.com/ticktock/akka/tree/wip-nat-friendly-remote-support

but as Viktor mentions here https://github.com/akka/akka/pull/396 (closed,unmerged) this needs some thought around getting the public-addresses correct
User picture
  on 2012-06-08 07:16 *
By Jonas Bonér
What is the status here?
User picture
  on 2012-06-08 07:18 *
By viktorklang
Not fixed
User picture
  on 2012-06-08 12:17 *
By scott.clasen
Viktor-

Is there any guidance you have here for me to do any further work, or do you want to take this one from here?

SC
User picture
  on 2012-06-08 12:34 *
By viktorklang
I'm afraid I won't be able to tackle this any time soon, Scala 2.10-M4 is going out the door shortly and I have a lot of work to do to be able to ship Akka 2.1-M1.

The guidance I can give is that all code that assumes things around host/port combinations needs to be inspected so that behavior doesn't change inadvertently. Please refer back to the discussion we had on this earlier. If you have any questions don't hesitate to ask.

Cheers,
√
User picture
  on 2012-09-10 02:57 *
By Patrik Nordwall
Priority changed from Normal (3) to Low (4)
User picture
  on 2012-11-01 08:28 *
By viktorklang
Priority changed from Low (4) to Normal (3)
User picture
  on 2012-11-01 08:28 *
By viktorklang
Milestone changed from Coltrane to Backlog
User picture
  on 2013-01-25 17:47 *
By OlegYch
any update on this? this is actually preventing not only usage behind NAT, but also simpler cases like binding to 0.0.0.0
User picture
  on 2013-01-26 05:54 *
By viktorklang
If you have a solution for this problem, please don't hesitate to outline it here or via a PullRequest.

Cheers,
√
User picture
  on 2013-03-21 20:26 *
By viktorklang
Status changed from Accepted to New
User picture
  on 2013-03-21 20:26 *
By viktorklang
Assigned to changed from scott.clasen to -none-