Also, I confirmed that dg filtering does not work on reboot. All of the services start except for shorewall. So once you start shorewall it works. (also shorewall - shoreline firewall is not a daemon, so ps -ef |grep won't help.)

What I did was use webmin under Networking / Shoreline Firewall you can just hit the start shorewall button and it will begin (if you prefer not to work with the cli). Then you can confirm that it is working.

To make it persistent, you can also use webmin.Go to the System / Bootup and Shutdown menu and check shorewall and click the 'start at boot' button.

1. my understanding is that the apt-catcher server does not have to be a gateway / router. That is, it can just sit off a switch between the internet / external firewall / router and the core / dcerouter and traffic does not have to pass through it. Is that correct?

phenigma,Thank you. I've thought about putting a switch and an old server on the internet side of lmce and caching there - is that how you do it? Do you have a recipe that folks can follow?thanks,joseph

I still have two MDs that are affected. I also noticed that all of my MDs have a phantom TV device - "Acquos LCxxD6U / LCxxD7u/TV." I don't have any Acquos TV. I deleted it in the web admin and rebooted, but it was rediscovered.

I'm not sure if this has anything to do with the black screen & pointer, but thought I would mention the anomoly.

Also, I have successful results to report from installing webmin and the dansguardian module to webmin.webmin has many tools that allow easy (web) viewing and manipulation of many services - for instance it has an easy web-based log viewer. [This could be dangerous if you tinker with settings you do not understand!]

The dansguardian module also allows customization of many of the dg settings.

I'll describe the install in two steps. One - install webmin, and two - install & configure dg module for webmin.

Now we have webmin_1.480 _all.deb package install this package using the following command

sudo dpkg -i webmin_1.480_all.deb

This will complete the installation.

Ubuntu in particular doesn’t allow logins by the root user by default. However, the user created at system installation time can use sudo to switch to root. Webmin will allow any user who has this sudo capability to login with full root privileges.

You should see:The following modules have been successfully installed and added to your access control list : DansGuardian Web Content Filter in /usr/share/webmin/dansguardian (4612 kB) under category Servers

The first time you try to run the dg module, you'll get errors such as:Warning - DansGuardian binary file not found, maybe you need to update your module config (especially the directory paths). (Expected location: /sbin/dansguardian)

The problem is that the we are using differnet directory locations for many of the files.

So, look at the Configurable options for DansGuardian Web Content Filter (in the upper left corner of the dg page) - and nearly every path needs to be changed. For instance, our binary is in /usr/sbin/dansguardian instead of /sbin/dansguardian, so change that.

Confirm the locations for the rest of the files by running #find as follows (or just use these locations)dcerouter_1001275:/usr/local/sbin# find / -name dansguardian/usr/share/webmin/dansguardian/usr/share/lintian/overrides/dansguardian/usr/share/doc/dansguardian/usr/share/dansguardian/usr/sbin/dansguardian/var/log/dansguardian/etc/webmin/dansguardian/etc/init.d/dansguardian/etc/logrotate.d/dansguardian/etc/dansguardiandcerouter_1001275:/usr/local/sbin#

When you've finished replacing all of the locations, hit save on the config page and then "stop & restart DG" on the top right of the main DG page.

Then it should work! If not, check your syslog for errors.You should be able to check the status of DG, review logs with a good viewer, and view and edit many of the detailed configurations.

There may be two issues if I'm reading this correctly and it may help to clarify. I have the issue described by this topic - that is my core hybrid runs and DCErouter is running, but the orbiter does not launch.

If the dcerouter doesn't start, then it may be certain that the orbiter can't start, but the reverse is not true. A core can be running as a core, which means that dcerouter is running. And the core may or may not be running an orbiter; a core running an orbiter makes it a hybrid.

If it helps, I don't have any old locks in /usr/pluto/locks (they are all timestamped after a reboot earlier today) and have not experienced any crashes since I installed from scratch a few days ago on the 24th of August.