0

I'm writing because i have a very strange issue with a newly installed debian 9.5 server. This server is behind a NAT made with a SonicWall firewall that assigns a public dedicated address to this server.

The internal IP address of the debian server is 192.168.50.45 and the firewall NATs this IP address to 93.xx.xx.220, but I see that the server's IP address gets translated to the default address (93.xx.xx.196) instead. So I assigned the private IP address 192.168.50.45 to another machine and this successfully gets translated to 93.xx.xx.220 on the firewall.

I've checked for env variables like http_proxy, https_proxy, checked for some kind of iptables rule that redirects traffic to the internal proxy, but I've found nothing. Does anyone have other suggestions on what can i check? Thanks in advance

Tommiie
  • 5,547
  • 2
  • 11
  • 45
Tiziano
  • 101
  • 1

1 Answers1

0

Make sure your server is in the correct SonicWall Zone/Port.

Outbound NAT rule are evaluated on the source IP and the source zone too. Thus your other server must match all the condition for the outbound NAT rule to correctly apply.

yagmoth555
  • 16,300
  • 4
  • 26
  • 48
  • Thanks for the info. I'm digging deeply and i saw that some sites, like whatismyip.com and dnsstuff.com sees the correct address, others instead sees the wrong one, so i think that it's a firewall issue – Tiziano Oct 16 '18 at 13:45
  • @Tiziano whatismyip see your outgooing IP, so your router is ok now, but dnsstuff see DNS's entry IP, we mix two thing now, it's not the same thing – yagmoth555 Oct 16 '18 at 13:47
  • dnsstuff sees the correct address... i get the wrong address by using for example `user@sdiws:~$ curl http://checkip.amazonaws.com/ 93.xx.xx.196` – Tiziano Oct 17 '18 at 15:31