HQY

某知名国产备份软件公司疑似爆雷：附全球备份软件真实评测！

Mon, 25 May 2026 17:43:53 +0800

近网传上海某知名国产备份软件厂商疑似爆雷，众多员工集体维权。

该公司今年4月份已经启动了集体降薪。

强制员工签署薪资调整协议。

作为一个在备份容灾领域工作了20多年的老司机。这家公司在成立之初，老司机就和他们打过交道。

作为国产软件，起步晚，底子薄。

为了和强势的国外备份软件厂商竞争：为了抢占市场；长期实行低价策略，也为项目的质量保证和验收付款埋下了隐患。当然用户低价本身就存在这些风险！

笔者在10年前浙江的一著名企业投标遇到过该软件公司。

该公司5万多人的网盘的项目，投标价格40W左右，还送用户4台服务器。并承诺大量二次开发。投标价格是其他几家的1/N.....

最终本项目无法验收收款，该软件公司还把该用户告上了法庭。

最终这个用户花了几年时间，项目无法验收。除了项目失败之外，也花了N倍的钱重新招标采购。

3proxy安装配置实践

Sun, 24 May 2026 22:47:09 +0800

3proxy安装配置实践

前言

本文推荐的是3proxy但是也不能不提一下SSH端口转发，因为很多使用场景可能只需要借助SSH即可实现。SSH有三种端口转发模式，本地端口转发(Local Port Forwarding)，远程端口转发(Remote Port Forwarding)以及动态端口转发(Dynamic Port Forwarding)。对于本地/远程端口转发，两者的方向恰好相反。动态端口转发则可以用于科学上网。3roxy的角色类似于CCProxy，如果你熟悉CCProxy那配置3proxy应该也不会存在太大问题。

3proxy tiny free proxy server

扩展阅读

3proxy - https://3proxy.ru/

3proxy简介

3proxy是一款代理软件支持http/socks，支持windows和linux平台，安装和配置都很简单
http://3proxy.ru/

详细的配置文档可以参考3proxy documentation How To (English, very incomplete)
https://3proxy.ru/doc/howtoe.html

关于3proxy的比较好的资料是
http://linux.die.net/man/3/3proxy.cfg
https://github.com/z3APA3A/3proxy/wiki

3proxy安装配置

Linux

3proxy的代码代管在github上面，地址是：
https://github.com/z3APA3A/3proxy

最新版的安装包(包括rpm,deb)下载地址:
https://3proxy.org/download/stable/

安装步骤如下：

# 通过git下载最新版3proxy源码
git clone https://github.com/z3APA3A/3proxy.git
# 切换到3proxy目录
cd 3proxy
# 编译3proxy,如果你的系统没有gcc，你需求先安装gcc
make -f Makefile.Linux
# 安装3proxy
make -f Makefile.Linux install

编辑生成3proxy.cfg配置文件

cat /etc/3proxy/conf/3proxy.cfg

#!/usr/local/bin/3proxy

#nserver 8.8.8.8
#nserver 8.8.4.4
nscache 65536
maxconn 1000
log /logs/3proxy-%y%m%d.log D
rotate 7
external 0.0.0.0
internal 0.0.0.0
auth none
allow *
proxy -a -p6666
socks -p6667

执行配置文件，如果有报错比如日志目录不存在和语法错误都会有具体提示

3proxy 3proxy.cfg

后台执行

3proxy 3proxy.cfg &

Windows

Windows安装3proxy
https://cloud.tencent.com/developer/article/1567809

# string into 3proxy.cfg. Now, start command prompt (cmd.exe). Change directory to 3proxy installation and run 3proxy.exe --install:
D:\>C:
C:\>cd C:\Program Files\3proxy
C:\Program Files\3proxy>3proxy.exe --install

# Now, you should have 3proxy service installed and running. If service is not started, remove "service" string from 3proxy.cfg, run 3proxy.exe manually and correct all errors.
# To remove 3proxy run 3proxy --remove:

D:\>C:
C:\>cd C:\Program Files\3proxy
C:\Program Files\3proxy>net stop 3proxy
C:\Program Files\3proxy>3proxy.exe --remove

3proxy配置文件解释

How To (English, very incomplete)
https://3proxy.org/doc/howtoe.html
https://github.com/3proxy/3proxy/wiki/How-To-(incomplete)

Recommendations for high load
https://3proxy.org/doc/highload.html
https://github.com/3proxy/3proxy/wiki/High%20Load

proxy -v

proxy of 3proxy-0.9.4 ()
Usage: proxy options
Available options are:
 -I inetd mode (requires real socket, doesn't work with TTY)
 -l@IDENT log to syslog IDENT
 -d go to background (daemon)
 -Di(DEVICENAME) bind internal interface to device, e.g. eth1
 -De(DEVICENAME) bind external interface to device, e.g. eth1
 -fFORMAT logging format (see documentation)
 -l log to stderr
 -lFILENAME log to FILENAME
 -b(BUFSIZE) size of network buffer (default 4096 for TCP, 16384 for UDP)
 -S(STACKSIZE) value to add to default client thread stack size
 -t be silent (do not log service start/stop)

 -iIP ip address or internal interface (clients are expected to connect)
 -eIP ip address or external interface (outgoing connection will have this)
 -rHOST:PORT Use IP:port for connect back proxy instead of listen port
 -RHOST:PORT Use PORT to listen connect back proxy connection to pass data to
 -4 Use IPv4 for outgoing connections
 -6 Use IPv6 for outgoing connections
 -46 Prefer IPv4 for outgoing connections, use both IPv4 and IPv6
 -64 Prefer IPv6 for outgoing connections, use both IPv4 and IPv6
 -ocOPTIONS, -osOPTIONS, -olOPTIONS, -orOPTIONS -oROPTIONS - options for
 to-client (oc), to-server (os), listening (ol) socket, connect back client
 (or) socket, connect back server (oR) listening socket
 where possible options are:
	TCP_NODELAY
	TCP_CORK
	TCP_DEFER_ACCEPT
	TCP_QUICKACK
	SO_REUSEADDR
	SO_REUSEPORT
	SO_KEEPALIVE
	SO_DONTROUTE
	IP_TRANSPARENT
 -pPORT - service port to accept connections
-a - anonymous proxy
-a1 - anonymous proxy with random client IP spoofing
	Example: proxy -i127.0.0.1

(c)3APA3A, Vladimir Dubrovin & 3proxy.org
Documentation and sources: https://3proxy.org/

3proxy -v
Usage: 3proxy [conffile]

 if conffile is missing, configuration is expected from stdin
available socket options:
	TCP_NODELAY
	TCP_CORK
	TCP_DEFER_ACCEPT
	TCP_QUICKACK
	SO_REUSEADDR
	SO_REUSEPORT
	SO_KEEPALIVE
	SO_DONTROUTE
	IP_TRANSPARENT

3proxy tiny proxy server 3proxy-0.9.4 ()
(c)3APA3A, Vladimir Dubrovin & 3proxy.org
Documentation and sources: https://3proxy.org/
Please read license agreement in 'copying' file.
You may not use this program without accepting license agreement

3proxy.cfg

https://3proxy.org/doc/man3/3proxy.cfg.3.html

Common structure:
Configuration file is a text file 3proxy reads configuration from. Each line of the file is a command executed immediately, as it was given from console. Sequence of commands is important. Configuration file as actually a script for 3proxy executable. Each line of the file is treated as a blank (space or tab) separated command line. Additional space characters are ignored. Think about 3proxy as "application level router" with console interface.

Comments:
Any string beginning with space character or ´#´ character is comment. It´s ignored. <LF>s are ignored. <CR> is end of command.

Quotation:
Quotation character is " (double quote). Quotation must be used to quote spaces or another special characters. To use quotation character inside quotation character must be dubbed (BASIC convention). For example to use HELLO "WORLD" as an argument you should use it as "HELLO ""WORLD""". Good practice is to quote any argument you use.

File inclusion:
You can include file by using $FILENAME macro (replace FILENAME with a path to file, for example $/usr/local/etc/3proxy/conf.incl or
$"c:\\Program Files\3proxy\include.cfg" Quotation is required in last example because path contains space character. For included file <CR> (end of line characters) is treated as space character (arguments delimiter instead of end of command delimiter). Thus, include files are only useful to store long signle-line commands (like userlist, network lists, etc). To use dollar sign somewhere in argument it must be quoted. Recursion is not allowed.

Next commands start gateway services:

proxy [options]
socks [options]
pop3p [options]
ftppr [options]
admin [options]
dnspr [options]
tcppm [options] <SRCPORT> <DSTADDR> <DSTPORT>
udppm [options] <SRCPORT> <DSTADDR> <DSTPORT>
Descriptions:
proxy HTTP/HTTPS proxy (default port 3128)
socks SOCKS 4/4.5/5 proxy (default port 1080)
pop3p POP3 proxy (default port 110)
ftppr FTP proxy (default port 21)
admin Web interface (default port 80)
dnspr caching DNS proxy (default port 53)
tcppm TCP portmapper
udppm UDP portmapper

Options:
-pNUMBER change default server port to NUMBER
-n disable NTLM authentication (required if passwords are stored in Unix crypt format).
-n1 enable NTLMv1 authentication.
-s
(for admin) secure, allow only secure operations, currently only traffic counters view without ability to reset.
(for dnspr) simple, do not use resolver and 3proxy cache, always use external DNS server.
(for udppm) singlepacket, expect only one packet from both client and server
-u Never ask for username/password
-u2 (for socks) require username/password in authentication methods
-a (for proxy) anonymous proxy (no information about client reported)
-a1 (for proxy) anonymous proxy (random client information reported)
-a2 (for proxy) generate Via: and X-Forwared-For: instead of Forwarded:
-6 Only resolve IPv6 addresses. IPv4 addresses are packed in IPv6 in IPV6_V6ONLY compatible way.
-4 Only resolve IPv4 addresses
-46 Resolve IPv6 addresses if IPv4 address is not resolvable
-64 Resolve IPv4 addresses if IPv6 address is not resolvable
-RHOST:port listen on given local HOST:port for incoming connections instead of making remote outgoing connection. Can be used with another 3proxy service running -r option for connect back functionality. Most commonly used with tcppm. HOST can be given as IP or hostname, useful in case of dynamic DNS.
-rHOST:port connect to given remote HOST:port instead of listening local connection on -p or default port. Can be used with another 3proxy service running -R option for connect back functionality. Most commonly used with proxy or socks. HOST can be given as IP or hostname, useful in case of dynamic DNS.
-ocOPTIONS, -osOPTIONS, -olOPTIONS, -orOPTIONS, -oROPTIONS options for proxy-to-client (oc), proxy-to-server (os), proxy listening (ol), connect back client (or), connect back listening (oR) sockets. Options like TCP_CORK, TCP_NODELAY, TCP_DEFER_ACCEPT, TCP_QUICKACK, TCP_TIMESTAMPS, USE_TCP_FASTOPEN, SO_REUSEADDR, SO_REUSEPORT, SO_PORT_SCALABILITY, SO_REUSE_UNICASTPORT, SO_KEEPALIVE, SO_DONTROUTE may be supported depending on OS.
-DiINTERFACE, -DeINTERFACE bind internal interface / external inteface to given INTERFACE (e.g. eth0) if SO_BINDTODEVICE supported by system. You may need to run as root or to have CAP_NET_RAW capability in order to bind to interface, depending on system, so this option may require root privileges and can be incompatible with some configuraton commands like chroot and setuid (and daemon if setcap is used).
-e External address. IP address of interface proxy should initiate connections from. External IP must be specified if you need incoming connections. By default system will deside which address to use in accordance with routing table.
-i Internal address. IP address proxy accepts connections to. By default connection to any interface is accepted.
-N (for socks) External NAT address 3proxy reports to client for BIND and UDPASSOC By default external address is reported. It’s only useful in the case of IP-IP NAT (will not work for PAT)
Also, all options mentioned for proxy(8) socks(8) pop3p(8) tcppm(8) udppm(8) ftppr(8)
are also supported.
Portmapping services listen at SRCPORT and connect to DSTADDR:DSTPORT HTTP and SOCKS proxies are standard.
POP3 proxy must be configured as POP3 server and requires username in the form of: pop3username@pop3server. If POP3 proxy access must be authenticated, you can specify username as proxy_username:proxy_password:POP3_username@pop3server
DNS proxy resolves any types of records but only hostnames are cached. It requires nserver/nscache to be configured. If nserver is configured as TCP, redirections are applied on connection, so parent proxy may be used to resolve names to IP.
FTP proxy can be used as FTP server in any FTP client or configured as FTP proxy on a client with FTP proxy support. Username format is one of
FTPuser@FTPServer
FTPuser:FTPpassword@FTPserver
proxyuser:proxypassword:FTPuser:FTPpassword@FTPserver
Please note, if you use FTP client interface for FTP proxy do not add FTPpassword and FTPServer to username, because FTP client does it for you. That is, if you use 3proxy with authentication use proxyuser:proxypassword:FTPuser as FTP username, otherwise do not change original FTP user name

include <path>
Include config file

config <path>
Path to configuration file to use on 3proxy restart or to save configuration.

writable
ReOpens configuration file for write access via Web interface, and rereads it. Usually should be first command on config file but in combination with config it can be used anywhere to open alternate config file. Think twice before using it.

end
End of configuration

log [[@|&]logfile] [<LOGTYPE>]
sets logfile for all gateways
@ (for Unix) use syslog, filename is used as ident name
& use ODBC, filename consists of comma-delimited datasource,username,password (username and password are optional)
radius - use RADIUS for logging
LOGTYPE is one of:
M Monthly
W Weekly (starting from Sunday)
D Daily
H Hourly
if logfile is not specified logging goes to stdout. You can specify individual logging options for gateway by using -l option in gateway configuration.
log command supports same format specifications for filename template as "logformat" (if filename contains ´%´ sign it´s believed to be template). As with "logformat" filename must begin with ´L´ or ´G´ to specify Local or Grinwitch time zone for all time-based format specificators.

rotate <n>
how many archived log files to keep

logformat <format>
Format for log record. First symbol in format must be L (local time) or G (absolute Grinwitch time). It can be preceeded with -XXX+Y where XXX is list of characters to be filtered in user input (any non-printable characters are filtered too in this case) and Y is replacement character. For example, "-,%+ L" in the beginning of logformat means comma and percent are replaced with space and all time based elemnts are in local time zone.
You can use:

%y Year in 2 digit format
%Y Year in 4 digit format
%m Month number
%o Month abbriviature
%d Day
%H Hour
%M Minute
%S Second
%t Timstamp (in seconds since 01-Jan-1970)
%. milliseconds
%z timeZone (from Grinvitch)
%D request duration (in milliseconds)
%b average send rate per request (in Bytes per second) this speed is typically below connection speed shown by download manager.
%B average receive rate per request (in Bytes per second) this speed is typically below connection speed shown by download manager.
%U Username
%N service Name
%p service Port
%E Error code
%C Client IP
%c Client port
%R Remote IP
%r Remote port
%i Internal IP used to accept client connection
%e External IP used to establish connection
%Q Requested IP
%q Requested port
%n requested hostname
%I bytes In
%O bytes Out
%h Hops (redirections) count
%T service specific Text
%N1-N2T (N1 and N2 are positive numbers) log only fields from N1 thorugh N2 of service specific text
in the case of ODBC logging logformat specifies SQL statement, for exmample:
logformat "-´+_Linsert into log (l_date, l_user, l_service, l_in, l_out, l_descr) values (´%d-%m-%Y %H:%M:%S´, ´%U´, ´%N´, %I, %O, ´%T´)"

logdump <in_traffic_limit> <out_traffic_limit>
Immediately creates additional log records if given amount of incoming/outgoing traffic is achieved for connection, without waiting for connection to finish. It may be useful to prevent information about long-lasting downloads on server shutdown.

archiver <ext> <commandline>
Archiver to use for log files. <ext> is file extension produced by archiver. Filename will be last argument to archiver, optionally you can use %A as produced archive name and %F as filename.

timeouts <BYTE_SHORT> <BYTE_LONG> <STRING_SHORT> <STRING_LONG> <CONNECTION_SHORT> <CONNECTION_LONG> <DNS> <CHAIN> <CONNECT> <CONNECTBACK>
Sets timeout values, defaults 1, 5, 30, 60, 180, 1800, 15, 60, 15, 5.
BYTE_SHORT short timeout for single byte, is usually used for receiving single byte from stream.
BYTE_LONG long timeout for single byte, is usually used for receiving first byte in frame (for example first byte in socks request).
STRING_SHORT short timeout, for character string within stream (for example to wait between 2 HTTP headers)
STRING_LONG long timeout, for first string in stream (for example to wait for HTTP request).
CONNECTION_SHORT inactivity timeout for short connections (HTTP, POP3, etc).
CONNECTION_LONG inactivity timeout for long connection (SOCKS, portmappers, etc).
DNS timeout for DNS request before requesting next server
CHAIN timeout for reading data from chained connection
default timeouts 1 5 30 60 180 1800 15 60 15 5

radius <NAS_SECRET> <radius_server_1[:port][/local_address_1]> <radius_server_2[:port][/local_address_2]>
Configures RADIUS servers to be used for logging and authentication (log and auth types must be set to radius). port and local address to use with given server may be specified.
Attributes within request: User-Name, Password: (username and password if presented by client), Service Type: Authenticate-Only, NAS-Port-Type: NAS-Port-Virtual, NAS-Port-ID: (proxy service port, e.g. 1080), NAS-IPv6-Address / NAS-IP-Address: (proxy interface accessed by client), NAS-Identifier: (text identifing proxy, e.g. PROXY or SOCKSv5), Framed-IPv6-Address / Framed-IP-Address: (IP address of the client), Called-Station-ID: (requested Hostname, if presents), Login-Service: (type of request, e.g. 1001 - SOCKS CONNECT, 1010 - HTTP GET, 1013 - HTTP CONNECT), Login-TCP-Port: (requested port), Login-IPv6-Host / Login-IP-Host: (requested IP).
Supported reply attributes for authentication: Framed-IP-Address / Framed-IPv6-Address (IP to assign to user), Reply-Message. Use authcache to speedup authentication. RADIUS feature is currently experimental.

nserver <ipaddr>[:port][/tcp]
Nameserver to use for name resolutions. If none specified system routines for name resolution is used. Optional port number may be specified. If optional /tcp is added to IP address, name resolution is performed over TCP.

nscache <cachesize> nscache6 <cachesize>
Cache <cachesize> records for name resolution (nscache for IPv4, nscache6 for IPv6). Cachesize usually should be large enougth (for example 65536).

nsrecord <hostname> <hostaddr>
Adds static record to nscache. nscache must be enabled. If 0.0.0.0 is used as a hostaddr host will never resolve, it can be used to blacklist something or together with dialer command to set up UDL for dialing.

fakeresolve
All names are resolved to 127.0.0.2 address. Usefull if all requests are redirected to parent proxy with http, socks4+, connect+ or socks5+.

dialer <progname>
Execute progname if external name can´t be resolved. Hint: if you use nscache, dialer may not work, because names will be resolved through cache. In this case you can use something like http://dial.right.now/ from browser to set up connection.

internal <ipaddr>
sets ip address of internal interface. This IP address will be used to bind gateways. Alternatively you can use -i option for individual gateways. Since 0.8 version, IPv6 address may be used.

external <ipaddr>
sets ip address of external interface. This IP address will be source address for all connections made by proxy. Alternatively you can use -e option to specify individual address for gateway. Since 0.8 version External or -e can be given twice: once with IPv4 and once with IPv6 address.

maxconn <number>
sets maximum number of simulationeous connections to each services started after this command. Default is 250.

service
(depricated). Indicates 3proxy to behave as Windows 95/98/NT/2000/XP service, no effect for Unix. Not required for 3proxy 0.6 and above. If you upgraded from previous version of 3proxy use --remove and --install to reinstall service.

daemon
Should be specified to close console. Do not use ´daemon´ with ´service´. At least under FreeBSD ´daemon´ should preceed any proxy service and log commands to avoid sockets problem. Always place it in the beginning of the configuration file.

auth <authtype> [...]
Type of user authorization. Currently supported:
none - no authentication or authorization required.
Note: is auth is none any ip based limitation, redirection, etc will not work. This is default authentication type
iponly - authentication by access control list with username ignored.
Appropriate for most cases
useronly - authentication by username without checking for any password with authorization by ACLs. Useful for e.g. SOCKSv4 proxy and icqpr (icqpr set UIN / AOL screen name as a username)
dnsname - authentication by DNS hostnname with authorization by ACLs. DNS hostname is resolved via PTR (reverse) record and validated (resolved name must resolve to same IP address). It´s recommended to use authcache by ip for this authentication. NB: there is no any password check, name may be spoofed.
strong - username/password authentication required. It will work with SOCKSv5, FTP, POP3 and HTTP proxy.
cache - cached authentication, may be used with ´authcache´.
radius - authentication with RADIUS.
Plugins may add additional authentication types.

It´s possible to use few authentication types in the same commands. E.g.
auth iponly strong
In this case ´strong´ authentication will be used only in case resource access can not be performed with ´iponly´ authentication, that is username is required in ACL. It´s usefull to protect access to some resources with password allowing passwordless access to another resources, or to use IP-based authentication for dedicated laptops and request username/password for shared ones.

authcache <cachtype> <cachtime>
Cache authentication information to given amount of time (cachetime) in seconds. Cahtype is one of:
ip - after successful authentication all connections during caching time from same IP are assigned to the same user, username is not requested.
ip,user username is requested and all connections from the same IP are assigned to the same user without actual authentication.
user - same as above, but IP is not checked.
user,password - both username and password are checked against cached ones.
limit - limit user to use only one ip, ´ip´ and ´user´ are required
acl - only use cached auth if user access service with same ACL
ext - cache external IP
Use auth type ´cache´ for cached authentication

allow <userlist> <sourcelist> <targetlist> <targetportlist> <operationlist> <weekdayslist> <timeperiodslist>
deny <userlist> <sourcelist> <targetlist> <targetportlist> <operationlist> <weekdayslist> <timeperiodslist>
Access control entries. All lists are comma-separated, no spaces are allowed. Usernames are case sensitive (if used with authtype nbname username must be in uppercase). Source and target lists may contain IP addresses (W.X.Y.Z), ranges A.B.C.D - W.X.Y.Z (since 0.8) or CIDRs (W.X.Y.Z/L). Since 0.6, targetlist may also contain host names, instead of addresses. It´s possible to use wildmask in the begginning and in the the end of hostname, e.g. *badsite.com or *badcontent*. Hostname is only checked if hostname presents in request. Targetportlist may contain ports (X) or port ranges lists (X-Y). For any field * sign means ANY. If access list is empty it´s assumed to be
allow *
If access list is not empty last item in access list is assumed to be
deny *
You may want explicitly add deny * to the end of access list to prevent HTTP proxy from requesting user´s password. Access lists are checked after user have requested any resource. If you want 3proxy to reject connections from specific addresses immediately without any conditions you should either bind proxy to appropriate interface only or to use ip filters.

Operation is one of:
CONNECT establish outgoing TCP connection
BIND bind TCP port for listening
UDPASSOC make UDP association
ICMPASSOC make ICMP association (for future use)
HTTP_GET HTTP GET request
HTTP_PUT HTTP PUT request
HTTP_POST HTTP POST request
HTTP_HEAD HTTP HEAD request
HTTP_CONNECT HTTP CONNECT request
HTTP_OTHER over HTTP request
HTTP matches any HTTP request except HTTP_CONNECT
HTTPS same as HTTP_CONNECT
FTP_GET FTP get request
FTP_PUT FTP put request
FTP_LIST FTP list request
FTP_DATA FTP data connection. Note: FTP_DATA requires access to dynamic non-ptivileged (1024-65535) ports on remote side.
FTP matches any FTP/FTP Data request
ADMIN access to administration interface

Weeksdays are week days numbers or periods, 0 or 7 means Sunday, 1 is Monday, 1-5 means Monday through Friday.
Timeperiodlists is a list of time periods in HH:MM:SS-HH:MM:SS format. For example, 00:00:00-08:00:00,17:00:00-24:00:00 lists non-working hours.

parent <weight> <type> <ip> <port> <username> <password>
this command must follow "allow" rule. It extends last allow rule to build proxy chain. Proxies may be grouped. Proxy inside the group is selected randomly. If few groups are specified one proxy is randomly picked from each group and chain of proxies is created (that is second proxy connected through first one and so on). Weight is used to group proxies. Weigt is a number between 1 and 1000. Weights are summed and proxies are grouped together untill weight of group is 1000. That is:
allow *
parent 500 socks5 192.168.10.1 1080
parent 500 connect 192.168.10.1 3128
makes 3proxy to randomly choose between 2 proxies for all outgoing connections. These 2 proxies form 1 group (summarized weight is 1000).
allow * * * 80
parent 1000 socks5 192.168.10.1 1080
parent 1000 connect 192.168.20.1 3128
parent 300 socks4 192.168.30.1 1080
parent 700 socks5 192.168.40.1 1080
creates chain of 3 proxies: 192.168.10.1, 192.168.20.1 and third is (192.168.30.1 with probability of 0.3 or 192.168.40.1 with probability of 0.7) for outgoing web connections. Chains are only applied to new connections, pipelined (keep-alive) requests in the same connection use the same chain.

type is one of:
extip does not actully redirect request, it sets external address for this request to <ip>. It can be chained with another parent types. It’s usefaul to set external IP based on ACL or make it random.
tcp simply redirect connection. TCP is always last in chain. This type of proxy is a simple TCP redirection, it does not support parent authentication.
http redirect to HTTP proxy. HTTP is always the last chain. It should only be used with http (proxy) service, if used with different service, it works as tcp redirection.
pop3 redirect to POP3 proxy (only local redirection is supported, can only be used as a first hop in chaining)
ftp redirect to FTP proxy (only local redirection is supported, can only be used as a first hop in chaining)
connect parent is HTTP CONNECT method proxy
connect+ parent is HTTP CONNECT proxy with name resolution (hostname is used instead of IP if available)
socks4 parent is SOCKSv4 proxy
socks4+ parent is SOCKSv4 proxy with name resolution (SOCKSv4a)
socks5 parent is SOCKSv5 proxy
socks5+ parent is SOCKSv5 proxy with name resolution
socks4b parent is SOCKS4b (broken SOCKSv4 implementation with shortened server reply. I never saw this kind ofservers byt they say there are). Normally you should not use this option. Do not mess this option with SOCKSv4a (socks4+).
socks5b parent is SOCKS5b (broken SOCKSv5 implementation with shortened server reply. I think you will never find it useful). Never use this option unless you know exactly you need it.
admin redirect request to local ´admin´ service (with -s parameter).
Use "+" proxy only with "fakeresolve" option

IP and port are ip addres and port of parent proxy server. If IP is zero, ip is taken from original request, only port is changed. If port is zero, it´s taken from original request, only IP is changed. If both IP and port are zero - it´s a special case of local redirection, it works only with socks proxy. In case of local redirection request is redirected to different service, ftp locally redirects to ftppr pop3 locally redirects to pop3p http locally redurects to proxy admin locally redirects to admin -s service.

Main purpose of local redirections is to have requested resource (URL or POP3 username) logged and protocol-specific filters to be applied. In case of local redirection ACLs are revied twice: first, by SOCKS proxy up to ´parent´ command and then with gateway service connection is redirected (HTTP, FTP or POP3) after ´parent´ command. It means, additional ´allow´ command is required for redirected requests, for example:
allow * * * 80
parent 1000 http 0.0.0.0 0
allow * * * 80 HTTP_GET,HTTP_POST
socks
redirects all SOCKS requests with target port 80 to local HTTP proxy, local HTTP proxy parses requests and allows only GET and POST requests.
parent 1000 http 1.2.3.4 0
Changes external address for given connection to 1.2.3.4 (an equivalent to -e1.2.3.4)
Optional username and password are used to authenticate on parent proxy. Username of ´*´ means username must be supplied by user.

nolog <n>
extends last allow or deny command to prevent logging, e.g.
allow * * 192.168.1.1
nolog

weight <n>
extends last allow or deny command to set weight for this request
allow * * 192.168.1.1
weight 100
Weight may be used for different purposes.

force
noforce
If force is specified for service, configuration reload will require all current sessions of this service to be re-authenticated. If ACL is changed or user account is removed, old connections which do not match current are closed. noforce allows to keep previously authenticated connections.

bandlimin <rate> <userlist> <sourcelist> <targetlist> <targetportlist> <operationlist> <weekdayslist> <timeperiodslist>
nobandlimin <userlist> <sourcelist> <targetlist> <targetportlist> <operationlist> <weekdayslist> <timeperiodslist>
bandlimout <rate> <userlist> <sourcelist> <targetlist> <targetportlist> <operationlist> <weekdayslist> <timeperiodslist>
nobandlimout <userlist> <sourcelist> <targetlist> <targetportlist> <operationlist> <weekdayslist> <timeperiodslist>
bandlim sets bandwith limitation filter to <rate> bps (bits per second) If you want to specife bytes per second - multiply your value to 8. bandlim rules act in a same manner as allow/deny rules except one thing: bandwidth limiting is applied to all services, not to some specific service. bandlimin and nobandlimin applies to incoming traffic bandlimout and nobandlimout applies to outgoing traffic If tou want to ratelimit your clients with IPs 192.168.10.16/30 (4 addresses) to 57600 bps you have to specify 4 rules like
bandlimin 57600 * 192.168.10.16
bandlimin 57600 * 192.168.10.17
bandlimin 57600 * 192.168.10.18
bandlimin 57600 * 192.168.10.19
and every of you clients will have 56K channel. If you specify
bandlimin 57600 * 192.168.10.16/30
you will have 56K channel shared between all clients. if you want, for example, to limit all speed ecept access to POP3 you can use
nobandlimin * * * 110
before the rest of bandlim rules.

connlim <rate> <period> <userlist> <sourcelist> <targetlist> <targetportlist> <operationlist> <weekdayslist> <timeperiodslist>
noconnlim <userlist> <sourcelist> <targetlist> <targetportlist> <operationlist> <weekdayslist> <timeperiodslist>
connlim sets connections rate limit per time period for traffic pattern controlled by ACL. Period is in seconds. If period is 0, connlim limits a number of parallel connections.
connlim 100 60 * 127.0.0.1
allows 100 connections per minute for 127.0.0.1.
connlim 20 0 * 127.0.0.1
allows 20 simulationeous connections for 127.0.0.1.
Like with bandlimin, if individual limit is required per client, separate rule mustbe added for every client. Like with nobanlimin, noconnlim adds an exception.

counter <filename> <reporttype> <repotname>
countin <number> <type> <limit> <userlist> <sourcelist> <targetlist> <targetportlist> <operationlist> <weekdayslist> <timeperiodslist>
nocountin <userlist> <sourcelist> <targetlist> <targetportlist> <operationlist> <weekdayslist> <timeperiodslist>
countout <number> <type> <limit> <userlist> <sourcelist> <targetlist> <targetportlist> <operationlist> <weekdayslist> <timeperiodslist>
nocountout <userlist> <sourcelist> <targetlist> <targetportlist> <operationlist> <weekdayslist> <timeperiodslist>
countall <number> <type> <limit> <userlist> <sourcelist> <targetlist> <targetportlist> <operationlist> <weekdayslist> <timeperiodslist>
nocountall <userlist> <sourcelist> <targetlist> <targetportlist> <operationlist> <weekdayslist> <timeperiodslist>

counter, countin, nocountin, countout, noucountout, countall, nocountall commands are used to set traffic limit in MB for period of time (day, week or month). Filename is a path to a special file where traffic information is permanently stored. number is sequential number of record in this file. If number is 0 this counter is not preserved in counter file (that is if proxy restarted all counters with 0 are flushed) overwise it should be unique sequential number which points to position of the couter within the file. Type specifies a type of counter. Type is one of:
H - counter is resetted hourly
D - counter is resetted daily
W - counter is resetted weekly
M - counter is resetted monthely
reporttype/repotname may be used to generate traffic reports. Reporttype is one of D,W,M,H(hourly) and repotname specifies filename template for reports. Report is text file with counter values in format:
<COUNTERNUMBER> <TRAF>
The rest of parameters is identical to bandlim/nobandlim.

users username[:pwtype:password] ...
pwtype is one of:
none (empty) - use system authentication
CL - password is cleartext
CR - password is crypt-style password
NT - password is NT password (in hex)
example:
users test1:CL:password1 "test2:CR:$1$lFDGlder$pLRb4cU2D7GAT58YQvY49."
users test3:NT:BD7DFBF29A93F93C63CB84790DA00E63

Note: double quotes are requiered because password contains $ sign.

flush
empty active access list. Access list must be flushed avery time you creating new access list for new service. For example:
allow *
pop3p
flush
allow * 192.168.1.0/24
socks
sets different ACLs for pop3p and socks

system <command>
execute system command

pidfile <filename>
write pid of current process to file. It can be used to manipulate 3proxy with signals under Unix. Currently next signals are available:

monitor <filename>
If file monitored changes in modification time or size, 3proxy reloads configuration within one minute. Any number of files may be monitored.

setuid <uid>
calls setuid(uid), uid can be numeric or since 0.9 username. Unix only. Warning: under some Linux kernels setuid() works for current thread only. It makes it impossible to suid for all threads.

setgid <gid>
calls setgid(gid), gid can be numeric or since 0.9 groupname. Unix only.

chroot <path> [<uid>] [<gid>]
calls chroot(path) and sets gid/uid. Unix only. uid/gid supported since 0.9, can be numeric or username/groupname

stacksize <value_to_add_to_default_stack_size>
Change default size for threads stack. May be required in some situation, e.g. with non-default plugins, on on some platforms (some FreeBSD version may require adjusting stack size due to invalid defined value in system header files, this value is also oftent reqruied to be changed for ODBC and PAM support on Linux. If you experience 3proxy crash on request processing, try to set some positive value. You may start with stacksize 65536 and then find the minimal value for service to work. If you experience memory shortage, you can try to experiment with negative values.

Centos7下载安装3proxy
https://juejin.cn/post/7091955944631992350

# #DNS服务器
# nserver 202.141.162.123
# nserver 202.141.176.93
nserver 127.0.0.1

#DNS缓存时间
nscache 65536

# 将DNS解析交给上级代理完成
# fakeresolve
# dnspr参数表示使用dns
# dnspr

#超时
timeouts 1 5 30 60 180 1800 15 60

#对linux及非nt系统应替换为daemon，就可以保证在后台运行。
daemon

# 日志相关配置
## 日志保存目录
log /var/log/3proxy/3proxy.log D
## 日志格式
#logformat "- +_L%N.%p %E %U %C:%c %R:%r %O %I %h %T"
logformat "L%y-%m-%d %H:%M:%S %U %N %C:%c %R:%r %I %O %T"
# 日志保存时长
rotate 30

# 定义了一个用户，用户名：ziyou，密码：pass
## CL表示使用了明文密码。
users zhouwen:CL:zhouwen123 qiaofei:CL:qiaofei123

# 认证方式:使用账号密码认证
auth strong

# 允许ziyou这个用户访问
## 注意添加完用户还要配置允许用户
# allow zhouwen
allow zhouwen,qiaofei

# 父代理 轮询比例(1000最大) 协议 ip 端口
# parent 1000 http 43.132.255.122 9999
parent 1000 socks5 127.0.0.1 1080
# 监听端口
# -a表示匿名代理,-p代表监听的端口
## 匿名代理-对方知道你使用了代理,但不知道你的真实ip
## http协议端口3128
proxy -a -p10808

## socks4协议端口1080

#socks -p1080
# socks -a -p10808

3proxy容器化部署

https://hub.docker.com/r/3proxy/3proxy
https://github.com/my6889/3proxy

设置用户名密码和服务端口
修改3proxy.cfg中的用户名、密码、服务端口

下载项目
git clone https://github.com/my6889/3proxy.git

docker-compose
docker-compose up -d

Kubernetes
创建Configmap
kubectl apply -f 3proxy-configmap.yml

如果用Daemonset部署
kubectl apply -f 3proxy-daemonset.yml

如果用Deployment部署
kubectl apply -f 3proxy-deployment.yml

客户端代理使用

windows

有钱任性，服务端可以购买使用CCProxy

浏览器代理
Proxifier

Linux

export http_proxy=””
proxychains(proxychains-ng)
redsocks + iptables

轻量级批量HTTP请求工具——WebBatchRequest

Sun, 24 May 2026 01:51:15 +0800

工具介绍

WebBatchRequest是一款轻量级批量HTTP请求工具，适用于安全测试中的存活探测、Title获取、Banner识别和漏洞批量验证。

安装使用

下载地址：

https://github.com/ScriptKid-Beta/WebBatchRequest/releases

下载解压后双击 jar 文件即可运行

支持系统：Windows / Linux / Mac（跨平台）
运行环境：基于 Java 8+ 开发，无额外依赖

功能特点

批量存活探测

快速检测大量目标地址存活状态，返回HTTP状态码和响应时间。

多线程并发：可自定义线程数，提高探测效率
实时进度显示：进度条实时更新，一目了然
状态筛选：支持按状态码筛选存活站点

Title批量获取

一键获取所有存活站点的网页标题，支持中文编码识别。

Banner识别

获取HTTP响应头信息，包括Server版本、X-Powered-By、响应状态码等。

HTTP请求自定义

配置项	说明
请求方法	GET、POST、HEAD
HTTP代理	支持配置代理服务器
自定义Header	Host头碰撞、绕过CDN
自定义Cookies	需登录态的场景
自定义UA	模拟不同浏览器

数据导入导出

导入：TXT文本文件（每行一个URL）
导出：CSV格式，支持结果排序和状态筛选

使用技巧

线程数调优：内网测试可用20-50线程；公网测试建议5-10线程避免触发封禁
Host头碰撞：配置自定义Host头绕过CDN，获取真实服务器响应
代理配置：使用HTTP/SOCKS代理分散请求来源，降低封禁概率
结果筛选：导出后按状态码或Title关键词筛选高价值目标

想了解更多可以访问：https://github.com/ScriptKid-Beta/WebBatchRequest

HTML/PHP 在线访问链接生成器

Sun, 24 May 2026 01:46:55 +0800

一款基于原生 PHP 开发的在线代码托管+随机链接生成工具，无需数据库，支持输入 HTML / PHP 代码，自动生成6位随机字符访问链接，保存至服务器独立目录，可直接浏览器在线访问，适合临时网页、接口演示、代码临时托管、中转页面快速生成使用。

功能特性

✅ 支持两种代码类型： HTML / PHP 自由切换

✅ 自动生成 6位小写随机字母唯一访问链接

✅ 采用服务器绝对路径存储，彻底避免相对路径错乱

✅ 程序自动创建存储目录，并自动设置 777 读写权限

✅ 访问路由严格正则校验，仅允许6位小写字母路由

✅ 优先解析并执行 PHP 文件，不存在则读取 HTML 文件

✅ 文件不存在友好提示，展示实际服务器检测路径

✅ 生成链接后支持一键复制、新标签页直接访问

✅ 前端简约响应式 UI，适配手机、电脑端

✅ 代码编辑框采用编程等宽字体，支持手动拉伸高度

✅ 自带禁止浏览器缓存配置，修改代码实时生效

✅ 一键清空编辑内容，操作简单易用

文件结构

plaintext

├── index.php # 程序主文件（后端逻辑 + 前端页面合一）

└── code_files/ # 自动生成的代码文件存储目录

├── xxxxxx.html

└── xxxxxx.php

环境要求

PHP 7.0 及以上版本

服务器目录支持 777 写入权限

兼容宝塔 / Apache / Nginx 运行环境

无需 MySQL，纯文件模式运行

配置说明

打开文件顶部，修改三处配置即可部署：

php

$domain = 'http://你的域名/'; // 填写你的网站域名

$storageDir = '/www/wwwroot/xxx/code_files/'; // 服务器绝对存储路径

$linkLength = 6; // 随机链接字符长度

安装部署

1. 将代码保存为 index.php 上传至站点目录

2. 修改顶部域名和服务器绝对存储路径

3. 给站点目录设置读写权限

4. 直接访问域名即可进入工具主页

使用教程

1. 选择代码类型：HTML 或 PHP

2. 在文本框粘贴或编写完整代码

3. 点击「生成链接」自动保存文件并生成访问地址

4. 点击「复制链接」可直接分享使用

5. 支持点击链接新标签页在线预览访问

6. 可随时点击「清空内容」重新编写生成

HTML/PHP 在线访问链接生成器下载地址：https://pan.baidu.com/s/1yxf7tV08ofJzPlThDCw97Q?pwd=6666

? 收藏！不写代码改 HTML 页面的神器

Sun, 24 May 2026 01:43:34 +0800

? 收藏！不写代码改 HTML 页面的神器

经常需要改 AI生成的HTML 报告/简历/页面，但不想再费力“指挥”？
这个 Chrome 插件让你像用 PPT 一样编辑 HTML ?

✅ 拖拽移动 — 选中就能拖
✅ 文字编辑 — 双击直接改
✅ 表格编辑 — 加行加列合并单元格
✅ 图片粘贴 — 直接 Ctrl+V
✅ 对齐参考线 — 拖的时候自动吸附
✅ 画板模式 — 画矩形、箭头、文本框
✅ 导出PDF — 智能分页，完美排版

纯原生 JavaScript，不依赖任何框架开源免费，MIT 协议随便用

如果 VPS 服务器不能直连了，要怎么办？

Sat, 23 May 2026 01:33:58 +0800

有一台越南的 NAT 服务器，买来就配置了端口转发：

之前一直是可以直连的，但这两天发现，连不上了。

简单的测试一下连通性：

从本地 Windows 去 ping，的确已经不通了。

虽然不记得之前通不通，但现在的情况，大概率是没办法直连了。

于是自然要想办法，本文就分享我的两个方案给大家。

如果大家以后遇到了同样的问题，就知道该怎样去连了。

方案1：安装 Tailscale

这是最推荐的方法

Tailscale 简明安装/登录/使用教程

它本质上是给所有设备都拉进虚拟局域网。

即使公网不能直连，服务器之间仍然能通过局域网 IP 互联。

SSH、RDP 都能正常进行。

安装完成后，可以直接使用 Tailscale 分配的内网 IP 登录：

ssh root@100.x.x.x

实际体验和直连几乎没差别。

最大的优点是：不依赖公网 IP 。

即使 NAT、动态 IP 也能正常使用。

方案2：通过能直连的服务器去中转

如果你还有一台能正常访问的服务器。

那么也可以让它作为跳板机。

例如，先 SSH 到能直连的服务器：

ssh root@跳板机

然后再从跳板机 SSH 到越南 NAT 服务器：

ssh -p 65001 root@160.191.245.48

这里的 65001 就是 NAT 机器做端口转发时映射出来的公网端口。

这种方案的本质是：

本机 → 跳板机 → NAT服务器

注：我已经向商家反馈了，希望之后能给换一个正常的 IP，不然虽然我能访问自己的机器，但如果搭一个小站，大家仍然访问不了。

VMware vsan 磁盘故障，进行更换

Fri, 22 May 2026 17:17:43 +0800

1、登录Vcenter

查看硬盘故障情况

2、开启故障硬盘的所在主机的SSH

SSH登录主机

3、查看存储信息

esxcli vsan storage list

4、删除故障硬盘

esxcli vsan storage remove -u 5208abb3-af87-45c8-f985-54ac65161034

可能不支持 uuid, 可以尝试使用 naa的 devices name.

esxcli vsan storage remove -u naa.5002538a983e8e10

简单手搓一个HTML版本合同审核工具

Fri, 22 May 2026 17:12:50 +0800

现在LLM已经越发完善，遇事不决先问AI已成为很多人的潜意识。

比如说，有时候别人送个合同过来，是不是会用AI检查一下存在什么问题？又或者审核一些文章的时候，会不会直接让AI看哪些地方需要改？

当然，以上功能在线LLM平台就能够很好的实现。但假如每天都要多次做的话，终归弄起来不太便利。这个时候就可以用AI做一个HTML小工具来提高效率。

想起做这个，是因为之前听一个讲座，发现HTML也可以方便的嵌入DOCX进行预览，当时就想，使用这个功能的话不就能很好地去对比审核材料了吗？

于是乎，就做了一个合同审核网页工具，功能也很简单：

上传合同 → AI自动审核 → 红色标注问题 → 可以提问 → 下载结果

具体来说：

上传DOCX合同文件（点击或拖拽都行）
AI会分析合同，把有问题的条款用红色标出来（调用deepseek的API进行分析）
每个问题下面都附上备注：什么问题？建议怎么改？
右侧显示合同原文，方便对照

有个问答框，可以对合同内容提问

最后可以下载标注后的Word文档

这个工具的项目结构如下，我直接在Deepseek官网手搓下来的，嫌麻烦的话用opencode或者hermes等Agents提要求生成应该会更方便。

项目文件夹/├── index.html├── css/│   └── style.css（HTML样式，AI生成即可）├── js/│   ├── docx.umd.min.js（docx文件处理插件）│   ├── word-generator.js（文本生成器代码，AI生成即可）│   └── mammoth.browser.min.js（浏览器预览docx插件）

其实重点是docx.umd.min.js和mammoth.browser.min.js，建议把这两个下到本地，让网页直接调用，避免由于网络问题导致工具失灵。

docx.umd.min.js

访问：https://cdn.jsdelivr.net/npm/docx@8.5.0/build/index.umd.min.js
右键另存为 → js/docx.umd.min.js

mammoth.browser.min.js

访问：https://cdn.jsdelivr.net/npm/mammoth@1.4.2/mammoth.browser.min.js
右键另存为 → js/mammoth.browser.min.js

Honker：把队列、流、Pub/Sub 和定时调度，装进一个 SQLite 文件

Fri, 22 May 2026 17:11:32 +0800

如果你的应用已经把 SQLite 当作主存储，那么任务队列是否也应该和数据“共存”在同一个文件里？

honker 为 SQLite 增加了类似 PostgreSQL 的 NOTIFY/LISTEN 语义，同时提供持久化的 pub/sub、任务队列和事件流功能，而且不需要客户端轮询，也不需要独立的守护进程或消息中间件（broker）。在 M 系列芯片的笔记本上，跨进程唤醒延迟 p50 约为 0.7 毫秒。

在最基础的形式下，它只是一个普通的 SQLite 可加载扩展，因此任何支持 SELECT load_extension('honker_ext') 的语言，都可以在同一个数据库文件上使用相同的队列、流和通知机制。Python、Node、Rust、Go、Ruby、Bun 和 Elixir 的绑定共享同一种磁盘数据格式。

SQLite 已经在真实生产环境中承担关键业务，例如 Bluesky 的 PDS、Fly 的 LiteFS、Turso。一旦真实业务流进入基于 SQLite 的应用，就必然需要队列系统。传统方案通常是“加 Redis + Celery”。这种方式是可行的，但会引入第二套数据存储系统及其备份方案，还会带来业务表与队列之间的双写问题，以及运行消息中间件的运维成本。

honker 的思路是：如果 SQLite 是主存储，那么队列也应该存在于同一个文件中。

这意味着 INSERT INTO orders 和 queue.enqueue(...) 可以在同一个事务中提交；如果事务回滚，两者都会一起撤销。队列本质上只是由表和部分索引组成的数据行。

一句话理解：

Honker = SQLite + 内建队列系统（无外部依赖）

一个例子

在一次原子事务中，同时完成业务写入与任务入队，然后进行消费。所有操作都在同一个 .db 文件中完成，采用统一的磁盘格式，并可在七种语言中使用。

import honker

db = honker.open("app.db")
q = db.queue("emails")

# 在同一个事务中：业务写入 + 入队
with db.transaction() as tx:
    tx.execute("INSERT INTO orders (id, total) VALUES (?, ?)", [42, 99])
    q.enqueue({"to": "wujm_xa@qq.com", "order_id": 42}, tx=tx)

# worker 在数据库任何提交发生时被唤醒，无需轮询
async for job in q.claim("worker-1"):
    await send_email(job.payload)
    job.ack()

或者使用类似 Huey 的装饰器方式：

@q.task(retries=3, timeout_s=30)
def send_email(to, subject):
    ...
    return {"sent_at": time.time()}

r = send_email("wujm_xa@qq.com", "Hi")   # 入队，返回 TaskResult
print(r.get(timeout=10))                    # 阻塞直到 worker 执行完成

工作原理

honker 每隔 1 毫秒轮询一次 SQLite 的 PRAGMA data_version。这是一个单调递增计数器，SQLite 会在每次来自任意连接、任意日志模式或任意进程的提交发生时对其加一——读取它大约只需要 3 微秒，却可以作为一个非常精确的“唤醒信号”。

后台线程会把这个 tick 分发给所有订阅者，然后每个订阅者执行：

SELECT ... WHERE id > last_seen

并返回新的数据行。对于每个数据库而言，无论订阅者数量多少，都只需要一个轮询线程。

在空闲状态下的成本是：每个数据库每毫秒执行一次轻量级 SELECT。但不会带来 page-cache 压力，不会造成写锁竞争，也不依赖操作系统的文件监听机制。由于“唤醒信号”是一次共享轮询，而不是为每个监听器单独执行查询，所以监听器数量可以自由扩展。

队列、数据流以及 pub/sub 原语，本质上都是扩展所管理表中的 INSERT 操作。

在你的业务事务中调用：

queue.enqueue(payload, tx=tx)

意味着这个 job 行与前面的：

INSERT INTO orders

处于同一个 ACID 事务中。如果事务回滚，job 也会一并被撤销。

复活十八年前的古董USB电视棒

Fri, 22 May 2026 16:36:07 +0800

本期话题似乎和广播没有太大关系，但事情的开端确实和广播有关。写这篇文章，是因为我找到了一种复活老古董USB设备的方法，同时也踩了不少坑。谈不上什么“血和泪”，但至少浪费了我不少时间。

最近两期文章都在聊反射接收FM广播，于是有网友留言，询问频率更高的电视信号是否也能被有效反射。

其实这个问题我也想过，只是一直没有真正动手。原因很简单：手上既没有便携式DTMB电视机，也没有其他合适的接收设备。

直到近日整理杂物时，我翻出了一块十八年前的神州数码USB电视棒，型号是DCDTV330。当时使用DMB-TH描述国标地面数字电视，DTMB一词还没出现。

这个电视棒当年的官方驱动只有Windows XP和Vista版本，而且还都是32位，后来也再没有更新过。

从2008年到现在，整整十八年过去了。虽然Windows这些年更新节奏不算快，但也已经迭代了好几个大版本。没有驱动的硬件，基本和电子垃圾没什么区别。厂家早已把电视棒从官网删除，自身也转型成了一家AI方案供应商。

我看着手上的电视棒，陷入了短暂的沉思。为了它专门装一台XP显然不现实，更何况XP这种古老系统，也未必能驱动现在的新硬件。

忽然，我灵机一动：既然实体机不行，那虚拟机呢？如果在Windows 11里安装一台XP虚拟机，是不是就能继续使用现代系统，同时又让XP去驱动这根古董电视棒？

想到就做。Windows 11本身集成了Hyper-V，于是我直接开了一台虚拟机安装Windows XP。

幸好以前备份过XP的Ghost镜像。不得不说，Ghost这东西虽然古老，但确实高效，前后不到十分钟，一个XP系统就装好了。

结果正当我兴冲冲准备安装电视棒驱动时，第一个大坑来了。

Hyper-V和主机之间的隔离程度很高，几乎没有直接访问USB设备的机制。除了键盘鼠标之类的基础设备，它根本不允许虚拟机直接控制USB硬件。

好吧，此路不通彼路通。我记得VirtualBox支持USB穿透，于是马上下载VirtualBox，结果又踩中了第二个坑。

在VirtualBox里安装XP时，可模拟的最新芯片组只有ICH9，硬盘接口也只能选IDE。之前在Hyper-V里不到十分钟就能完成的安装，到了VirtualBox里居然慢了十倍不止。

这也和两者架构有关。简单来说，VirtualBox属于Type 2虚拟机，它需要运行在操作系统之上；而Hyper-V属于Type 1虚拟机，虚拟化层更接近硬件，因此效率更高。

更令人哭笑不得的是，XP安装完成后，显卡等设备居然显示成带黄色叹号的“其他设备”。

这就很离谱了。虚拟机里的硬件本来就是“虚拟出来”的，你想让它模拟成什么，它就应该是什么。结果现在居然虚拟出一个系统根本不认识、还没有驱动的设备。难不成我还得给“虚拟硬件”再去找驱动？我真是服了！

折腾一番后，我最终放弃VirtualBox，转而下载了VMware Workstation Pro。

事实证明，VMware确实有它厉害的地方，既有Hyper-V的效率，又具备VirtualBox那种USB设备穿透能力。

整个XP系统几分钟就安装完成，没有任何异常。插入U盘后，虚拟机能正确识别，也可以在主机和虚拟机之间自由切换控制权。

再插入USB电视棒，虽然Windows 11主机本身没有驱动、完全不认识这设备，但VMware依然能够像处理U盘一样，把设备控制权交给XP虚拟机。

随后在XP里正确安装驱动和播放软件，一切终于恢复正常。十八年前的古董，居然真的复活了。

接下来，就等找机会外出测试电视信号反射接收效果了。

总结：

安装虚拟机这件事，可以很简单，也可以很复杂。理论上，虚拟机软件完全知道宿主机有什么硬件，也知道不同版本的操作系统适合什么配置。让普通用户来一键自动生成一套“最佳兼容方案”其实并不难。但现实情况却是，Hyper-V和VirtualBox都出现了带“黄色叹号”的异常设备，让人颇为费解。只有VMware，最终交出了一份近乎满分的答卷。

虽然整个过程踩了好些大坑和小坑，但是通过安装虚拟机复活USB老古董的思路完全行得通。

HQY

某知名国产备份软件公司疑似爆雷：附全球备份软件真实评测！

3proxy安装配置实践

3proxy安装配置实践

前言

3proxy简介

3proxy安装配置

Linux

Windows

3proxy配置文件解释

3proxy.cfg

3proxy容器化部署

客户端代理使用

windows

Linux

轻量级批量HTTP请求工具——WebBatchRequest

批量存活探测

Title批量获取

Banner识别

HTTP请求自定义

HTML/PHP 在线访问链接生成器

? 收藏！不写代码改 HTML 页面的神器

? 收藏！不写代码改 HTML 页面的神器

如果 VPS 服务器不能直连了，要怎么办？

VMware vsan 磁盘故障，进行更换

简单手搓一个HTML版本合同审核工具

Honker：把队列、流、Pub/Sub 和定时调度，装进一个 SQLite 文件

一句话理解：

一个例子

工作原理

相关工作

引用链接

复活十八年前的古董USB电视棒