All MIBs › RCV3 › rc3PacketHandlingOptions
rc3PacketHandlingOptions
Module: RCV3
OID (symbolic): RCV3::rc3PacketHandlingOptions
OID (numeric): 1.3.6.1.4.1.1958.1.1.8.2.3
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: This is Bit Masked Object. Zero or more bits can be set or cleared. Bit 0 - Forward non-IP Traffic in Bridge Mode Bit 1 - Forward Local IP Traffic in Bridge Mode Bit 2 - Forward MAC Broadcast in Bridge Mode Bit 3 - Forward IP Broadcast in Router Mode Bit 4 - Send ICMP Re-Direct Messages in Router Mode Bit 5 - Forward Multicast Bit 6 - ARP proxy on the Remote Port Bit 7 - Ignore Don't frag bit. Default is disable. In default mode, if - the Don't frag bit is set, and packets needs to be fragmented - then Ravlin will send ICMP back to the sender and drop the packet. Bit 8 - NAT packets matching bypass selector list.
Bit 9 - SNMP access on Remote port in clear. Default is enabled. If disabled then the ONLY way to access the device from the Remote side is to manage it via a tunnel. Note - 0 Allow SNMP on remote in the clear. - 1 Allow SNMP on remote thru. the tunnel. -- Enable/Disable is reversed for bit 9 to avoid hassles in backward -- compatibility Bit 10 - Enable/Disable PPPoE on Remote Port - Default is disable. Note - 1 Enable - 0 Disable
Bit 11 - Enable/Disable PPPoE connect on Demand - Default is disable. Note - 1 Enable - 0 Disable
Bit 29 - Enable/Disable listening to unsolicited ARP on local port. Default is disable. Note - 1 Enable - 0 Disable
Bit 30 - Enable/Disable cascading packets from one gateway to another. Default is disable. Note - 1 Enable - 0 Disable
The flags specifying behavior for bridge mode are ignored when the device is in router mode, and the flags specifying behavior for router mode are ignored when the device is in bridge mode.
What is rc3PacketHandlingOptions?
A bitmask controlling many independent packet-forwarding behaviors, such as forwarding non-IP or broadcast traffic in bridge mode, sending ICMP redirects in router mode, enabling multicast forwarding, ARP proxying on the remote port, and whether SNMP is reachable on the remote port in the clear versus only through a tunnel. Bridge-mode-specific bits are ignored while the device runs as a router, and vice versa; note bit 9's enable/disable sense is intentionally reversed from the others (0 = allow SNMP in the clear, 1 = require the tunnel) for backward compatibility, per the source DESCRIPTION.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1958.1.1.8.2.3 snmpwalk -v2c -c public <target> RCV3::rc3PacketHandlingOptions
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.1958.1.1.8.2.3.1 snmpget -v2c -c public <target> RCV3::rc3PacketHandlingOptions.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.1958.1.1.8.2.3.1 i <value>
Start monitoring RedCreek Communications VPN/routing gateway (firmware/hardware version and basic IP/interface config) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RCV3::rc3PacketHandlingOptions OID value, configure state conditions and alerts, and monitor any RedCreek Communications VPN/routing gateway (firmware/hardware version and basic IP/interface config) from a single console.
OID Breakdown
Upper-level ancestors (6 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.1958 | redCreek | RCV3 |
| 1.3.6.1.4.1.1958.1 | products | RCV3 |
| 1.3.6.1.4.1.1958.1.1 | rcRavlin | RCV3 |
| 1.3.6.1.4.1.1958.1.1.8 | rcMgmt | RCV3 |
| 1.3.6.1.4.1.1958.1.1.8.2 | rc3Network | RCV3 |
| 1.3.6.1.4.1.1958.1.1.8.2.3 | rc3PacketHandlingOptions | RCV3 |