The pfSense Store

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Maxburn

Pages: [1]
1
General Questions / Re: HOWTO: Notifications with GMAIL SMTP
« on: Yesterday at 01:21:26 pm »
It appears google app passwords are a part of the paid google services (as of Jan 2018). If you try to use the above URL's to get an app password you will see "The setting you are looking for is not available for your account. GO TO MY ACCOUNT".

What you must do is set up the page as shown in OP, with your regular gmail password. Click test a couple times and it will fail. Then go log into that account and look for the security messages saying account access was blocked. You must click "this was me" and allow the connection. Further test email in pfsense should work then.

Probably a good idea to not use your main gmail account to send from due to this, just register a secondary.

2
DHCP and DNS / Re: Dynamic DNS, freedns.afraid.org
« on: January 13, 2018, 04:11:16 pm »
Edit; these appear to be the correct instructions. Lots of misinformation out there.

https://geeklk.com/2016/08/25/pfsense-configure-dynamic-dns-freedns/

-----------------------------------------------------------------------------------------
Found this old post talking about the ID string. Changed my entry to that and now cached IP shows N/A.

https://forum.pfsense.org/index.php?topic=23980.0

Then found this newer guide that shows I should have set it up the way I did at first.

https://community.spiceworks.com/how_to/126203-dynamicdns-freedns-on-pfsense

3
DHCP and DNS / Dynamic DNS, freedns.afraid.org
« on: January 13, 2018, 02:44:24 pm »
Services -> Dynamic DNS -> Dynamic DNS Clients -> Add -> "Service Type" = freeDNS

I stopped DDClient on my Ubuntu machine and entered my info with user/password into pfSense, didn't get any errors when setting it up but does not go green in the list, cached IP stays 0.0.0.0 (red) and status, services doesn't list DDNS. Don't see it mentioned in logs. Check IP seems to be running. So why isn't it doing anything? Can I see a failed log or status somewhere?

4
Packages / Re: NUT package
« on: January 11, 2018, 02:44:47 pm »
Is this the right package to monitor a UPS and shut down pfsense if I get a low battery?

I'm poking around and tried to add a remote snmp UPS but there doesn't seem to be a field to specify a community string. I don't run public for obvious reasons.

Edit; it's a Liebert GXT. My synology had no issue monitoring it and doing shutdown. Looked through the MAN pages linked under advanced config and didn't see anything mentioning community strings.

Edit2; added public in the UPS and it worked, where can I specify that in this package?

Also where do I specify shutdown settings?

5
Thanks for that list, should have started with the most obvious being that WAN wasn't getting an IP lease. Everything working much better now after fixing that.

6
On a hunch my PiHole on my network was blocking it I connected WAN straight to my cable modem and had pfsense reboot. In that configuration windows still was reporting no internet connection and I couldn't reach this site for example but the pkg update comes back differently now. Even reset to defaults and reran the wizard same results.

Quote
Updating pfSense-core repository catalogue...
pkg: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory
pkg: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-core/meta.txz: No address record
repository pfSense-core has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-core/packagesite.txz: No address record
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory
pkg: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-pfSense_v2_4_2/meta.txz: No address record
repository pfSense has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-pfSense_v2_4_2/packagesite.txz: No address record
Unable to update repository pfSense
Error updating repositories!

7
note; I'm very new to pfsense

Problem:
Edit: the larger problem seems to be no internet access. I thought the wizard would leave me with a working router but I guess not.
Under Package Manager/Available Packages I'm getting: Unable to retrieve package information. Searched around a bit and found some advice regarding pkg clean, pkg update, pkg upgrade, reboot. Errors for those are below, and searching around I'm seeing results from 2.3 failed upgrades and it being necessary to create directories for these missing files or directories but this being a brand new install this all seems weird, what's wrong?

History:
I installed 2.4.2 release last night and went through the wizard choosing mostly defaults, nothing strange I'm aware of, chose 9.9.9.9 and 8.8.4.4 for DNS. I didn't have the WAN connected, I wanted to have everything in and working before I connected it to the internet. Now with everything connected it acts as a router fine and update check says it's good.

Results from pkg clean
Quote
pkg: Repository pfSense-core missing. 'pkg update' required
pkg: No package database installed.  Nothing to do!

Results from pkg update
Quote
Updating pfSense-core repository catalogue...
pkg: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
pkg: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-core/meta.txz: Authentication error
repository pfSense-core has no meta file, using default settings
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
pkg: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-core/packagesite.txz: Authentication error
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
pkg: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-pfSense_v2_4_2/meta.txz: Authentication error
repository pfSense has no meta file, using default settings
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
Certificate verification failed for /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
34405241800:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:/builder/ce-242/tmp/FreeBSD-src/crypto/openssl/ssl/s3_clnt.c:1269:
pkg: https://pkg.pfsense.org/pfSense_v2_4_2_amd64-pfSense_v2_4_2/packagesite.txz: Authentication error
Unable to update repository pfSense
Error updating repositories!


8
IDS/IPS / Re: Snort + SG-3100 = exited on signal 10
« on: January 01, 2018, 01:37:27 pm »
Ouch, I literally just bought one of these today because I wanted to get introduced to pfSense and things like Snort. Saw mention elsewhere it didn't work on the SG1000 but missed this about the SG3100. I'm subscribed and best of luck but I think I'm going to put in more research on Qotom.

Pages: [1]