*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I scrounged an old HP Vectra with a 166 MHz Pentium proc and 48 MB of RAM to set up as an OpenBSD firewall. The box has two networking cards in it. I'm not sure of the makes and models of each, but one shows up as dc0 and the other as le1. The install went OK, but at the time I only configured one of the cards, dc0, so I could get the box on my network and get a feel for OpenBSD. However, when I started to configure le1 while working on the firewall (I hadn't started messing with forwarding of PF yet) did not have much luck. The system would recognize the card, and I could assign an IP, but it was as if the Ethernet cable was unplugged (it wasn't ). I could not ping this machine, nor could I ping other machines via this interface. Setting it up to get an IP via DHCP didn't work either; I just got timeout messages.
Anyone seen anything like this before? I'm thinking of just getting a new network card...
Scrap it, pay $10 and go on with life. I've never had much luck using the older network cards. OpenBSD supports the drivers but the low speed card is a blocking point in your network speed especially if youu are using it in your firewall. You could also set the speed selection to auto and will usually pick the right one.
On a side note, I have an OpenBSD firewall with a 200Mhz processor, no fan, 64 MB RAM and an 850MB harddrive. The longest it was up was 193 days and it only shut off because my house lost power.
I've played with it a bit, but it gives me errors when I try to specify a media type. Here is what the hostname.le1 file looks like:
inet 192.168.1.25 255.255.255.0 NONE media 10BaseT
It says something about an improper format. (I don't have this box handy at the moment, otherwise I'd have the exact thing.)
I do indeed have an extra Ethernet card which I planned to put in, but this comp (an HP Vectra XM 5/166) uses some kind of arcane PCI slot, and has two more modern looking ones, one of which has the Ethernet card that works, the other has the vid card. The Ethernet card I'm having the problem with came with the computer and uses one of the strange PCI slots. (I'm sure there's a technical term; don't have the docs with me.) I don't know where to go about getting one of the older cards, so my only option would be to take out the vid card, which I've thought about doing as I don't really need it once I can SSH into it.
Or maybe I'll just go find another older comp looking for a home...
OK, thanks for all of your help. For some strange reason, this box is not working, and probably down for good. It kept giving me parity errors after booting, and now it won't boot at all. I'm going to try to fix it, but I don't think there's much hope. I guess I'll just have to get another firewall box. Maybe I'll check the closet again.