|Eliezer Croitoru 2c15aa34ab Replaced the logic of when the tcp and sctp connections are closed to the original one.||2 weeks ago|
|sctp-to-tcp||2 weeks ago|
|systemd-service-files||2 weeks ago|
|tcp-to-sctp||2 weeks ago|
|LICENSE||1 month ago|
|README.md||1 month ago|
|build.sh||1 month ago|
|install.sh||1 month ago|
Since Squid-Cache doesn't have any support for SCTP socket, even a non stream based one I wrote these two proxy servers. The original goal was to write a fully featured SCTP proxies. These ideally should utilize the full capacity of SCTP which is to be able to communicate between two hosts (client and server) while shifting between src and destination IP addresses due to load balancing or failure of one or more routes on the path between the hosts.
Since the Squid-Cache project didn't got enough support these tools are a begining of something.
Listens on TCP port like on the loopback(127.0.0.1) of a client with the browser pointed to it and the remote SCTP server ipv4+port are configured as a peer. Every new TCP connection is being proxied over SCTP to the remote ipv4+port.
Listens on a SCTP ipv4+port (only a single one) and proxies every incomming connection to a local or remote server TCP ipv4+port service. The service is able to write a PROXY protocol header V1(only if is bound to one external IPv4 address and not loopback or all interfaces) which Squid-Cache support and there for will be able to enforce static or dynamic(external_acl, ICAP, other) source IP based acl's.