[Spce-user] Virtual Network Interface as RTP Interface and missing v6gateway

[Richard Fuchs]

On 27/03/2019 06.36, Hohl Matthias wrote:
>
> Hello,
>
> in my test environment I want following setup:
>
> I want 2 network interfaces in the same subnet for ipv4 and ipv6.
>
> So I created 1 main interface eth0 and 1 alias interface (virtual 
> interface) eth0:1
>
> On eth0 the subscriber should connect and on eth0:1 the peering should 
> connect (inbound and outbound)
>
> My Problem:
>
> 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.
>
> eth0:1 for rtp_engine works, but if I generate the config ngcp created 
> an additional eth0 RTP_Interface:
>
> rtp_interface eth0:1_peering=eth0:1_peering is sync between config and db
>
> rtp_interface eth0=eth0 is sync between config and db
>
>          rtp_interface ext=ext is sync between config and db
>
> is this a bug? Normally eth0 is the “ext” interface, so there is no 
> need to generate eth0 as rtp_interface separately.
>
No, that's actually a feature. :)

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.

This is documented under 12.2.4 on 
https://www.sipwise.org/doc/mr6.5.3/spce/ar01s12.html

Cheers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20190327/0aef5504/attachment-0001.html>