Hairpinning stopped working ?

[thomasthomsen]

I have a MX setup where hairpinning from LAN to WAN stopped working after we changed ISP.

Its very strange. And I cant seem to figure out whats going on.

What I can see from packet traces, is that when my client pings the WAN IP thats set aside in 1:1 NAT for this internal device the MX will do an ARP for that WAN IP, and then no response will be given. (On the LAN side, how strange).

The 1:1 NAT works just fine for outside devices, but the hairpinning just stopped forking for some reason.

Have anyone ever seen this happen ? - And how did you resolve it ? 🙂

(We have done many things to try and resolve it. Cleared ARP cache on the ISP's WAN routers, rebooted MX, reapplied the config to MX and so on ... but it just seems to be broken , out of the blue.)

[PhilipDAth]

I don't know the answer.

I think I would try deleting and re-adding the 1:1 rule in desperation.

[thomasthomsen]

I think that's the only thing I have not tried ... will try it now.

(Tried to edit and modify the rule.... that did nt help ... but let's see about removing and adding.).

The only thing that was changed is that the WAN IP subnet was made bigger by our ISP, because we needed a few more IPs and the next segment was available.

[thomasthomsen]

Tried to remove the NAT config, save, and reapply.

Did not work 😕

So Im waiting in the phone support queue ....