Well done, thats sorted it out  :)

Thanks very much

Ben

1.  Thanks, I'll fix this shortly
2.  Tinydns status page is for LB/Failover (DNS)
3.  TinyDNS will not start until you configure atleast one item on the settings page and click save
4.  Not sure about DNS Forwarders, that was done by someone else.  Patches accepted.
5.  See #4
6.  I will look into it

EDIT: looks like someone forgot to finish their code (not me):

/* NEED TO FIX there are 2 logs /etc/tinydns/log/main/current and /etc/dnscache/log/main/current */

$tinydnslogs = cat /etc/tinydns/log/main/current | /usr/local/bin/tai64nlocal | php -f /usr/local/pkg/tinydns_parse_logs.php | grep -v ":0";

/* NEED TO FIX */
if ($_POST['clear']) {
// exec("rm /etc/tinydns/log/main/current");
// exec("touch /etc/tinydns/log/main/current");
}

Good deal!

I connected the previously unplugged WAN interface to the network and now I have zero spamd-setup lines in /etc/crontab.  spamd seems to be running Ok.

Hm.  I guess the lesson is always to have the WAN interface up when configuring anything.

One doubt.

In file /etc/inc/filter.inc and the code:

Whats happys if the file squid.inc is empty? the function squid_generate_rules('nat') will not work.

I have install squid and disconnected WAN interface of the Internet, reboot. During the boot, I see this error and nothing work again.

Just to clarify, you have two network cards operating on those networks, Lan, and lan2-opt1 correct?  I will also throw in that before the major revision to the squid package it was binding to 127.0.0.1, I don't know if that is the case now.

See http://forum.pfsense.org/index.php/topic,4435.new.html#new

Known issue basically.

just updated to the newsest snapshot

Yeah it works great now, thanks for the support guys  :)

That was totally over my head… I've been using pfsense for some time now, but anything outside of the normal interface is beyond me. I would really like to have upnp set up and working but it isn't critical. If you have any other simple or very detailed ideas they are more then welcome I would be more then happy to try them...

…nearly there...

[Downloading and Installing the Developers ISO went fine. I'd no idea that, on initial boots, downloading all the Source, etc, takes very many hours, and MAKE INDEX takes an hour or 2 also!! I made one possibly nasty error with GREP, as noted in another thread]

Anyway, on the MAKE INSTALL, it downloads the sources, and compiles, and flashes up a massive amount of progress messages, but ends with: "Error Code 1". Whatever that means… Dang. The associated messages suggest running
  - make deinstall && make reinstall, or
  - setting FORCE_PKG_REGISTER in the Env, or
  - setting this in the make install command-line.

Any advice welcome. Perhaps just "make install FORCE_PKG_REGISTER", but I don't want to make things worse!

Separate interesting point:
  - BandWidthD DID create the INDEX files when I ran it for the first time. Looked only beautiful!
  - BUT... next time around, which was only a few minutes later (default config parms, generally), the INDEX.HTML was set to a size of 0, and the other 3 INDEX files were still OK (not refreshed yet).
  - Then, 1 hour later, the INDEX2.HTML file was set to 0. The other 2 were still OK.
  - presumably, when its time to refresh the others, they'll be duly clobbered.
  - I believe I did not do anything very major with the entire system, apart from installing Midnight-Commander.

I dearly hope this info rings a bell with someone... I doubt if tweaking the code will readily identify why the code sometimes creates the files, and sometimes does not...

I could try removing BandWidthD, clearing out the files, and re-installing, etc...

Thanks again...
  - Mike

cd /var/db/pkg && pkg_delete -r ls | grep mc

In the course of experimenting with getting MC running, I ran the above command, but ended it with "GREP M" (instead of "GREP MC"!)

I may have deleted other M* packages!

I would greatly appreciate if anyone could post a list of all the "M*" entries in /var/db/pkg (if any!), in the standard Developers edition.

Thank you.
  - Mike

Should be fixed now.  Thanks.

1.0.1 is not the latest snapshot.

Search the forum.

pick cache patch game online

Try installing again about 5 minutes from this message.

I have found it.

To add extra parameters to squid.conf, you have to edit /usr/local/pkg/squid.inc