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

Richard Fuchs rfuchs at sipwise.com
Tue Apr 2 11:45:51 EDT 2019

On 02/04/2019 11.33, Hohl Matthias wrote:
> Hmm…
> How can i check what is all under “RELATED, ESTABLISHED”..?
> I use the eth1 interface just for my peering.
> So I defined a extra socket with the eth1 IP address in the config.yml 
> and set this for outbound socket in my peering settings and also use 
> the rtp interface rtp_eth1_peering in the peering settings for rtp 
> traffic.
> Is this just a “related, established” case?
> The peering itself is connected via ip authentication.
Incoming responses to packets that you sent yourself would count as 
belonging to an "established" connection, yes.

If you really want to know which packets are matched by which rule, you 
can add a custom "TRACE" rule in the "raw" iptable, and then the kernel 
will produce logs with all the details. Not recommended for the faint of 
heart, but you can find tutorials for this online, e.g. 


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

More information about the Spce-user mailing list