fix: support SOCKS5 IPv6 literal destinations

docs/man/bssh.1

@@ -124,6 +124,7 @@ Example: -R 8080:localhost:80 (remote:8080 → localhost:80)
 .BR \-D " " \fI[bind_address:]port[/socks_version]\fR
 Dynamic port forwarding (SOCKS proxy). Creates a local SOCKS proxy that dynamically forwards connections via SSH.
 Supports SOCKS4 and SOCKS5 protocols. Default is SOCKS5.
+SOCKS5 accepts IPv4 literals, domain names, and IPv6 literals.
 Multiple -D options can be specified for multiple SOCKS proxies.
 Example: -D 1080 (SOCKS5 proxy on localhost:1080), -D *:1080/4 (SOCKS4 on all interfaces)
 
@@ -1213,7 +1214,10 @@ but are rejected under
 .B \-6
 or
 .I AddressFamily inet6
-with the usual forced-family error instead of silently tunneling IPv4.
+with the usual forced-family error instead of silently tunneling IPv4. SOCKS5
+literal IPv4 and IPv6 requests likewise already carry numeric destinations; when
+a forced family excludes that literal, the request fails with the same
+no-address-for-family error instead of silently falling back to the other family.
 
 .SS What the constraint does not cover
 The remote listener created by

src/cli/bssh.rs

@@ -325,7 +325,7 @@ pub struct Cli {
         long = "dynamic-forward",
         value_name = "dynamic_forward_spec",
         action = clap::ArgAction::Append,
-        help = "Dynamic port forwarding (SOCKS proxy) [bind_address:]port[/socks_version]\nCreates a local SOCKS proxy that dynamically forwards connections via SSH.\nMultiple -D options can be specified for multiple SOCKS proxies.\nSOCKS4 destinations are IPv4-only by protocol and are rejected when -6 or AddressFamily inet6 is forced.\nExample: -D 1080 (SOCKS5 proxy on localhost:1080), -D *:1080/4 (SOCKS4 on all interfaces)"
+        help = "Dynamic port forwarding (SOCKS proxy) [bind_address:]port[/socks_version]\nCreates a local SOCKS proxy that dynamically forwards connections via SSH.\nSOCKS5 accepts IPv4 literals, domain names, and IPv6 literals; SOCKS4 destinations are IPv4-only and fail when IPv6 is forced.\nMultiple -D options can be specified for multiple SOCKS proxies.\nExample: -D 1080 (SOCKS5 proxy on localhost:1080), -D *:1080/4 (SOCKS4 on all interfaces)"
     )]
     pub dynamic_forwards: Vec<String>,
 }