Hi Valdis, Re 1.. completely understand. The environment is such that we will openly state what does and doesn't work. It is a captive environment and the users don't have a choice who they use. Think large university dorm (about 600) for part of the customer base.
Re 2.. The larger design is already approved and budgeted for... this is a proof-of-concept cheap solution to see if the uptake happens as expensive. I agree with you that we should just build it the right was the first time, but the people paying want to do it this way. And in the end, I am just the designer, if they leave it in place, it is not really my concern, they have my advice. ...Skeeve *Skeeve Stevens - *eintellego Networks Pty Ltd ske...@eintellegonetworks.com ; www.eintellegonetworks.com Phone: 1300 239 038; Cell +61 (0)414 753 383 ; skype://skeeve facebook.com/eintellegonetworks ; <http://twitter.com/networkceoau> linkedin.com/in/skeeve experts360: https://expert360.com/profile/d54a9 twitter.com/theispguy ; blog: www.theispguy.com The Experts Who The Experts Call Juniper - Cisco - Cloud - Consulting - IPv4 Brokering On Mon, Jun 30, 2014 at 11:40 PM, <valdis.kletni...@vt.edu> wrote: > On Mon, 30 Jun 2014 15:59:47 +1000, Skeeve Stevens said: > > > I am after a LSN/CGN/NAT444 solution to put about 1000 Residential > profile > > NBN speeds (fastest 100/40) services behind. > > > This solution is for v4 only, and needs to consider the profile of the > > typical residential users. Any pitfalls would be helpful to know - as in > > what will and and more importantly wont work - or any work-arounds which > > may work. > > Pitfall 1: Make sure you have enough support desk to handle calls from > everybody who's doing something that doesn't play nice with CGN/NAT444. > And remember that unless "screw you, find another provider" is an > acceptable > response to a customer, those calls are going to be major resource sinks to > resolve to the customer's satisfaction... > > Pitfall 2: These sort of short-term solutions often end up still in > use well after their sell-by date. If you're planning to deploy a > new solution in 6 months, maybe throwing resources at a short-term fix > is counterproductive and the resources should go towards making the current > solution hold together and deploying the long-term solution... >
