Thanks. That does it.
Here's what I now have.
-A RH-Firewall-1-INPUT -s 128.3.128.0/22 -p udp --dport 5064 -j ACCEPT
-A RH-Firewall-1-INPUT -s 128.3.128.0/22 -p udp --dport 5065 -j ACCEPT
-A RH-Firewall-1-INPUT -s 128.3.128.0/22 -p tcp --dport 5064 -j ACCEPT
-A RH-Firewall-1-INPUT -s 128.3.128.0/22 -p tcp --dport 5065 -j ACCEPT
-A RH-Firewall-1-INPUT --s 128.3.128.0/22 p udp --sport 5064 -j ACCEPT
Maybe this needs to go in either the application developer's guide or the release notes.
On Nov 4, 2010, at 9:19 AM, Darren S. Dale wrote:
>
> I recently had the same problem. I think this was the change that took care of it:
>
> -A INPUT -m udp -p udp --sport 5064 -j ACCEPT
>
> Darren
--
Eric Norum
[email protected]
- Replies:
- Re: Firewall (iptables) issues? Andrew Johnson
- References:
- Firewall (iptables) issues? Eric Norum
- RE: Firewall (iptables) issues? Mark Rivers
- Re: Firewall (iptables) issues? Matthieu Bec
- Re: Firewall (iptables) issues? Eric Norum
- Re: Firewall (iptables) issues? Darren S. Dale
- Navigate by Date:
- Prev:
Re: Firewall (iptables) issues? Darren S. Dale
- Next:
Re: Firewall (iptables) issues? Andrew Johnson
- 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
- Navigate by Thread:
- Prev:
Re: Firewall (iptables) issues? Darren S. Dale
- Next:
Re: Firewall (iptables) issues? Andrew Johnson
- 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
|