SD-WAN for enlightened

2017-04-16 Thread Kasper Adel
Hi,

I'm not sure if the buzzword SD-WAN is used to compensate for another
buzzword that got over-utilized (SDN) or it is a true 'new and improved'
way of doing things that has some innovation into it.

I heard different explanation from different vendors:

1) appliances (+ controller) placed in-line to put traffic in tunnels based
on policy, with some DPI and traffic tagging...(to do performance/policy
based routing) over an expensive link (MPLS) and a cheap one (broadband)
with some 'firewall-like' filtering capabilities.
2) same as above, with a flavor of 'machine learning' to find a pattern for
traffic to optimize utilization.
3) a controller that instantiates and tears down tunnels from 'classic
routers' based on external policies and Network based features to do
performance based routing over an expensive link (MPLS) and a cheap one
(broadband) with encryption.

Is the above a decent high-level summary?

Has anyone tried any of these solutions, any general feedback ?

Cheers,
Kim


John Van Oppen - Wave Broadband

2017-04-16 Thread Rod Beck
If John is on the list, please have him contact me. Thanks.


Regards,


Roderick.

Sales

Cross Lake

SeaX-1 and SeaX-2


Re: Facebook more specific via Level3 ?

2017-04-16 Thread Job Snijders
On Sun, Apr 16, 2017 at 04:20:20PM +0300, Max Tulyev wrote:
> got the same from Kiev, Ukraine:
> 
> dig fbcdn.com
> fbcdn.com.300 IN  A   31.13.74.1
> which is slow and routed through USA
> 
> and
> dig fbcdn.com @8.8.8.8
> fbcdn.com.299 IN  A   31.13.93.3
> which is fast and routed through Germany
> 
> Same is for IPv6.
> 
> Is there any solutions without dirty hacks?

As mentioned in this thread, talk to the Facebook NOC:

On Tue, Mar 21, 2017 at 05:41:23PM +, Doug Porter wrote:
>
> Please reach out to n...@fb.com in the future."
>

Kind regards,

Job


Re: Facebook more specific via Level3 ?

2017-04-16 Thread Max Tulyev
Hi,

got the same from Kiev, Ukraine:

dig fbcdn.com
fbcdn.com.  300 IN  A   31.13.74.1
which is slow and routed through USA

and
dig fbcdn.com @8.8.8.8
fbcdn.com.  299 IN  A   31.13.93.3
which is fast and routed through Germany

Same is for IPv6.

Is there any solutions without dirty hacks?

On 22.03.17 12:02, Radu-Adrian Feurdean wrote:
> Hi, the load-balancing definitely doesn't choose the *nearest* mirror.
> We are in France and unless we do dirty tricks, we *always* get directed
> to US sites (as far as LA), with horrible performance. Everything since
> end of December. As a consequence we let the dirty tricks in place
> (query facebook.com and fbcdn.com on 8.8.8.8 instead of regular
> recursive resolving) and we get directed to Frankfurt or Amsterdam
> (never London or Paris).
>