[2026-09-23] eagle: family/how-to/rasputin-router.md

This commit is contained in:
Alexey Martemyanov committed 2026-09-23 01:06:59 +06:00
1 parent 8e4f6ec743
commit de1d2fd93b
1 file changed
+8 -3
+8 -3
View File
@@ -12,7 +12,8 @@ tags:
--- ---
# Rasputin R5S OpenWrt router # Rasputin R5S OpenWrt router
> Status as of 2026-09-22: Rasputin is the OpenWrt edge/LAN router, routing normal LAN traffic through a VLESS/Xray tunnel via `tun0`, with explicit direct-WAN exceptions for upstream LAN access and Mac `cloudflared` QUIC traffic. 🔴 **WAN СНОВА ПЕРЕЕХАЛ (2026-09-22): `eth0` теперь `192.168.1.50/24`, gw `192.168.1.1`** — Распутин воткнут в сегмент `192.168.1.0/24`, где живут Кра́кен (`.14`/`.15`), ТВ (`.70`) и Мак (`.57`/`.69`). Прежний `192.168.2.157/24` (gw `192.168.2.2`) больше не активен. Линк WAN — `1000/full`, MAC `36:ae:87:04:08:dc`. Транзит в GPON-сегмент `192.168.0.0/24` — см. одноимённый раздел. > Status as of 2026-09-22: Rasputin is the OpenWrt edge/LAN router, routing normal LAN traffic through a VLESS/Xray tunnel via `tun0`, with explicit direct-WAN exceptions for upstream LAN access and Mac `cloudflared` QUIC traffic. 🔴 **WAN СНОВА ПЕРЕЕХАЛ (2026-09-22): `eth0` теперь `192.168.1.50/24`, gw `192.168.1.1`, MAC `36:ae:87:04:08:dc`, линк `1000/full`** — Распутин воткнут в сегмент `192.168.1.0/24`, где живут Кра́кен (`.14`/`.15`) и ТВ (`.70`). Прежний `192.168.2.157/24` (gw `192.168.2.2`) больше не активен.
> 🔴 **Мак теперь в LAN Распутина** — `192.168.6.173` (en0), а НЕ `192.168.1.57`. Транзит из LAN `192.168.6.0/24` в `192.168.1.0/24` **СЛОМАН** (тот же класс проблемы, что и GPON-сегмент): правила `100` покрывают только `192.168.2.0/24` и `192.168.0.0/24`. См. раздел «🔴 Транзит из LAN в 192.168.1.0/24».
## Identity ## Identity
@@ -305,24 +306,28 @@ Backup made before the Cloudflare direct-bypass update:
## Policy Routing ## Policy Routing
Current rules: Current rules (снято 2026-09-22, живая система):
```text ```text
0: from all lookup local 0: from all lookup local
98: from 192.168.6.173 ipproto udp dport 7844 lookup main 98: from 192.168.6.173 ipproto udp dport 7844 lookup main
99: from 192.168.6.104 ipproto udp dport 7844 lookup main 99: from 192.168.6.104 ipproto udp dport 7844 lookup main
100: from all to 192.168.2.0/24 lookup main 100: from all to 192.168.2.0/24 lookup main
100: from all to 192.168.0.0/24 lookup main
101: from all iif br-lan lookup vpn 101: from all iif br-lan lookup vpn
32766: from all lookup main 32766: from all lookup main
32767: from all lookup default 32767: from all lookup default
``` ```
Две строки с `priority 100` — это нормально (обе добавлены вручную, `192.168.0.0/24` — 2026-09-17).
Meaning: Meaning:
- Mac Wi-Fi `192.168.6.173` UDP/7844 goes direct through `main`. - Mac Wi-Fi `192.168.6.173` UDP/7844 goes direct through `main`.
- Mac Ethernet `192.168.6.104` UDP/7844 goes direct through `main`. - Mac Ethernet `192.168.6.104` UDP/7844 goes direct through `main`.
- Traffic to upstream LAN `192.168.2.0/24` goes direct through `main`. - Traffic to upstream LAN `192.168.2.0/24` goes direct through `main`.
- 🔴 Traffic to the GPON segment `192.168.0.0/24` is **NOT** covered by rule `100` (2026-09-17) → falls through to rule `101` → `table vpn` → `tun0`. Доступ к GPON-сегменту из LAN `192.168.6.0/24` не работает. See the «🔴 Транзит Rasputin → 192.168.0.0/24» section. - Traffic to GPON `192.168.0.0/24` goes direct through `main` (исправлено 2026-09-17).
- 🔴 Traffic to `192.168.1.0/24` (Кра́кен, ТВ, ASUS) is **NOT** covered by any rule `100` (2026-09-22) → falls through to rule `101` → `table vpn` → `tun0`. Доступ к Кра́кену/ТВ из LAN `192.168.6.0/24` не работает. См. раздел «🔴 Транзит из LAN в 192.168.1.0/24».
- All other traffic entering from LAN bridge `br-lan` uses `table vpn`. - All other traffic entering from LAN bridge `br-lan` uses `table vpn`.
- `table vpn` sends default traffic through `tun0`. - `table vpn` sends default traffic through `tun0`.