A hands-on look at Vyatta Community Edition 4 networking software

Tags

Special Forums News, Links, Events and Announcements UNIX and Linux RSS News A hands-on look at Vyatta Community Edition 4 networking software

08-13-2008

Registered User

26,240, 27

Join Date: Sep 2000

Last Activity: 1 August 2008, 3:09 PM EDT

Posts: 26,240

Thanks Given: 0

Thanked 27 Times in 26 Posts

A hands-on look at Vyatta Community Edition 4 networking software

08-13-2008 08:00 AM
Vyatta offers hardware and open source software for enterprise-level network infrastructure. Vyatta can turn any 32-bit x86 machine with at least one network interface into a network appliance that handles routing, firewall, and VPN tasks. The company released Vyatta Community Edition 4 in April, with improved scalability and feature enhancements. Large enterprises now have a low-cost alternative to proprietary hardware like the Cisco 7200.

Source...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Infrastructure Monitoring

GroundWork Monitor Community Edition 5.3.0 (GA) (Default branch)

http://c.fsdn.com/fm/screenshots/63584_thumb.jpgGroundWork Monitor Community Edition can give you insight into your computing infrastructure, allowing you to see the current and historical states of all your computers: servers, desktops, and laptops, all of your network devices, all of your...

LEARN ABOUT OPENDARWIN

lo

LO(4)							   BSD Kernel Interfaces Manual 						     LO(4)

NAME

     lo -- software loopback network interface

SYNOPSIS

     pseudo-device
     loop

DESCRIPTION

     The loop interface is a software loopback mechanism which may be used for performance analysis, software testing, and/or local communication.
     As with other network interfaces, the loopback interface must have network addresses assigned for each address family with which it is to be
     used.  These addresses may be set or changed with the SIOCSIFADDR ioctl(2).  The loopback interface should be the last interface configured,
     as protocols may use the order of configuration as an indication of priority.  The loopback should never be configured first unless no hard-
     ware interfaces exist.

DIAGNOSTICS

     lo%d: can't handle af%d.  The interface was handed a message with addresses formatted in an unsuitable address family; the packet was
     dropped.

SEE ALSO

     intro(4), inet(4), ns(4)

HISTORY

     The lo device appeared in 4.2BSD.

BUGS

     Previous versions of the system enabled the loopback interface automatically, using a nonstandard Internet address (127.1).  Use of that
     address is now discouraged; a reserved host address for the local network should be used instead.

4.2 Berkeley Distribution					   June 5, 1993 					 4.2 Berkeley Distribution

UNIX and Linux RSS News