Network problem.

Hello all,
I’m here first time and of course have question. Networking problem.
My NIC - 3Com EtherLink XL PCI Combo (3com900). After first system
start, there was en0. I configured my network and what returned ping
after pinging my network server:
ping: sendto: Host is down
ping: wrote 192.168.0.1 64 chars, ret=-1

And that’s not true because this host was running. So, i read a little
documentation and wrote the following commands:
umount /dev/io-net/en0 (ifconfig -a showed me only loopback interface)
io-net -d el900 -p tcpip (ifconfig -a showed loopback and en0
interfaces)
ifconfig en0 192.168.0.99 netmask 255.255.255.0
route add default 192.168.0.1
After this ifconfig -a printed info about correctly configured en0 - as
i wanted.
But pinging 192.168.0.1 still give me the same answer! What is wrong?
Waiting for answer :slight_smile:
Greetings


P.S.
Sorry for my english. Please answer on newsgroup and e-mail too.

“Piotr Gajewski” <gajos@REMOVE-IT.piast.t19.ds.pwr.wroc.pl> wrote in message
news:a0hpj7$1po$1@inn.qnx.com

Hello all,
I’m here first time and of course have question. Networking problem.
My NIC - 3Com EtherLink XL PCI Combo (3com900). After first system
start, there was en0. I configured my network and what returned ping
after pinging my network server:
ping: sendto: Host is down
ping: wrote 192.168.0.1 64 chars, ret=-1

And that’s not true because this host was running. So, i read a little
documentation and wrote the following commands:

“Host is down” usually means that an arp on an IP failed - usually this
because the physical layer isn’t working properly. When you do a nicinfo,
does the MAC address etc, all check out ok? You should post the contents
of pci -vvv (just the network related section) and nicinfo output. The
hardware group may have more insight.

-Adam

You just wroted…

My NIC - 3Com EtherLink XL PCI Combo (3com900). After first system
start, there was en0. I configured my network and what returned ping
after pinging my network server:
ping: sendto: Host is down
ping: wrote 192.168.0.1 64 chars, ret=-1
And that’s not true because this host was running. So, i read a
little
documentation and wrote the following commands:
“Host is down” usually means that an arp on an IP failed - usually
this
because the physical layer isn’t working properly. When you do a
nicinfo,
does the MAC address etc, all check out ok? You should post the
contents
of pci -vvv (just the network related section) and nicinfo output.
The
hardware group may have more insight.
Here you have nicinfo output:

3COM (90x) 10BASE-T/100BASE-TX Ethernet Controller
Physical Node ID … 006008 4939C0
Current Physical Node ID … 006008 4939C0
Media Rate … 0 kb/s half-duplex UTP
MTU … 1514
Lan … 0
I/O Port Range … 0xD000 → 0xD03F
Hardware Interrupt … 0xA
Promiscuous … Disabled
Multicast … Enabled
Total Packets Txd OK … 9
Total Packets Txd Bad … 0
Total Packets Rxd OK … 0
Total Rx Errors … 0
Total Bytes Txd … 558
Total Bytes Rxd … 0
Tx Collision Errors … 0
Tx Collisions Errors (aborted) … 0
Carrier Sense Lost on Tx … 0
FIFO Underruns During Tx … 0
Tx deferred … 0
Out of Window Collisions … 0
FIFO Overruns During Rx … 0
Alignment errors … 0
CRC errors … 0
So, here everything is ok - i think.
And here is pci output:
PCI version = 2.10

Class = Mass Storage (IDE)
Vendor ID = 1106h, VIA Technologies Inc
Device ID = 571h, VT82C586/686 PCI IDE Controller
PCI index = 0h
PCI IO Address = ffa0h enabled
PCI Int Pin = NC
Interrupt line = no connection
[cut]
Class = Network (Ethernet)
Vendor ID = 10b7h, 3Com Corporation
Device ID = 9001h, 3C900-COMBO Fast Etherlink XL PCI Combo NIC
PCI index = 0h
PCI IO Address = d000h enabled
PCI Expansion ROM = dfff0000h disabled
PCI Int Pin = INT A
Interrupt line = 10
[cut]
So, what are you proposing? What is the explanation of my problem?
Please answer fast…
Greetings for all in brand new 2002 :slight_smile:
gajos

Piotr Gajewski <gajos@remove-it.piast.t19.ds.pwr.wroc.pl> wrote:

3COM (90x) 10BASE-T/100BASE-TX Ethernet Controller
Physical Node ID … 006008 4939C0
Current Physical Node ID … 006008 4939C0
Media Rate … 0 kb/s half-duplex UTP

There is your problem. Is this a 3C900 card?

chris


Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

Chris McKillop <cdm@qnx.com> wrote:

Piotr Gajewski <> gajos@remove-it.piast.t19.ds.pwr.wroc.pl> > wrote:
3COM (90x) 10BASE-T/100BASE-TX Ethernet Controller
Physical Node ID … 006008 4939C0
Current Physical Node ID … 006008 4939C0
Media Rate … 0 kb/s half-duplex UTP


There is your problem. Is this a 3C900 card?

Just to be clear, the problem is the Media Rate being 0.

chris


Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

U¿ytkownik “Chris McKillop” <cdm@qnx.com> napisa³ w wiadomo¶ci
news:a115fo$c25$4@nntp.qnx.com

3COM (90x) 10BASE-T/100BASE-TX Ethernet Controller
Physical Node ID … 006008 4939C0
Current Physical Node ID … 006008 4939C0
Media Rate … 0 kb/s half-duplex UTP
There is your problem. Is this a 3C900 card?
Yes, it is a 3c900 card.
Just to be clear, the problem is the Media Rate being 0.
I think the same… but in documentation

http://support.qnx.com/support/docs/neutrino/utilities/n/nicinfo.html
is the same rereturn for media rate, and i thought that this is ok.
My cable is BNC. Maybe this is a problem? Do i need some “special”
configuration for that?
Greetings,
gajos

“Piotr Gajewski” <gajos@REMOVE-IT.piast.t19.ds.pwr.wroc.pl> wrote in message
news:a1196l$jfh$1@inn.qnx.com

U¿ytkownik “Chris McKillop” <> cdm@qnx.com> > napisa³ w wiadomo¶ci
news:a115fo$c25$> 4@nntp.qnx.com> …
3COM (90x) 10BASE-T/100BASE-TX Ethernet Controller
Physical Node ID … 006008 4939C0
Current Physical Node ID … 006008 4939C0
Media Rate … 0 kb/s half-duplex UTP
There is your problem. Is this a 3C900 card?
Yes, it is a 3c900 card.
Just to be clear, the problem is the Media Rate being 0.
I think the same… but in documentation
http://support.qnx.com/support/docs/neutrino/utilities/n/nicinfo.html
is the same rereturn for media rate, and i thought that this is ok.

The example is just illustrating what the format of the data from nicinfo
would look like.

My cable is BNC. Maybe this is a problem? Do i need some “special”
configuration for that?

Try specifying the option to your driver “connector=0” to force BNC media
and perhaps turn off multicast using “multicast=0”

-Adam

My cable is BNC. Maybe this is a problem? Do i need some “special”
configuration for that?

Try specifying the option to your driver “connector=0” to force BNC media
and perhaps turn off multicast using “multicast=0”

Actually the option is nomulticast. My feeling is that our el900 driver will
not work with your card. The 3C900 has a different physical layer interface
then the other 900 series devices.

chris


Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

Chris McKillop <cdm@qnx.com> wrote:

My cable is BNC. Maybe this is a problem? Do i need some “special”
configuration for that?

Try specifying the option to your driver “connector=0” to force BNC media
and perhaps turn off multicast using “multicast=0”


Actually the option is nomulticast. My feeling is that our el900 driver will
not work with your card. The 3C900 has a different physical layer interface
then the other 900 series devices.

Good point, however there is no harm in trying.

Erick.


chris


Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

Did you get this working? Some of the 6.1 NIC drivers had problems
auto detecting the media rate – you had to hard code the media
rate on the command line. But some of the 6.1 NIC drivers didn’t
support the media rate command line arg. Quite a mess – we hope
the 6.2 drivers will be less troublesome.

Piotr Gajewski <gajos@remove-it.piast.t19.ds.pwr.wroc.pl> wrote:

You just wroted…
My NIC - 3Com EtherLink XL PCI Combo (3com900). After first system
start, there was en0. I configured my network and what returned ping
after pinging my network server:
ping: sendto: Host is down
ping: wrote 192.168.0.1 64 chars, ret=-1
And that’s not true because this host was running. So, i read a
little
documentation and wrote the following commands:
“Host is down” usually means that an arp on an IP failed - usually
this
because the physical layer isn’t working properly. When you do a
nicinfo,
does the MAC address etc, all check out ok? You should post the
contents
of pci -vvv (just the network related section) and nicinfo output.
The
hardware group may have more insight.
Here you have nicinfo output:
3COM (90x) 10BASE-T/100BASE-TX Ethernet Controller
Physical Node ID … 006008 4939C0
Current Physical Node ID … 006008 4939C0
Media Rate … 0 kb/s half-duplex UTP
MTU … 1514
Lan … 0
I/O Port Range … 0xD000 → 0xD03F
Hardware Interrupt … 0xA
Promiscuous … Disabled
Multicast … Enabled
Total Packets Txd OK … 9
Total Packets Txd Bad … 0
Total Packets Rxd OK … 0
Total Rx Errors … 0
Total Bytes Txd … 558
Total Bytes Rxd … 0
Tx Collision Errors … 0
Tx Collisions Errors (aborted) … 0
Carrier Sense Lost on Tx … 0
FIFO Underruns During Tx … 0
Tx deferred … 0
Out of Window Collisions … 0
FIFO Overruns During Rx … 0
Alignment errors … 0
CRC errors … 0
So, here everything is ok - i think.
And here is pci output:
PCI version = 2.10

Class = Mass Storage (IDE)
Vendor ID = 1106h, VIA Technologies Inc
Device ID = 571h, VT82C586/686 PCI IDE Controller
PCI index = 0h
PCI IO Address = ffa0h enabled
PCI Int Pin = NC
Interrupt line = no connection
[cut]
Class = Network (Ethernet)
Vendor ID = 10b7h, 3Com Corporation
Device ID = 9001h, 3C900-COMBO Fast Etherlink XL PCI Combo NIC
PCI index = 0h
PCI IO Address = d000h enabled
PCI Expansion ROM = dfff0000h disabled
PCI Int Pin = INT A
Interrupt line = 10
[cut]
So, what are you proposing? What is the explanation of my problem?
Please answer fast…
Greetings for all in brand new 2002 > :slight_smile:
gajos


Kirk Russell Bridlewood Software Testers Guild