[slinkeey]

Hello,

I am using my BB as a modem and it is working great for mostly everything.

Is there a way to have the BB assign my PPP connection a different IP scemed IP address?

Long story short. The network at my office is on the same ip scheme so VPN is hairy..
I usually end up finding a hotspot because I need a different IP..

I can hit a few machines that are on some oddball subnet, but the main network just happens to be numbered the same as the IP address I am getting from the BB.

[dc/dc]

No. The IP your BlackBerry receives is assigned by your service provider and there is no way to change it.

[johnling]

The IP is assigned by the router each time you log onto a network. It can be and most likely is different each time you log in. If you have access to the router you could assign a static IP and see if that solves your problem.

[dc/dc]

Originally Posted by johnling

The IP is assigned by the router each time you log onto a network. It can be and most likely is different each time you log in. If you have access to the router you could assign a static IP and see if that solves your problem.

It is not possible to access AT&T's routers to make any such changes.

[slinkeey]

I am not talking about being plugged into a router unless oyu are talking about a router built into the phone..

Actually that is what I was wondering.. I was hoping the phone was assigned an IP address from AT&T and then when I tether I am assigned a IP address from the phone.

[dc/dc]

Originally Posted by slinkeey

I am not talking about being plugged into a router unless oyu are talking about a router built into the phone..

Actually that is what I was wondering.. I was hoping the phone was assigned an IP address from AT&T and then when I tether I am assigned a IP address from the phone.

I know you weren't talking about that which is why I corrected the other guy.

And no, the IP address that your phone is assigned is the one your computer uses. There are no additional routing processes involved.

There is no easy solution to your problem unfortunately. The easiest one would be for you to use a different provider for mobile broadband. The other, but far more difficult solution would be to request to your company IT department that they change the public IP address of their VPN concentrator to allow you to connect whilst you're mobile. I highly doubt they will do that (depending on the size of your company), so I would be prepared to do something different yourself.

[slinkeey]

Maybe I can do some slick routing on my notebook..

I will see if I can create a virtual adapter on a 192.168 network in ubuntu that routes traffic to my ppp connection. Then when I try to go to a 10.x addess it wont be thinking to use the local network instead of the vpn route..

[dc/dc]

Originally Posted by slinkeey

Maybe I can do some slick routing on my notebook..

I will see if I can create a virtual adapter on a 192.168 network in ubuntu that routes traffic to my ppp connection. Then when I try to go to a 10.x addess it wont be thinking to use the local network instead of the vpn route..

Actually, now that I think about it, since you have Linux, you might be able to build some interface-based static routes. Is there at least one octet of the IP address that is different between your company's VPN interface and the AT&T connection (e.g., VPN = 10.10.x.x, AT&T = 10.11.x.x)?

[slinkeey]

Yes..
The Offic Lan has:

10.10.x.x
10.20.x.x
10.30.x.x

The PPP connection is getting 10.56.x.x

[slinkeey]

Yes..
The Office Lan has:

10.10.x.x
10.20.x.x
10.30.x.x

The IT department went a little wild..

The PPP connection is getting 10.56.x.x

[dc/dc]

Ok, then I think we can make this work. You obviously seem familiar enough with Linux, so here's the basic commands that should make this work (you will probably need to tweak it):

# The following lines will route your office traffic through the VPN tunnel whilst all other traffic goes out through the BlackBerry directly to the Internet
#
# In each line, after "dev", enter the VPN interface number
#
route add -net 10.10.0.0 netmask 255.255.0.0 dev vpn0
route add -net 10.20.0.0 netmask 255.255.0.0 dev vpn0
route add -net 10.30.0.0 netmask 255.255.0.0 dev vpn0

I'm not guaranteeing this will work, but it's the best I've got.

[slinkeey]

Thank You Sir!

That worked..

I just added:
route add -net 10.20.0.0 netmask 255.255.0.0 dev tun0

This is the only part of the network I care about... (AS400 and My Desktop are ont his network..)

It added an entry with 0.0.0.0 as the gateway....

I am suprised it wouldn't work before this as 10.0.0.0 netmask 255.0.0.0 was added to my routing table by OpenVNC but the difference was th 10.0.0.0 was pointing to OpenVNCs IP as the gateway..

Unless drilling down to 10.20 makes darn sure that my own network between the BB and myself doesn't try routing it on it's own..

Jeff

[dc/dc]

Originally Posted by slinkeey

Thank You Sir!

That worked..

I just added:
route add -net 10.20.0.0 netmask 255.255.0.0 dev tun0

This is the only part of the network I care about... (AS400 and My Desktop are ont his network..)

It added an entry with 0.0.0.0 as the gateway....

I am suprised it wouldn't work before this as 10.0.0.0 netmask 255.0.0.0 was added to my routing table by OpenVNC but the difference was th 10.0.0.0 was pointing to OpenVNCs IP as the gateway..

Unless drilling down to 10.20 makes darn sure that my own network between the BB and myself doesn't try routing it on it's own..

Jeff

Awesome! Glad it worked.

0.0.0.0 is the default route and should always be there. It is dynamic based on how your computer is connected to the Internet at the time.

The reason that the 10.0.0.0 255.0.0.0 entry did work is that with that network mask it was including both the 10.20.0.0 and 10.56.0.0 traffic in that route. By default, computers try to summarize routes as much as possible, and this is normally seen as best practice in networking, but in some cases such as yours this can cause problems.