ARM compile

tried it worked but i get stuck on connected for some reason

good to know it builds! :)

it's probably some configuration issue; i suggest you double-check. in particular, check for ADC vs NMDC. using a client that shows messages being received & sent (eg DC++ with the dev plugin) could help investigating.

# Configuration file for DCBouncer <https://launchpad.net/dcbouncer>.

# Address (IP or domain name) of a client authorized to connect. Add multiple "AUTHORIZED=..."
# lines to specify multiple authorized addresses. If no authorized address is defined, anyone can
# connect.
AUTHORIZED=xxx.xxx.x.xxx

# Certificate file containing a private key and a server certificate, to be used for secure
# connections. Linux servers often have one such file at "/etc/httpd/conf/httpd.pem".
# If no file is specified, DCBouncer will generate one and store it at "../var/DCBouncer/cert.pem".
CERT_FILE=../var/DCBouncer/cert.pem

# Define one set of options for each hub you want to proxy. See the "README" file for information.
# Each profile must end with "OK".
# Note that the following are the only mandatory options; more are available.

LISTENING_PORT=7070
HUB_ADDRESS=xxxx.xxx.xx
HUB_PORT=xxxx
PASS=xxxx
OK

is that correct for the config file

and from the client i should i adc://xxxxx.xxx:xxxx

x being the value although redacted :P

that seems ok... assuming you are connecting to <adc://example.com:5200>, here are a few things to check:
- ensure the 5200 port is open on the rpi;
- try with "adcs" instead of "adc" (DCBouncer should auto-detect but just in case);
- delete the cache directory (../var/DCBouncer/data);
- remove the "AUTHORIZED" line;
- from the rpi, ping the hub (to ensure it can access it);
- run the client with some diagnostics to see whether DCBouncer sends anything back.

good luck!