Hi Baldur,
* Baldur Norddahl
> On 1 February 2015 at 20:10, Tore Anderson wrote:
>
> > - Tunneling moves the original layer-4 header into another
> > encapsulation layer, so e.g. an ACL attempting to match an IPv6
> > HTTP packet using something like "next-header tcp, dst port 80"
> > wi
"If you choose not to renew, your Meraki systems will cease to provide network
access on February 28, 2015."
I find that interesting as it is my understanding (confirmed by Meraki
documents the last I knew) the Meraki Cloud's functionality is carried
out on the control domain & does not have any
That's it. Step 1, buy the equipment at full price. Step 2, pay for the cloud
management license, yearly. Step 3, no extended warranty option, so pay full
price if equipment from step one fails.
We just dumped our meraki deployment because of it:
>Dear Helpdesk,
>Thank you for being a v
On 1 February 2015 at 20:10, Tore Anderson wrote:
> - Tunneling moves the original layer-4 header into another
> encapsulation layer, so e.g. an ACL attempting to match an IPv6 HTTP
> packet using something like "next-header tcp, dst port 80" will not
> work. With translation, it will.
>
B
* William Herrin
> T-Mobile uses something called 464XLAT. Don't let the "translation"
> part fool you: it's a tunnel. IPv4 in one side, IPv4 out the other.
464XLAT is not a tunnel. Protocol translation is substantially
different from tunneling. With tunneling, the original layer-3 header
is kept
> Worse, IPv6's promises are falling one by one. You saw an example in
> this thread: Eric wants to break up his announcements for traffic
> engineering purposes because, as it turns out, one announcement per
> ISP isn't actually enough, Registry practices aren't the primary
> drivers behind routi
On Fri, Jan 30, 2015 at 3:23 PM, Tore Anderson wrote:
> Kabel Deutschland, T-Mobile USA, and Facebook are examples of companies
> who have already or are in the process of moving their network
> infrastructure to IPv6-only. Without going bust.
Hi Tore,
T-Mobile uses something called 464XLAT. Don
I have tried Meraki for a large deployment, and was significantly underwhelmed.
PF performance was poor compared to Ruckus, meshing was erratic, Radius auth
only worked with one Radius server (a cloud-based service). The final straw
was when we were trying to debug the Radius auth problem with
I try to avoid anything that Cisco has touched.
Also not a fan of their stop paying our recurring fee and the device becomes a
brick policy.
-
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
- Original Message -
From: "Dennis Bohn"
To: "Eric C. Mille
Den 30/01/2015 21.23 skrev "Tore Anderson" :
> Kabel Deutschland, T-Mobile USA, and Facebook are examples of companies
> who have already or are in the process of moving their network
> infrastructure to IPv6-only. Without going bust.
Assuming larger service providers are using MPLS in some form,
We are substantially larger and use Aruba, but I am wondering why no one
has mentioned Meraki (now cisco-meraki). We tried one of their give-away
aps and it seemed fine, with the 'cloud management.' I am not advocating
Meraki, just curious.
best,
Dennis Bohn
Manager of Network and Systems
Adel
11 matches
Mail list logo
