Re: Can't get on internet (10.2)

On Tue, 09 Jan 2007, in the Usenet newsgroup alt.os.linux.suse, in article
<OKOdnQwWzbCKxDnYnZ2dnUVZ_t2tnZ2d@xxxxxxxx>, Richard Kruse wrote:

That's when I got myself in trouble: For reasons we won't go into now,
I decided I should have used ext2 instead of ext3 for my / filesystem.

OK - we won't go into it, but ext3 is a better choice in most cases

After some futile attempts to change "manually", I decided to just do
a fresh install.

Should have only taken one command and one file edit - but anyway

*EXCEPT: NO INTERNET ACCESS!* Browser gives the "Cannot Connect..."
message for any site, regardless of whether I type in a regular URL or
a numeric one. Also cannot "ping", either # or URL, from a command line

So two applications agree that your network setup is wrong.

ping simply hangs, no response. I have to hit ctrl-c to get a prompt back.

ping could be a filtering problem (lots of people block ping because of
abuse), but ping should return after ten seconds unless you tried a
continuous ping (use 'ping -c3 hostname')

Internet is DSL via a router/modem/firewall (Zoom 5660), connected thru
ethernet (eth 10/100 built in to MB, identified as "Davicom ... (DEC
Tulip compatible)" All Zoom LAN addresses (local side) are in range
10.0.0.x. DHCP enabled; Zoom set as DHCP server.

Windows "ifconfig /all" gives:
+++++++++++++++++++++++++++++++++
Description . . . . . . . . . . . : DAVICOM 9102-Based PCI Fast
Ethernet Adapter
Physical Address. . . . . . . . . : 00-50-2C-09-D9-15

eth0 Link encap:Ethernet HWaddr 00:50:2C:09:D9:15

OK - you can talk to the hardware

inet addr:10.0.0.4 Bcast:255.255.255.255 Mask:255.255.255.0

The broadcast is B/S - should be 10.0.0.255 for that mask.

inet6 addr: fe80::250:2cff:fe09:d915/64 Scope:Link

You may want to disable IPv6 - it's probably not useful to you, but I
don't think it relates to this problem.

RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:46 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000

You can talk - but you can't hear anything. That's the problem

Interrupt:209 Base address:0xa400

I hate cards that use non-traditional interrupt numbers. That may be the
problem, but I have no idea how to verify it. You may want to try using
mii-tools (or ethtool) to investigate the NIC setup. Another thing to
look at is /var/log/messages relating to the network card.

SUSE "route -n" gives:

Fine

I'm stumped. I've read lots of man pages, and tried various network
settings, all to no avail. It's especially aggravating because it
worked once!

I can understand that.

Old guy
.