[bug] [0.3.0] downloads freezes in "connecting" state

[SMT 0]

when i just connect to hub (in active mode), all downloads freezes in "connecting" state, but uploads works.

does anybody seen this bug? if it's annoying, i can tell quick solution or explain why it happens

[Crise 26]

Cannot seem to be able to reproduce...

[SMT 0]

Cannot seem to be able to reproduce...

well.. suppose you are always using 'direct connection' and get ip on DHCP (ADSL)

goto 'connection settings', press 'Get IP Address'

reconnect to provider again, so you'll get another IP

that's all, apex can't download anything

the problem is in Client::getLocalIp()

function returns 'external ip' even if 'direct connection' selected. i think, 'external ip' should be used only in 'firewall with manual port forwarding' mode

so curious users, who tested 'get ip' button suffer for their curiosity :-)

[Crise 26]

well.. suppose you are always using 'direct connection' and get ip on DHCP (ADSL)

goto 'connection settings', press 'Get IP Address'

reconnect to provider again, so you'll get another IP

that's all, apex can't download anything

the problem is in Client::getLocalIp()

function returns 'external ip' even if 'direct connection' selected. i think, 'external ip' should be used only in 'firewall with manual port forwarding' mode

so curious users, who tested 'get ip' button suffer for their curiosity :-)

Get ip button doesn't even use Client::getLocalIp(), unless it has to (which shouldn't happen too often)

[SMT 0]

Get ip button doesn't even use Client::getLocalIp(), unless it has to (which shouldn't happen too often)

it fills 'external WAN/IP' field, that returned by Client::getLocalIp()

just try - fill 'external WAN/IP' with some garbage, like 64.233.187.99, set direct connection (so, this field should not be used) and try to download something

i've recently recieved one more complain about this issue, so it's very actual

[Big Muscle 1]

IP address in "External WAN/IP" field is used only when the check "Don't allow override IP" is checked, else it uses IP address which has been used for connecting to hub.

[SMT 0]

IP address in "External WAN/IP" field is used only when the check "Don't allow override IP" is checked, else it uses IP address which has been used for connecting to hub.

same problem applies to hub options too. when using 'direct connection' in hub options, 'External IP' is also used, but it should not