ZJU Connect

🚫 Disclaimer

This program is provided as is, and the author does not guarantee the correctness or reliability of the program. Please judge whether the specific scenario is suitable for using this program. The problems or consequences caused by using this program are borne by the user!

中文 | English

This program is based on EasierConnect (now Archived), thanks to the original author lyc8503.

QQ group: 946190505, welcome to join the discussion.

Usage

Run directly

Windows users can use the GUI version ZJU Connect for Windows (There's only Chinese GUI).

Download the latest version of the corresponding platform on the Release page.
Take macOS as an example, unzip the executable file zju-connect.
macOS needs to remove security restrictions first. Run in the command line: sudo xattr -rd com.apple.quarantine zju-connect.
Run in the command line: ./zju-connect -username <username> -password <password>.
At this time, port 1080 is the Socks5 proxy, and port 1081 is the HTTP proxy. If you need to change the default port, please refer to Arguments.

Run as a service

Please first run directly to ensure that there is no error before creating a service, so as to avoid repeated login failures resulting in temporary IP ban!

For Linux distributions based on Systemd such as Ubuntu/Debian, RHEL, Arch, etc., in addition to running as described above, ZJU Connect can also be installed as a system service through the following steps to achieve automatic reconnection function:

Download the latest version of the corresponding platform on the Release page, place the executable file in the /opt directory and grant executable permissions.
Create the zju-connect directory under /etc, and create the configuration file config.toml in the directory. The content refers to config.toml.example in the repository.

Create the zju-connect.service file under /lib/systemd/system, and the content is as follows:

[Unit]
Description=ZJU Connect
After=network-online.target
Wants=network-online.target

[Service]
Restart=on-failure
RestartSec=5s
ExecStart=/opt/zju-connect -config /etc/zju-connect/config.toml

[Install]
WantedBy=multi-user.target

Execute the following command to enable the service and set it to start automatically:
```
sudo systemctl start zju-connect
sudo systemctl enable zju-connect
```

For MacOS, system services are based on launchd, which is different from systemd. You can apply the following steps to achieve the same effect:

Download the latest version pf darwin platform on the Release page.
Place the executable file in the /usr/local/bin/ directory and grant executable permissions.
Remove security restrictions: sudo xattr -rd com.apple.quarantine zju-connect.
Create plist file referring to com.zju.connect.plist. Since plist is a binary file, it's recommended to edit using PlistEdict Pro. Here are some key configurations:
- UserName: The default user for running zju-connect in the background is root, it's recommended to change to your own username.
- ProgramArguments: zju-connect running parameters.
- StandardErrorPath: The directory for outputting zju-connect running logs (for debugging, can be omitted).
- StandardOutPath: The directory for outputting zju-connect running logs (for debugging, can be omitted).
- RunAtLoad: Whether to start automatically at boot.
- KeepAlive: Whether to reconnect in the background.
For more details, please refer to the following documents:
- plist argument docs
- Apple Developer docs
Move the plist file to ~/Library/LaunchDaemons/ directory, and execute the following command:
```
cd /Library/LaunchDaemons
sudo chown root:wheel com.zju.connect.plist
```
Execute the following command to enable the service and set it to start automatically:
```
sudo launchctl load com.zju.connect.plist
```
Execute the following command to disable the service:
```
sudo launchctl unload com.zju.connect.plist
```

If you need to turn on/off the service, you can directly turn on/off zju-connect in the background program switch in macOS system settings.

For OpenWrt system, you can use procd init script to make zju-connect start automatically and run in the background. Add corresponding node and routing rules in the proxy plugin to use.

Download the latest version of the corresponding platform on the Release page, place the executable file in the /usr/bin directory and grant executable permissions.
Refer to config.toml.example in the repository, create the configuration file /etc/back2zju.toml, configure the socks/http proxy port, and because routing is implemented through the proxy plugin, it's recommended to set the zju-connect configuration item proxy_all to true.

Save the following content as /etc/init.d/back2zju and grant executable permissions:

#!/bin/sh /etc/rc.common

USE_PROCD=1
START=60
STOP=03

PROGRAM="/usr/bin/zju-connect"
NET_CHECKER="rvpn.zju.edu.cn"
CONFIG_FILE="/etc/back2zju.toml"
LOG_FILE="/var/log/back2zju.log"

boot() {
	ubus -t 10 wait_for network.interface.wan 2>/dev/null
	sleep 10
	rc_procd start_service
}

start_service() {
    ping -c1 ${NET_CHECKER} >/dev/null || ping -c1 ${NET_CHECKER} >/dev/null || return 1
    procd_open_instance
    procd_set_param command /bin/sh -c "${PROGRAM} -config ${CONFIG_FILE} >>${LOG_FILE} 2>&1"
    procd_set_param respawn 3600 5 3
    procd_set_param limits core="unlimited"
    procd_set_param limits nofile="200000 200000"
    procd_set_param file ${CONFIG_FILE}
    procd_close_instance
    logger -p daemon.warn -t back2zju 'Service has been started.'
}

reload_service() {
    stop
    start
    logger -p daemon.warn -t back2zju 'Service has been restarted.'
}

Execute the following command:
```
/etc/init.d/back2zju enable
/etc/init.d/back2zju start
```
Or enable and start back2zju in System-Startup page of OpenWrt LuCi web page (you can also disable the service here).

Then zju-connect will start running, support boot self-starting, and its running log is saved in /var/log/back2zju.log.
Add corresponding node and routing rules in the proxy plugin to use.

According to the configuration in /etc/back2zju.toml, add node in the proxy plugin. Fill in 127.0.0.1 for IP, and keep the port/protocol consistent with /etc/back2zju.toml. If you set the socks username and password, you also need to fill it in.

Then add routing rules in the corresponding proxy plugin, the specific operation is omitted.

Note:
1. The internal IP range used by ZJU campus network is 10.0.0.0/8, you may need to remove this IP range from the direct connection list/LAN list of the proxy plugin and add it to the proxy list.
2. Please make sure that the RVPN server used is directly connected to OpenWrt. If rvpn.zju.edu.cn is not configured as a direct connection, this domain name may match the routing rules and other zju.edu.cn traffic will be sent to the zju-connect proxy, which will cause network anomalies.

Run in Docker

docker run -d --name zju-connect -v $PWD/config.toml:/home/nonroot/config.toml -p 1080:1080 -p 1081:1081 --restart unless-stopped mythologyli/zju-connect

You can also use Docker Compose. Create docker-compose.yml file with the following content:

version: '3'

services:
   zju-connect:
      image: mythologyli/zju-connect
      container_name: zju-connect
      restart: unless-stopped
      ports:
         - 1080:1080
         - 1081:1081
      volumes:
         - ./config.toml:/home/nonroot/config.toml

And run the following command in the same directory:

docker compose up -d

Arguments

server: SSL VPN server address, default is rvpn.zju.edu.cn
port: SSL VPN server port, default is 443
username: Network account. For example: student ID
password: Network account password
disable-server-config: Disable server configuration, generally no need to add this argument
disable-zju-config: Disable ZJU related configuration, generally no need to add this argument
disable-zju-dns: Disable ZJU DNS and use local DNS, generally no need to add this argument
disable-multi-line: Disable automatic line selection based on latency. After adding this argument, use the line specified by the server parameter
proxy-all: Whether to proxy all traffic, generally no need to add this argument
socks-bind: SOCKS5 proxy listening address, default is :1080
socks-user: SOCKS5 proxy username, leave blank if no authentication is required
socks-passwd: SOCKS5 proxy password, leave blank if no authentication is required
http-bind: HTTP proxy listening address, default is :1081. Set to "" to disable HTTP proxy
shadowsocks-url: Shadowsocks server URL. For example: ss://aes-128-gcm:password@server:port. Format refer to here
tun-mode: TUN mode (experimental). Please read the TUN mode precautions below
add-route: Add route according to the configuration issued by the server when TUN mode is enabled
dns-ttl: DNS cache time, default is 3600 seconds
disable-keep-alive: Disable periodic keep-alive, generally no need to add this argument
zju-dns-server: ZJU DNS server address, default is 10.10.0.21
secondary-dns-server: Standby DNS server used when ZJU DNS server cannot be used, default is 114.114.114.114. Leave blank to use the system default DNS, but must be set when dns-hijack is enabled
dns-server-bind: DNS server listening address, default is empty to disable. For example, set to 127.0.0.1:53, then you can send DNS requests to 127.0.0.1:53
dns-hijack: Hijack DNS requests when TUN mode is enabled, it's recommended to add this argument when TUN mode is enabled
debug-dump: Whether to enable debugging, generally no need to add this argument
tcp-port-forwarding: TCP port forwarding, format is local address-remote address,local address-remote address,..., for example 127.0.0.1:9898-10.10.98.98:80,0.0.0.0:9899-10.10.98.98:80. Multiple forwarding is separated by ,
udp-port-forwarding: UDP port forwarding, format is local address-remote address,local address-remote address,..., for example 127.0.0.1:53-10.10.0.21:53. Multiple forwarding is separated by ,
custom-dns: Specify custom DNS resolution results, format is domain name:IP,domain name:IP,..., for example www.cc98.org:10.10.98.98,appservice.zju.edu.cn:10.203.8.198. Multiple resolutions are separated by ,
twf-id: twfID login, for debugging purposes, generally no need to add this argument
config: Specify the configuration file, the content refers to config.toml.example. Other parameters are ignored when the configuration file is enabled

TUN mode precautions

Need to run with administrator privileges
Windows system needs to go to Wintun official website to download wintun.dll and place it in the same directory as the executable file
To ensure that *.zju.edu.cn is resolved correctly, it's recommended to configure dns-hijack to hijack the system DNS
macOS does not currently support accessing addresses outside of 10.0.0.0/8 through the TUN interface

Schedule

Completed

Proxy TCP traffic
Proxy UDP traffic
SOCKS5 proxy service
HTTP proxy service
Shadowsocks proxy service
ZJU DNS resolution
ZJU rules addition
Support IPv6 direct connection
DNS cache acceleration
Automatic line selection
TCP port forwarding
UDP port forwarding
Start through configuration file
Periodic keep-alive
TUN mode
Automatical DNS hijack

To Do

Fake IP mode

Contributors

Thanks

EasierConnect
socks2http

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

README_en.md

README_en.md

ZJU Connect

Usage

Run directly

Run as a service

Run in Docker

Arguments

TUN mode precautions

Schedule

Completed

To Do

Contributors

Thanks

Files

README_en.md

Latest commit

History

README_en.md

File metadata and controls

ZJU Connect

Usage

Run directly

Run as a service

Run in Docker

Arguments

TUN mode precautions

Schedule

Completed

To Do

Contributors

Thanks