Page 96 / 216 Scroll up to view Page 91 - 95
Administrator’s Handbook
96
Factory Reset Switch
Lose your Access Code? This section shows how to reset the Motorola® Gateway so that you can access the
configuration screens once again.
NOTE:
Keep in mind that all of your settings will need to be reconfigured.
If you don't have an Access Code, the only way to access the Motorola® Gateway is the following:
1.
Referring to the diagram below, find the round Reset Switch opening.
2.
Carefully insert the point of a pen or an unwound paperclip into the opening.
If you press the factory reset button for
less than ten (10) seconds
, the device will be rebooted.
The indicator lights on the device will respond immediately and start blinking red within one (1) second of the
reset button being pressed.
This will occur independent of the fact that the button is still being pressed or has been released. The indicator
lights will flash for a minimum of five seconds, even if the reset button is released prior to five seconds after it
has been depressed. If the reset button is held for more than 5 seconds, then it will continue to flash until
released or until 10 seconds (see below).
If you press the factory reset button for a
longer period of time
, the device will be reset to the factory default
shipped settings.
If the button is held for ten seconds, the Power indicator continues to flash, for an additional 5 seconds and
then the indicator lights will return to their normal operating mode, independent of whether or not the reset but-
ton is still depressed.
Factory Reset Switch:
Push to clear all settings
Page 97 / 216
97
Log Event Messages
Administration Related Log Messages
1. administrative access
attempted:
This log-message is generated whenever the user attempts to access
the router's management interface.
2. administrative access
authenticated and allowed:
This log-message is generated whenever the user attempts to access
the router's management interface and is successfully authenticated
and allowed access to the management interface.
3. administrative access
allowed:
If for some reason, a customer does not want password protection for
the management interface, this log-message is generated whenever
any user attempts to access the router's management interface and is
allowed access to the management interface.
4. administrative access
denied - invalid user name:
This log-message is generated whenever the user tries to access the
router's management interface and authentication fails due to incor-
rect user-name.
5. administrative access
denied - invalid password:
This log-message is generated whenever the user tries to access the
router's management interface and authentication fails due to incor-
rect password.
6. administrative access
denied - telnet access not
allowed:
This log-message is generated whenever the user tries to access the
router's Telnet management interface from a Public interface and is
not permitted since Remote Management is disabled.
7. administrative access
denied - web access not
allowed:
This log-message is generated whenever the user tries to access the
router's HTTP management interface from a Public interface and is
not permitted since Remote Management is disabled.
System Log Messages
1. Received NTP Date and
Time:
This log-message is generated whenever NTP receives Date and
time from the server.
2. EN: IP up:
This log-message is generated whenever Ethernet WAN comes up.
3. WAN: Ethernet WAN1 acti-
vated at 100000 Kbps:
This log-message is generated when the Ethernet WAN Link is up.
4. Device Restarted:
This log-message is generated when the router has been restarted.
Page 98 / 216
Administrator’s Handbook
98
DSL Log Messages (most common):
1. WAN: Data link
activated at <Rate> Kbps (rx/
tx)
This log message is generated when the DSL link comes up.
2.WAN: Data link deactivated
This log message is generated when the DSL link goes down.
3. RFC1483 up
This log message is generated when RFC1483 link comes up.
4. RFC1483-<WAN-instance>:
IP down
This log message is generated when RFC1483 link goes down.
5. PPP: Channel <ID> up Dia-
lout Profile name: <Profile
Name>
This log message is generated when a PPP channel comes up.
6. PPP-<WAN Instance> down:
<Reason>
This log message is generated when a PPP channel goes down. The
reason for the channel going down is displayed as well.
Access-related Log Messages
1. permitted:
This log-message is generated whenever a packet is allowed to
traverse router-interfaces or allowed to access the router itself.
2. attempt:
This log-message is generated whenever a packet attempts to
traverse router-interfaces or attempts to access the router itself.
3. dropped - violation of secu-
rity policy:
This log-message is generated whenever a packet, traversing the
router or destined to the router itself, is dropped by the firewall
because it violates the expected conditions.
4. dropped - invalid checksum:
This log-message is generated whenever a packet, traversing the
router or destined to the router itself, is dropped because of invalid IP
checksum.
5. dropped - invalid data
length:
This log-message is generated whenever a packet, traversing the
router or destined to the router itself, is dropped because the IP
length is greater than the received packet length or if the length is too
small for an IP packet.
6. dropped - fragmented
packet:
This log-message is generated whenever a packet, traversing the
router, is dropped because it is fragmented, stateful inspection is
turned ON on the packet's transmit or receive interface, and deny-
fragment option is enabled.
7. dropped - cannot fragment:
This log-message is generated whenever a packet traversing the
router is dropped because the packet cannot be sent without frag-
mentation, but the do not fragment bit is set.
8. dropped - no route found:
This log-message is generated whenever a packet, traversing the
router or destined to the router itself, is dropped because no route is
found to forward the packet.
9. dropped - invalid IP version:
This log-message is generated whenever a packet, traversing the
router or destined to the router itself, is dropped because the IP ver-
sion is not 4.
10. dropped - possible land
attack:
This log-message is generated whenever a packet, traversing the
router or destined to the router itself, is dropped because the packet
is TCP/UDP packet and source IP Address and source port equals
the destination IP Address and destination port.
Page 99 / 216
99
11. TCP SYN flood detected:
This log-message is generated whenever a SYN packet destined to
the router's management interface is dropped because the number of
SYN-sent and SYN-receives exceeds one half the number of allow-
able connections in the router.
12. Telnet receive DoS attack -
packets dropped:
This log-message is generated whenever TCP packets destined to
the router's telnet management interface are dropped due to over-
whelming receive data.
13. dropped - reassembly time-
out:
This log-message is generated whenever packets, traversing the
router or destined to the router itself, are dropped because of reas-
sembly timeout.
14. dropped - illegal size:
This log-message is generated whenever packets, traversing the
router or destined to the router itself, are dropped during reassembly
because of illegal packet size in a fragment.
Firewall Log Messages Detail (AT&T requirement #841)
Reason Enumeration ( C )
Log Text
Representation
Why the packet was
logged
NM_LOGDROP_CAT_DIR
DIRECTION
Direction (generic)
NM_LOGDROP_CAT_DIR_UP
DIRECTION-UP
Upstream direction
NM_LOGDROP_CAT_DIR_DOWN
DIRECTION-DOWN
Downstream direction
NM_LOGDROP_CAT_ETH
ETH
Ethernet Header (generic)
NM_LOGDROP_CAT_ETH_SRC_ADDR
ETH-SRC
Ethernet Source MAC Address
NM_LOGDROP_CAT_ETH_DST_ADDR
ETH-DST
Ethernet Destination MAC
Address
NM_LOGDROP_CAT_ETH_PROT
ETH-PROTOCOL
Ethernet Protocol
NM_LOGDROP_CAT_ETH_VLAN
ETH-VLAN
Ethernet VLAN ID (where appli-
cable)
NM_LOGDROP_CAT_IP
IP
IP Header (generic)
NM_LOGDROP_CAT_IP_SRC
IP-SRC
IP Source Address
NM_LOGDROP_CAT_IP_DST
IP-DST
IP Destination Address
NM_LOGDROP_CAT_IP_PROT
IP-PROTOCOL
IP Protocol
NM_LOGDROP_CAT_IP_SPOOF
IP-SPOOF
IP Address is spoofed (could not
have been sent by a device legit-
imately with the address in the
source address field)
NM_LOGDROP_CAT_IP_ILL
IP-ILLEGAL
IP Address is illegal (either src or
dest)
NM_LOGDROP_CAT_TCP
TCP
TCP Header (generic)
NM_LOGDROP_CAT_TCP_SRC_PORT
TCP-SRC-PORT
TCP Source Port
NM_LOGDROP_CAT_TCP_DST_PORT
TCP-DST-PORT
TCP Destination Port
NM_LOGDROP_CAT_TCP_FLAGS
TCP-FLAGS
TCP Flags field
NM_LOGDROP_CAT_UDP
UDP
UDP Header (generic)
NM_LOGDROP_CAT_UDP_SRC_PORT
UDP-SRC-PORT
UDP Source Port
NM_LOGDROP_CAT_UDP_DST_PORT
UDP-DST-PORT
UDP Destination Port
Access-related Log Messages
Page 100 / 216
Administrator’s Handbook
100
NM_LOGDROP_CAT_ICMP
ICMP
ICMP Packet (generic)
NM_LOGDROP_CAT_ICMP_TYPE
ICMP-TYPE
ICMP Type Field
NM_LOGDROP_CAT_ICMP_CODE
ICMP-CODE
ICMP Code Field
NM_LOGDROP_CAT_ICMP6
ICMPv6
ICMPv6 (generic)
NM_LOGDROP_CAT_POLICY
POLICY
Policy (generic). This currently
includes filterset rules, restricted
hosts, IPv6 Profiles.
NM_LOGDROP_CAT_POLICY_INPUT
POLICY-INPUT-GEN-
DISCARD
Packets destined for the CPE
that are generically discarded
(we specify the packets we DO
want; the rest are discarded.)
NM_LOGDROP_CAT_POLICY_WAN_M
GMT
POLICY-WAN-MGMT-
ACCESS
1) Trying to access CPE service
from WAN side using LAN-side
port
2) Trying to access CPE service
from LAN side using WAN-side
IP address
3) Trying to access CPE service
from WAN side using IPv6
NM_LOGDROP_CAT_POLICY_ICMP_E
CHO
POLICY-ICMP-ECHO
ICMP Echo Request discarded
(more specific than
NM_LOGDROP_CAT_ICMP_TY
PE)
NM_LOGDROP_CAT_POLICY_UWC_R
ESTRICT
POLICY-UWC-RESTRICT
Packets dropped because of
“Universal Wi-Fi Configuration”
restrictions (currently unused)
NM_LOGDROP_CAT_POLICY_RESTRI
CTED_HOST
POLICY-RESTRICTED-
HOST
Packets dropped because of
“Restricted Host” feature (either
content or time restrictions) (cur-
rently unused)
NM_LOGDROP_CAT_POLICY_WAN_D
NS_QUERY
POLICY-WAN-SIDE-DNS-
QUERY
DNS query packets received on
a WAN interface
NM_LOGDROP_CAT_POLICY_WAN_D
HCP_TOSRVR
POLICY-WAN-SIDE-
DHCP-TO-SRVR
DHCP DISCOVER/REQUEST
received on a WAN interface
NM_LOGDROP_CAT_POLICY_AH
POLICY-IPV6-AH
IPv6 Packets with AH Header (if
so configured)
NM_LOGDROP_CAT_POLICY_ESP
POLICY-IPV6-ESP
IPv6 Packets with ESP Header
(if so configured)
NM_LOGDROP_CAT_POLICY_DEP_HE
ADER
POLICY-DEPRECATED-
HEADER
IPv6 Packets with deprecated
header (currently this only
includes routing extension
header type 0)
NM_LOGDROP_CAT_POLICY_CAPT_P
ORTAL
POLICY-CAPTIVE-POR-
TAL
[IPv6] Packets dropped because
captive portal is enabled.
NM_LOGDROP_CAT_FLOW
FLOW
Packets rejected as a result of
analysis of multiple related pack-
ets (generic)
Firewall Log Messages Detail (AT&T requirement #841)
Reason Enumeration ( C )
Log Text
Representation
Why the packet was
logged

Rate

4.5 / 5 based on 2 votes.

Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top