I'm thinking this is your problem here
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 eth0
you need to get rid of this line somehow. And make the output from
'route -n' match the 1.4.1 version.
try
route del -net 0.0.0.0
Now this might get rid of the line with
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
which you want to keep. So you might need to add it back in with
route add default gateway 192.168.0.1
After each change, use 'route -n' to see the difference. And do a
'ping
www.google.com' to see if it fixes anything.
On 12/1/06, Kristofer Dale <barefoot@???> wrote:
>
> v2.3 route -n has the following output:
>
> Kernal IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
> 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
> 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 eth0
>
> cat /etc/resolv.conf:
>
> nameserver 205.171.3.65
> nameserver 205.171.2.65
>
>
>
> for comparison, v1.4.1 has the corresponding output:
>
> route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
>
> 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
>
> cat /etc/resolv.conf
>
> nameserver 205.171.3.65
> nameserver 205.171.2.65
>
> Hope this helps...
>
> .
> . _o Kristofer Dale,
> . _ \<,_ ragged individualist,
> . ( )/ ( ) statistic at large...
> .
>
> p.s. Learn and live, http://www.vitaletherapeutics.org
> _______________________________________________
> dynebolic mailing list
> dynebolic@???
> http://mailinglists.dyne.org/mailman/listinfo/dynebolic
>
::
Re: [dyne:bolic] DNS problem?
