The new port whitelisting feature only allows TCP ports, doesn't affect UDP ports

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Find the IP of a public NTP server (from pool.ntp.org) and create a test 
blocklist to include the IP.
2. Test that Peerblock is blocking it.
3. Add NTP port 123 to the new Port Settings tab.
4. NTP traffic is still blocked.
5. Uncheck the test blocklist or shut down Peerblock to see the traffic is 
allowed. 

What is the expected output? What do you see instead?
UDP traffic should be whitelisted by the new feature.

What version of PeerBlock are you using? On what operating system? 32- or
64-bit?
v1.2.0.693 64-bit

Please provide any additional information below.  Make sure to attach
peerblock.log and/or any screenshots that would help explain your problem.

My needs for this commonly is to whitelist NTP and DNS traffic.

Is there a special format for adding UDP packets?  I've added a few NTP server 
hosts from resolving <us.pool.ntp.org> to a new list TestBlock.p2p, but when 
using the new feature to allow port 123, they are still blocked possibly due to 
using UDP.  Removing the hosts from TestBlock.p2p allows them to received the 
UDP packets.

Also, I tried adding GoogleDNS hosts 8.8.8.8 and 8.8.4.4 to TestBlock.p2p, 
thinking I could test similarly with port 53.  But even though they are both in 
the new blocklist, I can successful use NSLookup against 8.8.8.8 at will. 
8.8.4.4 is blocked, however, and since DNS is using UDP, adding port 53 in the 
new functionality likewise does not whitelist the port.

Thank you for the work!

Original issue reported on code.google.com by bmar...@gmail.com on 11 Aug 2015 at 6:57

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

This symptom has been reported by a few in Issue 12. I'm guessing Issue 12 
could be closed soon as (1) older version, and (2) most of that thread is 
regarding implementing the new whitelist feature.  Thanks!

Original comment by bmar...@gmail.com on 16 Aug 2015 at 7:22