Bind does not seem to work

未關閉
#571 0 則留言 2 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
35/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
停滯
技術堆疊
c
領域
networking

研究方向

Start by reading the implementation and documentation for the Bind setting to establish whether it binds the proxy's outgoing connection or routes traffic through an interface. Then trace how outgoing connections choose their local address and consult the relevant networking tests. Done means clarifying the expected behavior and, if it is a software defect, demonstrating that proxy traffic uses the requested interface without changing the server's general routing.

由索引模型根據 Issue 內容生成。

描述

I have a ppp interface ppp1 created by the following command:

pppd pty "pptp 1.2.3.4 --nolaunchpppd" user vpnuser password vpnpassword lock noauth nobsdcomp nodeflate nodetach

It is verified to work. My tinyproxy config:

Port 8888
Listen 70.80.90.100 #public ip of my server
Timeout 600
bind 10.0.77.11 #inet addr of ppp1 interface

The proxy starts, however when I use it to connect the remote client (e.g. web browser) I get the public IP of my server (70.80.90.100) which isn't what I expect (it would be expected to receive 1.2.3.4 (PPTP VPN server IP address) as the public IP).
Am I missing anything or is this a software error? I assumed the bind to interface feature would allow to route traffic from proxy clients through the specified interface without routing all traffic of the server through that interface (ppp1 in the example).

主要語言
C
星號
6.1k
分支
768
平均合併
15 天 3 小時
30 天內合併 PR
1

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

tinyproxy/tinyproxy 的其他 Issue

查看 tinyproxy/tinyproxy 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。