Re: External IP addresses on internal network

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Aug 28, 2003 at 12:05:24PM -0400, Jeffrey Laramie wrote:
> 
> >
> >Could it be that the client machine dials up to AOL, receives that IP
> >address and later it needs to resolve a name and vecause of the DNS
> >settings on the client machine it tries the query 192.168.0.24 with
> >its source 172.144.233.136?
> >
> Thanks for the suggestion. That was my first thought since one of the LAN
> clients is a notebook with dialup ability, but with a DSL connection through
> the LAN it's not used now. I did check it though to see if it still had an
> AOL IP assigned to it or an AOL server listed for DNS. It didn't, and the log
> timestamp indicates that these packets are occuring when a different client
> (with no dialup) is checking AOL mail.
> 

What about this theory (although I don't know anything about the AOL stuff)
that the client connects to AOL. AOL sets up a tunnel with this client
and assigns 172.144.233.136 to it. Then due to the static DNS settings
on the client, a DNS query is made to your named on the firewall, instead
of using AOL's DNS server?

Ramin


[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux