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…') |
|||
| Line 5: | Line 5: | ||
* 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. | + | This procedure can be reused for another kernels at the same time, just remember to use a new unique SOCKS port / profile folder. |
Revision as of 08:17, 14 July 2021
- 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.
This procedure can be reused for another kernels at the same time, just remember to use a new unique SOCKS port / profile folder.
