https://redmine.pfsense.org/issues/5721

@NOYB: What with this 2.2.6 stuf?  Thought this was the 2.3 beta board.  ;) Didn't catch that. Yeah c'mon johnpoz, time to upgrade. :)

If it's something that fixes a problem, then we're still merging such changes. If it's merely UI improvements, not fixing things that are broken, that's what we're holding off on until post-2.3-RELEASE. Thanks!

Cool. Thanks.

I resorted to installing the Service Watchdog.  At least it will keep my network running, until this bullshit with unbound gets sorted.

A number of times I've looked for a cancel button too.  Think it would be nice even if it just does the same thing as back button.  Should be part of the app rather than having to find the browser back button.  Especially with so many diverse device types being used today.  Seems like an app provided cancel button would be easier on some of them.  Interact with the app interface , not the browser interface.

Lets you reorder items in the list. Check the box on an entry, click the anchor on the place you want it to go, and it moves to the new position. It's how things get rearranged now without the drag-and-drop feature. Not a lot of significance to the order in services watchdog though, unless you always want to make sure a specific service is checked/restarted before another one.

With 3rd option, you would probably not know that you can click on that icon. It's just not very intuitive. How about hiding icon when alert is open and when user closes the alert icon appears :)

There is a basic log viewer in squidguard I believe but the layout is extremely differant then 2.2.6. There is no way to clear the log. What I posted above was caused but enabling the wrong option in squid. It cause ALOT of false positives and blocked good pages. Basically what happen was a url that triggered a content block was reported as a virus. All is well with the exception of not being able to reset the widget count aka log clear?

As long as an interface is using that specific gateway, it wont let you change it. Go to the interface setting that is using the gateway. Select "None" in the Gateway. That will let you change the getway name and even delete it if you need to. Once you have updated the name, go back and select the gateway in the Interface setting.

Fixed, thanks!

VPN (PIA in my case) gave problems in my setup also. Gateway status stay at 'pending' until I turned off gateway monitoring. After that, it start working and routing traffic. Maybe not just my setup….

The compatibility is up to ISC – it's their daemon, the daemon is rejecting the setting. So if you need to use them together, advocate upstream to have them fix it. In the past they've had similar issues that were actually OK and just an over-protective parser rejecting it, but in this case it seems more deliberate, so there may be a reason.

Decided to try again.  After looking at the LUA file where the error was occurring, it appeared to be in an IF block for verbose logging.  I was enabling that option so thought I would try again, this time without verbose logging enabled.  I also selected the quick install option this time.  Worked like a charm.  So appears something is up with either the verbose logging and/or custom install selections. [image: Capture.JPG] [image: Capture.JPG_thumb]

That doesn't sound specific to 2.3, try the proxy board.

@brianc69: The question is how to fix it? I tried the above but the backup gets restored automatically. What am I missing? Why does it keep coming back? Editing the entry out of the config is the easiest way. If you get the message that a config is being restored it means you removed too much or the wrong chunk, leaving it with invalid XML. Be sure to only remove the one menu tag and its contents and no lines above/below it. Downloading a config backup, editing it, and then restoring it is the safest way, rather than editing live.

Sure, that works fine. Put the restrictions in the LDAP auth server entry in extended filter and such. You can have multiple entries defined for the same target server, so if you want different servers to restrict to different groups, make additional auth server entries with different filters.

I think it was a bad NIC. Switched with a new similar network card and all is well. Sync works perfectly now.

Bump