Re: [pfSense] Issues with 2.2.x and Alix devices
I've successfully upgraded 5 Alix 2D3 fron 2.2.2 to 2.2.3 Everything OK Odette In data martedì 7 luglio 2015 09:45:38, Микаел Бак ha scritto: Hi Kostas, On 2015-07-06 18:53, Kostas Backas wrote: 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? You do not specify how much RAM your Alix device have. I have only been able to run pfsence reliably with Alix devices that have 256MB RAM. With less (128MB RAM) the webconfigurator process kills itself, presumably because it needs more RAM to work properly. Perhaps I'm wrong, but this is what I have noticed on my systems. HTH, Mikael ___ 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
Re: [pfSense] FTP issues on 1:1
10.20.*.* really shouldn’t be on your wan, that’s not routable. Also, 214*256+167=54951, outside the range you say you dictated in the conf (49500-52500) I don’t think PFSense is going to provide you an ftp proxy, both because you’re not using port 21, and this document: https://doc.pfsense.org/index.php/FTP_without_a_Proxy I’m not convinced that ProFTPd is actually using your conf. I think you’re now fighting with ProFTPd, not PFSense. wireshark (or Microsoft Network Monitor) is your friend. ED On 2015, Jul 7, at 10:49 PM, Ryan Coleman ryan.cole...@cwis.biz wrote: Yes. ProFTPd reports the masquerading address properly when starting the service. — Ryan On Jul 7, 2015, at 5:14 PM, Steve Yates st...@teamits.com wrote: Ryan Coleman wrote on Tue, Jul 7 2015 at 4:48 pm: http://www.proftpd.org/docs/directives/linked/config_ref_MasqueradeAddress.html Yep - I’m using that. Command:PORT 10,20,1,49,214,167 Pretty sure this would be IP 10.20.1.49, not the public one...is 10.20.1.x on your WAN? -- Steve Yates ITS, Inc. ___ 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 mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] IPSEC Tunnel with NAT not working under 2.2.3
On Tue, Jul 7, 2015 at 8:39 AM, compdoc comp...@hotrodpc.com wrote: The same thing happened to me. I had to change the Encryption algorithm from AES256 to 3DES to get it to work. Another option is to disable the AES-NI hardware acceleration in 2.2.3. ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] FTP issues on 1:1
On Jul 8, 2015, at 9:30 AM, ED Fochler soek...@liquidbinary.com wrote: 10.20.*.* really shouldn’t be on your wan, that’s not routable. Also, 214*256+167=54951, outside the range you say you dictated in the conf (49500-52500) I’ll give you that. PITA. I don’t think PFSense is going to provide you an ftp proxy, both because you’re not using port 21, and this document: https://doc.pfsense.org/index.php/FTP_without_a_Proxy I’m not convinced that ProFTPd is actually using your conf. I think you’re now fighting with ProFTPd, not PFSense. wireshark (or Microsoft Network Monitor) is your friend. It connects locally on 10.50.1.2 on port 9000. 10.20.1.49 is the local IP of my computer when I was out of the house yesterday. Not the LAN IP of the server. 1:1 is routing things correctly to 1.2 otherwise (website is loading without issue). I’ll look more into it tonight. ED On 2015, Jul 7, at 10:49 PM, Ryan Coleman ryan.cole...@cwis.biz wrote: Yes. ProFTPd reports the masquerading address properly when starting the service. — Ryan On Jul 7, 2015, at 5:14 PM, Steve Yates st...@teamits.com wrote: Ryan Coleman wrote on Tue, Jul 7 2015 at 4:48 pm: http://www.proftpd.org/docs/directives/linked/config_ref_MasqueradeAddress.html Yep - I’m using that. Command: PORT 10,20,1,49,214,167 Pretty sure this would be IP 10.20.1.49, not the public one...is 10.20.1.x on your WAN? -- Steve Yates ITS, Inc. ___ 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 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
