On 7/6/2015 7:59 PM, Ryan Coleman wrote:
> Using 1:1 has turned most of my knowledge in pfSense completely useless. I
> feel like a beginner again.
>
> FTP worked on port 21. But for security reasons I do not want it there so I
> moved it to port 9000.
>
> ProFTPd is set up for Masquerading on
Using 1:1 has turned most of my knowledge in pfSense completely useless. I feel
like a beginner again.
FTP worked on port 21. But for security reasons I do not want it there so I
moved it to port 9000.
ProFTPd is set up for Masquerading on its 1:1 IP, passive ports are dictated in
the conf (49
On Fri, Jul 3, 2015 at 3:16 AM, Микаел Бак wrote:
> Hi list,
>
> I run pfsense nanobsd (1g) on an old PC Engines ALIX board with 256MB RAM.
>
> After upgrading to v2.2.3 my only installed package "OpenVPN Client Export
> Utility" and its dependencies disappeared.
>
> I tried to reinstall it, but n
Has anyone else notice lightsquid no longer updates according to schedule since
update to 2.2.3? If i click refresh now all is well but it doesn't follow the
configuration of hourly. I've tried 10 minites, 20, 30 as well. Only manual
updates are working.
Brian Caouette(207) 212-6560
Vis
On Wed, Jul 1, 2015 at 12:25 PM, Vick Khera wrote:
> With pfSense 2.2.3, the iPhone connects to the pfSense firewall to
> negotiate the VPN. The status seems to be normal and as far as I can tell
> all the IPSec bits are in order. Nothing unexpected in the logs. SAD and
> SPD look fine to me.
>
Hello,
I had no success restoring 2.2.x (2.2.2 or 2.2.3) proper installers or updaters
to 2 different Alix devices.
2.1.5 is installing fine, and then update works OK. I haven’t tested yet the
devices with serial cables to see where they stop.
Anyone faced this?
Best regards
Kostas
___
Ahh good to know - that would explain the other thing I was experiencing but
decided no to pursue right away.
> On Jul 6, 2015, at 9:49 AM, Vick Khera wrote:
>
> On Sun, Jul 5, 2015 at 12:03 PM, Ryan Coleman wrote:
>
>> Neither my desktop nor my mobile (OS X 10.10.3 and iOS 8.3) are able to
On Sun, Jul 5, 2015 at 12:03 PM, Ryan Coleman wrote:
> Neither my desktop nor my mobile (OS X 10.10.3 and iOS 8.3) are able to
> negotiate on a previously-functioning IPsec configuration. Only change I
> can determine right now is the updated OS of the firewall to CURRENT.
>
I had the issue with
