hello

[Janina Sajka]

I've edited this message ...

Eric Kosten writes:
> Hello Janina:
> Eric Kosten writing with the results of the output of the commands that you
> gave me.  The output was to large for the list and has been sent to the
> moderator.
i
Yes, there's a message limitet at the Speakup list. You'll need to edit
mail sent to the list--or break it up into multiple messages. I am
posting this response to the list, because others may benefit.

> here goes:
> 
> Thanks so much for helping! Here is what I found:
> 
> first the results of those commands:
> 
> modprobe:
> 
> alias eth0 b44

There's your ethernet device driver.
I've deleted it, but I see you're using a DEC Talk Express and have a
Sound Blaster type sound card, plus much more.

> lsmod:

The relevant output is:

> ipv6 232705 8
> b44 22341 0
> mii 4673 1 b44

Since I see no iptables related modules, I surmise you did not enable
the firewall. In other words, you selected to not use it, as it's on by
default.

> 
> ifconfig:
> eth0 Link encap:Ethernet HWaddr 00:0C:6E:55:D8:00
> inet addr:192.168.0.101 Bcast:192.168.0.255 Mask:255.255.255.0

This machine's iIP address is 192.168.0.101, which sounds like an
address supplied by your router via dhcp. Nothing wrong with that.

> lastly:
> 
> the command:
> 
> route add default gw 192.168.1.1 eth0 produces:

Not sure why you would choose to say your gateway is at 192.168.1.1.
Where did you get that address? Given the IP address ifconfig shows,
it's far more likely something in 192.168.0.X, probably 192.168.0.1 or
192.168.0.254.

But, you shouldn't have to guess. If your router is supplying data over
dhcp, it will supply the gateway address as well. You skipped a step in
the message I sent. You do not provide the output of:

route

So, as root, do the following:

service network restart

and then run route. The last line of output should provide your gateway
address. You should be able to ping that address.

				Janina