Simple Steps to Let AI Agent Help You Build Your Own Internet Access

Go to DMIT to buy a server, but it's currently unavailable. Buying from Bandwagon Host or other service providers that support CN2 GIA lines is also fine.

After payment, save and enter the server page, click to save the SSH private key.

Let AI handle all the subsequent work: Here I used the latest Ring-2.6-1T launched by @AntLingAGI, which is extremely fast and super cheap. Ring-2.6-1T is currently 75% off on OpenRouter, the price is practically free: https://openrouter.ai/inclusionai/ring-2.6-1t

How to connect: Use Pi agent or Hermes agent, bind OpenRouter and fill in the API key, find inclusionai/ring-2.6-1t under the model selection and select it. Besides local agents, you can also experience it on the official website: https://ling.tbox.cn/chat

Tell the agent: Log into the server via ssh -i ~/DMIT-Name-id_rsa/id_rsa.pem [email protected], disable IPv6, install Docker, read this document, and install remnawave: https://docs.rw/docs/install/remnawave-panel

After successfully installing remnawave, a username and password will be automatically generated. After logging in, you will see the application interface just installed.

Select Node - Management from the left navigation bar, create a new node. Fill in the region and IP address corresponding to your server. If you have other servers, you can fill in those as well, then click "Copy docker-compose.yml"

Then tell the agent: Install this: Paste the docker-compose.yml you just copied.

Wait a moment, switch back to the browser, and you can see that the remnawave backend already shows connected.

Then tell the agent to log into the remnawave backend: Log into the remnawave panel, username xxx password xxxxxxx, add configuration files and hosts, create a new user to test if the connection is successful. Use the vless protocol for the configuration file, you can refer to this:

json
{
  "log": {
    "loglevel": "info"
  },
  "inbounds": [
    {
      "tag": "VLESS_TCP_REALITY",
      "port": 8443,
      "protocol": "vless",
      "settings": {
        "clients": [],
        "decryption": "none"
      },
      "sniffing": {
        "enabled": true,
        "destOverride": [
          "http",
          "tls"
        ]
      },
      "streamSettings": {
        "network": "tcp",
        "security": "reality",
        "realitySettings": {
          "target": "gateway.icloud.com:443",
          "shortIds": [
            "",
            "a1b2c3d4"
          ],
          "privateKey": "your key",
          "serverNames": [
            "gateway.icloud.com"
          ]
        }
      }
    }
  ],
  "outbounds": [
    {
      "tag": "DIRECT",
      "protocol": "freedom"
    },
    {
      "tag": "BLOCK",
      "protocol": "blackhole"
    }
  ],
  "routing": {
    "rules": [
      {
        "protocol": [
          "bittorrent"
        ],
        "outboundTag": "BLOCK"
      },
      {
        "ip": [
          "geoip:private"
        ],
        "outboundTag": "BLOCK"
      }
    ],
    "domainStrategy": "IPIfNonMatch"
  }
}

Now entering the panel page should show that it's already configured. Create a new user to test. If the user's subscription link shows vless://xxxxxx, it means there's no problem.

Explanation:

Why disable IPv6: Because Claude and many overseas websites might block IPv6. If not disabled, for example, opening websites like Grok.com will directly show blocked.

Why not choose 3x-ui: Personally, I think remnawave is better, more powerful, user management is also better, and it can generate custom subscription pages with full automated management.

Remember to replace the SSH part with your own address.

If you want to add more nodes and hosts, repeat the above steps. You can operate via the agent or manually in the panel, but I still recommend letting the agent log in and help you do it. When you do it yourself, often one or two details are incorrect causing connection failure, and you can't find where the problem is. Ultimately, you still need to let the agent log in to check.

If you want to support more protocols, you can write all protocols into one configuration file.