Quote:
Originally Posted by niteriderxp
... That being said Bluetooth DUN should work without any additional software if the DUN NAI has been changed. It will also give you a non-NATed public IP.
... Now if your company uses IPSEC, the protocol is a bit more complex and does not like traversing NAT.
|
I have tried this method of BT DUN:
http://forum.ppcgeeks.com/showthread...35#post1780335
you do get internet but there is still no nonNAT'ed iP. I chked after connecting and i still got an internal ip of l92.l68.*. And I think I know why. Under the HKLM/software/Widcomm/plugin/DUNServer there is a string value: "ModemInterface = ICS".
So in essence the BT DUN just use ICS so instead thr USB it's now thr BT.
Once again, I don't know if Sprint is specifically targeting nonNAT'ed ip even more intensive in their effort to clam down on tether. It seems every method to successfully tether on TP2 so far has resulted in a NAT'ed ip.
Please, if anyone here has an idea of how we can tether on TP2 w/ a nonNAT'ed ip (be it wmodem or any method) , please say it. All of us w/ IPSEC and certain other VPN really need the nonNAT'ed ip.