On 4/30/25 11:47 PM, Dan Ritter wrote:
My program on :7777 is socks5 and ssh tunnel.Mohsen Pahlevanzadeh wrote:On 4/30/25 4:29 PM, Jonathan Dowland wrote:On Wed Apr 30, 2025 at 10:19 AM BST, Mohsen Pahlevanzadeh wrote: I want to send any packet to 127.0.0.1:7777 and it sends my packets to internet. my outgoing interface is eth0. You can use socat¹ to listen on a port and forward received packets elsewhere. But… I don't want to use set proxy in firefox and other application, but I want to send any packets to 127.0.0.1:7777 and my program itself send to eth0. But to what address on the Internet do you wish the packets to go? I don't want to send one type packet and one destination. any packet and any destination.When packets are released from 127.0.0.1:7777 , this should be sent anywhere.OK, there is an underlying assumption that you are not telling us. Why do you want to do this? What is the program at :7777 going to accomplish differently from connecting sockets to the actual remote IP addresses? -dsr- |
- route all traffic to a internal socket Mohsen Pahlevanzadeh
- Re: route all traffic to a internal socket Nicolas George
- Re: route all traffic to a internal socket Mohsen Pahlevanzadeh
- Re: route all traffic to a internal socket Jonathan Dowland
- Re: route all traffic to a internal socket Mohsen Pahlevanzadeh
- Re: route all traffic to a internal sock... Tim Woodall
- Re: route all traffic to a internal ... Tim Woodall
- Re: route all traffic to a internal socket Mohsen Pahlevanzadeh
- Re: route all traffic to a internal sock... Dan Ritter
- Re: route all traffic to a internal ... Mohsen Pahlevanzadeh
- Re: route all traffic to a inte... Dan Ritter