no forwarding

[tarelda]

I am testing packet-journey and after initial satisfaction I found out that forwarding is actually happening in Linux through out KNI interfaces. (Communication with Linux through KNI works flawlessly) I was pretty bummed so I tried to debug it.
In logs only one entry about SIGCHLD handler caught my eye but I was unable to figure what is calling it.
During gdb session I had pretty weird results. I set up breakpoints on functions implementing processing steps, but got hits on them non consistently. Also variables that I inspected weren't looking suspicious. I am puzzled what to do next.
Any suggestions?

[tarelda]

I setup very simple test bench. I added static ARPs for next hops in my routes. Forwarding actually occurs, but for some reason data that ingress is untagged but on the other end ends up in vlan 1892.
neigh ipv4 output looks weird:
hw addr(00:00:00:00:00:00) addr(255.255.255.255) action 2 state 0 vlan -1 port 65535
hw addr(00:00:00:00:00:00) addr(0.0.0.0) action 2 state 0 vlan -1 port 65535
hw addr(00:00:00:00:00:00) addr(10.0.0.2) action 3 state 0 vlan 0 port 0
hw addr(00:00:00:00:00:00) addr(10.0.1.2) action 3 state 0 vlan 0 port 1
hw addr(00:1B:21:BF:E2:DE) addr(10.0.1.1) action 1 state 128 vlan 14180 port 1
hw addr(00:1B:21:BF:E2:DC) addr(10.0.0.1) action 1 state 128 vlan 14180 port 0
hw addr(00:1B:21:BF:E2:DE) addr(48.0.0.1) action 1 state 4 vlan 14180 port 1

[tarelda]

I guess I am on right track. I found offending line:

packet-journey/app/control.c

Line 628 in 49526fb

unsigned kni_vlan;

Variable kni_vlan is not initialized, thus weird vlan values. That fixes issue if arp entries are added manually or other side also makes contact, but still for some reason packet-journey doesn't even try to find neighbour.