View Single Post
  #1 (permalink)  
Old 10-03-2007, 05:11 PM
ebmorgan's Avatar
ebmorgan
Halfway to VIP Status
Offline
Location: Seattle, WA.
 
Join Date: Mar 2007
Posts: 554
Reputation: 417
ebmorgan is becoming a PPCGeeks regularebmorgan is becoming a PPCGeeks regularebmorgan is becoming a PPCGeeks regularebmorgan is becoming a PPCGeeks regularebmorgan is becoming a PPCGeeks regular
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Debunking the Multi-NAI Myth

I've been doing research into this reg hack that has become to be beleived somehow hides your devices connection method from your carrier. The purpose of this would be so you can tether a device without your carrier finding out.

I don't think Multi-NAI does what everyone thinks it does.

NAI (Network Access Identifier) is, simply put, a roam-able method of identifying users to authentication server accross multiple providers. All that an NAI contains is a user name and routing info regarding the location of your carriers authentication server(s). So basically what it's used for is the authentication of your phone for IOTA handoff over multiple systems, including other carriers towers for IOTA while roaming.

If you're interested you should go read the RFC 4282 document which defines the NAI technology. NOWHERE is it stated that NAIs have anything to do with connection types or even connection states....only user names for authentication and auth server location info....that's it.

So, in my conclusion, disableing Multi-NAI does NOT hide your connection method from your provider. Why? Because that's not what NAIs do. In fact, with out NAIs you may have a problem with your IOTA when you roam because your phone may not be able to find it way to Sprint IOTA authentication servers.
__________________
MPx-200 -> MPx(300) -> MPx-220 -> MotoRZR -> Moto V600 -> SMT 5600 -> PPC-6700 -> Treo 700wx -> Mogul -> Diamond -> Touch Pro -> TOUCH PRO 2 -> HTC EVO 4G

Last edited by ebmorgan; 10-03-2007 at 06:31 PM. Reason: typos
Reply With Quote