7 Jul
2020
7 Jul
'20
5:39 a.m.
Hello,
Yeah that’s what I’m thinking.
This is on AWS where i added a secondary IP to the instance, wanting to
segregate the “public” and “private”
But under the hood they’re both private IPs able to reach the private
network, and that’s where my problem comes, because the OS simply selects
the first interface, not the secondary.
So only solution long-term that doesn’t need the deployer to fiddle with
network route tables, etc. is just to actually separate them.
Thanks all!
David
On Tue, 7 Jul 2020 at 08:39, Patrick Wakano <pwakano(a)gmail.com> wrote:
Check your output to the command "ip route show
table local".
For a connected network, the kernel will select the source IP based on
these rules. From memory I think, it is possible to change the "src"
parameter to use a different IP, so you can play with that.
Anyway, as a general rule, I don't think having multiple IP addresses on
the same subnet is a good practice. I would recommend breaking that into
multiple subnets so you won't fall under these edge cases.
Cheers,
Patrick
On Sun, 5 Jul 2020 at 15:33, Sergey Safarov <s.safarov(a)gmail.com> wrote:
--
Regards,
David Villasmil
email: david.villasmil.work(a)gmail.com
phone: +34669448337
you can also look
https://www.usenix.org/system/files/login/articles/login_summer16_10_anders…
On Sun, Jul 5, 2020 at 8:02 AM Sergey Safarov <s.safarov(a)gmail.com>
wrote:
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Required configure police based routing
https://www.drdobbs.com/policy-routing-in-linux/199100936
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/ht…
On Sun, Jul 5, 2020 at 2:54 AM David Villasmil <
david.villasmil.work(a)gmail.com> wrote:
Kamailio (SER) - Users
Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
I know this is more of a networking routing
question, just trying to
see if you can find a better solution than re-architecturing the network.
Although maybe that’s the best approach, since this is a pretty new setup.
Maybe it’s better to do it now and not using work-arounds?
On Sun, 5 Jul 2020 at 00:39, David Villasmil <
david.villasmil.work(a)gmail.com> wrote:
> Hello guys,
>
> I have rtpengine running on a box with ips like this:
>
> external: 172.10.0.10 (advertise 10.10.10.1)
> internal: 172.10.0.11
>
> Both Ips are on the same network.
> When i do rtpengine_manage i set "direction=external
> direction=internal", and the SDP offer is correct.
>
> The problem I'm having is that when rtp tried to send to the internal
> network, the OS (i believe) selects the first interface (external) ip
> 172.10.0.10 to reach the internal network.
> This I suppose is not a great deal, but I would like to separate them
> and only use the internal for internal proxying.
>
> Help is appreciated!
>
> Thanks!
>
> Regards,
>
> David Villasmil
> email: david.villasmil.work(a)gmail.com
> phone: +34669448337
>
--
Regards,
David Villasmil
email: david.villasmil.work(a)gmail.com
phone: +34669448337
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________