Sponsored Content
Full Discussion: FireHOL,
Operating Systems Linux FireHOL, Post 302091385 by Corona688 on Monday 2nd of October 2006 01:43:23 PM
Old 10-02-2006
You have given none of the information anyone would need to help you.

I don't know what your distro is, so I cannot tell you how to install it, or how to configure the kernel if necessary, whether you'll need to configure the kernel at all, or how to manage it's init scripts.

I don't know your network layout, how many network cards your server has, which one goes where, and what you want the firewall to do, so I can't give you a configuration, either.

I can't even give you an overview since you demanded exact steps and nothing else. You've already found their page anyway, which has a clearer overview than anything I could write.

The only difference between your question and demanding I set it all up for you is that you're asking me to type it in this forum instead of in your root console. Could you work with me just a little?
 
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)
All times are GMT -4. The time now is 02:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy