NekoBox for Android

https://matsuridayo.github.io/
Admin
NekoBox for Android is a universal proxy toolchain for Android based on sing-box.
Tokens:1,409
Snippets:11
Trust Score:8.3
Update:1 year ago
Show doc for...
Tokens:
Raw
### TLS伪装设置: Reality Configuration

Source: https://matsuridayo.github.io/nb4a-configuration

Configuration for Reality, a TLS obfuscation technique. It requires uTLS to be enabled and has known compatibility issues with Xray-core, recommending the same implementation for client and server.

```json
{
  "tls": {
    "enabled": true,
    "reality": {
      "enabled": true,
      "short_id": "",
      "server_name": "your_domain.com"
    }
  }
}
```

--------------------------------

### TLS伪装设置: uTLS Configuration

Source: https://matsuridayo.github.io/nb4a-configuration

Configuration for uTLS (Universal TLS) for TLS伪装 (TLS obfuscation) settings. This requires uTLS to be enabled and does not support SpiderX. ShortId can be left empty.

```json
{
  "tls": {
    "enabled": true,
    "utls": {
      "enabled": true,
      "mode": "chrome"
    }
  }
}
```

--------------------------------

### ShadowTLS Chain Configuration

Source: https://matsuridayo.github.io/nb4a-configuration

Configuration for using ShadowTLS, typically chained with a ShadowSocks type server for internet access. The order is ShadowTLS -> ShadowSocks. Compatibility of sing-box ShadowTLS with the original version is unknown.

```json
{
  "outbounds": [
    {
      "protocol": "shadowsocks",
      "tag": "shadowsocks_out",
      "server": "shadowsocks_server",
      "server_port": 8388,
      "password": "shadowsocks_password",
      "method": "aes-256-gcm"
    },
    {
      "protocol": "shadowtls",
      "tag": "shadowtls_out",
      "server": "shadowtls_server",
      "server_port": 443,
      "password": "shadowtls_password",
      "tls": {
        "enabled": true,
        "server_name": "your_domain.com"
      }
    }
  ],
  "route": {
    "rules": [
      {
        "outbound_tag": "shadowtls_out",
        "domain": "*"
      }
    ],
    "chain": {
      "shadowtls_out": "shadowsocks_out"
    }
  }
}
```

--------------------------------

### TUIC v5 Protocol with sing-box

Source: https://matsuridayo.github.io/nb4a-configuration

TUIC v5 protocol implementation using sing-box, eliminating the need for separate plugins. Supports `udp_over_stream` for real-time UDP streaming when sing-box is used as the TUIC server.

```json
{
  "protocol": "tuic",
  "version": 5,
  "server": "your_server_address",
  "port": 443,
  "password": "your_password",
  "udp_over_stream": true
}
```

--------------------------------

### TLS Security Settings: Allow Insecure Connections

Source: https://matsuridayo.github.io/nb4a-configuration

Configuration option to allow insecure connections in TLS settings. Enabling this reduces security to plaintext levels and may be necessary if server certificate configuration is incorrect.

```json
{
  "tls": {
    "enabled": true,
    "allow_insecure": true
  }
}
```

--------------------------------

### sing-box Private Protocols: V2Ray Transport

Source: https://matsuridayo.github.io/nb4a-configuration

Configuration for V2Ray Transport (http/ws/grpc/quic) in sing-box, used with protocols like vmess, vless, and trojan. Supports earlydata format like `?ed=2048` for compatibility with Xray.

```json
{
  "protocol": "vmess",
  "settings": {
    "vnext": [
      {
        "address": "your_server_address",
        "port": 8080,
        "users": [
          {
            "id": "your_uuid",
            "alterId": 4
          }
        ],
        "transport": {
          "protocol": "ws",
          "host": "your_domain.com",
          "path": "/ws?ed=2048"
        }
      }
    ]
  }
}
```

--------------------------------

### TLS Security Settings: Certificate Chain

Source: https://matsuridayo.github.io/nb4a-configuration

Configuration for providing the certificate chain in PEM format for TLS security. This is essential for establishing secure connections when custom certificates are used.

```json
{
  "tls": {
    "enabled": true,
    "certificate_file": "/path/to/your/certificate.pem"
  }
}
```

--------------------------------

### sing-box Private Protocols: Multiplex

Source: https://matsuridayo.github.io/nb4a-configuration

Configuration for the `multiplex` protocol in sing-box, compatible with ss, vmess, and vless protocols. Multiplexing can improve performance by combining multiple connections.

```json
{
  "protocol": "ss",
  "settings": {
    "address": "your_server_address",
    "port": 2087,
    "method": "aes-256-gcm",
    "password": "your_password",
    "plugin": {
      "name": "multiplex",
      "arg": ""
    }
  }
}
```

--------------------------------

### sing-box Private Protocols: UOT

Source: https://matsuridayo.github.io/nb4a-configuration

Configuration for the `uot` (UDP over TCP) protocol in sing-box, specifically for the ss (Shadowsocks) protocol. This allows UDP traffic to be tunneled over TCP.

```json
{
  "protocol": "ss",
  "settings": {
    "address": "your_server_address",
    "port": 8888,
    "method": "chacha20-poly1305",
    "password": "your_password",
    "plugin": {
      "name": "uot",
      "arg": ""
    }
  }
}
```

--------------------------------

### sing-box Private Protocols: Packetaddr and XUDP

Source: https://matsuridayo.github.io/nb4a-configuration

Configuration for `packetaddr` and `xudp` protocols in sing-box, primarily used with vmess and vless protocols. These provide alternative transport mechanisms for tunneling.

```json
{
  "protocol": "vmess",
  "settings": {
    "vnext": [
      {
        "address": "your_server_address",
        "port": 8443,
        "users": [
          {
            "id": "your_uuid"
          }
        ],
        "transport": {
          "protocol": "packetaddr",
          "data": {
            "type": "xudp"
          }
        }
      }
    ]
  }
}
```

--------------------------------

### TLS Security Settings: SNI Behavior

Source: https://matsuridayo.github.io/nb4a-configuration

Describes the Server Name Indication (SNI) behavior in sing-box and v2ray. If SNI is left empty and the server address is a domain, the server address will be used to fill SNI.

```json
{
  "tls": {
    "enabled": true,
    "server_name": ""
  }
}
```
Tokens:
Raw