[Firehol-support] Bittorrent

[Redeeman]

i think the chains name might become too long, try smaller names..

btw, you can specify ranges instead of all those definitions

On Mon, 2005-11-14 at 17:31 -0800, Daniel L. Miller wrote:
> Two items:
> 
> 1.  First, a request to add the "BitTorrent" service definition to the 
> standard database:
> server_bittorrent_ports="tcp/6881 tcp/6882 tcp/6883 tcp/6884 tcp/6885 
> tcp/6886 tcp/6887 tcp/6888 tcp/6889  udp/6881 udp/6882 udp/6883 udp/6884 
> udp/6885 udp/6886 udp/6887 udp/6888 udp/6889"
> client_bittorrent_ports="default 6881 6882 6883 6884 6885 6886 6887 6888 
> 6889"
> 
> 2.  I'm having a bizarre problem with using this definition.  On an 
> apparent intermittent basis, using this definition in my router clause 
> results in:
> ****
> firehol try
> 
> --------------------------------------------------------------------------------
> ERROR   : # 1.
> WHAT    : A runtime command failed to execute (returned error 1).
> SOURCE  : line 89 of /etc/firehol/firehol.conf
> COMMAND : /sbin/iptables -t filter -A in_xspedius2lan -j 
> in_xspedius2lan_bittorrent_s4
> OUTPUT  :
> 
> iptables: No chain/target/match by that name
> 
> --------------------------------------------------------------------------------
> ERROR   : # 2.
> WHAT    : A runtime command failed to execute (returned error 1).
> SOURCE  : line 89 of /etc/firehol/firehol.conf
> COMMAND : /sbin/iptables -t filter -A out_xspedius2lan -j 
> out_xspedius2lan_bittorrent_s4
> OUTPUT  :
> 
> iptables: No chain/target/match by that name
> 
> Stopped: Couldn't activate new firewall.
> 
> FireHOL: Restoring old firewall: OK
> ****
> 
> No errors are received with my interface/server lines, however.  Then, 
> if I copy the above custom definition, and rename it to say 
> "server_abc_ports/client_abc_ports", then use "router abc accept" - no 
> problem.
> 
> I've re-typed the "router bittorrent accept" line several times, and 
> copied the working "server bittorrent accept" line from my interface 
> clause while changing "server" to "router" - and I still have the 
> problem, so I don't think it's a typo.
>