Page 2 of 5 FirstFirst 12345 LastLast
Results 21 to 40 of 99
  1. #21  
    Just in case this helps anyone spot a trend:

    I have a Pre2 running webOS 2.0.1 and I am also on the AT&T network. I have freshly doctored my phone, installed the already-patched MHS, rebooted, and get the "No Sharing Service" error message when attempting to turn on MHS. ( Screenshot: img.ly photo sharing service for twitter )

    Edit* I should state that I've tried this process twice. Once by first installing FreeTetherD (via Preware), then the second time without it.
    Last edited by germboy; 12/01/2010 at 03:33 PM.
  2. jaltman's Avatar
    Posts
    285 Posts
    Global Posts
    729 Global Posts
    #22  
    Here is a thought that maybe helpful. My wife is still using my old Treo Pro. In the Internet Connection Sharing app there are two network connection choices. AT&T and ICS. They use different logins to the ATT network. The Att choice works with sharing and the ICS choice does not. I will have to research the login differences, but perhaps we need to specifiy the login in the Phone->Preferences->Manual Settings <on> then edit network settings for the right login.

    Now the old gprs type settings dont help, but perhaps this will make a light come on for someone.
  3. #23  
    Quote Originally Posted by TopTongueBarry View Post
    A very real possibility!

    I think Rich is on T- Mobile and he's having the same trouble.

    I used the method William described using the MHS already patched version at the link provided in the thread, then updated that from the app catalog. Still no Internet connectivity from my Laptop, just a connection to the Pre 2 via MHS with the laptop using the first assigned MHS DHCP pool IP address.

    Took a look at the ifconfig output while the laptop was connected to the Pre 2. MHS creates an IP bridge when it is turned on that isnt there without it unless usbnet is previously enabled.

    MHS also creates an interface identified as uap0. Ifconfig indicates no Ip address is assigned directly to the uap0 interface, but the bridge interface has the MHS DHCP server IP address assigned to it.

    The laptop is assigned a DHCP IP address from MHS's DHCP IP Address pool, but as I've stated previously, the laptop has no Internet connectivity (whilst the Pre 2's browser remains Internet connected).

    This actually makes partial sense since MHS uses the IP bridge, and on the Pre 2 dnsmasq is set by default to listen on the loopback interface and the bridge interface but on the Pre and Pre + dnsmasq listens only on the bridge interface by default.

    It would seem both the Pre 2 device and the MHS wifi connected devices could have internet access with this configuration, but I'm not sure. One thing is for certain, I still do not have a connection available to the Internet from my laptop using MHS.

    Its also a real possibility the tweaking I've been doing the past few days for MHS and Amazon app installs might be a factor. Rich and I are going to be doctoring and then trying again.

    I must get some work done today so I won't be doctoring until tonight.
    Did you check the routing tables and see if the interfaces are routed? There should be some kind of NAT going on.
    Palm IIIc -> Sony CLI… T650C -> Sony TJ-37 -> Palm TX -> Palm Centro -> Palm Pre Bell -> Palm Pre Plus Bell/Verizon Hybrid -> HP Veer -> HP Pre 3 NA -> BlackBerry Classic -> BlackBerry Priv

    It's a Late Goodbye, such a Late Goodbye.

    Need OEM Palm Pre parts? See here
  4. #24  
    Quote Originally Posted by germboy View Post
    Just in case this helps anyone spot a trend:

    I have a Pre2 running webOS 2.0.1 and I am also on the AT&T network. I have freshly doctored my phone, installed the already-patched MHS, rebooted, and get the "No Sharing Service" error message when attempting to turn on MHS. ( Screenshot: img.ly photo sharing service for twitter )

    Edit* I should state that I've tried this process twice. Once by first installing FreeTetherD (via Preware), then the second time without it.
    I've doctored my Pre 2 twice tonight, and tried multiple variations of MHS - the two versions, patched, and unpatched, with freetetherd and without freetetherd and have been unable to obtain an internet connection. Getting my laptop connected to the Pre 2 and a stable DHCP TCP/IP address is no trouble at all. I even went to the extreme of replacing the 2.0.1 /etc/dnsmasq.palm.conf, and the /etc/network/interfaces, files with the versions of those files from AT&T1.4.5 doctor and also added the /etc/dnsmasq.conf from that doctor as well because it was there on 1.4.5 but not on 2.0.1.

    That offered some hope because there wasn't any warning about the no sharing service on first attempt to open MHS, but didn't provide the solution to Internet connectivity. The network connections were slow and after turning off MHS, both wifi and 3G would remain enabled. The device was rendered unable to connect to the internet until it was rebooted.
    I examined ifconfig outputs at every stage and from what I can see, the only thing that changes is the local PPP interface is bridged with the uap0 (universal access point) interface and one warning about sharing indicated if my carrier was providing this service, that when MHS is connected, the Pre 2 would still be able to connect to the Internet explaining something along the lines of If I were to browse the internet on my Pre 2 browser while I share my data connection using MHS, all data use would count against my sharing limit whether from the Pre 2 or from my laptop.

    Final thoughts for the night and then some data captures:

    - I've since doctored again and everything is fresh. I've left MHS off for now.

    - I do believe there's some merit to investrigating the point about AT&T's two different networks jaltman makes. Yes there are two data networks. WAP.CINGULAR for the non smartphone data network and ISP.CINGULAR for the smartphone and (laptop data card) data network.
    Maybe because the PRE 2 has a ROW token instead of the ATT token, it's forced to run on the ISP.CINGULAR network (I'm reaching for something, anything at this point) The attached excel file contains the relevent APN data taken from the 1.2.1 carriers file anyone feels inclined to work this path to a possible resolution. Start by changing the APN manually for testing. Be advised, You may need to doctor your phone after messing with these settings.

    Take a look at these data captures. Maybe one of you might see something I missed.

    root@roadrunner:/tmp# netstat -rn | more
    netstat -rn | more
    Kernel IP routing table
    Destination Gateway Genmask Flags MSS Window irtt Iface
    10.64.64.64 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
    192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 usb0
    192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 usb0
    0.0.0.0 10.64.64.64 0.0.0.0 UG 0 0 0 ppp0
    0.0.0.0 192.168.0.200 0.0.0.0 UG 0 0 0 usb0

    root@roadrunner:/tmp/pmnetconfig# cat dnsmasq.server.conf
    cat dnsmasq.server.conf
    server=/mmsc.cingular.com/172.18.7.170 #interfacepp0
    server=/mmsc.cingular.com/172.18.7.170 #interfacepp0
    server=/wireless.cingular.com/172.18.7.170 #interfacepp0
    server=/wireless.cingular.com/172.18.7.170 #interfacepp0
    root@roadrunner:/tmp/tokens# ls -al
    ls -al
    dr-xr-xr-x 2 root root 540 Dec 1 20:26 .
    drwxrwxrwt 10 root root 500 Dec 2 00:45 ..
    -r--r--r-- 1 root root 411 Dec 1 20:26 ACCELCAL
    -r--r--r-- 1 root root 23 Dec 1 20:26 ALSCal
    -r--r--r-- 1 root root 16 Dec 1 20:26 BATToCH
    -r--r--r-- 1 root root 40 Dec 1 20:26 BATToRSP
    -r--r--r-- 1 root root 17 Dec 1 20:26 BToADDR
    -r--r--r-- 1 root root 3 Dec 1 20:26 DMCARRIER
    -r--r--r-- 1 root root 10 Dec 1 20:26 DMCLoAUTHNAME
    -r--r--r-- 1 root root 18 Dec 1 20:26 DMCLoAUTHPW
    -r--r--r-- 1 root root 24 Dec 1 20:26 DMCLoNONCE
    -r--r--r-- 1 root root 7 Dec 1 20:26 DMMODEL
    -r--r--r-- 1 root root 22 Dec 1 20:26 DMSETS
    -r--r--r-- 1 root root 18 Dec 1 20:26 DMSVRoAUTHPW
    -r--r--r-- 1 root root 24 Dec 1 20:26 DMSVRoNONCE
    -r--r--r-- 1 root root 1 Dec 1 20:26 HWoRev
    -r--r--r-- 1 root root 5 Dec 1 20:26 HousingA
    -r--r--r-- 1 root root 1 Dec 1 20:26 KEYoBRD
    -r--r--r-- 1 root root 0 Dec 1 20:26 MfgCode
    -r--r--r-- 1 root root 14 Dec 1 20:26 ModemSN
    -r--r--r-- 1 root root 12 Dec 1 20:26 PN
    -r--r--r-- 1 root root 7 Dec 1 20:26 PRODoID
    -r--r--r-- 1 root root 12 Dec 1 20:26 PalmSN
    -r--r--r-- 1 root root 14 Dec 1 20:26 ProdSN
    -r--r--r-- 1 root root 8 Dec 1 20:26 SimLockDef
    -r--r--r-- 1 root root 17 Dec 1 20:26 WIFIoADDR
    -r--r--r-- 1 root root 10 Dec 1 20:26 installer
    root@roadrunner:/tmp/tokens#
    root@roadrunner:/tmp/tokens# cat DMCARRIER
    cat DMCARRIER
    ROW

    - Forgot to note that the above captures were made without MHS running. Sorry about that, however, these captures may be useful to identify changes between 1.4.5 and 2.0.1

    - I previously posted some file captures in the MHS thread under WebOS patches that were made with MHS installed and running. Take a look there for more information

    - I'll take any requests in here for network or MHS file captures you want made while MHS is running and will post them as soon as I can within a day or so.

    There's a file in /var/logs named wan.log I just stumbled upon it. Its a very long log file and goes back to September, but near the end of it, time stamped while I was working on MHS, I found references to tethering and disconnects. Someone may want to look into this file on their Pre 2 after doing MHS testing. there's also a mobilehotspot.log and a carrierhotspot.log but I didn't see anything useful when I skimmed through them. It was late tonight though. You may want to take a peek at those files on your Pre 2 if you've already tried to get MHS going. Here's a tiny piece of my wan.log file with the tethering and disconnect references:

    2010-12-02T00:49:11.727478Z [389] roadrunner user.notice PmWsfDaemon: {wan.conne
    ctor}: RadioStatusCb: dataconn: 3->0 ppp:2
    2010-12-02T00:53:07.469604Z [624] roadrunner user.warning PmWsfDaemon: {wan.radi
    o}: CallsGetAllCb: voice active: singleActive
    2010-12-02T01:00:59.815277Z [1097] roadrunner user.warning PmWsfDaemon: {wan.ipc
    }: ConnectServiceLunaCb: Connect to service tethered
    2010-12-02T01:01:02.929626Z [1100] roadrunner user.err PmWsfDaemon: {wan.radio}:
    DataConnStatusQueryCb: mipfailure: 36
    2010-12-02T01:01:02.929962Z [1100] roadrunner user.warning PmWsfDaemon: {wan.rad
    io}: UpdateMipCode: causeCode 36
    2010-12-02T01:01:02.930053Z [1100] roadrunner user.notice PmWsfDaemon: {wan.conn
    ector}: RadioStatusCb: dataconn: 0->2 ppp:0
    2010-12-02T01:01:03.863739Z [1101] roadrunner user.notice PmWsfDaemon: {wan.conn
    ector}: RadioStatusCb: dataconn: 2->3 ppp:2
    2010-12-02T01:01:07.143432Z [1104] roadrunner user.err PmWsfDaemon: {wan.radio}:
    DataConnStatusQueryCb: mipfailure: 33
    2010-12-02T01:01:07.143768Z [1104] roadrunner user.warning PmWsfDaemon: {wan.rad
    io}: UpdateMipCode: causeCode 33
    2010-12-02T01:01:07.143859Z [1104] roadrunner user.notice PmWsfDaemon: {wan.conn
    ector}: RadioStatusCb: dataconn: 3->2 ppp:2
    2010-12-02T01:01:36.704376Z [1134] roadrunner user.err PmWsfDaemon: {wan.connect
    or}: PendingDisconnectedTimeoutCb: !!!!!!!! PendingDisconnected timed out
    2010-12-02T01:01:44.325744Z [1141] roadrunner user.err PmWsfDaemon: {wan.auto}:
    --More--
    UpdateRetryTimer: Connect to Internet failed. Updating timer.
    2010-12-02T01:01:44.697143Z [1142] roadrunner user.notice PmWsfDaemon: {wan.conn
    ector}: RadioStatusCb: dataconn: 2->3 ppp:2
    2010-12-02T01:01:50.408813Z [1147] roadrunner user.notice PmWsfDaemon: {wan.conn
    ector}: RadioStatusCb: dataconn: 3->0 ppp:2
    2010-12-02T01:04:48.599914Z [1325] roadrunner user.warning PmWsfDaemon: {wan.rad
    io}: CallsGetAllCb: voice active: singleActive
    2010-12-02T01:09:06.346649Z [1583] roadrunner user.warning PmWsfDaemon: {wan.rad
    io}: CallsGetAllCb: voice active: singleActive
    2010-12-02T01:32:59.108734Z [3016] roadrunner user.warning PmWsfDaemon: {wan.ipc
    }: ConnectServiceLunaCb: Connect to service tethered
    2010-12-02T01:33:02.900299Z [3020] roadrunner user.err PmWsfDaemon: {wan.radio}:
    DataConnStatusQueryCb: mipfailure: 36
    2010-12-02T01:33:02.900634Z [3020] roadrunner user.warning PmWsfDaemon: {wan.rad
    io}: UpdateMipCode: causeCode 36
    2010-12-02T01:33:02.900756Z [3020] roadrunner user.notice PmWsfDaemon: {wan.conn
    ector}: RadioStatusCb: dataconn: 0->2 ppp:0
    2010-12-02T01:33:05.168243Z [3022] roadrunner user.notice PmWsfDaemon: {wan.conn
    ector}: RadioStatusCb: dataconn: 2->3 ppp:2
    2010-12-02T01:33:08.305053Z [3025] roadrunner user.err PmWsfDaemon: {wan.radio}:
    DataConnStatusQueryCb: mipfailure: 33
    2010-12-02T01:33:08.305419Z [3025] roadrunner user.warning PmWsfDaemon: {wan.rad
    io}: UpdateMipCode: causeCode 33
    2010-12-02T01:33:08.305541Z [3025] roadrunner user.notice PmWsfDaemon: {wan.conn
    ector}: RadioStatusCb: dataconn: 3->2 ppp:2
    --More--

    root@roadrunner:/var/log# ls
    ls
    aab.log klog_1.txt.gz ota.log.gz
    bootmark klog_2.txt.gz rdxd
    bt.log klog_3.txt.gz reports
    bt.log.0.gz lost+found root_****.log
    btport md5-files sa
    carrierhotspot.log messages til.log
    dmesg.txt.gz messages.0.gz uimage.log
    download.log messages.1.gz updated.log
    efs.tar messages.2.gz uploadd
    efslogs messages.3.gz uploadd.log
    ****.log messages.4.gz uploadd.log.0.gz
    hll.log minidhcp.log uploadd.log.1.gz
    hwtest mobilehotspot.log var_****.log
    installer.log modeminfo wan.log
    installscripts.log omadm.log wtmp
    root@roadrunner:/var/log#
    Attached Files Attached Files
    Last edited by TopTongueBarry; 12/02/2010 at 05:08 AM.
    ----------------------------------------------------------------------------------------------------
    I am an AT&T employee and the postings on this site are my own and donít necessarily represent AT&Tís positions, strategies or opinions.
  5. #25  
    maybe compare the settings (for your carrier) in the carrier network settings db files on a Pre vs Pre2?

    The settings for my carrier in Australia, include a tether option?
    Last edited by dbmgreen; 12/02/2010 at 01:41 PM.
    HP200LX->Treo270->Treo600->Treo650->Treo680->Centro->iPhone3G->
    Treo680->TreoPro->iPhone3GS->PalmPre->HPPre2->HPVeer 2.2.3->HPPre3

  6. #26  
    Thanks TTB, I Dr'ed as well (only once last night) tried the MHS options again and had the same results, albeit without the same in depth analysis.
    Clicking the Thanks button is a great way to say... well THANKS
    Phone Apps: Church Search, Tap for HELP
    TouchPad Apps: Tap for HELP! HD, webOS Meetups
  7. jaltman's Avatar
    Posts
    285 Posts
    Global Posts
    729 Global Posts
    #27  
    I too note no success. However, and this is along the same lines as TTB's observations, there is a lil app called "what is my ip?" and I note that while it has the WAN address for the provider, it shows no interfaces active. While it is possible it is not picking up the bridge and I can ping the gateway address the laptop sees, but nothing any further. The gateway ip address does not show up in the ip addr checker.

    Also, I note that the 3g connection disappears upon connection and takes several minutes to return on the phone.
  8. #28  
    Quote Originally Posted by jaltman View Post
    I too note no success. However, and this is along the same lines as TTB's observations, there is a lil app called "what is my ip?" and I note that while it has the WAN address for the provider, it shows no interfaces active. While it is possible it is not picking up the bridge and I can ping the gateway address the laptop sees, but nothing any further. The gateway ip address does not show up in the ip addr checker.

    Also, I note that the 3g connection disappears upon connection and takes several minutes to return on the phone.
    This is not going to be easy. PmNetConfigManager is completely different in 2.xx The changes impact MHS WiFi and USBnet tethering connections.

    EDIT: possible breakthrough found:
    This might be our salvation.Theres a file located in /usr/bin named settethered. It has two switches available to use, on and off. When you run ./settetethered on (rooted of course) First thing it does is check for the type of network and when it detects gsm, it spits out an error message that it is not designed to be used on a gsm network. Clearly it is meant to be used only on CDMA networks. I'm hoping this file allows tethering the old fashoned way, like we used to do in WebOS 1.xx, using IP forwarding instead of bridging the traffic together over a point to point connection which is what we're seeing in WebOS 2.xx GSM versions as I describe in the original post below.Then again, it it coiuld just be used to toggle between tethered data capped use and non data capped smartphone use on cdma networks. No matter what settethered does, we do know it wasn't present in 1.4.5 and below, so it may offer us some help.If you're itching to help us out, then please explore this.

    RE: PmNetConfigManager, Here's what I've discovered this far. The PPP connection changes drastically when MHS is turned on or a USB cable is connected and you've set USBnet to enabled. Take a look at the output of ifconfig without MHS turned on or USBnet enabled, then look at it with either a USBNET tether configured, or with MHS turned on. Another good command is netstat -rn. Also try netstat -rnee and be prepared to read through wrapped data output.

    With USBnet or MHS, the bridge0 interface turns into a network and all trraffic is routed through a psuedo IP 10.64.64.64 with a mask of 255.255.255.255

    Without USBnet or MHS turned on, the PPP traffic uses a NAT IP Address randomly assigned when the Pre 2 is restarted. 10.xxx.xxx.xxx. This address can be seen in ifconfig output. After turning on USBnet and connecting a tether, OR turing on MHS, bridge0 (or usb0) and ppp interfaces use the 10.64.64.64 IP address to pass IP traffic. That's why the warning was seen previously about if your carrier has enabled your sharing services, then while MHS is on any devices connected to it and the Pre 2 will have Internet connectivity, but all traffic will count against your monthly sharing limit whether it is from the Pre 2 or from connected devices.

    We need to figure out how this is being accomplished in WebOS2 and how to turn it off . Once we can do that, I suppose we can work out an IP forwarding patch that will work on the new platform.

    Otherwise, be resigned to subscribing to your carriers tethering service, if your carrier happens to offer it.

    WebOS Internals references below:

    There's many changes in the software that drives the modem between the Pre/Plus and Pre 2.

    PalmPre2HardwareAndDriversInformations - WebOS Internals

    There's many differences in the way WebOS2 on a Pre 2 handles Network Management. Here's the WebOS Internals Wiki documenting Network Management on WebOS 1.xx

    Network Management - WebOS Internals

    If anyone wants to help, PmNetConfigManager is what really needs to be looked at in WebOS 2.0.1. PmNetConfigManager is the main service executable. It starts com.palm.firewall, com.palm.netroute, com.palm.bridge, com.palm.nettools and com.palm.connectionmanager.
    EDIT: If you're looking to help out, tearing apart PmNetConfigManager is probably just as important as figuring out what settethered is used for.....

    Thanks,
    TTB
    Last edited by TopTongueBarry; 12/03/2010 at 06:17 PM.
    ----------------------------------------------------------------------------------------------------
    I am an AT&T employee and the postings on this site are my own and donít necessarily represent AT&Tís positions, strategies or opinions.
  9. jaltman's Avatar
    Posts
    285 Posts
    Global Posts
    729 Global Posts
    #29  
    I'd be tempted to suggest something silly, like in settethered, on line 191 change "cdma" to "gsm<null>" and see what happens.

    Its the only occurence of cdma in the file and is right next to the "%s doesn't support tetheredset. exiting..."

    Just a thought.
  10. PLinger's Avatar
    Posts
    120 Posts
    Global Posts
    124 Global Posts
       #30  
    Are the reasons why HP isn't including the Mobile Hotspot app for the Pre2? It's not unusual for unlocked phones to come with tethering (WinMo and Symbian phones have had that feature for years) and the Pre2 isn't available via any US Carrier anyway. It's a good selling point for the phone.
  11. #31  
    Quote Originally Posted by Linger View Post
    Are the reasons why HP isn't including the Mobile Hotspot app for the Pre2? It's not unusual for unlocked phones to come with tethering (WinMo and Symbian phones have had that feature for years) and the Pre2 isn't available via any US Carrier anyway. It's a good selling point for the phone.
    It is included on the Pre 2. It's dependent on the carrier. It comes on the locked to SFR Pre 2 and will be on the Verizon Pre 2 also. I suspect one of the reasons for the network configuration changes we have seen in WebOS2 is so the carriers can meter and charge us for tethering use. That, and to keep us from using it for free with ip forwarding.
    ----------------------------------------------------------------------------------------------------
    I am an AT&T employee and the postings on this site are my own and donít necessarily represent AT&Tís positions, strategies or opinions.
  12. #32  
    Quote Originally Posted by BillyTT View Post
    All I did was:

    Installed the webos quick install, and used the 2.0.1 doctor from the webosinternals page, so that I can load a package. (installed Preware but did not use it for anything else)

    Then I grabbed the Mobile hotspot version 1.0.14 package, that you can find all over the internet and installed it on the Pre2. (see Livioo's post above)

    As soon as the hotspot was on my Pre2 it detected it and the Software Manager immediately notified me an upgrade was available, which I installed and that's all. (No 'Free Tether' patch as on 1.4.5.)

    I also did one complete reboot with battery taken out for good measure.

    The whole thing took just a couple of minutes. (I am on 2.0.1)
    Nice find. This may be slightly off topic from the original bent of this thread but can I take the opportunity to ask what people are actually using this feature for / how they use it? Not sure I could see myself using it so just wanted to understand different use scenarios.

    Cheers,
    Mark
    ___
    My Palm PDA history: m130 > Tungsten T > Tungsten T|X > Pre 2 > HP Pre 3 (unlocked)
    My Mobile history: Nokia 5146 > 3110 > Samsung D900 > N73 > Nokia 6300 > Pre 2 (convergence!) > HP Pre 3
    My Tablet history: HP TouchPad 32Gb (model A - 1st gen)
  13. #33  
    I pretty much just bought a WebOS phone especially for this feature (among others). I know other cheap smartphones could do it (Android, Symbian and Blackberry have mobile hotspot capabilities as well) but nothing gives me more bang for bucks than a cheap Pixi Plus with an unlimited 3G pay as you go option and wireless tethering. I pretty much use it when I'm somewhere where I don't have wifi for my laptop and it saves money otherwise spent on a 3G modem probably. I also plan on buying and iPad and if 2.0 does not support this feature, I really can't afford a 3G enabled iPad and an extra plan for mobile internet for it. That's why I pretty much asked here if it works on 2.0.

    Ontopic: I will admit I'm not as good at debugging as TopTongueBarry is but the symptoms you are experiencing on 2.0 are pretty much similar to what happened to us 1.4.5 folks after updating the MHS app to the latest version: the laptop/ipod touch (in my case, forgot to add how awesomely nice is this combo, it basically gives me another (skype) phone) will connect to the wireless hotspot but no actual data transfer will occur. This was fixed on 1.4.5 by manually patching the MHS app to the latest version. I heard that the MyTether guys are planning support for 2.0 but MHS is so much more natural and easier to set up so it would be a shame if we can't get it to work.

    If all the rumors/inside info the webOS community has here in the UK are right, we are about to receive the (first) webOS 2.0 OTA update on monday, december 6th. If that's still the case I shall test the patched version with my Pixi+ and report back here. The problem might be carrier specific since BillyTT does report that it is functional on a European network.

    Thank you guys for debugging and digging deep to figure out the problem. I'm new to Precentral forums and really love the enthusiasm and loyalty of the community towards Palm and webOS.
  14. #34  
    Quote Originally Posted by livioo View Post
    the symptoms you are experiencing on 2.0 are pretty much similar to what happened to us 1.4.5 folks after updating the MHS app to the latest version: the laptop/ipod touch (in my case, forgot to add how awesomely nice is this combo, it basically gives me another (skype) phone) will connect to the wireless hotspot but no actual data transfer will occur. This was fixed on 1.4.5 by manually patching the MHS app to the latest version.
    We're all aware of what transpired after the 1.4.5 update as most of us went through it. If you have a moment to read through the beginning of this thread and the threads in the patching forum relating to MHS and WebOS2, you'll note several folks have tried the methods you refer to.
    The only one's who have been successful happen to be on carriers who allow tethering and either offer it free with their plans or charge extra for it - usually offering a 5GB tethering pkg for a monthly fee tacked on to the customers plan as a feature. The lucky ones are the ones who's carriers allow it and do not charge extra for it YET.

    That being said, there's a whole group of us who's carriers do not offer Palm Web OS users a tethering option YET. They offer Blackberry and iPhone tethering for a monthly fee or they don't offer tethering at all claiming they don't allow it. For those in that situation, there's no legitimate option available. That is the basis for most of the energy placed into the MHS and MyTether forums.

    The problem were facing now after the release of WebOS2 is different than the problems seen after previous upgrades to WebOS, even if it appears to mimic the same issue seen after WebOS 1.4.5 was released, it doesn't. It's a far cry from a problem with Ip forwarding of tethered data from MHS to the PPP connection. WebOS 1.x.x (all versions) used IP forwarding to accomplish Internet connectivity to tethered (WiFi and USB) devices. The 1.3.1 and 1.4.5 upgrades presented problems after the upgrades due to the changes Palm made to PMnetconfig, but IP forwarding was still the basis for Tethering connectivity to the Internet.

    In the MHS 1.1.4 application, Palm also introduced a user configurable DHCP server instead of relying on the OS's dnsmasq.palm.conf file for DHCP capabilities. That provided another change requiring the patch to be rewritten in order for those of use whose carriers do not offer tethering packages. For those who were lucky enough to have a carrier that offered tethering whether free or measured, the MHS1.1.4 upgrade usually worked right out of the gate after the upgrade. It's the rest of us who have really suffered through all the changes, especially now.

    In WebOS2 the Tethering, whether by USBnet or Wifi (MHS) is routed over a TCP/IP point to point bridge so the carriers can see what traffic is tethered and what isn't. They can also measure tethering data use because it's easily colored by devices and OS's for carrier detection over PPP.

    The problem we're seeing is a result of this change to point to point data sharing with the device. Not some data, but all of the data traffic. The lack of Internet connectivity for MHS and USBnet tethered connections has nothing to do with IP forwarding, or DHCP. MHS 1.1.4 handles the DHCP for itself, and the Pre 2 is more than willing to hand off a network IP address when its asked for one, but having that doesnt get one to the Internet over their carrier's point to point connection unless the carrier is willing to allow that data to connect. Or unless a solution is found through these forums, or any carriers witout tethering packages offer it as an included or paid for option.

    Quote Originally Posted by livioo View Post
    If all the rumors/inside info the webOS community has here in the UK are right, we are about to receive the (first) webOS 2.0 OTA update on monday, december 6th. If that's still the case I shall test the patched version with my Pixi+ and report back here. The problem might be carrier specific since BillyTT does report that it is functional on a European network.

    Thank you guys for debugging and digging deep to figure out the problem. I'm new to Precentral forums and really love the enthusiasm and loyalty of the community towards Palm and webOS.
    Glad to hear of another WebOS update ....

    Yes BillyTT happens to be on a carrier that verified his ability to tether. Whether hes' paying for it or they are including it free , the bottom line is he has his carriers blessing to tether. His MHS worked after the upgrade as I mentioned it does when the carrier allows point to point tethering traffic to pass.

    The carriers now have the ability to decide what traffic can pass and what traffic can't pass, and as for charging for tethering, they're entitled to do that. However if they use their ability to know what type of data is passing over their network, and choose to restrict some types of data on their own accord for anything other than bandwidth regulation, then personal freedoms can be infringed upon and thats when it becomes a completely different discussion.
    Last edited by TopTongueBarry; 12/04/2010 at 03:23 AM.
    ----------------------------------------------------------------------------------------------------
    I am an AT&T employee and the postings on this site are my own and donít necessarily represent AT&Tís positions, strategies or opinions.
  15. PLinger's Avatar
    Posts
    120 Posts
    Global Posts
    124 Global Posts
       #35  
    Quote Originally Posted by TopTongueBarry View Post
    It is included on the Pre 2. It's dependent on the carrier. It comes on the locked to SFR Pre 2 and will be on the Verizon Pre 2 also. I suspect one of the reasons for the network configuration changes we have seen in WebOS2 is so the carriers can meter and charge us for tethering use. That, and to keep us from using it for free with ip forwarding.
    I still don't fully understand this. The Nexus One was an unlocked phone also sold directly to consumers/developers and it has the Wifi tethering. Are you suggesting the mobile hotspot is exclusive to Verizon (like Skype) or that T-Mobile and AT&T are stopping HP/Palm from offering the feature on an unlocked phone which neither carrier has plans to subsidize?

    Quote Originally Posted by TopTongueBarry View Post
    We're all aware of what transpired after the 1.4.5 update as most of us went through it. If you have a moment to read through the beginning of this thread and the threads in the patching forum relating to MHS and WebOS2, you'll note several folks have tried the methods you refer to.
    The only one's who have been successful happen to be on carriers who allow tethering and either offer it free with their plans or charge extra for it - usually offering a 5GB tethering pkg for a monthly fee tacked on to the customers plan as a feature. The lucky ones are the ones who's carriers allow it and do not charge extra for it YET.

    That being said, there's a whole group of us who's carriers do not offer Palm Web OS users a tethering option YET. They offer Blackberry and iPhone tethering for a monthly fee or they don't offer tethering at all claiming they don't allow it. For those in that situation, there's no legitimate option available. That is the basis for most of the energy placed into the MHS and MyTether forums.
    Is MyTether a viable alternative? I didn't want to use it before because I am leery of 'forced donationware'. I'm not averse to paying for apps or supporting independent developers but the forced donationware appears to me as a way of getting money without providing support and I've been burned before... like livioo, the sophisticated WiFi tethering is a big reason why I chose webOS...
  16. mike5's Avatar
    Posts
    762 Posts
    Global Posts
    782 Global Posts
    #36  
    Quote Originally Posted by BillyTT View Post
    All I did was:

    Installed the webos quick install, and used the 2.0.1 doctor from the webosinternals page, so that I can load a package. (installed Preware but did not use it for anything else)

    Then I grabbed the Mobile hotspot version 1.0.14 package, that you can find all over the internet and installed it on the Pre2. (see Livioo's post above)

    As soon as the hotspot was on my Pre2 it detected it and the Software Manager immediately notified me an upgrade was available, which I installed and that's all. (No 'Free Tether' patch as on 1.4.5.)

    I also did one complete reboot with battery taken out for good measure.

    The whole thing took just a couple of minutes. (I am on 2.0.1)

    Cheers, William
    Impressive as it takes more than a couple minutes for my Sprint Pre- just to reboot.
  17. #37  
    TopTongueBarry, thank you... I've started reading all of the threads I'm interested in this problem. I now fully understand what the problem is.

    I'm afraid that if O2 UK does not support wireless tethering and has such a refined way to detect and block specific data transfers on my device I will not be upgrading. Nonetheless I'm still hopeful.
  18. #38  
    Quote Originally Posted by livioo View Post
    TopTongueBarry, thank you... I've started reading all of the threads I'm interested in this problem. I now fully understand what the problem is.

    I'm afraid that if O2 UK does not support wireless tethering and has such a refined way to detect and block specific data transfers on my device I will not be upgrading. Nonetheless I'm still hopeful.
    Not sure, but I think O2 UK does allow it. If they do, I'm sure they'll charge for it. Does O2 UK ever offer any free bonus's to their customers?

    Let us know about their tethering options here in this thread. I'm thinking it miught not be a bad idea to start a list of carriers that allow tethering, whether its included free or as a tiered data feature plan add-on.

    Barry
    ----------------------------------------------------------------------------------------------------
    I am an AT&T employee and the postings on this site are my own and donít necessarily represent AT&Tís positions, strategies or opinions.
  19. #39  
    Hi

    I am deeply interested in this thread about the MHS.
    Though I am a Palm enthusiast however I don't fully understand all the info about DHS and IP bridge etc.
    It seems an un-necessary complicated way for Palm to do things just to monitor tethering traffic or to restrict tethering in the device.

    I was looking at another thread on modifying webos carrier settings
    http://forums.precentral.net/gsm-pre...ettings-2.html
    and found this:
    With this change the values for supportedService and serviceDefault seem to be:
    0 different descriptions: push email, email, VPN, prepaid, streaming and even WAP and MMS
    1 GPRS (and 3g?)
    2 WAP
    4 MMS
    5 Thether

    can one modify a carrier settings to have option 5 ie tethering?

    I have a unlock european GSM palm pre 2 but activated in Singapore running 2.0.1 (OTA update)
    I have added MHS, and it self updates to 1.1.14.
    Unfortunatedly MHS doesn't work. Same problem as everyone else. It can connect but no internet traffic allowed.

    I have gone to the phone settings and tried to manually edit the internet settings eg APN etc. Strangely enough, the phone doesn't save the change settings.

    Thanks to all the guys doing great work on trying to solve this problem
  20. #40  
    Hi Everyone,

    A quick update, as I was traveling in Switzerland, I took out my LuxGSM sim card and used a Swisscom one. (this one is regular business subscription with data enabled, 1Gb a month included)

    Hotspot worked here as well with a Swisscom card in Switzerland.

    (Just for the record as a few of you were wondering what type of plan I have for my LuxGSM Sim, it's an unlimited everything within Luxembourg, call local, call local mobile, all sms, all mms & unlimited data (25Gb a month, then slows down) for 50Euro a month.)

    Cheers, William
Page 2 of 5 FirstFirst 12345 LastLast

Posting Permissions