Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 13 replies
  • Subscribers 2 subscribers
  • Views 7062 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Firewall setting not applying for Destiny Ports

jadec712
I setup the Destiny ports to be allowed on the firewall, but the logs are still showing port 3074 getting blocked. Am I missing something on the configuration? I've attached screenshots of what I've configured so far. Below is an excerpt from the log showing the packet getting dropped:

2014:10:09-19:16:48 www ulogd[22886]: id="2001" severity="info" sys="SecureNet" sub="packetfilter" name="Packet dropped" action="drop" fwrule="60002" initf="eth1" outitf="eth0" srcmac="b0:5:94:b:a7:2d" dstmac="0:25:90:c8:b:b5" srcip="192.234.2.62" dstip="209.170.72.124" proto="17" length="31" tos="0x00" prec="0x00" ttl="63" srcport="3074" dstport="3074" 
2014:10:09-19:16:48 www ulogd[22886]: id="2001" severity="info" sys="SecureNet" sub="packetfilter" name="Packet dropped" action="drop" fwrule="60002" initf="eth1" outitf="eth0" srcmac="b0:5:94:b:a7:2d" dstmac="0:25:90:c8:b:b5" srcip="192.234.2.62" dstip="209.170.72.124" proto="17" length="32" tos="0x00" prec="0x00" ttl="63" srcport="3074" dstport="3074" 
2014:10:09-19:16:49 www ulogd[22886]: id="2001" severity="info" sys="SecureNet" sub="packetfilter" name="Packet dropped" action="drop" fwrule="60002" initf="eth1" outitf="eth0" srcmac="b0:5:94:b:a7:2d" dstmac="0:25:90:c8:b:b5" srcip="192.234.2.62" dstip="209.170.72.124" proto="17" length="31" tos="0x00" prec="0x00" ttl="63" srcport="3074" dstport="3074" 
2014:10:09-19:16:49 www ulogd[22886]: id="2001" severity="info" sys="SecureNet" sub="packetfilter" name="Packet dropped" action="drop" fwrule="60002" initf="eth1" outitf="eth0" srcmac="b0:5:94:b:a7:2d" dstmac="0:25:90:c8:b:b5" srcip="192.234.2.62" dstip="209.170.72.124" proto="17" length="32" tos="0x00" prec="0x00" ttl="63" srcport="3074" dstport="3074" 
2014:10:09-19:16:49 www ulogd[22886]: id="2001" severity="info" sys="SecureNet" sub="packetfilter" name="Packet dropped" action="drop" fwrule="60002" initf="eth1" outitf="eth0" srcmac="b0:5:94:b:a7:2d" dstmac="0:25:90:c8:b:b5" srcip="192.234.2.62" dstip="209.170.72.124" proto="17" length="31" tos="0x00" prec="0x00" ttl="63" srcport="3074" dstport="3074" 
2014:10:09-19:16:49 www ulogd[22886]: id="2001" severity="info" sys="SecureNet" sub="packetfilter" name="Packet dropped" action="drop" fwrule="60002" initf="eth1" outitf="eth0" srcmac="b0:5:94:b:a7:2d" dstmac="0:25:90:c8:b:b5" srcip="192.234.2.62" dstip="209.170.72.124" proto="17" length="32" tos="0x00" prec="0x00" ttl="63" srcport="3074" dstport="3074"


This thread was automatically locked due to age.
Parents
  • 0
    Hi Jadec,

    Welcome to the user forums! Your firewall rule allows the ports you defined from your internal network, to your PS3/PS4 host definitions, which appear to also be on your internal network. 

    If you put "Internet" in the destination, rather than the host definitions you have there now, then the rule should work as you're expecting.
Reply
  • 0
    Hi Jadec,

    Welcome to the user forums! Your firewall rule allows the ports you defined from your internal network, to your PS3/PS4 host definitions, which appear to also be on your internal network. 

    If you put "Internet" in the destination, rather than the host definitions you have there now, then the rule should work as you're expecting.
Children
No Data