/etc/net 0.9.6 (Scripts branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News /etc/net 0.9.6 (Scripts branch)
# 1  
Old 04-11-2008
/etc/net 0.9.6 (Scripts branch)

Image/etc/net represents a new approach to Linux network configuration tasks. Inspired by the limitations of traditional network configuration subsystems, /etc/net provides built-in support for configuration profiles, interface name management, removable devices, full iproute2 command set, interface dependencies resolution, QoS, and firewall configuration frameworks. /etc/net provides support for the following interface types: ethernet, WiFi (WEP), IPv4/IPv6 tunnels, PSK IPSec tunnels, VLAN, PLIP, ethernet bonding and bridging, traffic equalizer, Pent@NET, Pent@VALUE, SkyStar-2, TUN/TAP, OpenVPN TUN/TAP, usbnet, and PPP. Due to its modular structure, support for new interface types can be added without overall design changes.License: GNU General Public License (GPL)Changes:
This maintenance release features fixes for DHCPand VLAN processing, for handling of removableinterfaces shutdown, and for OpenVPN and OpenSSHtunnels. More documentation has been included inthe tarball.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Net::SSLeay or Net::FTPSSL

Hello, I ran into an issue in one of my monitoring scripts. If I use the public ip address in my connection string everything works, but if I switch the connection string ip to 127.0.0.1 or the internal ip I get, " Connection refused at... (1 Reply)
Discussion started by: Styles
1 Replies
Login or Register to Ask a Question
NETWORK_NAMESPACES(7)					     Linux Programmer's Manual					     NETWORK_NAMESPACES(7)

NAME
network_namespaces - overview of Linux network namespaces DESCRIPTION
Network namespaces provide isolation of the system resources associated with networking: network devices, IPv4 and IPv6 protocol stacks, IP routing tables, firewall rules, the /proc/net directory (which is a symbolic link to /proc/PID/net), the /sys/class/net directory, various files under /proc/sys/net, port numbers (sockets), and so on. A physical network device can live in exactly one network namespace. When a network namespace is freed (i.e., when the last process in the namespace terminates), its physical network devices are moved back to the initial network namespace (not to the parent of the process). A virtual network (veth(4)) device pair provides a pipe-like abstraction that can be used to create tunnels between network namespaces, and can be used to create a bridge to a physical network device in another namespace. When a namespace is freed, the veth(4) devices that it contains are destroyed. Use of network namespaces requires a kernel that is configured with the CONFIG_NET_NS option. SEE ALSO
nsenter(1), unshare(1), clone(2), veth(4), proc(5), sysfs(5), namespaces(7), user_namespaces(7), brctl(8), ip(8), ip-address(8), ip- link(8), ip-netns(8), iptables(8), ovs-vsctl(8) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2018-02-02 NETWORK_NAMESPACES(7)