Chris L, can you clarify your point?
Every RFC1918 subnet carries with it a risk of subnet conflict. Some
subnets carry more risk than others. In our case, 192/168/n would
result in higher probability of conflict because most small networks use
that space. I might 'fault' Comcast because they're allocating the
largest netblock to their smallest residential customers. It's not
wrong per-se (AFAIK), but it's certainly poor judgement. Mobile Network
Operators and large enterprises run large 10/8 intranets, thus are known
to utilize the largest IPV4 netblock. Home/small users do not, thus it
is good practice to use the smaller netblock to reduce the risk of
conflict when multi-homing, whether it be via VPN or MNO.
On 12/10/2014 12:36 AM, 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
