Accessing CUI in restricted Faurecia network
From PlcWiki
(Difference between revisions)
(Created page with '* SSH to kernel while creating a local terminated SOCKS proxy on port 1307: ssh -D 1307 -C plcnewkrnl * Start Chrome with a new profile to avoid interfering with your normal…') |
|||
| (3 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| + | == Accessing the client CUI port directly == | ||
| + | |||
* SSH to kernel while creating a local terminated SOCKS proxy on port 1307: | * SSH to kernel while creating a local terminated SOCKS proxy on port 1307: | ||
| Line 5: | Line 7: | ||
* Start Chrome with a new profile to avoid interfering with your normal Chrome profile and tell it to use the SOCKS proxy: | * Start Chrome with a new profile to avoid interfering with your normal Chrome profile and tell it to use the SOCKS proxy: | ||
| - | google-chrome --proxy-server="socks5://localhost:1307" --user-data-dir=~/chrome-faurecia --no-first-run \ | + | google-chrome --proxy-server="socks5://localhost:1307" --user-data-dir=~/chrome-faurecia-plcnewkrnl --no-first-run \ |
'http://plcnewkrnl:8080/cui?machine=10.139.118.140' | 'http://plcnewkrnl:8080/cui?machine=10.139.118.140' | ||
The forwarded ports on kernel cannot be accessed from localhost (=plcnewkrnl), so CUI has to connect directly to the stations. | The forwarded ports on kernel cannot be accessed from localhost (=plcnewkrnl), so CUI has to connect directly to the stations. | ||
| - | This procedure can be reused for another kernels at the same time, just remember to use a new unique SOCKS port. | + | ---- |
| + | |||
| + | |||
| + | |||
| + | == Using CLEA to access the CUI interface via the redirected ports == | ||
| + | |||
| + | If the redirected ports can be accessed from the SQL server, you can ssh to SQL and then make CLEA use the SOCKS proxy: | ||
| + | |||
| + | ssh -D 1308 -C clever@plcchtsql | ||
| + | |||
| + | google-chrome --proxy-server="socks5://localhost:1308" --user-data-dir=~/chrome-faurecia-plcchtkrnl --no-first-run \ | ||
| + | http://plcchtsql:8080/clea | ||
| + | |||
| + | The browser would then work as if running on the SQL server, i.e. the links from CLEA should work OK. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | |||
| + | |||
| + | This procedure can be reused for another kernels at the same time, just remember to use a new unique SOCKS port / profile folder. | ||
Current revision as of 18:12, 29 July 2021
Accessing the client CUI port directly
- SSH to kernel while creating a local terminated SOCKS proxy on port 1307:
ssh -D 1307 -C plcnewkrnl
- Start Chrome with a new profile to avoid interfering with your normal Chrome profile and tell it to use the SOCKS proxy:
google-chrome --proxy-server="socks5://localhost:1307" --user-data-dir=~/chrome-faurecia-plcnewkrnl --no-first-run \ 'http://plcnewkrnl:8080/cui?machine=10.139.118.140'
The forwarded ports on kernel cannot be accessed from localhost (=plcnewkrnl), so CUI has to connect directly to the stations.
Using CLEA to access the CUI interface via the redirected ports
If the redirected ports can be accessed from the SQL server, you can ssh to SQL and then make CLEA use the SOCKS proxy:
ssh -D 1308 -C clever@plcchtsql
google-chrome --proxy-server="socks5://localhost:1308" --user-data-dir=~/chrome-faurecia-plcchtkrnl --no-first-run \ http://plcchtsql:8080/clea
The browser would then work as if running on the SQL server, i.e. the links from CLEA should work OK.
This procedure can be reused for another kernels at the same time, just remember to use a new unique SOCKS port / profile folder.
