Conversation

Notices

1.  (mint@ryona.agency)'s status on Wednesday, 29-Jan-2025 04:37:30 JST 
   Apparently https://github.com/pufferffish/wireproxy is a thing so I didn't need to fuck around with Wireguard and dante-sockd in LXC containers.
   • † top dog :pedomustdie: likes this.
   • di (di@fsebugoutzone.org)'s status on Wednesday, 29-Jan-2025 05:33:37 JST di

     in reply to
     @mint
     
     Nice, what's your use case, was it to route a specific application running inside a container through a wg tunnel? And you used a dante socks proxy on the remote end that was probably limited through iptables to only accept connections from the wg interface.
     
     Lately I've been setting up a mobile phone farm infrastructure just in case. I'm testing it using the latest tools and planning on live testing it trying to scrape linkedin.
     Concept is to transparently route the phone connections through one or more proxies. I'm using redsocks, iptables and dante (to simulate paid proxies).
      and † top dog :pedomustdie: like this.
   •  (mint@ryona.agency)'s status on Wednesday, 29-Jan-2025 05:35:36 JST 

     in reply to

     • di
     @di No iptables, the container just has wireguard as its main interface and runs sockd that gets exposed on host as a SOCKS proxy to use in browsers and whatnot.
     † top dog :pedomustdie: likes this.