On 12/08/2010 09:38 AM, Ralf Baechle wrote:
I have discovered a bug in ax25ipd. I was setting up ax25ipd last night, and it would receive data fine, but wouldn't transmit anything out the IP side. After looking in my log files, I observed this message every time I tried to send a packet out via ax25ipd:
I will just add that tcpdump verified that nothing was going out the IP side.
John, what is the actual value of the control byte in your case?
So I changed the LOG2 to log the control byte when it happens, but now the problem isn't recurring. I am unsure if it has something to do with the order that kissnetd or kissattach are started; I have both kissnetd and kissattach running for other purposes on this machine as well.
I did log a control byte of 128 and another of 32 but traffic is flowing right now despite reverting the test back to the way it was. I have stopped and restarted all AX.25 pieces on my system several times since then.
This is broken. From the original K3MC / KA9Q KISS spec:
Where can I find that spec, BTW?
I'm just wondering why the test isn't (*iframe& 0xf) == 0 which would handle the full number of possible 16 possible TNCs.
That smells like it's a correct solution to me, given what the spec says. I will compile it with that test and let you know if I see any issues.
-- John