[Ubuntu]version 0.99.1 - wrong ip adress

[cwgmacedo]

Swproxy gets the wrong ip adress on ubuntu, on GUI and non GUI version

SWParser v0.99 - Summoners War Proxy

...

Running Proxy server at 0.0.74.79 on port 8080

here's my best guess for a way to fix this, it works for OSX, but requires netifaces module

ip = ip4_addresses()[0]

from netifaces import interfaces, ifaddresses, AF_INET

def ip4_addresses():
    ip_list = []
    for interface in interfaces():
        try:
            for link in ifaddresses(interface)[AF_INET]:
                ip_list.append(link['addr'])
        except KeyError:
            continue
    if '127.0.0.1' in ip_list:
        ip_list.remove('127.0.0.1')
    return ip_list


# returns a list, first address is likely the correct one
print ip4_addresses()

[fperegrinvs]

not sure if we will have the same problem. Maybe we can allow user to
select the correct ip (dropbox for gui , list all valid ips on console)

On Mon, Mar 28, 2016 at 3:19 PM, Alex notifications@github.com wrote:

here's my best guess for a way to fix this, it works for OSX, but requires
netifaces module

ip = ip4_addresses()[0]

from netifaces import interfaces, ifaddresses, AF_INET

def ip4_addresses():
ip_list = []
for interface in interfaces():
try:
for link in ifaddresses(interface)[AF_INET]:
ip_list.append(link['addr'])
except KeyError:
continue
if '127.0.0.1' in ip_list:
ip_list.remove('127.0.0.1')
return ip_list

returns a list, first address is likely the correct one

print ip4_addresses()

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#64 (comment)

we could implement a flag really quick (--ipguess2) or something to enable the above code (instead of current ip detection); then we could ask users to run it with this flag and see if the first ip works out of the box, we'd need to test linux and windows certainly.

This seems like the best xplatform code, I do like your idea of the dropdown (maybe GUI-less just picks the first one)

[fperegrinvs]

relevant info "You comment made me double check. It's not trying to use 127.0.0.1 which is blocked in the code, It's trying to open the proxy on 127.0.1.1
no clue where its getting that address from. Loopback is 127.0.0.1"

[kakaroto]

This is being discussed in #38 and it's been fixed already, so expect it to work on the next release.

[kakaroto]

FYI: when I tried the app during FRR day, it gave me 127.0.0.1 (weird since 127.* should be filtered out), so I updated my local git and then it worked properly.