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

Fix IPv6 trace: use node:https with family option instead of IP literal fetch (1.1.1)

Browse Source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
Gino Ben Salah
2026-09-08 01:23:28 +02:00
parent 60c1c8770e
commit 37e9af4080
5 changed files with 39 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+8 -1
View File
@@ -3,10 +3,17 @@
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.1] - 2026-09-08
### Fixed
- IPv6 trace showed `n/a (fetch failed)`: Node's `fetch` (undici) mangles IPv6 literals during TLS
hostname verification. The check now uses `node:https` with the `family` option against
`www.cloudflare.com`, so both families work with normal certificate validation.
## [1.1.0] - 2026-09-08
### Changed
- WARP check now queries Cloudflare over IPv4 and IPv6 separately (by edge IP literal) and logs both
- WARP check now queries Cloudflare over IPv4 and IPv6 separately 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.