wwqgtxx a1c7881229 chore: rebuild udp dns resolve
The DNS resolution of the overall UDP part has been delayed to the connection initiation stage. During the rule matching process, it will only be triggered when the IP rule without no-resolve is matched.

For direct and wireguard outbound, the same logic as the TCP part will be followed, that is, when direct-nameserver (or DNS configured by wireguard) exists, the result of the matching process will be discarded and the domain name will be re-resolved. This re-resolution logic is only effective for fakeip.

For reject and DNS outbound, no resolution is required.

For other outbound, resolution will still be performed when the connection is initiated, and the domain name will not be sent directly to the remote server at present.
2025-05-27 10:45:26 +08:00
2025-04-25 12:36:28 +08:00
2025-05-27 10:45:26 +08:00
2025-05-25 22:07:29 +08:00
2025-05-27 10:45:26 +08:00
2025-05-27 10:45:26 +08:00
2023-11-03 21:58:21 +08:00
2023-11-03 21:58:21 +08:00
2025-05-24 23:19:38 +08:00
2025-05-15 18:07:55 +08:00
2025-05-03 15:06:13 +08:00
2024-08-16 14:15:36 +08:00
2025-05-27 10:45:26 +08:00
2023-01-14 18:10:22 +08:00
2023-11-03 21:58:21 +08:00
2022-04-28 14:18:54 +08:00
2024-07-31 13:04:30 +08:00
2022-12-15 13:25:18 +08:00
2023-11-03 21:58:21 +08:00
2025-05-24 22:23:10 +08:00
2025-05-24 22:23:10 +08:00
2019-10-18 11:12:35 +08:00
2025-02-04 00:44:18 +08:00
2024-08-16 14:15:36 +08:00
2021-12-09 17:54:53 +08:00

Meta Kennel
Meta Kernel

Another Mihomo Kernel.

Features

  • Local HTTP/HTTPS/SOCKS server with authentication support
  • VMess, VLESS, Shadowsocks, Trojan, Snell, TUIC, Hysteria protocol support
  • Built-in DNS server that aims to minimize DNS pollution attack impact, supports DoH/DoT upstream and fake IP.
  • Rules based off domains, GEOIP, IPCIDR or Process to forward packets to different nodes
  • Remote groups allow users to implement powerful rules. Supports automatic fallback, load balancing or auto select node based off latency
  • Remote providers, allowing users to get node lists remotely instead of hard-coding in config
  • Netfilter TCP redirecting. Deploy Mihomo on your Internet gateway with iptables.
  • Comprehensive HTTP RESTful API controller

Dashboard

A web dashboard with first-class support for this project has been created; it can be checked out at metacubexd.

Configration example

Configuration example is located at /docs/config.yaml.

Docs

Documentation can be found in mihomo Docs.

For development

Requirements: Go 1.20 or newer

Build mihomo:

git clone https://github.com/MetaCubeX/mihomo.git
cd mihomo && go mod download
go build

Set go proxy if a connection to GitHub is not possible:

go env -w GOPROXY=https://goproxy.io,direct

Build with gvisor tun stack:

go build -tags with_gvisor

IPTABLES configuration

Work on Linux OS which supported iptables

# Enable the TPROXY listener
tproxy-port: 9898

iptables:
  enable: true # default is false
  inbound-interface: eth0 # detect the inbound interface, default is 'lo'

Debugging

Check wiki to get an instruction on using debug API.

Credits

License

This software is released under the GPL-3.0 license.

In addition, any downstream projects not affiliated with MetaCubeX shall not contain the word mihomo in their names.

Description
A simple Python Pydantic model for Honkai: Star Rail parsed data from the Mihomo API.
Readme MIT 46 MiB
Languages
Python 100%