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.
Leave a comment
on 2012-04-06 16:12 *
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
on 2012-04-07 09:42 *
By scott.clasen
Added tests, pull req updated
on 2012-04-09 09:44 *
By scott.clasen
Simplified per conversation with Viktor to only use a single public-addresses config property.
This hasn't been fixed AFAIK
on 2012-05-10 10:07 *
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
but as Viktor mentions here https://github.com/akka/akka/pull/396 (closed,unmerged) this needs some thought around getting the public-addresses correct
on 2012-06-08 04:46 *
By Jonas Bonér
What is the status here?
on 2012-06-08 04:48 *
By viktorklang
Not fixed
on 2012-06-08 09:47 *
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
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
on 2012-06-08 10:04 *
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,
√
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,
√
on 2013-01-26 02:24 *
By viktorklang
If you have a solution for this problem, please don't hesitate to outline it here or via a PullRequest.
Cheers,
√
Cheers,
√