From: Ray Wells (kic.lcbvbfql@aarhus.dk)
Date: Fri May 11 2001 - 11:29:01 EEST
Thanks to all who have contributed to this.
I have to leave the in depth analysis of this one to the experts, it's way
out of my league, but what Cathryn says about the problem being harmless
certainly appeared to be the case here.
Apart from some syslog entries and the annoying messages appearing whilst I
was typing something, there appears to be no other problems created.
At Craig Small's suggestion I'm going to move away from 2.2.17 kernel (for a
different reason) so I'll see what that does.
.. Ray Wells VK2TV
----- Original Message -----
From: "Cathryn Mataga" <ilnvilw@bb.banban.jp>
To: <unlisted-recipients:; (no To-header on input)>
Cc: <terhi.victor@logonet.com>
Sent: Tuesday, May 08, 2001 5:41 PM
Subject: Re: possible bug
>
>
> Craig Small wrote:
> >
> > On Mon, May 07, 2001 at 06:06:32PM +1000, Ray Wells wrote:
> > > May 4 22:24:28 vk2tv kernel: protocol fd88 is buggy, dev ax1
> > >
> > > I've been able to ascertain that the messages are happening only when
both
> > > listen and rxecho are in use simultaneously. If I kill either process
and
> > > leave the other running, there is no problem.
> >
> > It's very strange because it is the kernel complaining about it, not
> > listen or rxecho.
> >
> > The message is coming from core/dev.c in the function
> > dev_queue_xmit_nit()
> >
> > I think it is failing on this:
> > skb2->nh.raw < skb2->data || skb2->nh.raw >= skb2->tail
> >
> > > I'm uncertain about dselect reporting the actual installed version.
Does it do this
> > > or does it simply report the version that came with the package, even
if a later
> > > version was obtained and packages updated? The .deb versions I
obtained had their
> > > names truncated to 8.3 by my Windows system, so the filenames reported
are meaningless.
> > dpkg -l ax25-apps (or whatever you are looknig for) will tell you the
> > version.
> >
> > BTW, you really should upgrade that kernel version, there is some
> > security hole in 2.2.17 IIRC
> >
>
> It was awhile back, but I thought this was related somehow to the fact
that
> with ax25 the tcp/ip data doesn't start at a constant offset. I think,
because
> of the digipeat stuff. I tried tracking down the 'is buggy' message about
a
> year ago, and I think I convinced myself that it was harmless at the time.
Though
> my memory is vague on this.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to mvw.uhmlxl@orangecaibe.com
>
----- Original Message -----
From: "Cathryn Mataga" <xvplkkw@commercebank.com>
To: <unlisted-recipients:; (no To-header on input)>
Cc: <lnio@mail.dy.fi>
Sent: Tuesday, May 08, 2001 5:41 PM
Subject: Re: possible bug
>
>
> Craig Small wrote:
> >
> > On Mon, May 07, 2001 at 06:06:32PM +1000, Ray Wells wrote:
> > > May 4 22:24:28 vk2tv kernel: protocol fd88 is buggy, dev ax1
> > >
> > > I've been able to ascertain that the messages are happening only when
both
> > > listen and rxecho are in use simultaneously. If I kill either process
and
> > > leave the other running, there is no problem.
> >
> > It's very strange because it is the kernel complaining about it, not
> > listen or rxecho.
> >
> > The message is coming from core/dev.c in the function
> > dev_queue_xmit_nit()
> >
> > I think it is failing on this:
> > skb2->nh.raw < skb2->data || skb2->nh.raw >= skb2->tail
> >
> > > I'm uncertain about dselect reporting the actual installed version.
Does it do this
> > > or does it simply report the version that came with the package, even
if a later
> > > version was obtained and packages updated? The .deb versions I
obtained had their
> > > names truncated to 8.3 by my Windows system, so the filenames reported
are meaningless.
> > dpkg -l ax25-apps (or whatever you are looknig for) will tell you the
> > version.
> >
> > BTW, you really should upgrade that kernel version, there is some
> > security hole in 2.2.17 IIRC
> >
>
> It was awhile back, but I thought this was related somehow to the fact
that
> with ax25 the tcp/ip data doesn't start at a constant offset. I think,
because
> of the digipeat stuff. I tried tracking down the 'is buggy' message about
a
> year ago, and I think I convinced myself that it was harmless at the time.
Though
> my memory is vague on this.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to rxvbwn.rcho@mailit.tunk.net
>
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to ipqmz.kxnk@mil.fi
This archive was generated by hypermail 2b30 : Fri May 11 2001 - 11:40:15 EEST