Can't bind to public ip address

[p1ratrulezzz]

Can't bind to public ip address

[p1ratrulezzz]

Solved. Just commented out the line with

ipv4=0;

on https://github.com/TelegramMessenger/MTProxy/blob/master/engine/engine.c line 230

if ((ipv4 >> 24) != 10) {
      kprintf ("Bad binded IP address " IP_PRINT_STR ", search in ifconfig\n", IP_TO_PRINT (ipv4));
      kprintf("But I dont care about it...");
      //ipv4 = 0;
    } 

Server started and serving connections now. So looks like there is some issue with ipv4 check

[JaminZhou]

./mtproto-proxy -u nobody -p 8888 -H 443 -S <secret> --nat-info <intranet ip>:<public ip> --aes-pwd proxy-secret proxy-multi.conf -M 1

--nat-info <intranet ip>:<public ip> add this will work

[stek29]

It probably should’ve been == 10, since 10.0.0.0/8 is a private network.
However, rfc1918 specifies two more subnets for private networks which are not handled.

get_my_ipv4 also only skips 10.0.0.0/8 and loopback

MTProxy/net/net-events.c

Line 737 in cc7b709

unsigned get_my_ipv4 (void) {

[LDVSOFT]

Agree, cannot bind to public ip.

[p1ratrulezzz]

Just disable this ip address check on line 230 as i mentioned in comment 2 (temporary, until developer fixes it)

[zvpdev]

Same issue.
Change from ipv4 = 0; to //ipv4 = 0; doesn't help me, stay binding to local ip.

[p1ratrulezzz]

@zvpdev forcely bind to public address by passing

--address 11.22.33.44

[p1ratrulezzz]

Also bug label needed for this, as it determines correct ip addresses as incorrect.

UPD: workaround for this is

--nat-info 127.0.0.1:11.22.33.44

where 11.22.33.44 - your public ip

[p1ratrulezzz]

I'm really not sure what does this check do but as @stek29 noticed it checks only networks like 10.10... But rfc has two more ranges so I've added them too. Binding to external ip actually work so if it is needed it can be easily changed.

[liquidpredator]

Same issue.
Change from ipv4 = 0; to //ipv4 = 0 and use --address
binding to local ip anyway...

UPD
It works when I delete -d option...
but get same issue #34

[p1ratrulezzz]

@liquidpredator try cloning my fork of this proxy. you should use --address ur.if.ip.adr for example --address 8.8.8.8 (check interface's ip address in ifconfig)

[savely-krasovsky]

@p1ratrulezzz after last update with padding support seems like it broken again. Is there new workaround?

[p1ratrulezzz]

Yes, i also noticed this. I'm using my fork with older version, it works for me so don't see any reason to upgrade вт, 10 июл. 2018 г., 22:39 Savely Krasovsky <[email protected]>:

…

@p1ratrulezzz <https://github.com/p1ratrulezzz> after last update with padding support seems like it broken again. Is there new workaround? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEyYFbgSWC-Mbuwbx4R8SANj0Z0FlNXgks5uFQMFgaJpZM4UToEc> .

[savely-krasovsky]

@p1ratrulezzz I heard Rostelecom already testing DPI blocking by packet size. So considered to update and stuck...