Black Box LRA005A-R2 - Manual (Page 242)

aASYNC ROUTER AR-P, AR-5, AND SYNC ROUTER REFERENCE MANUALNAME
242
message. This message will almost never be seen because the Router will fall back to V.25 bis only if
limited capabilities of the remote modem force it.
iface V.25bis call timed out
This is a routine notification that a dialup connection (using the V.25 bis protocol) timed out from
inactivity. This message will almost never be seen as the Router will fall back to V.25 bis only if limited
capabilities of the remote modem force it.
modemx timeout was set to 86400 seconds (24 hours), the maximum setting
An attempt was made with the dialup command to set the timeout value higher than permitted. In that
event, the system automatically sets timeout at the maximum allowed setting, and displays the above
message.
Updating modemx (init)
This message is sent after the IPX update command has been issued with the init parameter. This
updates (synchronizes) the local and remote networks. Priority: LOG_DEBUG.
Updating modemx (now)
This message is sent after the IPX update command has been issued with the now parameter. This
updates (synchronizes) the local and remote networks’ IPX service and routing information. Priority:
LOG_DEBUG.
Updating modemx (periodic)
This message is sent after the IPX update command has been issued with the periodic parameter. This
updates (synchronizes) the local and remote networks’ IPX service and routing information. Priority:
LOG_DEBUG.
A.1.3 F ILTER G ROUP
possible security violation : iface received proto addr:port -> addr:port
This message indicates that a packet was received on a different interface from that which we would
have used to send data to the originator (of the packet). This message will be displayed every 5 seconds
or so. One of the following conditions exists:
• your site is being attacked with forged packets pretending to come from inside your network
• your network’s routing plan is misconfigured
If your network includes redundant routing such as dial backup for leased synchronous lines, this
message may merely reflect a temporary routing anomaly. In such network configurations, you may have
to allow the packets to flow through, in order for the RIP protocol to establish the new routing pattern
when the call fallback occurs. Also see the “[ip] filter spoof” command.