For the archives:
Found my problem. Te firewall_type option is case sensitive -- and OPEN
is supposed to be lowercase.
Cheerio,
SigmaX
On 7/28/06, SigmaX asdf [EMAIL PROTECTED] wrote:
I'm trying to setup a gateway/firewall on my network in a similar setup to
that shown in the in the
I've setup a firewall box with IPFW and NATD with what the handbook
had to offer on the subject, and now would like to get traffic
forwarded to behind my shmancy new firewall.
Google is purely confusing me on this one. From what I understand I
need to do one or more of the following:
setup a
Spoke too soon; figured it out not a minute later. It seems to work
if I remove the divert rule for my server (10.0.0.2) from ipfw, and
leave the natd parameter.
SigmaX
On 8/20/06, SigmaX asdf [EMAIL PROTECTED] wrote:
I've setup a firewall box with IPFW and NATD with what the handbook
had to
SigmaX asdf wrote:
For the archives:
Found my problem. Te firewall_type option is case sensitive -- and OPEN
is supposed to be lowercase.
I would find that very surprising, given that as far as I can see,
everywhere that the firewall_type variable is parsed it's tested against
Tom Hummel wrote:
alright, it was bash :( stupid shell.
Um, sorry, let's not blame the shell for the BCK (between chair and
keyboard) problem. Lots of us use bash as our everyday shell (for privileged
and unprivileged users) without the kinds of problems you described. The
first thing I do when
Igor Robul wrote:
On Sat, Aug 19, 2006 at 04:39:55PM +0200, Miroslav Lachman wrote:
I upgraded to RELENG_6, changed all HW (whole servers and changed
Seagate HHDs to Samsung so every piece of HW is different from time of
my first post), but after one week I got the same error and system
Dear All,
I am the user of FreeBSD 6.1. Recently, i buy a new server for my company
which is a Intel Core 2 Duo E6300 (1.86GHz) with Intel D946GZIS mainboard,
2GB Consair DDR2 Ram, 3Ware 9500S-4LP, and 4X Seagate 250GB SATA II
Harddrive. But when i install the on-board LAN card driver by
On Sunday 20 August 2006 13:00, [EMAIL PROTECTED] wrote:
Do you mean different type of cables, or just another piece? I can't
change cables by myself, servers are dedicated from provider, but as I
can saw, they picked whole new machine from their HW storage and put new
Samsung disk drives in.
On Sun, Aug 20, 2006 at 01:38:55PM +0100, Matt Dawson wrote:
On Sunday 20 August 2006 13:00, [EMAIL PROTECTED] wrote:
Do you mean different type of cables, or just another piece? I can't
change cables by myself, servers are dedicated from provider, but as I
can saw, they picked whole new
I'm not sure if I'm expecting too much, or this is a real bug.
Using FreeBSD 6.1 release, CVSup'd to current. The motherboard is a Supermicro
P4SCT0 with a 3.2Ghz P4 and 2 DDR400 1G sticks of RAM. On the MB is a built-in
RAID controller (Adaptec chip) for the SATA drives. You set it for
On Sun, Aug 20, 2006 at 10:02:05AM -0700, Bill Blue wrote:
I'm not sure if I'm expecting too much, or this is a real bug.
Using FreeBSD 6.1 release, CVSup'd to current. The motherboard is a
Supermicro P4SCT0 with a 3.2Ghz P4 and 2 DDR400 1G sticks of RAM. On
the MB is a built-in RAID
Greg Byshenk wrote:
[...]
I am not sure if it is related, but... I experienced a similar sort of
problem, although the details in my case are quite different.
What was similar was that I would lose two ATA drives from an array,
inexplicably. Reconfiguring the same drives and rebuilding would
On Sun, Aug 20, 2006 at 07:38:28PM +0200, Roland Smith wrote:
On Sun, Aug 20, 2006 at 10:02:05AM -0700, Bill Blue wrote:
I'm not sure if I'm expecting too much, or this is a real bug.
Using FreeBSD 6.1 release, CVSup'd to current. The motherboard is a
Supermicro P4SCT0 with a 3.2Ghz P4
On Sun, Aug 20, 2006 at 07:51:29PM +0200, Miroslav Lachman wrote:
Greg Byshenk wrote:
[...]
This happened four times (with the same errors that have been discussed
here), running 6.1 STABLE as of June 22. Before attempting to RMA the
drives, I tried an updated kernel, 6.1 STABLE as of July
On Sun, Aug 20, 2006 at 07:55:47PM +0200, Greg Byshenk wrote:
On Sun, Aug 20, 2006 at 07:38:28PM +0200, Roland Smith wrote:
On Sun, Aug 20, 2006 at 10:02:05AM -0700, Bill Blue wrote:
I'm not sure if I'm expecting too much, or this is a real bug.
Using FreeBSD 6.1 release, CVSup'd to
On Sun, Aug 20, 2006 at 08:22:48PM +0200, Roland Smith wrote:
On Sun, Aug 20, 2006 at 07:55:47PM +0200, Greg Byshenk wrote:
On Sun, Aug 20, 2006 at 07:38:28PM +0200, Roland Smith wrote:
If FreeBSD supports the device, you should see an ar0 device.
Do you have the ataraid(4) driver
Hello!
On Sat, 19 Aug 2006, Miroslav Lachman wrote:
Aug 19 15:11:20 track ntpd[456]: kernel time sync enabled 2001
Aug 19 15:15:47 track kernel: ad6: FAILURE - device detached
Aug 19 15:15:47 track kernel: subdisk6: detached
Aug 19 15:15:47 track kernel: ad6: detached
I think that's a
Greg Byshenk wrote:
On Sun, Aug 20, 2006 at 07:51:29PM +0200, Miroslav Lachman wrote:
Greg Byshenk wrote:
[...]
This happened four times (with the same errors that have been discussed
here), running 6.1 STABLE as of June 22. Before attempting to RMA the
drives, I tried an updated kernel,
On Sun, 20 Aug 2006 11:22:48 -0700, Roland Smith [EMAIL PROTECTED] wrote:
On Sun, Aug 20, 2006 at 07:55:47PM +0200, Greg Byshenk wrote:
On Sun, Aug 20, 2006 at 07:38:28PM +0200, Roland Smith wrote:
On Sun, Aug 20, 2006 at 10:02:05AM -0700, Bill Blue wrote:
I'm not sure if I'm expecting
Miroslav Lachman wrote:
I upgraded to RELENG_6, changed all HW (whole servers and changed
Seagate HHDs to Samsung so every piece of HW is different from time of
my first post), but after one week I got the same error and system
reboot today:
Aug 19 15:11:20 track ntpd[456]: kernel time sync
Am 20.08.2006 um 21:24 schrieb Bill Blue:
Now, when the ar0s1a-f devices do show up, does the boot device
actually get changed from ad4* to ar0* or do I need to boot single
user while it's talking to ad4* and change the mount points and
reboot? I've never played much with changing boot
On Sun, Aug 20, 2006 at 12:24:36PM -0700, Bill Blue wrote:
On Sun, 20 Aug 2006 11:22:48 -0700, Roland Smith [EMAIL PROTECTED] wrote:
snip
ad6* were the only new devices seen in the OS.
If FreeBSD supports the device, you should see an ar0 device.
Do you have the ataraid(4) driver
Am 20.08.2006 um 18:20 schrieb Greg Byshenk:
On Sun, Aug 20, 2006 at 01:38:55PM +0100, Matt Dawson wrote:
On Sunday 20 August 2006 13:00, [EMAIL PROTECTED]
wrote:
Do you mean different type of cables, or just another piece? I can't
change cables by myself, servers are dedicated from
I am having issues with a VIA RAID system and so I disabled the RAID and just
used a single drive (it was in a mirror) - I did this because the
hardware/firmware sucks, not because of a FreeBSD bug!
However I notice this..
ar0: 305245MB VIA Tech V-RAID RAID1 status: BROKEN
ar0: disk0 DOWN no
On 6/1/06, Jack Vogel [EMAIL PROTECTED] wrote:
I occasionally run into issues that newer PCI device IDs are
not yet supported, these in particular are on a new box
I am working on. Can someone see that these changes
get integrated please :)
Cheers,
Jack
--- dev/ata/ata-chipset.orig.c Fri Jun
On 8/20/06, Nikolas Britton [EMAIL PROTECTED] wrote:
On 6/1/06, Jack Vogel [EMAIL PROTECTED] wrote:
I occasionally run into issues that newer PCI device IDs are
not yet supported, these in particular are on a new box
I am working on. Can someone see that these changes
get integrated please
Johnie Wong wrote:
Dear All,
I am the user of FreeBSD 6.1. Recently, i buy a new server for my
company which is a Intel Core 2 Duo E6300 (1.86GHz) with Intel
D946GZIS mainboard, 2GB Consair DDR2 Ram, 3Ware 9500S-4LP, and 4X
Seagate 250GB SATA II Harddrive. But when i install the on-board
On 8/20/06, Jack Vogel [EMAIL PROTECTED] wrote:
On 8/20/06, Nikolas Britton [EMAIL PROTECTED] wrote:
On 6/1/06, Jack Vogel [EMAIL PROTECTED] wrote:
I occasionally run into issues that newer PCI device IDs are
not yet supported, these in particular are on a new box
I am working on. Can
28 matches
Mail list logo
