DA-681 Linux
Managing Communications
3-22
SNMPv2-MIB::snmpOutGetRequests.0 = Counter32: 0
SNMPv2-MIB::snmpOutGetNexts.0 = Counter32: 0
SNMPv2-MIB::snmpOutSetRequests.0 = Counter32: 0
SNMPv2-MIB::snmpOutGetResponses.0 = Counter32: 540
SNMPv2-MIB::snmpOutTraps.0 = Counter32: 0
SNMPv2-MIB::snmpEnableAuthenTraps.0 = INTEGER: disabled(2)
SNMPv2-MIB::snmpSilentDrops.0 = Counter32: 0
SNMPv2-MIB::snmpProxyDrops.0 = Counter32: 0
[root@jaredRH90 root]#
***** SNMP QUERY FINISHED *****
ATTENTION
Click on the following links for more information about RFC1317 RS-232 like group and RFC 1213 MIB-II.
•
http://www.tldp.org/HOWTO/NFS-HOWTO/index.html
•
http://nfs.sourceforge.net/nfs-howto/client.html
OpenVPN
OpenVPN provides two types of tunnels for users to implement VPNS:
Routed IP Tunnels
and
Bridged
Ethernet Tunnels
.
An Ethernet bridge is used to connect different Ethernet networks together. The Ethernets are bundled into one
bigger, “logical” Ethernet. Each Ethernet corresponds to one physical interface (or port) that is connected to the
bridge.
On each OpenVPN machine, you should carry out configurations in the
/etc/openvpn
directory, where script
files and key files reside. Once established, all operations will be performed in that directory.
Ethernet Bridging for Private Networks on Different Subnets
1.
Set up four machines, as shown in the following diagram.
Host A represents the machine that belongs to OpenVPN A, and Host B represents the machine that belongs to
OpenVPN B. The two remote subnets are configured for a different range of IP addresses. When this
configuration is moved to a public network, the external interfaces of the OpenVPN machines should be
configured for static IPs, or connected to another device (such as a firewall or DSL box) first.