John wrote:

>Hi all
>
>I'm trying to figure out how to lift off the block from m0n0wall.
>The attached logs contains my BitTorrent application listening on port 
>11192, however, all the packets that are coming in from random 
>users/ports are being blocked.
>
>How do i circumvent this?
>
>
>   14:27:53.518183      WAN      69.192.239.126, port 2887      
>218.186.169.202, port 11192      TCP
>    14:27:54.149049     WAN     218.94.80.90, port 59755     
>218.186.169.202, port 11192     TCP
>    14:27:54.261860     WAN     211.94.197.10, port 1513     
>218.186.169.202, port 11192     TCP
>    14:27:54.446629     WAN     64.229.117.80, port 2505     
>218.186.169.202, port 11192     TCP
>    14:27:54.758725     WAN     69.196.44.253, port 3825     
>218.186.169.202, port 11192     TCP
>    14:27:54.929664     WAN     222.132.21.147, port 63958     
>218.186.169.202, port 11192     TCP
>    14:27:55.957052     WAN     210.148.16.161, port 32974     
>218.186.169.202, port 11111     TCP
>    14:27:56.327677     WAN     222.243.9.12, port 20095     
>218.186.169.202, port 11192     TCP
>  
>
All you should need to do is create an a rule to allow traffic from any 
IP:port combination which is directed to your IP on port 11192.

-- 
Usenet is like a herd of performing elephants with diarrhea --
massive, difficult to redirect, awe-inspiring, entertaining, and a
source of mind-boggling amounts of shit when you least expect it.