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 Reply Children
  • 0 in reply to jadec712
    PlayStation Network

    Utilizing the Automatic Firewall Rule should eliminate the need to whitelist these ports via Network Protection --> Firewall, unless of course you prefer to control that yourself. 

    Anything that these Service Definitions do not cover (e.g. My Internal Network exposes a port that yours do not), simply look at Logging & Reporting --> Network Protection --> Firewall and filter the IP of your PlayStation.

    Network Protection --> NAT --> NAT --> DNAT


    Definitions & Users --> Service Definitions