Skip to main content

Liberated Networking with Vyatta: Vyatta matures, should Cisco worry?

Absolutely!

Here's more from ZDnet!

Early, pre-release views are ecstatic. You have VPN support, QOS functionality, even traffic-shaping. Download it here.

Like many open source companies Vyatta has both community and subscription versions. VC4, in fact, is short for Vyatta Community. This is not just important to Vyatta, but to the market it seeks to serve.

Even if phone companies subscribe to open source code, they still want to keep their proprietary tweaks. Most won’t go anywhere near a product with out a sales contract. Vyatta lets them do this.

The reality of the carrier market is that today it consists almost entirely of incumbents. Fortunately there remains an immense and growing corporate market, Intranets running telecomm services and Web 2.0 companies offer that market.

This is Vyatta’s sweet spot. Whether it can really build a community is less important than whether it can build a sales channel.

If it can, Cisco will face its first real market threat in a decade.

Decade? I'll say not more than 5 years! More here...

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op