Re: Wireless security.



On Sun, 18 Dec 2005 20:31:28 +0000, "Hello!" <efjewjfjef@xxxxxxxxxxx>
wrote:

>There is one thing I do not understand about the concerns regarding
>wireless network security. Around where I work there are plenty of open
>and unsecured connections. One can connect and you get an IP address,
>DNS IP address, etc, there is decent signal strength, no dropped
>connections, etc.
>
>However, there is absolutely no way to use said networks - whilst
>packets are being sent and recieved, trying web, traceroute, etc, does
>not give any connection. Nothing happens.
>
>So, what is the problem because just because the network can be
>connected to, if no user can actually use it, then why do people get
>agitated about it?
>
>Of course, I guess it may be a problem with my computer, but since I can
>access other wireless networks, it would seem unlikely.
>
>Sorry for my naivete here.

There are lots of ways to secure a wireless connection. One of the
more popular ways with business WLAN's is to not secure the wireless
connection at all, and run everything over a VPN connection. The VPN
traffic is encrypted and is therefore sniffer safe. Authentication is
left to the VPN.

However, all the one's I've seen have a splash screen that greets the
casual hacker with threats of prosecution if they continue beyond the
initial connection. You're expected to fire up your VPN software, or
connect via SSL/TLS to an obscure authentication server. If you don't
know the name of the server, you don't go anywhere. I guess someone
is setting up a similar system but without the splash screen warning.

You can usually get a clue as to who owns the system by the SSID. If
it's your local police department or government, I would tread
carefully.

There are also various services that provide VPN terminations. I
blundered across:
http://www.hotspotvpn.com
which has a Flash movie of how to setup their VPN client or XP at:
http://www.hotspotvpn.com/inwinxp.asp?mm=3
which shows roughly how it's setup. Once connected to the VPN server,
all the internet traffic goes through the default route at the
terminating VPN server, instead of throught the default route of the
hot spot or corporate access point.

--
Jeff Liebermann jeffl@xxxxxxxxxxxxxxxxxxxxxx
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558
.



Relevant Pages

  • Re: ISA2004 kills VPN outbound
    ... I have the same problem connecting to several different VPN servers. ... > it use a hardware router or a windows-based computer to be its VPN Server? ... > connection will fail in some cases when a hardware firewall resides in the ... > |> FW client and configure the client as a SecureNAT client. ...
    (microsoft.public.windows.server.sbs)
  • Internet_2: Active Sync Timeout during GPRS Exchange Sync (VPN issue?)
    ... establish the VPN connection and wait at least 45 sec (to allow the VPN ... Active Sync application on the mobile client. ... VPN server to authenticate & authorize. ...
    (microsoft.public.pocketpc.activesync)
  • Internet_2: Active Sync Timeout during GPRS Exchange Sync (VPN issue?)
    ... establish the VPN connection and wait at least 45 sec (to allow the VPN ... Active Sync application on the mobile client. ... VPN server to authenticate & authorize. ...
    (microsoft.public.pocketpc.phone_edition)
  • Internet_2: Active Sync Timeout during GPRS Exchange Sync (VPN issue?)
    ... establish the VPN connection and wait at least 45 sec (to allow the VPN ... Active Sync application on the mobile client. ... VPN server to authenticate & authorize. ...
    (microsoft.public.pocketpc.wireless)
  • RE: PPTP VPN connection problems
    ... Since you want to contact your local MS support for help, ... Additional, you can establish the VPN connection from internal client, that ... | A ping to the server would result in "Request timed out". ...
    (microsoft.public.windows.server.sbs)