PuppyIP Resource Center
Network & Connection Troubleshooting 10 min Published 2026-11-17

iStoreOS PassWall2 Reports unknown option --tproxy-mark: 15353 DNS Timeout Troubleshooting

When PassWall2 reports unknown option --tproxy-mark and dnsmasq points to an unbound 15353 port, inspect the invoked iptables command and proxy-DNS state instead of guessing a firewall backend change.

iStoreOS PassWall2 TPROXY iptables-nft unknown option DNS port 15353

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • unknown option --tproxy-mark means the current iptables invocation rejected that parameter; the message alone does not identify the right backend.
  • If dnsmasq forwards to port 15353 with no listener, DNS may time out on the router's upstream path.
  • Check the firewall invocation, proxy-DNS process and generated forwarding settings separately before changing rules.
  • Router-local results do not prove LAN recovery; test DNS, routing policy and actual access from a LAN client.

Identify the symptom: transparent-proxy rules and DNS service are related paths

On iStoreOS, if enabling PassWall2 produces unknown option --tproxy-mark while system dnsmasq still listens on port 53, generated settings forward queries to 15353 and no process listens there, check at least two parts separately: whether the iptables command accepts the rule parameter and whether the proxy-DNS process starts and binds its port. A running dnsmasq does not show that its downstream resolver is ready.

In one PassWall2 and iptables-nft 1.8.10 combination, this error proves only that the invoked command did not recognize the supplied option. The wording alone does not identify a package, extension, backend selection or startup-script adaptation issue. Do not generalize it to every iStoreOS installation or use it to justify flushing firewall rules, switching legacy/nft backends or reinstalling firmware.

Read the state first: check the iptables backend, 15353 listener and config source

Use the read-only commands below to record the iptables version identifier, PassWall2 log lines, system listeners and generated configuration mentioning 15353. Generated files may be rebuilt after a restart, so match the current service state to the configured target. A grep match does not prove that the DNS service started.

If output includes LAN addresses, node hostnames, subscription fragments or routing policies, redact it before sharing. Do not publish a complete /etc, /tmp or /var configuration bundle, and never put node credentials in commands, screenshots or tickets. If there is no current 15353 forward, this is a different path; continue with the DNS port actually in use.

Read PassWall2, iptables and DNS state

sh
iptables -V
iptables -t mangle -S 2>&1 | sed -n '1,80p'
netstat -lnp 2>/dev/null | grep -E ':(53|15353)([[:space:]]|$)'
grep -Rns '15353' /var/etc /tmp/etc /etc/config 2>/dev/null
logread | grep -iE 'passwall|tproxy-mark|chinadns|xray|sing-box' | tail -n 100
From an iStoreOS router shell, collect version, read-only rules, listeners, generated configuration and service logs. Output can contain sensitive network details; redact it before sharing.

Interpret unknown option without switching the firewall backend first

Identify the startup step that emitted the error, which iptables executable produced it and whether PassWall2 generated the parameter. iptables -V can show the current command's version and backend hint. If a read-only rule listing fails on the same option, retain the original error instead of moving on to commands that change rules. Then compare installed PassWall2, iptables, related extensions and kernel firewall packages; confirm that they come from one firmware/software-source combination.

The error does not identify whether nft or legacy is the right backend, nor does it prove that a particular extension or package is missing. Before changing packages, find maintenance guidance for the device firmware and package feed, and prepare local recovery access, a configuration backup and a known rollback package set. If the guidance does not name a package or backend combination for that firmware, do not install, downgrade or switch backends. There is no single repair command that applies to every iStoreOS and PassWall2 combination.

Treat DNS port 15353 as a separate listener check

Confirm the address and port dnsmasq forwards to, then find the listener and service configuration that generated port 15353. If nothing owns that port, a client query can time out on the router's local DNS path before reaching a proxy core. Do not describe this as a bad node until you know the request reached the core. Check PassWall2 startup order, whether a core exited, the first error in the logs and whether the selected DNS component was expected to bind that address.

Temporarily bypassing PassWall2 DNS changes dnsmasq's upstream path and may also change client- or domain-based routing. First identify the actual dnsmasq forward entry, the DNS address given to LAN clients and a configured, reachable system upstream. Only after confirming the exact entry and rollback target should you back up and adjust that setting, then immediately verify DNS, proxy policy and external access from a LAN client. If the entry or upstream is unknown, do not clear all DNS settings or change the firewall globally.

A router-local check cannot replace LAN client verification

You may compare router-originated DNS requests with router-local proxying enabled and disabled, but record and restore the original setting. If disabling router-local proxy changes only the router's own access, that result describes its outbound path. It does not prove that transparent proxying, DHCP DNS, routing marks or website access work for wireless or wired LAN clients.

For a LAN check, use an authorized client to confirm which DNS address it received, then observe name resolution, connectivity to the router and the destination response separately. Do not simultaneously change the node, DNS mode, proxy scope and firewall backend. If LAN access still fails or has not been checked, record it as pending; do not describe a router-only result as a complete fix.

Stop conditions, rollback and acceptance checks

Stop configuration changes if you cannot identify the iptables command that ran, the rules generated by PassWall2, the process expected to listen on 15353, or whether the firewall still allows management access. Record firmware and package versions, startup time, redacted log lines and listener output. Do not publish complete rules, configuration files or node details.

If you have only router-local option errors and listener results, and have not tested a LAN client, mark LAN recovery as pending verification. Keep a network configuration backup and local recovery method before changing settings. Ask a maintainer familiar with the firmware's package feed to confirm a compatible package or backend plan. Confirm recovery only after router DNS, the proxy core, LAN-client resolution and actual access all work.

Sources

Frequently Asked Questions

Does unknown option --tproxy-mark prove I must switch to iptables-legacy?

No. It shows that this invocation rejected the option, but does not identify the correct backend, missing extension or matching package release. Collect versions and call context first.

Does dnsmasq forwarding to 15353 mean Xray is handling DNS?

No. A configured forward does not prove that a DNS core is listening. Check the actual listener PID, startup log and selected DNS component.

If disabling router-local proxy restores router access, is the LAN fixed?

No. The setting can change the router's own traffic path. Check DHCP-provided DNS, resolution and destination access from a LAN client separately.

Can I flush iptables and restart PassWall2 first?

Do not. Flushing rules can remove forwarding, firewall protection and remote management access, and there is no confirmed evidence that stale rules are the cause. Preserve state and inspect package versions and service logs.