Lonebandit
IS-IT--Management
I dont think this is possible, but I thought I would ask:
Is it possible to allow NAT loopback on the 800 series router?
I have 2 public DNS servers that run under the same 837 router. Since my last router didnt support this, I had to create the most gawd-awful setup with bind using views along with alias ethernet interfaces! - while this all works, I cannot send out 'notify' statements using this process and as such simply have to wait for the REFRESH to actually update the zone. (Notify statements have to come from the master IP or they are considered invalid)
I have 5 public IPs not including the router's IP.
They are all in a 1-1 static mapping.
All of the 'client' machines use the router's WAN IP via overload.
So, can I config the router so that NAT loopback is possible?
(example)
192.168.1.1 <-> mapped to 64.91.73.22
192.168.1.2 <-> mapped to 64.91.73.23
192.168.1.1 needs to connect to 64.91.73.23:
from inside -> to router -> back in to 192.168.1.2
This doesnt work. Neither does ssh from internal to external to back in again. I am presuming this is by design...but looking for a way around it.
Thanks.
Jeff
Is it possible to allow NAT loopback on the 800 series router?
I have 2 public DNS servers that run under the same 837 router. Since my last router didnt support this, I had to create the most gawd-awful setup with bind using views along with alias ethernet interfaces! - while this all works, I cannot send out 'notify' statements using this process and as such simply have to wait for the REFRESH to actually update the zone. (Notify statements have to come from the master IP or they are considered invalid)
I have 5 public IPs not including the router's IP.
They are all in a 1-1 static mapping.
All of the 'client' machines use the router's WAN IP via overload.
So, can I config the router so that NAT loopback is possible?
(example)
192.168.1.1 <-> mapped to 64.91.73.22
192.168.1.2 <-> mapped to 64.91.73.23
192.168.1.1 needs to connect to 64.91.73.23:
from inside -> to router -> back in to 192.168.1.2
This doesnt work. Neither does ssh from internal to external to back in again. I am presuming this is by design...but looking for a way around it.
Thanks.
Jeff