topic Re: gateway own address translate not working in s2s in Firewall and Security Management

gateway own address translate not working in s2s

Feridun_ÖZTOK — Tue, 27 Feb 2024 09:05:06 GMT

Hi there,

i wish remote gateway come to our gateway use internal address. I write nat rule for this job but it's not working. Maybe i didn't perfectly explain but i attached a diagram and screeanshot. İs there any way ?

Re: gateway own address translate not working in s2s

AmirArama — Tue, 27 Feb 2024 21:17:05 GMT

Can you provide more details?

Is it gaia or spark (smb)? What version?

Why do you want to hide traffic from your GW behind it's internal IP?

Is it possible that you have "disable nat inside the vpn community" selected in the vpn community > advanced tab?

Re: gateway own address translate not working in s2s

Feridun_ÖZTOK — Tue, 27 Feb 2024 22:15:28 GMT

Hi Amir,

All gateways R81.10 Take 130

Remote gateway is cluster state. S2S running over cluster ip. Members send cpview data (skyline) to my side. My side drop the packed "According to the policy the packet should not have been decrypted". I thought that if I could send it via their internal addresses, there would be no need to define their external addresses in the VPN domain. If I can't I know I can solve it this way, I just wanted to try and ask.

"disable nat inside the vpn community" not selected, i checked it 👍

Re: gateway own address translate not working in s2s

AmirArama — Wed, 28 Feb 2024 09:33:28 GMT

Seems like a bug to me, unless you did some special configuration that may affect it.

i tried to replicate it on R81.20 jhf 41, and it's working properly.

Consider upgrade or open TAC to investigate.

Re: gateway own address translate not working in s2s

Feridun_ÖZTOK — Wed, 28 Feb 2024 11:46:01 GMT

Hi Amir,

Always finds me 🙂 Thanks for help.

Re: gateway own address translate not working in s2s

Feridun_ÖZTOK — Wed, 28 Feb 2024 14:21:19 GMT

Hi Amir,

I solved the problem, I'm happy 🙂 A little bit of user error, a little bit of a bug. I made a mistake when the logs showed something that wasn't working as working. The problem is solved now, thank you again.