adobe / adobe/frl-online-proxy
FRL Proxy stops listening if the machine's IP address changes
- Dominant language
- Rust
- Stars
- 6
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
**Description**
If you start the FRL proxy on a machine with a dynamically assigned IP address, and the machine is then reconfigured to have a different IP address at the next refresh, then the FRL proxy will stop responding to incoming connections but will not show any errors in the log.
**Steps to reproduce**
* Be on a machine that gets its IP address via DHCP
* Configure frl-proxy to listen on 0.0.0.0
* Start it from the command line as a regular user
* Have the DHCP server assign a different address to the machine while the proxy is running.
**Observed behavior**
The proxy stops responding to requests, whether they are directed to the old or new IP address of the machine.
**Expected behavior**
The proxy should respond to requests sent to the new IP address of the machine.
**Environment**
- frl-proxy version: 1.2
- OS type and version: Windows 10
- Any other relevant info: haven't tried reproducing on Mac
Contributor guide
Research direction
Start the frl-proxy command-line entry point and reproduce the issue on Windows 10 with DHCP while listening on 0.0.0.0. Trace the listener lifecycle across an address change and verify that requests to the new IP receive responses and that failures are visible in the log.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100