I manage two remote WRAP 486 firewalls running Bering 5.0.1.
If I log in with putty, change shorewall rules - do svi shorewall
restart - it says shorewall already running.
I have to save configuration and a reboot to implement shorewall changes.
When it restarts - I get a shorewall-init.log but
Hi Victor,
Based on a quick look at /etc/init.d/shorewall I reckon that the "restart"
block might be broken - seems that it does "start" without "stop".
Most people use the "shorewall" command directly to do a restart.
In other words just:
shorewall restart
not:
svi shorewall restart
(Th
On 10/9/2013 1:48 PM, david M brooke wrote:
> Hi Victor,
>
> Based on a quick look at /etc/init.d/shorewall I reckon that the "restart"
> block might be broken - seems that it does "start" without "stop".
>
> Most people use the "shorewall" command directly to do a restart.
> In other words just:
>
Hello,
Trying out the 5.0.x leaf and kernel hangs at:
[ 1.19xxx] Switiching to clocksource tsc
Any one experiences the issue above?
Cheers,
Kwon
--
October Webinars: Code for Performance
Free Intel webinars can help you a
