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 <[email protected]> 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 <[email protected]> wrote: > >> you can also look >> >> https://www.usenix.org/system/files/login/articles/login_summer16_10_anderson.pdf >> >> On Sun, Jul 5, 2020 at 8:02 AM Sergey Safarov <[email protected]> >> wrote: >> >>> 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/html/configuring_and_managing_networking/configuring-policy-based-routing-to-define-alternative-routes_configuring-and-managing-networking >>> >>> >>> On Sun, Jul 5, 2020 at 2:54 AM David Villasmil < >>> [email protected]> wrote: >>> >>>> 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 < >>>> [email protected]> 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: [email protected] >>>>> phone: +34669448337 >>>>> >>>> -- >>>> Regards, >>>> >>>> David Villasmil >>>> email: [email protected] >>>> phone: +34669448337 >>>> _______________________________________________ >>>> Kamailio (SER) - Users Mailing List >>>> [email protected] >>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>> >>> _______________________________________________ >> Kamailio (SER) - Users Mailing List >> [email protected] >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> > _______________________________________________ > Kamailio (SER) - Users Mailing List > [email protected] > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- Regards, David Villasmil email: [email protected] phone: +34669448337
_______________________________________________ Kamailio (SER) - Users Mailing List [email protected] https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
