Fellow Bering-users,
encouraged by an answer from Cédric Schieli, I went
ahead to bye myself two Ralink wireless cards CWP-854.
Unfortunately, they turned out not to react to the
driver rt2500.o present with Bering-uC 3.0, and this
was due to the fact that Ralink has as of late changed
the
Hi!
not wanting to discourage the users in anyway, let me make
things clear.
No Ralink card will work with any of the available drivers
in AP (master) mode.
Work is under way to achieve this, but only for 2.6 kernels.
In fact all wireless cards from Ralink are currently
scheduled for inclusion
In the Shorewall FAQs, there's and interesting writeup regarding using
Portsentry with Shorewall:
(FAQ 4c) How do I use Shorewall with PortSentry?
Here's a writeup
http://www.shorewall.net/pub/shorewall/contrib/PortsentryHOWTO.txt on
a nice integration of Shorewall and PortSentry
The problem is
Hi Cedric,
I'm running 3.0-beta1 and I have some 3c509s on one of my machines so I thought
I'd give this a try.
When I run 3c5x9setup I get an error. Seemingly the same error no matter what
options I provide (apart from --help, which works OK). For example:
firewall# 3c5x9setup --version
Hi Jim,
The at command seems legacy, I don't even have it on my linux server
anymore...
You could start with a simplified script:
#!/bin/sh
# Get the attacker's IP address and probed port from the command
# parameters. DO NOT CHANGE THIS!
BAD_IP=$1
BAD_PORT=$2
# Block the bad guy.
Hi David,
It may be necessary to bring down the interface before use (ifdown ethx)
or maybe even rmmod the NIC module. The error message also seems to
implicate that the NIC is in use.
Upgrading to beta3 shouldn't be needed.
Eric
Hi Cedric,
I'm running 3.0-beta1 and I have some 3c509s on
Hi Jim
Jim Ford wrote:
In the Shorewall FAQs, there's and interesting writeup regarding using
Portsentry with Shorewall:
(FAQ 4c) How do I use Shorewall with PortSentry?
Here's a writeup
http://www.shorewall.net/pub/shorewall/contrib/PortsentryHOWTO.txt on
a nice integration of Shorewall
Hi David,
That may be related to the grsec patch which is applied to the kernel and
may prevent this kind of ops.
I've encountered a similar problem when trying to make isapnptools to work.
If that is the case, I'm not sure we can do something at all.
I will investigate a bit.
Thanks for the
Hello All!
i am able to burn the image file
Bering-uClibc_2.4.2_usb_bering-uclibc-iso.bin.img
onto my usb drive with no problems whatsoever. However
i noticed that the resulting partition on the usb
drive is only around 100mb. Is there a way of
extending it to occupy the usb drive's
