djweis at sjdjweis.com
Wed Aug 3 10:24:15 CDT 2005
On Wed, 3 Aug 2005, Kevin C. Smith wrote:
>> On Wed, 3 Aug 2005, Kevin C. Smith wrote:
>>> Dave appears to be correct regarding the Actiontec DNS issue.
>>> I upgraded my firmware to version: QW04-18.104.22.168.6.3-GT701-WG
>>> Then set my DNS as static, and it appears to work correctly thus far.
>>> I'm sure this didn't work for me before. Must be the firmware.
>> woohoo, I will be doing that today. Is that the most recent one on the
>> qwest site?
> 1. The DNS not resolving correctly, or being slow, when is spits out
> search "whatever the was" and nameserver 192.168.0.1 in /etc/resolv.conf.
This was my main problem, the onboard dns server was crap and forced
itself to be primary for dhcp clients.
> 2. The other issue is that internal/intranet hosts are not resolved
> correclty from inside the firewall. Externel IP 65.xxx.xxx.xx which is
> a server behind the firewall (port 25, 80, etc) forwared to 192.168.0.x.
> When an internal machine attempts with contact www.xxxx.com (65.xxx.xxx.xx)
> it gets 192.168.0.1 the Actiontec login.
They are resolved correctly, but to 65.x.x.x. The problem is that the
actiontec doesn't know how to hairpin the connection back inside. It's a
known problem, there's something on the iptables site about source and
destination nat onto the same network.
Dave Weis "I believe there are more instances of the abridgment
djweis at sjdjweis.com of the freedom of the people by gradual and silent
encroachments of those in power than by violent
and sudden usurpations."- James Madison
More information about the Cialug