NAT not working ?

I run an email server at home that takes are of the email
on my domain. It's setup to only trust things on my
internal subnet (the 192.168. network). When I send email
and connect to the SMTP server I get denied. The logs
show that the MN 500 is passing in my WAN IP (the public
IP).

TO be clear, I've got an email server at 192.168.1.4
that's plugged into the MN500 (which is set to act as a
router, not a bridge). My laptop connects wirelessly, and
if I don ipconfig shows its IP as 192.168.1.10. That
would work, but when I connect to my SMTP server by name
(smtp.foo.com, say), the logs show that the IP passed in
is the external IP (66.something) and so the email server
denies sending since it thinks I'm someone from the
outside trying to spam.

It's not the router. It's the DNS zone file that has been
set that way (DNS converts (sub)domain names to IPs). You
can change the DNS zone file for smtp.foo.com to
192.168.1.4.

I have done that on mine to make it easy to access some
local PCs by name using local IP's, but not for the SMTP
server (I have authentication enabled on SMTP to prevent
being taken by spammers).

>-----Original Message-----
>I run an email server at home that takes are of the
email
>on my domain. It's setup to only trust things on my
>internal subnet (the 192.168. network). When I send
email
>and connect to the SMTP server I get denied. The logs
>show that the MN 500 is passing in my WAN IP (the public
>IP).
>
>TO be clear, I've got an email server at 192.168.1.4
>that's plugged into the MN500 (which is set to act as a
>router, not a bridge). My laptop connects wirelessly,
and
>if I don ipconfig shows its IP as 192.168.1.10. That
>would work, but when I connect to my SMTP server by name
>(smtp.foo.com, say), the logs show that the IP passed in
>is the external IP (66.something) and so the email
server
>denies sending since it thinks I'm someone from the
>outside trying to spam.
>
>.
>

Which version of the firmware are you running? I bet it's a version
before 1.09.* as prior versions don't have loopback support which is
what it sounds like you are trying to do.

Rick Gregory wrote:

> I run an email server at home that takes are of the email
> on my domain. It's setup to only trust things on my
> internal subnet (the 192.168. network). When I send email
> and connect to the SMTP server I get denied. The logs
> show that the MN 500 is passing in my WAN IP (the public
> IP).
>
> TO be clear, I've got an email server at 192.168.1.4
> that's plugged into the MN500 (which is set to act as a
> router, not a bridge). My laptop connects wirelessly, and
> if I don ipconfig shows its IP as 192.168.1.10. That
> would work, but when I connect to my SMTP server by name
> (smtp.foo.com, say), the logs show that the IP passed in
> is the external IP (66.something) and so the email server
> denies sending since it thinks I'm someone from the
> outside trying to spam.
>

Runtime code version: V1.11.017
Boot code version: V1.06

Are there later versions? Checking for updates doesn't
produce anything...
>-----Original Message-----
>Which version of the firmware are you running? I bet
it's a version
>before 1.09.* as prior versions don't have loopback
support which is
>what it sounds like you are trying to do.
>
>Rick Gregory wrote:
>
>> I run an email server at home that takes are of the
email
>> on my domain. It's setup to only trust things on my
>> internal subnet (the 192.168. network). When I send
email
>> and connect to the SMTP server I get denied. The logs
>> show that the MN 500 is passing in my WAN IP (the
public
>> IP).
>>
>> TO be clear, I've got an email server at 192.168.1.4
>> that's plugged into the MN500 (which is set to act as
a
>> router, not a bridge). My laptop connects wirelessly,
and
>> if I don ipconfig shows its IP as 192.168.1.10. That
>> would work, but when I connect to my SMTP server by
name
>> (smtp.foo.com, say), the logs show that the IP passed
in
>> is the external IP (66.something) and so the email
server
>> denies sending since it thinks I'm someone from the
>> outside trying to spam.
>>
>
>.
>

Thx. I think I'm going to go the SMTP auth route too...
>-----Original Message-----
>It's not the router. It's the DNS zone file that has
been
>set that way (DNS converts (sub)domain names to IPs).
You
>can change the DNS zone file for smtp.foo.com to
>192.168.1.4.
>
>I have done that on mine to make it easy to access some
>local PCs by name using local IP's, but not for the SMTP
>server (I have authentication enabled on SMTP to prevent
>being taken by spammers).
>
>>-----Original Message-----
>>I run an email server at home that takes are of the
>email
>>on my domain. It's setup to only trust things on my
>>internal subnet (the 192.168. network). When I send
>email
>>and connect to the SMTP server I get denied. The logs
>>show that the MN 500 is passing in my WAN IP (the
public
>>IP).
>>
>>TO be clear, I've got an email server at 192.168.1.4
>>that's plugged into the MN500 (which is set to act as a
>>router, not a bridge). My laptop connects wirelessly,
>and
>>if I don ipconfig shows its IP as 192.168.1.10. That
>>would work, but when I connect to my SMTP server by
name
>>(smtp.foo.com, say), the logs show that the IP passed
in
>>is the external IP (66.something) and so the email
>server
>>denies sending since it thinks I'm someone from the
>>outside trying to spam.
>>
>>.
>>
>.
>

The firmware is up-to-date and supports loopback.
It's a DNS problem.

>-----Original Message-----
>Runtime code version: V1.11.017
>Boot code version: V1.06
>
>Are there later versions? Checking for updates doesn't
>produce anything...
>>-----Original Message-----
>>Which version of the firmware are you running? I bet
>it's a version
>>before 1.09.* as prior versions don't have loopback
>support which is
>>what it sounds like you are trying to do.
>>
>>Rick Gregory wrote:
>>
>>> I run an email server at home that takes are of the
>email
>>> on my domain. It's setup to only trust things on my
>>> internal subnet (the 192.168. network). When I send
>email
>>> and connect to the SMTP server I get denied. The logs
>>> show that the MN 500 is passing in my WAN IP (the
>public
>>> IP).
>>>
>>> TO be clear, I've got an email server at 192.168.1.4
>>> that's plugged into the MN500 (which is set to act as
>a
>>> router, not a bridge). My laptop connects wirelessly,
>and
>>> if I don ipconfig shows its IP as 192.168.1.10. That
>>> would work, but when I connect to my SMTP server by
>name
>>> (smtp.foo.com, say), the logs show that the IP passed
>in
>>> is the external IP (66.something) and so the email
>server
>>> denies sending since it thinks I'm someone from the
>>> outside trying to spam.
>>>
>>
>>.
>>
>.
>