Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    URLs for latest Dante package and dependencies?

    Routing and Multi WAN
    3
    9
    1.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      networknotwork
      last edited by networknotwork

      I'm trying to install the latest Dante SOCKS5 proxy, and all the posts I've seen, like this one, refer to FreeBSD 10/11 repos and Dante 1.4.2. How does one find the URL for the latest Dante (1.4.3) for FreeBSD 12? Just subbing 12 and 1.4.3 in the URL didn't work.

      Thanks!

      1 Reply Last reply Reply Quote 0
      • A
        AGA 0
        last edited by AGA 0

        Steps to setup DANTE on 2.6.0-RELEASE (amd64):

        pkg install cyrus-sasl

OR

pkg add https://mirrors.xtom.com/freebsd-pkg/FreeBSD%3A12%3Aamd64/quarterly/All/cyrus-sasl-2.1.28.pkg


pkg add https://mirrors.xtom.com/freebsd-pkg/FreeBSD%3A12%3Aamd64/quarterly/All/miniupnpc-2.2.4.pkg

        Due to missing DANTE for FreeBSD 12, we need to do some 'magic':

        env ABI=freebsd:11:amd64 pkg add https://mirrors.xtom.com/freebsd-pkg/FreeBSD%3A11%3Aamd64/quarterly/All/dante-1.4.3.txz

ln -s /lib/libcrypto.so.111 /lib/libcrypto.so.8
chmod 444 /lib/libcrypto.so.8

        After that you can tune your sockd.conf AND firewall rules.

        Check before putting to startup:

        /usr/local/etc/rc.d/sockd onestart

        Above worked for me, and dante started successfully, but unfortunately, Telegram desktop calls not working through dante because of (my suggestion) bug in Telegram desktop version (Telegram just ignores 'use proxy for calls' setting...). See here:
        https://github.com/telegramdesktop/tdesktop/issues/23916

        N L 3 Replies Last reply Reply Quote 0
        • N
          networknotwork @AGA 0
          last edited by

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • N
            networknotwork @AGA 0
            last edited by networknotwork

            @aga-0 pkg add produces this error:

            Certificate verification failed for /C=US/ST=New Jersey/L=Jersey City/O=The USERTRUST Network/CN=USERTrust ECC Certification Authority
35122753536:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
Certificate verification failed for /C=US/ST=New Jersey/L=Jersey City/O=The USERTRUST Network/CN=USERTrust ECC Certification Authority
35122753536:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
Certificate verification failed for /C=US/ST=New Jersey/L=Jersey City/O=The USERTRUST Network/CN=USERTrust ECC Certification Authority
35122753536:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921:
pkg: https://mirrors.xtom.com/freebsd-pkg/FreeBSD%3A14%3Aamd64/latest/All/miniupnpc-2.2.4.pkg: Authentication error

            Any idea how to fix this?

            1 Reply Last reply Reply Quote 0
            • N
              networknotwork
              last edited by

              @AGA-0 Well I got around the certificate errors by fetch-ing the package to a local file followed by pkg add but now I'm getting this error:

              warning: new client from 192.168.2.8.49263 dropped: no resources

              Googling and ChatGPT are no help.

              A 1 Reply Last reply Reply Quote 0
              • A
                AGA 0 @networknotwork
                last edited by

                @networknotwork not sure this error is related to package manager... have you tried pfsense rebooting?

                N 1 Reply Last reply Reply Quote 0
                • N
                  networknotwork @AGA 0
                  last edited by

                  @aga-0 yes tried rebooting. Using a very basic sockd.conf allowing all connections and sockd definitely starting up (can see the socket) and accepting the incoming connection, but that’s as far as it gets.

                  A 1 Reply Last reply Reply Quote 0
                  • A
                    AGA 0 @networknotwork
                    last edited by

                    @networknotwork I'm not very sophisticated in freebsd, can only say that using dante as socks5 proxy for telegram worked for me except only calls are not working, but this seems to be not dante, but Telegram issue.

                    1 Reply Last reply Reply Quote 0
                    • L
                      LA_FORGE @AGA 0
                      last edited by

                      @AGA-0
                      Thank you. It worked very well with these steps in 2.6.0 but since upgrade to 2.7.0 error is occurring again:

                      Aug  7 11:27:35 (1691404055.938356) sockd[74692]: warning: new client from 192.168.13.5.62833 dropped: no resources
                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post
                      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.