Re: [pfSense] yesterday update to 2.3.2 has not worked - these machines now can not update any more

On Wed, Jul 27, 2016 at 8:53 AM, WolfSec-Support wrote: > Hi Jim > > Many thanks for your hint. > Well it is still not working. > > See: > Updating repositories metadata... > Updating pfSense-core repository catalogue... > pfSense-core repository is up-to-date. > Updating

Re: [pfSense] yesterday update to 2.3.2 has not worked - these machines now can not update any more

>From the console: pkg clean pkg update pkg upgrade reboot Em 27 de jul de 2016 10:54, "WolfSec-Support" escreveu: > Hi Jim > > Many thanks for your hint. > Well it is still not working. > > See: > > >>> Updating repositories metadata... > Updating pfSense-core repository

Re: [pfSense] Removing obsolete packages

On 27/7/16 2:46 pm, Jim Pingle wrote: At the moment there is no automated way to do that, but you can edit them out of your config.xml. Either by editing in-place using "viconfig" if you're daring, familiar with vi, and don't mind the potential for danger. Or the safer route is to download a

Re: [pfSense] yesterday update to 2.3.2 has not worked - these machines now can not update any more

Hi Jim Many thanks for your hint. Well it is still not working. See: >>> Updating repositories metadata... Updating pfSense-core repository catalogue... pfSense-core repository is up-to-date. Updating pfSense repository catalogue... Fetching meta.txz: . done Fetching packagesite.txz: ... done

Re: [pfSense] Removing obsolete packages

On 07/26/2016 05:38 PM, Chris Bagnall wrote: > It would, however, be rather nice to remove the obsolete references. At the moment there is no automated way to do that, but you can edit them out of your config.xml. Either by editing in-place using "viconfig" if you're daring, familiar with vi, and

Re: [pfSense] yesterday update to 2.3.2 has not worked - these machines now can not update any more

On 07/27/2016 12:48 AM, WolfSec-Support wrote: > Any hint to solve the broken upbated-boxes ? Use ssh or the console and either use option 13, or use option 8 and from the shell, execute "pfSense-upgrade -d" Early in the upgrade process, pkg is updated and from that point, the GUI for updates

Re: [pfSense] Alerts

On 07/27/2016 07:47 AM, Luis G. Coralle wrote: > Hello everyone. > Someone knows how pfsense considered an alert? They can be customized? > There is list? There isn't an official list, but it's not very long. Usually emergency-level events or events at the very least that require the attention of

Re: [pfSense] DNS-forwarder through OpenVPN "stopped working" with 2.3.2

On 07/27/2016 08:45 AM, Philipp Tölke wrote: > since the update to 2.3.2 yesterday our external devices do not get > DNS-Replies anymore. What version was this firewall running previously? > We have configured the DNS-Forwarder to listen on the interface and > sockstat show it's listening on

[pfSense] DNS-forwarder through OpenVPN "stopped working" with 2.3.2

Hi all, since the update to 2.3.2 yesterday our external devices do not get DNS-Replies anymore. We have configured the DNS-Forwarder to listen on the interface and sockstat show it's listening on *:53. We have a rule allowing everything to pass to "self" on port 53. With tcpdump I can see that

Re: [pfSense] CIFS slow on PPTP

Karl Fife wrote: > Are you sure that CIFS is slow because of PPTP? All but the latest > CIFS/SMB protocols are poorly suited for high-latency connections such > as the public Internet (e.g. where you might use VPN). Even under the > best circumstances, many applications don't tolerate it well >

Re: [pfSense] Lightning strike

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: > > > After some > > testing, I found the system would not come up after reboot because > > it had gone into port reassignment mode since the config made >