NAT Loopback

I'm assuming the Technicolor tg588v v2 does not do NAT loopback, which is odd as the Technicolor tg582n I was using does? Is there anyway round this?

I have tried using my tg582n, but [blank], password and install all fail if used as the dsl password and the one in the tg588v is hidden. Anyone know what this should be? I was under the impression that anything would work as the authentication was done on the line, but this doesn't seem to be the case.

Shell Energy seem to use 01*********@first-utility.com rather than the 01*********@talktalk.net I thought they would have.

Edited by hk11 (Thu 19-Sep-19 15:16:23)

There's a useful page here - http://opensimulator.org/wiki/NAT_Loopback_Routers Not sure how you submit a "new" rooter but the Technicolor TG582N does NAT loopback and the Technicolor TG588v doesn't appear to, if anyone can suss it.

Edited by hk11 (Fri 20-Sep-19 13:57:50)

And the "proper" solution to accommodate that is to use split horizon DNS. That is if you are in the internal network and lookup myserver.com you get say a 192.168.x.x address and if you are outside the network and lookup myserver.com you get the public IP address. With the added benefit that you don't pound the poor router to death NATing packets that should be handled at layer two.

Thanks: I'll Google "split horizon DNS"

In reply to a post by jabuzzard:

And the "proper" solution to accommodate that is to use split horizon DNS. That is if you are in the internal network and lookup myserver.com you get say a 192.168.x.x address and if you are outside the network and lookup myserver.com you get the public IP address. With the added benefit that you don't pound the poor router to death NATing packets that should be handled at layer two.

Very easy to sort if your devices are configurable (e.g. Mac/Linux/Windows) and pick up the DNS server from DHCP, if you run your own. However some people prefer tables and phones these days, and some of these ignore the DHCP provided DNS, and end up using some provided by Google, or a cellular provider, or a mix of the two. Its a bit of a mess

My server (Linux) doesn't get a lot of use, but I do connect via an iPad, so may have the problems you highlight.

I'd be reasonably happy if I could use my TG582N as that has worked fine with the last handful of ISPs, but SEBB's total lack of customer care really grates. I don't need any technical support just a password so I can log on!

Edited by hk11 (Wed 25-Sep-19 22:37:04)

You just need to get your BOFH ban hammer out and block port 53 outbound apart from your DNS server. That will teach them

That said with the exception of Apple devices for which I have no experience I have not seen any device ignore the DHCP provided DNS server. It may help however that I am handing out a domain name in the DHCP response (I have a domain name for two decades now for email purposes) so maybe the devices are noting that say nas.mydomain.com really does need to be looked up on the local DNS server rather than something upstream.

However you really want to avoid your router doing hairpin NAT to a NAS box because you are likely going to be sacrificing a lot of performance, and a large file transfer to the NAS could easily cause problems with general internet access while it is going on.

I'm afraid your post goes completely over my head. I'll have to do some Googling.

In reply to a post by jabuzzard:

You just need to get your BOFH ban hammer out and block port 53 outbound apart from your DNS server. That will teach them

Ha, nice, but some just switch to cellular (at least the phones). Then there is the whole DNS-over-HTTPS to worry about!

However you really want to avoid your router doing hairpin NAT to a NAS box because you are likely going to be sacrificing a lot of performance, and a large file transfer to the NAS could easily cause problems with general internet access while it is going on.

I agree completely, but I'm not the OP here

Update:-

Finally received and entered my ADSL password into the TG582N and things are running sweet again. Why an outdated (5 year old plus) router beats a more up to date model remains a mystery

One thing that I did concider was telnetting into the TG588. Would I be able to force NAT loopback there?

Edited by hk11 (Sun 20-Oct-19 19:51:40)