Hello,
What is wrong with the following configuration?
SocksPort 127.0.0.1:9050
TransPort 127.0.0.1:9040
DNSPort 127.0.0.1:5353
AutomapHostsOnResolve 1
VirtualAddrNetworkIPv4 10.192.0.0/10
Why can’t I see the port 5353?
Thank you.
UDP port 5353 might have been in use when tor started ( Multicast DNS uses port 5353 too ), could you try other ports please? On Linux you can use ss -ulpn 'sport = :5353' to see if UDP port 5353 is in use.
Hello,
The output is:
# ss -ulpn ‘sport = :5353’
State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
I changed the configuration as follows:
SocksPort 127.0.0.1:9050
TransPort 127.0.0.1:9040
DNSPort 127.0.0.1:5353
AutomapHostsOnResolve 1
VirtualAddrNetworkIPv4 10.192.0.0/10
TransListenAddress 0.0.0.0
DNSPort 0.0.0.0:5353
But:
Tor 0.4.9.8 died: Caught signal 11
/usr/bin/tor(+0xf2060) [0x55cb2aa38060]
/usr/bin/tor(smartlist_add+0x1c) [0x55cb2aa55b0c]
/usr/bin/tor(smartlist_add+0x1c) [0x55cb2aa55b0c]
/usr/bin/tor(retry_all_listeners+0x602) [0x55cb2aaee772]
/usr/bin/tor(+0x6ef8a) [0x55cb2a9b4f8a]
/usr/bin/tor(+0x8bb27) [0x55cb2a9d1b27]
/lib/x86_64-linux-gnu/libevent-2.1.so.7(+0x21a4e) [0x7f4f7eb6fa4e]
/lib/x86_64-linux-gnu/libevent-2.1.so.7(event_base_loop+0x49f) [0x7f4f7eb7013f]
/usr/bin/tor(do_main_loop+0xf5) [0x55cb2a9b8b85]
/usr/bin/tor(tor_run_main+0x1e5) [0x55cb2a9b42b5]
/usr/bin/tor(tor_main+0x5b) [0x55cb2a9b04ab]
/usr/bin/tor(main+0x1d) [0x55cb2a9b003d]
/lib/x86_64-linux-gnu/libc.so.6(+0x29ca8) [0x7f4f7dfebca8]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7f4f7dfebd65]
/usr/bin/tor(_start+0x21) [0x55cb2a9b0091]
May 16 01:56:40.000 [notice] Tor 0.4.9.8 opening log file.
May 16 01:56:40.518 [notice] We compiled with OpenSSL 30500050: OpenSSL 3.5.5 27 Jan 2026 and we are running with OpenSSL 30500010: 3.5.1. These two versions should be binary compatible.
May 16 01:56:40.523 [notice] Tor 0.4.9.8 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.5.1, Zlib 1.3.1, Liblzma 5.8.1, Libzstd 1.5.7 and Glibc 2.41 as libc.
May 16 01:56:40.524 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at
May 16 01:56:40.524 [notice] Read configuration file “/usr/share/tor/tor-service-defaults-torrc”.
May 16 01:56:40.524 [notice] Read configuration file “/etc/tor/torrc”.
May 16 01:56:40.526 [warn] Skipping obsolete configuration option “TransListenAddress”.
May 16 01:56:40.527 [warn] You specified a public address ‘0.0.0.0:5353’ for DNSPort. Other people on the Internet might find your computer and use it as an open proxy. Please don’t allow this unless you have a good reason.
May 16 01:56:40.528 [warn] You specified a public address ‘0.0.0.0:5353’ for DNSPort. Other people on the Internet might find your computer and use it as an open proxy. Please don’t allow this unless you have a good reason.
May 16 01:56:40.529 [notice] Opening Socks listener on 127.0.0.1:9050
May 16 01:56:40.529 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
May 16 01:56:40.529 [notice] Opening DNS listener on 127.0.0.1:5353
May 16 01:56:40.529 [notice] Opened DNS listener connection (ready) on 127.0.0.1:5353
May 16 01:56:40.529 [notice] Opening DNS listener on 0.0.0.0:5353
May 16 01:56:40.529 [notice] Opened DNS listener connection (ready) on 0.0.0.0:5353
May 16 01:56:40.530 [notice] Opening Transparent pf/netfilter listener on 127.0.0.1:9040
May 16 01:56:40.530 [notice] Opened Transparent pf/netfilter listener connection (ready) on 127.0.0.1:9040
May 16 01:56:40.000 [notice] Set list of supported TLS groups to: ?*X25519MLKEM768 / ?SecP256r1MLKEM768 / *P-256:?X25519:P-224
May 16 01:56:40.000 [notice] Bootstrapped 0% (starting): Starting
May 16 01:56:41.000 [notice] Starting with guard context “default”
May 16 01:56:41.000 [notice] Signaled readiness to systemd