I'm trying to determine why lumumba can autoconfig DNS for internet access
and no version of dhoruba can't. This is NOT a hardware issue. I can boot
up and network both of my computers via wired ethernet using WinME,
dyne1.4.1, and many other Linux distros. Since dyne2, DNS is not working. I
have valid pingable eth0, but I can't ping my gateway. It is my
understanding that v1.4.1 uses pump, but varies among versions of dhoruba.
I have docked and nested every release of dhoruba to date, and DNS has
never functioned. For some reason, dhoruba can't see my DSL gateway at its
default address of 192.168.0.1 even when v1.4.1 does. To clarify the
problem, I am typing this post on one of my computers running 1.4.1 while
trying to troubleshoot v2.3 on the other. It makes no difference which of
the two computers I try (one is an HP Pavilion PIII, the other is an AMD
homebuilt) and both work fine otherwise. The gateway is an older Actiontech
DSL gateway provided by Qwest, my ISP and business telephone company. It is
configured for DHCP, and has no problems keeping up even when several
computers on the network are all accessing the internet. Does anyone know
what the difference is between v1.4.1 and the dhoruba series that would
affect DNS in this way? THanks for your help...

K.D.