On Thursday 03 July 2003 12:19 am, bino-psn wrote:
[...]
I really doubt it as this is that last thing anyone would put on a
firewall/
Well .. I need to do some IP Accounting.
Need to store ipchain -L -V result to remote MySqld for further
administration.
And Lynn ... I see LEAF can be
On Wed, 2 Jul 2003, Jim Hubbard wrote:
OK, I'm baffled by this. I have Roadrunner cable, which went
down for about a day. When it came back up, I noticed my
LEAF-Bering (v1.0-stable) firewall was getting hit a lot on udp
port 1191 and it just hasn't stopped. I've also got some other
hits
Raymond Page [EMAIL PROTECTED] writes:
ability to dns lookups from my Bering box. It can ping nameservers, however
the lookup seems to have died. Any ideas why?
The first bet is always that the generated logs are not taken by the
responsible processes. If that occurs, dnscache will stop
Hello allo,
I have this erreur when I type htb.init
/sbin/htb.init : 638:syntax erreur bad substitution.
tc.lrp and qos-htb.lrp already installed in my Bering-uClibc 1.2
Good days
_
Envie de discuter en live avec vos amis ?
I have a successfully working bering1.2 installation.
I download the latest shorewall package v1.45 from TomEastep at
www.shorewall.net
I followed the upgrade procedure --see below
...
after the upgrade, the firewall performs correctly but the
shorewall.log is now broken. Can anyone determine
On Thu, 2003-07-03 at 15:53, lbilyeu wrote:
I have a successfully working bering1.2 installation.
I download the latest shorewall package v1.45 from TomEastep at
www.shorewall.net
I followed the upgrade procedure --see below
...
after the upgrade, the firewall performs correctly but the
after the upgrade, the firewall performs correctly but the
shorewall.log is now broken.
What does that mean exactly?
Shorewall functions as it did before the upgrade...
allows traffic that is allowed by the rulesets to get through
and denies those that should be denied.
shorewall status
---
a) Are you using syslogd or ulogd for logging?
which syslogd
returns /sbin/syslogd
which ulogd
returns /usr/sbin/ulogd
###forgive me master, my meager skills are unable to determine.
###I am using whatever the
On Thu, 3 Jul 2003 20:19:55 -0400, lbilyeu [EMAIL PROTECTED] wrote:
b) what does shorewall status | grep LOG show you?
shorewall status | grep LOG messages.txt
###the output of messages.txt is a follows
0 0 LOGall -- * * 0.0.0.0/0
0.0.0.0/0 LOG
Your Shorewall configuration is using syslogd -- The Bering 1.2
Shorewall
package has been modified to use ulog. Looks like the upgrade
instructions
that you followed are incomplete with respect to Bering 1.2.
I'm not surprised the instructions are incomplete.
I cobbled the HOWTO together from
Bonjour Jacques!
Désolé pour le réponse tardive, j'ai profité des journées de vacances qui me
restent pour procéder à des rénovations majeures...
Jacques Nilo wrote:
Nick:
The Homepna module (il.o) for Bering 1.2 is available in my testing directory
I believe I still have 1.1, do you believe it
Richard Doyle wrote:
On Tue, 2003-07-01 at 05:36, Nicolas Riendeau wrote:
Sorry, I forgot to mention that I'm talking about the ones for the
Broadcom chips (Homepna 2.0?).
Hi!
A quick google would have led you to
http://www.homepna.org/support/faqs.asp#FAQ6, which provides directions
for
On Wednesday 02 July 2003 01:44 pm, Gregory Anthony wrote:
Hi guys,
I'm not sure what caused the problem. I rebooted my server, only to find
that it now gets stuck
at Calibrating delay loop. Using different floppies didn't work. Using
different distros (including a
clean Bering 1.1 version)
On Thu, 3 Jul 2003, Gregory Anthony wrote:
Hi guys,
I'm not sure what caused the problem. I rebooted my server, only to find
that it now gets stuck
at Calibrating delay loop. Using different floppies didn't work. Using
different distros (including a
clean Bering 1.1 version) didn't
14 matches
Mail list logo
