On Wed, 23 Feb 2005 23:29:57 +0100, Terje Midtbø <(E-Mail Removed)>
wrote:
>Thank you for your answer. This evening I have done some more research,
>and it sems like my local peer-to-peer network goes down the moment my
>VPN connection is established. When close down the VPN my local network
>is OK again. I have tried to generate some network activity without the
>VPN, and it does'nt seme to influence on my local network.
>
>Any suggestion on what I can do?
Several possibilities.
1. Your routes change when you connect to the VPN. Run:
route print
before and after connecting to the VPN. See where your local packets
are going. Post both results and we can help. While you're at it,
kindly disclose what operating system you're using, what version, what
VPN client, what version, what wireless service you're using, IP
address assignments, and anything else that might seem useful.
2. You configured your ad-hoc network to be the same as the VPN IP
block. If your VPN delivers an IP address as 192.168.22.xxx from its
IP address pool, then you should NOT use 192.168.22.xxx for the ad-hoc
network. The 192.168.xxx.xxx is fine, but don't re-use
192.168.22.xxx. Depending on the client and/or OS, your routing will
be a mess. Run:
ipconfig /all | more
to see what IP addresses are assigned to which interfaces.
3. Isolating the VPN traffic from the rest of the network is a
security feature of many VPN clients. For example, the Boigo wireless
client disconnects the user from anything outside the VPN address
space. This is normally a good thing as it protects against client to
client hacking and worm distribution. In a host spot environment,
there's also no reason to connect to other nearby clients.
Methinks #3 is the most likely, especially if you're using Boingo.
--
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831.336.2558 voice
http://www.LearnByDestroying.com
#
(E-Mail Removed)
#
(E-Mail Removed) AE6KS