[pfSense] Unbound DNS Resolver doesn't listen on IP aliases even when selected in settings

2015-11-12 Thread Paul Mather
I recently started using "DNS Resolver" on my pfSense 2.2 system, which had been previously using "DNS Forwarder." The pfSense install has a WAN network and two local networks, LAN and INTERNAL. The INTERNAL network has two IP aliases defined for it. In DNS Resolver -> General Settings -> Net

Re: [pfSense] 2.2.5 problem with FreeBSD packages

2015-11-12 Thread Robert Fuller
I hear nothing but crickets. Anybody have any luck installing BSD packages under the NanoBSD pfSense 2.2.5? I had no problem with 2.2.4 and earlier, but there don't seem to be any packages after you bootstrap pkg-ng in 2.2.5. I hate to open a Redmine bug or whatever if it's just me or already

Re: [pfSense] Hostname resolution of OpenVPN-connected clients

2015-11-12 Thread Geoff Nordli
On 15-11-12 02:15 AM, Marco wrote: On Wed, 11 Nov 2015 15:22:40 + Espen Johansen wrote: I think you have to set up a radius server and assign ip based on the user. That way they will be "static" and then add DNS entries to that static IP. I've never dealt with RADIUS. Seems like a bit lik

Re: [pfSense] Hostname resolution of OpenVPN-connected clients

2015-11-12 Thread Marco
On Wed, 11 Nov 2015 09:50:30 -0500 Vick Khera wrote: > On Wed, Nov 11, 2015 at 2:46 AM, Marco wrote: > > > How to access the mobile hosts via the same hostname regardless if > > they are connected to the LAN or VPN? > > > > Via some form of dynamic DNS perhaps? It seems it should be possible

Re: [pfSense] Hostname resolution of OpenVPN-connected clients

2015-11-12 Thread Marco
On Wed, 11 Nov 2015 15:22:40 + Espen Johansen wrote: > I think you have to set up a radius server and assign ip based on the > user. That way they will be "static" and then add DNS entries to that > static IP. I've never dealt with RADIUS. Seems like a bit like overkill to just get the DNS w

Re: [pfSense] Latency issues with 2.2.25 Release

2015-11-12 Thread Chris Buechler
On Wed, Nov 11, 2015 at 9:47 AM, Wade Blackwell wrote: > Good morning list, >I recently upgraded to *2.2.5-RELEASE * (amd64) on a VMware stack > and noticed that my Wan latency shot up by about 100ms rtt. Nothing else on > the box had changed. I reverted to a pre-upgrade snapshot and the l