<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
span.E-MailFormatvorlage18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.E-MailFormatvorlage20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.E-MailFormatvorlage21
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=DE-AT link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='color:windowtext'>Aah okay… <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:windowtext'>I forgot about 12.2.4 in this way… so to “disable” this I have to choose a rtp interface name without “:” in it </span><span lang=EN-US style='font-family:"Segoe UI Emoji",sans-serif;color:windowtext'>😊</span><span lang=EN-US style='color:windowtext'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:windowtext'><o:p> </o:p></span></p><p class=MsoNormal><i><span lang=EN-US style='font-size:9.0pt'> rtp_interface eth0_1_peering=eth0_1_peering is sync between config and db<o:p></o:p></span></i></p><p class=MsoNormal><i><span lang=EN-US style='font-size:9.0pt'> rtp_interface ext=ext is sync between config and db<o:p></o:p></span></i></p><p class=MsoNormal><i><span lang=EN-US style='font-size:9.0pt'> smsc_peer default_smsc=default_smsc is sync between config and db<o:p></o:p></span></i></p><p class=MsoNormal><span lang=EN-US style='color:windowtext'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:windowtext'>done… is working.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:windowtext'>Also v6gateway I insert. Also works now.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:windowtext'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:windowtext'>So dealing in this way with eth0 and eth0:1 is the productive way, right?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:windowtext'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:windowtext'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=DE style='color:windowtext;mso-fareast-language:DE-AT'>Von:</span></b><span lang=DE style='color:windowtext;mso-fareast-language:DE-AT'> Spce-user <spce-user-bounces@lists.sipwise.com> <b>Im Auftrag von </b>Richard Fuchs<br><b>Gesendet:</b> Mittwoch, 27. März 2019 12:28<br><b>An:</b> spce-user@lists.sipwise.com<br><b>Betreff:</b> Re: [Spce-user] Virtual Network Interface as RTP Interface and missing v6gateway<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On 27/03/2019 06.36, Hohl Matthias wrote:<span style='mso-fareast-language:DE-AT'><o:p></o:p></span></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal><span lang=EN-US>Hello,</span><o:p></o:p></p><p class=MsoNormal><span lang=EN-US> </span><o:p></o:p></p><p class=MsoNormal><span lang=EN-US>in my test environment I want following setup:</span><o:p></o:p></p><p class=MsoNormal><span lang=EN-US> </span><o:p></o:p></p><p class=MsoNormal><span lang=EN-US>I want 2 network interfaces in the same subnet for ipv4 and ipv6.</span><o:p></o:p></p><p class=MsoNormal><span lang=EN-US> </span><o:p></o:p></p><p class=MsoNormal><span lang=EN-US>So I created 1 main interface eth0 and 1 alias interface (virtual interface) eth0:1</span><o:p></o:p></p><p class=MsoNormal><span lang=EN-US>On eth0 the subscriber should connect and on eth0:1 the peering should connect (inbound and outbound)</span><o:p></o:p></p><p class=MsoNormal><span lang=EN-US> </span><o:p></o:p></p><p class=MsoNormal><span lang=EN-US>My Problem:</span><o:p></o:p></p><p class=MsoNormal><span lang=EN-US>If I create a second network interface like eth1 instead of eth0:1 I have a problem with routing, cause same IP addresses are in the same subnet, so I have to create the alias eth0:1.</span><o:p></o:p></p><p class=MsoNormal><span lang=EN-US>eth0:1 for rtp_engine works, but if I generate the config ngcp created an additional eth0 RTP_Interface:</span><o:p></o:p></p><p class=MsoNormal><span lang=EN-US> </span><o:p></o:p></p><p class=MsoNormal><span lang=EN-US> rtp_interface eth0:1_peering=eth0:1_peering is sync between config and db</span><o:p></o:p></p><p class=MsoNormal><span lang=EN-US> rtp_interface eth0=eth0 is sync between config and db</span><o:p></o:p></p><p class=MsoNormal><span lang=EN-US> rtp_interface ext=ext is sync between config and db</span><o:p></o:p></p><p class=MsoNormal><span lang=EN-US> </span><o:p></o:p></p><p class=MsoNormal><span lang=EN-US>is this a bug? Normally eth0 is the “ext” interface, so there is no need to generate eth0 as rtp_interface separately.</span><o:p></o:p></p></blockquote><p>No, that's actually a feature. :)<o:p></o:p></p><p>The colon has a special meaning in RTP interface names. The idea is that if an interface is named `foo:bar`, then an additional pseudo-interface `foo` is created for load balancing purposes. If multiple interfaces are named in this way, let's say `foo:bar`, `foo:quux`, and `foo:baz`, then selecting `foo` as RTP interface in the preferences will make rtpengine use all of those 3 interfaces in a round-robin fashion.<o:p></o:p></p><p>This is documented under 12.2.4 on <a href="https://www.sipwise.org/doc/mr6.5.3/spce/ar01s12.html">https://www.sipwise.org/doc/mr6.5.3/spce/ar01s12.html</a><o:p></o:p></p><p>Cheers<o:p></o:p></p></div></body></html>