{"action":"closed","issue":{"url":"https://api.github.com/repos/aowen87/BAR/issues/769","repository_url":"https://api.github.com/repos/aowen87/BAR","labels_url":"https://api.github.com/repos/aowen87/BAR/issues/769/labels{/name}","comments_url":"https://api.github.com/repos/aowen87/BAR/issues/769/comments","events_url":"https://api.github.com/repos/aowen87/BAR/issues/769/events","html_url":"https://github.com/aowen87/BAR/issues/769","id":390508124,"node_id":"MDU6SXNzdWUzOTA1MDgxMjQ=","number":769,"title":"Client/server from Windows to RZ through VPN doesn't work.","user":{"login":"aowen87","id":11658578,"node_id":"MDQ6VXNlcjExNjU4NTc4","avatar_url":"https://avatars0.githubusercontent.com/u/11658578?v=4","gravatar_id":"","url":"https://api.github.com/users/aowen87","html_url":"https://github.com/aowen87","followers_url":"https://api.github.com/users/aowen87/followers","following_url":"https://api.github.com/users/aowen87/following{/other_user}","gists_url":"https://api.github.com/users/aowen87/gists{/gist_id}","starred_url":"https://api.github.com/users/aowen87/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aowen87/subscriptions","organizations_url":"https://api.github.com/users/aowen87/orgs","repos_url":"https://api.github.com/users/aowen87/repos","events_url":"https://api.github.com/users/aowen87/events{/privacy}","received_events_url":"https://api.github.com/users/aowen87/received_events","type":"User","site_admin":false},"labels":[{"id":1159700189,"node_id":"MDU6TGFiZWwxMTU5NzAwMTg5","url":"https://api.github.com/repos/aowen87/BAR/labels/bug","name":"bug","color":"d73a4a","default":true},{"id":1159700664,"node_id":"MDU6TGFiZWwxMTU5NzAwNjY0","url":"https://api.github.com/repos/aowen87/BAR/labels/likelihood%20medium","name":"likelihood medium","color":"003152","default":false},{"id":1159700523,"node_id":"MDU6TGFiZWwxMTU5NzAwNTIz","url":"https://api.github.com/repos/aowen87/BAR/labels/reviewed","name":"reviewed","color":"008ECC","default":false},{"id":1159700787,"node_id":"MDU6TGFiZWwxMTU5NzAwNzg3","url":"https://api.github.com/repos/aowen87/BAR/labels/severity%20medium","name":"severity medium","color":"0F52BA","default":false},{"id":1159700200,"node_id":"MDU6TGFiZWwxMTU5NzAwMjAw","url":"https://api.github.com/repos/aowen87/BAR/labels/wontfix","name":"wontfix","color":"ffffff","default":true}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":{"url":"https://api.github.com/repos/aowen87/BAR/milestones/31","html_url":"https://github.com/aowen87/BAR/milestone/31","labels_url":"https://api.github.com/repos/aowen87/BAR/milestones/31/labels","id":3894591,"node_id":"MDk6TWlsZXN0b25lMzg5NDU5MQ==","number":31,"title":"2.7.2","description":null,"creator":{"login":"aowen87","id":11658578,"node_id":"MDQ6VXNlcjExNjU4NTc4","avatar_url":"https://avatars0.githubusercontent.com/u/11658578?v=4","gravatar_id":"","url":"https://api.github.com/users/aowen87","html_url":"https://github.com/aowen87","followers_url":"https://api.github.com/users/aowen87/followers","following_url":"https://api.github.com/users/aowen87/following{/other_user}","gists_url":"https://api.github.com/users/aowen87/gists{/gist_id}","starred_url":"https://api.github.com/users/aowen87/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aowen87/subscriptions","organizations_url":"https://api.github.com/users/aowen87/orgs","repos_url":"https://api.github.com/users/aowen87/repos","events_url":"https://api.github.com/users/aowen87/events{/privacy}","received_events_url":"https://api.github.com/users/aowen87/received_events","type":"User","site_admin":false},"open_issues":0,"closed_issues":19,"state":"open","created_at":"2018-12-13T00:15:19Z","updated_at":"2018-12-13T03:58:12Z","due_on":null,"closed_at":null},"comments":0,"created_at":"2018-12-13T03:58:08Z","updated_at":"2018-12-13T03:58:12Z","closed_at":"2018-12-13T03:58:12Z","author_association":"OWNER","body":"Steve Langer reported that an offsite user is unable to get client server working to the RZ through VPN. Here is the text of Steve's e-mail. Eric: This is a followup to the problems Mike Purvis was having in using Visit to visualize HYDRA runs on the RZ from his office in San Diego. Mike is now dragging HYDRA dump sets from rzmerl to cab (using rzslic). Visit works fine in clientserver mode to the CZ, so he is up and running. In the longer term, I would like to find a way for the clientserver mode to work when someone accesses the RZ through an LLNL VPN. LLNL's VPN is currently set up so that all network traffic goes through the VPN. It used to be that only traffic for llnl.gov addresses was routed through the VPN. This change might have had a significant impact on clientserver mode. It has been several years since I worked with Brad on the port usage of the client-server mode. If I remember correctly, you launch the data engine by ssh'ing a command to the machine where the data engine is supposed to run. That command tells the data engine the \"name\" and port on which the visit client is listening for a connection. I don't remember how it gets the \"name\" of the desktop computer. The proper name to use isn't completely obvious because the hostname changes when the VPN is fired up. If visit uses the \"VPN name\", the network traffic will come back through the VPN and the connection should be made OK. If visit uses the original hostname, the traffic should try and go directly to the laptop. The LLNL firewall allows outbound traffic on the visit port, but the laptop no longer responds to its preVPN name and the connection should fail. As near as I can tell from Mike's description, clientserver mode fails for him when the data engine tries to connect back to the client. Have you guys tested client-server mode through the VPN since the VPN was changed to route everything? If not, could you check what name is used when the engine tries to connect back to the server? I think it needs to be something like vpnXXXX.llnl.gov Thanks,Steve\n\n\n\n\n\n-----------------------REDMINE MIGRATION-----------------------\nThis ticket was migrated from Redmine. As such, not all \ninformation was able to be captured in the transition. Below is\na complete record of the original redmine ticket.\n\nTicket number: 1713\nStatus: Rejected\nProject: VisIt\nTracker: Bug\nPriority: Normal\nSubject: Client/server from Windows to RZ through VPN doesn't work.\nAssigned to: Eric Brugger\nCategory: -\nTarget version: 2.7.2\nAuthor: Eric Brugger\nStart: 01/27/2014\nDue date: \n% Done: 0%\nEstimated time: \nCreated: 01/27/2014 04:45 pm\nUpdated: 03/11/2014 07:27 pm\nLikelihood: 3 - Occasional\nSeverity: 3 - Major Irritation\nFound in version: 2.7.0\nImpact: \nExpected Use: \nOS: All\nSupport Group: Any\nDescription:\n Steve Langer reported that an offsite user is unable to get client server working to the RZ through VPN. Here is the text of Steve's e-mail. Eric: This is a followup to the problems Mike Purvis was having in using Visit to visualize HYDRA runs on the RZ from his office in San Diego. Mike is now dragging HYDRA dump sets from rzmerl to cab (using rzslic). Visit works fine in clientserver mode to the CZ, so he is up and running. In the longer term, I would like to find a way for the clientserver mode to work when someone accesses the RZ through an LLNL VPN. LLNL's VPN is currently set up so that all network traffic goes through the VPN. It used to be that only traffic for llnl.gov addresses was routed through the VPN. This change might have had a significant impact on clientserver mode. It has been several years since I worked with Brad on the port usage of the client-server mode. If I remember correctly, you launch the data engine by ssh'ing a command to the machine where the data engine is supposed to run. That command tells the data engine the \"name\" and port on which the visit client is listening for a connection. I don't remember how it gets the \"name\" of the desktop computer. The proper name to use isn't completely obvious because the hostname changes when the VPN is fired up. If visit uses the \"VPN name\", the network traffic will come back through the VPN and the connection should be made OK. If visit uses the original hostname, the traffic should try and go directly to the laptop. The LLNL firewall allows outbound traffic on the visit port, but the laptop no longer responds to its preVPN name and the connection should fail. As near as I can tell from Mike's description, clientserver mode fails for him when the data engine tries to connect back to the client. Have you guys tested client-server mode through the VPN since the VPN was changed to route everything? If not, could you check what name is used when the engine tries to connect back to the server? I think it needs to be something like vpnXXXX.llnl.gov Thanks,Steve\n\nComments:\nI just tried this from my mac at home and vpn connected in. I first tried my trunk, which is 2.8.0b and selected RZ Alastor from Open dialog's host list. That asked me for password and I entered pin+cryptocard. Then, a window popped up regarding the host autenticity and asked for a 'yes/no' response to proceed (as ssh normally does when connecting to a host it hasn't seen before). That worked and then I got a 2.8.0b version doesn't exist error message. Thats because we don't have 2.8.0b installed on RZ.So, I went and tried my 2.7RC and everything there worked fine for me. I was able to plot mesh plot of globe.silo.So, this works for me with default host profiles. However, I also have passwordless ssh working from rzgw and rz machines. Using 2.7RC client-server to RZ, on my Windows 7 machine at home, while VPN'd in , I can access RZ system without issue. I have passwordless ssh set up between rzgw and rz machines. SSH tunnelling is enabled for all the rz host profiles. Since both Mark and Kathleen are able to connect to the RZ through VPN this isn't a bug. I will e-mail Steve Langer and tell him he should try setting up password less ssh between rzgw and the rest of the rz.\n"}}
{"actor":{"display_login":"aowen87"}}