You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "mashengchen (JIRA)" <ji...@apache.org> on 2017/04/11 06:46:41 UTC
[jira] [Created] (TRAFODION-2587) ip showed in dcsMaster monitor is
not correct
mashengchen created TRAFODION-2587:
--------------------------------------
Summary: ip showed in dcsMaster monitor is not correct
Key: TRAFODION-2587
URL: https://issues.apache.org/jira/browse/TRAFODION-2587
Project: Apache Trafodion
Issue Type: Bug
Components: dcs
Reporter: mashengchen
Assignee: mashengchen
if client has two+ ip(use wifi or openvpn), then there may has a random ip send to dcsmaster, and thus, the mapping will not work correct, because dcsmaster use the socket ip
another case is if no mapping ip limit, once connect success, in dcsMaster monitor page there may show error ip
eg:
client have two ip , 192.168.3.14 & 192.168.6.10
mapping ip criteria is 192.168.3.*
in this case client send 192.168.6.10, but the really ip which can connect to dcs side is 192.168.3.14, so the mapping will be error
client have two ip , 192.168.3.14 & 192.168.6.10
mapping ip criteria is no limit
in this case client send 192.168.6.10, but the really ip which can connect to dcs side is 192.168.3.14, then in dcsmaster monitor will show connected side is 192.168.6.10
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)