Understanding my network

[Gregory P. Ennis]

/30/2012 08:47 AM, Dale Dellutri wrote:
> On Wed, Aug 29, 2012 at 2:40 PM, Arthur Dent
> <misc.lists at blueyonder.co.uk> wrote:
>> ...
>> So here's the thing - and I don't remember having this problem with F15
>> (or previous):
>> I can access my mail using a client on another machine in my network if
>> I configure it to use 192.168.2.2, but for my mobile devices I configure
>> the email client to point to example.org. If I am outside of my network
>> they can access mail fine, but if I am at home and they are connecting
>> via my own wi-fi... no joy...
> It looks like it has something to do with your home router.  It seems to
> be having trouble routing packets which are meant for itself but coming
> from inside the lan.
>
>

I have a D-Link wifi router with the same problem.  Rather than try to kludge things to get around the problem I found it easier, and ultimately better, to run a split DNS.  So, when my wifi clients are on the internal network they are given the LAN IP address of the mail server when they use the FQDN.  When they are outside they get the external IP address they get the external IP address.

-- 
------------------------------------------------------------------------------------

This is the solution that I used as well.  There were also a lot of
unrealized benefits of having internal dns service.  I eventually got
rid of the telephone company router, and used a linux box to control all
of the traffic.  It took some time to figure out, and synchronize
iptables and nat addressing, bind, dhcpd, along with sendmail, dovecot,
and httpd.  I have found using a Linux box as the router with an
internal subnet that is differnt than the external subnet gave me a
better understanding of network traffic, and was much easier to control
than a telephone company router.  I was also surprised at how easy it
was to connect the Verizon Fios cable box through the same setup.  

Greg