Hi, every one,
I have two compter – A(installed TurboLinux,ip:198.9.200.1,node1) and
B(installed QNX 4.25, ip:198.9.200.2, node21). They were installed same type
ethernet interface cards (3Com EtherLink III 3C509TP), also I set B as DNS
server. When I ping 198.9.200.1 on computer B. I found something on computer
A with tcpdump utility as following:
tcpdump -e
tcpdump: listening on eth0
21:14:48.495429 0:20:af:12:87:c Broadcast arp 60: arp who-has node1 tell node21.fxd.com
21:14:48.495462 0:20:af:12:87:c Broadcast arp 60: arp who-has node1 tell node21.fxd.com
When I ping 198.9.200.2 on computer A. I found something on computer A with
tcpdump utility as following:
tcpdump -e
tcpdump: listening on eth0
21:17:44.118826 0:20:af;33:3d:57 0:20:af:12:87:c ip 98: node1 > node21.fxd.com : icmp :echo request
21:17:44.118866 0:20:af;33:3d:57 0:20:af:12:87:c ip 98: node1 > node21.fxd.com : icmp :echo request
In brief, they can’t communication normally, I don’t know whether or not
that the NIC driver Net.ether509 can not support the NIC completely. Or is
there any other reasons?
Thank you!
Hi, every one,
I have two compter – A(installed TurboLinux,ip:198.9.200.1,node1) and
B(installed QNX 4.25, ip:198.9.200.2, node21). They were installed same type
ethernet interface cards (3Com EtherLink III 3C509TP), also I set B as DNS
server. When I ping 198.9.200.1 on computer B. I found something on computer
A with tcpdump utility as following:
tcpdump -e
tcpdump: listening on eth0
21:14:48.495429 0:20:af:12:87:c Broadcast arp 60: arp who-has node1 tell node21.fxd.com
21:14:48.495462 0:20:af:12:87:c Broadcast arp 60: arp who-has node1 tell node21.fxd.com
When I ping 198.9.200.2 on computer A. I found something on computer A with
tcpdump utility as following:
tcpdump -e
tcpdump: listening on eth0
21:17:44.118826 0:20:af;33:3d:57 0:20:af:12:87:c ip 98: node1 node21.fxd.com : icmp :echo request
21:17:44.118866 0:20:af;33:3d:57 0:20:af:12:87:c ip 98: node1 node21.fxd.com : icmp :echo request
In brief, they can’t communication normally, I don’t know whether or not
that the NIC driver Net.ether509 can not support the NIC completely. Or is
there any other reasons?
If you are seeing packets from the QNX box on the wire, then it isn’t
a problem with the Net.ether509 driver. (Though, from my understanding
the 509 isn’t the best of cards.)
More likely there is something in the TCP/IP setup that isn’t working
quite right. When you configured the interfaces (ifconfig) what netmask
did you use for them? Non-matching netmasks can cause a problem. I don’t
know what else might be the problem, but it is likely TCP/IP config.
But my another 509 card is working rightly, the two computers installed 509
NIC have same configurations.( I have computer C who acts client like
computer B, installed QNX 4.25)
fxd <> xdfang@public.cc.jl.cn> > wrote:
Hi, every one,
I have two compter – A(installed TurboLinux,ip:198.9.200.1,node1) and
B(installed QNX 4.25, ip:198.9.200.2, node21). They were installed same
type
ethernet interface cards (3Com EtherLink III 3C509TP), also I set B as
DNS
server. When I ping 198.9.200.1 on computer B. I found something on
computer
A with tcpdump utility as following:
tcpdump -e
tcpdump: listening on eth0
21:14:48.495429 0:20:af:12:87:c Broadcast arp 60: arp who-has node1 tell node21.fxd.com
21:14:48.495462 0:20:af:12:87:c Broadcast arp 60: arp who-has node1 tell node21.fxd.com
When I ping 198.9.200.2 on computer A. I found something on computer A
with
tcpdump utility as following:
tcpdump -e
tcpdump: listening on eth0
21:17:44.118826 0:20:af;33:3d:57 0:20:af:12:87:c ip 98: node1 node21.fxd.com : icmp :echo request
21:17:44.118866 0:20:af;33:3d:57 0:20:af:12:87:c ip 98: node1 node21.fxd.com : icmp :echo request
In brief, they can’t communication normally, I don’t know whether or not
that the NIC driver Net.ether509 can not support the NIC completely. Or
is
there any other reasons?
If you are seeing packets from the QNX box on the wire, then it isn’t
a problem with the Net.ether509 driver. (Though, from my understanding
the 509 isn’t the best of cards.)
More likely there is something in the TCP/IP setup that isn’t working
quite right. When you configured the interfaces (ifconfig) what netmask
did you use for them? Non-matching netmasks can cause a problem. I don’t
know what else might be the problem, but it is likely TCP/IP config.
On the QNX node do you load TCP/IP - Net like this:
Net
Net.ether509
netmap
Socket
ifconfig …
My bet is the netmap has the wrong MAC for this card - TCP/IP uses
the MAC from the netmap for ARP requests.
Change the order to:
Net
Net.ether509
Socket
ifconfig
netmap
Also, fix the MAC in the netmap file.
Jay
David Gibbs wrote in message <934vqm$b12$7@nntp.qnx.com>…
fxd <> xdfang@public.cc.jl.cn> > wrote:
Hi, every one,
I have two compter – A(installed TurboLinux,ip:198.9.200.1,node1) and
B(installed QNX 4.25, ip:198.9.200.2, node21). They were installed same
type
ethernet interface cards (3Com EtherLink III 3C509TP), also I set B as
DNS
server. When I ping 198.9.200.1 on computer B. I found something on
computer
A with tcpdump utility as following:
tcpdump -e
tcpdump: listening on eth0
21:14:48.495429 0:20:af:12:87:c Broadcast arp 60: arp who-has node1 tell node21.fxd.com
21:14:48.495462 0:20:af:12:87:c Broadcast arp 60: arp who-has node1 tell node21.fxd.com
When I ping 198.9.200.2 on computer A. I found something on computer A
with
tcpdump utility as following:
tcpdump -e
tcpdump: listening on eth0
21:17:44.118826 0:20:af;33:3d:57 0:20:af:12:87:c ip 98: node1 node21.fxd.com : icmp :echo request
21:17:44.118866 0:20:af;33:3d:57 0:20:af:12:87:c ip 98: node1 node21.fxd.com : icmp :echo request
In brief, they can’t communication normally, I don’t know whether or not
that the NIC driver Net.ether509 can not support the NIC completely. Or
is
there any other reasons?
If you are seeing packets from the QNX box on the wire, then it isn’t
a problem with the Net.ether509 driver. (Though, from my understanding
the 509 isn’t the best of cards.)
More likely there is something in the TCP/IP setup that isn’t working
quite right. When you configured the interfaces (ifconfig) what netmask
did you use for them? Non-matching netmasks can cause a problem. I don’t
know what else might be the problem, but it is likely TCP/IP config.
If you are seeing packets from the QNX box on the wire, then it isn’t
a problem with the Net.ether509 driver. (Though, from my understanding
the 509 isn’t the best of cards.)
One my experience with Net.ether509, QNX4.24, TCPIP4.24 :
after two-three week of pernament operation, tcp/ip has got stuck.
Restart of tcp/ip does not help, but restart of Net.ether509 and
tcp/ip helps.
=> recommendation: use another card, e.g. NE2000 compatible