Shorewall users - Feb 2003 - Routestopped don''t accept comma separated values

For the /etc/shorewall/routestopped, the documentation states that I can 
specify the host(s) to route when the firewall is stopped as a 
"comma-separated list". I tried a line like this:

  eth1     151.99.150.8,151.99.150.150

but shorewall complains with:

  iptables v1.2.6a: host/network `151.99.150.8,151.99.150.133'' not
found

I tried also a "space separated list", but the inserted rules are
confused and
does not bring the expected result.

Is this a (known) bug? Thanks.

shorewall version 1.3.14
uname -a Linux pigbox 2.4.17 #1 Wed Feb 27 17:59:17 CET 2002 i586 unknown

--
Niccolo Rigacci
http://www.texnet.it/

At 2/17/2003 13:28, Niccolo Rigacci wrote:
>For the /etc/shorewall/routestopped, the documentation states that I can
>specify the host(s) to route when the firewall is stopped as a
>"comma-separated list". I tried a line like this:
>
>   eth1     151.99.150.8,151.99.150.150
>
>but shorewall complains with:
>
>   iptables v1.2.6a: host/network `151.99.150.8,151.99.150.133'' not
found
>
>I tried also a "space separated list", but the inserted rules are
confused
>and
>does not bring the expected result.
>
>Is this a (known) bug? Thanks.
>
>shorewall version 1.3.14
>uname -a Linux pigbox 2.4.17 #1 Wed Feb 27 17:59:17 CET 2002 i586 unknown
For me, works fine (1.3.14). Try to qualify the network:

eth1     151.99.150.8/32,151.99.150.150/32

-Gilson

Niccolo Rigacci wrote:
> For the /etc/shorewall/routestopped, the documentation states that I can 
> specify the host(s) to route when the firewall is stopped as a 
> "comma-separated list". I tried a line like this:
> 
>   eth1     151.99.150.8,151.99.150.150
> 
> but shorewall complains with:
> 
>   iptables v1.2.6a: host/network `151.99.150.8,151.99.150.133'' not
found
> 
> I tried also a "space separated list", but the inserted rules are
confused and
> does not bring the expected result.
> 
> Is this a (known) bug?
If it had been a known bug, it would have been described on the errata 
page (http://www.shorewall.net/errata.htm).

There will be a description of the problem and a link to a corrected 
version of the firewall script on the Errata page shortly.

Thanks,
-Tom
-- 
Tom Eastep    \ Shorewall - iptables made easy
Shoreline,     \ http://www.shorewall.net
Washington USA  \ teastep@shorewall.net

Gilson Soares wrote:
> 
> For me, works fine (1.3.14). Try to qualify the network:
> 
> eth1     151.99.150.8/32,151.99.150.150/32
> 
Better check again since until I released a corrected firewall script 
this evening, there was NO support for a list there...

-Tom
-- 
Tom Eastep    \ Shorewall - iptables made easy
Shoreline,     \ http://www.shorewall.net
Washington USA  \ teastep@shorewall.net