-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow specifying multiple IP addresses for 1-1 NAT. #2279
Conversation
Thanks! This does seem useful, but I'll have to do a deeper review, since there's a lot of new code. I'm a bit busy these days, so that may take a while. Please ping me if I haven't come back to you in a few days. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did a first review, and added a few notes. I think the way the IPs are added/kept should be changed, you can find more details in the comments.
Thanks for your feedback, all comments addressed. Public IPs are now stored in a |
Should I rebase now or do you want to finish your review first? |
I won't be able to do another review today, sorry... I'll check again tomorrow. |
No worries, take your time. I can rebase whenever you are ready with the review. |
I added a small note. The code looks fine to me (I'll test after it's rebased, before I merge), I'm just a bit concerned by the fact we now have a bunch of |
This can be used if Janus is deployed in a DMZ between two 1-1 NAT firewalls for external and internal users.
2514f0a
to
f7eb60d
Compare
Thanks! I'll make a couple of tests after lunch and merge if I don't spot anything strange 👍 |
Just made a few tests and it seems to be working as expected, merging! |
This can be used if Janus is deployed in a DMZ between two 1-1 NAT firewalls for external and internal users.
I am using something like this for the scenario described in https://groups.google.com/d/msg/meetecho-janus/x-LhB_cTs7k/fHT4i5pzBQAJ