similar to: watchdog firebox has blocked ssh out

We are trying to setup a sip connection behind a Watchguard Firebox 1000 and it is simply put...not working. The ports are all forwarded but the packets are not going out. It is as if the firewall simply ignores SIP packets. Has anyone seen this or have any idea what the issue could be? Watchguard so far has been of zero help. Kerry Garrison Director of Technical Services Tech Data Pros -

Has any had any experiences with Watchguard Firebox 1000 and Asterisk. I have asterisk on public side and phones on the private side. I am able to get the phones to register and make outbound calls but the inbound calls are intermittent. I have NAT enable in asterisk and on the Cisco 7960. Any insight would be appreciated. Thanks

Dear Developers, I've released a patch against openssh-2.5.2p2. The patch adds heartbeat (keepalive) function to ssh(1), and watchdog timeout function to sshd(8). The watchdog timeout is intended to terminate user's processes as soon as possible after the link has been lost. http://www.ecip.tohoku.ac.jp/~hgot/sources/openssh-watchdog.html The combination of the heartbeat and the

Good morning! On a CentOS 6.4 / 64 bit server I have installed the watchdog 5.5 package. The rpm -qi watchdog states: The watchdog program can be used as a powerful software watchdog daemon or may be alternately used with a hardware watchdog device such as the IPMI hardware watchdog driver interface to a resident Baseboard Management Controller (BMC). ... This configuration file is also used to

Hello Nut Devs, I'm working with usbhid-ups and a Tripplite OMNI1000LCD. I used a USB packet sniffer to discover something cool about the watchdog feature in this unit. (not sure if the other OMNI-X-LCD models work the same or not.) Basically there's a single HID variable at Report ID 0x52 (UPS.OutletSystem.Outlet.ffff0092) that's one byte (0-255 int) and it contains the Watchdog

Hi! I''m trying to run w83627hf_wdt.ko watchdog driver in domain 0 (xenlinux 2.6.10-xen0), but the driver doesn''t seem to work (the machine reboots all the time after the watchdog-timeout set in BIOS). Is there something that could prevent the driver from accessing the watchdog-hardware (io-ports/registers) ? The watchdog-driver is very simple, and you can find it in

Hello, I am trying to use WINE (20050725-r1 on Gentoo Linux) to install/run Watchguard's Firebox Management Software (WFS). The WFS installer uses an installshield installer of course.. I've been looking thru the FAQ, wiki, etc and have found info about DCOM98 needing to be installed. I've tried a bunch of things so far, and here's where I stand: First, I tried getting

CentOS 6 Hi all, I am working on setting up sanlock + watchdog on a 2 node KVM pair. Sanlock is working beautifully and is preventing access to the VM disks by more than one process as it should across both boxes. I am attempting to test failure scenarios involving watchdog, but I am having a hard time getting it to actually reset the server. I am running wdmd with -D so I can see the

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1336153082 -7200 # Node ID 9a430b7e2df2893f7f4f75d10e66d52bdffa7efa # Parent 113fd57259b91af06a5352404dd94b484a98d2bc tools/hotplug: remove 4 from default runlevel in xen-watchdog, xend and xendomains Similar to what changeset 24847:0900b1c905f1 does in xencommons, remove runlevel 4 from the other runlevel scripts. LSB defines

/usr/sfw/bin/firefox is a shell script which calls run-mozilla.sh which calls firebox-bin. Is there a way to call dapptrace on firefox in order to trace firefox-bin? This message posted from opensolaris.org

Here's couple of patches to improve the softlockup watchdog. The first changes the softlockup timer from using jiffies to sched_clock() as a timebase. Xen and VMI implement sched_clock() as counting unstolen time, so time stolen by the hypervisor won't cause the watchdog to bite. The second adds per-cpu enable flags for the watchdog timer. This allows the timer to be disabled when the

Here's couple of patches to improve the softlockup watchdog. The first changes the softlockup timer from using jiffies to sched_clock() as a timebase. Xen and VMI implement sched_clock() as counting unstolen time, so time stolen by the hypervisor won't cause the watchdog to bite. The second adds per-cpu enable flags for the watchdog timer. This allows the timer to be disabled when the

I''m looking at building a xenstore-based watchdog, as described at http://lists.xensource.com/archives/html/xen-users/2005-07/msg00597.html However, being somewhat new to xenstore, I''d appreciate some pointers. - What portions of the xenstore namespace should I use? I''m looking for at least two settings writable by the DomUs: A flag to enable/disable the watchdog

The softlockup watchdog is currently a nuisance in a virtual machine, since the whole system could have the CPU stolen from it for a long period of time. While it would be unlikely for a guest domain to be denied timer interrupts for over 10s, it could happen and any softlockup message would be completely spurious. Earlier I proposed that sched_clock() return time in unstolen nanoseconds, which

The softlockup watchdog is currently a nuisance in a virtual machine, since the whole system could have the CPU stolen from it for a long period of time. While it would be unlikely for a guest domain to be denied timer interrupts for over 10s, it could happen and any softlockup message would be completely spurious. Earlier I proposed that sched_clock() return time in unstolen nanoseconds, which

Hi Ingo, This series of patches implements a number of improvements to the softlockup watchdog and its users. They are: 1. Make the watchdog ignore stolen time When running under a hypervisor, the kernel may lose an arbitrary amount of time as "stolen time". This may cause the softlockup watchdog to trigger spruiously. Xen and VMI implement sched_clock() as measuring unstolen time,

Hi Ingo, This series of patches implements a number of improvements to the softlockup watchdog and its users. They are: 1. Make the watchdog ignore stolen time When running under a hypervisor, the kernel may lose an arbitrary amount of time as "stolen time". This may cause the softlockup watchdog to trigger spruiously. Xen and VMI implement sched_clock() as measuring unstolen time,

Hello, Is there a generic built-in way on CentOS to overlook that a specific process is alive and re-spawn it (or just run a configured command) when it dies? I know how to script things so a parent will watch its child, but was wondering whether there is something more readily available instead of having to reinvent the wheel. The process must be controlled via a /etc/init.d/... script and

On Mon, 31 Jul 2023 09:25:12 +0800, "zhanghao1" <zhanghao1 at kylinos.cn> wrote: > A new virtio pci driver is added for listening to vcpus > inside guest. Each vcpu creates a corresponding thread to > periodically send data to qemu's back-end watchdog device. > If a vCPU is in the stall state, data cannot be sent to > back-end virtio device. As a result, the

Hello I have some problems with 3Com nics, after a upgrade from 5.5-STABLE to 6.4-STABLE. This machine has two 3com nics (one is LAN other is WAN) and i see too much "watchdog timeout" on both cards. This on/off up/down on cards, affect the interrupt to clients that are downloading from apache web server, especially on large files. --------------------------------------------