Re: [pfSense] Running newer then released?

gt;> wrote: >>> >>>> The issue is that the message displayed is, exactly: >>>> ``` >>>> 2.3.3-RELEASE (amd64) >>>> built on Thu Feb 16 06:59:53 CST 2017 >>>> FreeBSD 10.3-RELEASE-p16 >>>> >>>> The system is on

Re: [pfSense] Running newer then released?

elease process? > > > On Sat, Mar 4, 2017 at 2:48 AM, Arno Gramatke <a...@gramatke.biz > <mailto:a...@gramatke.biz>> wrote: > >> 2.3.3 is the current release, isn’t it? >> >> https://blog.pfsense.org/?p=2325 <https://blog.pfsense.org/?p=2325>

Re: [pfSense] Running newer then released?

2.3.3 is the current release, isn’t it? https://blog.pfsense.org/?p=2325 > Am 03.03.2017 um 14:45 schrieb Yılmaz Bilgili : > > 03-03-2017 15:38 tarihinde Doug Lytle yazdı: >> My home pfSense is reporting: >> >> 2.3.3-RELEASE (amd64)

Re: [pfSense] pfSense reloads configuration every second after enabling IPV6 on WAN interface

BNG would reply with NoPrefixAvail >with a lifetime of 0. Does that make any sense when looking at the log excerpts I sent? If so, is there a way to work around this issue in pfSense? > Am 17.10.2016 um 12:31 schrieb Arno Gramatke <a...@gramatke.biz>: > > Hi all, > > I am

[pfSense] pfSense reloads configuration every second after enabling IPV6 on WAN interface

Hi all, I am running pfSense 2.3.2-RELEASE-p1 on a PC Engines APU1D4 connected to a Deutsche Telekom VDSL line. My interface configuration looks like this: WAN => PPPoE on re0_vlan7 LAN => re1 OPT1 => re2 OPT2 => re0 (for access to the DSL modem) When just using IPv4 everything works fine.