SQUID + several external IPs + user identification. How to make it work together?

Question

Squid

Good day.
The essence of the problem is as follows: there is a server with several external IPs. I want to make a proxy server out of it, with a limited number of users, and at the same time, so that each user has his own external IP for accessing the Internet.
I want to use all this stuff further through HttpWebRequest in a C # application.
For this task, I chose SQUID, as it seems like the most obvious solution. But, as I did not suffer with the configuration file, I could not get everything to work correctly.
Here is my config:
# Here I say where my logins and passwords are
# Login / password of the form: user1 / xxx , user2 / yyy
auth_param basic program /usr/lib64/squid/ncsa_auth /etc/squid/internet_users
#
# Recommended minimum configuration:
#
acl manager proto cache_object
acl localhost src 127.0.0.1/32 ::1
acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1
# Example rule allowing access from your local networks.
# Adapt to list your (internal) IP networks from where browsing
# should be allowed
acl localnet src 10.0.0.0/8 # RFC1918 possible internal network
acl localnet src 172.16.0.0/12 # RFC1918 possible internal network
acl localnet src 192.168.0.0/ 16 # RFC1918 possible internal network
acl localnet src fc00::/7 # RFC 4193 local private network range
acl localnet src fe80::/10 # RFC 4291 link-local (directly plugged) machines
acl SSL_ports port 443
acl Safe_ports port 80 # http
acl Safe_ports port 21 # ftp
acl Safe_ports port 443 # https
acl Safe_ports port 70 # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 1025-65535 # unregistered ports
acl Safe_ports port 280 # http-mgmt
acl Safe_ports port 488 # gss-http
acl Safe_ports port 591 # filemaker
acl Safe_ports port 777 # multiling http
acl CONNECT method CONNECT #The
next 6 lines are also mine. Here I think that I create two access sheets and open my external ip
acl user1acl proxy_auth user1
acl user2acl proxy_auth user2
tcp_outgoing_address 193.124.xx.zz user1acl
tcp_outgoing_address 193.124.yyy.vvv user2acl
acl ncsa_users proxy_auth REQUIRED
http_access allow ncsa_users
#
# Recommended minimum Access Permission configuration:
#
# Only allow cachemgr access from localhost
http_access allow manager localhost
http_access deny manager
# Deny requests to certain unsafe ports
http_access deny !Safe_ports
# Deny CONNECT to other than secure SSL ports
http_access deny CONNECT !SSL_ports
# We strongly recommend the following be uncommented to protect innocent
# web applications running on the proxy server who think the only
# one who can access services on "localhost" is a local user
#http_access deny to_localhost
#
# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
#
# Example rule allowing access from your local networks.
# Adapt localnet in the ACL section to list your (internal) IP networks
# from where browsing should be allowed
http_access allow localnet
http_access allow localhost
# And finally deny all other access to this proxy
http_access deny all
# Squid normally listens to port 3128
http_port 3128
# We recommend you to use at least the following line.
hierarchy_stoplist cgi-bin ?
# Uncomment and adjust the following to add a disk cache directory.
#cache_dir ufs /var/spool/squid 100 16 256
# Leave coredumps in the first cache dir
coredump_dir /var/spool/squid
# Add any of your own refresh_pattern entries above these.
refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
refresh_pattern . 0 20% 4320
But this config (and its variations) don't work. If I log in as user1, and then as user2, I will be redirected to the same external ip for the first and second time (and it happens in different ways, then the first one is used). But always one at a time. Moreover, the behavior is non-deterministic.
It looks like some setting from the config is ignored or written incorrectly. There are only 7 of my lines in the config - the first and 6 in the middle.
Please indicate where I do not see a beam in the eye here? I rummaged through a bunch of forums and config options - I could not achieve the required behavior.
Thank you.

Answer 1

Hello. Did you find a solution to the issue. A similar task is worth it, too, everything goes through one IP