No change in behavior.

I created the file as noted.

/etc/resolvconf.conf resolv_conf_passthrough=YES

Rebooted

v4 DNS does not show.

/etc/resolv.conf nameserver 2601:a:2500:4c0:225:90ff:fef1:c230 search localdomain

Disabled / Enabled DNS Forwarder  (unbound was never enabled)

EDIT: Or just hit Save on the DNS Forwarder page.

Now the v4 DNS configured in the General Setup is there.

/etc/resolv.conf nameserver 127.0.0.1 search localdomain nameserver 192.168.1.52 nameserver 8.8.8.8

I upgraded to the Wed Dec 03 13:29:19 build and no change.

–
This isn't an operational problem for me.  But, a behavior I wanted to point out.

Just installed

2.2-BETA (i386)
built on Wed Dec 03 13:29:19 CST 2014
FreeBSD 10.1-RELEASE

Issue appears to be resolved  ;D

Thanks!

Apparently, the wireless card isn't being detected at all.

It's a PCI-E x1 Dual-Band 2.4/5GHz Wireless Card - ASUS PCE-N53 (Ralink RT2860 chipset)

looking into it
https://redmine.pfsense.org/issues/4066

Is that package working for you now? I don't have a setup handy to fully test that package, and that's one of a small number on our package testing list we haven't gotten confirmation on yet.

Thanks, charliem. I've checked with 2.1.5 and it behaves exactly the same, so, it should be ok. Thanks again for taking the time to look at it.

+1

Hi!

I having this problem on 2.1.5 too

To resolve this increase Probe Interval on all gateways
I set value to 10 sec
No problems after that


After updating to the latest snapshot, it looks like it's back. Thanks!

@jimp:

The time estimate is not possible, but the total number and current package should be.

Well that still gives you the info that I was talking about so I'd be happy :)

@Keljian:

Even if it's not precise, at least you know roughly at a glance: a. it's doing something and hasn't hit a hard stall, b. where it's at.

So revised "Currently installing X of Y packages, Current package: <foo>- #% complete"</foo>

@jimp:

Drop those onto the redmine ticket linked above as notes, one of us can reopen that ticket since it appears the fix isn't quite right.

Done!

You should probably limit the queues of ix1 to less or tune the nmblusters more up as required.

My mistake. now i feel soooo stupid! thanks cmb for the prompt catch. I am glad to see I am not the only one though  :)

Thanks,
now it's works fine !

Steffen

I added this to the doc wiki: https://doc.pfsense.org/index.php/Dig_command_on_pfSense_2.2_and_later

tl;dr version: drill, baby, drill.

The only thing configuring squid for transparent mode does is automatically add the same redirect you can add manually.