Skip to content

Debugging Log

Jump to bottom
Ian Clarke edited this page Aug 27, 2025 · 2 revisions

Freenet Debugging Log

Current Week: 2025-Week-35 (Aug 26 - Sep 1)
Archives: 2025-Week-34 | Older...

Active Hypotheses

H1: Gateway Communication Degradation Over Distance/Network Boundaries

Status: 🟡 Under Investigation
Relevant Log Entries: 2025-08-26-001, 2025-08-26-002
Theory: Something about network communication degrades when peers connect to remote gateways vs local gateways. Could be latency, packet loss, NAT traversal, or protocol-specific issues.
Next Test: Isolate network variables systematically

H2: Multiple WebSocket Connections Per Peer Issue

Status: 🟡 Needs Testing
Relevant Log Entries: 2025-08-27-001
Theory: Current WebSocket API implementation may not handle multiple client connections from same peer correctly
Next Test: Single user per peer isolation test

H3: AWS UDP Traffic Filtering

Status: 🟡 Partial Evidence
Relevant Log Entries: 2025-08-25-001
Theory: AWS may be filtering or throttling UDP traffic on certain ports
Workaround Active: Using alternative provider (nova.locut.us)

Current Week

Entries older than 7 days are moved to weekly archives.

2025-08-27-001

Time: 09:29 CDT
Activity: Meeting with Nacho/Hector
Facts:

  • Discussed current debugging approach and issues
  • Nacho confirmed connection stability with ping app
  • River integration test PR opened by Hector
  • Agreed to create systematic integration tests
  • Decided to document debugging efforts in wiki

2025-08-26-002

Time: ~23:00 (evening)
Activity: Local vs Remote Gateway Test
Test Configuration:

# Local test
3 peers running locally, 1 as gateway
Test: River multi-user end-to-end

# Remote test  
2 local peers → remote gateway (nova.locut.us)
Test: Same River multi-user end-to-end

Results:

  • Local configuration: PASSED - all operations successful
  • Remote configuration: FAILED - subscription timeout after room creation
  • Failure consistent across multiple runs

2025-08-26-001

Time: ~14:00 (estimated)
Activity: River Release with Subscribe Fix
Facts:

  • Released new version of River
  • Changed to use separate GET and SUBSCRIBE operations
  • Previously using subscribe=true flag with GET requests
  • Subscribe flag with GET is not properly supported in freenet-core Result: Issue persists even with fix

Note: Earlier entries from Week 34 (Aug 19-25) have been archived.

Test Configurations

Standard Local Test

cd ~/code/freenet/freenet-testing-tools/gateway-testing
python gateway_test_framework.py --local

Remote Gateway Test

python gateway_test_framework.py --remote-gateway [gateway-host]

River Stress Test

python gateway_test_framework.py --local --multi-room 50

Confirmed Working

  • ✅ Ping app with remote gateways
  • ✅ Basic PUT/GET/SUBSCRIBE operations
  • ✅ River with pre-existing rooms (direct subscription)
  • ✅ River full flow with local gateway

Confirmed Failing

  • ❌ River room creation → invite → join with remote gateway
  • ❌ Multiple River users on same peer (configuration not recommended)

Environment Details

Test Machines:

  • Local: Development machine
  • AWS Gateway: EC2 instance (discontinued due to suspected UDP issues)
  • Nova Gateway: nova.locut.us (current primary test gateway)

Ports:

  • Originally: 31337 (potentially problematic)
  • Current: Various alternatives tested

Software Versions:

  • Freenet Core: v0.1.21+
  • River: v0.1.x (latest with subscribe fix)

Related Links

Clone this wiki locally