After I installed the QNX 6.2, I found the TCP/IP is not correctly
configured. I set the IP 130.9.15.148, mask
255.255.240.0, and I can ping my self by pinging 127.0.0.1, or
130.9.15.148. However, I cannot ping any other machine in the same
subnet, like 130.9.15.146. Neither can other machine ping this QNX
machine.
The net cmd is set to:
set(IONET-CMD io-net -pttcpip)
I attempted to slay the io-net but don’t know how to reload the driver,
since I don’t know which driver corresponds to the NIC I use (D-link).
I’ll try with another NIC, maybe Realtek 8139, which is always
successful with my previous configuration. But the weird thing is that
this NIC is recognized by the QNX, and IO-NET is also started. Only the
TCP/IP with other machine is problematic. The phycial error can be
excluded, because under Windows, all the machines can communicate with
same hardware.
Yijun Zou <yjzou@sina.com> wrote:
After I installed the QNX 6.2, I found the TCP/IP is not correctly
configured. I set the IP 130.9.15.148, mask
255.255.240.0, and I can ping my self by pinging 127.0.0.1, or
130.9.15.148. However, I cannot ping any other machine in the same
subnet, like 130.9.15.146. Neither can other machine ping this QNX
machine.
Are the other machines on the subnet also using a netmask of
255.255.240.0?
-David
QNX Training Services
http://www.qnx.com/services/training/
Please followup in this newsgroup if you have further questions.
“Yijun Zou” <yjzou@sina.com> wrote in message
news:ccejid$olu$1@inn.qnx.com…
After I installed the QNX 6.2, I found the TCP/IP is not correctly
configured. I set the IP 130.9.15.148, mask
255.255.240.0, and I can ping my self by pinging 127.0.0.1, or
130.9.15.148. However, I cannot ping any other machine in the same
subnet, like 130.9.15.146. Neither can other machine ping this QNX
machine.
The net cmd is set to:
set(IONET-CMD io-net -pttcpip)
What does nicinfo says. Are packet being transmisted/received?
I attempted to slay the io-net but don’t know how to reload the driver,
since I don’t know which driver corresponds to the NIC I use (D-link).
I’ll try with another NIC, maybe Realtek 8139, which is always
successful with my previous configuration. But the weird thing is that
this NIC is recognized by the QNX, and IO-NET is also started. Only the
TCP/IP with other machine is problematic. The phycial error can be
excluded, because under Windows, all the machines can communicate with
same hardware.
Yes, nicinfo sometimes displays the MAC of the NIC, sometimes not ( just 12
bit of 0). Seems this NIC is not correctly supported by QNX.
The nicinfo also tells this card is a VT86C100A VIA Ethernet ctrller. I
swapped it with a RTL 8139D NIC and then no such problem.
thanks for your hints.
Yijun
“Mario Charest” <nowheretobefound@8thdimension.com> дÈëÏûÏ¢ÐÂÎÅ
:ccf857$a4d$1@inn.qnx.com…
“Yijun Zou” <> yjzou@sina.com> > wrote in message
news:ccejid$olu$> 1@inn.qnx.com> …
After I installed the QNX 6.2, I found the TCP/IP is not correctly
configured. I set the IP 130.9.15.148, mask
255.255.240.0, and I can ping my self by pinging 127.0.0.1, or
130.9.15.148. However, I cannot ping any other machine in the same
subnet, like 130.9.15.146. Neither can other machine ping this QNX
machine.
The net cmd is set to:
set(IONET-CMD io-net -pttcpip)
What does nicinfo says. Are packet being transmisted/received?
I attempted to slay the io-net but don’t know how to reload the driver,
since I don’t know which driver corresponds to the NIC I use (D-link).
I’ll try with another NIC, maybe Realtek 8139, which is always
successful with my previous configuration. But the weird thing is that
this NIC is recognized by the QNX, and IO-NET is also started. Only the
TCP/IP with other machine is problematic. The phycial error can be
excluded, because under Windows, all the machines can communicate with
same hardware.
\