Re: altq priq Anomaly

2007-07-22 Thread Daniel Melameth
On 7/22/07, Stuart Henderson <[EMAIL PROTECTED]> wrote: On 2007/07/20 15:20, Daniel Melameth wrote: > then go back to the broken behavior sometime later. A reboot of the box or > removing altq is the only way to resolve the issue, temporarily. I've tried > both priq and cbq, adjusting tbrsize,

Re: altq priq Anomaly

2007-07-22 Thread Daniel Melameth
A recompile of pfstat has addressed this. On 7/22/07, Daniel Melameth <[EMAIL PROTECTED]> wrote: Thanks for taking the time to reply. I can't readily do a snapshot now, but since I am using apmd, I'll try this avenue first and see what happens. I also went ahead and incorporated your diffs int

Re: altq priq Anomaly

2007-07-22 Thread Stuart Henderson
On 2007/07/20 15:20, Daniel Melameth wrote: > then go back to the broken behavior sometime later. A reboot of the box or > removing altq is the only way to resolve the issue, temporarily. I've tried > both priq and cbq, adjusting tbrsize, recompiling the kernel with a higher > HZ value and using

Re: No route to host

2007-07-22 Thread Stuart Henderson
On 2007/07/21 07:45, Jeff Santos wrote: > > "memory" is PFRES_MEMORY, this could well be it. the description > > is "Dropped due to lacking mem", it's triggered in quite a few > > places (grep for PFRES_MEMORY in /sys/dev/net/pf*). > > I could not find any /sys/dev/net directory. Could that be a p

Re: Delay changing the dynamic address in a VPN NAT rule

2007-07-22 Thread Stuart Henderson
On 2007/07/20 17:39, Paul Collis wrote: > I have a firewall running OpenBSD 4.1-STABLE with pptp-1.7.1 to access a > corporate VPN from a Windows XP machine on the internal LAN. The VPN uses > dial on demand. Running ping on the Windows machine to access the corporate > server (192.168.0.143) does