**** BEGIN LOGGING AT Wed Jun 15 02:59:57 2011
Jun 15 13:28:32 <wagi> Hi, I'm feeling really stupid because I'm complete lost how DUN is supposed to work. I understand that BlueZ does the service descovering. Then it publishes the device on the D-Bus. With GetPropertes() on the org.bluez.Device interface oFono knows there is a DUN capable device. So far so good. What happends then? I aware that not all patches are on the tree yet
Jun 15 13:39:46 <Gzajac> wagi: Hi,  once the bluetooth connection is established, the DUN client will send ATD*99 for instance to oFono emulator. The latter will  through D-Bus ask ConnMan for TUN interface.
Jun 15 13:39:46 <Gzajac> ConnMan will open a TUN interface, return the fd and the network settings. It will also enable NAT on the default interface to forward IP stream to it.
Jun 15 13:40:30 <Gzajac> The missing part is the oFono plugin that will request/release the private network.
Jun 15 13:40:48 <wagi> Gzajac: Okay, what is the DUN client? sorry I'm a bit lost
Jun 15 13:41:08 <wagi> I have looked at the dialup-overview.txt
Jun 15 13:42:44 <Gzajac> wagi: no pb, the DUN client is, for instance, the computer you will use to connect to your mobile phone (via bluetooth)  to be connected to the web.
Jun 15 13:44:19 <Gzajac> Like a 3G usb dongle
Jun 15 13:44:35 <wagi> Right, so ConnMan has to send the AT string?
Jun 15 13:48:53 <wagi> Maybe I should ask my question this way. Which interfaces are in use between the components? If there is a DUN capable device, does ConnMan also look what BlueZ tells which kind of device is there? Or does ConnMan only listen on oFono and interact with oFono?
Jun 15 13:49:09 <Gzajac> no, DUN client sends ATD*99 to oFono, then oFono requests to ConnMan a private network
Jun 15 13:49:10 <Gzajac> If the private network is passed successfully to oFono.
Jun 15 13:49:10 <Gzajac> oFono responds OK otherwise it responds ERROR
Jun 15 13:49:10 <Gzajac> ConnMan is just here to provide private network settings to oFono.
Jun 15 13:49:45 <Gzajac> sry didn' tsee your last post :)
Jun 15 13:50:24 <Gzajac> so ConnMan only interact with oFono
Jun 15 13:51:01 <wagi> ah, I understood that ConnMan will expose a DUN devices as service
Jun 15 13:51:16 <wagi> But if I understood you correctly this is not the case?
Jun 15 13:51:30 <wagi> ConnMan just provides the TUN and the private IP range
Jun 15 13:51:36 <Gzajac> right
Jun 15 13:52:14 <wagi> Hmm, that's a bit strange, because I though all IP connections will be a ConnMan service 
Jun 15 13:52:26 <wagi> for example as the PAN 
Jun 15 13:52:57 <wagi> sameo_: ping
Jun 15 13:53:23 <Gzajac> wagi: sry I don't know about PAN
Jun 15 13:53:42 <wagi> Gzajac: no problem. ConnMan talks to BlueZ directly.
Jun 15 13:53:52 <sameo_> wagi: pong
Jun 15 13:54:21 <wagi> sameo_: I just learned that DUN is mapped to ConnMan service
Jun 15 13:54:32 <wagi> sameo_: I find this a bit strange
Jun 15 13:54:47 <sameo_> wagi: is _not_ mapped to a ConnMan service ?
Jun 15 13:55:48 <wagi> sameo_: yes, that's what I am try to figure out. Gzajac told me that a DUN client does the Connect()/Disconnect()
Jun 15 13:56:03 <wagi> sameo_: and ConnMan provides just the RequestPrivateNetwork interface
Jun 15 13:56:30 <sameo_> wagi: that's correct. In that case, ConnMan and oFono are the DUN server.
Jun 15 13:56:39 <wagi> Gzajac: BlueZ exports PAN as org.bluez.Network interface and ConnMan uses this to setup IP connections
Jun 15 13:56:51 <sameo_> wagi: in the client case, yes.
Jun 15 13:57:18 <sameo_> wagi: the one you're looking at is similar to PAN tethering.
Jun 15 13:57:36 <wagi> I'm so confused right now
Jun 15 13:58:12 <sameo_> wagi: The code path Gzajac is talking about is when a DUN client talks to the device running oFono+ConnMan.
Jun 15 13:59:03 <sameo_> wagi: in which case it will send AT commands to oFono, who will then asks ConnMan to basically give it an IP setting to send back to the DUN client.
Jun 15 13:59:10 <wagi> sameo_: so in this case the AT string comes from the 'other side'?
Jun 15 13:59:22 <sameo_> wagi: yes, and it's received by oFono.
Jun 15 14:00:29 <wagi> sameo_: okay, that explains a bit
Jun 15 14:01:20 <wagi> So next stupid question: In case we are the DT (Data Terminal) we have a ConnMan service?
Jun 15 14:02:13 <sameo_> wagi: we would, but we don't right now as we don't support BT DUN client mode.
Jun 15 14:02:44 * sameo_ -> meeting
Jun 15 14:04:01 <wagi> sameo_: thanks
Jun 15 14:04:07 * wagi -> meeting
Jun 15 15:04:19 <wagi> Gzajac: btw, thanks for explaining
Jun 15 15:28:45 <holtmann> denkenz: Do you have pending patches. I think we should do a new oFono release as well.
Jun 15 15:29:16 <denkenz> go for it
Jun 15 17:52:13 <fdanis> denkenz: ping
Jun 15 17:59:16 <denkenz> fdanis: pong
Jun 15 17:59:58 <fdanis> did you take a look to v5 of ATD/AT+BLDN patches ?
Jun 15 18:00:15 <denkenz> not yet
Jun 15 18:02:08 <fdanis> ok
**** ENDING LOGGING AT Thu Jun 16 02:59:57 2011