Ahh - I have to disagree here. A VPN makes a virtual connection
between two networks. The state of those networks is entirely up to
the people who run the networks. I know of a LOT of cases where
people use VPNs to tunnel puddles of networks over the public
infrastructure to stitch a single AS together, for example.
As far as 1918 vs. globally unique address space, there are many
"public" and "private" networks that use the later. Anyone planning
on using 1918 space for VoIP infrastructure that is going to connect
to external entities is not really thinking things through (or
believe that SBC's will make everything painless). To quote Randy
Bush...
Chris
On Jun 8, 2007, at 23.30 , Matt wrote:
I'm not sure what the problem is. You use public IP, you use IPSEC,
static
route VZ IPs down the tunnel. No problem.
Right there is no problem, now. As everyone else in this thread
has said (for the most part). It works once you understand what
Verizon is trying to do, however prior to that their IPSEC layout
is rather confusing. IE *normally* a VPN connects two PRIVATE
networks togethor... not two PUBLIC networks.
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-biz mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-biz
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-biz mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-biz
