top | item 24779465 (no title) armon | 5 years ago That is correct! The local proxy has a listening socket and handles all the authentication, encapsulation, and forwarding transparently. discuss order hn newest parliament32|5 years ago So does it intercept all connections on that port (from the client app) and pass them along? Or do I need to reconfigure my client application to talk to localhost:whatever? Your only example is that curl using a hostname, it's not really clear. armon|5 years ago You would point the application at the local port. It operates very similarly to SSH port forwarding. No fancy magic to intercept all traffic. load replies (1) zokier|5 years ago I started thinking, using network namespaces to intercept traffic from client applications would be pretty neat trick.
parliament32|5 years ago So does it intercept all connections on that port (from the client app) and pass them along? Or do I need to reconfigure my client application to talk to localhost:whatever? Your only example is that curl using a hostname, it's not really clear. armon|5 years ago You would point the application at the local port. It operates very similarly to SSH port forwarding. No fancy magic to intercept all traffic. load replies (1)
armon|5 years ago You would point the application at the local port. It operates very similarly to SSH port forwarding. No fancy magic to intercept all traffic. load replies (1)
zokier|5 years ago I started thinking, using network namespaces to intercept traffic from client applications would be pretty neat trick.
parliament32|5 years ago
armon|5 years ago
zokier|5 years ago