High yield Opportunity of the year.
Greetings freebsd-ipfw@freebsd.org, I would like to inform you about a very professional program I participate in since half a year. I made 510% profit by now. This is a Hong Kong traders company, working on stock, derivatives, and Forex markets. Their performance is very consistent, they make up to 3% daily and the company pays its members up to 2.5% each day. HYt fund is really transparent, showing their trading results and offering phone, chat, and email support to its members. I am sure they are the company to work with in 2010. Check them out: http://texugauto.com/93bbjaqm ___ freebsd-ipfw@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw To unsubscribe, send any mail to "freebsd-ipfw-unsubscr...@freebsd.org"
Re: rule 00000.
Hi, > the last thing I want is to lock myself out and have to dispatch a > technician... There's always a risk ;) > Is this problem localized to any particular architecture? (we have > sparc64, amd64 and i386 servers deployed). Is this just the stable > branch that's affected, or was this bug also in the ISO release? (I > deploy via NFS/FTP/bootp from internal servers hosting the ISO images). It was recently introduced, so you're safe with release. To my knowledge, it only affects stable. I'm only using AMD64. Cheers. ___ freebsd-ipfw@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw To unsubscribe, send any mail to "freebsd-ipfw-unsubscr...@freebsd.org"
Re: rule 00000.
Pawel Tyll wrote: Unfortunately FreeBSD 8.0-STABLE #0: Mon Apr 5 08:43:58 CEST 2010 still has problems. ipfw show: (...) 65534 44262253 27617819701 allow ip from any to any 1 5335 405460 allow ip from me to any dst-port 123 00 0 ip from any to any Anything I can do to help? ___ freebsd-ipfw@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw To unsubscribe, send any mail to "freebsd-ipfw-unsubscr...@freebsd.org" Pawel: My skin crawled the moment I read this post. Could you provide a bit more information about this issue? I manage a very large deployment of FreeBSD boxes which are geographically dispersed, and we've started upgrading them to the 8.0 release. My default policy is to deny everything but the services running, so I generally end with a "deny all" statement, and the last thing I want is to lock myself out and have to dispatch a technician... Is this problem localized to any particular architecture? (we have sparc64, amd64 and i386 servers deployed). Is this just the stable branch that's affected, or was this bug also in the ISO release? (I deploy via NFS/FTP/bootp from internal servers hosting the ISO images). Erich M. Jenkins Fuujin Group Limited "You should never, never doubt what no one is sure about." -- Gene Wilder ___ freebsd-ipfw@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw To unsubscribe, send any mail to "freebsd-ipfw-unsubscr...@freebsd.org"
