Project Home
Project Home
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - QNET Bad Address problem: (2 Items)
   
QNET Bad Address problem  
Hi,

I am currently trying to set up qnet on a small network of two Raspberry Pi boards (node1 and node2), connected via a 
router. 


On each of the nodes I start qnet with io-pkt and it seems to start correctly.
io-pkt-v6-hc -p qnet host=node1

After bootup I can see the following in /proc/qnetstats (here executed on node1):

       kif net_server                :         0,0         
       kif waiting                   :         1,1         
       kif net_client                :         0,0         
       kif buffer                    :         0,0         
       kif outbound_msgs             :         0,0         
       kif vtid                      :         0,0         
       kif server_msgs               :         0,0         
       kif nd_down                   :         0
       kif nd_up                     :         2
       kif nd_changed                :         1
       kif send_acks                 :         0
       kif client_kercalls           :         0
       kif server_msgs               :         0
       kif server_unblock            :         0
       qos tx_begin_errors           :         0
       qos tx_done_errors            :         0
       qos tx_throttled              :         0
       qos tx_failed                 :         0
       qos pkts_rxd_noL4             :         0
       qos tx_conn_created           :         0
       qos tx_conn_deleted           :         0
       qos rx_conn_created           :         0
       qos rx_conn_deleted           :         0
       qos rx_seq_order              :         0
**** Qnet compiled on Jun 13 2020 at 19:52:17 running on node1
**** Tx Connections:
**** Rx Connections:
**** L4 Status:
slot 0 genet0 mtu 1496 ack 1 crc 0
  txd ok       4
  txd bad      0
  txd descr    0
  txd still    0
  tx  timeouts 0
  tx  slow     0
  rxd ok       4
  rxd bad dr   0
  rxd bad L4   0
  rxd dropped  0
  rxd duplic   0
  rxd nacks    0
slot 1 is unused
**** Last 8192 bytes of circular qnet_error() log:
00000000:: mac_load(): security policy not being used
00000000: qnet_birth(): qnet_init() - complete
00000000: lr_verify_my_name_and_domain(): set _CS_DOMAIN
00000000: lr_verify_my_name_and_domain(): starting resolution of our hostname node1.net.intra to ensure unique
00000000: lr_verify_my_name_and_domain(): qnet going online
00000001: try_ifp(): new interface: genet0: index 0 mac addr DC:A6:32:BB:EC:05
00000001:: nd_change_notify(): Node Up:   nd 0 node1.net.intra
00000031: lr_add_ndb(): adding L4 0 addr to ndb for nd 1  node2.net.intra
00000031:: nd_change_notify(): Node Up:   nd 1 node2.net.intra

It seems both nodes can discover each other on the network fine. 
According to the guide on using qnet (https://www.qnx.com/developers/docs/7.1/index.html#com.qnx.doc.neutrino.user_guide
/topic/qnet_UsingQnet.html) I try to see the neighbourhood via
#pidin net 
which returns the following:
 ND    Node             CPU      Release FreeMem       BootTime
 0     node1            4 AARCH64    7.1.0   3803MB/4032MB ------------------------
           Processes: 25, Threads: 88
           CPU 1: 1091555459 Cortex-A72             1500MHz FPU 
           CPU 2: 1091555459 Cortex-A72             1500MHz FPU 
           CPU 3: 1091555459 Cortex-A72             1500MHz FPU 
           CPU 4: 1091555459 Cortex-A72             1500MHz FPU 
 1     node2           Bad address

The same on the other node gives the same results. 
I have also tried to execute execute processes on the different nodes that communicate with each other but the results 
are the same. 
Is there anything I am doing wrong when setting up qnet?
Re: QNET Bad Address problem  
There was a change in a 7.1 update that may have caused the issue you are seeing. It was since fixed, but I'm not sure 
whether the fix is generally available. You should contact support to see if you can get it. If not. try downgrading to 
the original 7.1.0 kernel.

--Elad