DUN client questions

Hi All,

I have applied Gustavos patches from 09/11/2010 to the current git version of ofono and besides a problem with the cid range (min = max = 2, but my mobile (Nokia N82) only has one context) I was able to get a connection until the point where the ip and the dns addresses where written to the log file. So far so good (I guess).

I am not too far into the code right know, so the following questions maybe stupid. Please bear with me, I appreciate any help.

I am using MeeGo 1.1 with updated ofono, connman and carrick packages (all from git).

Here is what I did to get the DUN connection up:

1. Connect the mobile using the bluetooth applet in MeeGo -> The modem was recognized as DUN capable and shows up in the "list-modems" output from ofonos test script as "/dun/xxx_yyy"
2. Then using the ofono test scripts: enable_modem, create-internet-context, activate-context

Questions:
- How to proceed from here. What is missing to have the context show up in the meego-network-panel?

- From my understanding a DUN modem looks very much like the USB 3G modem. The AT commands look similar (if not identical). Why is it necessary to have another modem type for this? Can't the atmodem driver be used for DUN, too?

Thanks,
Rolf

Hi Rolf,

connman should enable modem and all the magic needed to set it up, you should not need to run ofono test scripts.

It seems that somehow connman doesn't detect the modem. Once connman detects it, I would assume UI would show it as well.

Kalle Valo

It seems there is more involved with cellular connections. Detecting the modem in ofono is not enough to get it detected in connman.

I have a USB 3G modem, too. It does not show up in Connman when I plug it in. After some time the modem registers to a network and only then it gets listed in the meego-network-panel.

I think something along "register to a network and send notification about this" is missing in the dunmodem driver.

-Rolf