This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SNAT RULE persists when LAN Network is changed

Hi all,
using an XG Cluster.
i'm having kind of a strange problem here.

Former LAN-NET: 10.106.72.0/22
Replaced with LAN-NET: 10.106.68.0/22

I'm having a RADIUS VM runnin on azure(10.0.1.5) and several other virtual machines.
As we are using the RADIUS to authenticate on-site Wifi Users i needed a fixed configured RADIUS-CLIENT IP on Server Side, which is 10.106.68.1

To make this work, that every request to RADIUS arrives with same IP i made:

system ipsec_route add host 10.0.1.5 tunnelname AZURE

set advanced-firewall sys-traffic-nat add destination 10.0.1.5 snatip 10.106.72.2

all worked fine, even with natting rule configured in gui.

Now, as the LAN-NET has been replaced, of course i changed all network objects/alias etc.. .but still.

for example: if i ping another azure vm 10.0.1.4 it goes outside with 10.106.68.1, which is correct.

if i ping the vm, for which i configured SNAT (10.0.1.5) , it still tries to go out with old LAN-GW address of 10.106.72.2.
Any idea of how to get completely rid of the old entry/reference of 10.106.72.2?

From inside the SSL-VPN all is ok, as users when try to authenticate with radius, the radius server gets request from 10.106.68.1.

hope this is explained in the manner, that someone will be able to help

p.s.: i also cleaned conntrack with -F and -D -n (snat-ip) and also restarted the Firewall... i have no idea anymore




This thread was automatically locked due to age.
Parents Reply Children
No Data