From owner-freebsd-newbies Thu Jan 25 9:44:26 2001 Delivered-To: freebsd-newbies@freebsd.org Received: from bsd.sixpak.net (adsl-151-204-22-8.adsl.bellatlantic.net [151.204.22.8]) by hub.freebsd.org (Postfix) with ESMTP id D7CDD37B402 for ; Thu, 25 Jan 2001 09:44:04 -0800 (PST) Received: from mike (mike.sixpak.net [192.168.10.2]) by bsd.sixpak.net (8.11.1/8.11.1) with SMTP id f0PHhvI00287 for ; Thu, 25 Jan 2001 12:44:02 -0500 (EST) (envelope-from mike@sixpak.net) Message-ID: <00ea01c086f6$8d611300$020aa8c0@sixpak.net> From: "Mike" To: Subject: Frustrated with FreeBSD Date: Thu, 25 Jan 2001 12:45:00 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00E7_01C086CC.A15F4680" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-newbies@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_00E7_01C086CC.A15F4680 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have spent the last 48 - 72 hours pounding my head against the wall = attempting to get a few things to work correctly. FreeBSD 4.2 running on a pretty basic hardware setup. It seems to be = running just fine. My problems are when I start trying to configure a = few things Sendmail and Qpopper I've managed to get working. This was a pleasant = surprise :) DNS may NOT be working. It's hard to tell from inside my network but = I'm beginning to suspect that it's my secondary name server which is = resolving the domain for the world. Named is starting up and tells me = things like Zone "name" (file) is using SOA minimum and that named is = ready to answer queries. However, the seconday won't load, my secondary DNS still has the old = entries, and in Linux it used to say "Zone MASTER" now it just says = "Zone". The firewall is a nightmare. I followed the default using client and = simple and both of those lock me out and prevent forwarding. I get = "Failed to write packet back (Permission Denied)". Only "open" works. = I also tried the example from the graveconcern site and I get the same = problems. I've followed the examples straight out of the complete = FreeBSD book and STILL my inside network can't get out. Just when I = leave the firewall wide open. Has anyone experienced similiar problems? Anyone have any = recommendations for me to conduct some last bit of research before I = throw in the towel? I'm not stupid, I've managed to get my linux server = running, but I'm having WAY too many problems with no information here. = Some things are just NOT making sense. Mike ------=_NextPart_000_00E7_01C086CC.A15F4680 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

I have spent the last 48 - 72 hours = pounding my=20 head against the wall attempting to get a few things to work=20 correctly.

FreeBSD 4.2 running on a pretty basic = hardware=20 setup. It seems to be running just fine. My problems are = when I=20 start trying to configure a few things

Sendmail and Qpopper I've managed to = get=20 working. This was a pleasant surprise :)

DNS may NOT be working. It's hard = to tell=20 from inside my network but I'm beginning to suspect that it's my = secondary name=20 server which is resolving the domain for the world. Named is = starting up=20 and tells me things like Zone "name" (file) is using SOA minimum and = that named=20 is ready to answer queries.

However, the seconday won't load, my = secondary DNS=20 still has the old entries, and in Linux it used to say "Zone MASTER" now = it just=20 says "Zone".

The firewall is a nightmare. I = followed the=20 default using client and simple and both of those lock me out and = prevent=20 forwarding. I get "Failed to write packet back (Permission = Denied)". =20 Only "open" works. I also tried the example from the graveconcern = site and=20 I get the same problems. I've followed the examples straight out = of the=20 complete FreeBSD book and STILL my inside network can't get out. = Just when=20 I leave the firewall wide open.

Has anyone experienced similiar = problems? =20 Anyone have any recommendations for me to conduct some last bit of = research=20 before I throw in the towel? I'm not stupid, I've managed to get = my linux=20 server running, but I'm having WAY too many problems with no=20 information here. Some things are just NOT making = sense.

Mike

------=_NextPart_000_00E7_01C086CC.A15F4680-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-newbies" in the body of the message