Tethering failes to start on the Motorola Cliq

[GoogleCodeExporter]

Which device (manufacturer, type)?
Motorola Cliq (MB200)

Which firmware is installed?
The Dudes CliqCake v0.4.1. T-Mobile US, Blur Version 1.1.13
with boot.engineeringw4r-r1.img(enables iptables & netfilters) for custom 
boot image.

What version of wireless tether are you using?
1.6 HTC

What steps will reproduce the problem?
1.Start tethering

What is the expected output? What do you see instead?
Should see the wifi start and become discoverable.
Instead the error log shows:
Loading wlan.ko module...
failed

Configuring WiFi interface...
failed

Setting up firewall rules...
failed

Enabling IP forwarding...
done

Starting dnsmasq...
done

Activating MAC access control...
failed

Adding MAC addresses for allowed clients...
done

Please provide any additional information below.
Attached is the kernel config.

Original issue reported on code.google.com by engineer...@gmail.com on 29 Dec 2009 at 9:12

Attachments:

• .config

[GoogleCodeExporter]

Can you please update with what "ls /system/lib/modules" shows?

Original comment by bbux...@gmail.com on 6 Jan 2010 at 10:16

[GoogleCodeExporter]

The directory doesn't exist on the Cliq

# ls /system/lib/modules
/system/lib/modules: No such file or directory
# cd /system/lib
# ls  
libmedia_jni.so
libui.so
libdiag.so
libopencorertsp.so
libOmxVidEnc.so
libmedia.so
libthread_db.so
libdbus.so
libopencoreplayer.so
libOmxQcelpDec.so
libm.so
libsystem_server.so
libcutils.so
libopencorenet_support.so
libOmxMpeg4Dec.so
liblog.so
libsurfaceflinger.so
libctest.so
libopencoremp4reg.so
libOmxMp3Dec.so
libloc_api.so
libstdc++.so
libcrypto.so
libopencoremp4.so
libOmxH264Dec.so
libjni_pinyinime.so
libssl.so
libcorecg.so
libopencorehw.so
libOmxEvrcDec.so
libjni_latinime.so
libsrec_jni.so
libcommondefs.so
libopencoredownloadreg.so
libOmxCore.so
libicuuc.so
libsqlite.so
libcm.so
libopencoredownload.so
libOmxAmrEnc.so
libicui18n.so
libspeech.so
libcameraservice.so
libopencorecommon.so
libOmxAmrDec.so
libicudata.so
libsoundpool.so
libcamera.so
libopencoreauthor.so
libOmxAacEnc.so
libhpprop.so
libsonivox.so
libc_debug.so
liboncrpc.so
libOmxAacDec.so
libhgl.so
libsnd.so
libc.so
liboem_rapi.so
libGLESv1_CM.so
libhcid.so
libskiagl.so
libbluetooth.so
libnv.so
libFMRadio.so
libhardware_legacy.so
libsgl.so
libbluedroid.so
libnetutils.so
libFFTEm.so
libhardware.so
librpc.so
libaudioflinger.so
libnativehelper.so
libEGL.so
libgstk_exp.so
libril.so
libaudioeq.so
libmvs.so
libgsdi_exp.so
libril-qc-1.so
libaudio.so
libmotefem_svc.so
libz.so
libexpat.so
libreference-ril.so
libatcmd_svc.so
libmmjpeg.so
libwpa_client.so
libexif.so
libqueue.so
libarc_mpeg4h263_dec.so
libmmgsdilib.so
libwmsts.so
libemoji.so
libqmi.so
libarc_mp4_splitter.so
libmmcamera.so
libwms.so
hw
libdvm.so
libpixelflinger.so
libarc_h264_dec.so
libmm-qcamera-tgt.so
libwebcore.so
dhd.ko
libdss.so
libping_mdm.so
libandroid_servers.so
libmm-omxcore.so
libwbxml_jni.so
browsertestplugin.so
libdsm.so
libpdsm_atl.so
libandroid_runtime.so
libmm-adspsvc.so
libvorbisidec.so
libdrm1_jni.so
libpdapi.so
libagl.so
libmediaplayerservice.so
libutils.so
libdrm1.so
libpagemap.so
libaes.so
libmediagallery.so
libuim.so
bluez-plugin
libdl.so
libopencorertspreg.so
liba2dp.so

Original comment by engineer...@gmail.com on 7 Jan 2010 at 1:59

[GoogleCodeExporter]

Ok, alternatively can you give the output of 'lsmod' or 'cat /proc/modules' 
whilst
wifi is running? I am assuming that wifi is a kernel module.

Original comment by bbux...@gmail.com on 7 Jan 2010 at 2:53

[GoogleCodeExporter]

#lsmod
dhd 164936 0 - Live 0xbf000000

Original comment by engineer...@gmail.com on 7 Jan 2010 at 2:59

[GoogleCodeExporter]

Ok, one more thing...can you run "iwconfig" and send the output? I hope the 
wireless
might use standard linux extensions, which will really simplify supporting it...

Original comment by bbux...@gmail.com on 7 Jan 2010 at 3:50

[GoogleCodeExporter]

# iwconfig
iwconfig
lo        no wireless extensions.

dummy0    no wireless extensions.

rmnet0    no wireless extensions.

rmnet1    no wireless extensions.

rmnet2    no wireless extensions.

usb0      no wireless extensions.

eth0      IEEE 802.11-DS  ESSID:""  Nickname:""
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated
          Bit Rate:54 Mb/s   Tx-Power:32 dBm
          Retry min limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Managementmode:All packets received
          Link Quality=5/5  Signal level=0 dBm  Noise level=-11 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Original comment by engineer...@gmail.com on 7 Jan 2010 at 3:55

[GoogleCodeExporter]

Awesome, this means we should be able to support it relatively easily. I need 
just
one more thing before I code this...can you also run 'iwconfig' with wifi 
disabled? I
want to see if the interface stays present.

Original comment by bbux...@gmail.com on 7 Jan 2010 at 6:07

[GoogleCodeExporter]

eth0 does not stay present.

Thanks for the effort.

Original comment by engineer...@gmail.com on 7 Jan 2010 at 6:10

[GoogleCodeExporter]

Ah ok, this could get much tricker than I thought...can you enable wifi, then 
run
'dmesg' and post the output?

I am trying to find out what modules/etc I need to do in order to bring up the 
wifi
kernel interface.

Original comment by bbux...@gmail.com on 7 Jan 2010 at 6:26

[GoogleCodeExporter]

Dmesg output:
<4>[181110.692707] bcm_wlan_power_on: power_mode 1
<3>[181110.693868] mot_sdcc_wlan_power: WLAN power control on 1
<3>[181110.913287] mot_sdcc_wlan_power: WLAN power ON
<7>[181110.913345] mmc1: card_present 1
<6>[181110.913370] mmc1: Slot status change detected (0 -> 1)
<7>[181110.989572] mmc1: queuing CIS tuple 0x80 length 51
<7>[181110.997647] mmc1: queuing CIS tuple 0x80 length 7
<7>[181111.001040] mmc1: queuing CIS tuple 0x80 length 2
<7>[181111.011590] mmc1: queuing CIS tuple 0x80 length 9
<7>[181111.013464] mmc1: queuing CIS tuple 0x00 length 0
<7>[181111.015270] mmc1: queuing CIS tuple 0x00 length 0
<7>[181111.017007] mmc1: queuing CIS tuple 0x00 length 0
<7>[181111.018730] mmc1: queuing CIS tuple 0x00 length 0
<7>[181111.020455] mmc1: queuing CIS tuple 0x00 length 0
<7>[181111.022185] mmc1: queuing CIS tuple 0x00 length 0
<4>[181111.023014] bcmsdh_sdmmc: sdio_function_init Enter
<7>[181111.026859] mmc1: queuing CIS tuple 0x00 length 0
<4>[181111.028887]
<4>[181111.028927] Dongle Host Driver, version 4.217.27.12
<4>[181111.028982] Compiled in /localrepo/w36107/1.1.31/platform/system/wlan/bcm
/osrc/open-src/src/dhd/linux/../.. on Nov 11 2009 at 23:56:10
<7>[181111.030595] mmc1: queuing CIS tuple 0x00 length 0
<4>[181111.030800] dhd_oob_irq_handler thread : enter
<7>[181111.032472] mmc1: queuing CIS tuple 0x00 length 0
<7>[181111.034404] mmc1: queuing CIS tuple 0x00 length 0
<7>[181111.036414] mmc1: queuing CIS tuple 0x00 length 0
<7>[181111.039955] mmc1: queuing CIS tuple 0x00 length 2
<6>[181111.045497] mmc1: new SDIO card at address 0001
<4>[181111.060752] F1 signature read @0x18000000=0x5264325
<4>[181111.066439] DHD: dongle ram size is set to 393216(orig 393216)
<4>[181111.424062] dhd_oob_enable_intr : enable
<4>[181111.570973] eth0: Broadcom Dongle Host Driver

Original comment by engineer...@gmail.com on 7 Jan 2010 at 6:37

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

insmod dhd.ko produces the same dmesg output posted above...but it does not 
bring up 
the eth0 interface. 

# ifconfig eth0 up
ifconfig eth0 up
error: SIOCGIFFLAGS (No such device)

Original comment by engineer...@gmail.com on 7 Jan 2010 at 6:49

[GoogleCodeExporter]

It may be that you need to also install firmware via another command. If you 
can dig 
around to bring eth0 up via command line, then we can get this sorted.

Original comment by bbux...@google.com on 8 Jan 2010 at 12:32

[GoogleCodeExporter]

Issue 219 has been merged into this issue.

Original comment by ulf...@gmail.com on 8 Jan 2010 at 11:10

[GoogleCodeExporter]

What is the status on this issue, I would really like to have a cliq build as I 
use my 
G1 as a usb tether on my tower and now my wife has a cliq that I would to open 
up as a 
WAP.

Original comment by acidn...@gmail.com on 19 Jan 2010 at 5:30

[GoogleCodeExporter]

I can't help with coding, but I'm willing to do any testing or digging once I 
root my
Cliq later today.  I'd really like to see this work for the Cliq users.

Original comment by music4da...@gmail.com on 19 Jan 2010 at 5:44

[GoogleCodeExporter]

I don't presently have time to try to figur out how to bring up the eth0 
interface.  If 
anyone can figure this out and note the solution here.  Then bbuxton can code a 
cliq 
version.

So far I know the kernel module is /system/lib/dhd.ko.  Also the firmware is 
located 
somewhere in /etc or one of its sub dirs.(don't remember the exact location)

Original comment by engineer...@gmail.com on 20 Jan 2010 at 4:59

[GoogleCodeExporter]

bbuxton you the man!! Got my Cliq all ready and rooted for this.  This is the 
final
straw for getting me Iphone friends converted.

Original comment by justindu...@gmail.com on 26 Jan 2010 at 3:56

[GoogleCodeExporter]

Ok, engineeringw4r.  I'll root my Cliq sometime this week and see if I can help 
you
get the info you need.

Original comment by music4da...@gmail.com on 26 Jan 2010 at 6:08

[GoogleCodeExporter]

I tried the command:

ifconfig eth0 up

This gave an error of:

error: SIOCGIFFLAGS (no such device)

This would typically mean that a module isnt loaded. I have no idea what module
though. wlan.ko?

Original comment by dlglos...@gmail.com on 27 Jan 2010 at 3:59

[GoogleCodeExporter]

Oh jeez. I was doing this from work. I guess I didnt read it. engineeringw4r 
posted
that a long time ago. sorry. 

Original comment by dlglos...@gmail.com on 27 Jan 2010 at 4:20

[GoogleCodeExporter]

I want this too, because liquid uses same chip, same module and cant bring eth0
interface up !

Original comment by joaoh88 on 13 Feb 2010 at 8:30

[GoogleCodeExporter]

Have you guys tried to load the wifi-kernel like:

insmod /lib/modules/dhd.ko firmware_path=/etc/rtecdc.bin 
nvram_path=/etc/nvram.txt

firmware_path and nvram_path needs probably to be updated. It's a broadcom 
wifi-chip 
right? firmware_path and nvram_path are needed as parameters for loading the 
kernel-
module on the samsung galaxy - and the galaxy has a broadcom-chip included as 
well (as 
far as I know).

Original comment by harald....@gmail.com on 14 Feb 2010 at 11:05

[GoogleCodeExporter]

yeah.. I based the configuration in galaxy, as it has the same wifi chip as 
liquid..
But no success so far.. Just found that I have in the system folder a program 
name
netcfg that apparently it as similliar usage as as ifconfig.
"usage: netcfg [<interface> {dhcp|up|down}]"

Don't know if this programs chips with other android devices, but don't know why
there is 2 programs to do the same, or at least one program that does the same 
that
other does and nothing more..

But tried bringing up eth0 interface with netcfg and nothing so far!

Original comment by joaoh88 on 18 Feb 2010 at 5:15

[GoogleCodeExporter]

Ok, here we go ...

I've added support for Motorola Cliq in the latest pre-version available here:
http://code.google.com/p/android-wifi-tether/downloads/detail?name=wireless_teth
er_2_0-pre8.apk

I'm not able to test it because I don't own such a device!

Here are the changes I made:
http://code.google.com/p/android-wifi-tether/source/detail?r=397

Please note that you need a kernel which has "some" netfilter-related
features/options enabled. For more details please see our FAQ.

Original comment by harald....@gmail.com on 10 Mar 2010 at 10:41

[GoogleCodeExporter]

Please check and report.

The program generates more detailed output if you start it from command-line:
(start it first via gui - if something fails start from command-line and report 
the
output)

adb shell
su
cd /data/data/android.tether/bin
./tether start 1

Thanks.

Original comment by harald....@gmail.com on 10 Mar 2010 at 10:45

[GoogleCodeExporter]

I have a Dext/Cliq.
I installed pre8 version and the prompt showed this message:

# ./tether start 1
./tether start 1
about to run: [/system/bin/ifconfig eth0 192.168.2.254 netmask 255.255.255.0]
about to run: [/system/bin/ifconfig eth0 up]
about to run: [/data/data/android.tether/bin/iwconfig eth0 mode ad-hoc]
about to run: [/data/data/android.tether/bin/iwconfig eth0 essid AndroidTether]
about to run: [/data/data/android.tether/bin/iwconfig eth0 channel 6]
about to run: [/data/data/android.tether/bin/iwconfig eth0 commit]
about to run: [/data/data/android.tether/bin/iptables -F]
iptables v1.3.7: can't initialize iptables table `filter': iptables who? (do you
 need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
about to run: [/data/data/android.tether/bin/dnsmasq -i eth0 --resolv-file=/data
/data/android.tether/conf/resolv.conf --conf-file=/data/data/android.tether/conf
/dnsmasq.conf]
script result was []
#

Original comment by hugsso...@gmail.com on 15 Mar 2010 at 6:21

[GoogleCodeExporter]

@hugssouza: Some netfilter-related kernel-options are not enabled in the kernel 
you
have installed! You have to recompile and/or install such a kernel or you could
install a custom-rom which comes with these features.

Please see the FAQ:
http://code.google.com/p/android-wifi-tether/wiki/FAQ
"Why do I get the message "No Netfilter" on startup? This means that the Linux 
kernel
on your device does not have the features (CONFIG_NETFILTER, 
CONFIG_IP_NF_IPTABLES
and CONFIG_NETFILTER_XT_MATCH_MAC) required for tethering. If the feature
"CONFIG_NETFILTER_XT_MATCH_MAC" is missing the "access control"-feature will 
not work
correctly (you will see a "failed"-status in "Show log" for "Enabling access 
control")."

Hope this helps. 

Original comment by harald....@gmail.com on 15 Mar 2010 at 8:01

[GoogleCodeExporter]

@harald.mue: I saw this tutorial but is for a HTC. 
And I really like my firmware. I'm from Brazil.
My firmware is a little customized with some applications.
I dont know if this will help but after I tried to start the program by 
command-line,
I was able to connect my notebook to my phone by wifi. My notebook got a IP 
Address
but was not able to navigate.

Tell me if you dont understand something. My english is not so good.

Original comment by hugsso...@gmail.com on 15 Mar 2010 at 8:42

[GoogleCodeExporter]

@hugssouza: You need to recompile your kernel - netfilter-support as described 
in the
faq is mandatory. Otherwise you will discover exactly the symptoms you have 
described.

I don't have such a device but I know that there are roms out there which 
support
exactly these features. See: http://www.demoshadow.com 

This rom comes with hacked-up wifi-tethering-app (which is an older version of
wireless tether for root users). It has obviously a netfilter-enabled kernel - 
so it
can be done. There is a forum - please ask there how to recompile a kernel for 
cliq.

OR ... you could try TheDude CliqCake mentioned in the first post. 

Original comment by harald....@gmail.com on 15 Mar 2010 at 9:01

[GoogleCodeExporter]

You guys do know that Wifi-tethering works on HandlerExploit's 1.5 ROM on 
ModMyMoto.com?

Original comment by deadscen...@gmail.com on 18 Apr 2010 at 10:14

[GoogleCodeExporter]

@deadscenekid: No, I didn't know that. I've added support for cliq devices but 
the 
kernel (or rebuilinding it with netfilter-support) was the main-problem.
We are working hard to add support for different android devices - but it looks 
like 
that other "devs" are taking this info to create their own propriatary, 
closed-source 
wifi tethering-apps (check android market) instead of supporting 
opensource-software. 
And that's really annoying!

Anyway, thanks for info and happy tethering :-)

Original comment by harald....@gmail.com on 18 Apr 2010 at 12:08