RVO16 Protocol Binding Unexpected Behavior

Question

Good Afternoon. I have an RV016 device I have been running with a single WAN utilizing the Forwarding service to redirect any external requests appropriately. I now need to direct those requests to multiple systems. I have enabled multi-wan and am now utilizing two WANs with separate static IP addresses. I set up protocol binding for each WAN the same as how I had the Forwarding service configured, they are simply now WAN/Public IP specific, at least that is what I am hoping for. I removed the forwarding requests that existed previously as that section does not allow to specify which WAN port the requests come in on.
When I am attempting to access my system utilizing protocol binding I am getting the RV016 authentication and not being forwarded to the appropriate internal/private system and service port. Am I missing something? Thank you.

Answer 1

I changed to the tr:inputText with no better results. The side effect also is that this does not render correctly in an af:panelLayout control.
<tr:inputText id="agencyId" label="Agency Id:" value="#{AgencyMaintenance.agency.id}" disabled="true"/>
The HTML markup follows: (This is for the af:inputText)
<tr id="agencyId" class="x1e p_AFDisabled">
<td class="xu x4j">
<label for="agencyId::content">Agency Id:</label>
</td>
<td class="xk7" valign="top" nowrap="">
<input id="agencyId::content" class="x1p" type="text" disabled="" name="agencyId"/>
</td>
</tr>
Message was edited by:
Scott Bishopp IBI