Tom,
Do you happen to know what a hardware watchdog timer watches? Perhaps there
is something it can watch like whether or not the device is sending on the
Ethernet port or the program counter. But, it seems that as embedded systems
add more software, a useful hardware watchdog timer becomes less
Mmmm, the Wrap, is its private IP in the 10.0.0.0/8 ? Can you look
up in the RB's NAT table and see what the source IP is?
FTP out to the world, is it using the NAT IP or the correct public IP
? I wonder if Proxy ARP isn't biting you.
On Sat, Dec 19, 2009 at 10:19 PM, RickG rgunder...@gmail.com
A hardware watchdog timer, typically, watches only one thing - is the
software and/or CPU still alive? If a software pinger fails to reset a
hardware counter or timer every few seconds or so, the timer reaches the end
of its count and resets the motherboard. It is a failsafe if everything else
Robert,
While I don't have specific experience with Skycross antennas, the
underlying idea is well established -- two different radiation patterns
from elements in the same area, i.e.a scheme that creates pattern
diversity. This is possible and commercial versions are being driven
the need
Tom,
Try again, Ubiquity AR71xx based stuff (all the M series) supports a
hardware watchdog fine.
from dmesg via OpenWRT.
Atheros AR71xx hardware watchdog driver version 0.1.0
Regards
Michael Baird
A hardware watchdog timer, typically, watches only one thing - is the
software and/or CPU
That's good - but just because it's supported at the chipset level doesn't
necessarily mean the ubnt firmware or sdk supports it. In any case we were
working with the original a/g nano's and bullets, not the M series. The M is
way too new and bleeding edge for us.
Tom S.
- Original
A hardware watchdog timer isn't something that's supported. To me that sounds
like a software feature. A true hardware watchdog is a separate circuit that
oversees the system. If it detects a problem it toggle the power controller
chip to reset the whole board.
Greg
On Dec 20, 2009, at 2:19
I believe the routerboard watchdogs are hardware. The software resets
the hardware timer. If it hits 0 the watchdog reboots.
On 12/20/09, Greg Ihnen os10ru...@gmail.com wrote:
A hardware watchdog timer isn't something that's supported. To me that
sounds like a software feature. A true
Tom,
Watchdog timers like you describe are useful, but they tend to be less
valuable than they used to be because newer software tends to be
multi-threaded instead of single threaded and also the interfaces are
smarter and do more processing on their own. This means there are more paths
that the
And that's so basic, it's really the most useful watchdog, IMO. Many times
I've been able to get a ping response from a piece of equipment yet it's
still not functioning. Thus, it still needs to have a visit even though it
pings just fine. And as a wonderful coincidence, I had one just like
If it has it, it ain't a workin'!
Bob-
-Original Message-
From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On
Behalf Of Greg Ihnen
Sent: Sunday, December 20, 2009 4:26 PM
To: Tom Sharples; WISPA General List
Subject: Re: [WISPA] Ubiquiti ready for prime time?
A
I think so too. I've never had a Routerboard hang on me and I've had plenty
reboot themselves after I did something foolish or idiotic in a config.
Bob-
-Original Message-
From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On
Behalf Of Josh Luthman
Sent: Sunday,
But a device can still respond to a ping yet be locked up. If anything, it
needs to just be a small part of the overall picture.
Maybe if then hardware watchdog was based on a separate firmware and one
could specify the parameters to trigger the hardware reboot, not dependant
on the operating
Yes, the WRAPs are in the 10.0.0.0/8. However, I dont have the WRAPs defined
in NAT. The working WRAP I'm off of at my office is using the public IP.
I'll have to FTP test the non-working WRAP at the customer site to see. As
I said, the net does work using the public IP from there location. I
At the risk of boring people - we use both. We have a fairly sophisticated
software watchdog routine that checks all threads and the integrity of the
various network devices like eth, ath, tun, tap, ppp, etc. etc, every few
minutes. If it sees anything wrong it takes corrective action, which
I loaded it once, but wasn't interested enough in it to pay for a license.
That is one of the radios they require a license for. I do have a Nano-2
now with Open-WRT loaded on it, just started playing with it though.
-Original Message-
From: wireless-boun...@wispa.org
Tom,
Sounds like a great approach.
Mark
On 12/20/09 7:30 PM, Tom Sharples tsharp...@qorvus.com wrote:
At the risk of boring people - we use both. We have a fairly sophisticated
software watchdog routine that checks all threads and the integrity of the
various network devices like eth, ath,
Have to disagree with that - at least in any embedded device I've ever
worked on (and I've worked on a great many), the hw watchdog was incapable
of independent detection of anything. All it did was wait for a tickle from
the firmware which, if absent for greater than x amount of time, would
Not boring at all, Tom. Informative.
Bob-
-Original Message-
From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On
Behalf Of Tom Sharples
Sent: Sunday, December 20, 2009 7:31 PM
To: WISPA General List
Subject: Re: [WISPA] Ubiquiti ready for prime time?
At the risk of
19 matches
Mail list logo
