mrambossekandClaude Fable 5
ce1aaa332a
fmr binds two IPv4 addresses. connFor picked whichever socket of the right family came first in the bind list, so a downtrain for a session established on .150 went out from .151 — and every packet was dropped by the client's NAT, which has no mapping for that pair. tcpdump on the server showed all 50 leaving; the client saw none. Read as "100% downstream loss", which is the worst kind of wrong: a confident measurement of something that never happened. Sessions now record which of our own bound addresses received their traffic, and granted sends (and delayed echo) go back out through that socket. The fallback to a family match is kept for the case where nothing has been received yet, and the test pins both paths — a single-homed lab can never reproduce this. Also: the client-side halves of the same work — anonymizer (core-privacy), local run archive with retention (core-archive), upload client, and the app's settings and history screens. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
33 lines
830 B
Kotlin
33 lines
830 B
Kotlin
// SPDX-FileCopyrightText: 2026 Echolot contributors
|
|
// SPDX-License-Identifier: GPL-3.0-or-later
|
|
|
|
pluginManagement {
|
|
repositories {
|
|
google()
|
|
mavenCentral()
|
|
gradlePluginPortal()
|
|
}
|
|
}
|
|
dependencyResolutionManagement {
|
|
repositories {
|
|
google()
|
|
mavenCentral()
|
|
}
|
|
}
|
|
|
|
rootProject.name = "echolot-app"
|
|
|
|
// core-protocol is a pure Kotlin/JVM module (the client side of
|
|
// probe-protocol.md) so it builds and unit-tests without the Android SDK and
|
|
// can run integration tests against a live server. Android modules
|
|
// (core-probe, core-shizuku, app) join as they land.
|
|
include(":core-protocol")
|
|
include(":core-measurement")
|
|
include(":core-engine")
|
|
include(":core-privacy")
|
|
include(":core-archive")
|
|
include(":core-probe")
|
|
include(":core-shizuku")
|
|
include(":app")
|
|
include(":adb-beacon")
|