enable auth and BNEP question?

Hi I've recently switched to 3.5 from 2.25 version and have few questions:

1. Here is my hcid.conf

options {
        autoinit yes;
        security auto;
        pairing multi;
        passkey "BlueZ";
}
device {
        name "%h-%d";
        class 0x3e0100;
        iscan enable;
        pscan enable;
        discovto 0;
        lm accept;
        lp rswitch,hold,sniff,park;
        auth enable;
}

but my hciconfig still show no auth, and I can connect to PC without aut Of course I can bring it by "hciconfig piscan auth" but I wish to bring it by default.
Is there a way to do so?

2. I mostly use my Linux box to share create bluetooth network with other PC and my PDA so previously I had "pan " directory inside /etc/bluetooth/ with dev-up and dev-down files which automatically bring up bnep0 device, but seems that BlueZ 3.5 is working differently and I need to execute "ifconfig benp0 up" to enable my connection. Is there a way to automate this?

Quoted 7 lines

2. I mostly use my Linux box to share create bluetooth network with other PC and my PDA so previously I had "pan " directory inside /etc/bluetooth/ with dev-up and dev-down files which automatically bring up bnep0 device, but seems that BlueZ 3.5 is working differently and I need to execute "ifconfig benp0 up" to enable my connection. Is there a way to automate this?

you might wanna try the -A, -E or -S switch for pand.

Quoted 10 lines

Quoted 7 lines

2. I mostly use my Linux box to share create bluetooth network with other PC and my PDA so previously I had "pan " directory inside /etc/bluetooth/ with dev-up and dev-down files which automatically bring up bnep0 device, but seems that BlueZ 3.5 is working differently and I need to execute "ifconfig benp0 up" to enable my connection. Is there a way to automate this?

you might wanna try the -A, -E or -S switch for pand.

Thanks for response, Marcel!

I've tried switches you've recommend and seems that "-S" is what I'm looking for although it asked me authorization 3 times(even once devices was paired) but now it seems to work like it should.

Maybe you can help me with brining up bnep0 interface automatically as well?

Hi Denis,

Quoted 17 lines

Quoted 11 lines

Quoted 8 lines

2. I mostly use my Linux box to share create bluetooth network with other PC and my PDA so previously I had "pan " directory inside /etc/bluetooth/ with dev-up and dev-down files which automatically bring up bnep0 device, but seems that BlueZ 3.5 is working differently and I need to execute "ifconfig benp0 up" to enable my connection. Is there a way to automate this?

you might wanna try the -A, -E or -S switch for pand.

Thanks for response, Marcel!

I've tried switches you've recommend and seems that "-S" is what I'm looking for although it asked me authorization 3 times(even once devices was paired) but now it seems to work like it should.

Quoted 2 lines

Maybe you can help me with brining up bnep0 interface automatically as well?

this depends on your distro. All distros have a way of bringing up devices automatically. Or you might wanna check the pand.1 manual page.

Quoted 17 lines

Quoted 17 lines

Quoted 11 lines

Quoted 8 lines

2. I mostly use my Linux box to share create bluetooth network with other PC and my PDA so previously I had "pan " directory inside /etc/bluetooth/ with dev-up and dev-down files which automatically bring up bnep0 device, but seems that BlueZ 3.5 is working differently and I need to execute "ifconfig benp0 up" to enable my connection. Is there a way to automate this?

you might wanna try the -A, -E or -S switch for pand.

Thanks for response, Marcel!

I've tried switches you've recommend and seems that "-S" is what I'm looking for although it asked me authorization 3 times(even once devices was paired) but now it seems to work like it should.

Quoted 6 lines

Quoted 2 lines

Maybe you can help me with brining up bnep0 interface automatically as well?

this depends on your distro. All distros have a way of bringing up devices automatically. Or you might wanna check the pand.1 manual page.

Thanks, Marcel! I'm on Debian and have tried few ways of brining up interface by distro means but failed.
I were managed to automate process by using --devup switch with pand which was just what I was looking for.

BTW just wish to say that this option isn't appearing in man page, thought you may like to know about this.

Hi Denis,

Quoted 26 lines

Quoted 19 lines

Quoted 19 lines

Quoted 9 lines

Quoted 9 lines

2. I mostly use my Linux box to share create bluetooth network with other PC and my PDA so previously I had "pan " directory inside /etc/bluetooth/ with dev-up and dev-down files which automatically bring up bnep0 device, but seems that BlueZ 3.5 is working differently and I need to execute "ifconfig benp0 up" to enable my connection. Is there a way to automate this?

Quoted 4 lines

you might wanna try the -A, -E or -S switch for pand.

Thanks for response, Marcel!

I've tried switches you've recommend and seems that "-S" is what I'm looking for although it asked me authorization 3 times(even once devices was paired) but now it seems to work like it should.

Quoted 7 lines

Quoted 3 lines

Maybe you can help me with brining up bnep0 interface automatically as well?

this depends on your distro. All distros have a way of bringing up devices automatically. Or you might wanna check the pand.1 manual page.

Quoted 8 lines

Thanks, Marcel! I'm on Debian and have tried few ways of brining up interface by distro means but failed.
I were managed to automate process by using --devup switch with pand which was just what I was looking for.

BTW just wish to say that this option isn't appearing in man page, thought you may like to know about this.

check the latest source code and if it is still missing, send in a patch for it.

Regards

Marcel

But I've got another a bit off topic and lame question, I've never send patches before but would like to help when I can. So if I would find a bug and solution for it in future, should I just generate patch in a way like this:
"|diff -up original modified > patch"
and send it to mail-list or there are some other commonly used procedure?