Hi Folks,
I did some more tests with sshuttle and phoebus. To get this combination working I had to set up the
"org.phoebus.pv.pva/epics_pva_name_servers" preference variable in my settings.ini file and uncomment the "org.phoebus.pv.pva/epics_pva_addr_list".
But if I am in the same network in the lab, I have to enable "org.phoebus.pv.pva/epics_pva_addr_list". Otherwise phoebus will need significant more time
to read the PV's from my IOC.
I still need to configure sshuttle differently. Currently I am limited to about 900kb on an 600MBit uplink from home which comes probably
from the latency control in sshuttle as suggested from report on the internet. Disabling that hopefully will give me higher transfer speeds.
I choose sshuttle to connect phoebus and my IOC because I have multiple IOC's I want to access and I am not allowed to run a gateway on our login node.
Regards,
Jörn
Am Dienstag, 7. April 2026, 04:33:38 Mitteleuropäische Sommerzeit schrieb Michael Davidsaver via Tech-talk:
> On 3/27/26 12:59 AM, Jörn Dreyer via Tech-talk wrote:
> > Hi Folks,
> >
> > I have a problem with remote access to my EPICS pvagw using sshuttle as tunnel into my lab network.
> > If I enable on the gateway the debug output, I see the request I send from home and that it gets processed correctly by the gateway.
> > It ask the IOC for the PV and sends the answer correctly back to my entry host. But on the client side at home I get a timeout.
> > If I uase the ca protocol over sshuttle to another ioc running in the lab network everything works correctly.
> > Does anybody know ho to get that combination running?
>
> I had not heard of "sshuttle" before. At a guess, port numbers are probably being remapped. PVA does not handle this well.
>
> Personally, I can usually make due with forwarding only TCP and making use of EPICS_PVA_NAME_SERVER. For simple situations, I can point the client directly at a single IOC. For more complex situations, I can configure a p4p.gw to listen on TCP port 15064. Forward that port with SSH. Then point my client at "EPICS_PVA_NAME_SERVER=127.0.0.1:15064".
>
>
BEGIN:VCARD
VERSION:3.0
EMAIL;TYPE:j.dreyer at hzdr.de
FN:Jörn Dreyer
N:Dreyer;Jörn;;;
ORG:Helmholtz - Zentrum Dresden- Rossendorf;FWKX
TEL;TYPE=WORK:+0493502603263
TITLE:Dr.
UID:c191707b-eb41-4699-bb8d-a5ef050ab4aa
X-KADDRESSBOOK-MailPreferedFormatting:TEXT
END:VCARD
- Replies:
- Re: PVA via sshuttel tunnel Ralph Lange via Tech-talk
- References:
- PVA via sshuttel tunnel Jörn Dreyer via Tech-talk
- Re: PVA via sshuttel tunnel Michael Davidsaver via Tech-talk
- Navigate by Date:
- Prev:
What are use cases for E-Traveler Wang, Lin via Tech-talk
- Next:
Re: PVA via sshuttel tunnel Ralph Lange via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
<2026>
- Navigate by Thread:
- Prev:
Re: PVA via sshuttel tunnel Michael Davidsaver via Tech-talk
- Next:
Re: PVA via sshuttel tunnel Ralph Lange via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
<2026>
|