Hi Tom,
I was lurking for a long time here and finally decided to jump into the perl
testing (mostly due to the slow shell compilation).
I upgraded my 3.4.1 to 3.9.4 and run shorewall check on my current settings.
I got a few errors:
Checking /etc/shorewall/blacklist...
ERROR: ipset names in
Tom Eastep wrote:
> You are welcome.
>
> Any additional testing of ipsets that you can do would be very much
> appreciated.
>
> -Tom
Right now I'm using ipsets only for blacklisting purposes. I had to go with
ipsets due to the sheer size of the blacklist.
I have one set for dropping SMTP requ
Tom Eastep wrote:
>
> Revision 6174 should get by that one.
>
> Thanks,
> -Tom
Hi Tom,
It solved all the compilation problems.
Unfortunately the generated firewall doesn't work :(
I'll do some more debugging tomorrow on it.
Thanks,
Andras
Tom Eastep wrote:
> I was able to hack up your configuration and get it to compile. The
> Shorewall-perl compiler now generates rules similar to those generated by
> shorewall-shell.
>
> Revision are 6189/6190.
>
> -Tom
Hi Tom,
It works so far!
Thanks a lot (thinking how to test ipsets in rul
Andras Sarkozy wrote:
> Hi Tom,
>
> It works so far!
>
> Thanks a lot (thinking how to test ipsets in rules :)
>
> Best wishes,
> Andras
>
Hi Tom,
Ipset works in the ACCEPT rule like:
ACCEPT bnet:+mycomputers all - -
ACCEPT:debug anet:+mycomputers all - -
ACCEPT
Tom Eastep wrote:
> 3 days without a post on this list is a record.
>
> Just checking...
>
> -Tom
>
>
Last post was on 7/17/2007 3:54AM
Your current one is 7/19/2007 7:45PM
It is only 2 days and 16 hours approximately :)
Best wishes,
Andras
Hi,
I assume you use rp-pppoe for the connection.
Create another config file in the ppp folder which contains your other identity
and invoke
root# pppoe-start yournewconfig
If you want to play/hardcode the ppp0 to the first and the ppp1 to the second
pppoe connection, then you should append "un
