Categories

  • Discussions about TNSR

    462 Topics
    1k Posts
    A
    @Said.Fathy , Hi Said .. I'd strongly recommend Lawrence Systems' youtube channel... it's the best as far as pfsense is concerned.. from beginner to pro https://www.youtube.com/@LAWRENCESYSTEMS

  • Discussions about pfSense Software, click a category below

    121k Topics
    767k Posts
    RahzadanR
    My WAN type is IPv4 DHCP. DNS config: [image: 1758148242529-dns.png] I have around 20 DNS IP's in General Setup. It's never been an issue before. Here is the output of pkg -d update: DBG(1)[4374]> pkg initialized Updating pfSense-core repository catalogue... DBG(1)[4374]> PkgRepo: verifying update for pfSense-core DBG(1)[4374]> Pkgrepo, begin update of '/var/db/pkg/repos/pfSense-core/db' DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.conf DBG(1)[4374]> curl_open pkg: No SRV record found for the repo 'pfSense-core' DBG(1)[4374]> Fetch: fetcher used: pkg+https DBG(1)[4374]> curl> fetching https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.conf DBG(1)[4374]> CURL> No mirror set url to https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.conf DBG(1)[4374]> CURL> attempting to fetch from https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.conf, left retry 3 * Couldn't find host pkg.pfsense.org in the .netrc file; using defaults * Could not resolve host: pkg.pfsense.org * Closing connection DBG(1)[4374]> CURL> No mirror set url to https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.conf DBG(1)[4374]> CURL> attempting to fetch from https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.conf, left retry 2 * Couldn't find host pkg.pfsense.org in the .netrc file; using defaults * Could not resolve host: pkg.pfsense.org * Closing connection DBG(1)[4374]> CURL> No mirror set url to https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.conf DBG(1)[4374]> CURL> attempting to fetch from https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.conf, left retry 1 * Couldn't find host pkg.pfsense.org in the .netrc file; using defaults * Could not resolve host: pkg.pfsense.org * Closing connection pkg: An error occured while fetching package DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.txz pkg: packagesite URL error for pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.txz -- pkg+:// implies SRV mirror type repository pfSense-core has no meta file, using default settings DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/data.pkg pkg: packagesite URL error for pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/data.pkg -- pkg+:// implies SRV mirror type DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/data.tzst pkg: packagesite URL error for pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/data.tzst -- pkg+:// implies SRV mirror type DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/packagesite.pkg pkg: packagesite URL error for pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/packagesite.pkg -- pkg+:// implies SRV mirror type DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/packagesite.tzst pkg: packagesite URL error for pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/packagesite.tzst -- pkg+:// implies SRV mirror type Unable to update repository pfSense-core Updating pfSense repository catalogue... DBG(1)[4374]> PkgRepo: verifying update for pfSense DBG(1)[4374]> Pkgrepo, begin update of '/var/db/pkg/repos/pfSense/db' DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf DBG(1)[4374]> curl_open pkg: No SRV record found for the repo 'pfSense' DBG(1)[4374]> Fetch: fetcher used: pkg+https DBG(1)[4374]> curl> fetching https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf DBG(1)[4374]> CURL> No mirror set url to https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf DBG(1)[4374]> CURL> attempting to fetch from https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf, left retry 3 * Couldn't find host pkg.pfsense.org in the .netrc file; using defaults * Could not resolve host: pkg.pfsense.org * Closing connection DBG(1)[4374]> CURL> No mirror set url to https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf DBG(1)[4374]> CURL> attempting to fetch from https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf, left retry 2 * Couldn't find host pkg.pfsense.org in the .netrc file; using defaults * Could not resolve host: pkg.pfsense.org * Closing connection DBG(1)[4374]> CURL> No mirror set url to https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf DBG(1)[4374]> CURL> attempting to fetch from https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf, left retry 1 * Couldn't find host pkg.pfsense.org in the .netrc file; using defaults * Could not resolve host: pkg.pfsense.org * Closing connection pkg: An error occured while fetching package DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.txz pkg: packagesite URL error for pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.txz -- pkg+:// implies SRV mirror type repository pfSense has no meta file, using default settings DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/data.pkg pkg: packagesite URL error for pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/data.pkg -- pkg+:// implies SRV mirror type DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/data.tzst pkg: packagesite URL error for pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/data.tzst -- pkg+:// implies SRV mirror type DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/packagesite.pkg pkg: packagesite URL error for pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/packagesite.pkg -- pkg+:// implies SRV mirror type DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/packagesite.tzst pkg: packagesite URL error for pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/packagesite.tzst -- pkg+:// implies SRV mirror type Unable to update repository pfSense Error updating repositories! If I run pkg -d update 3-4 times, the output changes slightly: DBG(1)[8135]> pkg initialized Updating pfSense-core repository catalogue... DBG(1)[8135]> PkgRepo: verifying update for pfSense-core DBG(1)[8135]> Pkgrepo, begin update of '/var/db/pkg/repos/pfSense-core/db' DBG(1)[8135]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.conf DBG(1)[8135]> curl_open DBG(1)[8135]> Fetch: fetcher used: pkg+https DBG(1)[8135]> curl> fetching https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.conf DBG(1)[8135]> CURL> attempting to fetch from , left retry 3 * Couldn't find host pkg01-atx.netgate.com in the .netrc file; using defaults * Host pkg01-atx.netgate.com:443 was resolved. * IPv6: 2610:160:11:18::209 * IPv4: 208.123.73.209 * Trying 208.123.73.209:443... * Connected to pkg01-atx.netgate.com (208.123.73.209) port 443 * ALPN: curl offers http/1.1 * CAfile: none * CApath: /etc/ssl/certs/ * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / X25519 / RSASSA-PSS * ALPN: server accepted http/1.1 * Server certificate: * subject: CN=*.netgate.com * start date: Apr 10 00:00:00 2025 GMT * expire date: May 11 23:59:59 2026 GMT * subjectAltName: host "pkg01-atx.netgate.com" matched cert's "*.netgate.com" * issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA * SSL certificate verify ok. * Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha384WithRSAEncryption * Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha384WithRSAEncryption * using HTTP/1.x > GET /pfSense_v2_8_1_amd64-core/meta.conf HTTP/1.1 Host: pkg01-atx.netgate.com User-Agent: pkg/1.21.3 Accept: */* If-Modified-Since: Thu, 28 Aug 2025 16:50:33 GMT * Request completely sent off < HTTP/1.1 200 OK Fetching meta.conf: < Server: nginx < Date: Wed, 17 Sep 2025 22:26:01 GMT < Content-Type: application/octet-stream < Content-Length: 179 < Last-Modified: Thu, 28 Aug 2025 16:50:33 GMT < Connection: keep-alive < ETag: "68b088d9-b3" < Strict-Transport-Security: max-age=31536000; preload < X-Content-Type-Options: nosniff < X-XSS-Protection: 1; mode=block < X-Robots-Tag: all < X-Download-Options: noopen < X-Permitted-Cross-Domain-Policies: none < Accept-Ranges: bytes < * The requested document is not new enough * Simulate an HTTP 304 response * Closing connection DBG(1)[8135]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/data.pkg DBG(1)[8135]> curl_open DBG(1)[8135]> Fetch: fetcher used: pkg+https DBG(1)[8135]> curl> fetching https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/data.pkg DBG(1)[8135]> CURL> attempting to fetch from , left retry 3 * Couldn't find host pkg01-atx.netgate.com in the .netrc file; using defaults * Hostname pkg01-atx.netgate.com was found in DNS cache * Trying 208.123.73.209:443... * Connected to pkg01-atx.netgate.com (208.123.73.209) port 443 * ALPN: curl offers http/1.1 * CAfile: none * CApath: /etc/ssl/certs/ * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / X25519 / RSASSA-PSS * ALPN: server accepted http/1.1 * Server certificate: * subject: CN=*.netgate.com * start date: Apr 10 00:00:00 2025 GMT * expire date: May 11 23:59:59 2026 GMT * subjectAltName: host "pkg01-atx.netgate.com" matched cert's "*.netgate.com" * issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA * SSL certificate verify ok. * Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha384WithRSAEncryption * Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha384WithRSAEncryption * using HTTP/1.x > GET /pfSense_v2_8_1_amd64-core/data.pkg HTTP/1.1 Host: pkg01-atx.netgate.com User-Agent: pkg/1.21.3 Accept: */* If-Modified-Since: Thu, 28 Aug 2025 16:50:33 GMT * Request completely sent off < HTTP/1.1 200 OK Fetching data.pkg: < Server: nginx < Date: Wed, 17 Sep 2025 22:26:01 GMT < Content-Type: application/octet-stream < Content-Length: 1632 < Last-Modified: Thu, 28 Aug 2025 16:50:33 GMT < Connection: keep-alive < ETag: "68b088d9-660" < Strict-Transport-Security: max-age=31536000; preload < X-Content-Type-Options: nosniff < X-XSS-Protection: 1; mode=block < X-Robots-Tag: all < X-Download-Options: noopen < X-Permitted-Cross-Domain-Policies: none < Accept-Ranges: bytes < * The requested document is not new enough * Simulate an HTTP 304 response * Closing connection pfSense-core repository is up to date. Updating pfSense repository catalogue... DBG(1)[8135]> PkgRepo: verifying update for pfSense DBG(1)[8135]> Pkgrepo, begin update of '/var/db/pkg/repos/pfSense/db' DBG(1)[8135]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf DBG(1)[8135]> curl_open DBG(1)[8135]> Fetch: fetcher used: pkg+https DBG(1)[8135]> curl> fetching https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf DBG(1)[8135]> CURL> attempting to fetch from , left retry 3 * Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults * Host pkg00-atx.netgate.com:443 was resolved. * IPv6: 2610:160:11:18::207 * IPv4: 208.123.73.207 * Trying 208.123.73.207:443... * Connected to pkg00-atx.netgate.com (208.123.73.207) port 443 * ALPN: curl offers http/1.1 * CAfile: none * CApath: /etc/ssl/certs/ * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / X25519 / RSASSA-PSS * ALPN: server accepted http/1.1 * Server certificate: * subject: CN=*.netgate.com * start date: Apr 10 00:00:00 2025 GMT * expire date: May 11 23:59:59 2026 GMT * subjectAltName: host "pkg00-atx.netgate.com" matched cert's "*.netgate.com" * issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA * SSL certificate verify ok. * Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha384WithRSAEncryption * Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha384WithRSAEncryption * using HTTP/1.x > GET /pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf HTTP/1.1 Host: pkg00-atx.netgate.com User-Agent: pkg/1.21.3 Accept: */* If-Modified-Since: Mon, 15 Sep 2025 15:21:37 GMT * Request completely sent off < HTTP/1.1 200 OK Fetching meta.conf: < Server: nginx < Date: Wed, 17 Sep 2025 22:26:02 GMT < Content-Type: application/octet-stream < Content-Length: 179 < Last-Modified: Mon, 15 Sep 2025 15:21:37 GMT < Connection: keep-alive < ETag: "68c82f01-b3" < Strict-Transport-Security: max-age=31536000; preload < X-Content-Type-Options: nosniff < X-XSS-Protection: 1; mode=block < X-Robots-Tag: all < X-Download-Options: noopen < X-Permitted-Cross-Domain-Policies: none < Accept-Ranges: bytes < * The requested document is not new enough * Simulate an HTTP 304 response * Closing connection DBG(1)[8135]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/data.pkg DBG(1)[8135]> curl_open DBG(1)[8135]> Fetch: fetcher used: pkg+https DBG(1)[8135]> curl> fetching https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/data.pkg DBG(1)[8135]> CURL> attempting to fetch from , left retry 3 * Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults * Hostname pkg00-atx.netgate.com was found in DNS cache * Trying 208.123.73.207:443... * Connected to pkg00-atx.netgate.com (208.123.73.207) port 443 * ALPN: curl offers http/1.1 * CAfile: none * CApath: /etc/ssl/certs/ * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / X25519 / RSASSA-PSS * ALPN: server accepted http/1.1 * Server certificate: * subject: CN=*.netgate.com * start date: Apr 10 00:00:00 2025 GMT * expire date: May 11 23:59:59 2026 GMT * subjectAltName: host "pkg00-atx.netgate.com" matched cert's "*.netgate.com" * issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA * SSL certificate verify ok. * Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha384WithRSAEncryption * Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha384WithRSAEncryption * using HTTP/1.x > GET /pfSense_v2_8_1_amd64-pfSense_v2_8_1/data.pkg HTTP/1.1 Host: pkg00-atx.netgate.com User-Agent: pkg/1.21.3 Accept: */* If-Modified-Since: Mon, 15 Sep 2025 15:21:37 GMT * Request completely sent off < HTTP/1.1 200 OK Fetching data.pkg: < Server: nginx < Date: Wed, 17 Sep 2025 22:26:02 GMT < Content-Type: application/octet-stream < Content-Length: 189698 < Last-Modified: Mon, 15 Sep 2025 15:21:37 GMT < Connection: keep-alive < ETag: "68c82f01-2e502" < Strict-Transport-Security: max-age=31536000; preload < X-Content-Type-Options: nosniff < X-XSS-Protection: 1; mode=block < X-Robots-Tag: all < X-Download-Options: noopen < X-Permitted-Cross-Domain-Policies: none < Accept-Ranges: bytes < * The requested document is not new enough * Simulate an HTTP 304 response * Closing connection pfSense repository is up to date. All repositories are up to date.

  • Discussions about pfSense software packages

    20k Topics
    128k Posts
    bmeeksB
    Just FYI -- upstream released 7.0.12 yesterday.

  • Discuss pfSense in other languages

    43k Topics
    267k Posts
    chris1284C
    Ich denke die Antwort nun hier im englischen Teil gefunden zu haben https://forum.netgate.com/topic/185693/ha-setup-with-multi-wan-and-dhcp-guide

  • Information about hardware available from Netgate

    3k Topics
    21k Posts
    J
    @w0w Thanks very much for the details/info. I will look through it and see if they say anything about mitigation. It does not matter whose fault it is. It still reflects badly on Netgate, too.

  • Information about hardware available from Netgate

    44 Topics
    211 Posts
    AriKellyA
    It looks like unified web management could be coming soon. It would be great if it means easier control and management of all web services in one place. Let's see if any companies announce more details about it!

  • Feel free to talk about anything and everything here

    3k Topics
    19k Posts
    F
    Wa salam, I'm also new and I have a question but don't know from where I start do you have any experience?
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.