From owner-freebsd-ipfw@FreeBSD.ORG Mon Jun 29 03:25:26 2009 Return-Path: Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3707E1065688 for ; Mon, 29 Jun 2009 03:25:26 +0000 (UTC) (envelope-from mailinglistmember@mgwigglesworth.net) Received: from mgwigglesworth.net (mail.mgwigglesworth.net [75.146.26.81]) by mx1.freebsd.org (Postfix) with ESMTP id E2D948FC1B for ; Mon, 29 Jun 2009 03:25:25 +0000 (UTC) (envelope-from mailinglistmember@mgwigglesworth.net) To: freebsd-ipfw@freebsd.org Date: Sun, 28 Jun 2009 22:56:58 -0400 Envelope-To: freebsd-ipfw@freebsd.org References: <20090626085530.GA2623@heitec.de> Message-ID: <1246244218.8710.237.camel@localhost> From: "Systems Engineering Group" Received: from [192.168.200.29] (192.168.200.29 [192.168.200.29]) by mgwigglesworth.net; Sun, 28 Jun 2009 22:54:12 -0400 Organization: M. G. Wigglesworth Holdings, LLC Mime-Version: 1.0 X-Mailer: Evolution 2.26.1.1-1mdv2009.1 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Any *Working* Examples of kernel-based (IPFW2-based) NAT onFreeBSD 7.1-STABLE? X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mailinglistmember@mgwigglesworth.net List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 03:25:26 -0000 I don't know why you are attempting to be so "eligant" which is a smart-guy way of saying making something more complex by leaving out certain things that are still relivant, but "messy" as an experienced person would see it) if you are new to the methods. First, you need to make sure that natd is doing its job, by making sure that you have natd turned on, and that it is using the correct interface. Second, when you have verified that the natd configuration is accurate, and usable, the kernel needs to be verified to have the correct options, and that the ipfw rules, setup. You only need divert, and ipfirewall, with ipfirewall_verbose if you want logging. With these kernel options in place, you need to compile and install the kernel correlative to these installed kernel options for the firewalling functionality, with divertion to work. Given these aspects of the system are installed, then you only need to place a natd divert rule into the script for your ipfw-centric firewall. An example would be to start natd with the following included in either commandline options, or config file referenced at commandline call to natd (natd -f /path/to/natd/config) at the commandline, or requisite init script: natd -i $divert_iface -d This should start natd with the -i switch giving indication to natd what device is used to be translated (from/to). After verfication of initialization of the natd daemon via `sockstat | grep natd` you should then test divert rules within your ipfw script, or via dynamic rules that you sent at commandline. The simplest way to test the operation of the divert rules is to do the following. ipfw add 100 pass log tcp from any to any in via $divert_iface #The traffic coming into the external ip addresss will be "diverted" to the internal network ip range. ipfw add 200 divert natd ip from any to any in via $divert_iface ## #Rules 201-499 will be used to filter on the internal addresses after being mangled by the kernel. #They will now look like they are going to #the internal address, not the external ip address, so internal-ip-based #rules will be affective at this time. ## #This rule will divert traffic going from the internal network to the external network ipfw add 500 divert natd ip from any to any out via $divert_iface This is a very brief view of an example that works with freebsd. I would stay away from the complex "elegant" solutions that you referenced in your original post, on or about June 14th, until you verify that your solution is working properly. Check out the handbook, and the information on firewalling on onlamp.org and the freebsd handbook. I am just doing a datadump of my own experience right now, so if you have any further questions, then just post them and we can take a look. The setup is not very difficult, once you have the basics down. I have about thirty rules in my script, but about 20 of them have to do with filtering different stuff, which is merely skipto to a deletion rule with logging. ipfw and natd are not very difficult to use, however, that simplicity is also what makes it such a powerful network appliance solution. I have heard the ipnat + netfilter is supposedly more powerful solution, because ipnat does certain things better than natd, however, that is something for further exploration, and I have not had a need to do so, as of yet. I hope this assists your in your setup endeavor. Respectfully, Martes -- Systems Engineering Group M. G. Wigglesworth Holdings, LLC From owner-freebsd-ipfw@FreeBSD.ORG Mon Jun 29 03:39:40 2009 Return-Path: Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F5F1106566C for ; Mon, 29 Jun 2009 03:39:40 +0000 (UTC) (envelope-from mailinglistmember@mgwigglesworth.net) Received: from mgwigglesworth.net (mail.mgwigglesworth.com [75.146.26.81]) by mx1.freebsd.org (Postfix) with ESMTP id 021A58FC08 for ; Mon, 29 Jun 2009 03:39:39 +0000 (UTC) (envelope-from mailinglistmember@mgwigglesworth.net) To: freebsd-ipfw@freebsd.org Date: Sun, 28 Jun 2009 23:41:25 -0400 Envelope-To: freebsd-ipfw@freebsd.org References: <20090626085530.GA2623@heitec.de> <1246244218.8710.237.camel@localhost> Message-ID: <1246246885.8710.239.camel@localhost> From: "Systems Engineering Group" Received: from [192.168.200.29] (192.168.200.29 [192.168.200.29]) by mgwigglesworth.net; Sun, 28 Jun 2009 23:38:38 -0400 Content-Type: text/plain Organization: M. G. Wigglesworth Holdings, LLC Mime-Version: 1.0 X-Mailer: Evolution 2.26.1.1-1mdv2009.1 Content-Transfer-Encoding: 7bit Subject: Re: Any *Working* Examples of kernel-based (IPFW2-based) NAT onFreeBSD 7.1-STABLE? X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mailinglistmember@mgwigglesworth.net List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 03:39:40 -0000 The natd command should use the -interface switch, or -n however, the best ways to become informed about natd is to simply run a man natd and read the part about "Running natd," because you will get more out of it. man ipfw is also very informative. On Sun, 2009-06-28 at 22:56 -0400, Systems Engineering Group wrote: > I don't know why you are attempting to be so "eligant" which is a > smart-guy way of saying making something more complex by leaving out > certain things that are still relivant, but "messy" as an experienced > person would see it) if you are new to the methods. > > First, you need to make sure that natd is doing its job, by making sure > that you have natd turned on, and that it is using the correct > interface. > > Second, when you have verified that the natd configuration is accurate, > and usable, the kernel needs to be verified to have the correct options, > and that the ipfw rules, setup. > > You only need divert, and ipfirewall, with ipfirewall_verbose if you > want logging. > > With these kernel options in place, you need to compile and install the > kernel correlative to these installed kernel options for the firewalling > functionality, with divertion to work. > > Given these aspects of the system are installed, then you only need to > place a natd divert rule into the script for your ipfw-centric firewall. > > An example would be to start natd with the following included in either > commandline options, or config file referenced at commandline call to > natd (natd -f /path/to/natd/config) > > at the commandline, or requisite init script: natd -i $divert_iface -d > > This should start natd with the -i switch giving indication to natd what > device is used to be translated (from/to). > > After verfication of initialization of the natd daemon via `sockstat | > grep natd` you should then test divert rules within your ipfw script, or > via dynamic rules that you sent at commandline. > > The simplest way to test the operation of the divert rules is to do the > following. > > ipfw add 100 pass log tcp from any to any in via $divert_iface > > #The traffic coming into the external ip addresss will be "diverted" to > the internal network ip range. > ipfw add 200 divert natd ip from any to any in via $divert_iface > > ## > #Rules 201-499 will be used to filter on the internal addresses after > being mangled by the kernel. > #They will now look like they are going to #the internal address, not > the external ip address, so internal-ip-based > #rules will be affective at this time. > ## > > #This rule will divert traffic going from the internal network to the > external network > ipfw add 500 divert natd ip from any to any out via $divert_iface > > This is a very brief view of an example that works with freebsd. > I would stay away from the complex "elegant" solutions that you > referenced in your original post, on or about June 14th, until you > verify that your solution is working properly. > > Check out the handbook, and the information on firewalling on onlamp.org > and the freebsd handbook. > > I am just doing a datadump of my own experience right now, so if you > have any further questions, then just post them and we can take a look. > > The setup is not very difficult, once you have the basics down. > > I have about thirty rules in my script, but about 20 of them have to do > with filtering different stuff, which is merely skipto to a deletion > rule with logging. > > ipfw and natd are not very difficult to use, however, that simplicity is > also what makes it such a powerful network appliance solution. I have > heard the ipnat + netfilter is supposedly more powerful solution, > because ipnat does certain things better than natd, however, that is > something for further exploration, and I have not had a need to do so, > as of yet. > > I hope this assists your in your setup endeavor. > > Respectfully, > > Martes > From owner-freebsd-ipfw@FreeBSD.ORG Mon Jun 29 11:07:01 2009 Return-Path: Delivered-To: freebsd-ipfw@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 666591065674 for ; Mon, 29 Jun 2009 11:07:01 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 52D2F8FC27 for ; Mon, 29 Jun 2009 11:07:01 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n5TB71Iv046377 for ; Mon, 29 Jun 2009 11:07:01 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n5TB70sP046373 for freebsd-ipfw@FreeBSD.org; Mon, 29 Jun 2009 11:07:00 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 29 Jun 2009 11:07:00 GMT Message-Id: <200906291107.n5TB70sP046373@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-ipfw@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-ipfw@FreeBSD.org X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 11:07:01 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/135476 ipfw [ipfw] IPFW table breaks after adding a large number o o bin/134975 ipfw [patch] ipfw(8) can't work with set in rule file. o kern/132553 ipfw [ipfw] ipfw doesn't understand ftp-data port o kern/131817 ipfw [ipfw] blocks layer2 packets that should not be blocke o kern/131601 ipfw [ipfw] [panic] 7-STABLE panic in nat_finalise (tcp=0) o kern/131558 ipfw [ipfw] Inconsistent "via" ipfw behavior o bin/130132 ipfw [patch] ipfw(8): no way to get mask from ipfw pipe sho o kern/129103 ipfw [ipfw] IPFW check state does not work =( o kern/129093 ipfw [ipfw] ipfw nat must not drop packets o kern/129036 ipfw [ipfw] 'ipfw fwd' does not change outgoing interface n o kern/128260 ipfw [ipfw] [patch] ipfw_divert damages IPv6 packets o kern/127230 ipfw [ipfw] [patch] Feature request to add UID and/or GID l o kern/127209 ipfw [ipfw] IPFW table become corrupted after many changes o bin/125370 ipfw [ipfw] [patch] increase a line buffer limit o conf/123119 ipfw [patch] rc script for ipfw does not handle IPv6 o kern/122963 ipfw [ipfw] tcpdump does not show packets redirected by 'ip s kern/121807 ipfw [request] TCP and UDP port_table in ipfw o kern/121382 ipfw [dummynet]: 6.3-RELEASE-p1 page fault in dummynet (cor o kern/121122 ipfw [ipfw] [patch] add support to ToS IP PRECEDENCE fields o kern/118993 ipfw [ipfw] page fault - probably it's a locking problem o kern/117234 ipfw [ipfw] [patch] ipfw send_pkt() and ipfw_tick() don't s o bin/117214 ipfw ipfw(8) fwd with IPv6 treats input as IPv4 o kern/116009 ipfw [ipfw] [patch] Ignore errors when loading ruleset from p kern/115755 ipfw [ipfw] [patch] unify message and add a rule number whe o bin/115172 ipfw [patch] ipfw(8) list show some rules with a wrong form o docs/113803 ipfw [patch] ipfw(8) - don't get bitten by the fwd rule p kern/113388 ipfw [ipfw] [patch] Addition actions with rules within spec o kern/112708 ipfw [ipfw] ipfw is seems to be broken to limit number of c o kern/112561 ipfw [ipfw] ipfw fwd does not work with some TCP packets o kern/107305 ipfw [ipfw] ipfw fwd doesn't seem to work o kern/105330 ipfw [ipfw] [patch] ipfw (dummynet) does not allow to set q o bin/104921 ipfw [patch] ipfw(8) sometimes treats ipv6 input as ipv4 (a o kern/104682 ipfw [ipfw] [patch] Some minor language consistency fixes a o kern/103454 ipfw [ipfw] [patch] [request] add a facility to modify DF b o kern/103328 ipfw [ipfw] [request] sugestions about ipfw table o kern/102471 ipfw [ipfw] [patch] add tos and dscp support o kern/98831 ipfw [ipfw] ipfw has UDP hickups o kern/97951 ipfw [ipfw] [patch] ipfw does not tie interface details to o kern/97504 ipfw [ipfw] IPFW Rules bug o kern/95084 ipfw [ipfw] [regression] [patch] IPFW2 ignores "recv/xmit/v o kern/93300 ipfw [ipfw] ipfw pipe lost packets o kern/91847 ipfw [ipfw] ipfw with vlanX as the device o kern/88659 ipfw [modules] ipfw and ip6fw do not work properly as modul o kern/87032 ipfw [ipfw] [patch] ipfw ioctl interface implementation o kern/86957 ipfw [ipfw] [patch] ipfw mac logging o kern/82724 ipfw [ipfw] [patch] [request] Add setnexthop and defaultrou s kern/80642 ipfw [ipfw] [patch] ipfw small patch - new RULE OPTION o bin/78785 ipfw [patch] ipfw(8) verbosity locks machine if /etc/rc.fir o kern/74104 ipfw [ipfw] ipfw2/1 conflict not detected or reported, manp o kern/73910 ipfw [ipfw] serious bug on forwarding of packets after NAT o kern/72987 ipfw [ipfw] ipfw/dummynet pipe/queue 'queue [BYTES]KBytes ( o kern/71366 ipfw [ipfw] "ipfw fwd" sometimes rewrites destination mac a o kern/69963 ipfw [ipfw] install_state warning about already existing en o kern/60719 ipfw [ipfw] Headerless fragments generate cryptic error mes o kern/55984 ipfw [ipfw] [patch] time based firewalling support for ipfw o kern/51274 ipfw [ipfw] [patch] ipfw2 create dynamic rules with parent o kern/48172 ipfw [ipfw] [patch] ipfw does not log size and flags o kern/46159 ipfw [ipfw] [patch] [request] ipfw dynamic rules lifetime f a kern/26534 ipfw [ipfw] Add an option to ipfw to log gid/uid of who cau 59 problems total. From owner-freebsd-ipfw@FreeBSD.ORG Mon Jun 29 14:08:48 2009 Return-Path: Delivered-To: ipfw@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5418D106567B for ; Mon, 29 Jun 2009 14:08:48 +0000 (UTC) (envelope-from niteshbharti123@gmail.com) Received: from mail-pz0-f197.google.com (mail-pz0-f197.google.com [209.85.222.197]) by mx1.freebsd.org (Postfix) with ESMTP id D6B338FC20 for ; Mon, 29 Jun 2009 14:08:47 +0000 (UTC) (envelope-from niteshbharti123@gmail.com) Received: by pzk35 with SMTP id 35so151229pzk.3 for ; Mon, 29 Jun 2009 07:08:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to:subject :date:mime-version:content-type:x-mailer:x-mimeole:thread-index; bh=d7BVDf0QXgsZzlpwgQd1YQK7g4VBzsdWM4OhSz7kefs=; b=Z9oK9U/P3r+EE8iJq15ZUwNFTcobItafkbK+mNuM+nror/2zXRVAyF9oligm2PFnrq hGb/EGhzBQcrncNMs+XeZiSmv+aAOWl4vnNNuSnVTHu+j6nVYMCROBLY+f00ZKmHlCYz 08UI0i4r/pgxcF+4/aysSDy3SYk2sFgcepy2k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:subject:date:mime-version:content-type:x-mailer :x-mimeole:thread-index; b=dkkEQtsjC9j0EjUTowK3g6sVJN9CQLvBDhV7cbNogW1DNAvM3tQNYha2IHRfwHCHLp ATzgEjLEC+c4jsOOwEDGuLfKX/FRSLAA2lsLDmOxjnQmI7jTlnk8qTWtXw97fm/oNi+Z jsSkREHEHcIT8kvX5OnuTSL0yj0cRkAKf7f5I= Received: by 10.115.18.1 with SMTP id v1mr11197111wai.200.1246277525751; Mon, 29 Jun 2009 05:12:05 -0700 (PDT) Received: from nitesh ([122.160.132.202]) by mx.google.com with ESMTPS id c26sm6887590waa.50.2009.06.29.05.12.00 (version=SSLv3 cipher=RC4-MD5); Mon, 29 Jun 2009 05:12:04 -0700 (PDT) Message-ID: <4a48af94.1a36720a.143f.6ef1@mx.google.com> From: "Nitesh. Bharti" To: Date: Mon, 29 Jun 2009 17:41:39 +0530 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Thread-Index: Acn4sr3qGt0Ig1snTWuxmYPYEBXTjg== Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: AstroWix Solutions X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 14:08:48 -0000 AstroWix is a forward thinking Program and Project Management Solutions Company. With its strong adherence to Project Management norms, AstroWix facilitates organizations to excel in their respective business domains by achieving their desired organizational goals at the right time and at minimum budget. Our services range from helping organizations select the right projects, programs and portfolios to effectively drive business value and achieve sustainable competitive advantage. For the balanced and effective execution of these solutions, we blend a series of services which include Project Management Consulting, Project Management Competency Development, Setup and Support of Project Management Office, Collaboration and SharePoint Deployment and End-to-End Project Management Support. As a registered Education Provider of PMI, AstroWix is a leading provider for Project Management Training in helping professionals with their PMPR Certification India . PMP certification preparation involves rigorous training but our PMP training program ensures every PMP aspirant a comprehensive, quality and up to date training. For PMPR Certification India, AstroWix is a very popular choice for PMP professionals and PMP aspirants, providing training and end-to-end support for professionals to prepare for PMPR Certification examination. To know more about Project Management Training , PMP R Certification India Visit : www.astrowix.com Nitesh Ranjan AstroWix Project Solutions Pvt Ltd From owner-freebsd-ipfw@FreeBSD.ORG Mon Jun 29 14:17:44 2009 Return-Path: Delivered-To: ipfw@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01913106566C for ; Mon, 29 Jun 2009 14:17:44 +0000 (UTC) (envelope-from niteshbharti123@gmail.com) Received: from mail-px0-f191.google.com (mail-px0-f191.google.com [209.85.216.191]) by mx1.freebsd.org (Postfix) with ESMTP id C4D8A8FC19 for ; Mon, 29 Jun 2009 14:17:43 +0000 (UTC) (envelope-from niteshbharti123@gmail.com) Received: by pxi29 with SMTP id 29so3463854pxi.3 for ; Mon, 29 Jun 2009 07:17:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to:subject :date:mime-version:content-type:x-mailer:x-mimeole:thread-index; bh=9+mLjdw8aCLMY/j+wkMiG5QECdivtIezuaXP+tGOoAI=; b=npQRT4odx8pVeQRBMBlHe4nHveZ8zIE/RqdQ7Xvhja9pQJdgARSSIqqzIR2VK7EM8V Of0CFoE71M/ITxWq+OgLTNUItkgcqnfyEDK1f/ThxU3WAF3PFTfUJ4cphZwng0CCy4A4 0/9FSe0Be6HnX+p9WMJ9Cc9BujnMjnCMagMAo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:subject:date:mime-version:content-type:x-mailer :x-mimeole:thread-index; b=uJp6PiJRsnZKja+x6q5qpx+kzP5+0dDlJZHcb2XLhQ4xK+7GekmdeOBn1/S4DO27+H 3BiJHzDwa4oGLtbMN473voCPcz9LaBLhnv7LNqfAj0rgU7x4Iglzw9kxNjBik55Rh2d4 kj2fSdCGk358+ZXOlwOHn+hQIprwaglZBjHmQ= Received: by 10.114.53.3 with SMTP id b3mr11278025waa.112.1246277533260; Mon, 29 Jun 2009 05:12:13 -0700 (PDT) Received: from nitesh ([122.160.132.202]) by mx.google.com with ESMTPS id c26sm6887590waa.50.2009.06.29.05.12.07 (version=SSLv3 cipher=RC4-MD5); Mon, 29 Jun 2009 05:12:12 -0700 (PDT) Message-ID: <4a48af9c.1a36720a.143f.6efc@mx.google.com> From: "Nitesh. Bharti" To: Date: Mon, 29 Jun 2009 17:41:39 +0530 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Thread-Index: Acn4srzRiDFMSDeuQByukGglF/fuNw== Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: AstroWix Solutions X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 14:17:44 -0000 AstroWix is a forward thinking Program and Project Management Solutions Company. With its strong adherence to Project Management norms, AstroWix facilitates organizations to excel in their respective business domains by achieving their desired organizational goals at the right time and at minimum budget. Our services range from helping organizations select the right projects, programs and portfolios to effectively drive business value and achieve sustainable competitive advantage. For the balanced and effective execution of these solutions, we blend a series of services which include Project Management Consulting, Project Management Competency Development, Setup and Support of Project Management Office, Collaboration and SharePoint Deployment and End-to-End Project Management Support. As a registered Education Provider of PMI, AstroWix is a leading provider for Project Management Training in helping professionals with their PMPR Certification India . PMP certification preparation involves rigorous training but our PMP training program ensures every PMP aspirant a comprehensive, quality and up to date training. For PMPR Certification India, AstroWix is a very popular choice for PMP professionals and PMP aspirants, providing training and end-to-end support for professionals to prepare for PMPR Certification examination. To know more about Project Management Training , PMP R Certification India Visit : www.astrowix.com Nitesh Ranjan AstroWix Project Solutions Pvt Ltd From owner-freebsd-ipfw@FreeBSD.ORG Fri Jul 3 20:16:34 2009 Return-Path: Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 58ADC10656B0 for ; Fri, 3 Jul 2009 20:16:34 +0000 (UTC) (envelope-from plaxo@mx.plaxo.com) Received: from mx.plaxo.com (mx.plaxo.com [66.151.128.13]) by mx1.freebsd.org (Postfix) with ESMTP id 3BD7C8FC2E for ; Fri, 3 Jul 2009 20:16:34 +0000 (UTC) (envelope-from plaxo@mx.plaxo.com) Received: from localhost by mx.plaxo.com (StrongMail Enterprise 3.2.2.2(3.00.287)); Fri, 03 Jul 2009 13:16:34 -0700 X-VirtualServer: Pulse, mx.plaxo.com, 10.1.6.55 X-PlaxoMailType: Pulse X-Destination-ID: freebsd-ipfw@freebsd.org X-MailingID: 00000::00000::00000::00000::::1305705 X-SMHeaderMap: mid="X-MailingID" X-SMFBL: ZnJlZWJzZC1pcGZ3QGZyZWVic2Qub3Jn From: "Jean Dupre" To: freebsd-ipfw@freebsd.org Message-Id: <3dba5d00b7617e2086f8fb5e706bfcd1@xpertmailer.com> X-VirtualServerGroup: Pulse Errors-To: plaxo@mx.plaxo.com Date: Fri, 03 Jul 2009 12:42:28 -0700 X-Mailer: XPM4 v.0.3 < www.xpertmailer.com > MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: =?utf-8?q?Jean_Dupre_a_partag=C3=A9_un_message_avec_vous_sur_Pul?= =?utf-8?q?se?= X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ja.dupre@live.fr List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jul 2009 20:16:36 -0000 Jean Dupre a partag=C3=A9 un message avec vous sur Pulse et souhaitait vous le faire savoir. http://www.plaxo.com/public/event/189178955319?src=3Demail&et=3D6&el=3Dfr_o= 1&key=3D70634ecb3f154d61ab941ea5fed30e573283e72f&email=3Dfreebsd-ipfw%40fre= ebsd.org&share_id=3D4662473&share_key=3D1973782934&name=3D&webmailfix=3D1&l= ang=3Dfr Besoin de pr=C3=AAt ? Bonjour, Je suis DUPRE JEAN ALBERT. Ancien th=C3=A9rapeute, financier suisse et Directeur d=E2=80=99=C3=A9tude de projets dans une banque. J'octroie des pr=C3=AAts =C3=A0 toute personne d=C3=A9sireuse selon le= s crit=C3=A8res suivants: Choix du montant : =C3=A0 partir de 15.000 =E2=82=AC Choix de la dur=C3=A9e de remboursement : 8 ans maximum TEG annuel fixe : 2,15%* (*offre soumise =C3=A0 condition) En option : l=E2=80=99assurance e... http://www.plaxo.com/public/event/189178955319?src=3Demail&et=3D6&el=3Dfr_o= 1&key=3D70634ecb3f154d61ab941ea5fed30e573283e72f&email=3Dfreebsd-ipfw%40fre= ebsd.org&share_id=3D4662473&share_key=3D1973782934&name=3D&webmailfix=3D1&l= ang=3Dfr Merci ! L'=C3=A9quipe Plaxo Plus de 20=C2=A0millions de personnes utilisent Plaxo pour rester en contact avec leur entourage dans le cadre priv=C3=A9 comme professionnel.=20 Vous ne voulez plus recevoir d'e-mails de Plaxo=C2=A0? Rendez-vous sur=C2=A0: http://www.plaxo.com/stop?src=3Demail&et=3D6&el=3Dfr_o1&email=3Dfreebsd-ipf= w%40freebsd.org From owner-freebsd-ipfw@FreeBSD.ORG Sat Jul 4 21:40:16 2009 Return-Path: Delivered-To: ipfw@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14833106566C for ; Sat, 4 Jul 2009 21:40:16 +0000 (UTC) (envelope-from update+kju~w1md@facebookmail.com) Received: from mx-out.facebook.com (outcampmail002.snc1.tfbnw.net [69.63.178.187]) by mx1.freebsd.org (Postfix) with ESMTP id E68478FC0C for ; Sat, 4 Jul 2009 21:40:15 +0000 (UTC) (envelope-from update+kju~w1md@facebookmail.com) DKIM-Signature: v=1; a=rsa-sha1; d=facebookmail.com; s=q1-2009b; c=relaxed/relaxed; q=dns/txt; i=@facebookmail.com; t=1246742715; h=From:Subject:Date:To:MIME-Version:Content-Type; bh=Ik42LxD1oAQUmdNrrTSgTScEfCQ=; b=Uj4yBQ4aOKWajyJA+n+KmozlYJLdr9SHC5g7c2/OJyAAjPdeZ7XKYOw6X/ZVa5lC F9LtvJQag/Gn6SArzeILvQ==; Received: from [10.18.255.175] ([10.18.255.175:53991] helo=10.16.151.182) by mta011.snc1.facebook.com (envelope-from ) (ecelerity 2.2.2.37 r(28805/28844)) with ESMTP id 7C/E7-06101-AB8CF4A4; Sat, 04 Jul 2009 14:25:15 -0700 X-Facebook: from zuckmail ([MTAuMTYuMTUxLjE4Mg==]) by 10.16.151.182 with HTTP (ZuckMail); Date: Sat, 4 Jul 2009 14:25:14 -0700 To: Ipfw From: Facebook Message-ID: X-Priority: 3 X-Mailer: ZuckMail [version 1.00] X-Facebook-Camp: reminder_email X-Facebook-Notify: reminder_email; mailid=b9c5e8G41d79197G44b6a8G46 Errors-To: update+kju~w1md@facebookmail.com X-FACEBOOK-PRIORITY: 1 MIME-Version: 1.0 Content-Type: text/plain; charset = "UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Reminder: Michael invited you to join Facebook... X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Facebook List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jul 2009 21:40:16 -0000 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D To sign up for Facebook, follow the link below: http://www.facebook.com/r.php?re=3D99d4e672e080ba96cc0d0e79dab01e38&mid=3D= b9c5e8G41d79197G44b6a8G46 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Hi Ipfw, The following person recently invited you to be their friend on Facebook: Michael Sierchio Other people you may know on Facebook: Lynn Strough (East Bay, CA) Ishara Hudson (Santa Cruz, CA) Ericka Lutz (East Bay, CA) Gina Podesta Danny Santos (Berkeley) Helga Veideman (San Francisco, CA) Facebook is a great place to keep in touch with friends, post photos, = videos and create events. But first you need to join! Sign up today to = create a profile and connect with the people you know. Thanks, The Facebook Team To sign up for Facebook, follow the link below: http://www.facebook.com/r.php?re=3D99d4e672e080ba96cc0d0e79dab01e38&mid=3D= b9c5e8G41d79197G44b6a8G46 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D This message was intended for ipfw@freebsd.org. If you do not wish to = receive this type of email from Facebook in the future, please click on = the link below to unsubscribe. http://www.facebook.com/o.php?c&k=3D86cbe6&u=3D1104646551&mid=3Db9c5e8G41d= 79197G44b6a8G46 Facebook's offices are located at 1601 S. California Ave., Palo Alto, CA = 94304.