Mailinglist Archive: opensuse (4288 mails)

< Previous Next >
RE: [SLE] Card Hell (Was network hell)
  • From: Nick Selby <php@xxxxxxxxxxxxx>
  • Date: Thu, 02 May 2002 16:06:08 +0200
  • Message-id: <5.0.0.25.2.20020502160248.00a73f80@xxxxxxxxxxxxxxxxxx>
At 09:54 AM 5/2/2002 -0400, you wrote:
Nick,
I don't see any mention of your DNS entries!
Can you get out on the Internet from ANY computer going through that
gateway?

Yes, the other two have no problem seeing each other or the internet. Or we wouldn't be able to have these stimulating conversations!!!

I'm in my old hard drive now copying /etc/*.conf .

The contents of route.conf:

192.168.0.1 0.0.0.0 255.255.255.255 ippp0
192.168.10.0 0.0.0.0 255.255.255.0 NONE
default 192.168.0.99


Contents of resolv.conf


nameserver 192.168.10.1
search nickselby.de


If not, check that you have entries in the Name Server List.
This would explain why you can ping the other machines on the network, but
you can't get out to the Internet.

---------------------------
Eric Carbone



-----Original Message-----
From: Nick Selby [mailto:php@xxxxxxxxxxxxx]
Sent: Thursday, May 02, 2002 9:49 AM
To: suse-linux-e@xxxxxxxx
Subject: Re: [SLE] Card Hell (Was network hell)

At 09:31 AM 5/2/2002 -0400, you wrote:
>A couple of things bothered me about Nick's posts.
>First, the necessity of rebooting the system. In Linux and Unix systems
>there are very few reasons why a system needs to be rebooted. Possibly the
>card services thing may have assigned the installed NIC on eth1 and the PC
>card onto eth0. In that case, I might suggest a reboot. But, changing most
>networking information generally requires simply a quick reconfiguration.

That was my suspicion, and the main reason I am hesitant to make the clean
reinstall: I just made a clean install on a spanking new hard drive; the
thing SEES my ethernet card; there should be no reason it cannot be
configured.

Except I don't know how. Or even where to start.




>YaST normally handles this. Certainly, if you want to run a new kernel, you
>need to reboot. But even if you want to change a driver, simply unload the
>module (if it is loaded), and load the new module. Even if X is screwing
>up, if you can get to a virtual terminal (ctl-alt-f[1-6]). Log in as root
>and telinit 3 (to shut off X until you can fix the problem). There are some
>other reasons. I have seen X grab the mouse and keyboard in such a manner
>that the only thing you can do is power off.
>
>The other is reinstall. If you really messed up the installation, then that
>might be a solution, but with most modern Linux distros, you can easily
>remove and add packages.
>
>With YaST, it is relatively simple to change your network configuration. We
>hold our monthly LUG meetings at MIT where we have a static IP. After I
>boot my laptop, I simply reconfigure the network with the static IP
>assigned to that classroom.
>
>(BTW: I've spent many hours in network hell as well as various code
>management systems hell :-)
>
>
>
>On 2 May 2002 at 15:13, Nick Selby wrote:
> > Actually I agree, but since I'm trying to learn about Linux this seems a
> > very Windoweez way of going about it. Something don't work? Reinstall
the
> > entire operating system! But I take your point. Of more concern was my
> > distinct impression that the suse tech, while a VERY nice guy, seemed a
> bit
> > lost. For example, not once did he ask me for the output of ifconfig.
For
> > example.
>
>--
>Jerry Feldman
>Portfolio Partner Engineering
>508-467-4315 http://www.testdrive.compaq.com/linux/
>Compaq Computer Corp.
>200 Forest Street MRO1-3/F1
>Marlboro, Ma. 01752
>
>
>--
>To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
>For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
>Also check the archives at http://lists.suse.com


--
To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx

Also check the archives at http://lists.suse.com

--
To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com


< Previous Next >