Because of this "Remember that static-port means you can't have two
machines behind the same NAT using the same source port and destination.",
you should instead probably use "binat-to" as a good practice.
This will help force you to not be able to accidentally reuse the same
public IP for another
On 2016-06-09, Markus Wernig wrote:
> On 06/09/2016 08:03 PM, Bryan Vyhmeister wrote:
>> On Thu, Jun 9, 2016, at 10:48 AM, Markus Wernig wrote:
>>> Short question:
>>> How do I prevent pf from changing the source port of outgoing natted udp
>>> packets?
>>
>> Did you look at static-port in pf.co
On 06/09/2016 08:03 PM, Bryan Vyhmeister wrote:
> On Thu, Jun 9, 2016, at 10:48 AM, Markus Wernig wrote:
>> Short question:
>> How do I prevent pf from changing the source port of outgoing natted udp
>> packets?
>
> Did you look at static-port in pf.conf(5)?
Argh! I had overlooked that. Shame. W
On Thu, Jun 9, 2016, at 10:48 AM, Markus Wernig wrote:
> Short question:
> How do I prevent pf from changing the source port of outgoing
> natted udp
> packets?
Did you look at static-port in pf.conf(5)?
Bryan
> On 09/06/2016, at 18:48, Markus Wernig wrote:
>
> Hi all
>
> I have a strange behaviour in pf on 5.9-stable:
>
> A system (asterisk) behind the gateway is receiving and replying to udp
> streams (RTP). The connection parameters (src/dst ip/port) are set up
> before (STUN and SIP), so both system
5 matches
Mail list logo
