First of all, thanks to OP for original idea and whole thread and to Viqsi for clever approach with bridge usage, courtesy of latest KP.

Now, I'm pretty green when it comes to bluetooth PAN (never used it before - DUN user for ages), so bear with me, please - my question may be noobish:

I've tried both methods (cleaned everything after attempts, so don't worry about config mess) and I think both should be working for me - the thing is, that I have problems at *earlier* stage, i.e. connecting PCs and N900 in PAN mode.

Machines in question are windoze XP systems with broadcomm WIDCOMM bluetooth stack. Every other bluetooth profile works OK, I also have a "Bluetooth Network Interface" created under "networks". PC pairs up with N900 in any other profile without problems, and both devices are each's other "trusted" machines.

But, "network access" profile doesn't show as "service" offered by N900 (from PC perspective), at all. I *only* see DUN, object push, hands-free and so goes on - *no* network access or anything resembling PAN, whatsoever.

When I try to force connect to N900 using "network access" profile, error appears, stating that "this service isn't offered by <my N900 bluetooth hostname>".
---

Any ideas? May it be related to bluetooth-dun package being installed, at some point, on N900? Could it somehow "disable" PAN profile all-together? If yes, where to check and how to clean mess left?

/Estel

// Edit

Normally, DUN was more than enough for me - but currently, my internet access situation is such, that having N900 as device sharing connection to all others (bluetooth-equipped - one another N900 and one PC) devices in home, would be most comfortable solution. As DUN allows only 2 deevices to cooperate, PAN seemed like best option (I would like to avoid fallback mobile hotspot [aka ad-hoc wifi] usage, due to high battery drain - it's good for short connections, but not 24/7 solution, which I'm aiming at).

Thanks in advance,
/Estel