Chris,
Maybe Karl needs to read RFC 1918. It can be enlightening to find out
he does not 'own' 10.0.0.0/8
Yes, VPN's require unique subnets on both sides of the VPN server, but
that is the price you pay for using a VPN with RFC 1918 addresses.
Lyle Giese
LCR Computer Services, Inc.
On 12/10/14 00:36, Chris L wrote:
On Dec 9, 2014, at 8:53 PM, Karl Fife <karlf...@gmail.com> wrote:
In the wild, I'm seeing a an increasing number of crappy consumer/ISP
routers with subnets that conflict with ours (10../8). Comcast appears
to be a common offender, curiously allocating the largest private subnet
to their smallest customers. Of course this breaks VPN due to address
ambiguity/conflicts.
That’s actually your fault for using 10/8, not Comcast's.
Even if they were to use something like 10.58.223.0/24 they’d still conflict
with your 10/8.
_______________________________________________
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list
_______________________________________________
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list