From owner-freebsd-net@FreeBSD.ORG Sun Dec 19 04:23:44 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFF6016A4CF for ; Sun, 19 Dec 2004 04:23:44 +0000 (GMT) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id D642C43D41 for ; Sun, 19 Dec 2004 04:23:44 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id iBJ4NgwN012793 for ; Sat, 18 Dec 2004 20:23:43 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (pc1.oakwoodazabu1-unet.ocn.ne.jp [220.110.140.201]) by mail.meer.net (8.12.10/8.12.10/meer) with ESMTP id iBJ4Net7038977 for ; Sat, 18 Dec 2004 20:23:40 -0800 (PST) (envelope-from gnn@neville-neil.com) Date: Sun, 19 Dec 2004 13:23:43 +0900 Message-ID: From: gnn@FreeBSD.org To: freebsd-net@FreeBSD.org User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.5 Emacs/21.2 (powerpc-apple-darwin) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Subject: Dingo and PerForce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 04:23:45 -0000 Howdy, For those who use PerForce and want to work on Dingo there is now a dingo branch, named "dingo". The dingo branch contains all of src, not just sys, as I suspect there are userland bits we'll want to do. I know I'll be doing userland things. Please make your own sub-branch off of dingo. For example, here is mine (gnn_dingo): # A Perforce Branch Specification. # # Branch: The branch name. # Update: The date this specification was last modified. # Access: The date of the last 'integrate' using this branch. # Owner: The user who created this branch. # Description: A short description of the branch (optional). # Options: Branch update options: [un]locked. # View: Lines to map source depot files to target depot files. # # Use 'p4 help branch' to see more about branch views. Branch: gnn_dingo Update: 2004/12/19 03:17:21 Access: 2004/12/19 03:17:26 Owner: gnn Description: My personal sub-branch of the dingo branch. Options: locked View: //depot/projects/dingo/sys/... //depot/user/gnn/dingo/sys/... //depot/projects/dingo/tools/... //depot/user/gnn/dingo/tools/... The main branch (dingo) is locked against changes and, more importantly, accidental deletion. Let me know if there are any issues with any of this. Oh, and the integration from vendor to dingo was done last Saturday night around 23:00 JST. Later, George From owner-freebsd-net@FreeBSD.ORG Sun Dec 19 10:21:29 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98BE616A4CE for ; Sun, 19 Dec 2004 10:21:29 +0000 (GMT) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id A851443D55 for ; Sun, 19 Dec 2004 10:21:28 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received-SPF: pass (mp2.macomnet.net: domain of maxim@macomnet.ru designates 127.0.0.1 as permitted sender) receiver=mp2.macomnet.net; client_ip=127.0.0.1; envelope-from=maxim@macomnet.ru; Received: from localhost (localhost [127.0.0.1]) by mp2.macomnet.net (8.12.11/8.12.11) with ESMTP id iBJALN3B034772; Sun, 19 Dec 2004 13:21:25 +0300 (MSK) (envelope-from maxim@macomnet.ru) Date: Sun, 19 Dec 2004 13:21:23 +0300 (MSK) From: Maxim Konovalov To: Mike Silbersack In-Reply-To: <20041218033226.L28788@odysseus.silby.com> Message-ID: <20041219130649.F790@mp2.macomnet.net> References: <20041218033226.L28788@odysseus.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SpamTest-Info: Profile: Formal (180/041217) X-SpamTest-Info: Profile: Detect Hard (4/030526) X-SpamTest-Info: Profile: SysLog X-SpamTest-Info: Profile: Marking - Keywords (2/030321) X-SpamTest-Status: Not detected X-SpamTest-Version: SMTP-Filter Version 2.0.0 [0124], SpamtestISP/Release cc: net@freebsd.org Subject: Re: Alternate port randomization approaches X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 10:21:29 -0000 Hi Mike, On Sat, 18 Dec 2004, 04:03-0600, Mike Silbersack wrote: [...] > Although this isn't a perfect fix, I think that it should be > acceptable for the vast majority of systems, and I'd like to get it > in before 4.11-release ships. To be conservative, I'll probably > choose a value like 5, which should be fine for most systems out > there. Super specialized users will always be able to lower it to > 0. Can we leave it zero by default? I affraid this patch won't get much testing before 4.11-REL. The super specialized users will always be able to set net.inet.ip.portrange.randomized whatever they want to. The next thing I am worry about - some users already have net.inet.ip.portrange.randomized=1 in their /etc/sysctl.conf and now we are going to change a meaning of this sysctl. Can we garantee there are no any side effects with this setting? I failed to find the documentation part of your patch also :-) -- Maxim Konovalov From owner-freebsd-net@FreeBSD.ORG Sun Dec 19 13:50:12 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A37F416A4CF for ; Sun, 19 Dec 2004 13:50:12 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB31D43D3F for ; Sun, 19 Dec 2004 13:50:11 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 72416 invoked from network); 19 Dec 2004 13:38:09 -0000 Received: from unknown (HELO freebsd.org) ([195.134.148.7]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 19 Dec 2004 13:38:09 -0000 Message-ID: <41C58711.A343881C@freebsd.org> Date: Sun, 19 Dec 2004 14:50:09 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: gnn@FreeBSD.org References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@FreeBSD.org Subject: Re: Dingo and PerForce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 13:50:12 -0000 gnn@FreeBSD.org wrote: > > Howdy, > > For those who use PerForce and want to work on Dingo there is Did you update the Dingo project page with the stuff I sent you about three weeks ago? -- Andre > now a dingo branch, named "dingo". The dingo branch contains > all of src, not just sys, as I suspect there are userland bits > we'll want to do. I know I'll be doing userland things. > Please make your own sub-branch off of dingo. For example, > here is mine (gnn_dingo): > > # A Perforce Branch Specification. > # > # Branch: The branch name. > # Update: The date this specification was last modified. > # Access: The date of the last 'integrate' using this branch. > # Owner: The user who created this branch. > # Description: A short description of the branch (optional). > # Options: Branch update options: [un]locked. > # View: Lines to map source depot files to target depot files. > # > # Use 'p4 help branch' to see more about branch views. > > Branch: gnn_dingo > > Update: 2004/12/19 03:17:21 > > Access: 2004/12/19 03:17:26 > > Owner: gnn > > Description: > My personal sub-branch of the dingo branch. > > Options: locked > > View: > //depot/projects/dingo/sys/... //depot/user/gnn/dingo/sys/... > //depot/projects/dingo/tools/... //depot/user/gnn/dingo/tools/... > > The main branch (dingo) is locked against changes and, more > importantly, accidental deletion. Let me know if there are any issues > with any of this. > > Oh, and the integration from vendor to dingo was done last Saturday > night around 23:00 JST. > > Later, > George > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Sun Dec 19 17:20:26 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2505816A4CE; Sun, 19 Dec 2004 17:20:26 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9BBF43D1D; Sun, 19 Dec 2004 17:20:25 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.209] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1Cg4jI-0002Lo-00; Sun, 19 Dec 2004 18:20:24 +0100 Received: from [80.131.159.125] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1Cg4jI-0002DN-00; Sun, 19 Dec 2004 18:20:24 +0100 From: Max Laier To: freebsd-net@freebsd.org Date: Sun, 19 Dec 2004 18:20:17 +0100 User-Agent: KMail/1.7.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1971132.UmuDyrQo8W"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412191820.23664.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 cc: gnn@freebsd.org Subject: Re: Dingo and PerForce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 17:20:26 -0000 --nextPart1971132.UmuDyrQo8W Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 19 December 2004 05:23, gnn@FreeBSD.org wrote: > For those who use PerForce and want to work on Dingo there is > now a dingo branch, named "dingo". The dingo branch contains > all of src, not just sys, as I suspect there are userland bits > we'll want to do. I know I'll be doing userland things. > Please make your own sub-branch off of dingo. For example, > here is mine (gnn_dingo): <...> > The main branch (dingo) is locked against changes and, more > importantly, accidental deletion. Let me know if there are any issues > with any of this. > > Oh, and the integration from vendor to dingo was done last Saturday > night around 23:00 JST. I am not all that familiar with perforce so I am wondering: What is the=20 benefit of having this branch if it will be tracking HEAD anyway, we can ju= st=20 branch off the normal vendor branch. Or do you plan to integrate parts back? I have 'mlaier_carp2' off the vendor branch. What will be the benefit if I= =20 move it to 'dingo' instead? =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart1971132.UmuDyrQo8W Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBxbhXXyyEoT62BG0RAufyAJ45BCwprf3VbLqZoeDK2Qbx4fa5EQCaA7Mm HBWeKMe4jvOY67UCLbmVeb8= =am+I -----END PGP SIGNATURE----- --nextPart1971132.UmuDyrQo8W-- From owner-freebsd-net@FreeBSD.ORG Sun Dec 19 17:32:30 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6EC7C16A4CE; Sun, 19 Dec 2004 17:32:30 +0000 (GMT) Received: from stephanie.unixdaemons.com (stephanie.unixdaemons.com [67.18.111.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0FB143D48; Sun, 19 Dec 2004 17:32:29 +0000 (GMT) (envelope-from bmilekic@technokratis.com) Received: from stephanie.unixdaemons.com (bmilekic@localhost.unixdaemons.com [127.0.0.1])iBJHWRYk072769; Sun, 19 Dec 2004 12:32:27 -0500 (EST) Received: (from bmilekic@localhost) by stephanie.unixdaemons.com (8.13.1/8.12.1/Submit) id iBJHWR5K072768; Sun, 19 Dec 2004 12:32:27 -0500 (EST) (envelope-from bmilekic@technokratis.com) X-Authentication-Warning: stephanie.unixdaemons.com: bmilekic set sender to bmilekic@technokratis.com using -f Date: Sun, 19 Dec 2004 12:32:27 -0500 From: Bosko Milekic To: Max Laier Message-ID: <20041219173227.GA72013@technokratis.com> References: <200412191820.23664.max@love2party.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200412191820.23664.max@love2party.net> User-Agent: Mutt/1.4.2.1i cc: freebsd-net@freebsd.org cc: gnn@freebsd.org Subject: Re: Dingo and PerForce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 17:32:30 -0000 This way he can push changes back into 'dingo' before pushing them back into HEAD. It makes a lot of sense, actually, to do this sort of 3-tier approach when multiple people are working on different parts of a larger sub-project, like for example dingo. HEAD (top, must work) <-- (dingo, pre-production, test all changes together) <-- (your individual branch, single set of changes). You develop in your individual branch, test your changes. If all is well, you push into dingo, where changes get tested with respect to other dingo-related changes (which have not yet been pushed into HEAD). When it's all ready, everything gets pushed at once into HEAD, or in pieces, but you know that the individual pieces work well together. This is because dingo changes less often than HEAD. -Bosko On Sun, Dec 19, 2004 at 06:20:17PM +0100, Max Laier wrote: > On Sunday 19 December 2004 05:23, gnn@FreeBSD.org wrote: > > For those who use PerForce and want to work on Dingo there is > > now a dingo branch, named "dingo". The dingo branch contains > > all of src, not just sys, as I suspect there are userland bits > > we'll want to do. I know I'll be doing userland things. > > Please make your own sub-branch off of dingo. For example, > > here is mine (gnn_dingo): > <...> > > The main branch (dingo) is locked against changes and, more > > importantly, accidental deletion. Let me know if there are any issues > > with any of this. > > > > Oh, and the integration from vendor to dingo was done last Saturday > > night around 23:00 JST. > > I am not all that familiar with perforce so I am wondering: What is the > benefit of having this branch if it will be tracking HEAD anyway, we can just > branch off the normal vendor branch. Or do you plan to integrate parts back? > > I have 'mlaier_carp2' off the vendor branch. What will be the benefit if I > move it to 'dingo' instead? > > -- > /"\ Best regards, | mlaier@freebsd.org > \ / Max Laier | ICQ #67774661 > X http://pf4freebsd.love2party.net/ | mlaier@EFnet > / \ ASCII Ribbon Campaign | Against HTML Mail and News -- Bosko Milekic bmilekic@technokratis.com bmilekic@FreeBSD.org From owner-freebsd-net@FreeBSD.ORG Sun Dec 19 20:32:39 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F173F16A4CE for ; Sun, 19 Dec 2004 20:32:39 +0000 (GMT) Received: from borgtech.ca (borgtech.ca [216.187.106.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBD0743D46 for ; Sun, 19 Dec 2004 20:32:39 +0000 (GMT) (envelope-from asegu@borgtech.ca) Received: from www.borgtech.ca (localhost.borgtech.ca [127.0.0.1]) by borgtech.ca (Postfix) with SMTP id 8D39854C3; Sun, 19 Dec 2004 20:33:57 +0000 (GMT) Received: from 161.53.212.202 (SquirrelMail authenticated user asegu.borgtech.ca) by borg.darktech.org with HTTP; Sun, 19 Dec 2004 20:33:57 -0000 (GMT) Message-ID: <3721.161.53.212.202.1103488437.squirrel@borg.darktech.org> In-Reply-To: <721371959296.20041217154130@star-sw.com> References: <20041217094937.E4E6054C3@borgtech.ca> <721371959296.20041217154130@star-sw.com> Date: Sun, 19 Dec 2004 20:33:57 -0000 (GMT) From: asegu@borgtech.ca To: freebsd-net@freebsd.org User-Agent: SquirrelMail/1.4.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal cc: "Nickolay A. Kritsky" Subject: Re: FW: Curiosity in IPFW/Freebsd bridge. [more] 802.1q VLAN at fault? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 20:32:40 -0000 Ok, the whole discussion to date led to how VLAN traffic wasn't being registered by IPFW in my system. I think that it'll probably be too late for a code change to fix my problem, so I'm going to go the route of changing the network configuration. I've rebuilt to 4.10 and.. And I had no luck there (IPFW _really_ doesn't see the traffic now!). On the other hand, I've read about vlan pseudo-dev and goten myself access to the switch's configuration. So tomorrow evening I plan on changing the vlan id used to 3, and then in freebsd, use the following configuration(and I post this to the list to see if anybody knows that this is going to fail) fxp1 --> router (uses ID 2) fxp0 --> switch (uses ID 2, will switch to ID 3) ifconfig vlan1 vlan 3 vlandev fxp0 ifconfig vlan0 vlan 2 vlandev fxp1 sysctl net.link.ether.bridge_cfg=vlan1,vlan0 sysctl net.link.ether.bridge_ipfw=1 Does anybody think this will allow IPFW to see the packets? or that this will outright fail? Thank you everybody, Andrew From owner-freebsd-net@FreeBSD.ORG Sun Dec 19 21:53:32 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 856E216A518 for ; Sun, 19 Dec 2004 21:53:31 +0000 (GMT) Received: from poczta.o2.pl (mx.go2.pl [193.17.41.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B82A43D55 for ; Sun, 19 Dec 2004 21:53:30 +0000 (GMT) (envelope-from knockefreebsd@o2.pl) Received: from ALFA (aaf223.warszawa.sdi.tpnet.pl [217.97.85.223]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by poczta.o2.pl (Postfix) with ESMTP id DBC0A137701; Sun, 19 Dec 2004 22:53:27 +0100 (CET) Message-ID: <004e01c4e615$70234d80$df5561d9@ALFA> From: "Heinz Knocke" To: "Bjoern A. Zeeb" References: <003501c4e228$5f2cd780$df5561d9@ALFA> <006301c4e2f4$26a67fc0$df5561d9@ALFA> Date: Sun, 19 Dec 2004 22:55:18 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 cc: freebsd-net@freebsd.org Subject: Re: Marvell 88E8001 on sk0 and RELENG_5_3 - big problems X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 21:53:32 -0000 ----- Original Message -----=20 From: "Bjoern A. Zeeb" To: "Heinz Knocke" Cc: Sent: Thursday, December 16, 2004 2:45 PM Subject: Re: Marvell 88E8001 on sk0 and RELENG_5_3 - big problems > would you mind trying this patch. It should only activate jumbo frames > conditional on interface MTU like we do for xmacii. >=20 >=20 > Index: sys/pci/if_sk.c > (...) I tried this one and seems to work corectly :) Jumbograms were used, = data stream was smooth,=20 I haven't seen any error messages in system log.=20 In rough tests I had a little bit better speeds than with this one:=20 http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/if_sk.c.diff?r1=3D1= .51&r2=3D1.52 But I only tried netperf with maximal message send size on similar = boxes, if you'd like some other tests,=20 let me know the details.=20 By the way - do you know if sk(4) driver supports device polling (man 4 = polling)? I know there were some plans to make it work, but I couldn't found any up2date information.=20 hk From owner-freebsd-net@FreeBSD.ORG Sun Dec 19 22:35:08 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECC1416A4CE for ; Sun, 19 Dec 2004 22:35:08 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20CAF43D45 for ; Sun, 19 Dec 2004 22:35:08 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 14F2D1FF9A8; Sun, 19 Dec 2004 23:35:07 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 091181FF931; Sun, 19 Dec 2004 23:35:04 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 4C41A15659; Sun, 19 Dec 2004 22:30:31 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 49512155FB; Sun, 19 Dec 2004 22:30:32 +0000 (UTC) Date: Sun, 19 Dec 2004 22:30:32 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Heinz Knocke In-Reply-To: <004e01c4e615$70234d80$df5561d9@ALFA> Message-ID: References: <003501c4e228$5f2cd780$df5561d9@ALFA> <004e01c4e615$70234d80$df5561d9@ALFA> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: freebsd-net@freebsd.org Subject: Re: Marvell 88E8001 on sk0 and RELENG_5_3 - big problems X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 22:35:09 -0000 On Sun, 19 Dec 2004, Heinz Knocke wrote: > > Index: sys/pci/if_sk.c > > (...) > > I tried this one and seems to work corectly :) Jumbograms were used, data stream was smooth, > I haven't seen any error messages in system log. > In rough tests I had a little bit better speeds than with this one: > http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/if_sk.c.diff?r1=1.51&r2=1.52 ok; I will get this comitted soon then. Thanks for testing. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-net@FreeBSD.ORG Mon Dec 20 00:49:39 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9576E16A4CE for ; Mon, 20 Dec 2004 00:49:39 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAF6543D31 for ; Mon, 20 Dec 2004 00:49:37 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iBK0mXSr005947 for ; Mon, 20 Dec 2004 11:18:33 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id ; Sat, 18 Dec 2004 19:16:44 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iBI8e7Q15721; Sat, 18 Dec 2004 19:10:07 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id YK3667S4; Sat, 18 Dec 2004 19:09:54 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iBI8eqvs054376 ; Sat, 18 Dec 2004 19:10:52 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iBI8eqwu054375; Sat, 18 Dec 2004 19:10:52 +1030 (CST) (envelope-from wilkinsa) Date: Sat, 18 Dec 2004 19:10:51 +1030 From: "Wilkinson, Alex" To: freebsd-net@freebsd.org, Donatas Message-ID: <20041218084048.GA54243@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-net@freebsd.org, Donatas References: <005801c4e42a$a1825890$9f90a8c0@donatas> <20041217223519.GB27607@odin.ac.hmc.edu> <20041217230349.GA15905@ack.Berkeley.EDU> <20041218081627.GA54494@scylla.towardex.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20041218081627.GA54494@scylla.towardex.com> User-Agent: Mutt/1.5.6i Subject: Re: vlan double tagging X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 00:49:39 -0000 0n Sat, Dec 18, 2004 at 03:16:27AM -0500, James wrote: > On Fri, Dec 17, 2004 at 03:03:49PM -0800, Mike Hunter wrote: > > On Dec 17, "Brooks Davis" wrote: > > > > > On Fri, Dec 17, 2004 at 01:22:02PM +0200, Donatas wrote: > > > > hello, > > > > i'd like to ask if there's any possibility to pass double tagged vlan packets through freebsd 5.x routers? > > > > and....how many level1 vlans are supported on one parent device? > > > > > > I don't know what happens with double tagged vlan packets. > > > > I think what he's asking about is whether FreeBSD prevents any of the > > nasty hacks that can be accomplished by double-tagging frames, or if there > > is something he can do with netgraph to prevent such badness. > > /me thinks he's asking for q-in-q tunneling feature. What is 'q-in-q tunneling' ? - aW From owner-freebsd-net@FreeBSD.ORG Mon Dec 20 01:44:26 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E35616A4CE for ; Mon, 20 Dec 2004 01:44:26 +0000 (GMT) Received: from mx01.bos.ma.towardex.com (mx01.bos.ma.towardex.com [65.124.16.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5ADB43D49 for ; Mon, 20 Dec 2004 01:44:25 +0000 (GMT) (envelope-from haesu@mx01.bos.ma.towardex.com) Received: by mx01.bos.ma.towardex.com (TowardEX ESMTP 3.0p11_DAKN, from userid 1001) id B06852FA16; Sun, 19 Dec 2004 20:44:25 -0500 (EST) Date: Sun, 19 Dec 2004 20:44:25 -0500 From: James To: freebsd-net@freebsd.org Message-ID: <20041220014425.GA5686@scylla.towardex.com> References: <005801c4e42a$a1825890$9f90a8c0@donatas> <20041217223519.GB27607@odin.ac.hmc.edu> <20041217230349.GA15905@ack.Berkeley.EDU> <20041218081627.GA54494@scylla.towardex.com> <20041218084048.GA54243@squash.dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041218084048.GA54243@squash.dsto.defence.gov.au> User-Agent: Mutt/1.4.1i Subject: Re: vlan double tagging X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 01:44:26 -0000 On Sat, Dec 18, 2004 at 07:10:51PM +1030, Wilkinson, Alex wrote: > 0n Sat, Dec 18, 2004 at 03:16:27AM -0500, James wrote: > > > /me thinks he's asking for q-in-q tunneling feature. > > What is 'q-in-q tunneling' ? http://www.google.com/search?hl=en&q=q-in-q+tunneling -J -- James Jun TowardEX Technologies, Inc. Technical Lead Boston IPv4/IPv6 Web Hosting, Colocation and james@towardex.com Network design/consulting & configuration services cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net From owner-freebsd-net@FreeBSD.ORG Mon Dec 20 02:01:18 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3319316A4CE for ; Mon, 20 Dec 2004 02:01:18 +0000 (GMT) Received: from nic-naa.net (nic-naa.net [216.220.241.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E74843D1F for ; Mon, 20 Dec 2004 02:01:17 +0000 (GMT) (envelope-from brunner@nic-naa.net) Received: from nic-naa.net (localhost [127.0.0.1]) by nic-naa.net (8.13.1/8.13.1) with ESMTP id iBJM0BRg019651; Sun, 19 Dec 2004 22:00:11 GMT (envelope-from brunner@nic-naa.net) Message-Id: <200412192200.iBJM0BRg019651@nic-naa.net> To: James In-Reply-To: Your message of "Sun, 19 Dec 2004 20:44:25 EST." <20041220014425.GA5686@scylla.towardex.com> Date: Sun, 19 Dec 2004 22:00:10 +0000 From: Eric Brunner-Williams in Portland Maine cc: freebsd-net@freebsd.org Subject: Re: vlan double tagging X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 02:01:18 -0000 I'm still working on the problem. I'm waiting on a cert renewal that seems to have gotten stuck. From owner-freebsd-net@FreeBSD.ORG Mon Dec 20 04:45:34 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5ED416A4CE for ; Mon, 20 Dec 2004 04:45:34 +0000 (GMT) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FC9E43D46 for ; Mon, 20 Dec 2004 04:45:34 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) iBK4jWwN036974; Sun, 19 Dec 2004 20:45:32 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (pc1.oakwoodazabu1-unet.ocn.ne.jp [220.110.140.201]) by mail.meer.net (8.12.10/8.12.10/meer) with ESMTP id iBK4jUib036170; Sun, 19 Dec 2004 20:45:31 -0800 (PST) (envelope-from gnn@neville-neil.com) Date: Mon, 20 Dec 2004 13:45:26 +0900 Message-ID: From: gnn@freebsd.org To: Bosko Milekic In-Reply-To: <20041219173227.GA72013@technokratis.com> References: <200412191820.23664.max@love2party.net> <20041219173227.GA72013@technokratis.com> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.5 Emacs/21.2 (powerpc-apple-darwin) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: Dingo and PerForce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 04:45:34 -0000 At Sun, 19 Dec 2004 12:32:27 -0500, Bosko Milekic wrote: > You develop in your individual branch, test your changes. If all is > well, you push into dingo, where changes get tested with respect to > other dingo-related changes (which have not yet been pushed into HEAD). > When it's all ready, everything gets pushed at once into HEAD, or in > pieces, but you know that the individual pieces work well together. > This is because dingo changes less often than HEAD. Thanks Bosko, this is it exactly. Later, George From owner-freebsd-net@FreeBSD.ORG Mon Dec 20 05:37:03 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1003C16A4CE for ; Mon, 20 Dec 2004 05:37:03 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FB1243D41 for ; Mon, 20 Dec 2004 05:37:00 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iBK5ZuOC004746 for ; Mon, 20 Dec 2004 16:05:56 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Mon, 20 Dec 2004 16:06:53 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iBK5UlQ01833 for ; Mon, 20 Dec 2004 16:00:48 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id YK369R27; Mon, 20 Dec 2004 16:00:33 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iBK5VdPF038561 for ; Mon, 20 Dec 2004 16:01:39 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iBK5VdUH038560 for freebsd-net@freebsd.org; Mon, 20 Dec 2004 16:01:39 +1030 (CST) (envelope-from wilkinsa) Date: Mon, 20 Dec 2004 16:01:39 +1030 From: "Wilkinson, Alex" To: freebsd-net@freebsd.org Message-ID: <20041220053139.GN36954@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-net@freebsd.org References: <41C58711.A343881C@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <41C58711.A343881C@freebsd.org> User-Agent: Mutt/1.5.6i Subject: Re: Dingo and PerForce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 05:37:03 -0000 0n Sun, Dec 19, 2004 at 02:50:09PM +0100, Andre Oppermann wrote: >> now a dingo branch, named "dingo". The dingo branch contains >> all of src, not just sys, as I suspect there are userland bits >> we'll want to do. I know I'll be doing userland things. >> Please make your own sub-branch off of dingo. For example, >> here is mine (gnn_dingo): What is dingo ? - aW From owner-freebsd-net@FreeBSD.ORG Mon Dec 20 06:04:24 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B59AA16A4CE for ; Mon, 20 Dec 2004 06:04:24 +0000 (GMT) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB7CC43D3F for ; Mon, 20 Dec 2004 06:04:23 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received-SPF: pass (mp2.macomnet.net: domain of maxim@macomnet.ru designates 127.0.0.1 as permitted sender) receiver=mp2.macomnet.net; client_ip=127.0.0.1; envelope-from=maxim@macomnet.ru; Received: from localhost (localhost [127.0.0.1]) by mp2.macomnet.net (8.12.11/8.12.11) with ESMTP id iBK64H7q011797; Mon, 20 Dec 2004 09:04:17 +0300 (MSK) (envelope-from maxim@macomnet.ru) Date: Mon, 20 Dec 2004 09:04:17 +0300 (MSK) From: Maxim Konovalov To: "Wilkinson, Alex" In-Reply-To: <20041220053139.GN36954@squash.dsto.defence.gov.au> Message-ID: <20041220090336.I11788@mp2.macomnet.net> References: <20041220053139.GN36954@squash.dsto.defence.gov.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SpamTest-Info: Profile: Formal (180/041217) X-SpamTest-Info: Profile: Detect Hard (4/030526) X-SpamTest-Info: Profile: SysLog X-SpamTest-Info: Profile: Marking - Keywords (2/030321) X-SpamTest-Status: Not detected X-SpamTest-Version: SMTP-Filter Version 2.0.0 [0124], SpamtestISP/Release cc: freebsd-net@freebsd.org Subject: Re: Dingo and PerForce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 06:04:24 -0000 On Mon, 20 Dec 2004, 16:01+1030, Wilkinson, Alex wrote: > 0n Sun, Dec 19, 2004 at 02:50:09PM +0100, Andre Oppermann wrote: > > >> now a dingo branch, named "dingo". The dingo branch contains > >> all of src, not just sys, as I suspect there are userland bits > >> we'll want to do. I know I'll be doing userland things. > >> Please make your own sub-branch off of dingo. For example, > >> here is mine (gnn_dingo): > > What is dingo ? http://www.freebsd.org/projects/dingo/ The first link on google. -- Maxim Konovalov From owner-freebsd-net@FreeBSD.ORG Mon Dec 20 11:02:11 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B81F716A4CE for ; Mon, 20 Dec 2004 11:02:11 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 905B943D3F for ; Mon, 20 Dec 2004 11:02:11 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iBKB2B32047083 for ; Mon, 20 Dec 2004 11:02:11 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iBKB2Aeo047078 for freebsd-net@freebsd.org; Mon, 20 Dec 2004 11:02:10 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 20 Dec 2004 11:02:10 GMT Message-Id: <200412201102.iBKB2Aeo047078@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 11:02:11 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2002/07/26] kern/41007 net overfull traffic on third and fourth adap o [2003/10/14] kern/57985 net [patch] Missing splx in ether_output_fram 2 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/07/11] kern/54383 net [nfs] [patch] NFS root configurations wit 1 problem total. From owner-freebsd-net@FreeBSD.ORG Mon Dec 20 12:25:10 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A98416A4CE; Mon, 20 Dec 2004 12:25:10 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35D7B43D49; Mon, 20 Dec 2004 12:25:09 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 9094D1FF9A8; Mon, 20 Dec 2004 13:25:07 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 8D2BB1FF90C; Mon, 20 Dec 2004 13:25:05 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id DFA8F1575A; Mon, 20 Dec 2004 12:23:39 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id D3F22156BB; Mon, 20 Dec 2004 12:23:39 +0000 (UTC) Date: Mon, 20 Dec 2004 12:23:39 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: FreeBSD current mailing list Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: FreeBSD net mailing list Subject: Re: mem leak in mii ? (fwd) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 12:25:10 -0000 Hi, haven't had any feedback on this.... Can someone please review? Also answers to the questions would be welcome. Thanks. ---------- Forwarded message ---------- Date: Tue, 23 Nov 2004 19:31:10 +0000 (UTC) From: Bjoern A. Zeeb To: John Baldwin Cc: Bjoern A. Zeeb , freebsd-current@FreeBSD.org Subject: Re: mem leak in mii ? On Mon, 22 Nov 2004, John Baldwin wrote: Hi, hope you won't get it twice; the first one didn't seem to go out... > On Friday 19 November 2004 06:49 pm, Bjoern A. Zeeb wrote: > > Hi, > > > > in sys/dev/mii/mii.c there are two calls to malloc for ivars; > > see for example mii_phy_probe: .. > > Where is the free for this malloc ? I cannot find it. > > > > analogous: miibus_probe ? > > It's a leak. It should be free'd when the miibus device is destroyed. Here's > a possible fix: could you please review this one ? Should plug both of the memleaks; also for more error cases. notes: * mii doesn't ssem to be very error corrective and reporting; as others currently also seem to be debugging problems with undetectable PHYs I added some error handling in those places that I touched anyway. * in miibus_probe in the loop there is the possibility - and the comment above the functions also talks about this - that we find more than one PHY ? I currrently doubt that but I don't know for sure. As device_add_child may return NULL we cannot check for that; I had seen some inconsistency while debugging the BMSR_MEDIAMASK check so I added the count variable for this to have a reliable state. * all PHY drivers currently seem to use mii_phy_detach for device_detach. If any implements his own function it will be responsible for freeing the ivars allocated in miibus_probe. This should perhaps be documented somewhere ? patch can also be found at http://sources.zabbadoz.net/freebsd/patchset/mii-memleaks.diff Index: mii.c =================================================================== RCS file: /local/mirror/FreeBSD/r/ncvs/src/sys/dev/mii/mii.c,v retrieving revision 1.20 diff -u -p -r1.20 mii.c --- mii.c 15 Aug 2004 06:24:40 -0000 1.20 +++ mii.c 23 Nov 2004 17:08:58 -0000 @@ -111,7 +111,7 @@ miibus_probe(dev) struct mii_attach_args ma, *args; struct mii_data *mii; device_t child = NULL, parent; - int bmsr, capmask = 0xFFFFFFFF; + int count = 0, bmsr, capmask = 0xFFFFFFFF; mii = device_get_softc(dev); parent = device_get_parent(dev); @@ -145,12 +145,26 @@ miibus_probe(dev) args = malloc(sizeof(struct mii_attach_args), M_DEVBUF, M_NOWAIT); + if (args == NULL) { + device_printf(dev, "%s: memory allocation failure, " + "phyno %d", __func__, ma.mii_phyno); + continue; + } bcopy((char *)&ma, (char *)args, sizeof(ma)); child = device_add_child(dev, NULL, -1); + if (child == NULL) { + free(args, M_DEVBUF); + device_printf(dev, "%s: device_add_child failed", + __func__); + continue; + } device_set_ivars(child, args); + count++; + /* XXX should we break here or is it really possible + * to find more then one PHY ? */ } - if (child == NULL) + if (count == 0) return(ENXIO); device_set_desc(dev, "MII bus"); @@ -173,12 +187,15 @@ miibus_attach(dev) */ mii->mii_ifp = device_get_softc(device_get_parent(dev)); v = device_get_ivars(dev); + if (v == NULL) + return (ENXIO); ifmedia_upd = v[0]; ifmedia_sts = v[1]; + device_set_ivars(dev, NULL); + free(v, M_DEVBUF); ifmedia_init(&mii->mii_media, IFM_IMASK, ifmedia_upd, ifmedia_sts); - bus_generic_attach(dev); - return(0); + return (bus_generic_attach(dev)); } int @@ -186,8 +203,14 @@ miibus_detach(dev) device_t dev; { struct mii_data *mii; + void *v; bus_generic_detach(dev); + v = device_get_ivars(dev); + if (v != NULL) { + device_set_ivars(dev, NULL); + free(v, M_DEVBUF); + } mii = device_get_softc(dev); ifmedia_removeall(&mii->mii_media); mii->mii_ifp = NULL; @@ -305,12 +328,15 @@ mii_phy_probe(dev, child, ifmedia_upd, i int bmsr, i; v = malloc(sizeof(vm_offset_t) * 2, M_DEVBUF, M_NOWAIT); - if (v == 0) { + if (v == NULL) return (ENOMEM); - } v[0] = ifmedia_upd; v[1] = ifmedia_sts; *child = device_add_child(dev, "miibus", -1); + if (*child == NULL) { + free(v, M_DEVBUF); + return (ENXIO); + } device_set_ivars(*child, v); for (i = 0; i < MII_NPHY; i++) { @@ -324,14 +350,22 @@ mii_phy_probe(dev, child, ifmedia_upd, i } if (i == MII_NPHY) { + device_set_ivars(dev, NULL); + free(v, M_DEVBUF); device_delete_child(dev, *child); *child = NULL; return(ENXIO); } - bus_generic_attach(dev); + i = bus_generic_attach(dev); - return(0); + v = device_get_ivars(*child); + if (v != NULL) { + device_set_ivars(*child, NULL); + free(v, M_DEVBUF); + } + + return (i); } /* Index: mii_physubr.c =================================================================== RCS file: /local/mirror/FreeBSD/r/ncvs/src/sys/dev/mii/mii_physubr.c,v retrieving revision 1.21 diff -u -p -r1.21 mii_physubr.c --- mii_physubr.c 29 May 2004 18:09:10 -0000 1.21 +++ mii_physubr.c 23 Nov 2004 17:07:30 -0000 @@ -522,7 +522,13 @@ int mii_phy_detach(device_t dev) { struct mii_softc *sc; + void *args; + args = device_get_ivars(dev); + if (args != NULL) { + device_set_ivars(dev, NULL); + free(args, M_DEVBUF); + } sc = device_get_softc(dev); mii_phy_down(sc); sc->mii_dev = NULL; -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Mon Dec 20 16:31:50 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E272516A4CE for ; Mon, 20 Dec 2004 16:31:50 +0000 (GMT) Received: from ms-dienst.rz.rwth-aachen.de (ms-2.rz.RWTH-Aachen.DE [134.130.3.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DFB043D31 for ; Mon, 20 Dec 2004 16:31:50 +0000 (GMT) (envelope-from chris@unixpages.org) Received: from r220-1 (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by ms-dienst.rz.rwth-aachen.de (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003)) with ESMTP id <0I91003EB4L0DU@ms-dienst.rz.rwth-aachen.de> for freebsd-net@freebsd.org; Mon, 20 Dec 2004 17:31:49 +0100 (MET) Received: from relay.rwth-aachen.de ([134.130.3.1]) by r220-1 (MailMonitor for SMTP v1.2.2 ) ; Mon, 20 Dec 2004 17:31:47 +0100 (MET) Received: from haakonia.hitnet.rwth-aachen.de (mulzirak.hitnet.RWTH-Aachen.DE [137.226.181.149]) iBKGVgEG005700; Mon, 20 Dec 2004 17:31:42 +0100 (MET) Received: from gondor.middleearth (gondor.middleearth [192.168.1.42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))(Postfix) with ESMTP id 34D8A2842E; Mon, 20 Dec 2004 17:31:37 +0100 (CET) Received: by gondor.middleearth (Postfix, from userid 1001) id 6CCBF22824; Mon, 20 Dec 2004 17:31:36 +0100 (CET) Date: Mon, 20 Dec 2004 17:31:36 +0100 From: Christian Brueffer In-reply-to: <004e01c4e615$70234d80$df5561d9@ALFA> To: Heinz Knocke Message-id: <20041220163135.GM10670@unixpages.org> MIME-version: 1.0 Content-type: multipart/signed; boundary=3hAdtgBjtgL7p0NQ; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-disposition: inline User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 6.0-CURRENT X-PGP-Key: http://people.freebsd.org/~brueffer/brueffer.key.asc X-PGP-Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D References: <003501c4e228$5f2cd780$df5561d9@ALFA> <006301c4e2f4$26a67fc0$df5561d9@ALFA> <004e01c4e615$70234d80$df5561d9@ALFA> cc: "Bjoern A. Zeeb" cc: freebsd-net@freebsd.org Subject: Re: Marvell 88E8001 on sk0 and RELENG_5_3 - big problems X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 16:31:51 -0000 --3hAdtgBjtgL7p0NQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 19, 2004 at 10:55:18PM +0100, Heinz Knocke wrote: >=20 > By the way - do you know if sk(4) driver supports device polling > (man 4 polling)? I know there were some plans > to make it work, but I couldn't found any up2date information.=20 >=20 polling(4) isn't supported yet. I'm not aware of anyone working on it either. I'll take a look at it, as time permits (don't have hardware though). - Christian --=20 Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D --3hAdtgBjtgL7p0NQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBxv5nbHYXjKDtmC0RAs7LAKDqEIWdD6aPnnfmrWMiHgC8oGiq6ACg8gmn 1ZFGuCw1NYa34moIFca6d1c= =mbD4 -----END PGP SIGNATURE----- --3hAdtgBjtgL7p0NQ-- From owner-freebsd-net@FreeBSD.ORG Mon Dec 20 17:55:53 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBCA116A4D0; Mon, 20 Dec 2004 17:55:53 +0000 (GMT) Received: from smtp.uol.com.br (smtpout3.uol.com.br [200.221.4.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34BBC43D45; Mon, 20 Dec 2004 17:55:53 +0000 (GMT) (envelope-from giulianocm@uol.com.br) Received: from [201.1.132.37] (unknown [201.1.132.37]) by scorpion3.uol.com.br (Postfix) with ESMTP id 930BD70A93; Mon, 20 Dec 2004 15:53:37 -0200 (BRST) Message-ID: <41C7119B.1020204@uol.com.br> Date: Mon, 20 Dec 2004 15:53:31 -0200 From: Giuliano Cardozo Medalha Organization: WZTECH User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org, freebsd-net@freebsd.org X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Route-Server X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: giulianocm@uol.com.br List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 17:55:54 -0000 Hi, Does anyone knows how to create a route-server for BGPv4 peering using freebsd and vlans (802.1q) ? There is some good tutorial about it ? I read something about quagga software !!! This is enough secure ? Its possible to use it for BGP MD-5 authentication ? How can I do that ? thanks a lot Giuliano From owner-freebsd-net@FreeBSD.ORG Mon Dec 20 18:28:22 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A99CA16A4DF for ; Mon, 20 Dec 2004 18:28:22 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 790F643D2D for ; Mon, 20 Dec 2004 18:28:22 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id iBKISemL015804; Mon, 20 Dec 2004 10:28:40 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iBKISdMh015803; Mon, 20 Dec 2004 10:28:39 -0800 Date: Mon, 20 Dec 2004 10:28:39 -0800 From: Brooks Davis To: Mihail Balikov Message-ID: <20041220182839.GB12399@odin.ac.hmc.edu> References: <001e01c4e527$78caac10$9f90a8c0@donatas> <002501c4e533$7df445f0$c7cdf0d5@misho> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nVMJ2NtxeReIH9PS" Content-Disposition: inline In-Reply-To: <002501c4e533$7df445f0$c7cdf0d5@misho> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-net@freebsd.org Subject: Re: double vlans - once again. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 18:28:22 -0000 --nVMJ2NtxeReIH9PS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 18, 2004 at 08:57:58PM +0200, Mihail Balikov wrote: > I have done this 2 years ago for FreeBSD 4-STABLE >=20 > in sys/net/if_vlan.c in vlan_config(), replace >=20 > if (p->if_data.ifi_type !=3D IFT_ETHER) > return EPROTONOSUPPORT; >=20 > with >=20 > if (p->if_data.ifi_type !=3D IFT_ETHER && > p->if_data.ifi_type !=3D IFT_L2VLAN) > return EPROTONOSUPPORT; Hmm, for -current this appears incomplete. I think the following is what is needed. Any one in a position to test this? -- Brooks Index: if_vlan.c =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=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 RCS file: /home/ncvs/src/sys/net/if_vlan.c,v retrieving revision 1.73 diff -u -p -r1.73 if_vlan.c --- if_vlan.c 15 Aug 2004 06:24:42 -0000 1.73 +++ if_vlan.c 20 Dec 2004 18:25:48 -0000 @@ -273,7 +273,8 @@ vlan_clone_match_ethertag(struct if_clon /* Check for . style interface names. */ IFNET_RLOCK(); TAILQ_FOREACH(ifp, &ifnet, if_link) { - if (ifp->if_type !=3D IFT_ETHER) + if (ifp->if_type !=3D IFT_ETHER && + ifp->if_type !=3D IFT_L2VLAN) continue; if (strncmp(ifp->if_xname, name, strlen(ifp->if_xname)) !=3D 0) continue; @@ -566,6 +567,7 @@ vlan_input(struct ifnet *ifp, struct mbu } else { switch (ifp->if_type) { case IFT_ETHER: + case IFT_L2VLAN: if (m->m_len < sizeof(*evl) && (m =3D m_pullup(m, sizeof(*evl))) =3D=3D NULL) { if_printf(ifp, "cannot pullup VLAN header\n"); @@ -641,7 +643,8 @@ vlan_config(struct ifvlan *ifv, struct i =20 VLAN_LOCK_ASSERT(); =20 - if (p->if_data.ifi_type !=3D IFT_ETHER) + if (p->if_data.ifi_type !=3D IFT_ETHER && + p->if_data.ifi_type !=3D IFT_L2VLAN) return (EPROTONOSUPPORT); if (ifv->ifv_p) return (EBUSY); --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --nVMJ2NtxeReIH9PS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBxxnWXY6L6fI4GtQRAlEqAKCeGEAMg6JJb4ep7JJU9IrsQh5EVwCgokqH PEmV3TLjc5/nWH0OuM4Sosg= =NGb5 -----END PGP SIGNATURE----- --nVMJ2NtxeReIH9PS-- From owner-freebsd-net@FreeBSD.ORG Mon Dec 20 18:32:14 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5413F16A4CE for ; Mon, 20 Dec 2004 18:32:14 +0000 (GMT) Received: from mail.star-sw.com (mail.star-sw.com [217.195.82.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5382E43D31 for ; Mon, 20 Dec 2004 18:32:13 +0000 (GMT) (envelope-from nkritsky@star-sw.com) Received: from ARGON.star-sw.com (argon.star-sw.com [217.195.82.10]) by mail.star-sw.com (8.12.11/8.12.11) with ESMTP id iBKIW79T033695; Mon, 20 Dec 2004 21:32:07 +0300 (MSK) Received: from ibmka.stardevelopers4msi.com ([82.140.87.236]) by ARGON.star-sw.com with Microsoft SMTPSVC(5.0.2195.5329); Mon, 20 Dec 2004 21:32:07 +0300 Date: Mon, 20 Dec 2004 21:32:27 +0300 From: "Nickolay A. Kritsky" X-Mailer: The Bat! (v1.49) Personal X-Priority: 3 (Normal) Message-ID: <8510784015.20041220213227@star-sw.com> To: asegu@borgtech.ca In-reply-To: <3721.161.53.212.202.1103488437.squirrel@borg.darktech.org> References: <20041217094937.E4E6054C3@borgtech.ca> <721371959296.20041217154130@star-sw.com> <3721.161.53.212.202.1103488437.squirrel@borg.darktech.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 20 Dec 2004 18:32:07.0801 (UTC) FILETIME=[360BE690:01C4E6C2] cc: freebsd-net@freebsd.org Subject: RE: FW: Curiosity in IPFW/Freebsd bridge. [more] 802.1q VLAN at fault? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Nickolay A. Kritsky" List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 18:32:14 -0000 Hello asegu, This one should work OK. But do not forget to put parent interfaces in up and promisc mode in your rc.conf, otherwise you will not see any vlan-bridging. Sunday, December 19, 2004, 11:33:57 PM, asegu@borgtech.ca wrote: abc> Ok, the whole discussion to date led to how VLAN traffic wasn't being abc> registered by IPFW in my system. I think that it'll probably be too late abc> for a code change to fix my problem, so I'm going to go the route of abc> changing the network configuration. abc> I've rebuilt to 4.10 and.. And I had no luck there (IPFW _really_ doesn't abc> see the traffic now!). On the other hand, I've read about vlan pseudo-dev abc> and goten myself access to the switch's configuration. abc> So tomorrow evening I plan on changing the vlan id used to 3, and then in abc> freebsd, use the following configuration(and I post this to the list to abc> see if anybody knows that this is going to fail) fxp1 -->> router (uses ID 2) fxp0 -->> switch (uses ID 2, will switch to ID 3) abc> ifconfig vlan1 vlan 3 vlandev fxp0 abc> ifconfig vlan0 vlan 2 vlandev fxp1 abc> sysctl net.link.ether.bridge_cfg=vlan1,vlan0 abc> sysctl net.link.ether.bridge_ipfw=1 abc> Does anybody think this will allow IPFW to see the packets? or that this abc> will outright fail? abc> Thank you everybody, abc> Andrew -- Best regards, ; Nickolay A. Kritsky ; SysAdmin STAR Software LLC ; mailto:nkritsky@star-sw.com From owner-freebsd-net@FreeBSD.ORG Mon Dec 20 19:29:45 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61FFC16A4CE for ; Mon, 20 Dec 2004 19:29:45 +0000 (GMT) Received: from access1.man-m13.wildcardinternet.co.uk (access1.man-m13.wildcardinternet.co.uk [195.10.230.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD15943D49 for ; Mon, 20 Dec 2004 19:29:44 +0000 (GMT) (envelope-from lee@wildcard.net.uk) Received: from gate.office.wildcardinternet.co.uk ([192.168.15.3] helo=gate.wildcard.net.uk) by access1.man-m13.wildcardinternet.co.uk with esmtp (Exim 4.24; FreeBSD 4.7) id 1CgTDz-000DEv-IN for freebsd-net@freebsd.org; Mon, 20 Dec 2004 19:29:43 +0000 Message-Id: <6.1.0.6.0.20041220191713.019eff38@mail.wildcardinternet.co.uk> X-Sender: ljohns@mail.wildcardinternet.co.uk X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6 Date: Mon, 20 Dec 2004 19:28:21 +0000 To: freebsd-net@freebsd.org From: Lee Johnston Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: FreeBSD Router : ARP who-has requests X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 19:29:45 -0000 Hi there, We are using a FreeBSD machine as a router in one of our PoPs (using Quagga for BGP support). Today I've noticed a sudden increase in the amount of ether broadcast traffic on the network. This seems to boil down to the rate the router is issuing ARP who-has requests. The machine has about 10 local subnets connected to it via one interface (ranging in size up to /26's, totalling about a /23). I'm using device polling on the network adapters, and have the following option in the kernel: 'options HZ=1000'. The requests are only for IPs not in use (presumably because the ones in use are cached). I'm seeing the same who-has request for the same IP about 3-4 times a second. We've had the machine configured the same way for about a month, normal broadcast traffic is around 2kbps, but suddenly today it's increased 10 fold to about 20kbps. Does any one have any ideas on this? Could the kernel option (options HZ) which we use for dummynet/polling effect the rate in which ARP requests are issued? I had planned to place each subnet in a VLAN, and looks like this will have to be done fairly quickly. But I just don't understand the sudden increase. My only other though is that some could be port scanning, or someone has just been exploited. Appreciate any feedback. Thanks, Regards, Lee. Lee Johnston, Wildcard Internet t: +44 (0)845 165 1510 f: +44 (0)845 165 1511 m: +44 (0)7795 423 617 e: lee@wildcard.net.uk www: http://www.wildcard.net.uk/ Web Development - Domains - Hosting - Co-location - Dedicated Servers From owner-freebsd-net@FreeBSD.ORG Mon Dec 20 19:42:18 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62AEF16A4CF; Mon, 20 Dec 2004 19:42:18 +0000 (GMT) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13F1D43D2F; Mon, 20 Dec 2004 19:42:18 +0000 (GMT) (envelope-from qing.li@bluecoat.com) Received: from bcs-mail.bluecoat.com (bcs-mail.bluecoat.com [216.52.23.69]) by whisker.bluecoat.com (8.13.0/8.13.0) with ESMTP id iBKJgHUA013512; Mon, 20 Dec 2004 11:42:17 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 20 Dec 2004 11:42:17 -0800 Message-ID: <00CDF9AA240E204FA6E923BD35BC643607C47915@bcs-mail.internal.cacheflow.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: build failure in usr.sbin Thread-Index: AcTmzAMGUJa3xt99SW+IqbxrXTJllg== From: "Li, Qing" To: , X-Scanned-By: MIMEDefang 2.49 on 216.52.23.28 Subject: build failure in usr.sbin X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 19:42:18 -0000 -- Qing cc -O2 -fno-strict-aliasing -pipe -DUSE_INET6 -DIPL_NAME=3D\"/dev/ipl\" -DIPFILTER_LOG -I/usr/src/usr.sbin/ipftest/../../sys/contrib/ipfilter/netinet=20 -I/usr/src/usr.sbin/ipftest/../../sys/contrib/ipfilter -I/usr/src/usr.sbin/ipftest/../../contrib/ipfilter =20 -c /usr/src/usr.sbin/ipftest/../../sys/contrib/ipfilter/netinet/ip_nat.c /usr/src/usr.sbin/ipftest/../../sys/contrib/ipfilter/netinet/ip_nat.c: In function `nat_log': /usr/src/usr.sbin/ipftest/../../sys/contrib/ipfilter/netinet/ip_nat.c:29 04: error: `rulen' undeclared (first use in this function) /usr/src/usr.sbin/ipftest/../../sys/contrib/ipfilter/netinet/ip_nat.c:29 04: error: (Each undeclared identifier is reported only once /usr/src/usr.sbin/ipftest/../../sys/contrib/ipfilter/netinet/ip_nat.c:29 04: error: for each function it appears in.) /usr/src/usr.sbin/ipftest/../../sys/contrib/ipfilter/netinet/ip_nat.c:29 04: error: `np' undeclared (first use in this function) *** Error code 1 Stop in /usr/src/usr.sbin/ipftest. *** Error code 1 Stop in /usr/src/usr.sbin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. From owner-freebsd-net@FreeBSD.ORG Mon Dec 20 23:57:39 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F80916A4CE; Mon, 20 Dec 2004 23:57:39 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44ADD43D58; Mon, 20 Dec 2004 23:57:39 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id iBKNvat0007119; Mon, 20 Dec 2004 15:57:36 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iBKNvaZY007118; Mon, 20 Dec 2004 15:57:36 -0800 Date: Mon, 20 Dec 2004 15:57:36 -0800 From: Brooks Davis To: gnn@freebsd.org Message-ID: <20041220235736.GA6531@odin.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RnlQjJ0d97Da+TV1" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-net@freebsd.org Subject: Re: Dingo and PerForce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 23:57:39 -0000 --RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 19, 2004 at 01:23:43PM +0900, gnn@freebsd.org wrote: > Howdy, >=20 > For those who use PerForce and want to work on Dingo there is > now a dingo branch, named "dingo". The dingo branch contains > all of src, not just sys, as I suspect there are userland bits > we'll want to do. I know I'll be doing userland things. What's the planned model for committing changes to the main dingo branch? The IPv6 ipfw patches I'm working with are probably ready for wider exposure. Also, for subsystems such as ip6fw that have no future, how agressive should we be about nuking them in dingo. My guess is not very because we don't want to hamper work that might need to modify the old stuff to be committed when we aren't entierly sure how much longer we'll be supporting the subsystem in cvs, but I think there's some arugment for a more agressive approach to reduce the amount of junk we have to look at. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --RnlQjJ0d97Da+TV1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBx2bvXY6L6fI4GtQRAnjZAKC6OKcXE3S12oldoRKIhEml+tAdAgCgjqQh /GAUA7kX1XtlJBoOL0Ii9aI= =eHhk -----END PGP SIGNATURE----- --RnlQjJ0d97Da+TV1-- From owner-freebsd-net@FreeBSD.ORG Tue Dec 21 01:01:39 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DE3D16A4CE for ; Tue, 21 Dec 2004 01:01:39 +0000 (GMT) Received: from sv2.per.eftel.com (sv2.per.eftel.com [203.24.100.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id D157143D54 for ; Tue, 21 Dec 2004 01:01:37 +0000 (GMT) (envelope-from dspezialie@gmail.com) Received: from bpfwex01-rsmtp (unknown [202.76.163.13]) by sv2.per.eftel.com (Postfix) with ESMTP id E81221A82CF for ; Tue, 21 Dec 2004 09:01:35 +0800 (WST) Message-ID: <41C775AA.5060800@gmail.com> Date: Tue, 21 Dec 2004 12:00:26 +1100 From: David MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: IPF to PF rule migration tools X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: dspezialie@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2004 01:01:39 -0000 Greetings All and a merry X-Mas, I am looking for a migration script/program to migrate my IPF rule bases to a PF rule base... does anyone know of any such tool or do I need to go through them all by hand?. Thanks in advance. Cheers!, -- David From owner-freebsd-net@FreeBSD.ORG Tue Dec 21 02:05:15 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F1E216A4CE for ; Tue, 21 Dec 2004 02:05:15 +0000 (GMT) Received: from mailhost.schluting.com (schluting.com [131.252.214.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1141243D2F for ; Tue, 21 Dec 2004 02:05:15 +0000 (GMT) (envelope-from charlie@schluting.com) Received: from localhost (localhost [127.0.0.1]) by mailhost.schluting.com (Postfix) with ESMTP id 8E44621E3 for ; Mon, 20 Dec 2004 18:05:14 -0800 (PST) Received: from mailhost.schluting.com ([127.0.0.1]) by localhost (schluting.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 54913-03 for ; Mon, 20 Dec 2004 18:05:07 -0800 (PST) Received: from [131.252.209.122] (smelly.cat.pdx.edu [131.252.209.122]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailhost.schluting.com (Postfix) with ESMTP id EF50120EF for ; Mon, 20 Dec 2004 18:05:06 -0800 (PST) Message-ID: <41C784DC.5020805@schluting.com> Date: Mon, 20 Dec 2004 18:05:16 -0800 From: Charlie Schluting User-Agent: Mozilla Thunderbird 1.0 (X11/20041215) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by your mom at schluting.com Subject: firewalling with tunnels, and/or ipv6 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2004 02:05:15 -0000 Ok, I've got a v6 tunnel, and to make it work I had to "allow ipv6 from " in ipfw. From what I understand, I have to make a completely different set of rules for ipv6, and load them using the -6 flag. Correct so far? Ok, so I want to set up an ipip v4 tunnel to another box (that runs ipf), and then squirt ipv6 through the tunnel. Sounds easy, but I can't even seem to get the ipip tunnel working. The question: How do you configure ipf/ipfw (in a general sense) to allow ipip tunnels? More importantly, if I "allow ipip from " does that mean I just poked a big ass hole in the firewall... i.e. anything coming through the ipip tunnel will pass? Or, does that make an IP layer be shed, then the packet is run through all the rules again? Inefficient, but I'd think this would be the desired behaivor. At any rate, simply allowing ipip from doesn't allow the v4 tunnel to work. What else is needed? (of course static routes, etc.) I think I'll stop here for now; once that's clear I should be able to set it up. Thanks, _Charlie From owner-freebsd-net@FreeBSD.ORG Tue Dec 21 02:43:37 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 89E9216A4CE for ; Tue, 21 Dec 2004 02:43:37 +0000 (GMT) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5174D43D5E for ; Tue, 21 Dec 2004 02:43:37 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) iBL2hZwN069351; Mon, 20 Dec 2004 18:43:36 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (pc1.oakwoodazabu1-unet.ocn.ne.jp [220.110.140.201]) by mail.meer.net (8.12.10/8.12.10/meer) with ESMTP id iBL2hYgA095776; Mon, 20 Dec 2004 18:43:34 -0800 (PST) (envelope-from gnn@neville-neil.com) Date: Tue, 21 Dec 2004 11:43:22 +0900 Message-ID: From: gnn@FreeBSD.org To: Lee Johnston In-Reply-To: <6.1.0.6.0.20041220191713.019eff38@mail.wildcardinternet.co.uk> References: <6.1.0.6.0.20041220191713.019eff38@mail.wildcardinternet.co.uk> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.5 Emacs/21.2 (powerpc-apple-darwin) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: freebsd-net@FreeBSD.org Subject: Re: FreeBSD Router : ARP who-has requests X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2004 02:43:37 -0000 At Mon, 20 Dec 2004 19:28:21 +0000, Lee Johnston wrote: > Does any one have any ideas on this? Could the kernel option (options HZ) > which we use for dummynet/polling effect the rate in which ARP requests are > issued? > > I had planned to place each subnet in a VLAN, and looks like this will have > to be done fairly quickly. But I just don't understand the sudden increase. > My only other though is that some could be port scanning, or someone has > just been exploited. > > Appreciate any feedback. > This may be obvious to you, but I would sniff the net for the IPs that are being arped for. Also, if you're being scanned there might be a pattern. Good luck, George From owner-freebsd-net@FreeBSD.ORG Tue Dec 21 02:47:27 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9405316A4CE; Tue, 21 Dec 2004 02:47:27 +0000 (GMT) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B6B243D4C; Tue, 21 Dec 2004 02:47:27 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) iBL2lOwN069470; Mon, 20 Dec 2004 18:47:25 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (pc1.oakwoodazabu1-unet.ocn.ne.jp [220.110.140.201]) by mail.meer.net (8.12.10/8.12.10/meer) with ESMTP id iBL2lHgA096447; Mon, 20 Dec 2004 18:47:21 -0800 (PST) (envelope-from gnn@neville-neil.com) Date: Tue, 21 Dec 2004 11:46:53 +0900 Message-ID: From: gnn@FreeBSD.org To: Brooks Davis In-Reply-To: <20041220235736.GA6531@odin.ac.hmc.edu> References: <20041220235736.GA6531@odin.ac.hmc.edu> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.5 Emacs/21.2 (powerpc-apple-darwin) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: gnn@FreeBSD.org cc: freebsd-net@FreeBSD.org Subject: Re: Dingo and PerForce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2004 02:47:27 -0000 At Mon, 20 Dec 2004 15:57:36 -0800, Brooks Davis wrote: > > [1 ] > On Sun, Dec 19, 2004 at 01:23:43PM +0900, gnn@freebsd.org wrote: > > Howdy, > > > > For those who use PerForce and want to work on Dingo there is > > now a dingo branch, named "dingo". The dingo branch contains > > all of src, not just sys, as I suspect there are userland bits > > we'll want to do. I know I'll be doing userland things. > > What's the planned model for committing changes to the main dingo > branch? The IPv6 ipfw patches I'm working with are probably ready > for wider exposure. I would think that work being done on Dingo, once people think it's ready, should be shared. The usual comments of "don't break the build" apply. I also figure that folks doing dingo work are watching the dingo branch for changes, but it might be good, before a big change, to say something here on net@. > Also, for subsystems such as ip6fw that have no future, how > agressive should we be about nuking them in dingo. My guess is not > very because we don't want to hamper work that might need to modify > the old stuff to be committed when we aren't entierly sure how much > longer we'll be supporting the subsystem in cvs, but I think there's > some arugment for a more agressive approach to reduce the amount of > junk we have to look at. I like cleaning things up, but I'm really the greenhorn at committing so I hope others wil chime in. If it were my decision I would say that the Dingo branch should be the "cleanest" and then we could decide, when pushing to HEAD, how to handle that. Other thoughts? Later, George From owner-freebsd-net@FreeBSD.ORG Tue Dec 21 05:55:27 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1557216A4CE for ; Tue, 21 Dec 2004 05:55:27 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id A470E43D31 for ; Tue, 21 Dec 2004 05:55:26 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id iBL5tTTM028426; Mon, 20 Dec 2004 21:55:29 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iBL5tTqG028425; Mon, 20 Dec 2004 21:55:29 -0800 Date: Mon, 20 Dec 2004 21:55:29 -0800 From: Brooks Davis To: Charlie Schluting Message-ID: <20041221055528.GA27519@odin.ac.hmc.edu> References: <41C784DC.5020805@schluting.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k1lZvvs/B4yU6o8G" Content-Disposition: inline In-Reply-To: <41C784DC.5020805@schluting.com> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-net@freebsd.org Subject: Re: firewalling with tunnels, and/or ipv6 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2004 05:55:27 -0000 --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 20, 2004 at 06:05:16PM -0800, Charlie Schluting wrote: > Ok, I've got a v6 tunnel, and to make it work I had to "allow ipv6 from= =20 > " in ipfw. From what I understand, I have to make a completely= =20 > different set of rules for ipv6, and load them using the -6 flag. >=20 > Correct so far? ip6fw is an entierly different beast from ipfw. There is no -6 option to ipfw. Use ip6fw instead. If 6.x we should have ipv6 support in ipfw and ip6fw should be gone. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --k1lZvvs/B4yU6o8G Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBx7rQXY6L6fI4GtQRAkBNAJ9R16Bhddf/JIvsRnxbUZAZEOOoeACgtP/N d8KFGuf9ZPJIhLElywdb/tk= =z2Fz -----END PGP SIGNATURE----- --k1lZvvs/B4yU6o8G-- From owner-freebsd-net@FreeBSD.ORG Tue Dec 21 10:47:15 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FAAD16A4CE for ; Tue, 21 Dec 2004 10:47:15 +0000 (GMT) Received: from r2d2.bromirski.net (r2d2.bromirski.net [217.153.57.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C52543D1D for ; Tue, 21 Dec 2004 10:47:14 +0000 (GMT) (envelope-from lbromirski@mr0vka.eu.org) Received: from [127.0.0.1] (unknown [195.117.157.3]) by r2d2.bromirski.net (Postfix) with ESMTP id E95831088B6; Tue, 21 Dec 2004 11:47:12 +0100 (CET) Message-ID: <41C7FF33.6070508@mr0vka.eu.org> Date: Tue, 21 Dec 2004 11:47:15 +0100 From: =?ISO-8859-2?Q?=A3ukasz_Bromirski?= User-Agent: Mozilla Thunderbird 1.0 (Windows/20041205) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Petri Helenius References: <4194CDF9.3000609@mr0vka.eu.org> <41961690.8040406@he.iki.fi> In-Reply-To: <41961690.8040406@he.iki.fi> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit X-Scan-Module: SMTP[mks_vir 2004.12.15 (2004.10.07)] cc: net@freebsd.org Subject: Re: OpenBGPd? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2004 10:47:15 -0000 Petri Helenius wrote: >> Is anyone working on a port of OpenBGPd, or current version of Quagga >> (0.97.3)? > openbgpd compiles fairly painlessly on 5.3. Making it work on 5.2.1 was > definetly more work. So, is anyone willing to share info how to compile OpenBGPd on FreeBSD 5.3 in some greater detail? We're missing `netinet/ip_ipsp.h' obviously, and as Petri said he compiled it, and Andre mentioned some success with porting OpenBGPd to FreeBSD I hope someone could actually drop a line saying `you should do this and this'. Best regards, -- this space was intentionally left blank | Łukasz Bromirski you can insert your favourite quote here | lukasz:bromirski,net From owner-freebsd-net@FreeBSD.ORG Tue Dec 21 04:20:13 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E222D16A4CF for ; Tue, 21 Dec 2004 04:20:13 +0000 (GMT) Received: from webmail-outgoing.us4.outblaze.com (webmail-outgoing.us4.outblaze.com [205.158.62.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 158BC43D58 for ; Tue, 21 Dec 2004 04:20:13 +0000 (GMT) (envelope-from linguae@lycos.com) Received: from wfilter.us4.outblaze.com (wfilter.us4.outblaze.com [205.158.62.180])07CDB180020F for ; Tue, 21 Dec 2004 04:20:13 +0000 (GMT) X-OB-Received: from unknown (208.36.123.33) by wfilter.us4.outblaze.com; 21 Dec 2004 04:20:12 -0000 Received: by ws7-4.us4.outblaze.com (Postfix, from userid 1001) id B16DACA07F; Tue, 21 Dec 2004 04:20:12 +0000 (GMT) Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [4.246.247.42] by ws7-4.us4.outblaze.com with http for linguae@lycos.com; Mon, 20 Dec 2004 23:20:12 -0500 From: linguae@lycos.com To: freebsd-questions@freebsd.org Date: Mon, 20 Dec 2004 23:20:12 -0500 X-Originating-Ip: 4.246.247.42 X-Originating-Server: ws7-4.us4.outblaze.com Message-Id: <20041221042012.B16DACA07F@ws7-4.us4.outblaze.com> X-Mailman-Approved-At: Tue, 21 Dec 2004 13:30:42 +0000 Subject: 3Com Megahertz 3CXEM556 B Multifunction Card Not Working X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2004 04:20:14 -0000 Hello. I have problems trying to get my multifunction 3Com Megahertz=20 3CXEM556 B Ethernet/56K Modem PCMCIA card working on FreeBSD 5.1 on=20 my Compaq Armada 7400. The card works perfectly (as far as the modem=20 part, can't test the ethernet portion) on Windows 98 SE. Whenever I=20 try to configure PPP for my card on FreeBSD, when I type the dialing=20 commands (such as at, atdt, etc.), the output on the screen would=20 either be jarbled or won't appear at all. Here is my dmesg output: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-RELEASE #0: Thu Jun 5 02:55:42 GMT 2003 root@wv1u.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc0689000. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 266677223 Hz CPU: Pentium II/Pentium II Xeon/Celeron (266.68-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x652 Stepping =3D 2 =20=20=20 Features=3D0x183f9ff real memory =3D 67067904 (63 MB) avail memory =3D 58134528 (55 MB) Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Using $PIR table, 7 entries at 0xc00f0970 pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 0.1 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) cbb0: mem 0x7fffe000-0x7fffefff irq 11 at=20 device 12.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb1: mem 0x7ffff000-0x7fffffff irq 11 at=20 device 12.1 on pci0 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 isab0: at device 14.0 on pci0 isa0: on isab0 atapci0: port=20 0x1000-0x100f,0-0x3,0-0x7,0-0x3,0-0x7 at device 14.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ohci0: mem 0x44080000-0x44080fff irq=20 11 at device 14.2 on pci0 usb0: OHCI version 1.0 usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x0e11) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered eisa0: on motherboard mainboard0: on eisa0 slot 0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port=20 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0x200 sio1: port may not be enabled sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (port) unknown: can't assign resources (irq) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) Timecounters tick every 10.000 msec ep0: <3Com Megahertz 3CXEM556 B> at port 0x100-0x10f irq 11 function=20 0 config 7 on pccard0 ep0: eeprom failed to come ready. device_probe_and_attach: ep0 attach returned 6 sio4: <3Com Megahertz 3CXEM556 B> at port 0x110-0x117 irq 11 function=20 1 config 39 on pccard0 sio4: type 16550A with a bogus IIR_TXRDY register sio4: unable to activate interrupt in fast mode - using normal mode ad0: 4108MB [8905/15/63] at ata0-master BIOSDMA Mounting root from ufs:/dev/ad0s2a I did read the ep man page; it did say that my card was "wedged"=20 (which, according to the Jargon File, means that the card doesn't=20 really work). I also used Google to see if other people had problems=20 with the same card, but I didn't find any solutions at all. What do=20 I need to do in order to get my PCMCIA card working properly? I am=20 relatively new to FreeBSD, so I don't really know where to go from=20 here. Thanks in advance. -linguae ---------------------------------------------- An Apple a day keeps the doctor away. Proud supporter of Unix-based operating systems. --=20 _______________________________________________ Find what you are looking for with the Lycos Yellow Pages http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.as= p?SRC=3Dlycos10 From owner-freebsd-net@FreeBSD.ORG Wed Dec 22 21:02:56 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3070416A4CE; Wed, 22 Dec 2004 21:02:56 +0000 (GMT) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id F148943D54; Wed, 22 Dec 2004 21:02:55 +0000 (GMT) (envelope-from qing.li@bluecoat.com) Received: from bcs-mail.bluecoat.com (bcs-mail.bluecoat.com [216.52.23.69]) by whisker.bluecoat.com (8.13.0/8.13.0) with ESMTP id iBML2t7t013354; Wed, 22 Dec 2004 13:02:55 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 22 Dec 2004 13:02:54 -0800 Message-ID: <00CDF9AA240E204FA6E923BD35BC643607C4803C@bcs-mail.internal.cacheflow.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: TCP URG point Thread-Index: AcToaZs4rj1zYtFcRASeS3QwS8Onyg== From: "Li, Qing" To: , X-Scanned-By: MIMEDefang 2.49 on 216.52.23.28 Subject: TCP URG point X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Dec 2004 21:02:56 -0000 It appears the TCP urgent pointer is off by 1. In RFC-1122, section 4.2.2.4 on Page 83 describes the urgent pointer error in RFC-793. The 6.0-CURRENT code has the urgent pointer set to (LAST+1). Any comments before I sent a PR ? -- Qing From owner-freebsd-net@FreeBSD.ORG Wed Dec 22 21:15:52 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4E4116A4CF for ; Wed, 22 Dec 2004 21:15:52 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 154D243D55 for ; Wed, 22 Dec 2004 21:15:52 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 255 invoked from network); 22 Dec 2004 21:03:13 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 22 Dec 2004 21:03:13 -0000 Message-ID: <41C9E437.5040309@freebsd.org> Date: Wed, 22 Dec 2004 22:16:39 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Li, Qing" References: <00CDF9AA240E204FA6E923BD35BC643607C4803C@bcs-mail.internal.cacheflow.com> In-Reply-To: <00CDF9AA240E204FA6E923BD35BC643607C4803C@bcs-mail.internal.cacheflow.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: TCP URG point X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Dec 2004 21:15:52 -0000 Li, Qing wrote: > It appears the TCP urgent pointer is off by 1. > > In RFC-1122, section 4.2.2.4 on Page 83 describes the > urgent pointer error in RFC-793. > > The 6.0-CURRENT code has the urgent pointer set > to (LAST+1). > > Any comments before I sent a PR ? No, please do and send me the PR number. -- Andre From owner-freebsd-net@FreeBSD.ORG Wed Dec 22 21:28:30 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 23C2E16A4CE; Wed, 22 Dec 2004 21:28:30 +0000 (GMT) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05C9143D1D; Wed, 22 Dec 2004 21:28:30 +0000 (GMT) (envelope-from justin@mac.com) Received: from mac.com (smtpin02-en2 [10.13.10.147]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id iBMLSTuR015337; Wed, 22 Dec 2004 13:28:29 -0800 (PST) Received: from [24.6.153.138] (c-24-6-153-138.client.comcast.net [24.6.153.138]) (authenticated bits=0) by mac.com (Xserve/smtpin02/MantshX 4.0) with ESMTP id iBMLSROR009054 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Wed, 22 Dec 2004 13:28:29 -0800 (PST) In-Reply-To: <41C9E437.5040309@freebsd.org> References: <00CDF9AA240E204FA6E923BD35BC643607C4803C@bcs-mail.internal.cacheflow.com> <41C9E437.5040309@freebsd.org> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <6A79A3D3-5460-11D9-99AD-00306544D642@mac.com> Content-Transfer-Encoding: 7bit From: Justin Walker Date: Wed, 22 Dec 2004 13:28:26 -0800 To: freebsd-net@freebsd.org X-Mailer: Apple Mail (2.619) cc: freebsd-current@freebsd.org Subject: Re: TCP URG point X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Dec 2004 21:28:30 -0000 On Dec 22, 2004, at 13:16, Andre Oppermann wrote: > Li, Qing wrote: >> It appears the TCP urgent pointer is off by 1. >> In RFC-1122, section 4.2.2.4 on Page 83 describes the >> urgent pointer error in RFC-793. >> The 6.0-CURRENT code has the urgent pointer set >> to (LAST+1). >> Any comments before I sent a PR ? > > No, please do and send me the PR number. It may be well-known here, but this is a long-standing issue. It's been around since 4.2 days. Cf. the discussions in Stevens's UNPv12e (p. 566) and TCP/IP Illustrated, v1 (p 292-296). It may be impolitic to change this :=} Regards, Justin -- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | "Weaseling out of things is what | separates us from the animals. | Well, except the weasel." | - Homer J Simpson *--------------------------------------*-------------------------------* From owner-freebsd-net@FreeBSD.ORG Wed Dec 22 22:20:50 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7050F16A4CE for ; Wed, 22 Dec 2004 22:20:50 +0000 (GMT) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19E2043D2F for ; Wed, 22 Dec 2004 22:20:50 +0000 (GMT) (envelope-from qing.li@bluecoat.com) Received: from bcs-mail.bluecoat.com (bcs-mail.bluecoat.com [216.52.23.69]) by whisker.bluecoat.com (8.13.0/8.13.0) with ESMTP id iBMMKnUX017569 for ; Wed, 22 Dec 2004 14:20:49 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 22 Dec 2004 14:20:48 -0800 Message-ID: <00CDF9AA240E204FA6E923BD35BC643607C48075@bcs-mail.internal.cacheflow.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: question on tcp_syn_backoff Thread-Index: AcTodF1NQbGjgNagRRq5q9izR6NWDg== From: "Li, Qing" To: X-Scanned-By: MIMEDefang 2.49 on 216.52.23.28 Subject: question on tcp_syn_backoff X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Dec 2004 22:20:50 -0000 I'm trying to understand the logics behind tcp_syn_backoff. Was this a change associated with =20 revision 1.40 date: 2001/02/26 authro: jlemon Does this change have anything to do with RFC-3390 ? -- Qing From owner-freebsd-net@FreeBSD.ORG Thu Dec 23 03:15:27 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEF4816A4CE for ; Thu, 23 Dec 2004 03:15:27 +0000 (GMT) Received: from smtp.volant.org (gate.volant.org [207.111.218.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E04943D49 for ; Thu, 23 Dec 2004 03:15:27 +0000 (GMT) (envelope-from patl+freebsd@volant.org) Received: from 64-144-229-193.client.dsl.net ([64.144.229.193] helo=[192.168.0.22]) by smtp.volant.org with asmtp (TLSv1:AES256-SHA:256) (Exim 4.34 (FreeBSD)) id 1ChJRd-000JxM-Pa; Wed, 22 Dec 2004 19:15:19 -0800 Date: Wed, 22 Dec 2004 19:15:16 -0800 From: Pat Lashley To: Sangwoo Shim , Pierre-Luc Drouin Message-ID: <404B0D742CB7FA6E000F4FD9@vanvoght.phoenix.volant.org> In-Reply-To: <20041215091257.GA79274@neo.redjade.org> References: <41BFA531.90001@pldrouin.net> <20041215091257.GA79274@neo.redjade.org> X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Scan-Signature: 93879de74cb745b3ae09b2a0ed0009a27cf25bd6 X-Spam-User: nobody X-Spam-Score: -4.9 (----) X-Spam-Score-Int: -48 X-Spam-Report: This mail has matched the spam-filter tests listed below. See http://spamassassin.org/tag/ for details about the specific tests reported. In general, the higher the number of total points, the more likely that it actually is spam. (The 'required' number of points listed below is the arbitrary number above which the message is normally considered spam.) Content analysis details: (-4.9 points total, 5.0 required) -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] cc: freebsd-net@freebsd.org Subject: Re: TCP/IP over USB X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Dec 2004 03:15:27 -0000 --On Wednesday, December 15, 2004 18:12:57 +0900 Sangwoo Shim wrote: >> I would like to establish a TCP/IP connection over USB between my >> FreeBSD box and my PDA (Sharp Zaurus SL-6000L) that has a USB host port. >> I've read that udbp can be used for this purpose, but I have not found >> enough information about it to be able to use it. Could someone explain >> me how this can be done? > > FYI, I've talked to YOPY PDA(also StrongArm-based linux PDA) using > udbp + ng_eiface (with minor hack, namely, add DEVICE/VENDOR ID.) > This combination seems to be compatible with linux's usbnet > implementation. But I've told Zaurus doesn't use standard arm linux kernel.. > I think you should hack ng_eiface to set the communication. For another alternative, try: http://www.gank.org/freebsd/cdce.tar.gz Unpack it anywhere, then cd to that directory (as root) and: make make install kldload if_cdce Then plug in the cable from your Zarus - you should wind up with a cdce0 device that you'll need to ifconfig. (You can add an entry to usbd.conf to do that automatically.) I downloaded a copy to use with my YOPY. (I needed to add a config line and the #define statements; but that's all it took. For anyone trying this with their own YOPY, leave off the CDCE_ZAURUS flag from the YOPY config line.) Now that that's out of the way, Sangwoo, could you post the details of your dubp + ng_eiface solution? I might want to switch to that. -Pat From owner-freebsd-net@FreeBSD.ORG Thu Dec 23 08:20:47 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5C5316A4CE for ; Thu, 23 Dec 2004 08:20:47 +0000 (GMT) Received: from orion.erdves.lt (ns2.lrtc.net [217.9.240.98]) by mx1.FreeBSD.org (Postfix) with SMTP id 03C1743D31 for ; Thu, 23 Dec 2004 08:20:46 +0000 (GMT) (envelope-from donatas@lrtc.net) Received: (qmail 37836 invoked from network); 23 Dec 2004 08:20:44 -0000 Received: from p2p-241-242-ird.vln0.lrtc.net (HELO donatas) (217.9.241.242) by orion.erdves.lt with SMTP; 23 Dec 2004 08:20:44 -0000 Message-ID: <000601c4e8c8$4aed85c0$9f90a8c0@donatas> From: "Donatas" To: Date: Thu, 23 Dec 2004 10:20:41 +0200 Organization: AB Lietuvos Radijo ir Televizijos Centras MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Content-Type: text/plain; charset="iso-8859-4" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Re: double vlans - once again - experiment unsucsessfull X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Donatas List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Dec 2004 08:20:47 -0000 well, we've tired both "tunings" - the short-one suggested my M.Balikov = and the longer-one, suggested by B.Davis in both cases - "Protocol not supported" how we've done this: on FreeBSD 5.3 stable: edited if_vlan.c then=20 make buildworld make installworld mergemaster make clean the test: ifconfig vlan1 create ifconfig vlan2 create ifconfig vlan1 vlan 1 vlandev em0 ifconfig vlan2 vlan 2 vlandev vlan1 SIOCSETVLAN: "Protocol not supported" or maybe it's possible to use hardware and software tagging = simultaneously? we could achieve double tagging proces by combining hardware and = software tag in the ethernet packet. -------------------------------------------------------------------------= ------- Re: double vlans - once again. Brooks Davis Mon, 20 Dec 2004 10:28:56 -0800 On Sat, Dec 18, 2004 at 08:57:58PM +0200, Mihail Balikov wrote: > I have done this 2 years ago for FreeBSD 4-STABLE >=20 > in sys/net/if_vlan.c in vlan_config(), replace >=20 > if (p->if_data.ifi_type !=3D IFT_ETHER) > return EPROTONOSUPPORT; >=20 > with >=20 > if (p->if_data.ifi_type !=3D IFT_ETHER && > p->if_data.ifi_type !=3D IFT_L2VLAN) > return EPROTONOSUPPORT; Hmm, for -current this appears incomplete. I think the following is what is needed. Any one in a position to test this? -- Brooks Index: if_vlan.c =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=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 RCS file: /home/ncvs/src/sys/net/if_vlan.c,v retrieving revision 1.73 diff -u -p -r1.73 if_vlan.c --- if_vlan.c 15 Aug 2004 06:24:42 -0000 1.73 +++ if_vlan.c 20 Dec 2004 18:25:48 -0000 @@ -273,7 +273,8 @@ vlan_clone_match_ethertag(struct if_clon /* Check for . style interface names. */ IFNET_RLOCK(); TAILQ_FOREACH(ifp, &ifnet, if_link) { - if (ifp->if_type !=3D IFT_ETHER) + if (ifp->if_type !=3D IFT_ETHER && + ifp->if_type !=3D IFT_L2VLAN) continue; if (strncmp(ifp->if_xname, name, strlen(ifp->if_xname)) = !=3D 0) continue; @@ -566,6 +567,7 @@ vlan_input(struct ifnet *ifp, struct mbu } else { switch (ifp->if_type) { case IFT_ETHER: + case IFT_L2VLAN: if (m->m_len < sizeof(*evl) && (m =3D m_pullup(m, sizeof(*evl))) =3D=3D = NULL) { if_printf(ifp, "cannot pullup VLAN = header\n"); @@ -641,7 +643,8 @@ vlan_config(struct ifvlan *ifv, struct i =20 VLAN_LOCK_ASSERT(); =20 - if (p->if_data.ifi_type !=3D IFT_ETHER) + if (p->if_data.ifi_type !=3D IFT_ETHER && + p->if_data.ifi_type !=3D IFT_L2VLAN) return (EPROTONOSUPPORT); if (ifv->ifv_p) return (EBUSY); From owner-freebsd-net@FreeBSD.ORG Thu Dec 23 18:09:16 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1750316A4CE; Thu, 23 Dec 2004 18:09:16 +0000 (GMT) Received: from Ehost067.exch005intermedia.net (ehost067.exch005intermedia.net [64.78.61.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2EA343D41; Thu, 23 Dec 2004 18:09:15 +0000 (GMT) (envelope-from jbehl@fastclick.com) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 23 Dec 2004 10:09:14 -0800 Message-ID: <7632915A8F000C4FAEFCF272A880344165164F@Ehost067.exch005intermedia.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: %cpu in system - squid performance in FreeBSD 5.3 thread-index: AcTcgGtwqE5TcaCWT+CNhckTP6RbvAMmJgnA From: "Jeff Behl" To: , Subject: RE: %cpu in system - squid performance in FreeBSD 5.3 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Dec 2004 18:09:16 -0000 =20 As a follow up to the below (original message at the very bottom), I installed a load balancer in front of the machines which terminates the tcp connections from clients and opens up a few, persistent connections to each server over which requests are pipelined. In this scenario everything is copasetic: last pid: 3377; load averages: 0.12, 0.09, 0.08 up 0+17:24:53 10:02:13 31 processes: 1 running, 30 sleeping CPU states: 5.1% user, 0.0% nice, 1.8% system, 1.2% interrupt, 92.0% idle Mem: 75M Active, 187M Inact, 168M Wired, 40K Cache, 214M Buf, 1482M Free Swap: 4069M Total, 4069M Free PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 474 squid 96 0 68276K 62480K select 0 53:38 16.80% 16.80% squid 311 bind 20 0 10628K 6016K kserel 0 12:28 0.00% 0.00% named It's actually so good that one machine can now handle all traffic (around 180 Mb/s) at < %50 cpu utilization. Seems like something in the network stack is responsible for the high %system cpu util... jeff -----Original Message----- From: owner-freebsd-performance@freebsd.org [mailto:owner-freebsd-performance@freebsd.org] On Behalf Of Jeff Behl Sent: Tuesday, December 07, 2004 9:17 AM To: Sean Chittenden Cc: freebsd-performance@freebsd.org Subject: Re: %cpu in system - squid performance in FreeBSD 5.3 I upgraded to STABLE but most cpu time is still being spent in system. This system is doing ~20Mb/s total with all content being grabbed out of memory. I see similar results when running MySQL (a lot of time being spent in system) Any ideas on what updates to be on the lookout for that might help with this? Am I right in guessing that this is a SMP issue and doesn't have anything to do with AMD architecture? thx FreeBSD www2 5.3-STABLE FreeBSD 5.3-STABLE #2: Sun Dec 5 21:06:14 PST=20 2004 root@www2.cdn.sjc:/usr/obj/usr/src/sys/SMP amd64 last pid: 15702; load averages: 0.15, 0.31, 0.31 up=20 0+19:55:14 09:09:28 38 processes: 2 running, 36 sleeping CPU states: 5.4% user, 0.0% nice, 12.7% system, 3.4% interrupt, 78.4% idle Mem: 163M Active, 284M Inact, 193M Wired, 72K Cache, 214M Buf, 1245M Free Swap: 4069M Total, 4069M Free PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 486 squid 96 0 79820K 73996K CPU1 1 110:00 15.04% 15.04% squid 480 squid 96 0 75804K 70012K select 0 105:56 14.89% 14.89% squid Sean Chittenden wrote: >> but the % system time can fluctuate up to 60 at times. My question=20 >> is if this is about the type of performance I could expect, or if=20 >> people have seen better. > > > I don't know about other people, but I suspect you're running into=20 > lock contention. Try using a post 5.3 snapshot (something from > RELENG_5) since alc@ has set debug.mpsafevm=3D1, which lets many calls = > to the VM run without GIANT, which I suspect is your problem and why=20 > the system usage is all over the place. -sc > _______________________________________________ freebsd-performance@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-performance To unsubscribe, send any mail to "freebsd-performance-unsubscribe@freebsd.org" howdy, I've got a dual proc AMD64 (2gHz) FreeBSD 5.3R system running two squid processes (to take advantage of both CPUs). Each process is doing around 195 req/s, and the total bandwidth is ~40Mb/s (gig nic via bge driver). Squid is being used exclusively as a reverse proxy, with all content being served out of memory (very little disk activity). Top shows: CPU states: 16.0% user, 0.0% nice, 42.7% system, 7.6% interrupt, 33.6% idle Mem: 898M Active, 569M Inact, 179M Wired, 214M Buf, 171M Free Swap: 4069M Total, 4069M Free PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 14598 squid 108 0 463M 459M select 0 39.2H 59.96% 59.96% squid 14605 squid 105 0 421M 416M CPU0 1 38.4H 49.95% 49.95% squid but the % system time can fluctuate up to 60 at times. My question is if this is about the type of performance I could expect, or if people have seen better. I was expecting to see much better performance, seeing how everything is being served out of memory, but maybe I'm asking too much? 400 reqs/s from RAM doesn't seem like much. Is this a FreeBSD issue (anybody else with similar experience)? A majority of the cpu time being spent in system would seem to indictate such. What is all the system load? How can i tell? Any help/pointers/remarks appreciated thanks, jeff From owner-freebsd-net@FreeBSD.ORG Thu Dec 23 22:07:06 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E98AE16A4CE; Thu, 23 Dec 2004 22:07:05 +0000 (GMT) Received: from a.mail.sonic.net (a.mail.sonic.net [64.142.16.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id C067A43D46; Thu, 23 Dec 2004 22:07:05 +0000 (GMT) (envelope-from bmah@freebsd.org) Received: from tomcat.kitchenlab.org (adsl-64-142-31-107.sonic.net [64.142.31.107]) by a.mail.sonic.net (8.12.11/8.12.11) with ESMTP id iBNM759a026953 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 23 Dec 2004 14:07:05 -0800 Received: from tomcat.kitchenlab.org (localhost.kitchenlab.org [127.0.0.1]) by tomcat.kitchenlab.org (8.13.1/8.13.1) with ESMTP id iBNM72oS054217; Thu, 23 Dec 2004 14:07:02 -0800 (PST) (envelope-from bmah@freebsd.org) Received: (from bmah@localhost) by tomcat.kitchenlab.org (8.13.1/8.13.1/Submit) id iBNM72ni054216; Thu, 23 Dec 2004 14:07:02 -0800 (PST) (envelope-from bmah@freebsd.org) X-Authentication-Warning: tomcat.kitchenlab.org: bmah set sender to bmah@freebsd.org using -f From: "Bruce A. Mah" To: Andrew Heyn In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Bm+ktHMk0GQq+PpJM/UI" Date: Thu, 23 Dec 2004 14:07:01 -0800 Message-Id: <1103839621.43102.75.camel@tomcat.kitchenlab.org> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port cc: "Bruce A. Mah" cc: freebsd-net@freebsd.org Subject: Re: Quick question about the tired ipf/ipnat/"dmz"/bridge scenario X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Dec 2004 22:07:06 -0000 --=-Bm+ktHMk0GQq+PpJM/UI Content-Type: text/plain Content-Transfer-Encoding: quoted-printable If memory serves me right, Andrew Heyn wrote: > Quoting http://www.moatware.com/support/docbook/faq-bridge.html, >=20 > 10.8. Why can't hosts on a NATed interface talk to hosts on a bridged > interface? > This frequently happens when someone wants to bridge an interface to thei= r > WAN to use it as a DMZ, and wants to put all of the hosts on their LAN > interface behind a NAT. This is actually a fairly reasonable and natural > thing to want to do. Interesting. This text is part of a document that appears to be, almost verbatim, copied from the documentation from m0n0wall, a FreeBSD-based firewall package. The original is at: http://m0n0.ch/wall/docbook/ I have some thoughts about this, but they're way off-topic for this list. > The problem here is that ipnat and bridging (at least as implemented in > FreeBSD) don't play well together. Packets from the LAN to the DMZ go out > just fine, but in the other direction, it seems like the packets arriving= on > the unnumbered bridge interface don't get looked up correctly in the ipna= t > state tables. >=20 > I've managed to convince myself that solving this is Really Really Hard > (TM). The irritating thing is that there's no theoretical reason why this > should be difficult...it all comes down to implementation details. >=20 >=20 > Is there any way at all, even with kludges, to get this to work? I'd be > extremely interested if there was any to accomplish this, as specified > above. I wrote this after I implemented m0n0wall's filtered bridging feature and had about a dozen people ask me this question, which is a reasonable question to ask, but tiring after you've heard it more than about five times. :-p My memory is a bit hazy but I think the problem was ipnat doesn't know that packets arriving on the unnumbered bridge interface need to have inbound NAT stuff done to them. It would need to know or figure out that the inbound interface was in a bridging group and that one of the other interfaces in the group was the interface being used for outbound NAT packets. I bet one could probably get this to work, if they were willing to hack up IPFilter and get it to understand the bridge(4) data structures. Bruce. --=-Bm+ktHMk0GQq+PpJM/UI Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBy0GF2MoxcVugUsMRAoJJAJ90yNpqTsjvgK65R+VO7SekOek2nACdHYz7 KtxV4XZY6MedNh1B6/TykKg= =4U+H -----END PGP SIGNATURE----- --=-Bm+ktHMk0GQq+PpJM/UI-- From owner-freebsd-net@FreeBSD.ORG Fri Dec 24 07:28:37 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A859916A4CE for ; Fri, 24 Dec 2004 07:28:37 +0000 (GMT) Received: from smtp.volant.org (gate.volant.org [207.111.218.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7031143D1F for ; Fri, 24 Dec 2004 07:28:37 +0000 (GMT) (envelope-from patl+freebsd@volant.org) Received: from 64-144-229-193.client.dsl.net ([64.144.229.193] helo=[192.168.0.22]) by smtp.volant.org with asmtp (TLSv1:AES256-SHA:256) (Exim 4.34 (FreeBSD)) id 1ChjsI-000PtN-L5; Thu, 23 Dec 2004 23:28:36 -0800 Date: Thu, 23 Dec 2004 23:28:33 -0800 From: Pat Lashley To: Sangwoo Shim Message-ID: <6F8763A46466565FC3C6A260@vanvoght.phoenix.volant.org> In-Reply-To: <20041223042516.GA12667@neo.redjade.org> References: <41BFA531.90001@pldrouin.net> <20041215091257.GA79274@neo.redjade.org> <404B0D742CB7FA6E000F4FD9@vanvoght.phoenix.volant.org> <20041223042516.GA12667@neo.redjade.org> X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Scan-Signature: f5fadab1df0456825de966ddf05de0fb00a55b6c X-Spam-User: nobody X-Spam-Score: -4.9 (----) X-Spam-Score-Int: -48 X-Spam-Report: This mail has matched the spam-filter tests listed below. See http://spamassassin.org/tag/ for details about the specific tests reported. In general, the higher the number of total points, the more likely that it actually is spam. (The 'required' number of points listed below is the arbitrary number above which the message is normally considered spam.) Content analysis details: (-4.9 points total, 5.0 required) -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] cc: freebsd-net@freebsd.org Subject: Re: TCP/IP over USB X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Dec 2004 07:28:37 -0000 --On Thursday, December 23, 2004 13:25:16 +0900 Sangwoo Shim wrote: > On Wed, Dec 22, 2004 at 07:15:16PM -0800, Pat Lashley wrote: > [snip] >> >> Now that that's out of the way, Sangwoo, could you post the details >> of your dubp + ng_eiface solution? I might want to switch to that. >> >> >> -Pat > > Ah, I don't have the YOPY anymore. So I can't describe every detail. > But the outline was: > > 1. Add YOPY's device id/vendor id to USB_MATCH() of /sys/dev/usb/udbp.c. > (I cannot recall the exact values, but it can be discovered by usbdevs -v > or looking at Linux's usbnet driver's header.) Already have it from my tweaks to the if_cdce driver. For those who might be following this thread, here are the values for my YP 3700: Vendor 0x22b8 Product 0x4902 Release 0x0001 Class 0x0002 Subclass 0x0000 Protocol 0x0000 The Vendor and Product are the only values necessary for the driver; and I suspect that in this case, there's no real advantage to specifying any of the others in usbd.conf. For completeness, I would be interested in obtaining values for the YP 3500 and YP 3000. > 2. Recompile udbp.ko and kldload it. > (do 'make all install' in /sys/modules/udbp) > 3. kldload ng_eiface.ko. > 4. Create ng_eiface node and connect it to the data hook of the udbp node. > e.g. do 'ngctl mkpeer udbp0: eiface data ether' > 5. Set ngethX appropriately. (using ifconfig). > > This gave me over 400KB/s ftp connection. > You could send a PR in udbp also, I suppose? :-) Thanks, I'll give that a try after the holidays. If I wind up going that route instead of cdce, I will submit a PR with the YOPY's values. -Pat From owner-freebsd-net@FreeBSD.ORG Sat Dec 25 12:40:18 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A9A016A4CE; Sat, 25 Dec 2004 12:40:18 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A893C43D2F; Sat, 25 Dec 2004 12:40:17 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iBPCb4wv038775; Sat, 25 Dec 2004 07:37:04 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iBPCb3Ah038772; Sat, 25 Dec 2004 12:37:04 GMT (envelope-from robert@fledge.watson.org) Date: Sat, 25 Dec 2004 12:37:03 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Jeff Behl In-Reply-To: <7632915A8F000C4FAEFCF272A880344165164F@Ehost067.exch005intermedia.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org cc: freebsd-performance@freebsd.org Subject: RE: %cpu in system - squid performance in FreeBSD 5.3 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Dec 2004 12:40:18 -0000 On Thu, 23 Dec 2004, Jeff Behl wrote: > As a follow up to the below (original message at the very bottom), I > installed a load balancer in front of the machines which terminates the > tcp connections from clients and opens up a few, persistent connections > to each server over which requests are pipelined. In this scenario > everything is copasetic: I'm not very familiar with Squid's architecture, but I would anticipate that what you're seeing is that the cost of additional connections served in parallel is pretty high due to the use of processes. Specifically: if each TCP connection being served gets its own process, and there are a lot of TCP connections, you'll be doing a lot of process forking, context switching, exceeding cache sizes, etc. With just a couple of connections, even if they're doing the same "work", the overhead is much lower. Depending on how much time you're willing to invest in this, we can probably do quite a bit to diagnose where the cost is coming from and look for any specific problems or areas we could optimize. I might start by turning on kernel profiling and doing a profile dump under load. Be aware that turning on profiling uses up a lot of CPU itself, so will reduce the capacity of the system. There's probably documentation elsewhere, but the process I use to set up profiling is here: http://www.watson.org/~robert/freebsd/netperf/profile/ Note that it warns the some results may be incorrect on SMP. I think it would be useful to give it a try anyway just to see if we get something useful. The next thing that would be interesting is using mutex profiling to measure contention on mutexes. The instructions in MUTEX_PROFILING(9) are pretty decent for this purpose. On an SMP system, time spent contending a mutex in active use will be spent spinning, which means wasted CPU. You can cause the kernel to block threads instead using options NO_ADAPTIVE_MUTEXES, but measurement in the past has shown that the overhead of blocking and restarting a thread is generally higher than just spinning. It would be useful to see the output of dmesg at boot to see if any performance options are obviously out of place. Likewise, the output of a couple of stats commands while the system is active would be useful -- for example, a couple of snapshots of "systat -vmstat 1", "netstat -mb", "vmstat -i", "top -S", and "iostat". As a final question: other than CPU consumption, do you have a reliable way to measure how efficiently the system is operating -- in particular, how fast it is able to serve data? Having some sort of metric for performance can be quite useful in optimizing, as it can tell us whether we're accomplishing incremental improvements prior to performance improving to a point where the system isn't saturated. Typical forms might be some sort of web benchmark, etc. If so, it might be interesting to compare the performance of the following configurations: - UP kernel (no SMP compiled in) - SMP kernel but SMP disabled using the appropriate tunable - SMP kernel with SMP enabled Finally, I'm not sure if the box has HTT on it, and if so, if HTT is enabled, but you might want to try disabling it, as it has proven to be relatively ineffective in improving performance in the application tests I've run, while at the same time increasing operating overhead. Another variable that might be interesting to look at is net.isr.enable. To do this, you want to be running 5-STABLE rather than 5.3-RELEASE, as I merged at least one significant bug fix that affects its operation. By default, net.isr.enable is 0, meaning that all inbound network traffic is processed in the netisr thread. When this variable is set to 1, inbound network traffic will be, where possible, directly dispatched in the device driver ithread. This has a couple of impacts, but the main ones are that there are substantially fewer context switches being done, and that parallelism is possible between the netisr and each interface card. This is an experimental feature, so be on the lookout for any resulting nits. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research > > last pid: 3377; load averages: 0.12, 0.09, 0.08 > up 0+17:24:53 10:02:13 > 31 processes: 1 running, 30 sleeping > CPU states: 5.1% user, 0.0% nice, 1.8% system, 1.2% interrupt, 92.0% > idle > Mem: 75M Active, 187M Inact, 168M Wired, 40K Cache, 214M Buf, 1482M Free > Swap: 4069M Total, 4069M Free > > PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU > COMMAND > 474 squid 96 0 68276K 62480K select 0 53:38 16.80% 16.80% > squid > 311 bind 20 0 10628K 6016K kserel 0 12:28 0.00% 0.00% > named > > > > It's actually so good that one machine can now handle all traffic > (around 180 Mb/s) at < %50 cpu utilization. Seems like something in the > network stack is responsible for the high %system cpu util... > > jeff > > > -----Original Message----- > From: owner-freebsd-performance@freebsd.org > [mailto:owner-freebsd-performance@freebsd.org] On Behalf Of Jeff Behl > Sent: Tuesday, December 07, 2004 9:17 AM > To: Sean Chittenden > Cc: freebsd-performance@freebsd.org > Subject: Re: %cpu in system - squid performance in FreeBSD 5.3 > > I upgraded to STABLE but most cpu time is still being spent in system. > > This system is doing ~20Mb/s total with all content being grabbed out of > memory. I see similar results when running MySQL (a lot of time being > spent in system) > > Any ideas on what updates to be on the lookout for that might help with > this? Am I right in guessing that this is a SMP issue and doesn't have > anything to do with AMD architecture? > > thx > > > > FreeBSD www2 5.3-STABLE FreeBSD 5.3-STABLE #2: Sun Dec 5 21:06:14 PST > 2004 root@www2.cdn.sjc:/usr/obj/usr/src/sys/SMP amd64 > > > last pid: 15702; load averages: 0.15, 0.31, 0.31 up > 0+19:55:14 09:09:28 > 38 processes: 2 running, 36 sleeping > CPU states: 5.4% user, 0.0% nice, 12.7% system, 3.4% interrupt, 78.4% > idle > Mem: 163M Active, 284M Inact, 193M Wired, 72K Cache, 214M Buf, 1245M > Free > Swap: 4069M Total, 4069M Free > > PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU > COMMAND > 486 squid 96 0 79820K 73996K CPU1 1 110:00 15.04% 15.04% > squid > 480 squid 96 0 75804K 70012K select 0 105:56 14.89% 14.89% > squid > > > > > > Sean Chittenden wrote: > > >> but the % system time can fluctuate up to 60 at times. My question > >> is if this is about the type of performance I could expect, or if > >> people have seen better. > > > > > > I don't know about other people, but I suspect you're running into > > lock contention. Try using a post 5.3 snapshot (something from > > RELENG_5) since alc@ has set debug.mpsafevm=1, which lets many calls > > to the VM run without GIANT, which I suspect is your problem and why > > the system usage is all over the place. -sc > > > > _______________________________________________ > freebsd-performance@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-performance > To unsubscribe, send any mail to > "freebsd-performance-unsubscribe@freebsd.org" > > > > howdy, > > I've got a dual proc AMD64 (2gHz) FreeBSD 5.3R system running two squid > processes (to take advantage of both CPUs). Each process is doing > around 195 req/s, and the total bandwidth is ~40Mb/s (gig nic via bge > driver). Squid is being used exclusively as a reverse proxy, with all > content being served out of memory (very little disk activity). > > Top shows: > > CPU states: 16.0% user, 0.0% nice, 42.7% system, 7.6% interrupt, 33.6% > idle > Mem: 898M Active, 569M Inact, 179M Wired, 214M Buf, 171M Free > Swap: 4069M Total, 4069M Free > > PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND > 14598 squid 108 0 463M 459M select 0 39.2H 59.96% 59.96% squid > 14605 squid 105 0 421M 416M CPU0 1 38.4H 49.95% 49.95% squid > > but the % system time can fluctuate up to 60 at times. My question is > if this is about the type of performance I could expect, or if people > have seen better. I was expecting to see much better performance, > seeing how everything is being served out of memory, but maybe I'm > asking too much? 400 reqs/s from RAM doesn't seem like much. Is this a > FreeBSD issue (anybody else with similar experience)? A majority of the > cpu time being spent in system would seem to indictate such. What is > all the system load? How can i tell? > > Any help/pointers/remarks appreciated > > thanks, > jeff > _______________________________________________ > freebsd-performance@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-performance > To unsubscribe, send any mail to "freebsd-performance-unsubscribe@freebsd.org" >