rego-tunnel: revert to 172.30.x.x for VM (avoid routing conflict)
Some checks failed
Test / test (push) Has been cancelled

Using same subnet for container external IP and VM internal IP
causes routing conflicts. Revert VM to default 172.30.0.0/24.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
2025-12-19 09:09:35 +00:00
parent 9192c62a9e
commit f992425e96

View File

@@ -19,8 +19,8 @@ get_windows_ip() {
local ip=$(awk '/Windows/ {print $3}' /var/lib/misc/dnsmasq.leases 2>/dev/null | head -1) local ip=$(awk '/Windows/ {print $3}' /var/lib/misc/dnsmasq.leases 2>/dev/null | head -1)
if [[ -n "$ip" ]]; then echo "$ip"; return; fi if [[ -n "$ip" ]]; then echo "$ip"; return; fi
# Method 2: ip neigh (ARP table) - look for 172.31.x.x on docker interface (VM_NET_IP subnet) # Method 2: ip neigh (ARP table) - look for 172.30.x.x on docker interface
ip=$(ip neigh show dev docker 2>/dev/null | grep -oE '172\.31\.[0-9]+\.[0-9]+' | head -1) ip=$(ip neigh show dev docker 2>/dev/null | grep -oE '172\.30\.[0-9]+\.[0-9]+' | head -1)
if [[ -n "$ip" ]]; then echo "$ip"; return; fi if [[ -n "$ip" ]]; then echo "$ip"; return; fi
# Method 3: qemu.ip file (if available) # Method 3: qemu.ip file (if available)