I forgot to mention this a long time ago. Thanks to Nicholas Brenkle for
pointing me to the solution of my problem getting OpenBSD 2.5 working as a
firewall/NAT box (NAT = "Network Address Translation" = "IPMasquerading" in
Linux lingo). Once I recompiled the kernel, it worked fine. For some
reason, the 3com driver was only detecting the first 3c509 card when it
started, but then ISAPNP was detecting both cards and reassigning their
resources and giving them new device names. So first it only detected one
card and called it "ep0". Then it detected both cards and called them "ep1"
and "ep2". Once I realized that and edited /etc/hostname.* everything was
fine.
This problem has since been fixed. I later installed OpenBSD 2.6 on the
same machine, and I didn't have to do anything special to get the cards
working. I did have to recompile my kernel to apply security patches, but
the patches applied cleanly and the whole process was quite easy. Overall
I'm impressed with OpenBSD. I really like that ssh is built in. OpenSSH
works great, except that it is incompatible with some older versions of ssh.
My only complaint would be that I find the IPNAT/IPFILTER configuration to
be a little abstruse compared to the Linux IPCHAINS interface, but that
could just be the bias of my relative inexperience. I tried forwarding all
the netbios packets between Yale and my x86 box which sometimes runs Windows
(video games...) Oddly, the Windows box didn't show up on outside browse
lists, and it couldn't browse Yale's LAN, but smbclient on other Unix boxes
had no trouble accessing it through the firewall.
Just thought I'd share my experience in case anyone is interested.
chad
This archive was generated by hypermail 2b29 : Wed Apr 27 2005 - 03:30:03 EDT