Tethering Bold 9000 with Mac over bluetooth (4.6.0.247)

[bermudache]

I'm about to downgrade. I can't get anything to work.

[khanam]

Guys, bluetooth tethering is pretty slow anyway and clunky. Install the usb tether program from thibaut colar. Much faster and os version makes no difference. Do a search and u will find it.

Posted from my CrackBerry at wapforums.crackberry.com

[tomte]

That would defeat the purpose of bluetooth : no cable. That's way more convenient to click on "connect bluetooth" than fumble for the usb cable, etc. And my experience with 4.6.0.162 bluetooth tethering is solid stable. I've been using it for hours without drops.
I am wondering if this Blacberry 3G modem script has something to do with the .2xx incompatibility. I can't remember where i found this script but i'm pretty sure it is not an official RIM file. Maybe the way the new OS interacts with this script prevents to get an IP from the ppp negociation.

Posted from my CrackBerry at wapforums.crackberry.com

[csete]

Looking at the logs, it appears that the problem occurs when the PPP negotiation tries to negotiate an IPV6 address for the connection. At least for me, IPV6 is not necessary. I've been unable to get the standard Network Preferences to not send that request, but I have been able to build out some scripts outside Network Preferences that correctly negotiate the connection.

Unfortunately, while the connection is successfully negotiated, no data will flow at this point. I haven't had time to debug things any further to try to understand why data isn't flowing. Assuming I can get this going, it will make it much clearer why the Bold may be failing and allow a proper bug report to RIM.

[tomte]

Looks like you're on the good track.
When you say "the connecttion is successfully negociated", does this mean that ppp is up with an IP and connectivity ? Or just that the link is up ?

[csete]

Good question...

I could have sworn that all of the PPP and LCP negotiation had been done and the IP connection was alive. The other night I sat down to look at it again and the peer was rejecting the connection after the negotiation... I'm still digging in between "real life".

[tomte]

Ah. Could you post the ppp.log of the negociation? I could do the same from a 4.6.0.162 OS and check what differs.

[csete]

I spent way too many hours on this today and I'm still drawing a blank. I've been playing with raw pppd scripts all day as well as the standard internet connection from Network preferences. I seem to get about the same results either way. It appears that the negotiation spins while trying to retrieve the DNS settings.

I've attached the logs from my Mac (mac2.txt) and also from my Ubuntu (8.10) machine. Ubuntu negotiates the connection just fine with the Bold, but the Mac won't negotiate the connection at all. Thus, while something may have changed in later Bold versions, it is likely also somewhat a problem with the Mac PPPD handling.

One thing that I noticed between the logs that may or may not have anything to do with the problem is the sending of ms-dns3 instead of ms-dns2.

Mac:
sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]
rcvd [IPCP ConfNak id=0x2 <compress VJ 0f 01> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]

Ubuntu:
sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]

The other thing that stands out to me as being different is the timing of the protocol requests. The Mac sends/receives very quickly, while the Ubuntu box spaces out the requests. It may be a situation where the peer is not fast enough.

That's what I have at this point. I've been staring at it for too many hours and I'm starting to go cross-eyed. I'm looking forward to seeing the logs from a working firmware to see if anything stands out.

Thanks,
Craig

[csete]

It doesn't look like it allowed me to attach (probably because I'm a newbie on this forum?)

I put the files on my web server (mangled) to get them to post:

http: slash slash setera.org/misc/ubuntu.txt
http: slash slash setera.org/misc/mac2.txt

[tomte]

Here's a log from my working firmware (4.6.0.162) :
http slash slash pastebin.com/fe3c4c32

[tomte]

dns3 is part of mac's negociation, but does not prevent the working firmware to sucessfully bring the link up :
Sun Apr 19 09:01:49 2009 : sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]

Did you try to negociate a ppp link without the dns ?

[tomte]

hm okay there's definitely something related to the dns negociation, or something that happens at the same time. The two mac logs look exactly the same till the local and remote IPs are set. Then at some point the mac hosts asks for 3 dns settings :

Sun Apr 19 09:01:49 2009 : sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]

And things start to differ from here :
On the working firmware, the remote host answers :

Sun Apr 19 09:01:49 2009 : rcvd [IPCP ConfRej id=0x1 <compress VJ 0f 01> <ms-dns3 0.0.0.0>]

Not sure what this ConfRej[ect] means but that's probably something to do with not serving a 3rd peer dns address. This ms-dns3 is gone forever in the rest of the negociation, which eventually succeeded. This line is not present in the b0rked firmware, and i suppose that is why the negociation loops while endlessy asking for this :

Sat Apr 18 20:40:40 2009 : sent [IPCP ConfReq id=0x8 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]

and miserably fails.
Now the question is, why this reject is not present in the new firmware negociation? Maybe you're right and the flow is too fast to get interpreted... i honestly have no clue at this point. But all this looks that we may be able to fix it from the client side and not wait for a RIM solution.

[csete]

I will spend some more time looking at this... I can say that one of the things I tried along the way was to tell it not to use the peer DNS which eliminated the calls for ms-dns, but still failed. BTW - it should be ms-dns1 and ms-dns2, not ms-dns3. I'm still not sure what Mac is up to there....

[TeritaM]

I couldn't even get my mac to recognize the bold as an outside drive. let alone tether. I tried downgrading and still nothing. it's like big bertha doesn't exist unless I use the windows partition.

I'm going back up to .247.

[tomte]

oh, so it does not loop on the ms-dns3 Nak but stills fails ?