“David Gibbs” <dagibbs@qnx.com> wrote in message
news:970rhl$rs1$1@nntp.qnx.com…
Chris Nasr <> cnasr@mechtronix.ca> > wrote:
Hello everyone,
well just to let everybody know the problem no longer exists, although I
can’t
say exactly why at the moment, (I’ll spend more time on that when I can)
I do
know that it had something to do with running “netmap -f” in the sysinit
file.
When I comment it out everything works just as it should (leading me to
believe
this problem always existed, I just never noticed before because I never
created nodes over 2)If you had an incorrect netmap file, then the netmap -f will probably
break
things. It tells Net about what the physical hardware address for your
node
is, then Socket asks Net for this information. If this machine has had
different identities, and you didn’t update the netmap with appropriate
information each time you changed, that could cause a problem.David,
I had lots of discussion by email with Chris, he assures me the
netmap file is empty (totaly blank). This is very odd i don’t understand
the logic behind this, it smells fishy.
In one of my email exchange with Chris we confirm that the arp
on Windows show the wrong MAC address for the node
he was trying to talk to. I suspected another machine with
the same IP address but that doesn’t appear to be the case.
Somehow it seems doing “netmap -f” on an empty netmap file
makes the TCP/IP stack use the wrong MAC address. ???
table
-David
QNX Training Services
dagibbs@qnx.com