| 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 | 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 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Firewall configuration? |
| From: | Ralph Lange <[email protected]> |
| To: | Chris Jacobsen <[email protected]> |
| Cc: | [email protected] |
| Date: | Thu, 05 Feb 2009 22:46:17 +0100 |
Hm.Seen from the client machine you will need outgoing access to 5064/TCP (data connection), 5064/UDP outgoing and incoming (name resolution), and 5065/UDP incoming (server beacons). Timeouts are usually caused by the name resolution mechanism not working properly. Can you run wireshark to see if the outgoing name requests and/or the incoming answers are blocked?
Good luck! Ralph On 05.02.2009 22:15 Chris Jacobsen wrote:
Hi - I'd like to have a firewall configured on my linux system but when I turn it on then I get a timeout when accessing EPICS variables on a remote system. I thought it would be sufficient to enable TCP and UDP access on ports 5064 and 5065, since I'm running with a "standard" EPICS build on the latest release. Can anyone suggest what else I need to set in a firewall configuration to allow EPICS to work?Thanks, Chris Jacobsen