Interesting. Ok, thank you for the info. Good to know that I can go that route.

I may still look into using the native logging in Fedora with logwatch (or something similar). I'll report back with any findings... you know, for posterity.

Thanks again.

Turn on DHCP on your router and set it to hand out 1 IP address. If you can specify the range, make it the IP address of the HDA. Then cycle your network, ensuring the HDA has the appropriate IP address before powering on any clients. Fantastic!! This worked! Everything else in the Troubleshooter s...

Ok well I use email with high and it provides me the SSH logins. I tried an email report with High detail, still only reports on samba, yum, and "Disk Space" services (even though the logwatch config is still services=all (the default)). Do you have a /var/log/secure dir? Do you have rsyslog or sys...

Yes, I was using High, but just from the command line (i.e. report to stdout).

I'll take a look at the wiki page. Thanks.

The key is that your clients get it's DHCP and DNS from the HDA. Recommend you check that for clients. If that is the case, then we must look at other settings. I have seen where a complete recycle of the network helps too. That would involve shutting everything down, then power up the modem, route...

Hello, I have been trying for a day or so to get logwatch to report on ssh logins. Still unsuccessful at this point. I haven't been able to find much information on why this might be, but I have a theory... As of Fedora 20, syslog was abandoned in favour of journalctl...?? which (I think) explains w...

It may require a network restart. Happened to me twice in the past few years.

Gotcha. Thanks again. Your experience and comments are a great help.
I'll give that a try from home tonight/tomorrow.

The key is that your clients get it's DHCP and DNS from the HDA. Not disputing this... but doesn't it seem like the problem is more than just with the clients? i.e. if I am *on* the server, shouldn't "nslookup hda" return consistent results? Recommend you check that for clients. If that is the case...

Did you verify that all the DNS and DHCP is off on your router? Well, I was pretty sure that I had. Just double-checked. DHCP was off. DNS/WINS server settings were empty. Tickety-boo. However ... under the WAN settings, there is a "Connect to DNS Server automatically" setting that: Allows the rout...

However, nslookup something.net doesn't resolve to my server, it points to the actual something.net on the internet. [root@localhost ~]# nslookup hda Server: 208.67.222.222 Address: 208.67.222.222#53 Non-authoritative answer: Name: hda.net Address: 74.220.199.8 Are you using your HDA as the DHCP an...