Tethering

[norcalsfinest]

So, i've installed iptables on to my phone in /system/bin, fixed permissions, etc, but i cannot get tethering to work with barnacle or wireless tether. my computer won't connect to either. am i missing something?

[jmgib]

See this thread, http://modmymobile.com/forums/406-mo...-iptables.html

[norcalsfinest]

i saw that already, but it still isnt working.

I got 3rd party apps installing fine, but for some reason since root my issue has been tethering. any config help?

[jmgib]

Did you really read that thread? It was stated that all needed bits may not be in the kernel. Why don't you follow the other thread since they are trying to achieve the same goal you are, instead of starting your own little thread.

[Double0EK]

if you are using banacle wifi tether then be sure that the skip_wpa suppicant is checked ON in the settings. Then try it again.

[lart]

Barnacle .5 seems to work if you tell it to skip wpa on the backflip. .5.1 blows up and .4.2 does not let you skip wpa.

szym.net: Barnacle Wifi Tether

[rbmyr8]

I got Barnacle .5 to run, but when I try to connect with my computer, it doesn't associate, and it doesn't appear under "Clients." Maybe something with DHCP? Not too familiar with this stuff.

[MACTEP]

I got Barnacle .5 to run, but when I try to connect with my computer, it doesn't associate, and it doesn't appear under "Clients." Maybe something with DHCP? Not too familiar with this stuff.

Mine shows dhcp error in the log.

[norcalsfinest]

Mine shows dhcp error in the log.

thats exactly what i get... i really just want tethering to work on my backflip... i installed barnacle on my roommates droid2 and it worked fine first try after root.

[Sub1ime14]

I'd really like to be helpful on this, as I am a network admin and understand the DHCP process, but the error is simple and gives no useful information for troubleshooting. What I understand so far is that our kernel doesn't support IPtables. It's possible there's just no workaround until we get ported to 2.1 or 2.2, but I wouldn't mind if somebody released an app that does the routing itself, rather than depending on the OS to do it. Kinda doubt there's enough incentive for that to occur though.

[summetj]

My console also shows [1] Bus error ./dhcp
This indicates to me that the dhcp server has crashed (segfaulted) when attempting to give out an IP address to the computer. (I have confirmed that this crash occurs when the computers's DHCP client requests an address.)
(Using Barnacle 0.5.0....anybody have a solution?)

[MACTEP]

My console also shows [1] Bus error ./dhcp
This indicates to me that the dhcp server has crashed (segfaulted) when attempting to give out an IP address to the computer. (I have confirmed that this crash occurs when the computers's DHCP client requests an address.)
(Using Barnacle 0.5.0....anybody have a solution?)

I second that. As soon as you try to connect that error occurs.

I am an admin myself, but we will need a programmer to figure this one out.

[summetj]

Attached is a debug log of DHCP dieing...

09-03 16:58:15.752 48 48 I DEBUG : *** *** *** *** *** *** *** *** *** *
** *** *** *** *** *** ***
09-03 16:58:15.752 48 48 I DEBUG : Build fingerprint: 'motorola/motus_at
t_us/motus/motus:1.5/CUPCAKE/0.13.37:user/release-keys'
09-03 16:58:15.752 48 48 I DEBUG : pid: 596, tid: 596 >>> ./dhcp <<<
09-03 16:58:15.752 48 48 I DEBUG : signal 7 (SIGBUS), fault addr 0000000
0
09-03 16:58:15.762 48 48 I DEBUG : r0 bea8a42f r1 00000125 r2 0000000
3 r3 bea8a390
09-03 16:58:15.762 48 48 I DEBUG : r4 bea8a42c r5 bea8a394 r6 bea8a39
8 r7 00000122
09-03 16:58:15.762 48 48 I DEBUG : r8 00000000 r9 00000090 10 bea8a94
0 fp 00000090
09-03 16:58:15.762 48 48 I DEBUG : ip bea8a378 sp bea8a370 lr 000099b
1 pc 000095e0 cpsr 00000030
09-03 16:58:15.792 48 48 I DEBUG : #00 pc 000095e0 /data/data
/net.szym.barnacle/files/dhcp
09-03 16:58:15.792 48 48 I DEBUG : #01 pc 000099ac /data/data
/net.szym.barnacle/files/dhcp
09-03 16:58:15.802 48 48 I DEBUG : #02 pc 00009466 /data/data
/net.szym.barnacle/files/dhcp
09-03 16:58:15.812 48 48 I DEBUG : #03 pc 0001fd7a /system/li
b/libc.so
09-03 16:58:15.822 48 48 I DEBUG : #04 pc 0000bcd2 /system/li
b/libc.so
09-03 16:58:15.822 48 48 I DEBUG : #05 pc b000157e /system/bi
n/linker
09-03 16:58:15.832 48 48 I DEBUG : stack:
09-03 16:58:15.832 48 48 I DEBUG : bea8a330 00000960
09-03 16:58:15.842 48 48 I DEBUG : bea8a334 afe0e984 /system/lib/l
ibc.so
09-03 16:58:15.842 48 48 I DEBUG : bea8a338 0000d008 [heap]
09-03 16:58:15.842 48 48 I DEBUG : bea8a33c afe0ed18 /system/lib/l
ibc.so
09-03 16:58:15.842 48 48 I DEBUG : bea8a340 0000d008 [heap]
09-03 16:58:15.852 48 48 I DEBUG : bea8a344 000001b4
09-03 16:58:15.852 48 48 I DEBUG : bea8a348 000000dc
09-03 16:58:15.852 48 48 I DEBUG : bea8a34c 00002bb8
09-03 16:58:15.852 48 48 I DEBUG : bea8a350 00000000
09-03 16:58:15.862 48 48 I DEBUG : bea8a354 afe0b683 /system/lib/l
ibc.so
09-03 16:58:15.862 48 48 I DEBUG : bea8a358 0000ca18
09-03 16:58:15.862 48 48 I DEBUG : bea8a35c 00000090
09-03 16:58:15.862 48 48 I DEBUG : bea8a360 0000b4e0 /data/data/ne
t.szym.barnacle/files/dhcp
09-03 16:58:15.872 48 48 I DEBUG : bea8a364 00000160
09-03 16:58:15.872 48 48 I DEBUG : bea8a368 df002777
09-03 16:58:15.872 48 48 I DEBUG : bea8a36c e3a070ad
09-03 16:58:15.872 48 48 I DEBUG : #00 bea8a370 bea8a390
09-03 16:58:15.882 48 48 I DEBUG : bea8a374 0000ca18
09-03 16:58:15.882 48 48 I DEBUG : bea8a378 bea8a42c
09-03 16:58:15.882 48 48 I DEBUG : bea8a37c bea8a940
09-03 16:58:15.882 48 48 I DEBUG : bea8a380 bea8a45c
09-03 16:58:15.882 48 48 I DEBUG : bea8a384 000099b1 /data/data/ne
t.szym.barnacle/files/dhcp
09-03 16:58:15.892 48 48 I DEBUG : #01 bea8a388 0105a8c0
09-03 16:58:15.892 48 48 I DEBUG : bea8a38c 040300ff
09-03 16:58:15.892 48 48 I DEBUG : bea8a390 00000000
09-03 16:58:15.892 48 48 I DEBUG : bea8a394 00000000
09-03 16:58:15.892 48 48 I DEBUG : bea8a398 00000001
09-03 16:58:15.902 48 48 I DEBUG : bea8a39c bea8a448
09-03 16:58:15.902 48 48 I DEBUG : bea8a3a0 00000010
09-03 16:58:15.902 48 48 I DEBUG : bea8a3a4 0105a8c0
09-03 16:58:15.902 48 48 I DEBUG : bea8a3a8 00000001
09-03 16:58:15.902 48 48 I DEBUG : bea8a3ac 62a2d1a7
09-03 16:58:15.902 48 48 I DEBUG : bea8a3b0 00000000
09-03 16:58:15.902 48 48 I DEBUG : bea8a3b4 00000000
09-03 16:58:15.902 48 48 I DEBUG : bea8a3b8 00000090
09-03 16:58:15.902 48 48 I DEBUG : bea8a3bc bea8a940
09-03 16:58:15.902 48 48 I DEBUG : bea8a3c0 00000000
09-03 16:58:15.902 48 48 I DEBUG : bea8a3c4 bea8a42c
09-03 16:58:15.902 48 48 I DEBUG : bea8a3c8 0000ca18
09-03 16:58:15.902 48 48 I DEBUG : bea8a3cc bea8a924
09-03 16:58:15.902 48 48 I DEBUG : bea8a3d0 bea8a954
09-03 16:58:15.902 48 48 I DEBUG : bea8a3d4 0000946b /data/data/ne
t.szym.barnacle/files/dhcp

It appears that the dhcp that is dying inside / included with the barncale application?

Does anybody have wifi tethering working with Barnacle? My impression was that version 0.5.0 was the correct version to use?

[m1armor]

Same thing happens to me. We need a fix

[BigKitty]

My understanding was we wont be able to get WiFi tethering to work until someone compiles a custom kernal