IPv6 Only Proxy

[vanitysys28]

I'm playing with 3proxy at the moment and whatever I do, I don't manage to make an IPv6 only proxy.

Here is my config file

daemon
pidfile /home/joke/proxy/3proxy.pid
nserver 2001:4860:4860:0:0:0:0:8888
nserver 2001:4860:4860:0:0:0:0:8844
nscache6 65536
users tester:CL:1234
timeouts 1 5 30 60 180 1800 16 60
log /home/joke/proxy/logs/3proxy.log D
logformat "- +_L%t.%. %N.%p %E %U %C:%c %R:%r %O %I %h %T"
rotate 3
auth none
flush
allow tester
socks -p3128
proxy -6 -n -a -p8080 -i157.245.82.149 -e2604:a880:400:d0::1765:1

I manage to connect to the proxy all good, but the displayed IP on IP checking website is always the IPv4 IP.

[z3APA3A]

what do you have in logs?

[z3APA3A]

It's unrelated, but read this doc, or it will be your next question

https://3proxy.ru/faqe.asp

Q: Why restrictions (redirections, limits, etc) do not work?
A: Most probable reasons: 'auth none' or no auth is used. For any ACL based feature one of 'iponly', 'nbname' or 'strong' auths required. Sequence of commands may be invalid. Commands are executed one-by-one and 'proxy', 'tcppm', 'socks' or another service commands must follow valid configuration. Invalid sequence of ACLs. First matching ACL is used (except of internal redirections, see below). If ACL contains at least one records last record is assumed to be 'deny *'.

[vanitysys28]

Decided to stop trying to do it through docker as enabling IPv6 on docker-compose is quite hard with new version. Installed it on bare metal, directly on a test server without docker.

Ping6 works in the server, but for some reason, I can't reach a website after trying to connect to proxy. Here is ifconfig, log and 3proxy.cfg

[z3APA3A]

what do you have in logs?

[z3APA3A]

P.S. browsers do not support username/password authentication for SOCKS, use 'proxy'.

[vanitysys28]

This is the only line I have in my logs
1586850869. L1586850869.526 PROXY.1080 00000 - 161.35.9.91:1080 2604:a880:400:d0::191f:7001:0 0 0 0 Accepting connections [20155/2939959040]

[z3APA3A]

It means proxy ip:port was not available to client. Check firewalls and network issues.

[vanitysys28]

Firewall is disabled and I'm able to ping6 google.com
No idea where it might come from.
Any idea what file I need to have a look to?

[z3APA3A]

Try to telnet/nc to
161.35.9.91:1080
from local host and remote host. If it's accessible from local host and not accessible from remote host it's definitely network or firewall issue.

[vanitysys28]

Fixed the issue.
Had to add an IPv4 nserver in my config.
Thanks for your help

[z3APA3A]

address for IPv6 nameserver must be in [], because 3proxy allows to specify port is addition to address, 2001:4860:4860::8888 is eqivalent to [2001:4860:4860:]:8888, while you probably mean [2001:4860:4860:0:0:0:0:8888].
But for this case you should have an error with 00100 code in logs. The problem you can not reach the proxy port is either unrelated or 3proxy was not running due to configuration eror

[andersonpfx]

Does the 3proxy.cfg file have any character limits?
I generated 3 thousand proxies and I restarted 3proxy, the same operating normally but all proxies without connection, when I reduced the amount removing some lines, and I restarted it came back to connect.

So my doubt is, how many proxies can I put in 3proxy.cfg?

[z3APA3A]

there is no limit for the number of lines in the config, probably you have sdome over limitation, e.g. open descriptors, see
https://3proxy.ru/highload.asp