So as I have gotten the proxy issued fixed, I can now see people's shares, most of the time.
I used ssh to listen on a local port then using localhost and that port to be the socks5 proxy for airdc.
Then I set up some port forwarding rules so the 3 ports that are used, 2 tcp and 1 udp will also be forwarded to that local proxy port.
And now I can download most people's file lists normally.
I have experienced with some that could be viewed on one hub, while the same one cannot be viewed in another.
There are also cases where in both hubs I cannot download a person's list.
I have no idea as to why that is at this point, and there isn't much resource online for airdc is largely a private thing.
Can the devs shred some light on what I could change or do / what is the problem here?
It seems like that me being on a proxy will make an active connection impossible. Is that correct?
AirDC++w 2.11.0 x86_64
2.11.0
Arch linux installed with pacman
Hello dev!
So as I have gotten the proxy issued fixed, I can now see people's shares, most of the time.
I used ssh to listen on a local port then using
localhost
and that port to be the socks5 proxy for airdc. Then I set up some port forwarding rules so the 3 ports that are used, 2 tcp and 1 udp will also be forwarded to that local proxy port.And now I can download most people's file lists normally.
I have experienced with some that could be viewed on one hub, while the same one cannot be viewed in another.
There are also cases where in both hubs I cannot download a person's list.
I have no idea as to why that is at this point, and there isn't much resource online for airdc is largely a private thing.
Can the devs shred some light on what I could change or do / what is the problem here?
It seems like that me being on a proxy will make an active connection impossible. Is that correct?