From: Marcel Holtmann <marcel@holtmann.org>
To: Kutschenreuter Matthias <Matthias.Kutschenreuter@siemens.com>
Cc: "'Bluez-devel@lists.sourceforge.net'"
<Bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] pand + socket filtering on zaurus
Date: Tue, 25 May 2004 17:48:30 +0200 [thread overview]
Message-ID: <1085500110.9779.144.camel@pegasus> (raw)
In-Reply-To: <AFE91B59A185A5439840B43AB7919047093972@mchp997a.mch.sbs.de>
Hi Matthias,
> I am running bluez / bnep / pan on a zaurus; it works fine.
>
> But thenI needed to change my kernel (zImage) to get some other
> software running:
> I had to build in the Socket Filtering (make menuconfig: Networking
> Options -> Socket Filtering).
> This was the only change I did to the kernel.
>
> With the new kernel, pand has some problems: I can "pand -s" ( remote
> station does "pand -c <MAC>").
> They can ping. but when the connection is terminated ("pand -K"), no
> matter from which station,
> the zaurus gets frozen. I have to reboot the zaurus.
> Also, I cannot "pand -c <MAC>" from the zaurus side, which works fine
> without the "Socket Filtering" .
>
> This problem occurs only on zaurus. On my desktop the Socket Filtering
> doesnt interfere with pand.
> But there, I have a completely different kernel (2.4.19) than on
> zaurus (2.4.6), with a different set of
> kernel build-ins
> Does anybody know, whether "Socket Filtering" requires or forbids some
> other kernel build-ins,
> in order to work with pand ?
you now that we are already at Linux kernel 2.6.6 ;) The 2.4.6 is so old
that I can't even tell you, if there are problems with your combination.
I stopped testing BNEP with 2.4.18 and you should take an iPAQ with
2.4.19 to check if your combination is there working, too. Maybe it is
an ARM related problem.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-05-25 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 15:31 [Bluez-devel] pand + socket filtering on zaurus Kutschenreuter Matthias
2004-05-25 15:48 ` Marcel Holtmann [this message]
[not found] <AFE91B59A185A5439840B43AB7919047093974@mchp997a.mch.sbs.de>
2004-05-26 10:00 ` Marcel Holtmann
[not found] <AFE91B59A185A5439840B43AB7919047093983@mchp997a.mch.sbs.de>
2004-06-01 14:53 ` Marcel Holtmann
[not found] ` <1086101397.2777.597.camel@baroque.rococosoft.com>
2004-06-01 14:56 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2004-06-02 15:51 AW: AW: AW: AW: " Kutschenreuter Matthias
[not found] ` <1086193144.7888.694.camel@baroque.rococosoft.com>
2004-06-03 10:36 ` Marcel Holtmann
[not found] <AFE91B59A185A5439840B43AB7919047093989@mchp997a.mch.sbs.de>
2004-06-03 15:32 ` Marcel Holtmann
[not found] <AFE91B59A185A5439840B43AB791904709398A@mchp997a.mch.sbs.de>
2004-06-03 16:16 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1085500110.9779.144.camel@pegasus \
--to=marcel@holtmann.org \
--cc=Bluez-devel@lists.sourceforge.net \
--cc=Matthias.Kutschenreuter@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox