Linux-Hams archive - January 1997: Re: listen problems.

Re: listen problems.

spgmjux.ncwdv@joensuu.fi
Fri, 3 Jan 1997 23:59:52 +1100 (EST)


Richard Adams typed:
> [Wed Jan 1 15:18:02 1997]
> Port scc3: EAX25: [invalid]->[invalid] <I S4 R0> pid=0x45 [DAMA]
Hmm, a pid of 0x45. The PID byte is just before the data payload and the
first byte in the payload is the IP version and header length. So an ipv4
packet with header length of 20 would be 0x45 (or 0x54 never get that
byteorder right!) coincindence?

The reason why I might be seeing funny calls and you are not could be due to
the callsigns we use or even the SSID's.

> scc driver, considering you mentioned it, i understand you use a PI(2)
> card,?.
I have a PT or PackeTwin card. The device drivers for both a very similar.
I remember seeing some dramitic warnings in the packetwin driver code for
NOS, perhaps it is time to re-read them again. I would be nice if Don was
active.

> What i will try to do this week is repair an old TNC i have here and connect
> it to a seriel port and see what happens..
This would be good to see the results for.

> uses also an scc card for 3 radio ports 2x4k8 and 1x9k6 and also has other
> stn's., connected via ethernet.
> Now i dont see any corrupt packets there.
This is strange, so what, other than different axtools, is different, did
the kernel change the scc between the two versions? (2.0.6->2.0.27)

For me and the rest of the PackeTwin users (perhaps PI too) it is a little
simpler; we've had this problem since the start of the general release of
the PT code. I cannot remember how it was with the non-GPL code, which used
a very different system. Perhaps one of the other alpha testers (Ken?)
could help.

- Craig vk2xlz

-- 
  // /\   |  | |  Craig Small VK2XLZ     @home: terhi.victor@logonet.com
 ||==||===|==|=|  [44.136.13.17]         @play: poatdcn@relay.tunkki.fi
  \\ \/   |  | |                         @work: whiu.gagxtgp@selectrade.hu