DSL Troubles Solved -- but not resolved...

[Jack Berger]

Just an fyi on your last comment. While knowing how to do whatever you
did to fix your problem from a command line is a good thing, keep in
mind that if it wasn't what Yast2 set up originally, the next time you
reboot, Yast2 will reset it to what it thinks is right, and you'll be
right back where you were. It's kind of anal that way.

So if you use Suse, and Yast2 for system configs, all system configs
should be done from there. There is an option to shut it off, but then
it is totally off, and I believe the next time you turn it on for
something, it will redo all the system config to what it knew last.

Does anyone know where Yast2 keeps this info so it could be changed to
reflect what you do outside of it?

-jhb-

From: Condon Thomas A KPWA <tcondon at kpt.nuwc.navy.mil>

> Thanks for the suggestion, Llama, but I don't think it was MTU...
>
> However, while mucking about in Yast2 I decided to turn on the firewall2
> software and it told me in the process that eth0 was *not* my output
> interface.  So I changed it to be the output interface and bingo, I'm
> connected.
>
> Now, so this lesson won't be wasted on the stupid (me), can someone tell me
> what the heck I did and how to do it from a command prompt?