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

Re: listen problems.

Richard Adams (diilk.xrfldybnfo@mailit.tunk.net)
Wed, 1 Jan 1997 16:00:30 +0000 (GMT)

According to eeatoz@tumbleweed.com, While burning my cpu.:
>
> they start halfway through. As an example, I have VK2TDS-1 and VK2XFW-3 =
> on =
>
> one of my ports and I get packets like:
>
> Port uhf: EAX25: WsVK2T-4->[invalid] v [invalid] [invalid] <[invalid] R22=
> > [DAMA]
>
> Port uhf: EAX25: 2XFW3V-11->[invalid] v [invalid]* <I S0 R1> pid=3D0x0 [D=
> AMA]
> 0000 =CC....=AC.d=A8.=A6.,..u.......,..D
>
> Port uhf: EAX25: 0VK2TD-3->[invalid] v [invalid]* [invalid] [invalid] [in=
> valid] [invalid]* [invalid] <I R F S6 R6>
> Port uhf: EAX25: K2TDSA-6->[invalid] v K2XFW3-1 <[invalid] R0>
>
> Port uhf: AX25: XFWsVK-2->a1i5VK-2 v [invalid] <I S0 R0> pid=3D0x0
> 0000 T4=B5..@.=D9+,..u,bnght.tebxotgc@hcs.net
> =2E..................... !"#$%&
> 0040 '()*+,-./01234567
>
> I believe that it is not listen's fault as the kernel ignores these packe=
> ts. =
>
> So perhaps it is in the scc drivers' code or in netif_rx() (unlikely?).
> Unfortunately, the offset varies with each packet.
>
Hi Craig.
I never see any trace whatsoever of a callsign in these corrupt packets, and
so far as i can see they are always the same.

[Wed Jan 1 15:18:00 1997]
Port scc3: AX25: PA3GCU->PI1GOE-3 <UI> pid=IP
IP: len 32 44.137.28.9->44.137.28.24 ihl 20 ttl 14 prot ICMP
ICMP: type Echo Request id 65535 seq 0
B^
[Wed Jan 1 15:18:02 1997]
Port scc3: EAX25: [invalid]->[invalid] <I S4 R0> pid=0x45 [DAMA]

Thats what i always see when someone is going tho' my box.
This does resemble what used to happen back in the devlopment days of the
scc driver, considering you mentioned it, i understand you use a PI(2)
card,?.
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..

The PI1GOE box is also a linux box ( at the moment a complete disaster area)
due to the fact that its a remote stn, and its 3 kilometers from here and i
have to push bike there, (its -10c) ;-) It has ax25-utils-2.0a kernel 2.0.6
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.
Jonathan, Terry is this food for thought.??? If so please let me know and i
will supply any infomation nessasary on request.

To make things clear: (i hope, its new years day and my head still herts) ;-)
pa3gcu has:
libc.so.5.0.9
gcc version 2.7.2
ld version cygnus-2.6 (with BFD 2.6.0.14)
libtermcap.so.2.0.8
kernel 2.0.27
axutils 2.0.12c

pi1goe has:
libc.so.5.0.9
gcc version 2.7.0
ld version cygnus/linux-2.5.2l.17 (with BFD cygnus/linux-2.5.2l.11)
libtermcap.so.2.0.0
kernel 2.0.6
axutils 2.0a

Of course this maybe of no significance at all.

> - Craig vk2xlz

-- 
Regards Richard, 73.
AX25  pa3gcu@pi8mid.#zld.nld.eu
smtp  eqbzzyi.tkqwpmowlr@kerailya.tunkki.fi
inet  iaknt@stofa.dk