Here are the commands used. ### 1. Find the mobile hotspot IP and route Show the default gateway—the hotspot/router IP: ```bash ip route | grep default ``` Example: ```text default via 10.128.97.214 dev wlo1 ``` Show the Wi-Fi interface address: ```bash ip addr show wlo1 ``` Or: ```bash ip addr | grep wlo1 ``` Show gateway and DNS information: ```bash nmcli device show | grep -E 'IP4.GATEWAY|IP4.DNS' ``` Check the active DNS configuration: ```bash resolvectl status ``` Check the current routing table: ```bash ip route ``` Check whether the Geph tunnel exists: ```bash ip link show geph-tun ip route show dev geph-tun ``` ### 2. Set the official Flatpak remote and update it List Flatpak remotes: ```bash sudo flatpak remotes --show-details ``` Set the `flathub` remote to the official repository: ```bash sudo flatpak remote-modify flathub \ --url=https://dl.flathub.org/repo/ ``` If a duplicate remote named `flathub-1` exists, remove it: ```bash sudo flatpak remote-delete flathub-1 ``` Confirm the result: ```bash sudo flatpak remotes --show-details ``` Update Flathub AppStream metadata through the local proxy: ```bash sudo env \ http_proxy=http://10.128.97.214:9910 \ https_proxy=http://10.128.97.214:9910 \ HTTP_PROXY=http://10.128.97.214:9910 \ HTTPS_PROXY=http://10.128.97.214:9910 \ flatpak update --appstream ``` When the laptop is no longer using the phone hotspot and Geph is listening locally, use: ```bash sudo env \ http_proxy=http://127.0.0.1:9910 \ https_proxy=http://127.0.0.1:9910 \ HTTP_PROXY=http://127.0.0.1:9910 \ HTTPS_PROXY=http://127.0.0.1:9910 \ flatpak update --appstream ``` ### 3. Install the local Flatpak bundle through the proxy Using the phone-side/proxy address: ```bash sudo env \ http_proxy=http://10.128.97.214:9910 \ https_proxy=http://10.128.97.214:9910 \ HTTP_PROXY=http://10.128.97.214:9910 \ HTTPS_PROXY=http://10.128.97.214:9910 \ flatpak install ./Geph-x86_64sep.flatpak ``` Using the laptop’s current local Geph proxy: ```bash sudo env \ http_proxy=http://127.0.0.1:9910 \ https_proxy=http://127.0.0.1:9910 \ HTTP_PROXY=http://127.0.0.1:9910 \ HTTPS_PROXY=http://127.0.0.1:9910 \ flatpak install ./Geph-x86_64sep.flatpak ``` Verify the installed version and runtime: ```bash flatpak info io.geph.GephGui ``` Launch it: ```bash flatpak run io.geph.GephGui ``` Test the local Geph proxy: ```bash curl --noproxy '' \ --proxy http://127.0.0.1:9910 \ -I --connect-timeout 15 \ https://example.com ``` Check the proxy listener: ```bash ss -ltnp | grep 9910 ``` Your current result indicates that Chromium and Brave are probably not configured to use `127.0.0.1:9910`, or they are bypassing the proxy because they use system settings differently from Firefox. Keep Firefox working as a fallback while checking their proxy settings. # 2026 10 04 0733am hi how to put all networking to proxy 10.128.97.214:9910, which is current hotspot. The right method depends on the proxy type (HTTP or SOCKS5) and on how much you want covered. Three levels: 1. Shell and CLI tools (env vars) export http_proxy=http://10.128.97.214:9910 export https_proxy=http://10.128.97.214:9910 export all_proxy=http://10.128.97.214:9910 # or socks5://... if it's SOCKS export no_proxy=localhost,127.0.0.1,10.0.0.0/8 This covers curl, pip, git, apt (apt also needs Acquire::http::Proxy in /etc/apt/apt.conf.d/) and Claude Code. It only covers apps that honor these variables. 2. Desktop system proxy (GNOME) gsettings set org.gnome.system.proxy mode 'manual' gsettings set org.gnome.system.proxy.http host '10.128.97.214' gsettings set org.gnome.system.proxy.http port 9910 gsettings set org.gnome.system.proxy.https host '10.128.97.214' gsettings set org.gnome.system.proxy.https port 9910 This covers browsers and GTK apps. To undo it, run gsettings set org.gnome.system.proxy mode 'none'. 3. Everything, including apps that ignore proxies (transparent) Use tun2socks, which creates a TUN device and routes all traffic through the proxy. It supports both HTTP and SOCKS5. sudo ip tuntap add dev tun0 mode tun sudo ip addr add 198.18.0.1/15 dev tun0 sudo ip link set tun0 up sudo tun2socks -device tun0 -proxy http://10.128.97.214:9910 # or socks5:// # keep the proxy itself off the tunnel, then send the rest through tun0 sudo ip route add 10.128.97.214 via dev sudo ip route add default dev tun0 metric 1 Two caveats: - Plain HTTP proxies can't carry UDP or DNS. For DNS you'd need a SOCKS5 proxy with UDP support, or a local resolver. - Don't route the proxy's own traffic through the tunnel. That's what the explicit route to 10.128.97.214 is for. If you only need one program covered, proxychains4 is simpler. Is the proxy HTTP or SOCKS5? Do you want the browser covered, or really every app? With that I can give you exact commands. http proxy 10.128.97.214:9910 , socks5 10.128.97.214:9910 , The option 3 is good, tun2socks But the network just connected, let's wait a while to apply tun2socks. so, for now, use the laptop network as it untill i hit new conditions. By the way, could we plan a backup solution over host lightsail.a ? command line options are my preferred solution.