network card configuration

i'm a relative newbie to this so please bear with me. i'm trying to
install linux on an old dell optiplex 150. i've install several
different distros but all give me the same problem with the network
card. when i run ifconfig i get this:

eth0 link encap:Ethernet HWAddr 00:xx:xx:xx:xx:xx
inet6 addr: fe80::xxx:xxxx:xxxx:xxxx/64 Scope:link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX PACKETS:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:16
collisions:0 TXqueuelen:1000
RX bytes: 0 (0.0 b) TX bytes: 2808 (2.7 b)
Interrupt: 11 Base Address: 0xec80

i'm connected to a linksys router which my other windows and mac
machines can get to. but as you can see there is no gateway or ipv4
address. i edited ifcfg-eth0 to add the line GATEWAY=192.168.1.1 then
i brought the eth0 down and back up and it shows the above response to
ifconfig.

route -n shows the title captions and nothing else. i'm at a loss
here. any ideas or directions would be greatly appreciated.

thanks



arafye

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

arafye wrote:
> i'm a relative newbie to this so please bear with me. i'm trying to
> install linux on an old dell optiplex 150. i've install several
> different distros but all give me the same problem with the network
> card. when i run ifconfig i get this:
>
> eth0 link encap:Ethernet HWAddr 00:xx:xx:xx:xx:xx
> inet6 addr: fe80::xxx:xxxx:xxxx:xxxx/64 Scope:link
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX PACKETS:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:16 errors:0 dropped:0 overruns:0 carrier:16
> collisions:0 TXqueuelen:1000
> RX bytes: 0 (0.0 b) TX bytes: 2808 (2.7 b)
> Interrupt: 11 Base Address: 0xec80
>
> i'm connected to a linksys router which my other windows and mac
> machines can get to. but as you can see there is no gateway or ipv4
> address. i edited ifcfg-eth0 to add the line GATEWAY=192.168.1.1 then
> i brought the eth0 down and back up and it shows the above response to
> ifconfig.
>
> route -n shows the title captions and nothing else. i'm at a loss
> here. any ideas or directions would be greatly appreciated.
>
> thanks
>

hi

try to define a IPv4 address with:

ifconfig eth0 <address>

like
ifconfig eth0 192.168.1.2

to add your gateway, type

route add default gw 192.168.1.1

These settings won't be saved if you reboot.
So how your addresses are set up at startup depends of the distro you're
using (and its init scripts). What's your distribution?

Greets
Bram4

- --


BIG BROTHER IS WATCHING YOU
www.anti-dmca.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)

iD8DBQFCZCBHsv7ahDE9W98RAkLOAKC6JBH5+DwLkcXaavi6uV XK/F22hACfZc/c
6s/ynK/a1DKe/jQr8ctJIG4=
=9lH4
-----END PGP SIGNATURE-----

thanks. i ran both commands and the ifconfig table shows the address.
the route table now shows the titles with:
destination gateway genmask
192.168.1.0 0.0.0.0 255.255.255.0
0.0.0.0 192.168.1.1 0.0.0.0

and i still can't ping the gateway. i'm using mandrake 10 right now.

thanks again.

joe

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

arafye wrote:
> thanks. i ran both commands and the ifconfig table shows the address.
> the route table now shows the titles with:
> destination gateway genmask
> 192.168.1.0 0.0.0.0 255.255.255.0
> 0.0.0.0 192.168.1.1 0.0.0.0
>
> and i still can't ping the gateway. i'm using mandrake 10 right now.
>
> thanks again.
>
> joe
>

hi

one strange thing: there's no 127.0.0.0 in your routing table.
Is the lo interface up?
(ifconfig lo and look for 'UP LOOPBACK RUNNING')
if it's not:
ifconfig lo 127.0.0.1 up

but your route seems ok. could you post the output of
ifconfig
and
route -nv
? It might be useful

and have you tried pinging 127.0.0.1 and your own IP? (192.168.1.2 I
think...)

I don't know how Mandrake sets up networking. I suppose the init scripts
are in /etc/init.d or /etc/rc.d . But what scripts are executed for
networking... no idea.


- --


BIG BROTHER IS WATCHING YOU
www.anti-dmca.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)

iD8DBQFCZCbjsv7ahDE9W98RAjGCAKCJpvf1FWhro46AEk6auA g1E3CmAACcDwa+
1f2jTFj+K6qB8XMqW8/sc8M=
=gA9i
-----END PGP SIGNATURE-----

ok. ifconfig showed the lo up and running but i ran the command anyway.
route table still shows the same information. lo is not included. i'm
not married to mandrake this is the 3rd distro i tried. if your more
familar with anther i will gladly switch to get this to work. route
-nv shows the same information as route -n. however i got lazy and
didn't type in the last 2 columns. the complete route -n shows this:

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
0.0.0.0 192.168.1.1 0.0.0.0 ug
0 0 0 eth0

also i can ping lo. (i don't know if that matters or not). the complete
ifconfig now shows:

eth0 link encap:Ethernet HWAddr 00:xx:xx:xx:xx:xx
inet addr: 192.168.1.99 Bcast 192.168.1.255 Mask 255.255.255.0
inet6 addr: fe80::xxx:xxxx:xxxx:xxxx/64 Scope:link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX PACKETS:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:82 errors:0 dropped:0 overruns:0 carrier:82
collisions:0 TXqueuelen:1000
RX bytes: 0 (0.0 b) TX bytes: 2808 (2.7 b)
Interrupt: 11 Base Address: 0xec80

lo link encap: local loopback
inet addr: 127.0.01 Mask: 255.0.0.0
inet6 addr: ::1/128 Scope:host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX PACKETS:86039 errors:0 dropped:0 overruns:0 frame:0
TX packets:86039 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 TXqueuelen:1000
RX bytes: 6710236 (6.3 b) TX bytes: 6710236 (6.3 b)

i'm wondering if it has something to do with the carrier number in
eth0. what exactly does that mean? do you have anyother ideas?

thanks,
Interrupt: 11 Base Address: 0xec80

On 18 Apr 2005 15:25:44 -0700, arafye wrote:
> ok. ifconfig showed the lo up and running but i ran the command anyway.
> route table still shows the same information. lo is not included.

That is normal for mandrake 10.x
> eth0 link encap:Ethernet HWAddr 00:xx:xx:xx:xx:xx
> inet addr: 192.168.1.99 Bcast 192.168.1.255 Mask 255.255.255.0
> inet6 addr: fe80::xxx:xxxx:xxxx:xxxx/64 Scope:link
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX PACKETS:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:82 errors:0 dropped:0 overruns:0 carrier:82
> collisions:0 TXqueuelen:1000
> RX bytes: 0 (0.0 b) TX bytes: 2808 (2.7 b)
> Interrupt: 11 Base Address: 0xec80

> i'm wondering if it has something to do with the carrier number in
> eth0. what exactly does that mean? do you have anyother ideas?

click up a terminal
su -l root
/sbin/mii-tool -v

and see if you have _link ok_, to verify connection to other nic.

You might want to power cycle whatever is hooked to other end of
ethernet cable. Cable modem modems for example will only talk to nic
it saw when the modem was last powered up.

You can disable IPV6 until everything works then enable it.

/etc/modprobe.conf add alias net-pf-10 off
/etc/modules.conf add alias net-pf-10 off
/etc/sysconfig/network add NETWORKING_IPV6=no

Be sure to add a carriage after the new line

Here is my network settings.
$ cat /etc/sysconfig/network
HOSTNAME=wb.home.invalid <==== my host and domain
NETWORKING=yes
GATEWAY=192.168.2.1
GATEWAYDEV=eth0
NETWORKING_IPV6=no

$ head /etc/hosts
127.0.0.1 localhost
192.168.2.1 fw.home.invalid fw
192.168.2.10 wb.home.invalid wb <==== my host.domain ip addy
192.168.2.12 wb1.home.invalid wb1
192.168.2.22 wb4.home.invalid wb4

$ cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=static
IPADDR=192.168.2.10 <==== ip addy for nic/node
NETMASK=255.255.255.0
NETWORK=192.168.2.0
BROADCAST=192.168.2.255
ONBOOT=yes
METRIC=10
MII_NOT_SUPPORTED=yes <=== do not change your value. Depends on nic

When you change a netwrork file, you can do a
service network restart to test.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

arafye wrote:
> ok. ifconfig showed the lo up and running but i ran the command anyway.
> route table still shows the same information. lo is not included. i'm
> not married to mandrake this is the 3rd distro i tried. if your more
> familar with anther i will gladly switch to get this to work. route
> -nv shows the same information as route -n. however i got lazy and
> didn't type in the last 2 columns. the complete route -n shows this:
>
> 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
> 0.0.0.0 192.168.1.1 0.0.0.0 ug
> 0 0 0 eth0
>
> also i can ping lo. (i don't know if that matters or not). the complete
> ifconfig now shows:
>
> eth0 link encap:Ethernet HWAddr 00:xx:xx:xx:xx:xx
> inet addr: 192.168.1.99 Bcast 192.168.1.255 Mask 255.255.255.0
> inet6 addr: fe80::xxx:xxxx:xxxx:xxxx/64 Scope:link
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX PACKETS:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:82 errors:0 dropped:0 overruns:0 carrier:82
> collisions:0 TXqueuelen:1000
> RX bytes: 0 (0.0 b) TX bytes: 2808 (2.7 b)
> Interrupt: 11 Base Address: 0xec80
>
> lo link encap: local loopback
> inet addr: 127.0.01 Mask: 255.0.0.0
> inet6 addr: ::1/128 Scope:host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX PACKETS:86039 errors:0 dropped:0 overruns:0 frame:0
> TX packets:86039 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 TXqueuelen:1000
> RX bytes: 6710236 (6.3 b) TX bytes: 6710236 (6.3 b)
>
> i'm wondering if it has something to do with the carrier number in
> eth0. what exactly does that mean? do you have anyother ideas?
>
> thanks,
> Interrupt: 11 Base Address: 0xec80
>
Well, well, well...
Interrupt 11 base address 0xEC80 is the IRQ and the address of the card...

What kind of network card is in your optiplex 150 ?
It's always very simple to say "it's the card's fault", but there might
indeed be a problem. Maybe looking at dmesg might help. Or if you see
something interesting in the logs...

And did it work with other distributions?

You could try a broadcast ping
ping -b 192.168.1.255
too see if something answers, but I don't think this will be any useful
at all...

Personally, I _love_ Slackware, but it might not be your taste. It's
kind of "The Standard All-Purpose Configuration Tool is 'vim'". But I
think text configuration files are the heart of *every* linux distrib ;-)

Your problem is weird, or we're just looking past a tiny stupid mistake
without seeing it...

bram4

- --


BIG BROTHER IS WATCHING YOU
www.anti-dmca.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)

iD8DBQFCZDpPsv7ahDE9W98RAhYpAJwNerM20sDZTiLmji6wPy fB/4vLvwCggGXA
rysI+IXbPITsJyIUWmsX960=
=B5Ex
-----END PGP SIGNATURE-----

k. well here's the answer to both questions. first, the system ran
fine under older versions of linux like rh 7. mandrake 7 etc. i use the
machine to experiment with and learn linux so i don't hesitate to drop
the distro and try something new. under the new versions suse 9.1
mandrake 10. debian (forget the number) it doesn't work. so back to
the commands -

/sbin/mii-tool -v gave me:

basic status: no link
(included other stuff but i think this is the important info if you
want i'll type it out later)

i ran $ cat /etc/sysconfig/network - got this:

NETWORKING=yes
(this was the only line)

$ head /etc/hosts - gave me:

127.0.0.1 localhost
(only line)

$ cat /etc/sysconfig/network-scripts/ifcfg-eth0 - returns:
DEVICE=eth0
BOOTPROTO=dhcp
NETMASK=255.255.255.0
ONBOOT=yes
METRIC=10
GATEWAY=192.168.1.1

on other note. this computer has been hooked up to the network since
there was a network. the network adapter is a 3com 3c920 integrated
fast ethernet controller (3c905c-tx compatible).

i wasn't sure if you wanted me to change my files to match yours or if
you were providing them for a comparison. neverless, i didn't change
them. if you want i'll try that next.

thanks again for the help

joe

arafye wrote:
> i'm a relative newbie to this so please bear with me. i'm trying to
> install linux on an old dell optiplex 150. i've install several
> different distros but all give me the same problem with the network
> card. when i run ifconfig i get this:
>
> eth0 link encap:Ethernet HWAddr 00:xx:xx:xx:xx:xx
> inet6 addr: fe80::xxx:xxxx:xxxx:xxxx/64 Scope:link
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX PACKETS:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:16 errors:0 dropped:0 overruns:0 carrier:16
> collisions:0 TXqueuelen:1000
> RX bytes: 0 (0.0 b) TX bytes: 2808 (2.7 b)
> Interrupt: 11 Base Address: 0xec80
>
> i'm connected to a linksys router which my other windows and mac
> machines can get to. but as you can see there is no gateway or ipv4
> address. i edited ifcfg-eth0 to add the line GATEWAY=192.168.1.1
then
> i brought the eth0 down and back up and it shows the above response
to
> ifconfig.
>
> route -n shows the title captions and nothing else. i'm at a loss
> here. any ideas or directions would be greatly appreciated.

I've read the other posts. Nothing wrong there.

What caught my eye is this:
TX packets:16 errors:0 dropped:0 overruns:0 carrier:16

You've not mentioned what this nic's patch cord is plugged into. These
days I would expect a switch. Much less likely, I would think "hub"
(they're hard to come by these days).

If it's plugged into a "modem" (dsl/cable) not much difference re: my
concern.

The carrier is the _base_ electrical signal upon which all other
signals are built. If this produces errors (basically, where's the
carrier?), you're SOL.

I would investigate hardware problems before going on. Bad patch cord?
Bad upstream plug? Bad nic plug? Bad nic? Another device that you
can test this with? What if you switch cords with a "working" box just
on the host end? Just on the upstream end?

Checked for firmware and driver updates? This really seems to be a
physical or link layer problem at this stage.

May explain why no distro can "make it work";(

good luck,
prg

On 18 Apr 2005 16:20:31 -0700, arafye wrote:
> k. well here's the answer to both questions. first, the system ran
> fine under older versions of linux like rh 7. mandrake 7 etc. i use the
> machine to experiment with and learn linux so i don't hesitate to drop
> the distro and try something new. under the new versions suse 9.1
> mandrake 10. debian (forget the number) it doesn't work. so back to
> the commands -
>
> /sbin/mii-tool -v gave me:
>
> basic status: no link

Yep, you have a cabling problem or a bad nic or two or mandrake did
not load the nic's driver module. Not much is going to work until that
turns _link ok_

> i ran $ cat /etc/sysconfig/network - got this:
>
> NETWORKING=yes
> (this was the only line)
>
> $ head /etc/hosts - gave me:
>
> 127.0.0.1 localhost
> (only line)
>
> $ cat /etc/sysconfig/network-scripts/ifcfg-eth0 - returns:
> DEVICE=eth0
> BOOTPROTO=dhcp
> NETMASK=255.255.255.0
> ONBOOT=yes
> METRIC=10
> GATEWAY=192.168.1.1
>
> on other note. this computer has been hooked up to the network since
> there was a network. the network adapter is a 3com 3c920 integrated
> fast ethernet controller (3c905c-tx compatible).

Well, that would seem to indicate that the cable and nics are ok
assuming you have not messed with them or the pets have not chewed on
the cable.

Next boot verify, Plug-n-Play (PNP) os is false/off/no in the PC bios.

> i wasn't sure if you wanted me to change my files to match yours or if
> you were providing them for a comparison. neverless, i didn't change
> them. if you want i'll try that next.

Ok, you have
> BOOTPROTO=dhcp
which indicates some other node on your network is going to hand out dhcp
leases to your machine.

If this node is to run with static ip addressing, then you might want
to use my files as examples, but set the ip address to whatever you
like.

And just for fun, when you are logged in as root, run both of these commands.
chkconfig tmdns off
chkconfig --del tmdns