127.0.53.53 Help with network

[maxim.dogonov]

Hello!

I have problem with my Proxmox server, OpenVZ VM.
Version PROXMOX 3.2-1/1933730b

I set up external IP on my VM

root@alfatell:~# vzlist
CTID NPROC STATUS IP_ADDR HOSTNAME
109 73 running 217.23.86.148 voip.prod


But when app inside VM try connect to external resources for example sip registration, all traffic go to lo interface and all connections nated with address 127.0.53.53.
I don't need nat with adress 127.0.53.53. How I can fix that?

root@alfatell:~# vzctl enter 109
entered into CT 109
[root@voip /]# tcpdump -i lo -n
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on lo, link-type EN10MB (Ethernet), capture size 65535 bytes
13:10:08.291244 IP 127.0.0.1.37205 > 127.0.0.1.agentx: Flags , seq 205119582, win 32792, options [mss 16396,sackOK,TS val 224785158 ecr 0,nop,wscale 7], length 0
13:10:08.291258 IP 127.0.0.1.agentx > 127.0.0.1.37205: Flags [R.], seq 0, ack 205119583, win 0, length 0
13:10:16.536140 IP 127.0.0.1.35932 > 127.0.0.1.5038: Flags , seq 3536973848, win 32792, options [mss 16396,sackOK,TS val 224793402 ecr 0,nop,wscale 7], length 0
13:10:16.536153 IP 127.0.0.1.5038 > 127.0.0.1.35932: Flags [S.], seq 1690861501, ack 3536973849, win 32768, options [mss 16396,sackOK,TS val 224793402 ecr 224793402,nop,wscale 7], length 0
13:10:16.536160 IP 127.0.0.1.35932 > 127.0.0.1.5038: Flags [.], ack 1, win 257, options [nop,nop,TS val 224793402 ecr 224793402], length 0
13:10:16.536233 IP 127.0.0.1.35932 > 127.0.0.1.5038: Flags [F.], seq 1, ack 1, win 257, options [nop,nop,TS val 224793403 ecr 224793402], length 0
13:10:16.536306 IP 127.0.0.1.5038 > 127.0.0.1.35932: Flags [.], ack 2, win 256, options [nop,nop,TS val 224793403 ecr 224793403], length 0
13:10:16.536421 IP 127.0.0.1.5038 > 127.0.0.1.35932: Flags [P.], seq 1:28, ack 2, win 256, options [nop,nop,TS val 224793403 ecr 224793403], length 27
13:10:16.536446 IP 127.0.0.1.35932 > 127.0.0.1.5038: Flags [R], seq 3536973850, win 0, length 0
13:10:19.021754 IP 127.0.53.53.sip > 127.0.53.53.sip: SIP, length: 517
13:10:19.021777 IP 127.0.53.53.sip > 127.0.53.53.sip: SIP, length: 3
13:10:19.021834 IP 127.0.53.53.sip > 127.0.53.53.sip: SIP, length: 464
13:10:23.306396 IP 127.0.0.1.37208 > 127.0.0.1.agentx: Flags , seq 775776305, win 32792, options [mss 16396,sackOK,TS val 224800173 ecr 0,nop,wscale 7], length 0
13:10:23.306422 IP 127.0.0.1.agentx > 127.0.0.1.37208: Flags [R.], seq 0, ack 775776306, win 0, length 0
^C
14 packets captured
28 packets received by filter


Thank you!

 

[Mr.Holmes]

Hello maxim.dogonov

But when app inside VM try connect to external resources for example sip registration, all traffic go to lo interface and all connections nated with address 127.0.53.53.
I don't need nat with adress 127.0.53.53. How I can fix that?

root@alfatell:~# vzctl enter 109
entered into CT 109
[root@voip /]# tcpdump -i lo -n
13:10:19.021777 IP 127.0.53.53.sip > 127.0.53.53.sip: SIP, length: 3
13:10:19.021834 IP 127.0.53.53.sip > 127.0.53.53.sip: SIP, length: 464

Seems to be rather a problem of the application than container configuration. Obviously your sip application is bound to lo address 127.0.53.53 and as sip server seems to be configured 127.0.53.53 too...

If you post more details about your application it can become clearer.

Kind regards

Mr.Holmes