ginoblij/DiscordBot-CloudflareWarp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Log both IPv4 and IPv6 Cloudflare egress IPs in WARP check (1.1.0)

Browse Source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
Gino Ben Salah
2026-09-08 01:20:55 +02:00
parent 1a9dc1d676
commit 60c1c8770e
5 changed files with 72 additions and 46 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+14
View File
@@ -3,6 +3,20 @@
All notable changes to this project are documented here, newest first.
Every change is committed and pushed so the history can be followed in git as well.
## [1.1.0] - 2026-09-08
### Changed
- WARP check now queries Cloudflare over IPv4 and IPv6 separately (by edge IP literal) and logs both
egress IPs: `ipv4=104.28.x.x (warp=on) ipv6=2a09:bac1:... (warp=on) colo=AMS loc=NL`.
- `/warp` slash command shows the IPv4 and IPv6 Cloudflare IPs on separate lines.
- "Connected" now means the IPv4 path (the one Discord uses) reports `warp=on`; IPv6 is informational.
### Verified on the host (192.168.5.67)
- Host public IP reports `warp=off`; inside the container both families report `warp=on`, colo `AMS`.
- The Node process's Discord gateway socket originates from `172.16.0.2` on the `CloudflareWARP`
interface, so bot traffic really goes through the tunnel.
- Docker health check reports `healthy`; `/ping` and `/warp` are registered in the test guild.
## [1.0.0] - 2026-09-08
### Added