Viper SC+™ IP Router for Licensed Spectrum PN 001-5008-000 Rev. C
| Page 53
4)
Viper A hears an RF acknowledgement from Viper B and generates a TCP ACK to send to Host A. Host B
receives the original TCP data packet and generates a TCP ACK to send back over the network.
5)
Viper B receives the TCP ACK, but does not send it over the air—saving bandwidth on the airlink.
Duplicate Packet Removal
Enable or disable the duplicate packet removal algorithm. The default is Disabled (to preserve compatibility with
older versions of the firmware). This algorithm detects duplicate packets that might appear through the system
because of retransmits.
Bridge Forwarding
Selections for Bridge Forwarding are either Everything, or IP and ARP types only. The default setting is IP and ARP
types (Ethernet II types 0x0800, 0x0806) only.
By selecting the Everything setting, the Viper will forward all 802.3 Ethernet II packet types. Use this setting to
transport protocols such as IPX, 802.1Q, etc.
Note:
Bridge Forwarding is not available in Router mode because the Viper will automatically forward all packets
according to its routing table. When selecting Router forwarding mode, all relevant IP settings must be configured.
Tx Packet Pacing
In a Viper network, a polling device may want to send a query to a remote device and wait for an amount of time for a
response. Failure to obtain a response will trigger the polling device to resend a query. If the polling device resends the
query too fast, it may collide (on the RF) with the previous response causing the new query and the old response to be
lost.
In this poll/response scenario, the user may not be able to configure the wait period between the request and the
response in the polling device. The Tx pacing parameter allows the user to configure a waiting period to insert in the
Viper unit after each packet is sent out over the RF interface. This waiting period gives enough time for the response to
come back to the polling device without causing any collisions on the RF interface.
These parameters set the amount of time for the Viper unit to remain idle after sending a packet over the RF interface.
If it is set to 100 ms, it will send a packet, wait 100 ms, send the next packet, wait 100 ms, etc. Normally, the pacing is
set to 0, meaning: don’t wait, send the next packet right away.
TCP
The TCP packet pacing (in milliseconds). Default setting is zero (0).
UDP
The UDP packet pacing (in milliseconds). Default setting is zero (0).
Fragment
Fragment packet pacing (in milliseconds). Default setting is zero (0).
Other
Pacing (in milliseconds) for any other type of packet. Default setting is zero (0).
Save
— Click Save to save any changes you have made to settings in this tab. See Note below.
Cancel
— Click Cancel to cancel any changes you may have made to any of the settings in this tab.
Note:
If you change the Data Retries, or TCP Proxy settings in this tab, as indicated by the yellow alert symbol (
), a
reset of the Viper is required before the setting will take effect.
