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

Loopbak/Hairpin NAT. XG 18 MR1

HI,

I've seen a couple of posts with issue with loopback/hairpin NAT (being able to lookup an External Name while on the internal network)

I created a rule for my service and the Loopback rule was created automatically, but it doesn't seem to work (at least, not as far as I can tell)

I've tried a couple of things, but still no luck.

While on 4G, I can connect to myname.ddns.net:xxxxx, but when on WIFI I can't.

Should the automatic loopback rules work or am I missing something?

Thanks

This thread was automatically locked due to age.

Top Replies

Dave Penson over 3 years ago in reply to FormerMember +2

Hi, thanks for the reply. This was one if the threads I'd found, i tried opening and saving the rule, but it didn't work. This thread also seemed to be linked to and upgrade from V17.x wheras this…

0 FormerMember over 3 years ago

Hi Dave Penson,

Thank you for reaching out to the Community!

This seems to be related to an ID that our support team already invested with internal ID(NC-59809) and a fix for this issue has been tentatively targeted with v18 MR3.

Workaround: Open the loopback rule and click on Save to make it working again.

Check out the following thread for more info: https://community.sophos.com/xg-firewall/f/discussions/120384/sfos-v18-0-379---hairpin-nat-loopback-rule-can-t-get-to-work

Thanks,
Cancel
Vote Up +1 Vote Down

Cancel
0 Dave Penson over 3 years ago in reply to FormerMember

Hi, thanks for the reply.

This was one if the threads I'd found, i tried opening and saving the rule, but it didn't work.

This thread also seemed to be linked to and upgrade from V17.x wheras this is a fresh install of 18.

It is a custom service/port, so I don't know if that has anything to do with it?

MR3 seems a bit like vapour-ware, which nobody really knows when it will be released.
Cancel
Vote Up +2 Vote Down

Cancel
0 FormerMember over 3 years ago in reply to Dave Penson

Hi Dave Penson,

I would suggest you open a support case for further investigation if the workaround did not work. You could send me the case number via PM so that I can help with the follow up if needed.

Thanks,
Cancel
Vote Up 0 Vote Down

Cancel
0 Philipp Greindl over 3 years ago

I had the same problem. Try different settings of route precedence.

This worked for me
Cancel
Vote Up 0 Vote Down

Cancel