Client-side setup
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 12.4k
- Forks
- 510
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I am trying to setup a proxy client-side to test a mobile application's behavior. The setup would be like this:
mobile ---[wifi]--- AP --- Toxiproxy ---[internet]--- servers
Toxiproxy is on a Windows PC with 2 ethernet cards. I would like to test how the mobile reacts when connectivity is bad; for example, when browsing with HTTP.
I can't seem to find how to create a proxy that catches streams regardless of destination IP. For example, I can set 192.168.1.100:80 to be forwarded to 172.217.13.196:80 (google), but I can't seem to have a request to 172.217.13.196:80 be handled by Toxiproxy and go through to Google.
The latest try I did was this:
toxiproxy-cli create http_out -l :80 -u :80
The toxiproxy server sees the connections, but the mobile gets nothing back and Wireshark gives me the impression that the internet-facing ethernet card is not implicated.
How is this done with the cli interface?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by checking the documented toxiproxy-cli create syntax and the proxy listener/upstream behavior described in the issue. Done means determining whether destination-independent client-side forwarding is supported for the stated Windows two-interface setup, or documenting the configuration or limitation found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100