Deja Vu all over again
John F. Kohler
jkohler2 at earthlink.net
Sat Mar 31 19:00:52 PST 2001
ME wrote:
> On Sat, 31 Mar 2001, John F. Kohler wrote:
> > ME wrote:
> > for the mac LC, only the link/act comes on, never the other two. It blinks
> > when I am making an internet query. In the old days, same for the Linux line.
>
> So, since you have installed this new Linux, have you seen the activity
> light blinking on the linksys port that has the cable connected to the
> linux box?
Yes. The red is on steady, and the green router LED flickers in step (run upstairs)
with the green light on the NIC. (red NIC is on steadily)
>
>
> > > If so do each
> > > link light show up for each port as "on" and does the port connected to
> > > the Linux box also show up as "on"?
> >
> > Yes. At all times for the Linux and Mac LC. Only for the iMac when
> > it is powered up.
>
> (Hm. We might come back to this,)
>
> > > Is there a link light on the ethernet
> > > card port on the back of your computer?
> >
> > There are 2 LED's on the NIC. The green one is labeled "t" nd the red
> > one "k" during the successful pings of 192.168.1.1 the green light
> > blinks, the red stays on steady. (interestingly, the successful pings
> > only work for a while. Just now I sent 768 packets and 94 were
> > answered. It seemed as if the LinkSys Router got "tired" of answering
> > after 94 and just shut off. The linux box after reporting the
> > successful 94, started reporting "Destination Host Unreacheable."
> > Starting the ping again, did not reset anything.
>
> Often (not *all of the time*) ethernet cards that have a red light turned
> on are telling you there is a problem with the media, cable, wiring, or
> signalling. do you recall it having been red when you had an old copy of
> linux installed with working networking?
With Linux 6.2 on the old box with another NIC the router and CAT-5 cable to it worked
fine. Now, I may justifiably be accused of changing too many elements in this mix.
1) RH 6.2 to RH 7.0
2)Pentium 200 machine to AMD k-6 machine
3) a new ethernet NIC in the new computer.
I plead guilty. It is probably better to change **one** item at a time in a complex
system to see if something changes, not **three**
>
>
> Could you try to disconnect the ethernet cable to your linux box and then
> disconnect the ethernet cable to one of your Macs that you know works fine
> on the network, and then connect the cable that was from the mac to the
> linksys box instead to the linux bos and linksys router
Yes. I think the goal here is to determin if the trouble "moved" with the cable & router
port. It did not.
1) the Mac LC works fine with both its "old" cable & port and with the "linux" cable and port.
2) The Linux fails with which ever cable and router port it is using.
....Wait a minute! After a whole bunch of "Destination Host Unreachable" with the linux box on
its "old" cable and port, it just started working! We have an intermittent
problem here...somewhere....
> . You will also
> want to keep the port used for the macintosh. (I'd like to make sure that
> there is not a problem with this port on the linksys box and the cable to
> presently attached to the linux box.)
That is correct. both cables and router ports work with the Mac LC
>
>
> After the above is done, try testing the ping of the linksys router from
> the linux box that is using the port on the Linksys and cable once used by
> a network working mac. You may need to reboot your Linux box for the card
> to "reset" and clear any errors when talking to the linksys router, or may
> not. It might be safer to shut down the linux box (just for testing) wen
> you switch the cables. Please note if the red light changes when using the
> other port/cable combination.
I did that. The red NIC led stays on steadily at all times. Only the green light flickers
Right now, I am successfully pinging the router address of 192.168.1.1 with over
100 successful sequences.
>
>
> > As I am writing this, the Linux is booting, verry slowly.
> > Particularly long on the
> > "Starting lpd: "
> > took about 5 minutes. and it normally starts in 2 seconds.
>
> Due to inability to talk with other devices on the network, or possibly
> resolve "loclahost" or other lookups.
There was some obscure message about localhost not responding before
I re-installed the7.0 system again.
>
>
> > When I finally logged at my user level, Ityped in "startx"
> > which usually starts in 30 seconds or so. This time a dialog box
> > came up:
> >
> > Could not look up internet address for localhost.localdomain.
> > This will preventGNOME fromworkingcorrectly.
> >
> > (continue) or (try again)
>
> If you would like to try to eliminate this message and test x anyway, you
> can edit /etc/hosts as root and add the following:
> 127.0.0.1 localhost.localdomain localhost loopback
>
> With the abobe added to your etc/hosts, see if GNOME starts up.
>
> The names of the errors listed above suggest that networking installation
> from your install may not have been complete, or you chose to name your
> computer "localhost" and your domain "localdomain" but I do not use GNOME
> so I am not sre itf this is the normal behavior of it instead. Howevere
> this is not necessary for our testing. This is only useful if you want to
> see GNOME.
>
> > My first impulse is to re- install the system.
> This is an option, but without an understanding of what went wrong, we may
> not be able to correct it.
>
> Did you say before that RedHad 6.x worked without any problem on this
> machine with present ethernet card for networking, but moving to RedHat 7
> now has the NIC to failing to work reliably?
Redhat 6.2 worked successfully on the Pentium but I am not sure I tried it on my
new computer (amd -k-6) I probably did not, but I am willing to do so. After all,
6.2 served me long and well on my home network with this cable, router, and an older
ISA nic ethernet card.
>
>
> Here are some of the remaining possible problems I see:
> 1) Hardware failure in the media, linksys port, ethernet card. (Good
> chance but we can test some above)
I suspect hardware also. A whole new computer and a recently purchased
NIC.
>
> 2) Bug being tickled in linux for the driver used to talk to the card
> (ood chance)
Redhat 7.0 did get some bad press, not for the kernel, or ethernet stuff
but for the "C" compiler, if I recall, and some security holes.
>
> 3) Network service/process or sentry that is not acting like it should
> (not so likely)
It is funny, to me, on successful pings to 192.168.1.1 some times I'll get
356 out of 427 packets (16% loss) on others:
190 packets transmitted, 1 packet received. I would think
that the problem would remain constand, i.e., continuous 15% losses across the
board.
Here is another puzzler....Just now I pinged 192.168.1.4 ....21 packets sent and
received 100% success, 0% packet loss.
Do intermittent problems raise their ugly heads in the ethernet arena?
>
> 4) Installation of system has included some corrupt files, or networking
> is incomplete, or library problems, or (also not likely for most of
> these except maybe incomplete network installation.)
I am capable of screwing the most simple and straightforward installation
processes. (Incidentally I **don't** have a surge suppressor on my "new"
PC, so utility line abberations during an installation might just interfere
with the successful transfer of software from the installation CD to the hard disk.
>
>
> We can test most of "1" here. Testing 2 would require that you borrow
> another ethernet card of exact make and model which you may not have.
This could be doable. The NIC came from Jameco, a reputable firm in Belmont
which offers 30 day exchange or refund priviliges.
> You
> can always try to examine your ethernet card physically. Is it seated in
> the slot on the motherboard all of the way?
As best I can tell, yes.
> When you inspect the
> recepticle on the ethernet card that receives the cable, do you notice all
> 8 conductors lined up in paralel with none bent or in non-symmetrical
> positions?
yes
> Does the ethernet card come with any diagnostic software to
> test media and the card?
Yes, but it requires that I boot the PC from a reliable Windows9x/DOS floppy.
The one I have now is corrupted, partly, and I can't trust it. I can try to get another,
maybe from a neighbor, or my son in Cotati.
> If you have this diagnostic software and can run
> it, examine the lights on the back of the card.
I did run the diagnostic software once, yesterday, successfully. I did
not notice the LED's on the back of the NIC.
> Do these lights appear
> differently during the tests?
Don't know.
> Do the tests all report passing status?
Yes.
John
>
>
> -ME (no more comments to stuff beyond this point from me in this message)
>
> > > > > (Output from each? Each will try to send only "1" ping out to the
> > > > > specified IP addresses.))
> > > > >
> > > > > I will assume this is a default install with no services turned off. If
> > > > > htis is the case, you should have "telnet" running on your local
> > > > > machine. Later you may want to look into turning this off depending upon
> > > > > how paranoid you are since you are behind a NAT translated router. For
> > > > > now, we can use it for testing.
> > > >
> > > > Yes, in fact, I did complete a full installation and don't know how to turn
> > > > any of the services off. It is probably true that "telnet" is installed and working
> > > > here.
> > >
> > > Since the grep for a telnet service shows up a negative, it seems
> > > unlikely or you to be able to connect to it. What does this report:
> > > # netstat -a -n --ip | grep "LIST"
> > > (It should tell us what services are running)
> > >
> > > > telnet>
> > > This is the telnet application command prompt. example command for this
> > > may include "open hostname" and "quit" while others do exist but these are
> > > the most common. "quit" will probably be the most useful for you to return
> > > back to a "#" prompt
> > >
> > > > > (If you see a login prompt appear, that is good. Just press conrol-d or
> > > > > press return a few tiumes until your connection is denied enough to have
> > > > > you disconnected and return you to your "#" prompt. If it "hangs" here ,
> > > > > then try control-c and note the problem in not being able to connect.)
> > > > >
> > > > > If the above works, then try:
> > > > > # telnet 192.168.1.4 23
> > > >
> > > > It does not seem to work with "23" for telnet, strangely, it does seem to work
> > > > with "25" SMTP. I don't understand that; further, after a (ctrl C)
> > > > I got the following prompt
> > >
> > > Yes, you must be running a mail service. The netstat from above should
> > > show us what ese you are running.
> > >
> > > > I stopped here for the night. Will return tomorrow for more attempts
> > > > at this new procedure (for me!!) when I can report results more accurately.
> > >
> > > OK. based on the information you have reported above, I have added a few
> > > more questions that don't require so much typing, but more of your
> > > examination of your physical cables, and "das blinken lights" (sorry,
> > > could not resist the arcane reference.)
> > >
> > > It would be good to verify some of the information below, but most of it
> > > assumes you have some sort of application layer or network check to an off
> > > linux node actually working. I'd like to focus on the physical connections
> > > and more the drivers and cards.
> > >
> > >
> > > > > (Follow same above procedure if you get a login prompt like above. If you
> > > > > do not get a login prompt this is worthy to note.)
> > > > >
> > > > > If the above also works, we can try telnetting to the "web" port on the
> > > > > linksys router. (You stated it runs a web service.)
> > > > >
> > > > > For this we will have a different disconnect procedure than the above.
> > > > > # telnet 192.168.1.1 80
> > > > >
> > > > > You should see something like this, and your cuursor will probably just
> > > > > sit therer blinking at you without returning you a "#" prompt:
> > > > > Trying 192.168.1.1...
> > > > > Connected to 127.0.0.1.
> > > > > Escape character is '^]'.
> > > > >
> > > > > (If it just hangs at the part "Trying 192..." then you should be able to
> > > > > type control-c to get out. If you see the above, then you should be able
> > > > > to press control-] and then see a "telnet->" prompt to which you can type
> > > > > "quit" and then press return.
> > > > >
> > > > > Assuming that the ICMP "ping" test worked and the TCP based connections
> > > > > above worked, we can move on to test UDP and then try some DNS lookups.
> > > > >
> > > > > If all of the above provides us with the desired results, then we can look
> > > > > at UDP and/or DNS lookups with your DNS values.
> > > > >
> > > > > Your listed entries for resolv.conf may have typos in transcription or
> > > > > need some attention. try editing the file "etc/resolv.conf" and change it
> > > > > from:
> > > > >
> > > > > search earthlink.net
> > > > > nameserver 207.217.126.01
> > > > > nameserver 207.217.77.82
> > > > > nameserver207.217.120.83
> > > > >
> > > > > to
> > > > > search earthlink.net
> > > > > nameserver 207.217.126.81
> > > > > nameserver 207.217.77.82
> > > > > nameserver 207.217.120.83
> > > > >
> > > > > If the second paragraph is actually what you presently have then we should
> > > > > be able to go on.
> > > > >
> > > > > DNS allows for TCP and UDP based name lookup. Most of the time, name
> > > > > lookups occur over UDP. We can try using "nslookup" to see if your linux
> > > > > box can talk to the dns you specified int he above resolv.conf
> > > > >
> > > > > (My comments should not by typed in. They are specified within ( ) and
> > > > > left question marks "?" for values that may be different when you run your
> > > > > check:
> > > > >
> > > > > Here is a sample session in nslookup that I would like you to try:
> > > > > # nslookup
> > > > > Default Server: ns1?.earthlink.net
> > > > > Address: 207.217.126.81? (or 207.217.77.82 or 207.217.120.83)
> > > > >
> > > > > > www.earthlink.net (type this in)
> > > > > Server: ns1?.earthlink.net
> > > > > Address: 207.217.126.81? (or 207.217.77.82 or 207.217.120.83)
> > > > >
> > > > > Name: www.earthlink.net
> > > > > Addresses: 207.217.114.220, 207.217.114.200
> > > > >
> > > > > > exit
> > > > > #
> > > > >
> > > > > At least one of the above tests should fail or unexpected information will
> > > > > be provided if you are still experiencing the problems with networking.
> > > > >
> > > > > Luckily, output from the above *should* be much shorter than everything
> > > > > else you have typed.
> > > > >
> > > > > if "ipchains" near the top pushes out a *lot* of stuff, then I'd try the
> > > > > file copy system mentioned before and do:
> > > > >
> > > > > # ipchains -L -n > /tmp/chainoutp.txt
> > > > > and then copy the "/tmp/chainoutp.txt" to floppy for attachment inclusion.
> > > > >
> > > > > Most of your values seem right (except for a leading zero for an octet on
> > > > > the resolv.conf and a missing space...)
> > > > >
> > > > > Now we are trying to test some of the parts and use some tools to see what
> > > > > happens.
> > > > >
> > > > > One thing that makes me think you had most of your settings properly set
> > > > > up, was an earlier statement where you said a traceroute worked, but a DNS
> > > > > lookup withing netscape failed.
> > > > >
> > > > > Thanks,
> > > > > -ME
> > > > >
> > > > > On Thu, 29 Mar 2001, John F. Kohler wrote:
> > > > >
> > > > > > Date: Thu, 29 Mar 2001 22:19:01 -0800
> > > > > > From: John F. Kohler <jkohler2 at earthlink.net>
> > > > > > Reply-To: nblug-talk at lists.sonic.net
> > > > > > To: nblug-talk at lists.sonic.net
> > > > > > Subject: Re: Deja Vu all over again
> > > > > >
> > > > > >
> > > > > >
> > > > > > ME wrote:
> > > > > >
> > > > > > > I am going to assume that this has not yet been resolved and take a stab
> > > > > > > at it. If this was resolved, and I did not notice, then skip this and
> > > > > > > please accept my appologies.
> > > > > > >
> > > > > > > Could you reboot your Linux box and then as root could you go to a command
> > > > > > > prompt and run the following command, and then take the contents of the
> > > > > > > output for each and paste them into one e-mail message for review on the
> > > > > > > list:
> > > > > > >
> > > > > > > # ifconfig
> > > > > >
> > > > > > eth0 Link encap: Ethernet HW addr 00:00:1C:56:C6:D1
> > > > > > inet addr: 192.168.1.4 Bcast: 192.168.1.255 Mask: 255.255.255.0
> > > > > > UP GROADCAST RUNNING MULTICAST MTU: 1500 Metric: 1
> > > > > > Rx packets: 0 errors:0 dropped:0 overruns:0 frame :0
> > > > > > Tx packets: 0 errors: 0 dropped:0 overruns:0 carrier:0
> > > > > > collisions:0 txqueuelen:100
> > > > > > Interrupt:10 Base Address:0x2a0
> > > > > >
> > > > > > lo Link encap:Local Loopback
> > > > > > inet addr: 127.0.0.1 Mask:255.0.0.0
> > > > > > UP LOOPBACK RUNNING MTU: 3924 Metric:1
> > > > > > RX packets :14 errors:0 dropped:0 overruns: 0 frame:0
> > > > > > TX packets: 14 errors:0 dropped:0 overrruns:0 carrier: 0
> > > > > > Colissions: 0 txqueuelen: 0
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > # ifconfig eth0 same as above
> > > > > >
> > > > > > >
> > > > > > > # route -n
> > > > > >
> > > > > > Kernel IP routing table
> > > > > > Destination Gateway Genmask Flags Metric Ref Use Iface
> > > > > > 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
> > > > > > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
> > > > > > lo
> > > > > > 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0
> > > > > > eth0
> > > > > >
> > > > > > >
> > > > > > > # cat /proc/interrupts
> > > > > >
> > > > > > CPU0
> > > > > > 0: 304648 XT-PIC timer
> > > > > > 1: 113 XT-PIC keyboard
> > > > > > 2: 0 XT-PIC cascade
> > > > > > 4: 6 XT-PIC serial
> > > > > > 8: 1 XT-PIC rtc
> > > > > > 9: 0 XT-PIC usb-uhci
> > > > > > 10: 1 XT-PIC NE2000
> > > > > > 13: 1 XT-PIC FPU
> > > > > > 14: 76601 XT-PIC ide0
> > > > > > NMI: 0
> > > > > >
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > # cat /proc/ioports
> > > > > >
> > > > > > 0000-001f : dma1
> > > > > > 0020-003f: pic1
> > > > > > 0040-005f: timer
> > > > > > 0060-006f: keyboard
> > > > > > 0070-007f: rtc
> > > > > > 0080-008f:dma page reg
> > > > > > 00a0-oobf:pic2
> > > > > > 00c0-00df: dma2
> > > > > > 00f0-00ff: fpu
> > > > > > 01f0-01f7:ide0
> > > > > > 02a0-02bf: ne2000
> > > > > > 02f8-02ff:serial (auto)
> > > > > > 03c0-03df:vga+
> > > > > > 03f6-03f6: ide0
> > > > > > o3f8-03ff: serial(auto)
> > > > > > e000-e00f: ide1
> > > > > > e400-e413: usb-uhci
> > > > > >
> > > > > > >
> > > > > > > # cat /resolve.conf
> > > > > >
> > > > > > search earthlink.net
> > > > > > nameserver 207.217.126.01
> > > > > > nameserver 207.217.77.82
> > > > > > nameserver207.217.120.83
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > # dselect
> > > > > >
> > > > > > No such file or directory
> > > > > >
> > > > > > >
> > > > > >
> > > > > > >
> > > > > > > # lsmod
> > > > > >
> > > > > > Module Size Used by
> > > > > > lockd 31176 1 (autoclean)
> > > > > > sunrpc 52964 1(autoclean)[lockd]
> > > > > > ppp 20236 0 (autoclean) (unused)
> > > > > > slhc 4504 0(autoclean) [ppp]
> > > > > > ne 6732 1(autoclean)
> > > > > > 8390 6072 0(autoclean)[ne]
> > > > > > appgart 18600 0(unused)
> > > > > > usb-uhci 19052 0(unused)
> > > > > > usbcore 42088 1[usb-uhci]
> > > > > >
> > > > > >
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > It is ok to just copy and paste them "as-is" and not try to format them on
> > > > > > > your own.
> > > > > > >
> > > > > >
> > > > > > Ihand transcribed them from the linux monitor to the mac. Sorry about bad
> > > > > > format.
> > > > > >
> > > > > > >
> > > > > > > *OR*
> > > > > > >
> > > > > > > If you can be sure there is no file in "/tmp" called "netstuff.txt" then
> > > > > > > you could append a ">> /tmp/netstuff.txt" to the end of each of the
> > > > > > > commands listed above and then "attach" the file "/tmp/netstuff.txt" to
> > > > > > > your e-mail message you send to the list.
> > > > > > >
> > > > > > > Also, could you take one of your working machines (macs I think you said
> > > > > > > you had) on your network that shares use of the router and go to the
> > > > > > > TCP/IP control panel and give me the following information that should be
> > > > > > > listed in that control panel of that mac:
> > > > > >
> > > > > > the Mac LC 475 has the following in the "TCP/IP" control panel:
> > > > > >
> > > > > > >
> > > > > > > IP Address :192.168.1.2
> > > > > > > Subnet Mask : 255.255.255.0
> > > > > >
> > > > > > > Gateway/router :192.168.1.1
> > > > > > > Domain Name Svrs: 207.217.126.81
> > > > > > > 207.217.77.82
> > > > > >
> > > > > > 207.217.120.83
> > > > > >
> > > > > > >
> > > > > > > Please also verify the network you have looks kind of like this:
> > > > > > > <!-- sorry about this html junk, I assume that the reason for the bad
> > > > > > > formatting of the previous messages was the use of a mail client by a
> > > > > > > sender that uses variable width fonts instead of fixed width fonts -->
> > > > > > >
> > > > > > > <pre>
> > > > > > > Mac1------|H|
> > > > > > > Mac2------|U|-- LINKSYS Router(?) --- DSL
> > > > > > > Linux Box-|B|
> > > > > > > </pre>
> > > > > > >
> > > > > >
> > > > > > The above is correct except for the hub, there is none. The cat-5 cables all go
> > > > > > directly
> > > > > > to the router. There is one cable from the router to the DSL modem ( or adapter)
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > Does your Linksys router (? Assuming it is a router) only use DHCP to hand
> > > > > > > out IP addresses to clients? Does it allow you to set static addresses
> > > > > > > too?
> > > > > >
> > > > > > There are 3 choices for the router configuration; manual, DHCP, and BOOTP.
> > > > > > I have always used "manual" in the past.
> > > > > >
> > > > > > > Are the static addresses in the same range as the DHCP assigned
> > > > > > > addresses or does their manual only allow static addresses to be outside a
> > > > > > > certain range?
> > > > > >
> > > > > > Not using DHCP, so I assign the addresses
> > > > > > 192.168.1.2 (mac #1)
> > > > > > 192.168.1.3 ( mac#2)
> > > > > > 192.168.1.4 ( linux box)
> > > > > >
> > > > > > > Does the router implement rules to disallow any passing of
> > > > > > > packets from IP addresses that it does not have listed as having a DHCP
> > > > > > > lease? Do both of your macs get their address via DHCP/BootP or are they
> > > > > > > static assignments?
> > > > > >
> > > > > > If static assignments are the same as manual, yes.
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Sorry to ask for all of this information again, but I would like to see it
> > > > > > > all after a reboot so we can be sure no other changes or oddness is in
> > > > > > > effect for this session.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > -ME
> > > > > > >
> > > > > > > On Wed, 28 Mar 2001, John F. Kohler wrote:
> > > > > > > > I started the netscape browser (version 4.75) and tried to pull up the address
> > > > > > > > of
> > > > > > > > the router (192.168.1.1) . On either macintosh also on the router, I get a
> > > > > > > > screen
> > > > > > > > with router setup information, and another screen indicating the router
> > > > > > > > is connected to the DSL line.
> > > > > > > >
> > > > > > > > On the Linux box I got the following:
> > > > > > > >
> > > > > > > > Netscape:Error
> > > > > > > >
> > > > > > > > A network Error occurred.
> > > > > > > > Unable to connect to server (TCP error. No route to host)
> > > > > > > > The server may be down or unreachable.
> > > > > > > >
> > > > > > > > Try connecting again later.
> > > > > > > >
> > > > > > > > -30-
> > > > > > > >
> > > > > > > > Trying to ping the router ( 192.168.1.1) from the linux box (192.168.1.4)
> > > > > > > >
> > > > > > > >
> > > > > > > > I got the following sentence over and over again
> > > > > > > >
> > > > > > > > >From 192.168.1.4: Destination host Unreachable.
> > > > > > > >
> > > > > > > > Trying to get the box to ping its own IP address was successful
> > > > > > > > time was from 50 usec to 350 usec.
> > > > > > > >
> > > > > > > > Trying to get the linux box to ping the macintosh (lc475) next to it, was
> > > > > > > > successful
> > > > > > > >
> > > > > > > > getting times from 1.6 to 4.7 miliseconds.
> > > > > > > >
> > > > > > > > Didn't try to ping the iMac, it was turned off.
> > > > > > > >
> > > > > > > > John
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Dustin Mollo wrote:
> > > > > > > >
> > > > > > > > > It seems this message got stuck in the mailing list queue, so I'm resending
> > > > > > > > > it. Enjoy!
> > > > > > > > >
> > > > > > > > > -Dustin
> > > > > > > > >
> > > > > > > > > ------------------------------------------------------------
> > > > > > > > >
> > > > > > > > > Date: Tue, 27 Mar 2001 11:20:16 -0800
> > > > > > > > > From: Mitch Petenaude <mrp at bolt.sonic.net>
> > > > > > > > > To: nblug-talk at lists.sonic.net
> > > > > > > > > Subject: Re: Deja Vu all over again
> > > > > > > > >
> > > > > > > > > Hi John,
> > > > > > > > >
> > > > > > > > > Have you set up your DNS server addresses? What is in /etc/resolv.conf?
> > > > > > > > >
> > > > > > > > > --Mitch
> > > > > > > > >
> > > > > > > > > On Tue, Mar 27, 2001 at 09:16:29AM -0800, John F. Kohler wrote:
> > > > > > > > > > Although I could ping addresses outside my network, neither
> > > > > > > > > > Netscape nor Lynx could display a page. So I am still
> > > > > > > > > > confused.
> > > > > > > > > >
> > > > > > > > > > I took a look at /etc/modules.conf
> > > > > > > > > >
> > > > > > > > > > alias parport_lowlever parport_pc
> > > > > > > > > > alias usb-controller usb-uhci
> > > > > > > > > > alias eth0 ne
> > > > > > > > > > options ne io=0x2a0 irq=10
> > > > > > > > > > ~
> > > > > > > > > > ~
> > > > > > > > > > ~
> > > > > > > > > > ~"modules.conf"4L, 109C"
> > > > > > > > > >
> > > > > > > > > > Here is /sbin/lsmod:
> > > > > > > > > >
> > > > > > > > > > Module Size Used by
> > > > > > > > > > ide-cd 23628` 0 (autoclean)
> > > > > > > > > > lockd 31176 1 (autoclean)
> > > > > > > > > > sunrpc 52964 1 (autoclean) [lockd]
> > > > > > > > > >
> > > > > > > > > > ppp 20236 0
> > > > > > > > > > (autoclean)[unused]
> > > > > > > > > > slhc 4504 0(autoclean) [ppp]
> > > > > > > > > > ne 6732 1 (autoclean)
> > > > > > > > > > 8390 6072 0 (autoclean )
> > > > > > > > > > [ne]
> > > > > > > > > > agpgart 18600 0 (unused)
> > > > > > > > > > usb-uhci 19052 0 (unused
> > > > > > > > > > usbcore 42088 1(usb-uhci)
> > > > > > > > > >
> > > > > > > > > > I tried /proc/interrupts: and got permission denied.
> > > > > > > > > >
> > > > > > > > > > John
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > ----- End forwarded message -----
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> >
> >
More information about the talk
mailing list