> On 07.02.2019, at 14:21, Stuart Henderson wrote:
>
> On 2019-02-06, Patrick wrote:
>> My nat rule use the parenthesis and all other devices behind the
>> firewall works fine. I think it’s more a specific issue with the SPA112.
>> I have also set the ruleset optimization to conservative but i
On 2019-02-06, Patrick wrote:
> My nat rule use the parenthesis and all other devices behind the
> firewall works fine. I think it’s more a specific issue with the SPA112.
> I have also set the ruleset optimization to conservative but in this
> case the generated state has just a longer time to li
> On 06.02.2019, at 11:15, Sebastian Reitenbach
> wrote:
>
> Am Mittwoch, Februar 06, 2019 10:57 CET, jum...@yahoo.de schrieb:
>
>> Hello,
>> I have a Cisco SPA112 VoIP to connect my analog phone to my provider SIP
>> system. Recently I replaced my Linux based (Fritzbox) with a OpenBSD 6.4
I think you need to show your pf rules.
Did you make your firewall aware that your ISP is changing address ?
Am Mittwoch, Februar 06, 2019 10:57 CET, jum...@yahoo.de schrieb:
> Hello,
> I have a Cisco SPA112 VoIP to connect my analog phone to my provider SIP
> system. Recently I replaced my Linux based (Fritzbox) with a OpenBSD 6.4
> firewall. The firewall is connected to a vDSL modem and performs NAT
Hello,
I have a Cisco SPA112 VoIP to connect my analog phone to my provider SIP
system. Recently I replaced my Linux based (Fritzbox) with a OpenBSD 6.4
firewall. The firewall is connected to a vDSL modem and performs NAT for
outgoing IPv4 connection. The connection to the SIP server from the SP
6 matches
Mail list logo
