Blackberry Tethering

I am able to tether from my blackberry via bluetooth with a "dial-up" connection.

All I did was setup the network(at@t) and a "dial number"(*9***1#) on my bluetooth device to tether.

But I don't really understand how this works. Can someone here help explain this to me?:confused

 

basiculy what ever devices your tethering with, is using your phone as a modem of sorts, despite the connection being from device to device with blue tooth, it uses the dial up networking component to make part of that connection happen.

 

The weird thing is this phone has lots of proxys and security features on it, and so far this is the only thing of this kind that I have been able to get working.

All I know is that everytime it connects the phone says "modem mode enabled" and it connects with dial-up networking. So is "dial-up" just a way of sending data to another device?

 

Yes in a simplified manner.

 

This phone has done a good job of blocking this type of thing(I think)

I did not do anything with my phone beside pairing it(which I do to my ear pieces and other things)

I'm not a hacker or anything but somehow I found this "loop-hole" :-D

 

Yes, most providers want you to pay extra for tethering

 

It's not so much that as it is the fact that it's a work phone, so that's why all the security features are there.

I am trying to find out about this to make sure this does not become a problem. I don't think it will because my device that I tether to does not have any access to my phone.

The phone just receives and sends out data(with dial-up in this case) just like I do when surf the web with my phone all time.

Plus I am on an unlimited data plan. There is no reason this setup would be problem right?:confused

 

Providers hate when people on unlimited devices tether a laptop/netbook so on to a phone, because its "harder" to use a bunch of data on a device with a fairly small screen, but you hook a full size laptop up with a keyboard and it becomes alot easier to push large numbers of traffic.

 

It's not so much the provider(AT@T) having a problem with it. It's more of my work thinking that this is some kind of "security breach"

Which I don't think it is.