Menu

Main Menu
Talk Get Daily Search

Member's Online

    User Name
    Password

    Free DUMMY type connection

    Reply
    Page 1 of 2 | 1   2   | Next
    Matan | # 1 | 2010-01-20, 21:26 | Report

    To users of DUMMY connections (Bluetooth PAN, USB networking, DUN client, etc.) can now use libicd-network-null from extras-devel, instead of the convoluted way of downloading libicd-network-dummy from nokia-binaries repository. The package name is different, but it sets up the same type DUMMY, so nothing actually needs to change.

    The package also compiles for diablo, but on the N810 I use no DUMMY connections, so I did not test it. I'll be happy to hear success/failure reports on N8x0.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following 3 Users Say Thank You to Matan For This Useful Post:
    iKneaDough, lma

     
    nicola.mfb | # 2 | 2010-01-25, 22:09 | Report

    Originally Posted by Matan View Post
    To users of DUMMY connections (Bluetooth PAN, USB networking, DUN client, etc.) can now use libicd-network-null from extras-devel, instead of the convoluted way of downloading libicd-network-dummy from nokia-binaries repository. The package name is different, but it sets up the same type DUMMY, so nothing actually needs to change.
    Hi Matan,
    I'm trying to setup the dummy connection on n900 (with os upgraded), so I installed libicd-network-null and executed:

    gconftool-2 -s -t string /system/osso/connectivity/IAP/DUMMY/type DUMMY
    gconftool-2 -s -t string /system/osso/connectivity/IAP/DUMMY/name 'Dummy network'
    gconftool-2 -s -t boolean /system/osso/connectivity/IAP/DUMMY/autoconnect true

    Anyway the dummy network does not appear on the list of those available in the connection manager.

    Some hints?

    Regards

    Niko

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Matan | # 3 | 2010-01-25, 22:20 | Report

    In version 1.0, connections did not appear on the available connections list, but could only be selected by direct commands to icd (with dbus, for example). This is fixed in version 1.2, which is already in extras-devel and my repository. If you already upgraded to this version, did you reboot (or at least killall icd2) since the upgrade?

    I am not sure about autoconnect, though, since a dummy type connection is always available.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    nicola.mfb | # 4 | 2010-01-25, 22:48 | Report

    After removing/reinstalling, rebooting and playing with gconftool-2 -u several time, finally it appeared.
    I do not remember the exact operation that fixed it (the version was already 1.2).

    Anyway it seems to work very nice, I desperately need it to receive voip calls in my office where campus wifi network signal is too weak.
    In the next days I'll test it deeply and update the wiki.

    Thank you very much!

    Regards

    Niko

    Edit | Forward | Quote | Quick Reply | Thanks

     
    nicola.mfb | # 5 | 2010-01-27, 13:54 | Report

    Ok it works fine
    The only problem is that If I activate the dummy connection from the GUI then cannot disconnect from the GUI itself, but have to use a dbus call.

    If the dummy connection is initated via dbus I can disconnect it both from dbus and from the GUI.

    Now I'm using the following script to automate the process:
    Code:
    ifconfig usb0 192.168.2.15 up
    route add default gw 192.168.2.14
    echo nameserver 213.230.129.10 >/var/run/resolv.conf.ppp0
    echo nameserver 217.200.200.42 >>/var/run/resolv.conf.ppp0
    dbus-send --system --dest=com.nokia.icd /com/nokia/icd_ui com.nokia.icd_ui.disconnect boolean:true
    sleep 2
    dbus-send --type=method_call --system --dest=com.nokia.icd /com/nokia/icd com.nokia.icd.connect string:DUMMY uint32:0
    and to disconnect
    Code:
    dbus-send --system --dest=com.nokia.icd /com/nokia/icd_ui com.nokia.icd_ui.disconnect boolean:true
    rm /var/run/resolv.conf.ppp0
    sudo route del default gw 192.168.2.14
    sudo ifconfig usb0 0.0.0.0 down
    echo nameserver 127.0.0.1 >/etc/resolv.conf
    Is that correct?

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Matan | # 6 | 2010-01-27, 14:04 | Report

    Is there no disconnect from DUMMY button in the available networks list, or does pressing the button do nothing?

    Edit | Forward | Quote | Quick Reply | Thanks

     
    nicola.mfb | # 7 | 2010-01-27, 14:17 | Report

    Originally Posted by Matan View Post
    Is there no disconnect from DUMMY button in the available networks list, or does pressing the button do nothing?
    On the available network list there is "Disconnect Dummy Network", clicking does nothing.

    Niko

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Matan | # 8 | 2010-01-27, 14:28 | Report

    Can you run dbus-monitor --system while pressing the button and sending me the output?

    When you say nothing happens, do you mean that the same disconnect from DUMMY button remains?

    Edit | Forward | Quote | Quick Reply | Thanks

     
    nicola.mfb | # 9 | 2010-01-27, 14:42 | Report

    Originally Posted by Matan View Post
    Can you run dbus-monitor --system while pressing the button and sending me the output?
    It seems nothing happens:

    Code:
    signal sender=:1.11 -> dest=(null destination) serial=5790 path=/org/freedesktop/Hal/devices/bme; interface=org.freedesktop.Hal.Device; member=PropertyModified
       int32 1
       array [
          struct {
             string "maemo.rechargeable.charging_status"
             boolean false
             boolean false
          }
       ]
    signal sender=:1.11 -> dest=(null destination) serial=5795 path=/org/freedesktop/Hal/devices/bme; interface=org.freedesktop.Hal.Device; member=PropertyModified
       int32 2
       array [
          struct {
             string "maemo.rechargeable.charging_status"
             boolean false
             boolean false
          }
          struct {
             string "maemo.charger.type"
             boolean false
             boolean false
          }
       ]
    signal sender=:1.11 -> dest=(null destination) serial=5802 path=/org/freedesktop/Hal/devices/bme; interface=org.freedesktop.Hal.Device; member=PropertyModified
       int32 1
       array [
          struct {
             string "maemo.charger.type"
             boolean false
             boolean false
          }
       ]
    signal sender=:1.11 -> dest=(null destination) serial=5807 path=/org/freedesktop/Hal/devices/bme; interface=org.freedesktop.Hal.Device; member=PropertyModified
       int32 1
       array [
          struct {
             string "maemo.rechargeable.charging_status"
             boolean false
             boolean false
          }
       ]
    signal sender=:1.47 -> dest=(null destination) serial=87 path=/com/nokia/iphbd; interface=com.nokia.iphbd; member=wakeup18
       int32 1264603073
    signal sender=:1.47 -> dest=(null destination) serial=88 path=/com/nokia/iphbd; interface=com.nokia.iphbd; member=wakeup19
       int32 1264603073
    signal sender=:1.11 -> dest=(null destination) serial=5812 path=/org/freedesktop/Hal/devices/bme; interface=org.freedesktop.Hal.Device; member=PropertyModified
       int32 2
       array [
          struct {
             string "maemo.rechargeable.charging_status"
             boolean false
             boolean false
          }
          struct {
             string "maemo.charger.type"
             boolean false
             boolean false
          }
       ]
    signal sender=:1.11 -> dest=(null destination) serial=5819 path=/org/freedesktop/Hal/devices/bme; interface=org.freedesktop.Hal.Device; member=PropertyModified
       int32 1
       array [
          struct {
             string "maemo.charger.type"
             boolean false
             boolean false
          }
       ]
    signal sender=:1.11 -> dest=(null destination) serial=5824 path=/org/freedesktop/Hal/devices/bme; interface=org.freedesktop.Hal.Device; member=PropertyModified
       int32 1
       array [
          struct {
             string "maemo.rechargeable.charging_status"
             boolean false
             boolean false
          }
       ]
    Originally Posted by
    When you say nothing happens, do you mean that the same disconnect from DUMMY button remains?
    Yes, exactly, I encountered another strange case, connection manager showed me to "Disconnect button", one for the dummy connection, the other for a wlan.

    Are you able to reproduce this? It may be my device was messed up with adding/removing the dummy/null plugin, and experimenting too many with gconftool.

    Regards

    Niko

    Edit | Forward | Quote | Quick Reply | Thanks

     
    eitama | # 10 | 2010-08-22, 13:31 | Report

    EDIT : I was afraid I ain't going to get enough exposure with this thread, so I started a thread as it's not DIRECTLY related to the topic. Please don't answer here to prevent double posting.

    Instead go here : http://talk.maemo.org/showthread.php...963#post794963



    Originally Posted by Matan View Post
    To users of DUMMY connections (Bluetooth PAN, USB networking, DUN client, etc.) can now use libicd-network-null from extras-devel, instead of the convoluted way of downloading libicd-network-dummy from nokia-binaries repository. The package name is different, but it sets up the same type DUMMY, so nothing actually needs to change.

    The package also compiles for diablo, but on the N810 I use no DUMMY connections, so I did not test it. I'll be happy to hear success/failure reports on N8x0.
    Hello Matan,

    I have been trying to setup my phone so that connection USB+Selecting Windows Networking (Mad Developer)+Selecting PC Suite will fire up USB networking where my windows PC shares internet to the N900.

    All is working besides one problem, I got AutoDisconnect, which I don't want to give up, and I got the phone to automatically connect to Any Connection. The problem is : If I start microb for example, it will connect to the Dummy Network, and nothing will work, I have to manually select Internet 3G beforehand.

    I am assuming auto_connect false was supposed to do it, and it is configured as false :
    Code:
    Nokia-N900:~# gconftool-2 -a /system/osso/connectivity/IAP/DUMMY
     ipv4_address = 0.0.0.0
     ipv4_autodns = true
     ipv4_gateway = 0.0.0.0
     ipv4_type = AUTO
     name = Dummy network
     type = DUMMY
     proxytype = NONE
     ipv4_dns1 = 0.0.0.0
     ipv4_dns2 = 0.0.0.0
     ipv4_netmask = 0.0.0.0
     autoconnect = false
    Nokia-N900:~#
    Any ideas? I am just missing this one BIT of preventing the phone from using Dummy Network spontaneously...

    Edit | Forward | Quote | Quick Reply | Thanks

    Last edited by eitama; 2010-08-22 at 14:16.

     
    Page 1 of 2 | 1   2   | Next
vBulletin® Version 3.8.8
Normal Logout