pfSense is normally tested on the devices that Netgate has released as
products over the past two years.
pfSense 2.3.2 was tested on the following devices and hypervisors:
SG-2220 (eMMC and M.2), SG-2440 (eMMC and mSATA), SG-4860 (eMMC and mSATA),
SG-8860 (eMMC and mSATA), 7541 (CF and SSD), 7551
I presume you mean AMD… But that’s what the 64-bit code base is labeled as,
regardless of Intel, AMD or other.
> On Jul 29, 2016, at 9:50 PM, Alfredo Tapia Sabogal
> wrote:
>
> So far i know pfsense have some issues related to the architecture of ADM
>
> CHEERS
>
> Alfredo Tapia Sabogal
__
So far i know pfsense have some issues related to the architecture of ADM
CHEERS
Alfredo Tapia Sabogal
El jul. 29, 2016 9:38 PM, "Ryan Coleman" escribió:
> Have we established an official bug for the newest release? I can babysit
> one installation on Sunday without an issue but it’s the one I
Have we established an official bug for the newest release? I can babysit one
installation on Sunday without an issue but it’s the one I cannot afford to
lose (retail shop) that needs updating sooner rather than later (as I won’t
have the time for a month)….
So does this effect APUs running the
On 7/26/2016 8:40 PM, Chris Buechler wrote:
On Tue, Jul 26, 2016 at 7:43 PM, Volker Kuhlmann wrote:
On Tue 26 Jul 2016 09:41:37 NZST +1200, Karl Fife wrote:
Interesting how it failed: The fried port 'simply' broke
connectivity for the interface's LAN segment. Everything else
continued to wor
> On Jul 29, 2016, at 5:20 AM, Kemecsei Gábor wrote:
>
> "Unable to check for updates"
>
> It's ok?
>
> I use:
> "2.3.1-RELEASE-p5 (i386)
> built on Thu Jun 16 12:53:31 CDT 2016
> FreeBSD 10.3-RELEASE-p3 "
>
> The Package Manager reply:
> "Unable to retrieve package information."
>
> I have a
"Unable to check for updates"
It's ok?
I use:
"2.3.1-RELEASE-p5 (i386)
built on Thu Jun 16 12:53:31 CDT 2016
FreeBSD 10.3-RELEASE-p3 "
The Package Manager reply:
"Unable to retrieve package information."
I have a bug or pfSense?
kemecs
___
pfSense m
