>From: "Craig Humphrey" <Craig.Humphrey@ChapmanTripp.com>
>BTW IP.Networking doesn't (have to) use VPNs. If you trust Telecom
>, then you don't need to set up a VPN over IP.Networking.

Trust Telecom ?

Their brochure on IP Networking (Private Office Networking) says:
"High-Level encryption ensures your private information stays private"

When I tried to follow this up with Telecom, the sales team were convinced
it was correct.
I got them to follow up with "the techos" - yes it was a "printing error".

So no encryption on IP.Networking

>However, if you don't trust Telecom, or dont want to deal with
>NAT, then a VPN can be your friend.

You are not using IP.Networking, you are using IP.Remote, a Jetstream realm
that connects to the IP.Networking core instead of FastIP or FastIPDirect.
The NAT issue comes from the fact that you are running NAT in your router.

>From a security perspective it is not whether you trust Telecom (noone
should trust a third party), it is how many levels of security should be in
place.

At present, anyone armed with your username and password can plug this into
any Jetstream router and get access to your work LAN.

Question being - will anyone notice ?

If not you need another Layer where things are logged and monitored e.g. a
VPN over IP.Remote to a firewall at your Office.

Cheers

BG.

-- 
This message is part of the NZ ADSL mailing list. 
see http://unixathome.org/adsl/ for archives, FAQ, 
and various documents. 
To unsubscribe: send mail to majordomo@lists.unixathome.org 
with "unsubscribe adsl" in the body of the message