search for: peterjeremy

I'm interested in crafting firewall rules that throttle connections that have lasted more than a certain amount of time. (Most such connections are P2P traffic, which should be given a lower priority than other connections and may constitute network abuse.) Alas, it doesn't appear that FreeBSD's IPFW can keep tabs on how long a connection has been established. Is there another firewall

I had the same problem so i setup up hosts.allow to only allow access from certain ips i require This has the affect of killing the connection from any other ip befor gettign to any login prompt example below sshd : localhost : allow sshd : 192.168.2. : allow sshd : 82.41.115.213 :allow sshd : 216.123.248.219 : allow <-- public ip i wish to allow of course i have changed it sshd : all :

Greetings, Well, I en devoured to install a copy of 7 as an effort to upgrade one of our servers. After installing a few ports, I began to notice: [: -le: argument expected messages being emitted during the configure/make process. I've already invested a fair amount of time on this upgrade, and /really/ don't want to wipe the disk(s) and start all over. This issue is not new to me - see

Hello everybody, I'm a newbie in this list, so I don't know if it's the appropriate place for my question. Anyway, I'd be happy to find out the solution. Please, has anyone simple answer for: I'm looking for an exact list of files, which: 1. MUST have... 2. HAVE FROM BSD INSTALLATION... 3. DO NOT NEED... 4. NEVER MAY... ...the suid-bit set. Of course, it's no problem to

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-05:21.openssl Security Advisory The FreeBSD Project Topic: Potential SSL 2.0 rollback Category: contrib Module: openssl Announced: 2005-10-11

or "How do I know my copy of FreeBSD is the same as yours?" I have recently been meditating on the issue of validating X.509 root certificates. An obvious extension to that is validating FreeBSD itself. Under "The Cutting Edge", the handbook lists 3 methods of synchronising your personal copy of FreeBSD with the Project's copy: Anonymous CVS, CTM and CVSup. There are

I would also like to help as well. As KMacy knows before i asked a lot of questions for T2 types of servers but unfortunately i have no more access to those kind of hardware as well. I;m willing to participate if a team will be formated.

In http://www.freebsd.org/releases/7.0R/announce.html says Updating Existing Systems > An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes > a major version upgrade, so no matter which method you use to update > an older system you should reinstall any ports you have installed on > the machine. This will avoid binaries becoming linked to inconsistent > sets

Dear FreeBSD users and system administrators, While the FreeBSD Security Team has traditionally been very good at investigating and responding to security issues in FreeBSD, this only solves half of the security problem: Unless users and administrators of FreeBSD systems apply the security patches provided, the advisories issued accomplish little beyond alerting potential attackers to the

[Moved to -stable as this is not relevant to -fs] On 2009-Feb-14 10:30:45 -0200, Sylvio C?sar Teixeira Amorim <scjamorim@bsd.com.br> wrote: >3 Pendrive, 2 are 1, 1G and 8G, I'm using FreeBSD-7.1-stable, the problem is >when you connect to 8G, the fbsd detects the device, da0, etc, but not >create the / dev/da0 takes us about 10min trying to create this device, only >appears

I have an Athlon system which isn't co-operating with the ACPI in -stable (I haven't tried -current yet). I notice that the general recommendation in -current is to provide the output of acpidump but none of the ACPI userland has been MFC'd. I just had a quick try and building the -current userland on -stable and found this is non-trivial because it appears that the APIs are

My wife got the following from a system running (effectively) 4.8-RELEASE (I built/installed world just before the kernel version was updated from 4.8-RC to 4.8-RELEASE). I gather she made a few attempts to get mozilla to start and then the system panic'd. According to the crashdump, p->p_leader is NULL but according to the code, this can never happen. This is a UP Athlon XP-1800 with

I have an on-going problem with DigiBoard Xem boards causing interrupt storms (since 4.x days). The FreeBSD driver polls the board and doesn't have a functional interrupt handler (and Linux behaves in the same way). It seems that under some conditions, the board will assert its interrupt line and, since there's no interrupt handler to clear whatever triggered the interrupt, the IRQ is

This morning, I upgraded my main system to an up-to-date -STABLE including acpi and it now hangs during shutdown after reporting: Waiting (max 60 seconds) for system process `vnlru' to stop...stopped If I set hw.acpi.disable_on_poweroff=0 then the shutdown completes but poweroff fails with (hand copied): ACPI-1287: ***Error: Method execution failed [\_PTS] (Node 0xc21ed450),