Linux下redsocks流量转发结合iptables流量透传出现 socket: Too many open files 和 connect: Bad file descriptor
  zAXjsPdxtYy3 2023年11月02日 45 0


Linux下redsocks流量转发结合iptables流量透传出现 socket: Too many open files 和 connect: Bad file descriptor。

Oct 8 18:59:34 localhost redsocks[26193]: connect: Bad file descriptor
Oct 8 18:59:34 localhost redsocks[26193]: [192.168.10.10:53318->124.225.191.19:443]: red_connect_relay: Bad file descriptor
Oct 8 18:59:34 localhost redsocks[26193]: [192.168.10.10:53318->124.225.191.19:443]: dropping client (R/W), relay (R/W), idle 0.000234s
Oct 8 18:59:34 localhost redsocks[26193]: [192.168.10.10:53319->124.225.191.19:8000]: accepted
Oct 8 18:59:34 localhost redsocks[26193]: socket: Too many open files
Oct 8 18:59:35 localhost redsocks[26193]: connect: Bad file descriptor
Oct 8 18:59:35 localhost redsocks[26193]: [192.168.10.10:53319->124.225.191.19:8000]: red_connect_relay: Bad file descriptor
Oct 8 18:59:35 localhost redsocks[26193]: [192.168.10.10:53319->124.225.191.19:8000]: dropping client (R/W), relay (R/W), idle 0.000234s
Oct 8 18:59:35 localhost redsocks[26193]: [192.168.10.10:53320->175.6.44.21:443]: accepted
Oct 8 18:59:35 localhost redsocks[26193]: socket: Too many open files
Oct 8 18:59:35 localhost redsocks[26193]: connect: Bad file descriptor
Oct 8 18:59:35 localhost redsocks[26193]: [192.168.10.10:53320->175.6.44.21:443]: red_connect_relay: Bad file descriptor
Oct 8 18:59:35 localhost redsocks[26193]: [192.168.10.10:53320->175.6.44.21:443]: dropping client (R/W), relay (R/W), idle 0.000237s
Oct 8 18:59:35 localhost redsocks[26193]: [192.168.10.10:53322->175.6.44.21:8000]: accepted
Oct 8 18:59:35 localhost redsocks[26193]: socket: Too many open files
Oct 8 18:59:35 localhost redsocks[26193]: connect: Bad file descriptor
Oct 8 18:59:35 localhost redsocks[26193]: [192.168.10.10:53322->175.6.44.21:8000]: red_connect_relay: Bad file descriptor
Oct 8 18:59:35 localhost redsocks[26193]: [192.168.10.10:53322->175.6.44.21:8000]: dropping client (R/W), relay (R/W), idle 0.000236s
Oct 8 18:59:35 localhost redsocks[26193]: [192.168.10.10:53323->175.6.44.23:443]: accepted
Oct 8 18:59:35 localhost redsocks[26193]: socket: Too many open files
Oct 8 18:59:35 localhost redsocks[26193]: connect: Bad file descriptor
Oct 8 18:59:35 localhost redsocks[26193]: [192.168.10.10:53323->175.6.44.23:443]: red_connect_relay: Bad file descriptor
Oct 8 18:59:35 localhost redsocks[26193]: [192.168.10.10:53323->175.6.44.23:443]: dropping client (R/W), relay (R/W), idle 0.000273s
Oct 8 18:59:35 localhost redsocks[26193]: [192.168.10.10:53325->175.6.44.23:8000]: accepted
Oct 8 18:59:35 localhost redsocks[26193]: socket: Too many open files
Oct 8 18:59:35 localhost redsocks[26193]: connect: Bad file descriptor
Oct 8 18:59:35 localhost redsocks[26193]: [192.168.10.10:53325->175.6.44.23:8000]: red_connect_relay: Bad file descriptor
Oct 8 18:59:35 localhost redsocks[26193]: [192.168.10.10:53325->175.6.44.23:8000]: dropping client (R/W), relay (R/W), idle 0.000360s
Oct 8 18:59:35 localhost redsocks[26193]: [192.168.10.10:53326->124.225.191.18:443]: accepted
Oct 8 18:59:35 localhost redsocks[26193]: socket: Too many open files
Oct 8 18:59:35 localhost redsocks[26193]: connect: Bad file descriptor
Oct 8 18:59:35 localhost redsocks[26193]: [192.168.10.10:53326->124.225.191.18:443]: red_connect_relay: Bad file descriptor
Oct 8 18:59:35 localhost redsocks[26193]: [192.168.10.10:53326->124.225.191.18:443]: dropping client (R/W), relay (R/W), idle 0.000218s
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:38099->192.168.10.1:8888]: got 1st packet from client
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:38099->192.168.10.1:8888]: socket: Too many open files
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:38099->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.10:58326->192.168.10.1:8888]: got 1st packet from client
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.10:58326->192.168.10.1:8888]: socket: Too many open files
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.10:58326->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.10:58326->192.168.10.1:8888]: got 1st packet from client
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.10:58326->192.168.10.1:8888]: socket: Too many open files
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.10:58326->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.10:58327->192.168.10.1:8888]: got 1st packet from client
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.10:58327->192.168.10.1:8888]: socket: Too many open files
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.10:58327->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.10:60455->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.10:60455->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:49924->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:49924->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:39003->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:39003->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:33201->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:33201->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:60964->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:60964->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:56258->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:56258->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:43991->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:43991->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:46423->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:46423->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:43075->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:43075->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:37960->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:37960->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:55090->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:55090->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:52716->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:52716->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:59136->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:59136->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:43787->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:43787->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:48279->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:48279->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:59988->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:59988->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:41381->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:41381->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:56439->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:56439->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:39527->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:39527->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:38125->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:38125->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:39793->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:39793->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:33729->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:33729->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:56530->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:56530->192.168.10.1:8888]: Dropping…
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:48387->192.168.10.1:8888]: Client timeout. First: 1696762745, last_client: 1696762746, last_relay: 0.
Oct 8 18:59:36 localhost redsocks[26193]: [192.168.10.1:48387->192.168.10.1:8888]: Dropping…

解决方法：

修改 redsocks.conf 配置文件中的 rlimit_nofile 和 redsocks_conn_max 的值，改大一些就可以，示例配置文件如下：

配置文件（/etc/redsocks.conf）：

base {
	// debug: connection progress & client list on SIGUSR1
	log_debug = off;

	// info: start and end of client session
	log_info = on;

	/* possible `log' values are:
	 *   stderr
	 *   "file:/path/to/file"
	 *   syslog:FACILITY  facility is any of "daemon", "local0"..."local7"
	 */
	log = "syslog:daemon";

	// detach from console
	daemon = on;

	/* Change uid, gid and root directory, these options require root
	 * privilegies on startup.
	 * Note, your chroot may requre /etc/localtime if you write log to syslog.
	 * Log is opened before chroot & uid changing.
	 */
	user = redsocks;
	group = redsocks;
	// chroot = "/var/chroot";

	/* possible `redirector' values are:
	 *   iptables   - for Linux
	 *   ipf        - for FreeBSD
	 *   pf         - for OpenBSD
	 *   generic    - some generic redirector that MAY work
	 */
	redirector = iptables;
	redsocks_conn_max = 10000;
	rlimit_nofile = 10240;
}

redsocks {
	/* `local_ip' defaults to 127.0.0.1 for security reasons,
	 * use 0.0.0.0 if you want to listen on every interface.
	 * `local_*' are used as port to redirect to.
	 */
	local_ip = 0.0.0.0;
	local_port = 12345;

	// `ip' and `port' are IP and tcp-port of proxy-server
	// You can also use hostname instead of IP, only one (random)
	// address of multihomed host will be used.
	ip = 192.168.21.1;
	port = 1080;


	// known types: socks4, socks5, http-connect, http-relay
	type = socks5;

	// login = "foobar";
	// password = "baz";
}

有时候连接会达到限制，而被强制关闭，以下是官方的说明文档：

base {
	// debug: connection progress
	log_debug = off;

	// info: start and end of client session
	log_info = on;

	/* possible `log' values are:
	 *   stderr
	 *   "file:/path/to/file"
	 *   syslog:FACILITY  facility is any of "daemon", "local0"..."local7"
	 */
	log = stderr;
	// log = "file:/path/to/file";
	// log = "syslog:local7";

	// detach from console
	daemon = off;

	/* Change uid, gid and root directory, these options require root
	 * privilegies on startup.
	 * Note, your chroot may requre /etc/localtime if you write log to syslog.
	 * Log is opened before chroot & uid changing.
	 * Debian, Ubuntu and some other distributions use `nogroup` instead of
	 * `nobody`, so change it according to your system if you want redsocks
	 * to drop root privileges.
	 */
	// user = nobody;
	// group = nobody;
	// chroot = "/var/chroot";

	/* possible `redirector' values are:
	 *   iptables   - for Linux
	 *   ipf        - for FreeBSD
	 *   pf         - for OpenBSD
	 *   generic    - some generic redirector that MAY work
	 */
	redirector = iptables;

	/* Override per-socket values for TCP_KEEPIDLE, TCP_KEEPCNT,
	 * and TCP_KEEPINTVL. see man 7 tcp for details.
	 * `redsocks' relies on SO_KEEPALIVE option heavily. */
	//tcp_keepalive_time = 0;
	//tcp_keepalive_probes = 0;
	//tcp_keepalive_intvl = 0;

	// Every `redsocks` connection needs two file descriptors for sockets.
	// If `splice` is enabled, it also needs four file descriptors for
	// pipes.  `redudp` is not accounted at the moment.  When max number of
	// connection is reached, redsocks tries to close idle connections. If
	// there are no idle connections, it stops accept()'ing new
	// connections, although kernel continues to fill listenq.

	// Set maximum number of open file descriptors (also known as `ulimit -n`).
	//  0 -- do not modify startup limit (default)
	// rlimit_nofile = 0;

	// Set maximum number of served connections. Default is to deduce safe
	// limit from `splice` setting and RLIMIT_NOFILE.
	// redsocks_conn_max = 0;

	// Close connections idle for N seconds when/if connection count
	// limit is hit.
	//  0 -- do not close idle connections
	//  7440 -- 2 hours 4 minutes, see RFC 5382 (default)
	// connpres_idle_timeout = 7440;

	// `max_accept_backoff` is a delay in milliseconds to retry `accept()`
	// after failure (e.g. due to lack of file descriptors). It's just a
	// safety net for misconfigured `redsocks_conn_max`, you should tune
	// redsocks_conn_max if accept backoff happens.
	// max_accept_backoff = 60000;
}

redsocks {
	/* `local_ip' defaults to 127.0.0.1 for security reasons,
	 * use 0.0.0.0 if you want to listen on every interface.
	 * `local_*' are used as port to redirect to.
	 */
	local_ip = 127.0.0.1;
	local_port = 12345;

	// listen() queue length. Default value is SOMAXCONN and it should be
	// good enough for most of us.
	// listenq = 128; // SOMAXCONN equals 128 on my Linux box.

	// Enable or disable faster data pump based on splice(2) syscall.
	// Default value depends on your kernel version, true for 2.6.27.13+
	// splice = false;

	// `ip' and `port' are IP and tcp-port of proxy-server
	// You can also use hostname instead of IP, only one (random)
	// address of multihomed host will be used.
	ip = example.org;
	port = 1080;

	// known types: socks4, socks5, http-connect, http-relay
	type = socks5;

	// login = "foobar";
	// password = "baz";

	// known ways to disclose client IP to the proxy:
	//  false -- disclose nothing
	// http-connect supports:
	//  X-Forwarded-For  -- X-Forwarded-For: IP
	//  Forwarded_ip     -- Forwarded: for=IP # see RFC7239
	//  Forwarded_ipport -- Forwarded: for="IP:port" # see RFC7239
	// disclose_src = false;

	// various ways to handle proxy failure
	//  close -- just close connection (default)
	//  forward_http_err -- forward HTTP error page from proxy as-is
	// on_proxy_fail = close;
}

redudp {
	// `local_ip' should not be 0.0.0.0 as it's also used for outgoing
	// packets that are sent as replies - and it should be fixed
	// if we want NAT to work properly.
	local_ip = 127.0.0.1;
	local_port = 10053;

	// `ip' and `port' of socks5 proxy server.
	ip = 10.0.0.1;
	port = 1080;
	login = username;
	password = pazzw0rd;

	// redsocks knows about two options while redirecting UDP packets at
	// linux: TPROXY and REDIRECT.  TPROXY requires more complex routing
	// configuration and fresh kernel (>= 2.6.37 according to squid
	// developers[1]) but has hack-free way to get original destination
	// address, REDIRECT is easier to configure, but requires `dest_ip` and
	// `dest_port` to be set, limiting packet redirection to single
	// destination.
	// [1] http://wiki.squid-cache.org/Features/Tproxy4
	dest_ip = 8.8.8.8;
	dest_port = 53;

	udp_timeout = 30;
	udp_timeout_stream = 180;
}

dnstc {
	// fake and really dumb DNS server that returns "truncated answer" to
	// every query via UDP, RFC-compliant resolver should repeat same query
	// via TCP in this case.
	local_ip = 127.0.0.1;
	local_port = 5300;
}

// you can add more `redsocks' and `redudp' sections if you need.


【版权声明】本文内容来自摩杜云社区用户原创、第三方投稿、转载，内容版权归原作者所有。本网站的目的在于传递更多信息，不拥有版权，亦不承担相应法律责任。如果您发现本社区中有涉嫌抄袭的内容，欢迎发送邮件进行举报，并提供相关证据，一经查实，本社区将立刻删除涉嫌侵权内容，举报邮箱： cloudbbs@moduyun.com
  1. 分享：
最后一次编辑于 2023年11月08日 0

暂无评论

推荐阅读
  HRODlxSsrDy9   2023年12月23日   15   0   0 linuxlinuxripgrepripgrepubuntuubuntuubuntu18.04ubuntu18.04
  HRODlxSsrDy9   2023年12月23日   20   0   0 libgllinuxlinuxlibgl
  HRODlxSsrDy9   2023年12月23日   17   0   0 pythonlinuxcimanimlinuxPython当前目录manimci当前目录
  HRODlxSsrDy9   2023年12月23日   54   0   0 unixlinuxglibcbcbcunixlinuxglibc
  HRODlxSsrDy9   2023年12月23日   49   0   0 bc源码编译linuxlinuxccls源码编译bcubuntuUbuntuccls
  HRODlxSsrDy9   2023年12月23日   81   0   0 源码编译faisslinuxlinux源码编译#includeubuntu#includeUbuntufaiss
  HRODlxSsrDy9   2023年12月23日   18   0   0 linuxrealpathlinuxshell相对路径Shell相对路径配置文件配置文件realpath
  wwLZeziuqjLR   2023年12月23日   58   0   0 服务器ablinuxlinux服务器Time运维ab运维Time
  HRODlxSsrDy9   2023年12月23日   13   0   0 linuxgithubAlbertlinuxAlbertgitgitubuntugithubUbuntu
  HRODlxSsrDy9   2023年12月23日   100   0   0 linuxubuntugit命令行fzffzfubuntulinux命令行git
  HRODlxSsrDy9   2023年12月23日   62   0   0 linuxlinuxbash报错解决ubuntuBash报错解决Ubuntu
  HRODlxSsrDy9   2023年12月23日   67   0   0 linuxlinuxshell创建文件夹判断文件是否存在Shell判断文件夹是否存在判断文件是否存在创建文件夹判断文件夹是否存在
  HRODlxSsrDy9   2023年12月23日   23   0   0 编译链接多个实现文件linux编译链接多个头文件linux头文件gcc编译链接多个实现文件头文件gcc编译链接多个头文件
zAXjsPdxtYy3
zAXjsPdxtYy3
作者其他文章 更多
全网国内外20个开源知识管理工具

2023-12-23

Failed to build lxml ERROR: Could not build wheels for lxml, which is required to install pyproject.

2023-12-23

Github上火爆的个人知识管理AI大脑：Quivr

2023-12-22

轻松搭建短域名短链接服务系统，可选权限认证，并自动生成证书认证把nginx的http访问转换为https加密访问，完整步骤和代码

2023-12-07

linux中各种最新网卡2.5G网卡驱动，不同型号的网卡需要不同的驱动，整合各种网卡驱动，包括有线网卡、无线网卡、Wi-Fi热点

2023-12-01

AI 换脸工具、ChatGPT Admin Web 网页应用、API 调用 Midjourney 进行 AI 画图、中华古诗词数据库、Neutrino-Proxy 是一款高性能网络代理软件

2023-11-14

Python Wordcloud报错：Only supported for TrueType fonts，多种解决方案

2023-11-13

【网盘聚合神器】支持百度(不限速)、阿里、天翼、迅雷、蓝奏、谷歌等29款网盘，使用Docker部署Alist网盘直链程序，给电脑整个80亿GB硬盘

2023-11-02

Linux下redsocks流量转发结合iptables流量透传出现 socket: Too many open files 和 connect: Bad file descriptor

2023-11-02

自动生成文档在线管理，为开源项目而生的开源项目——做开源项目的专属伙伴Docusaurus

2023-11-02

最新推荐 更多
基于uniapp+vue3自定义增强版table表格组件「兼容H5+小程序+App端」

2024-05-18

解释下什么是事件代理？应用场景？

2024-05-18

Vue项目中有封装过axios吗？主要是封装哪方面的？

2024-05-17

浅谈Vue.js与原生开发

2024-05-17

vue要做权限管理该怎么做？如果控制到按钮级别的权限怎么做？

2024-05-17

Vue模板语法、属性绑定、条件渲染的学习

2024-05-17

vue3编译优化之“静态提升”

2024-05-17

VUE-局部使用

2024-05-17

你是怎么处理vue项目中的错误的？

2024-05-17

实现抖音 “视频无限滑动“效果

2024-05-17

说说webpack proxy工作原理？为什么能解决跨域?

2024-05-17

我为什么还要造一个前端轮子？

2024-05-17

一款摸鱼神器！帮助你利用上班时间背单词！

2024-05-17

next-route

2024-05-17

深入探索JavaScript中的structuredClone：现代深拷贝的解密指南

2024-05-17

ES 2024 新特性

2024-05-17

记使用pdf.js过程遇到的坑

2024-05-17

JavaScript中执行上下文和执行栈是什么？

2024-05-17

如何使用 JS 判断用户是否处于活跃状态

2024-05-17

使用 JS 实现在浏览器控制台打印图片 console.image()

2024-05-17

常用标签
数据数据数据数据javalinuxlinuxpythonCentOSredisJava区块链技术python区块链信息系统字符串MySQL资讯项目管理mysql教程MySQL