> I still haven't resolved the problems on this machine. I had to have I'm sure that you're frustrated at this point not knowing how to resolve this issue and having to do it remotely at that :(
If everything else is working at this point and you have pf enabled as you should, then it's a matter of remote administration using ssh. It has already been suggest to setup a serial cable as an out-of-band alternative way to get to your box. I am assuming that the admins at the co-location site would be able to help you out here. Once set up, you'll have an easier time trying to troubleshoot and resolve your remote access issue. > 5-One other interesting thing to note is that /var/log/authlog was > around 21,000 lines when I checked it. The OS install is only about 5 > days old. I moved ssh to a non-standard port to try to help reduce the > random break-in attempts. I have found the following ssh_blocker to be very helpful in my fight against taps on port 22. http://blackshell.usebox.net/pub/shell/ > I would really like to use OpenBSD on this machine. If I can't figure > it out in the next day or two, I will have to switch to another > operating system. I highly doubt that it is an operating system issue. However, since you're running a snapshot, I can't be 100% sure. What I do know is that I've never had any stability issues with OpenSSH or OpenBSD for that matter in all the years that I've been using it. That comment probably doesn't help you much at this point but we've not much to go by. A dmesg would be helpful but you're best bet is either to get to this box or get to the console via a serial cable from another box. Mark T. Uemura OpenBSD Support Japan Inc. www.openbsd-support.com
