[Spce-user] Possible Bug? - NGCP Firewall in mr6.5.3

Hohl Matthias matthias.hohl at telematica.at
Tue Apr 2 11:04:19 EDT 2019



this i have to add in the config.yml file unter security > firewall > rules4   right?


Funny thing… also if I have nothing there inside for my eth1 I can place calls and receive calls over this eth1… and also ping it etc… like there is everything accepted???


Von: Spce-user <spce-user-bounces at lists.sipwise.com> Im Auftrag von Richard Fuchs
Gesendet: Dienstag, 2. April 2019 16:58
An: spce-user at lists.sipwise.com
Betreff: Re: [Spce-user] Possible Bug? - NGCP Firewall in mr6.5.3


On 02/04/2019 10.46, Hohl Matthias wrote:

Hello again,


eth1 has type:



      - sip_ext_incoming

      - rtp_eth1_peering


These are non-standard interface types. The firewall script only generates rules for standard interface types (such as `sip_ext` or `rtp_ext`) but not custom types that you create yourself. You'll have to create your own rules for these.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20190402/f76a17ce/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5585 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20190402/f76a17ce/attachment-0001.p7s>

More information about the Spce-user mailing list