The ATA191 Provisioning Guide (p.149) defines <Allowed_Remote_IP_Address> as:
Description—Specifies a remote IPv4 address that is allowed access to the web-based configuration utility, when Remote Management is enabled
User Interface—Administration > Management > Web Access Management page,
Allowed Remote IPv4 Address field, unlabeled text box
Valid inputs—IPv4 address, Default—0.0.0.0
Example
<Allowed_Remote_IP_Address>209.165.201.129</Allowed_Remote_IP_Address>
First question: That seems plain enough, but what is the address shown below from the example on p.173? Is the final '0' intended to specify an IP4 mask length (e.g. 1.2.3.4/24)?
<Web_Remote_Upgrade>1</Web_Remote_Upgrade>
<Allowed_Remote_IP_Type>1</Allowed_Remote_IP_Type>
<Allowed_Remote_IP_Address>0.0.0.0 0</Allowed_...>
The Provisioning Guide also states that <Web_Remote_Management> enables or disables WAN access to the GUI management utility and <Remote_Web_Utility_Access> specifies the HTTP or HTTPS protocol to be used, which can be one or the other but not either.
However <Web_Utility_Access_HTTP> and <Web_Utility_Access_HTTPS> independently specify whether one or the other, or either, can be used to access the GUI utility from systems on the same LAN port.
Second question: How does all the above apply to devices (including the ATA191 & SPA112) where all traffic is handled over one LAN port?
Just as a comment, I suggest both the terminology and the descriptions of the functional logic used in the Provisioning Guide should be reviewed. The distinction between WAN & LAN access is unclear and inconsistent. Call me a pedant, but I think expressions such as "Web_Remote_Management" "Remote_Web_Utility_Access" "Web_Utility_Access_HTTP" are not precise enough.
