Re: NAT replies not triggering pf rule

On 10/27/15 3:42 AM, Stuart Henderson wrote: On 2015-10-26, Giancarlo Razzolini wrote: I suggest you move your match rules to the beginning of the ruleset and use log on them. So you can watch your pflog interface and see the packets being triggered. Also, you can

Re: NAT replies not triggering pf rule

Because there will never be a packet on gem0 with destination 192.168.1.64. The packets are being natted, aren't they? Try using tags, your life will be much simpler. I tried tags in an earlier iteration of this. Didn't help. As a simpler test, I revised the rule for packets leaving gem0 to

Re: NAT replies not triggering pf rule

On 10/26/15 8:12 AM, Giancarlo Razzolini wrote: Are you aware that you'll need to have a queue on the internal interface and another on the egress one right? Queuing incoming packets is very tricky and not always have the desired effect. I suggest you start with prio and see where it leads you:

NAT replies not triggering pf rule

I've worked with this off and on for some time, but still don't know what I'm not doing correctly. I want to set queues to limit bandwidth for the streaming media devices on my home network. Unfortunately, the "pass out" rules on my internal network (external is PPPoE) don't ever trip for

Re: qemu-i386 error on OpenBSD 5.8 amd64

On 10/25/15 3:37 PM, ilyes aiouaz wrote: Hi every body, qemu-i368 prensent this error when I run it on OpenBSD 5.8 amd64 stable and patched : *(qemu-system-i386:18034): GLib-ERROR **: gmem.c:103: failed to allocate 592 byte* Can you help me, I have no problem on OpenBSD 5.7 amd64 stable and