I just had an event that I'm having trouble identifying the root cause.
I'm hoping that someone might have encountered this or might be able to
point me toward some things to check.
Yesterday we had an event where our primary firewall would stop passing
traffic. The only thing short of a reboot
internal networks
On Wed, Oct 17, 2012 at 12:23 PM, Luis Coronado lcoron...@ticoit.com wrote:
Devs/gurus will need for other information as well, at least you should
include dmesg output and how your network is arranged.
-luis
On Wed, Oct 17, 2012 at 9:51 AM, Bennett Samowich bsamow
though pflog made it look as if it were.
On Wed, Oct 17, 2012 at 11:51 AM, Bennett Samowich bsamow...@gmail.com wrote:
I just had an event that I'm having trouble identifying the root cause. I'm
hoping that someone might have encountered this or might be able to point me
toward some things
/2012 8:51 AM, Bennett Samowich wrote:
I just had an event that I'm having trouble identifying the root cause.
I'm hoping that someone might have encountered this or might be able to
point me toward some things to check.
Yesterday we had an event where our primary firewall would stop passing
On Mon, Jul 30, 2012 at 11:25 AM, Gregory Edigarov ediga...@cupid.com wrote:
On 07/30/2012 06:02 PM, Bennett Samowich wrote:
The problem exists even if I use the system's /usr/bin/false and
/usr/bin/true commands.
The problem exists even when PF is disabled or the only rule is pass
I've uncovered a troubling performance symptom that I believe is
related to relayd's check script functionality.
The system is a Dell R710 with 12GB RAM and 10Gb interfaces. The
problem is that when relayd is running with redirects that uses the
check script functionality, performance of the
\
check script /usr/bin/false \
timeout 4000\
interval 15\
mode roundrobin
}
On Mon, Jul 30, 2012 at 8:59 AM, Gregory Edigarov ediga...@cupid.com wrote:
On 07/30/2012 03:25 PM, Bennett Samowich wrote:
I've
We were in the process of deploying relayd into production when we
discovered that the relayctl reload command would always return
command failed. Following the archives I found the reported bug
6046 which doesn't seem like it's actively being worked on or get to
the heart of the problem. Both
8 matches
Mail list logo