[pfSense] Long delay before DHCP issued leases appear n the DHCP lease table

2016-04-28 Thread Karl Fife
I've been 'subdividing' some growing networks into multi-lan; guest, management networks etc. On every occasion I've observed that it has taken considerable time (perhaps 10 to 20 minutes) after the DHCP server begins issuing new leases (to hosts moved from the other interface) before they

Re: [pfSense] DNS secondary server on 2.3?

2016-04-28 Thread Chris Buechler
On Thu, Apr 28, 2016 at 10:21 AM, Adam Thompson wrote: > OK, I'm lost... In v2.3, what service, and/or where in the GUI, should I go > to make pfSense act as a slave (authoritative) DNS server? > No such capability. Neither dnsmasq nor unbound are authoritative servers.

[pfSense] DNS secondary server on 2.3?

2016-04-28 Thread Adam Thompson
OK, I'm lost... In v2.3, what service, and/or where in the GUI, should I go to make pfSense act as a slave (authoritative) DNS server? On a related note, in Services / DNS Resolver / General Settings, what does "DNS Query Forwarding" do? There's no description, so I assume if it's *not* set,

[pfSense] GUI /firewall_virtual_ip.php - reordering them?

2016-04-28 Thread Olivier Mascia
Could this be listed as an enhancement request for the GUI editing of the virtual IPs ? Some ability to reorder them, at least manually (like rules for instance)? When you have a good number of IP aliases, it would help grasp the big picture in a glimpse to check wether something is not right or

Re: [pfSense] Fw: new message

2016-04-28 Thread Randy Morgan
Thank you Chris, I appreciate your efforts. I have been on other lists that started out with no spam and then got nailed by spam because the list got hacked and nobody was watching over it. I get enough spam even with all the spam filters turned on and tuned. Randy Randy Morgan CSR

Re: [pfSense] CARP and both IPv4 and IPv6: do they live together?

2016-04-28 Thread Olivier Mascia
> Le 28 avr. 2016 à 00:28, Chris Buechler a écrit : > >> >> Sure, I'm not helped by the transit provider which does not actually route >> the /56 prefix to my link (savages!) but merely 'switch' it to me, expecting >> ARP/NDP from >> each of my connected devices, and me