On 17/06/11 10:56 PM, David Watkins wrote:
Are my shorewall restarts causing the problem?
I wanted a static ip address but I wasn't able to get one for this user.
Can you use their MAC address?
It is a good suggestion but I thought about this for a while, did some
investigation and realised
On 17/06/11 10:56 PM, David Watkins wrote:
Are my shorewall restarts causing the problem?
I wanted a static ip address but I wasn't able to get one for this user.
Can you use their MAC address?
It is a good suggestion but I thought about this for a while, did some
investigation and
On 18/06/11 1:06 AM, Ian Barton wrote:
On 17/06/11 11:56, David Watkins wrote:
Are my shorewall restarts causing the problem?
I wanted a static ip address but I wasn't able to get one for this user.
Can you use their MAC address?
If you are running dhcp on your server, you can make the dhcp
What can I do about it?
Have you configured a STARTUP_LOG in shorewall.conf? If not, you
should so you can see all of the Shorewall messages being generated at
the time of the hang. I would also recommend upgrading to the latest
version of Shorewall, as yours is almost two years old.
Are my shorewall restarts causing the problem?
I wanted a static ip address but I wasn't able to get one for this user.
Can you use their MAC address?
--
EditLive Enterprise is the world's most technically advanced
On 17/06/11 11:56, David Watkins wrote:
Are my shorewall restarts causing the problem?
I wanted a static ip address but I wasn't able to get one for this user.
Can you use their MAC address?
If you are running dhcp on your server, you can make the dhcp server
assign a static ip address to
On Fri, 2011-06-17 at 22:22 +1200, peter mcgregor wrote:
This may point towards iptables stopping top(and everything else) in
some way.
I do not know why my server is freezing, but I am assuming it is because
iptables has run amok and has locked up the kernel.
Is this a good
