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 latency
> went back down to 10-12 ms rtt. Anyone seen anything like this with the
> update to 2.2.5?
>

Not that I've seen or heard of. Latency as measured by what?
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

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 in the bug 
database.

Rob

- Original Message -
From: "Robert Fuller" 
To: "pfSense support and discussion" 
Sent: Monday, November 9, 2015 8:23:25 PM
Subject: [pfSense] 2.2.5 problem with FreeBSD packages

Ran into a problem with my upgrade from 2.2.4 to 2.2.5.  I am running the 
NanoBSD version.  I use a couple of FreeBSD packages.  Ran pkg to bootstrap the 
FreeBSD package system on 2.2.5.  There are no FreeBSD packages available for 
install.  Did a "pkg search" for various common things that should be there.  
They are not available.  Tried "pkg update" as well.  Finally, simply reverted 
to 2.2.4 for the time being.  Thoughts?

Thank you for a great product.  I always marvel at its flexibility.  This is 
just a minor bump in the road.

Rob
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

[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 -> Network Interfaces I have LAN, INTERNAL, 
Localhost, and the two IP aliases selected; All and WAN are unselected.  In 
"Outgoing Network Interfaces" I have All selected.

Unfortunately, with this configuration, unbound does not listen on the IP 
aliases: it only listens on the primary IP addresses of LAN, INTERNAL, and 
localhost.

Is anyone else having this problem?  If so, is there a way to get unbound to 
listen on all the *selected* interfaces?

Cheers,

Paul.
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

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 like overkill to just
get the DNS working. But I'll read up what it takes to implement
RADIUS. Thanks for the response.




Not sure how many clients you are going to have, but Openvpn allows you 
to assign an IP address to a specific client.  Look at the ipp.txt file.


Geoff

___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

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 working. But I'll read up what it takes to implement
RADIUS. Thanks for the response.

Marco
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold