What type of Broadband are you using this with?
The reason I ask is that the SM2 is usually used for Wireless Broadband which uses CGAT (unless you've got a Static IP), and the ramification is that with WBB port forwarding will not work.

cbrpilot:

 

What type of Broadband are you using this with?
The reason I ask is that the SM2 is usually used for Wireless Broadband which uses CGAT (unless you've got a Static IP), and the ramification is that with WBB port forwarding will not work.

 

 

 

oh yes, to add I have a fixed IP for my wireless broadband as I port forward various ports for my servers running home assistant, adguard home etc.

Ok, if you're got a Static IP, then port forwarding will work.  Can you describe a bit about what you're trying to do?

cbrpilot:

 

Ok, if you're got a Static IP, then port forwarding will work.  Can you describe a bit about what you're trying to do?

 

yip, port forwarding works, but what I am wondering if the modem supporrts NAT loopback/pinhole NAT or if I must configure it in the above settings page.

NAT loopback is needed for instance for my DNS domain to be accessible within my network, instead of using the IP address for my server.

So for instance, from outside my network my DNS domain (using duckdns.org) I can access my server, but from within my network I cant use duckdns and I must use the server IP address.

NAT loopback will avoid this issue.

Hairpin NAT.

Spyware:

 

Hairpin NAT.

 

more coffee! yes sorry Hairpin, not pinhole 🤣

Thanks Silvrav, I assume you've tried it with SM2 and it's not working?

I will ask the question of our devices team, but if it's not working then I'd imagine it's not supported.

Out of interet what ports were you trying to use here?  80/443?  Or something different?

cbrpilot:

 

Thanks Silvrav, I assume you've tried it with SM2 and it's not working?

 

I will ask the question of our devices team, but if it's not working then I'd imagine it's not supported.

 

Out of interet what ports were you trying to use here?  80/443?  Or something different?

 

Thanks cbrpilot, that would be great to know.

the main ports I am using are 443 and 8123

Thanks.  I have reached out internally to get a final answer but the person is on leave for another week or so.  Until then assume the answer is "it is not supported", and to be honest I would not get your hopes up!

cbrpilot:

 

Thanks.  I have reached out internally to get a final answer but the person is on leave for another week or so.  Until then assume the answer is "it is not supported", and to be honest I would not get your hopes up!

 

Nothing urgent so will check back in a week or so :) 

Hi There

Are you trying to access your internal services on your External IP from inside your network?

If the answer to that question is yes, this is not something most consumer grade routers support, you will need an enterprise grade router with a LAN to LAN Nat rule.

In these situations, the cheap and dirty is to setup internal DNS server point to the internal IP for your local devices to find your resources.

Even better IP lock your external IP to services like Cloudflare (to provide protection) and then your local devices will hit the cloud and the come back into your network.

Openly port forward to the big wide world is not very secure.

nztim:

 

Hi There

 

Are you trying to access your internal services on your External IP from inside your network?

 

If the answer to that question is yes, this is not something most consumer grade routers support, you will need an enterprise grade router with a LAN to LAN Nat rule.

 

In these situations, the cheap and dirty is to setup internal DNS server point to the internal IP for your local devices to find your resources.

 

Even better IP lock your external IP to services like Cloudflare (to provide protection) and then your local devices will hit the cloud and the come back into your network.

 

Openly port forward to the big wide world is not very secure.

 

 

 

Yes to your first question - all modems I have had in the past supported NAT loopback as it's not a new feature anymore.

and yip I am using a service like cloudflare (called duckdns) but without loopback its not accessible from within my network.

https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/

Silvrav:

 

Yes to your first question - all modems I have had in the past supported NAT loopback as it's not a new feature anymore.

 

and yip I am using a service like cloudflare (called duckdns) but without loopback its not accessible from within my network.

 

DuckDNS provides free DNS it is not a cloud-based web proxy which is the safest way to do what you are trying to achieve.

If this is not an option setup internal DNS so when you resolve the IP internally it resolves to the internal IP and when you resolve externally it resolves to your external IP.

Silvrav:

 

cbrpilot:

 

Thanks Silvrav, I assume you've tried it with SM2 and it's not working?

 

I will ask the question of our devices team, but if it's not working then I'd imagine it's not supported.

 

Out of interet what ports were you trying to use here?  80/443?  Or something different?

 

 

 

 

Thanks cbrpilot, that would be great to know.

 

the main ports I am using are 443 and 8123

 

Get HA behind a reverse proxy! I'd prioritise that over messing around with hairpin NAT.