From owner-freebsd-net@FreeBSD.ORG Sun Feb 8 03:20:19 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 50FB416A4CF for ; Sun, 8 Feb 2004 03:20:19 -0800 (PST) Received: from mail002.syd.optusnet.com.au (mail002.syd.optusnet.com.au [211.29.132.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B9D743D1D for ; Sun, 8 Feb 2004 03:20:18 -0800 (PST) (envelope-from tfrank@optushome.com.au) Received: from marvin.home.local (c211-28-241-189.eburwd5.vic.optusnet.com.au [211.28.241.189])i18BKFV08493; Sun, 8 Feb 2004 22:20:15 +1100 Received: by marvin.home.local (Postfix, from userid 1001) id 082253EF; Sun, 8 Feb 2004 22:20:15 +1100 (EST) Date: Sun, 8 Feb 2004 22:20:14 +1100 From: Tony Frank To: Tuc at the Beach House Message-ID: <20040208112014.GE92622@marvin.home.local> References: <200402030225.i132Pfax071987@vjofn.tucs-beachin-obx-house.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200402030225.i132Pfax071987@vjofn.tucs-beachin-obx-house.com> User-Agent: Mutt/1.4.1i cc: freebsd-net@freebsd.org cc: tuc@ttsg.com Subject: Re: Whats the best solution? 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, 08 Feb 2004 11:20:19 -0000 Hi there, On Mon, Feb 02, 2004 at 09:25:41PM -0500, Tuc at the Beach House wrote: > I want to be able to set something up where I can tunnel to a > dedicated private server I have on the global internet, and route all > my traffic through it. I want it to be the default route, and once they > hit my end server, they then can be forwarded over the rest of the global > internet. > > I need to be able to have the client be on dynamic IPs. I need some > sort of an authentication. And most of all, something easy to debug would > help. I assume your client is running FreeBSD, the suggestions below will work with other OS but the solution details will be up to you. If you have a dedicated server someplace on the internet you should be able to setup a tunnel to that server and route all your traffic through that. Some tunnel options: ipsec based vpn gre tunnel (man 4 gre) ppp over udp ipv6 tunnel (check out /usr/ports/net/freenet6) pptp (either through netgraph or ports pptpd) l2tp (ports l2tpd) Should be something to get you started, Tony From owner-freebsd-net@FreeBSD.ORG Sun Feb 8 03:39: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 4DB5916A4CE for ; Sun, 8 Feb 2004 03:39:30 -0800 (PST) Received: from mail001.syd.optusnet.com.au (mail001.syd.optusnet.com.au [211.29.132.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64A3F43D1D for ; Sun, 8 Feb 2004 03:39:29 -0800 (PST) (envelope-from tfrank@optushome.com.au) Received: from marvin.home.local (c211-28-241-189.eburwd5.vic.optusnet.com.au [211.28.241.189])i18BdPr05864; Sun, 8 Feb 2004 22:39:25 +1100 Received: by marvin.home.local (Postfix, from userid 1001) id 998383DF; Sun, 8 Feb 2004 22:39:24 +1100 (EST) Date: Sun, 8 Feb 2004 22:39:24 +1100 From: Tony Frank To: Sjaak Nabuurs Message-ID: <20040208113924.GF92622@marvin.home.local> References: <010701c3ec3f$91633a80$3303a8c0@citytower> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <010701c3ec3f$91633a80$3303a8c0@citytower> User-Agent: Mutt/1.4.1i cc: freebsd-net@freebsd.org Subject: Re: Routing 4 network cards for wirless network 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, 08 Feb 2004 11:39:30 -0000 Hi there, On Fri, Feb 06, 2004 at 12:27:05AM +0100, Sjaak Nabuurs wrote: > I hoop the drawing is readable ! [... snip of drawing :) ...] > The Facts : > OS FreeBSD 5.2 (is it stable for this problem or better to use 4.x) > With 4 nic's inside Personally I use 4.9-STABLE for my home gateway. If you need a feature (or driver) only in newer release I'd start with 5.2.1. > RL0 = 192.168.0.1 > RL1 = 192.168.1.1 > RL2 = 192.168.2.1 > RL4 = 192.168.3.1 > I like to connect RL1/2/3 to RL0 (internet) > I like to have a start how to setup FreeBSD 1 I assume you are referring to 'ipfw1' as you already mentioned you have FreeBSD 5.2. > I like to use dummynet(compiled and works very nice) to manage traffic let's say > 192.168.3.1/26 100Kb/s > 192.168.3.64/26 200Kb/s > 192.168.3.128/26 300Kb/s > 192.168.3.192/26 400Kb/s > Count every user with ipfw count > > --------------------------- > #!/usr/local/bin/bash > for ((a=2; a<=254; a++)) > do > IPCOUNT = "10"$a"0 add count tcp from 192.168.3.$a to any" > ipfw $IPCOUNT > done > ---------------------------- Personally I would add these type of rules near the start of the ruleset, also will only count TCP packets this way. May want to use "count all from x to any" to match udp etc as well. You might also find it's easier to just setup the dummynet pipes and use them for accounting purpose. That's not really an area I've dealt with much so far. > Give me a good hint how to set this up with ipfw and NAT > I googled many but ther's not that much about information about 3 or more nic with freeBSD. > I think I have to use NAT, but can i use it in combination with ipfw to dummynet out/ingoing traffic over the nic RL1/2/3 > And how can i "HOME1" go accross the whole network RL0/2/3 Make your default gateway 192.168.0.138. Your easiest option is to enable NATD, make RL0 the natd interface and then review the /etc/rc.firewall script. Specifically start with the 'simple' section of the script. You will need to extend the rules to include all three 'inside' interfaces & IP ranges. You will also need to permit any 192.168.0.0/24 traffic through interface RL0. Can try looking in the freebsd-ipfw archives as well for some ideas. Personally I would recommend ipfw2 as it supports many new features. Regards, Tony From owner-freebsd-net@FreeBSD.ORG Sun Feb 8 04:39: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 1700D16A4CF for ; Sun, 8 Feb 2004 04:39:27 -0800 (PST) Received: from mail001.syd.optusnet.com.au (mail001.syd.optusnet.com.au [211.29.132.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3362443D1F for ; Sun, 8 Feb 2004 04:39:26 -0800 (PST) (envelope-from tfrank@optushome.com.au) Received: from marvin.home.local (c211-28-241-189.eburwd5.vic.optusnet.com.au [211.28.241.189])i18CdNr07130; Sun, 8 Feb 2004 23:39:23 +1100 Received: by marvin.home.local (Postfix, from userid 1001) id F23B7373; Sun, 8 Feb 2004 23:39:22 +1100 (EST) Date: Sun, 8 Feb 2004 23:39:22 +1100 From: Tony Frank To: zhangweiwu@realss.com Message-ID: <20040208123922.GG92622@marvin.home.local> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: freebsd-net@freebsd.org Subject: Re: need suggestions on making a wireless network using bluetooth. 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, 08 Feb 2004 12:39:27 -0000 Hi there, On Fri, Feb 06, 2004 at 08:56:08PM +0800, Zhang Weiwu wrote: > * the office is not very big, just as big as the bluetooth signal can > reach. There are confidential information in the office, I don't want > anyone to get my data by just stopping a car in front of the office and > listen network traffice with a notebook. Encryption is a good idea for any wireless network. I believe bluetooth has a little more in this respect over 802.11 but I do not know any sure statement whether by itself it is enough. Eg you may need to run IPSec or similar over any wireless link to secure your data. > * We already have some bluetooth devices. > * Most of us use notebook computers. Notebook 802.11 cards are more > expensive than bluetooth cards. > * Some people in the office are going to buy GPRS enabled cell phone. If > they buy bluetooth enabled GPRS phones, they can go surf the Internet > outside the office through GPRS cell phone. This is cheaper than having > both 802.11 card and GPRS card. > > So I decide I'd better use bluetooth. Several questions: > > * Is it possible to make a wireless network by using bluetooth devices? Can > I have a bluetooth installed on the FreeBSD server, let it act as a > switch/hub? Would this network be stable? > > * I never see anyone setup a network in this way, would there be many > unexpected problems? Refer to the "bluetooth" chapter in the handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-bluetooth.html (might be available in other languages too...) Certainly it appears that RFCOMM is supported which should let you do what you want, both serial (eg GPRS) or LAN. I've not done it myself - will have to give it a try one day. Regards, Tony From owner-freebsd-net@FreeBSD.ORG Sun Feb 8 05:36:54 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 13FAD16A4CE for ; Sun, 8 Feb 2004 05:36:54 -0800 (PST) Received: from mail27.cn4e.com (unknown [218.107.207.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id D40AD43D1D for ; Sun, 8 Feb 2004 05:36:53 -0800 (PST) (envelope-from zhangweiwu@realss.com) Received: from realss.com (unknown [218.85.104.202]) by mail27.cn4e.com (WorldPost) with ESMTP id 166A07F4CB2E; Sun, 8 Feb 2004 21:56:27 +0800 (CST) Message-ID: <40263B6E.2000408@realss.com> Date: Sun, 08 Feb 2004 21:36:46 +0800 From: Zhang Weiwu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20040120 X-Accept-Language: zh-cn, en-us, en MIME-Version: 1.0 To: Tony Frank References: <20040208123922.GG92622@marvin.home.local> In-Reply-To: <20040208123922.GG92622@marvin.home.local> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: need suggestions on making a wireless network using bluetooth. 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, 08 Feb 2004 13:36:54 -0000 Tony Frank wrote: >Encryption is a good idea for any wireless network. >I believe bluetooth has a little more in this respect over 802.11 but >I do not know any sure statement whether by itself it is enough. >Eg you may need to run IPSec or similar over any wireless link to secure >your data. > > I don't mean bluetooth has better encryption ... I mean bluetooth cannot pass through walls, making it diffcult to listen network traffic outside the building:) From owner-freebsd-net@FreeBSD.ORG Mon Feb 9 00:29: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 AAE1E16A4CE; Mon, 9 Feb 2004 00:29:24 -0800 (PST) Received: from nsuncom.rz.hu-berlin.de (nsuncom.rz.hu-berlin.de [141.20.1.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B8EB43D31; Mon, 9 Feb 2004 00:29:24 -0800 (PST) (envelope-from h0444lp6@student.hu-berlin.de) Received: from localhost (localhost [127.0.0.1])i198TERq013971; Mon, 9 Feb 2004 09:29:14 +0100 (MET) Received: from nsuncom.rz.hu-berlin.de ([127.0.0.1]) by localhost (nsuncom [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13929-01; Mon, 9 Feb 2004 09:29:13 +0100 (MET) Received: from kojo (x82.rewi.hu-berlin.de [141.20.121.82]) i198GraR012535; Mon, 9 Feb 2004 09:16:57 +0100 (MET) From: "h0444lp6" To: "'Sam Leffler'" , , , Date: Mon, 9 Feb 2004 16:17:42 +0800 Message-ID: <00a101c3eee5$44a48520$5279148d@kojo> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <200402071108.09386.sam@errno.com> Importance: Normal X-Virus-Scanned: by amavisd-new at hu-berlin.de Subject: RE: Atheros Super G 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, 09 Feb 2004 08:29:24 -0000 Thanks! Will there be soon, e.g. 5.3R? -----Original Message----- From: Sam Leffler [mailto:sam@errno.com] Sent: Sunday, February 08, 2004 3:08 AM To: h0444lp6; freebsd-questions@freebsd.org; freebsd-hardware@freebsd.org; freebsd-net@freebsd.org Subject: Re: Atheros Super G On Saturday 07 February 2004 02:54 am, h0444lp6 wrote: > Dear list, > > I would like to know if the Atheros Super G chipset is supported by > 5.2-Release. > > According to Atheros.com its's the AR5004 and AR5003 chiops. > > In ath(4) I can only find reference to AR5210, AR5211, and AR5212. > No support for SuperG. Sam From owner-freebsd-net@FreeBSD.ORG Mon Feb 9 00:38: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 4D47116A4CE for ; Mon, 9 Feb 2004 00:38:50 -0800 (PST) Received: from smtp3.euronet.nl (smtp3.euronet.nl [194.134.35.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C41F43D1F for ; Mon, 9 Feb 2004 00:38:50 -0800 (PST) (envelope-from sjaak@vsm-hosting.nl) Received: from SJAAK (bmr-d8e9.mxs.adsl.euronet.nl [81.68.246.233]) by smtp3.euronet.nl (Postfix) with SMTP id 230793A08F for ; Mon, 9 Feb 2004 09:38:49 +0100 (MET) Message-ID: <03e301c3eee7$541627a0$0b68a8c0@SJAAK> From: "Sjaak Nabuurs" To: Date: Mon, 9 Feb 2004 09:33:00 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: RE: Routing 4 network cards for wireless network 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, 09 Feb 2004 08:38:50 -0000 > The Facts : > OS FreeBSD 5.2 (is it stable for this problem or better to use 4.x) > With 4 nic's inside ArGHHHHHHH I tried many ways to get FreeBSD running with 4 nic's We use Linksys wap4g and extend the poweradapter cable (4mtr) the wap54g on top of the roof. That's the reason I didn't get control over the network Sometimes it works with 2 nic's sometime 3 and I get *&%$#@#$%^&*# Put on every line a hub/switch and the nic's and FreeBSD box and works like a sun. As newbie in FreeBSD i get problems with myself what's wrong !! With natd and it's great I used 4 years Linux RH but FreeBSD is great. To all thanks Sjaak Make your default gateway 192.168.0.138. Your easiest option is to enable NATD, make RL0 the natd interface and then review the /etc/rc.firewall script. Specifically start with the 'simple' section of the script. You will need to extend the rules to include all three 'inside' interfaces & IP ranges. You will also need to permit any 192.168.0.0/24 traffic through interface RL0. Can try looking in the freebsd-ipfw archives as well for some ideas. Personally I would recommend ipfw2 as it supports many new features. Regards, Tony From owner-freebsd-net@FreeBSD.ORG Mon Feb 9 02:37:42 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 ECC0116A4CE for ; Mon, 9 Feb 2004 02:37:42 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC27543D1D for ; Mon, 9 Feb 2004 02:37:42 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id B4AD8653E6; Mon, 9 Feb 2004 10:37:41 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 18501-05-8; Mon, 9 Feb 2004 10:37:41 +0000 (GMT) Received: from saboteur.dek.spc.org (82-147-17-88.dsl.uk.rapidplay.com [82.147.17.88]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id 86BDC651FC; Mon, 9 Feb 2004 10:37:40 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id 4B51A11; Mon, 9 Feb 2004 10:37:38 +0000 (GMT) Date: Mon, 9 Feb 2004 10:37:38 +0000 From: Bruce M Simpson To: Mikhail Teterin Message-ID: <20040209103738.GJ750@saboteur.dek.spc.org> References: <200402052039.40634@misha-mx.virtual-estates.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200402052039.40634@misha-mx.virtual-estates.net> cc: Julian Elischer cc: net@FreeBSD.org Subject: Re: switching to an internal DSL modem -- natd, ipfw 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, 09 Feb 2004 10:37:43 -0000 On Thu, Feb 05, 2004 at 08:39:40PM -0500, Mikhail Teterin wrote: > Any other ATM card I should consider as an internal DSL modem? Thanks! You're likely to have better luck with an ATM25 card and an externally attached ATM25 DSL modem. I backported the idt(4) driver to 4.x for this reason but the card I purchased turned out to be an ATM155 model. http://people.freebsd.org/~bms/dump/idt/ BMS From owner-freebsd-net@FreeBSD.ORG Mon Feb 9 02:39:25 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 62EA916A4CE for ; Mon, 9 Feb 2004 02:39:25 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3201843D1D for ; Mon, 9 Feb 2004 02:39:25 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 720F7653E6; Mon, 9 Feb 2004 10:39:24 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 18501-05-11; Mon, 9 Feb 2004 10:39:24 +0000 (GMT) Received: from saboteur.dek.spc.org (82-147-17-88.dsl.uk.rapidplay.com [82.147.17.88]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id A5F19651FC; Mon, 9 Feb 2004 10:39:23 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id DA64711; Mon, 9 Feb 2004 10:39:22 +0000 (GMT) Date: Mon, 9 Feb 2004 10:39:22 +0000 From: Bruce M Simpson To: Brett Glass Message-ID: <20040209103922.GK750@saboteur.dek.spc.org> References: <200402051743.KAA25020@lariat.org> <20040207032053.K39637@odysseus.silby.com> <6.0.0.22.2.20040207234503.0527a228@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.0.0.22.2.20040207234503.0527a228@localhost> cc: net@freebsd.org Subject: Re: Support for USB Wi-Fi adapters? 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, 09 Feb 2004 10:39:25 -0000 On Sat, Feb 07, 2004 at 11:46:04PM -0700, Brett Glass wrote: > At 02:21 AM 2/7/2004, Mike Silbersack wrote: > >Apparently OpenBSD has support for the USB Prism devices now, but it has > >not been ported over here yet. > > It's interesting that it's OpenBSD and not NetBSD. I'll take a look > at their code and see how hard it would be to port it to the others. > Thank you for pointing this out! It's based on owi(4) and I found it a bit ugly... YMMV. It does make some changes to the attachment and the way the softc is laid out. BMS From owner-freebsd-net@FreeBSD.ORG Mon Feb 9 04:17:05 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 729AC16A4CE for ; Mon, 9 Feb 2004 04:17:05 -0800 (PST) Received: from mail022.syd.optusnet.com.au (mail022.syd.optusnet.com.au [211.29.132.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id E02E243D1F for ; Mon, 9 Feb 2004 04:17:03 -0800 (PST) (envelope-from tfrank@optushome.com.au) Received: from marvin.home.local (c211-28-241-189.eburwd5.vic.optusnet.com.au [211.28.241.189])i19CH0R28498; Mon, 9 Feb 2004 23:17:01 +1100 Received: by marvin.home.local (Postfix, from userid 1001) id 1EB8F331; Mon, 9 Feb 2004 23:17:00 +1100 (EST) Date: Mon, 9 Feb 2004 23:17:00 +1100 From: Tony Frank To: Zhang Weiwu Message-ID: <20040209121700.GA6585@marvin.home.local> References: <20040208123922.GG92622@marvin.home.local> <40263B6E.2000408@realss.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40263B6E.2000408@realss.com> User-Agent: Mutt/1.4.1i cc: freebsd-net@freebsd.org cc: Tony Frank Subject: Re: need suggestions on making a wireless network using bluetooth. 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, 09 Feb 2004 12:17:05 -0000 Hi, On Sun, Feb 08, 2004 at 09:36:46PM +0800, Zhang Weiwu wrote: > >Encryption is a good idea for any wireless network. > >I believe bluetooth has a little more in this respect over 802.11 but > >I do not know any sure statement whether by itself it is enough. > >Eg you may need to run IPSec or similar over any wireless link to secure > >your data. > I don't mean bluetooth has better encryption ... I mean bluetooth cannot > pass through walls, making it diffcult to listen network traffic outside > the building:) While bluetooth is primarily designed as a short-range cable replacement, it does use the same frequency range as 802.11 (2.4Ghz). I have seen bluetooth modules that can reportedly work at up to 100m. Practical experience in an office environment shows I can do LAN/dial up easily over a distance 15-20m without direct line of sight to a handset. Furthermore I have used PC to PC interfaces between offices that are 20m apart down hallways etc. The bluetooth layer2 encryption can however be tougher to crack than the WEP used in 802.11. Of course it only works if you enable it. Personally when using any fixed/wireless network for sensitive application I would use encryption at layer3 also (IPsec) at minimum. Anyway, please share your results if you do get things going well. Regards, Tony From owner-freebsd-net@FreeBSD.ORG Mon Feb 9 08:23:40 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 05F8016A4CE; Mon, 9 Feb 2004 08:23:40 -0800 (PST) Received: from tora.nunu.org (YahooBB219003182070.bbtec.net [219.3.182.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id D23FF43D1D; Mon, 9 Feb 2004 08:23:39 -0800 (PST) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from tora.nunu.org (unknown [192.168.1.2]) by tora.nunu.org (Postfix) with ESMTP id D07644ACAD; Tue, 10 Feb 2004 01:23:38 +0900 (JST) Date: Tue, 10 Feb 2004 01:23:38 +0900 Message-ID: <87ad3sgr1x.wl@tora.nunu.org> From: Hidetoshi Shimokawa To: Doug Rabson In-Reply-To: <1075800437.50848.14.camel@herring.nlsystems.com> References: <1075559223.615.9.camel@localhost> <87d68yowr7.wl@tora.nunu.org> <1075800437.50848.14.camel@herring.nlsystems.com> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 MULE XEmacs/21.4 (patch 14) (Reasonable Discussion) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: freebsd-net@freebsd.org cc: freebsd-firewire@freebsd.org cc: Dario Freni Subject: Re: Will rfc2734 be supported? 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, 09 Feb 2004 16:23:40 -0000 At Tue, 03 Feb 2004 09:27:17 +0000, Doug Rabson wrote: > > If you are interested in implementing rfc2734, you need several steps. > > > > - Implement rfc2734 encapsulation as /sys/net/if_ethersubr.c for > > ethernt. rfc2734 uses very different packet format from ethernet. > > > > - Implement generic GASP receive routin in the firewire driver. > > You need this service for multicast/broadcast packet such as an arp > > packet. > > > > - Implement if_fw.c for the interface device. > > > > Though I'm not sure it actually worked, the firewire driver for > > FreeBSD-4.0 seems to have a support for IPoFW > > See ftp://ftp.uec.ac.jp/pub/firewire/ for the patch. > > I spent a little time recently thinking about what would be needed for > this and came to similar conclusions. The most interesting part is > implementing generic GASP receive. I think the nicest way of doing that Actually, it shouldn't be hard because the stream receiving is alread implemented in if_fwe.c and all we have to do is cut-and-paste that code and tweak fw_bind to be applied not only for normal asynchronus packets but also for GASP. > would be to implement a new network protocol for firewire, allowing > userland programs to do something like: > > struct sockaddr_firewire a; > s = socket(PF_FIREWIRE, SOCK_DGRAM, 0); > a.sof_address = 0x12345000; > ...; > bind(s, &a, sizeof a); > ...; > len = recv(s, buf, sizeof buf, 0); > > Internally, this probably means arranging for all asynchronous packets > to be DMA'd directly into mbufs and would probably change the firewire > code a great deal. Still, it might be worth it to gain a familiar > socket-based user api. This sound somewhat ironic for me. As far as I heard from Kobayashi-san, he first implemented the driver socket-based. (see patches for FreeBSD-4 at ftp://ftp.uec.ac.jp/pub/firewire/) But the implemention was not accepted by some FreeBSD developpers and he rewrite the current code for FreeBSD-5 from scratch. Apart from this, please note asynchronus "stream" packets is not received by "asynchrounus" receive DMA but by "isochronous" receive DMA in OHCI. It somewhat confusing. For normal asynchronus packets, OHCI doesn't support packet-per-buffer mode and supports only buffer-fill-mode. I think we need to copy packets to mbuf or something anyway. /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html From owner-freebsd-net@FreeBSD.ORG Mon Feb 9 08:52: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 0258216A4CE for ; Mon, 9 Feb 2004 08:52:13 -0800 (PST) Received: from corbulon.video-collage.com (corbulon.video-collage.com [64.35.99.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F3BF43D31 for ; Mon, 9 Feb 2004 08:52:12 -0800 (PST) (envelope-from mi+mx@aldan.algebra.com) Received: from 250-217.customer.cloud9.net (195-11.customer.cloud9.net [168.100.195.11])i19Gq9HY017316 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 9 Feb 2004 11:52:10 -0500 (EST) (envelope-from mi+mx@aldan.algebra.com) Received: from localhost (mteterin@localhost [127.0.0.1]) i19Gprw3015658; Mon, 9 Feb 2004 11:51:54 -0500 (EST) (envelope-from mi+mx@aldan.algebra.com) From: mi+mx@aldan.algebra.com Organization: Murex N.A. To: Bruce M Simpson Date: Mon, 9 Feb 2004 11:51:53 -0500 User-Agent: KMail/1.5.4 References: <200402052039.40634@misha-mx.virtual-estates.net> <20040209103738.GJ750@saboteur.dek.spc.org> In-Reply-To: <20040209103738.GJ750@saboteur.dek.spc.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402091151.53448@misha-mx.virtual-estates.net> X-Scanned-By: MIMEDefang 2.39 cc: Julian Elischer cc: net@FreeBSD.org Subject: Re: switching to an internal DSL modem -- natd, ipfw 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, 09 Feb 2004 16:52:13 -0000 =On Thu, Feb 05, 2004 at 08:39:40PM -0500, Mikhail Teterin wrote: => Any other ATM card I should consider as an internal DSL modem? Thanks! =You're likely to have better luck with an ATM25 card and an externally =attached ATM25 DSL modem. =I backported the idt(4) driver to 4.x for this reason but the card I =purchased turned out to be an ATM155 model. Thanks, but reducing the clutter of the external devices is the whole point of my excercise :-) -mi =http://people.freebsd.org/~bms/dump/idt/ From owner-freebsd-net@FreeBSD.ORG Mon Feb 9 10:04: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 8174916A4CE for ; Mon, 9 Feb 2004 10:04:11 -0800 (PST) Received: from web40311.mail.yahoo.com (web40311.mail.yahoo.com [66.218.78.90]) by mx1.FreeBSD.org (Postfix) with SMTP id 7C05E43D1F for ; Mon, 9 Feb 2004 10:04:11 -0800 (PST) (envelope-from m_evmenkin@yahoo.com) Message-ID: <20040209180410.18522.qmail@web40311.mail.yahoo.com> Received: from [66.35.239.94] by web40311.mail.yahoo.com via HTTP; Mon, 09 Feb 2004 10:04:10 PST Date: Mon, 9 Feb 2004 10:04:10 -0800 (PST) From: Maksim Yevmenkin To: Tony Frank , Zhang Weiwu In-Reply-To: <4027C569.1080308@cw.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-bluetooth@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: need suggestions on making a wireless network using bluetooth 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, 09 Feb 2004 18:04:11 -0000 > > >Encryption is a good idea for any wireless network. > > >I believe bluetooth has a little more in this respect over 802.11 but > > >I do not know any sure statement whether by itself it is enough. > > >Eg you may need to run IPSec or similar over any wireless link to secure > > >your data. > > I don't mean bluetooth has better encryption ... I mean bluetooth cannot > > pass through walls, making it diffcult to listen network traffic outside > > the building:) > > While bluetooth is primarily designed as a short-range cable replacement, > it does use the same frequency range as 802.11 (2.4Ghz). > > I have seen bluetooth modules that can reportedly work at up to 100m. that is correct. > Practical experience in an office environment shows I can do LAN/dial up > easily over a distance 15-20m without direct line of sight to a handset. that is also correct. the range can be increased by using better antenna and increased power. > The bluetooth layer2 encryption can however be tougher to crack than the > WEP used in 802.11. Of course it only works if you enable it. personally, i do not think bluetooth link encryption would be harder to break then say WEP. i do not think that anyone actually looked into this. i recall an article about flaws in bluetooth link encryption but i can not find the link at the moment. as far as i know no one found/published the way to put of the shelf bluetooth device into monitor/promiscuous mode as one can do with prism based 802.11 cards (this statement *doesn't* mean that it cannot be done). that is the only thing that is preventing anyone from snooping on bluetooth network. i did mentioned bluetooth scanners/protocol analyzers in my previous email. have a look at http://www.palowireless.com/bluetooth/testequip.asp if (when) bluetooth gains more popularity as 802.11 then someone will find a cheap and easy way to snoop on bluetooth network. there is nothing you can do about it. > Personally when using any fixed/wireless network for sensitive > application I would use encryption at layer3 also (IPsec) at minimum. again i agree. i have one thing to say though. if someone really wants to get your data, he/she will. one way or another. there is still a human factor. you still need to communicate with the rest of the world using public internet etc. thanks, max __________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html From owner-freebsd-net@FreeBSD.ORG Mon Feb 9 10:20:59 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 45B7816A4CE for ; Mon, 9 Feb 2004 10:20:59 -0800 (PST) Received: from lariat.org (lariat.org [63.229.157.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id D054F43D31 for ; Mon, 9 Feb 2004 10:20:58 -0800 (PST) (envelope-from brett@lariat.org) Received: from runaround.lariat.org (IDENT:ppp1000.lariat.org@lariat.org [63.229.157.2]) by lariat.org (8.9.3/8.9.3) with ESMTP id LAA02114; Mon, 9 Feb 2004 11:20:51 -0700 (MST) X-message-flag: Warning! Use of Microsoft Outlook renders your system susceptible to Internet worms. Message-Id: <6.0.0.22.2.20040209103829.058d2368@localhost> X-Sender: brett@localhost (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Mon, 09 Feb 2004 10:40:58 -0700 To: Bruce M Simpson From: Brett Glass In-Reply-To: <20040209103922.GK750@saboteur.dek.spc.org> References: <200402051743.KAA25020@lariat.org> <20040207032053.K39637@odysseus.silby.com> <6.0.0.22.2.20040207234503.0527a228@localhost> <20040209103922.GK750@saboteur.dek.spc.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" cc: net@freebsd.org Subject: Re: Support for USB Wi-Fi adapters? 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, 09 Feb 2004 18:20:59 -0000 If it's the code in src/sys/dev/usb/if_wi_usb.{c,h}, it looks pretty portable. However, I haven't done driver development for FreeBSD in awhile, and I'm not familiar with the new macros or the architecture which allows one to stack "buses." Is there a good resource on driver development that would give me a head start? --Brett At 03:39 AM 2/9/2004, Bruce M Simpson wrote: >On Sat, Feb 07, 2004 at 11:46:04PM -0700, Brett Glass wrote: >> At 02:21 AM 2/7/2004, Mike Silbersack wrote: >> >Apparently OpenBSD has support for the USB Prism devices now, but it has >> >not been ported over here yet. >> >> It's interesting that it's OpenBSD and not NetBSD. I'll take a look >> at their code and see how hard it would be to port it to the others. >> Thank you for pointing this out! > >It's based on owi(4) and I found it a bit ugly... YMMV. It does make some >changes to the attachment and the way the softc is laid out. > >BMS From owner-freebsd-net@FreeBSD.ORG Mon Feb 9 11:01: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 30D5916A4E0 for ; Mon, 9 Feb 2004 11:01:37 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17FDF43D1D for ; Mon, 9 Feb 2004 11:01:37 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.10/8.12.10) with ESMTP id i19J1abv083112 for ; Mon, 9 Feb 2004 11:01:36 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i19J1aiD083106 for freebsd-net@freebsd.org; Mon, 9 Feb 2004 11:01:36 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 9 Feb 2004 11:01:36 -0800 (PST) Message-Id: <200402091901.i19J1aiD083106@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, 09 Feb 2004 19:01:37 -0000 Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/07/11] kern/54383 net NFS root configurations without dynamic p 1 problem total. From owner-freebsd-net@FreeBSD.ORG Mon Feb 9 16:45: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 1E21E16A4D1 for ; Mon, 9 Feb 2004 16:45:24 -0800 (PST) Received: from mail.valuehost.co.uk (mail.valuehost.co.uk [62.25.99.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 5A65B43D1D for ; Mon, 9 Feb 2004 16:45:23 -0800 (PST) (envelope-from bjorn@eikeland.info) Received: (qmail 16310 invoked by uid 89); 10 Feb 2004 00:45:06 +0000 Received: from unknown (HELO beer.eikeland.info) (bjorn@eikeland.info@80.202.106.8) by mail.valuehost.co.uk with SMTP; 10 Feb 2004 00:45:06 +0000 Date: Tue, 10 Feb 2004 01:43:44 +0100 To: "freebsd-net@freebsd.org" From: Bjorn Eikeland Content-Type: text/plain; format=flowed; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: User-Agent: Opera7.23/FreeBSD M2 build 518 Subject: dummynet = local taffic > 100ms - help! 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, 10 Feb 2004 00:45:24 -0000 I think I've made a mess of my attempt to shape my traffic, the traffic on my lan ip is getting delayed. (About 18ms idle and 100ms full load, load is the same as for internet traffic) Traffic to localhost and other lan hosts are not delayed, the delay only occurs from my box to my ip. I started with http://www.topfx.com/prioritizingackfreebsd.shtml as a template for my traffic shaping and have extended it a bit: DUMMYNET and HZ=10000 is in the kernel. Any suggestions what can be causing this? (I've only got the one nic, and use a adsl router for internett) thanks, Bjorn # # Traffic shaping rules # # # Define some variables (or "constants" really) # echo Setting up variables IPFW=ipfw WAN_UL_CAP=18KByte/s WAN_DL_CAP=180KByte/s LAN_NET=10.0.0.0 LAN_CIDR=24 echo WAN UPLOAD ${WAN_UL_CAP} echo WAN DOWNLOAD ${WAN_DL_CAP} echo LAN_NET ${LAN_NET} echo LAN_MASK ${LAN_MASK} echo LAN_CIDR ${LAN_CIDR} # # FLUSH old rules (< `echo y` answers yes) # echo Flushing rules ${IPFW} flush < `echo y` # # TRAFFIC SHAPING: # # Make packets exiting dummynet not continue down the chain # If this is not enabled, then packets leaving an early # queue might enter a later queue if the conditions for # the later queue are met, which would be completely # devastating to all the prioritizing we're doing # ${IPFW} enable one_pass # # Lopback and local net traffic # ${IPFW} pipe 1 config bw lo0 ${IPFW} pipe 2 config bw fxp0 ${IPFW} add pipe 1 all from localhost to localhost ${IPFW} add pipe 2 all from ${LAN_NET}/${LAN_CIDR} to ${LAN_NET}/${LAN_CIDR} # # WAN Pipes # echo Setting up WAN Pipes WAN_UL=3 WAN_DL=4 ${IPFW} pipe $WAN_UL config bw $WAN_UL_CAP ${IPFW} pipe $WAN_DL config bw $WAN_DL_CAP # # WAN_UL queues # echo Setting up WAN_UL Queues WAN_UL_HI=1 WAN_UL_M1=2 WAN_UL_M2=3 WAN_UL_LO=4 # Define a high-priority queue ${IPFW} queue $WAN_UL_HI config pipe $WAN_UL weight 50 # Define a medium-high-priority queues ${IPFW} queue $WAN_UL_M1 config pipe $WAN_UL weight 10 ${IPFW} queue $WAN_UL_M2 config pipe $WAN_UL weight 5 # Define a low-priority queue ${IPFW} queue $WAN_UL_LO config pipe $WAN_UL weight 1 # #Assign WAN_UL traffic to queue's # echo Assigning WAN_UL traffic # HIGH PRIORITY # Assign outgoing empty/small ACK + ICMP packets to the high-priority queue: ${IPFW} add queue $WAN_UL_HI tcp from me to not ${LAN_NET}/${LAN_CIDR} tcpflags ack iplen 0-80 ${IPFW} add queue $WAN_UL_HI icmp from me to not ${LAN_NET}/${LAN_CIDR} # MEDIUM PRIORITY # Outgoing DNS and SSH traffic to the medium-high-priority queue: ${IPFW} add queue $WAN_UL_M1 ip from me to not ${LAN_NET}/${LAN_CIDR} domain ${IPFW} add queue $WAN_UL_M1 tcp from me to not ${LAN_NET}/${LAN_CIDR} ssh,telnet,login # Outgoing http requests - possibly file uploads & mails ${IPFW} add queue $WAN_UL_M2 tcp from me to not ${LAN_NET}/${LAN_CIDR} http,https,pop3,imap,smtp # Outgoing ftp-control ${IPFW} add queue $WAN_UL_M2 ip from me to not ${LAN_NET}/${LAN_CIDR} ftp # Add gaming traffic later # LOW PRIORITY # Assign all other outgoing traffic to the low-priority queue: ${IPFW} add queue $WAN_UL_LO all from me to not ${LAN_NET}/${LAN_CIDR} # # WAN_DL queues # echo Setting up WAN_DL Queues WAN_DL_HI=5 WAN_DL_M1=6 WAN_DL_M2=7 WAN_DL_LO=8 # Define a high-priority queue ${IPFW} queue $WAN_DL_HI config pipe $WAN_DL weight 50 # Define a medium-high-priority queues ${IPFW} queue $WAN_DL_M1 config pipe $WAN_DL weight 10 ${IPFW} queue $WAN_DL_M2 config pipe $WAN_DL weight 5 # Define a low-priority queue ${IPFW} queue $WAN_DL_LO config pipe $WAN_DL weight 1 # #Assign WAN_DL traffic to queue's # echo Assigning WAN_DL traffic # HIGH PRIORITY # Assign outgoing empty/small ACK + ICMP packets to the high-priority queue: ${IPFW} add queue $WAN_DL_HI tcp from not ${LAN_NET}/${LAN_CIDR} to me tcpflags ack iplen 0-80 ${IPFW} add queue $WAN_DL_HI icmp from not ${LAN_NET}/${LAN_CIDR} to me # MEDIUM PRIORITY # Outgoing DNS and SSH traffic to the medium-high-priority queue: ${IPFW} add queue $WAN_DL_M1 ip from not ${LAN_NET}/${LAN_CIDR} to me domain ${IPFW} add queue $WAN_DL_M1 tcp from not ${LAN_NET}/${LAN_CIDR} to me ssh,telnet,login # Outgoing http requests - possibly file uploads & mails ${IPFW} add queue $WAN_DL_M2 tcp from not ${LAN_NET}/${LAN_CIDR} to me http,https,pop3,imap,smtp # Outgoing ftp-control ${IPFW} add queue $WAN_DL_M2 ip from not ${LAN_NET}/${LAN_CIDR} to me ftp # Add gaming traffic later # LOW PRIORITY # Assign all other outgoing traffic to the low-priority queue: ${IPFW} add queue $WAN_DL_LO all from not ${LAN_NET}/${LAN_CIDR} to me From owner-freebsd-net@FreeBSD.ORG Mon Feb 9 20:32:58 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 1E76216A4CE for ; Mon, 9 Feb 2004 20:32:58 -0800 (PST) Received: from mail.drunkencomputing.de (ratz.drunkencomputing.de [195.244.235.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id E63E743D39 for ; Mon, 9 Feb 2004 20:32:57 -0800 (PST) (envelope-from hscholz@raisdorf.net) Received: from localhost (localhost [127.0.0.1]) by mail.drunkencomputing.de (Postfix) with ESMTP id 2EE428B44A for ; Tue, 10 Feb 2004 05:31:48 +0100 (CET) Received: from mail.drunkencomputing.de ([127.0.0.1])port 10024) with ESMTP id 53709-09 for ; Tue, 10 Feb 2004 05:31:47 +0100 (CET) Received: from [10.0.1.2] (c-24-30-48-121.mw.client2.attbi.com [24.30.48.121]) by mail.drunkencomputing.de (Postfix) with ESMTP id A11F28B350 for ; Tue, 10 Feb 2004 05:31:41 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v612) Content-Transfer-Encoding: 7bit Message-Id: <1BEABD96-5B82-11D8-A0D4-000A95BAD088@raisdorf.net> Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-net@freebsd.org From: Hendrik Scholz Date: Mon, 9 Feb 2004 23:32:17 -0500 X-Mailer: Apple Mail (2.612) X-Virus-Scanned: by amavisd-new at drunkencomputing.de Subject: remote traceroute and ping for jails 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, 10 Feb 2004 04:32:58 -0000 Hi! I've just finished a quick hack to allow jails to indirectly execute ping and traceroute by sending commands to the FreeBSD host housing the jails. A small daemon processes the requests and sends the reply back to the clients. Just grab http://www.wormulon.net/files/FreeBSD/rsocket-HEAD.tar.gz and don't forget to modify defs.h :) 'features': - should be safe from 'hack' attempts like "traceroute 123.org;id" - IPv6 ready ... just need to add some lines - executes ping -c 4 and does not offer any way to modify parameters - works for me :) Any comments are welcome! Thanks, Hendrik -- Hendrik Scholz - hscholz@raisdorf.net - http://www.raisdorf.net/ cell phone: 404-606-5324 (US) 0160-1570-272 (DE) From owner-freebsd-net@FreeBSD.ORG Mon Feb 9 22:26: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 B0A8D16A4CE for ; Mon, 9 Feb 2004 22:26:32 -0800 (PST) Received: from smtp.netli.com (ip2-pal-focal.netli.com [66.243.52.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88E0443D1F for ; Mon, 9 Feb 2004 22:26:32 -0800 (PST) (envelope-from vlm@netli.com) Received: (qmail 1716 invoked by uid 84); 10 Feb 2004 06:26:33 -0000 Received: from vlm@netli.com by l3-1 with qmail-scanner-0.96 (uvscan: v4.1.40/v4121. . Clean. Processed in 0.164052 secs); 10 Feb 2004 06:26:33 -0000 Received: from unknown (HELO netli.com) (172.17.1.12) by mx01-pal-lan.netli.lan with SMTP; 10 Feb 2004 06:26:32 -0000 Message-ID: <402879D6.70401@netli.com> Date: Mon, 09 Feb 2004 22:27:34 -0800 From: Lev Walkin Organization: Netli, Inc. User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031019 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: Hendrik Scholz References: <1BEABD96-5B82-11D8-A0D4-000A95BAD088@raisdorf.net> In-Reply-To: <1BEABD96-5B82-11D8-A0D4-000A95BAD088@raisdorf.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: remote traceroute and ping for jails 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, 10 Feb 2004 06:26:32 -0000 Hendrik Scholz wrote: > Hi! > > I've just finished a quick hack to allow jails to indirectly execute ping > and traceroute by sending commands to the FreeBSD host housing the jails. > A small daemon processes the requests and sends the reply back to the > clients. > > Just grab http://www.wormulon.net/files/FreeBSD/rsocket-HEAD.tar.gz > and don't forget to modify defs.h :) > > 'features': > > - should be safe from 'hack' attempts like "traceroute 123.org;id" > - IPv6 ready ... just need to add some lines > - executes ping -c 4 and does not offer any way to modify parameters > - works for me :) > > Any comments are welcome! === cut === /* dissect into type and parameter */ param = strstr(buf, " "); if ((param != NULL) || (strstr(param, " ") != NULL)) { *param = '\0'; param++; param[strlen(param)-2] = '\0'; === cut === Suppose the buffer holds the following data: " ". param=strstr(buf, " "); will pass. param!=NULL will yield true *param++ = 0 will put \0 instead of the space. strlen(param) will yield 0. param[-2] = '\0' will write zero into... into... something... throw it off and rewirite anew. -- Lev Walkin vlm@netli.com From owner-freebsd-net@FreeBSD.ORG Tue Feb 10 00:32: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 7291E16A4CE; Tue, 10 Feb 2004 00:32:32 -0800 (PST) Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34AB543D1D; Tue, 10 Feb 2004 00:32:32 -0800 (PST) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=danny) by cs.huji.ac.il with esmtp id 1AqTJk-0009aT-Ea; Tue, 10 Feb 2004 10:32:28 +0200 X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Feb 2004 10:32:28 +0200 From: Danny Braniss Message-Id: cc: freebsd-net@freebsd.org Subject: TTCP/RFC1644 problem 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, 10 Feb 2004 08:32:32 -0000 hi, im running some experiments, and it seems to me that setting net.inet.tcp.rfc1644 has the reverse effect. with sysctl net.inet.tcp.rfc1644 = 0, the transaction uses only 6 packets and it's less than 1 sec, setting net.inet.tcp.rfc1644 to 1 uses 8 packets and takes more than 1 sec. with net.inet.tcp.rfc1644 = 0: No. Time Source Destination Protocol Info 1 0.000000 132.65.80.32 132.65.16.103 TCP 4105 > 255 [SYN] Seq=3300562868 Ack=0 Win=57920 Len=0 2 0.000038 132.65.16.103 132.65.80.32 TCP 255 > 4105 [SYN, ACK] Seq=3867169834 Ack=3300562869 Win=57344 Len=0 3 0.003137 132.65.80.32 132.65.16.103 TCP 4105 > 255 [FIN, PSH, ACK] Seq=3300562869 Ack=3867169835 Win=57920 Len=25 4 0.003215 132.65.16.103 132.65.80.32 TCP 255 > 4105 [ACK] Seq=3867169835 Ack=3300562895 Win=57895 Len=0 5 0.035350 132.65.16.103 132.65.80.32 TCP 255 > 4105 [FIN, PSH, ACK] Seq=3867169835 Ack=3300562895 Win=57920 Len=4 6 0.038110 132.65.80.32 132.65.16.103 TCP 4105 > 255 [ACK] Seq=3300562895 Ack=3867169840 Win=57916 Len=0 with net.inet.tcp.rfc1644 = 1: No. Time Source Destination Protocol Info 1 0.000000 132.65.80.32 132.65.16.103 TCP 4108 > 255 [FIN, SYN, PSH] Seq=967743282 Ack=0 Win=57600 Len=25 2 0.000036 132.65.16.103 132.65.80.32 TCP 255 > 4108 [SYN, ACK] Seq=99082279 Ack=967743283 Win=57344 Len=0 3 0.002622 132.65.80.32 132.65.16.103 TCP 4108 > 255 [FIN, ACK] Seq=967743308 Ack=99082280 Win=57920 Len=0 4 0.002671 132.65.16.103 132.65.80.32 TCP 255 > 4108 [ACK] Seq=99082280 Ack=967743283 Win=57920 Len=0 5 1.201556 132.65.80.32 132.65.16.103 TCP 4108 > 255 [FIN, PSH, ACK] Seq=967743283 Ack=99082280 Win=57920 Len=25 6 1.201609 132.65.16.103 132.65.80.32 TCP 255 > 4108 [ACK] Seq=99082280 Ack=967743309 Win=57895 Len=0 7 1.227906 132.65.16.103 132.65.80.32 TCP 255 > 4108 [FIN, PSH, ACK] Seq=99082280 Ack=967743309 Win=57920 Len=4 8 1.230653 132.65.80.32 132.65.16.103 TCP 4108 > 255 [ACK] Seq=967743309 Ack=99082285 Win=57916 Len=0 From owner-freebsd-net@FreeBSD.ORG Tue Feb 10 00:56:54 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 6A53016A4CE for ; Tue, 10 Feb 2004 00:56:54 -0800 (PST) Received: from pd3mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5ED9D43D1D for ; Tue, 10 Feb 2004 00:56:54 -0800 (PST) (envelope-from colin.percival@wadham.ox.ac.uk) Received: from pd4mr1so.prod.shaw.ca (pd4mr1so-qfe3.prod.shaw.ca [10.0.141.212]) by l-daemon (iPlanet Messaging Server 5.2 HotFix 1.18 (built Jul 28 2003)) with ESMTP id <0HSV000L921UE5@l-daemon> for freebsd-net@freebsd.org; Tue, 10 Feb 2004 01:53:54 -0700 (MST) Received: from pn2ml1so.prod.shaw.ca (pn2ml1so-qfe0.prod.shaw.ca [10.0.121.145]) by l-daemon (iPlanet Messaging Server 5.2 HotFix 1.18 (built Jul 28 2003)) with ESMTP id <0HSV00F1921UKE@l-daemon> for freebsd-net@freebsd.org; Tue, 10 Feb 2004 01:53:55 -0700 (MST) Received: from piii600.wadham.ox.ac.uk ([24.87.233.42]) by l-daemon (iPlanet Messaging Server 5.2 HotFix 1.18 (built Jul 28 2003)) with ESMTP id <0HSV0063721S70@l-daemon> for freebsd-net@freebsd.org; Tue, 10 Feb 2004 01:53:54 -0700 (MST) Date: Tue, 10 Feb 2004 08:53:19 +0000 From: Colin Percival In-reply-to: X-Sender: cperciva@imap.sfu.ca (Unverified) To: Danny Braniss Message-id: <6.0.1.1.1.20040210084851.03805a78@imap.sfu.ca> MIME-version: 1.0 X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT References: cc: freebsd-net@freebsd.org Subject: Re: TTCP/RFC1644 problem 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, 10 Feb 2004 08:56:54 -0000 At 08:32 10/02/2004, you wrote: >with sysctl net.inet.tcp.rfc1644 = 0, the transaction uses only 6 packets >and it's less than 1 sec, setting net.inet.tcp.rfc1644 to 1 uses >8 packets and takes more than 1 sec. > >with net.inet.tcp.rfc1644 = 1: > No. Time Source Destination Protocol Info > 1 > 0.000000 132.65.80.32 132.65.16.103 TCP 4108 > > 255 [FIN, SYN, PSH] Seq=967743282 Ack=0 Win=57600 Len=25 132.65.80.32 -> 132.65.16.103: "I'm trying to use TTCP. Here's my request." > 2 > 0.000036 132.65.16.103 132.65.80.32 TCP 255 > >4108 [SYN, ACK] Seq=99082279 Ack=967743283 Win=57344 Len=0 132.65.16.103 -> 132.65.80.32: "Uh, hello. I don't know what TTCP is, could you try saying something I understand?" Whereupon 132.65.80.32 reverts to normal behaviour, and uses the same 6 packets as it would if TTCP were disabled. Colin Percival From owner-freebsd-net@FreeBSD.ORG Tue Feb 10 01:26: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 C6FE616A4D1 for ; Tue, 10 Feb 2004 01:26:44 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id F07DD43D1D for ; Tue, 10 Feb 2004 01:26:43 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 2629 invoked from network); 10 Feb 2004 09:26:42 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.47]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 10 Feb 2004 09:26:42 -0000 Message-ID: <4028A3EA.1050405@freebsd.org> Date: Tue, 10 Feb 2004 10:27:06 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7a) Gecko/20040125 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Danny Braniss References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: TTCP/RFC1644 problem 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, 10 Feb 2004 09:26:45 -0000 Danny Braniss wrote: > hi, > im running some experiments, and it seems to me that > setting net.inet.tcp.rfc1644 has the reverse effect. > with sysctl net.inet.tcp.rfc1644 = 0, the transaction uses only 6 packets > and it's less than 1 sec, setting net.inet.tcp.rfc1644 to 1 uses > 8 packets and takes more than 1 sec. The first tcp session in an TTCP connection doesn't gain anything, only subsequent session can go faster. You see in the second case that it tries to send data in the packet which is not ACKed for the first connection and has to be retransmitted. You should check out the second and third connection to the server and look how they behave. Did you enable rfc1644 on server and client? -- Andre > with net.inet.tcp.rfc1644 = 0: > No. Time Source Destination Protocol Info > 1 0.000000 132.65.80.32 132.65.16.103 TCP 4105 > > 255 [SYN] Seq=3300562868 Ack=0 Win=57920 Len=0 > 2 0.000038 132.65.16.103 132.65.80.32 TCP 255 > > 4105 [SYN, ACK] Seq=3867169834 Ack=3300562869 Win=57344 Len=0 > 3 0.003137 132.65.80.32 132.65.16.103 TCP 4105 > > 255 [FIN, PSH, ACK] Seq=3300562869 Ack=3867169835 Win=57920 Len=25 > 4 0.003215 132.65.16.103 132.65.80.32 TCP 255 > > 4105 [ACK] Seq=3867169835 Ack=3300562895 Win=57895 Len=0 > 5 0.035350 132.65.16.103 132.65.80.32 TCP 255 > > 4105 [FIN, PSH, ACK] Seq=3867169835 Ack=3300562895 Win=57920 Len=4 > 6 0.038110 132.65.80.32 132.65.16.103 TCP 4105 > > 255 [ACK] Seq=3300562895 Ack=3867169840 Win=57916 Len=0 > > > with net.inet.tcp.rfc1644 = 1: > No. Time Source Destination Protocol Info > 1 0.000000 132.65.80.32 132.65.16.103 TCP 4108 > > 255 [FIN, SYN, PSH] Seq=967743282 Ack=0 Win=57600 Len=25 > 2 0.000036 132.65.16.103 132.65.80.32 TCP 255 > > 4108 [SYN, ACK] Seq=99082279 Ack=967743283 Win=57344 Len=0 > 3 0.002622 132.65.80.32 132.65.16.103 TCP 4108 > > 255 [FIN, ACK] Seq=967743308 Ack=99082280 Win=57920 Len=0 > 4 0.002671 132.65.16.103 132.65.80.32 TCP 255 > > 4108 [ACK] Seq=99082280 Ack=967743283 Win=57920 Len=0 > 5 1.201556 132.65.80.32 132.65.16.103 TCP 4108 > > 255 [FIN, PSH, ACK] Seq=967743283 Ack=99082280 Win=57920 Len=25 > 6 1.201609 132.65.16.103 132.65.80.32 TCP 255 > > 4108 [ACK] Seq=99082280 Ack=967743309 Win=57895 Len=0 > 7 1.227906 132.65.16.103 132.65.80.32 TCP 255 > > 4108 [FIN, PSH, ACK] Seq=99082280 Ack=967743309 Win=57920 Len=4 > 8 1.230653 132.65.80.32 132.65.16.103 TCP 4108 > > 255 [ACK] Seq=967743309 Ack=99082285 Win=57916 Len=0 > > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-net@FreeBSD.ORG Tue Feb 10 01:57: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 35CA616A4CF; Tue, 10 Feb 2004 01:57:45 -0800 (PST) Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC12543D2F; Tue, 10 Feb 2004 01:57:44 -0800 (PST) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=danny) by cs.huji.ac.il with esmtp id 1AqUeC-000ETG-DE; Tue, 10 Feb 2004 11:57:40 +0200 X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: Andre Oppermann In-reply-to: Your message of Tue, 10 Feb 2004 10:27:06 +0100 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Feb 2004 11:57:40 +0200 From: Danny Braniss Message-Id: cc: freebsd-net@freebsd.org Subject: Re: TTCP/RFC1644 problem 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, 10 Feb 2004 09:57:45 -0000 > Danny Braniss wrote: > > hi, > > im running some experiments, and it seems to me that > > setting net.inet.tcp.rfc1644 has the reverse effect. > > with sysctl net.inet.tcp.rfc1644 = 0, the transaction uses only 6 packets > > and it's less than 1 sec, setting net.inet.tcp.rfc1644 to 1 uses > > 8 packets and takes more than 1 sec. > > The first tcp session in an TTCP connection doesn't gain anything, only > subsequent session can go faster. > i have tried many. ( > 1), btw, your statement and what my reading of Stevens don't 'coincide' :-), but then my experiment is not working either. > You see in the second case that it tries to send data in the packet which > is not ACKed for the first connection and has to be retransmitted. > > You should check out the second and third connection to the server and > look how they behave. > > Did you enable rfc1644 on server and client? yes! what puzzels me is that with rfc1644 on on both ends it's slower than without it. from Colin's answer i assume that my client is doing the right thing, the server is not. From owner-freebsd-net@FreeBSD.ORG Tue Feb 10 02:11:19 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 D77EF16A4CE for ; Tue, 10 Feb 2004 02:11:19 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 298E943D1F for ; Tue, 10 Feb 2004 02:11:19 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 13465 invoked from network); 10 Feb 2004 10:11:18 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 10 Feb 2004 10:11:18 -0000 Message-ID: <4028AE40.E1866742@freebsd.org> Date: Tue, 10 Feb 2004 11:11:12 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Danny Braniss References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: TTCP/RFC1644 problem 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, 10 Feb 2004 10:11:20 -0000 Danny Braniss wrote: > > > Danny Braniss wrote: > > > hi, > > > im running some experiments, and it seems to me that > > > setting net.inet.tcp.rfc1644 has the reverse effect. > > > with sysctl net.inet.tcp.rfc1644 = 0, the transaction uses only 6 packets > > > and it's less than 1 sec, setting net.inet.tcp.rfc1644 to 1 uses > > > 8 packets and takes more than 1 sec. > > > > The first tcp session in an TTCP connection doesn't gain anything, only > > subsequent session can go faster. > > > > i have tried many. ( > 1), btw, your statement and what my reading of Stevens > don't 'coincide' :-), but then my experiment is not working either. > > > You see in the second case that it tries to send data in the packet which > > is not ACKed for the first connection and has to be retransmitted. > > > > You should check out the second and third connection to the server and > > look how they behave. > > > > Did you enable rfc1644 on server and client? > > yes! > > what puzzels me is that with rfc1644 on on both ends it's slower than without > it. > > from Colin's answer i assume that my client is doing the right thing, the > server > is not. I have been the last one fuzz around in the TTCP code areas. However there could be problems that were lurking there before in other code parts (syncache maybe). TTCP isn't used in production by anyone (AFAIK) and only minimally tested. What FreeBSD version are you using? -- Andre From owner-freebsd-net@FreeBSD.ORG Tue Feb 10 02:20:46 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 C623116A4CE; Tue, 10 Feb 2004 02:20:46 -0800 (PST) Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8859343D1D; Tue, 10 Feb 2004 02:20:46 -0800 (PST) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=danny) by cs.huji.ac.il with esmtp id 1AqUzs-000G9q-TH; Tue, 10 Feb 2004 12:20:05 +0200 X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: Andre Oppermann In-reply-to: Your message of Tue, 10 Feb 2004 11:11:12 +0100 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Feb 2004 12:20:04 +0200 From: Danny Braniss Message-Id: cc: freebsd-net@freebsd.org Subject: Re: TTCP/RFC1644 problem 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, 10 Feb 2004 10:20:46 -0000 > I have been the last one fuzz around in the TTCP code areas. However > there could be problems that were lurking there before in other code > parts (syncache maybe). TTCP isn't used in production by anyone (AFAIK) > and only minimally tested. ahh, that's one realy good piece of info so far. this is one more step away from 'don't judge a book by it's cover' ... reading the specs of ttcp, it seemed promising, but i guess it becomes insignificat when the world uses ssl:-) > > What FreeBSD version are you using? 4.8, 4.9 and current. and solaris(but i guess they don't do ttcp) and linux (not yet). danny From owner-freebsd-net@FreeBSD.ORG Tue Feb 10 02:46: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 931DE16A4CE for ; Tue, 10 Feb 2004 02:46:47 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id C358543D46 for ; Tue, 10 Feb 2004 02:46:46 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 22067 invoked from network); 10 Feb 2004 10:46:46 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 10 Feb 2004 10:46:46 -0000 Message-ID: <4028B68F.41DB11FD@freebsd.org> Date: Tue, 10 Feb 2004 11:46:39 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Danny Braniss References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: TTCP/RFC1644 problem 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, 10 Feb 2004 10:46:47 -0000 Danny Braniss wrote: > > > I have been the last one fuzz around in the TTCP code areas. However > > there could be problems that were lurking there before in other code > > parts (syncache maybe). TTCP isn't used in production by anyone (AFAIK) > > and only minimally tested. > ahh, that's one realy good piece of info so far. > this is one more step away from 'don't judge a book by it's cover' ... > reading the specs of ttcp, it seemed promising, but i guess it becomes > insignificat when the world uses ssl:-) There are who like it and there are people who hate it. > > What FreeBSD version are you using? > > 4.8, 4.9 and current. In 4.8 and 4.9 is the legacy code. When it doesn't work between a 4.x client and server then the TTCP as such is broken. My changes (tcp hostcache) are in 5.2 for the first time. Before it it's the legacy code as well. I hope I haven't broken TTCP more than it was before. > and solaris(but i guess they don't do ttcp) and linux (not yet). Linux never will. They consider TTCP broken by design. Solaris I dont know. The problem is that TTCP will never make it mainstream or even little side stream. FreeBSD is the only BSD implementing it. Removing it would make maintainance of the tcp code a bit easier. Yet there are a couple of our FreeBSD folks emotionally attached to it (but they do not actively or even passively maintain it). -- Andre From owner-freebsd-net@FreeBSD.ORG Tue Feb 10 02:59: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 9A5DA16A4CE; Tue, 10 Feb 2004 02:59:39 -0800 (PST) Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B42A43D1D; Tue, 10 Feb 2004 02:59:39 -0800 (PST) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=danny) by cs.huji.ac.il with esmtp id 1AqVc1-000JMv-Ay; Tue, 10 Feb 2004 12:59:29 +0200 X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: Andre Oppermann In-reply-to: Your message of Tue, 10 Feb 2004 11:46:39 +0100 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Feb 2004 12:59:27 +0200 From: Danny Braniss Message-Id: cc: freebsd-net@freebsd.org Subject: Re: TTCP/RFC1644 problem 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, 10 Feb 2004 10:59:39 -0000 thanks for insight! i guess it's time to change horses :-( i was planning to use it for an application that is udp, oh well, there goes another idea down the drain. danny > Danny Braniss wrote: > > > > > I have been the last one fuzz around in the TTCP code areas. However > > > there could be problems that were lurking there before in other code > > > parts (syncache maybe). TTCP isn't used in production by anyone (AFAIK) > > > and only minimally tested. > > ahh, that's one realy good piece of info so far. > > this is one more step away from 'don't judge a book by it's cover' ... > > reading the specs of ttcp, it seemed promising, but i guess it becomes > > insignificat when the world uses ssl:-) > > There are who like it and there are people who hate it. > > > > What FreeBSD version are you using? > > > > 4.8, 4.9 and current. > > In 4.8 and 4.9 is the legacy code. When it doesn't work between a > 4.x client and server then the TTCP as such is broken. My changes > (tcp hostcache) are in 5.2 for the first time. Before it it's the > legacy code as well. I hope I haven't broken TTCP more than it was > before. > > > and solaris(but i guess they don't do ttcp) and linux (not yet). > > Linux never will. They consider TTCP broken by design. Solaris > I dont know. > > The problem is that TTCP will never make it mainstream or even > little side stream. FreeBSD is the only BSD implementing it. > Removing it would make maintainance of the tcp code a bit easier. > Yet there are a couple of our FreeBSD folks emotionally attached > to it (but they do not actively or even passively maintain it). > > -- > Andre From owner-freebsd-net@FreeBSD.ORG Tue Feb 10 03:46:54 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 24ECA16A4CE; Tue, 10 Feb 2004 03:46:54 -0800 (PST) Received: from chiark.greenend.org.uk (chiark.greenend.org.uk [193.201.200.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9CDE43D2F; Tue, 10 Feb 2004 03:46:53 -0800 (PST) (envelope-from fanf@chiark.greenend.org.uk) Received: by chiark.greenend.org.uk (Debian Exim 3.35 #1) with local id 1AqWLs-0000vQ-00; Tue, 10 Feb 2004 11:46:52 +0000 To: andre@freebsd.org From: Tony Finch In-Reply-To: <4028B68F.41DB11FD@freebsd.org> References: Message-Id: Sender: Tony Finch Date: Tue, 10 Feb 2004 11:46:52 +0000 cc: Danny Braniss cc: freebsd-net@freebsd.org Subject: Re: TTCP/RFC1644 problem 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, 10 Feb 2004 11:46:54 -0000 Andre Oppermann wrote: > >Linux never will. They consider TTCP broken by design. [...] >The problem is that TTCP will never make it mainstream or even >little side stream. FreeBSD is the only BSD implementing it. The reason for its lack of popularity is that it has significant security problems. http://tcp-impl.grc.nasa.gov/tcp-impl/list/archive/1292.html Tony. -- f.a.n.finch http://dotat.at/ SOUTH UTSIRE: SOUTHERLY OR SOUTHWESTERLY 4 OR 5, OCCASIONALLY 6 AT FIRST, BECOMING CYCLONIC FOR A TIME. OCCASIONAL RAIN. MODERATE OR GOOD. From owner-freebsd-net@FreeBSD.ORG Tue Feb 10 04:08:23 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 060B316A4CE for ; Tue, 10 Feb 2004 04:08:23 -0800 (PST) Received: from out008.verizon.net (out008pub.verizon.net [206.46.170.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6DB743D2F for ; Tue, 10 Feb 2004 04:08:22 -0800 (PST) (envelope-from cswiger@mac.com) Received: from mac.com ([68.160.202.196]) by out008.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040210120822.TPGN10003.out008.verizon.net@mac.com>; Tue, 10 Feb 2004 06:08:22 -0600 Message-ID: <4028C9A9.7090503@mac.com> Date: Tue, 10 Feb 2004 07:08:09 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bjorn Eikeland References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out008.verizon.net from [68.160.202.196] at Tue, 10 Feb 2004 06:08:21 -0600 cc: "freebsd-net@freebsd.org" Subject: Re: dummynet = local taffic > 100ms - help! 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, 10 Feb 2004 12:08:23 -0000 Bjorn Eikeland wrote: [ ... ] > DUMMYNET and HZ=10000 is in the kernel. > > Any suggestions what can be causing this? (I've only got the one nic, > and use a adsl router for internett) I seem to recall some issues with setting HZ very fast, in that it breaks the uniqueness assumptions made by TCP sequence generation if HZ > 1000. Dummynet does want better than the standard 10ms granularity (HZ=100), so perhaps you might try HZ=1000 and see whether that makes any difference. You might also consider increasing the queue length of your pipes when using prioriziation--- are you seeing packets being dropped? -- -Chuck From owner-freebsd-net@FreeBSD.ORG Tue Feb 10 05:10:35 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 B34DC16A503 for ; Tue, 10 Feb 2004 05:10:35 -0800 (PST) Received: from mail.valuehost.co.uk (mail.valuehost.co.uk [62.25.99.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 114BB43D2F for ; Tue, 10 Feb 2004 05:10:35 -0800 (PST) (envelope-from bjorn@eikeland.info) Received: (qmail 32384 invoked by uid 89); 10 Feb 2004 13:10:25 +0000 Received: from unknown (HELO beer.eikeland.info) (bjorn@eikeland.info@80.202.106.8) by mail.valuehost.co.uk with SMTP; 10 Feb 2004 13:10:25 +0000 To: Chuck Swiger References: <4028C9A9.7090503@mac.com> Message-ID: From: Bjorn Eikeland Content-Type: text/plain; format=flowed; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Date: Tue, 10 Feb 2004 14:08:57 +0100 In-Reply-To: <4028C9A9.7090503@mac.com> User-Agent: Opera7.23/FreeBSD M2 build 518 cc: "freebsd-net@freebsd.org" Subject: Re: dummynet = local taffic > 100ms - help! 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, 10 Feb 2004 13:10:35 -0000 På Tue, 10 Feb 2004 07:08:09 -0500, skrev Chuck Swiger : > Bjorn Eikeland wrote: > [ ... ] >> DUMMYNET and HZ=10000 is in the kernel. >> >> Any suggestions what can be causing this? (I've only got the one nic, >> and use a adsl router for internett) > > I seem to recall some issues with setting HZ very fast, in that it > breaks the uniqueness assumptions made by TCP sequence generation if HZ > > 1000. Dummynet does want better than the standard 10ms granularity > (HZ=100), so perhaps you might try HZ=1000 and see whether that makes > any difference. > > You might also consider increasing the queue length of your pipes when > using prioriziation--- are you seeing packets being dropped? My bad, HZ is 1000 will try queue lengts, but havent seen any packets getting dropped. Have included ping statistics below: --- localhost ping statistics --- 10 packets transmitted, 10 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.039/0.055/0.074/0.011 ms --- 10.0.0.2 ping statistics --- (My box) 10 packets transmitted, 10 packets received, 0% packet loss round-trip min/avg/max/stddev = 30.989/114.977/162.977/36.056 ms --- 10.0.0.3 ping statistics --- (Host on my LAN) 10 packets transmitted, 10 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.224/0.247/0.300/0.024 ms --- 80.202.106.8 ping statistics --- (ADSL routers public ip) 10 packets transmitted, 10 packets received, 0% packet loss round-trip min/avg/max/stddev = 18.992/54.928/88.982/21.957 ms --- www.google.akadns.net ping statistics --- 10 packets transmitted, 10 packets received, 0% packet loss round-trip min/avg/max/stddev = 103.102/140.079/189.990/24.000 ms From owner-freebsd-net@FreeBSD.ORG Tue Feb 10 05: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 3880E16A4CE for ; Tue, 10 Feb 2004 05:42:18 -0800 (PST) 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 0976343D1F for ; Tue, 10 Feb 2004 05:42:18 -0800 (PST) (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 <0HSV000F2EX7W8@ms-dienst.rz.rwth-aachen.de> for net@freebsd.org; Tue, 10 Feb 2004 14:31:55 +0100 (MET) Received: from relay.RWTH-Aachen.DE ([134.130.3.1]) by r220-1 (MailMonitor for SMTP v1.2.2 ) ; Tue, 10 Feb 2004 14:31:54 +0100 (MET) Received: from haakonia.hitnet.rwth-aachen.de (haakonia.hitnet.RWTH-Aachen.DE [137.226.181.92])i1ADVrJC009006; Tue, 10 Feb 2004 14:31:53 +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 9C9EF28418; Tue, 10 Feb 2004 14:31:53 +0100 (CET) Received: by gondor.middleearth (Postfix, from userid 1001) id C634B6102; Tue, 10 Feb 2004 14:31:52 +0100 (CET) Date: Tue, 10 Feb 2004 14:31:52 +0100 From: Christian Brueffer In-reply-to: <200402051743.KAA25020@lariat.org> To: Brett Glass Message-id: <20040210133152.GG617@unixpages.org> MIME-version: 1.0 Content-type: multipart/signed; boundary=vSsTm1kUtxIHoa7M; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-disposition: inline User-Agent: Mutt/1.5.5.1i X-Operating-System: FreeBSD 5.2-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: <200402051743.KAA25020@lariat.org> cc: net@freebsd.org Subject: Re: Support for USB Wi-Fi adapters? 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, 10 Feb 2004 13:42:18 -0000 --vSsTm1kUtxIHoa7M Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 05, 2004 at 10:43:22AM -0700, Brett Glass wrote: > What is the state of support for USB Wi-Fi adapters in FreeBSD? > Several clients have asked me if they can use these adapters on > their BSD servers, but so far I can't find one that FreeBSD > recognizes. I have one here that's based on the Atmel chipset; > it says that it's made by Askey Computers and that its device > ID is 0x123. There's a Prism-family Wi-Fi radio in there, so > it may be that it's just a matter of glue to get the existing > Prism driver to work with it. Any ideas? >=20 Stuart Walsh was working on a driver for the USB atmel for some time. However, I don't know what the current status on that one is. - 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 --vSsTm1kUtxIHoa7M Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAKN1IbHYXjKDtmC0RAhQOAKDvL2pErvYO8IOUtPGdq9i9h3pTswCgqM8m FPp6QEI8K6UBFTjiY/N5lI4= =azC+ -----END PGP SIGNATURE----- --vSsTm1kUtxIHoa7M-- From owner-freebsd-net@FreeBSD.ORG Tue Feb 10 06:02:25 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 72CB716A4CE; Tue, 10 Feb 2004 06:02:25 -0800 (PST) Received: from starburst.demon.co.uk (adsl-02-143.abel.net.uk [193.109.51.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D1A343D2F; Tue, 10 Feb 2004 06:02:24 -0800 (PST) (envelope-from richard@starburst.demon.co.uk) Received: (from richard@localhost) by starburst.demon.co.uk (8.8.7/8.8.7) id OAA02096; Tue, 10 Feb 2004 14:06:54 GMT From: Richard Wendland Message-Id: <200402101406.OAA02096@starburst.demon.co.uk> To: andre@freebsd.org (Andre Oppermann) Date: Tue, 10 Feb 2004 14:06:53 +0000 (GMT) In-Reply-To: <4028B68F.41DB11FD@freebsd.org> from "Andre Oppermann" at Feb 10, 2004 11:46:39 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: Danny Braniss cc: freebsd-net@freebsd.org Subject: Re: TTCP/RFC1644 problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: richard@wendland.org.uk List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2004 14:02:25 -0000 > My changes > (tcp hostcache) are in 5.2 for the first time. Before it it's the > legacy code as well. I hope I haven't broken TTCP more than it was > before. > > > and solaris(but i guess they don't do ttcp) and linux (not yet). > > Linux never will. They consider TTCP broken by design. Solaris > I dont know. I'm pretty sure FreeBSD is the only general-purpose OS whose TCP stack implements T/TCP. > Removing it would make maintainance of the tcp code a bit easier. If T/TCP isn't being tested in the release cycle, and it causes problems eg for hostcache, that seems to me a good reason to remove or disable it (remove net.inet.tcp.rfc1644 sysctl), despite the emotional attachment to T/TCP. We don't really want novices playing with it if the code might have become broken. RFC1644 is after all a 1994 "Experimental Protocol" that hasn't gained acceptance. The only reason I can see for keeping the code now would be as a basis for experimenting with a similar new protocol - and I'm not aware of anyone looking at that. Richard -- Richard Wendland richard@wendland.org.uk From owner-freebsd-net@FreeBSD.ORG Tue Feb 10 07:56:04 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 B57B316A4D8 for ; Tue, 10 Feb 2004 07:56:04 -0800 (PST) Received: from smtp-out3.xs4all.nl (smtp-out3.xs4all.nl [194.109.24.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40A1F43D2F for ; Tue, 10 Feb 2004 07:56:04 -0800 (PST) (envelope-from boland37@xs4all.nl) Received: from xs2.xs4all.nl (xs2.xs4all.nl [194.109.21.3]) by smtp-out3.xs4all.nl (8.12.10/8.12.10) with ESMTP id i1AFtwTL098678 for ; Tue, 10 Feb 2004 16:56:03 +0100 (CET) Received: from xs2.xs4all.nl (boland37@localhost.xs4all.nl [127.0.0.1]) by xs2.xs4all.nl (8.12.10/8.12.9) with ESMTP id i1AFsgTN081758 for ; Tue, 10 Feb 2004 16:54:42 +0100 (CET) (envelope-from boland37@xs4all.nl) Received: from localhost (boland37@localhost) by xs2.xs4all.nl (8.12.10/8.12.9/Submit) with ESMTP id i1AFsg4m081755 for ; Tue, 10 Feb 2004 16:54:42 +0100 (CET) (envelope-from boland37@xs2.xs4all.nl) Date: Tue, 10 Feb 2004 16:54:42 +0100 (CET) From: Michiel Boland To: freebsd-net@freebsd.org Message-ID: <20040210164418.B80706-100000@xs2.xs4all.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: TCP reset when the window is closed. 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, 10 Feb 2004 15:56:04 -0000 Hi. Imagine the following situation: two programs set up a TCP connection between each other and then each starts send()ing data over it without calling recv(). After a short while the receive windowss at both ends close. Now suppose that one of the two programs crashes or exits. The TCP at the other end will then receive a RST after the next window probe, or whenever it sends anything. But as far as I can see this RST is never passed on to the application because the window is closed. Therefore the other appliction will hang forever. (Unless it has some kind of application timeout.) In src/sys/netinet/tcp_input.c there is a check whether the sequence number is correct for packets with RST set. But that check does include cases where zero-sized segments are received with SEG.SEQ = RCV.NXT. These are allowed by RFC793 (page 26). Am I overlooking something here? Cheers Michiel From owner-freebsd-net@FreeBSD.ORG Tue Feb 10 09:51:17 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 3160316A4CE; Tue, 10 Feb 2004 09:51:17 -0800 (PST) Received: from mx01.ca.mci.com (mx01.ca.mci.com [142.77.2.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03AA843D2F; Tue, 10 Feb 2004 09:51:17 -0800 (PST) (envelope-from kfl@xiphos.ca) Received: from xiphos.ca (unknown [216.95.199.148]) by mx01.ca.mci.com (Postfix) with ESMTP id 6224D1012E; Tue, 10 Feb 2004 12:51:15 -0500 (EST) Message-ID: <40291C15.1090008@xiphos.ca> Date: Tue, 10 Feb 2004 12:59:49 -0500 From: Karim Fodil-Lemelin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andre Oppermann References: <4028B68F.41DB11FD@freebsd.org> In-Reply-To: <4028B68F.41DB11FD@freebsd.org> Content-Type: multipart/mixed; boundary="------------010502000903050007030202" cc: Danny Braniss cc: freebsd-net@freebsd.org Subject: Re: TTCP/RFC1644 problem 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, 10 Feb 2004 17:51:17 -0000 This is a multi-part message in MIME format. --------------010502000903050007030202 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, We actively use TTCP and we like it (www.xiplink.com). The problem is that it does not behave exactly like in Steven's book. I have sample code if you want to try it. But basically you need to set the NOPUSH flag (setsockopt()) before using sendto() _and_ in the server as well. For short duration connections over satellite links, its very useful since it can save one RTT per connections (minimum 600ms) which can be very important when dealing with thousands of connections. See attachment for example and dumps. It does have to be used carefully (with security concerns), but can still be very useful. We are currently based on 4.8 and will port to 5.x whenever it becomes stable. I for one, would be very happy if FreeBSD continues supporting T/TCP. There are systems and users out there! Here is the dump: 12:44:01.851882 192.168.27.2.1096 > 192.168.28.2.8908: SFP 919859592:919859992(400) win 65535 (DF) 12:44:01.852185 192.168.28.2.8908 > 192.168.27.2.1096: S 3400625327:3400625327(0) ack 919859994 win 65535 (DF) 12:44:01.852355 192.168.27.2.1096 > 192.168.28.2.8908: . ack 1 win 62640 (DF) 12:44:01.852472 192.168.28.2.8908 > 192.168.27.2.1096: . ack 1 win 62500 (DF) 12:44:01.852718 192.168.28.2.8908 > 192.168.27.2.1096: F 1:1(0) ack 1 win 62500 (DF) 12:44:01.852846 192.168.27.2.1096 > 192.168.28.2.8908: . ack 2 win 62640 (DF) First packet you see the SYN-FIN PUSH, then second packet it gets acked (data + SYN + FIN) then the connection closes. BTW don't mind the option 20 (opt-20) Its our implementation of SCPS-TP. Karim Xiphos Technologies. Andre Oppermann wrote: >Danny Braniss wrote: > > >>>I have been the last one fuzz around in the TTCP code areas. However >>>there could be problems that were lurking there before in other code >>>parts (syncache maybe). TTCP isn't used in production by anyone (AFAIK) >>>and only minimally tested. >>> >>> I have to disagree here :) >>ahh, that's one realy good piece of info so far. >>this is one more step away from 'don't judge a book by it's cover' ... >>reading the specs of ttcp, it seemed promising, but i guess it becomes >>insignificat when the world uses ssl:-) >> >> > >There are who like it and there are people who hate it. > > > >>>What FreeBSD version are you using? >>> >>> >>4.8, 4.9 and current. >> >> > >In 4.8 and 4.9 is the legacy code. When it doesn't work between a >4.x client and server then the TTCP as such is broken. My changes >(tcp hostcache) are in 5.2 for the first time. Before it it's the >legacy code as well. I hope I haven't broken TTCP more than it was >before. > > > > >>and solaris(but i guess they don't do ttcp) and linux (not yet). >> >> > >Linux never will. They consider TTCP broken by design. Solaris >I dont know. > >The problem is that TTCP will never make it mainstream or even >little side stream. FreeBSD is the only BSD implementing it. >Removing it would make maintainance of the tcp code a bit easier. >Yet there are a couple of our FreeBSD folks emotionally attached >to it (but they do not actively or even passively maintain it). > > > --------------010502000903050007030202 Content-Type: text/plain; name="ttcpserv.c" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ttcpserv.c" #include "cliserv.h" int read_stream (int fd, char *ptr, int maxbytes) { int nleft, nread; nleft = maxbytes; while (nleft > 0) { if ((nread = read(fd, ptr, nleft)) < 0) return (nread); /* error return < 0 */ else if (nread == 0) break; /* EOF, return #bytes read */ nleft -= nread; ptr += nread; } return (maxbytes - nleft); } int main (int argc, char *argv[]) { struct sockaddr_in serv, cli; char *request; int listenfd, sockfd, n, clilen; int One = 1; if ((listenfd = socket(PF_INET, SOCK_STREAM, 0)) < 0) { printf("socket error\n"); exit(0); } memset(&serv, sizeof(serv), 0); serv.sin_family = AF_INET; serv.sin_port = htons(TCP_SERV_PORT); serv.sin_addr.s_addr = htonl(INADDR_ANY); if (bind(listenfd, (SA)&serv, sizeof(serv)) < 0) { perror("bind error"); exit(0); } if (listen(listenfd, SOMAXCONN) < 0) { printf("listen error\n"); exit(0); } for(;;) { clilen = sizeof(cli); printf("waiting for client to connect\n"); setsockopt(listenfd, IPPROTO_TCP, TCP_NOPUSH, &One, sizeof (One)); if ((sockfd = accept(listenfd, (SA)&cli, &clilen)) < 0) { printf("accept error\n"); exit(0); } One = 0; setsockopt(sockfd, IPPROTO_TCP, TCP_NOPUSH, &One, sizeof (One)); if ((n = read(sockfd, request, REQUEST)) < 0) { printf("read error\n"); exit(0); } printf("%d\n", n); close(sockfd); } } --------------010502000903050007030202 Content-Type: text/plain; name="ttcpcli.c" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ttcpcli.c" #include #include "cliserv.h" int read_stream (int fd, char *ptr, int maxbytes) { int nleft, nread; nleft = maxbytes; while (nleft > 0) { if ((nread = read(fd, ptr, nleft)) < 0) return (nread); /* error return < 0 */ else if (nread == 0) break; /* EOF, return #bytes read */ nleft -= nread; ptr += nread; } return (maxbytes - nleft); } int main (int argc, char *argv[]) { struct sockaddr_in serv; struct hostent *host; char request[REQUEST]; uint32_t ipAddr; int sockfd, n; int eof; int One = 1; if (argc !=3) { printf("usage: ttcpcli \n"); exit(0); } sscanf(argv[2], "%d", &eof); if ((sockfd = socket(PF_INET, SOCK_STREAM, 0)) < 0) { printf("socket error\n"); exit(0); } memset(&serv, sizeof(serv), 0); serv.sin_family = AF_INET; serv.sin_port = htons(TCP_SERV_PORT); if ((ipAddr = inet_addr(argv[1])) != -1) { serv.sin_addr.s_addr = ipAddr; } else if ((host = gethostbyname(argv[1])) != NULL) { bcopy((char *)host->h_addr, (char *)&serv.sin_addr, host->h_length); } else { printf("unknown host\n"); exit(0); } /* form request */ strcpy(request, "This is a T/TCP payload"); setsockopt(sockfd, IPPROTO_TCP, TCP_NOPUSH, &One, sizeof (One)); if (eof) { if (sendto (sockfd, request, REQUEST, MSG_EOF, (SA)&serv, sizeof(serv)) != REQUEST) { printf("sendto error\n"); exit(0); } } else { if (sendto (sockfd, request, REQUEST, 0, (SA)&serv, sizeof(serv)) != REQUEST) { printf("sendto error\n"); exit(0); } } setsockopt(sockfd, IPPROTO_TCP, TCP_NOPUSH, &One, sizeof (One)); /* Normally we would receive data and do some processing */ read(sockfd, request, REQUEST); exit(0); } --------------010502000903050007030202 Content-Type: text/plain; name="cliserv.h" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="cliserv.h" #include #include #include #include #include #include #include #include #include #define SA struct sockaddr * #define REQUEST 400 #define REPLY 400 #define TCP_SERV_PORT 8908 --------------010502000903050007030202-- From owner-freebsd-net@FreeBSD.ORG Tue Feb 10 09:53: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 C2AE616A4CE; Tue, 10 Feb 2004 09:53:30 -0800 (PST) Received: from mx01.ca.mci.com (mx01.ca.mci.com [142.77.2.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7D3743D2F; Tue, 10 Feb 2004 09:53:30 -0800 (PST) (envelope-from kfl@xiphos.ca) Received: from xiphos.ca (unknown [216.95.199.148]) by mx01.ca.mci.com (Postfix) with ESMTP id 0D9B4FE0C; Tue, 10 Feb 2004 12:53:29 -0500 (EST) Message-ID: <40291C9D.5090403@xiphos.ca> Date: Tue, 10 Feb 2004 13:02:05 -0500 From: Karim Fodil-Lemelin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Danny Braniss References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: TTCP/RFC1644 problem 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, 10 Feb 2004 17:53:30 -0000 Hi, Your problem here is that your TTCP connection times out and the data is retransmitted (loosing all the benefits of TTCP) see my other email for why this happens. Karim. Danny Braniss wrote: >hi, > im running some experiments, and it seems to me that >setting net.inet.tcp.rfc1644 has the reverse effect. >with sysctl net.inet.tcp.rfc1644 = 0, the transaction uses only 6 packets >and it's less than 1 sec, setting net.inet.tcp.rfc1644 to 1 uses >8 packets and takes more than 1 sec. > >with net.inet.tcp.rfc1644 = 0: > No. Time Source Destination Protocol Info > 1 0.000000 132.65.80.32 132.65.16.103 TCP 4105 > > 255 [SYN] Seq=3300562868 Ack=0 Win=57920 Len=0 > 2 0.000038 132.65.16.103 132.65.80.32 TCP 255 > >4105 [SYN, ACK] Seq=3867169834 Ack=3300562869 Win=57344 Len=0 > 3 0.003137 132.65.80.32 132.65.16.103 TCP 4105 > > 255 [FIN, PSH, ACK] Seq=3300562869 Ack=3867169835 Win=57920 Len=25 > 4 0.003215 132.65.16.103 132.65.80.32 TCP 255 > >4105 [ACK] Seq=3867169835 Ack=3300562895 Win=57895 Len=0 > 5 0.035350 132.65.16.103 132.65.80.32 TCP 255 > >4105 [FIN, PSH, ACK] Seq=3867169835 Ack=3300562895 Win=57920 Len=4 > 6 0.038110 132.65.80.32 132.65.16.103 TCP 4105 > > 255 [ACK] Seq=3300562895 Ack=3867169840 Win=57916 Len=0 > > >with net.inet.tcp.rfc1644 = 1: > No. Time Source Destination Protocol Info > 1 0.000000 132.65.80.32 132.65.16.103 TCP 4108 > > 255 [FIN, SYN, PSH] Seq=967743282 Ack=0 Win=57600 Len=25 > 2 0.000036 132.65.16.103 132.65.80.32 TCP 255 > >4108 [SYN, ACK] Seq=99082279 Ack=967743283 Win=57344 Len=0 > 3 0.002622 132.65.80.32 132.65.16.103 TCP 4108 > > 255 [FIN, ACK] Seq=967743308 Ack=99082280 Win=57920 Len=0 > 4 0.002671 132.65.16.103 132.65.80.32 TCP 255 > >4108 [ACK] Seq=99082280 Ack=967743283 Win=57920 Len=0 > 5 1.201556 132.65.80.32 132.65.16.103 TCP 4108 > > 255 [FIN, PSH, ACK] Seq=967743283 Ack=99082280 Win=57920 Len=25 > 6 1.201609 132.65.16.103 132.65.80.32 TCP 255 > >4108 [ACK] Seq=99082280 Ack=967743309 Win=57895 Len=0 > 7 1.227906 132.65.16.103 132.65.80.32 TCP 255 > >4108 [FIN, PSH, ACK] Seq=99082280 Ack=967743309 Win=57920 Len=4 > 8 1.230653 132.65.80.32 132.65.16.103 TCP 4108 > > 255 [ACK] Seq=967743309 Ack=99082285 Win=57916 Len=0 > > > >_______________________________________________ >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 Tue Feb 10 12:13: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 D5AB216A4CE for ; Tue, 10 Feb 2004 12:13:37 -0800 (PST) Received: from lariat.org (lariat.org [63.229.157.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B9CE43D1D for ; Tue, 10 Feb 2004 12:13:37 -0800 (PST) (envelope-from brett@lariat.org) Received: from runaround.lariat.org (IDENT:ppp1000.lariat.org@lariat.org [63.229.157.2]) by lariat.org (8.9.3/8.9.3) with ESMTP id NAA24789; Tue, 10 Feb 2004 13:13:31 -0700 (MST) X-message-flag: Warning! Use of Microsoft Outlook renders your system susceptible to Internet worms. Message-Id: <6.0.0.22.2.20040210131302.05c08750@localhost> X-Sender: brett@localhost (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Tue, 10 Feb 2004 13:13:29 -0700 To: Christian Brueffer From: Brett Glass In-Reply-To: <20040210133152.GG617@unixpages.org> References: <200402051743.KAA25020@lariat.org> <20040210133152.GG617@unixpages.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" cc: net@freebsd.org Subject: Re: Support for USB Wi-Fi adapters? 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, 10 Feb 2004 20:13:37 -0000 How can I get in touch with him to see how the project is coming along? --Brett At 06:31 AM 2/10/2004, Christian Brueffer wrote: >Stuart Walsh was working on a driver for the USB atmel for some time. >However, I don't know what the current status on that one is. > >- Christian From owner-freebsd-net@FreeBSD.ORG Tue Feb 10 14:08: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 070D516A4CE for ; Tue, 10 Feb 2004 14:08:16 -0800 (PST) Received: from mail08b.verio.de (mail08b.verio.de [213.198.55.74]) by mx1.FreeBSD.org (Postfix) with SMTP id 4139543D1D for ; Tue, 10 Feb 2004 14:08:15 -0800 (PST) (envelope-from testuser1@mdolze.de) Received: from www802.verio.de (213.198.55.132) by mail08b.verio.de (RS ver 1.0.90vs) with SMTP id 3-042818888; Tue, 10 Feb 2004 23:08:08 +0100 (CET) Received: (from root@localhost) by www802.verio.de (SGI-8.12.5/8.12.5/Submit) id i1AM8Cvg11314750; Tue, 10 Feb 2004 23:08:12 +0100 (CET) Message-Id: <200402102208.i1AM8Cvg11314750@www802.verio.de> Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 From: "=?ISO-8859-1?Q?Markus Dolze?=" To: freebsd-net@freebsd.org Date: Tue, 10 Feb 2004 23:08:12 +0100 X-Mailer: AutoBahn Webmail X-Originating-Ip: 82.82.235.123 X-Loop-Detect: 1 Subject: FreeBSD's pppd and l2tpd: connection stalls X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: =?ISO-8859-1?Q?Markus Dolze?= List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2004 22:08:16 -0000 Hello, I have problems with net/l2tpd. The people at their mailing list can't help me and it seems to be a problem with pppd, so I write to the list. Situation: I'm using L2TP over IPsec to secure a wireless lan. The lan connection itself works fine. The IPsec connection works fine (transport mode). System: FreeBSD 5.2-RELEASE-p2 Problem: When I'm transfering a large file (it is *reproducable* with mozilla-source-1.6.tar.gz) transfer via ftp over the L2TP connection, the connections always stalls at the same point (number of transfered bytes). This also happens without IPSec. I had a look with ethereal at the L2TP traffic, L2TP packets are fine, but the ppp packets insist mostly of 0x00 and ethereal reports 'bad ppp content type'. The file contains a lot of 0x00 at the position the transfer stalls. L2tpd uses pppd for the ppp connection. I tried setting MRU and MTU, but that doesn't help much (the number of transfered byte grew about 100). Disabling VJ header compression seems to have positive effect, too. Questions: Are there any issues known with pppd 2.3.5? Any ideas? Can anybody verify this? Regards Markus Dolze From owner-freebsd-net@FreeBSD.ORG Tue Feb 10 17:35:36 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 0C41E16A4CE for ; Tue, 10 Feb 2004 17:35:36 -0800 (PST) Received: from ms-dienst.rz.rwth-aachen.de (ms-1.rz.RWTH-Aachen.DE [134.130.3.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0EBD43D31 for ; Tue, 10 Feb 2004 17:35:35 -0800 (PST) (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 <0HSW008Y6CFA1G@ms-dienst.rz.rwth-aachen.de> for net@freebsd.org; Wed, 11 Feb 2004 02:35:34 +0100 (MET) Received: from relay.RWTH-Aachen.DE ([134.130.3.1]) by r220-1 (MailMonitor for SMTP v1.2.2 ) ; Wed, 11 Feb 2004 02:35:33 +0100 (MET) Received: from haakonia.hitnet.rwth-aachen.de (haakonia.hitnet.RWTH-Aachen.DE [137.226.181.92])i1B1ZXJC013614; Wed, 11 Feb 2004 02:35:33 +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 BF68528418; Wed, 11 Feb 2004 02:35:32 +0100 (CET) Received: by gondor.middleearth (Postfix, from userid 1001) id 770036102; Wed, 11 Feb 2004 02:35:31 +0100 (CET) Date: Wed, 11 Feb 2004 02:35:30 +0100 From: Christian Brueffer In-reply-to: <6.0.0.22.2.20040210131302.05c08750@localhost> To: Brett Glass Message-id: <20040211013530.GH617@unixpages.org> MIME-version: 1.0 Content-type: multipart/signed; boundary=RwGu8mu1E+uYXPWP; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-disposition: inline User-Agent: Mutt/1.5.5.1i X-Operating-System: FreeBSD 5.2-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: <200402051743.KAA25020@lariat.org> <20040210133152.GG617@unixpages.org> <6.0.0.22.2.20040210131302.05c08750@localhost> cc: net@freebsd.org Subject: Re: Support for USB Wi-Fi adapters? 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, 11 Feb 2004 01:35:36 -0000 --RwGu8mu1E+uYXPWP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 10, 2004 at 01:13:29PM -0700, Brett Glass wrote: > How can I get in touch with him to see how the project is coming > along? >=20 This thread was about the driver (including his email address): http://news.gw.com/freebsd.hackers/%3C20030828132653.GD817@icecold.stu%3E - 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 --RwGu8mu1E+uYXPWP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAKYbibHYXjKDtmC0RAh3UAJ4y4sfsIVCNDUFIjzcajJroEi3t9QCeL2Ni zB+//cCadRmasi97N27nYDE= =YtrC -----END PGP SIGNATURE----- --RwGu8mu1E+uYXPWP-- From owner-freebsd-net@FreeBSD.ORG Tue Feb 10 20:13:38 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 8CC4116A4CE for ; Tue, 10 Feb 2004 20:13:38 -0800 (PST) Received: from lariat.org (lariat.org [63.229.157.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09CEE43D31 for ; Tue, 10 Feb 2004 20:13:38 -0800 (PST) (envelope-from brett@lariat.org) Received: from runaround.lariat.org (IDENT:ppp1000.lariat.org@lariat.org [63.229.157.2]) by lariat.org (8.9.3/8.9.3) with ESMTP id VAA03416; Tue, 10 Feb 2004 21:13:31 -0700 (MST) X-message-flag: Warning! Use of Microsoft Outlook renders your system susceptible to Internet worms. Message-Id: <6.0.0.22.2.20040210211320.057a1750@localhost> X-Sender: brett@localhost (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Tue, 10 Feb 2004 21:13:30 -0700 To: Christian Brueffer From: Brett Glass In-Reply-To: <20040211013530.GH617@unixpages.org> References: <200402051743.KAA25020@lariat.org> <20040210133152.GG617@unixpages.org> <6.0.0.22.2.20040210131302.05c08750@localhost> <20040211013530.GH617@unixpages.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" cc: net@freebsd.org Subject: Re: Support for USB Wi-Fi adapters? 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, 11 Feb 2004 04:13:38 -0000 Thank you! I'll e-mail him. --Brett From owner-freebsd-net@FreeBSD.ORG Wed Feb 11 01:01:28 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 00F5816A4D2 for ; Wed, 11 Feb 2004 01:01:28 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 9475F43D1F for ; Wed, 11 Feb 2004 01:01:27 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 74810 invoked from network); 11 Feb 2004 09:01:26 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 11 Feb 2004 09:01:26 -0000 X-pair-Authenticated: 209.68.2.70 Date: Wed, 11 Feb 2004 03:01:25 -0600 (CST) From: Mike Silbersack To: Chuck Swiger In-Reply-To: <4028C9A9.7090503@mac.com> Message-ID: <20040211025940.J1798@odysseus.silby.com> References: <4028C9A9.7090503@mac.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Bjorn Eikeland cc: "freebsd-net@freebsd.org" Subject: Re: dummynet = local taffic > 100ms - help! 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, 11 Feb 2004 09:01:28 -0000 On Tue, 10 Feb 2004, Chuck Swiger wrote: > I seem to recall some issues with setting HZ very fast, in that it breaks the > uniqueness assumptions made by TCP sequence generation if HZ > 1000. Dummynet > does want better than the standard 10ms granularity (HZ=100), so perhaps you > might try HZ=1000 and see whether that makes any difference. > > You might also consider increasing the queue length of your pipes when using > prioriziation--- are you seeing packets being dropped? > > -- > -Chuck It breaks TCP Timestamp generation slightly, but that's not likely to break much of anything in practice. TCP sequence numbers should be ok, but there may be overflow if you go to something > 10000... I should check one of these days. Mike "Silby" Silbersack From owner-freebsd-net@FreeBSD.ORG Wed Feb 11 02:22:35 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 C39BB16A4CE for ; Wed, 11 Feb 2004 02:22:35 -0800 (PST) Received: from mail010.syd.optusnet.com.au (mail010.syd.optusnet.com.au [211.29.132.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id E450443D1D for ; Wed, 11 Feb 2004 02:22:34 -0800 (PST) (envelope-from tfrank@optushome.com.au) Received: from marvin.home.local (c211-28-241-189.eburwd5.vic.optusnet.com.au [211.28.241.189])i1BAMRl27003; Wed, 11 Feb 2004 21:22:28 +1100 Received: by marvin.home.local (Postfix, from userid 1001) id 9DE4524D; Wed, 11 Feb 2004 21:22:26 +1100 (EST) Date: Wed, 11 Feb 2004 21:22:26 +1100 From: Tony Frank To: Bjorn Eikeland Message-ID: <20040211102226.GA25251@marvin.home.local> References: <4028C9A9.7090503@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: "freebsd-net@freebsd.org" Subject: Re: dummynet = local taffic > 100ms - help! 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, 11 Feb 2004 10:22:35 -0000 Hi, On Tue, Feb 10, 2004 at 02:08:57PM +0100, Bjorn Eikeland wrote: > >>Any suggestions what can be causing this? (I've only got the one nic, > >>and use a adsl router for internett) > >You might also consider increasing the queue length of your pipes when > >using prioriziation--- are you seeing packets being dropped? > My bad, HZ is 1000 will try queue lengts, but havent seen any packets > getting dropped. Have included ping statistics below: > > --- localhost ping statistics --- > 10 packets transmitted, 10 packets received, 0% packet loss > round-trip min/avg/max/stddev = 0.039/0.055/0.074/0.011 ms > --- 10.0.0.2 ping statistics --- (My box) > 10 packets transmitted, 10 packets received, 0% packet loss > round-trip min/avg/max/stddev = 30.989/114.977/162.977/36.056 ms > --- 10.0.0.3 ping statistics --- (Host on my LAN) > 10 packets transmitted, 10 packets received, 0% packet loss > round-trip min/avg/max/stddev = 0.224/0.247/0.300/0.024 ms > --- 80.202.106.8 ping statistics --- (ADSL routers public ip) > 10 packets transmitted, 10 packets received, 0% packet loss > round-trip min/avg/max/stddev = 18.992/54.928/88.982/21.957 ms > --- www.google.akadns.net ping statistics --- > 10 packets transmitted, 10 packets received, 0% packet loss > round-trip min/avg/max/stddev = 103.102/140.079/189.990/24.000 ms What kind of response times do you get if you disable the queues/pipes and try without? Or just add a single rule at front of rules list to allow all traffic and repeat your tests - try and confirm that the problem is with the pipes or queues... Tony From owner-freebsd-net@FreeBSD.ORG Wed Feb 11 05:30:55 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 7759F16A4CE for ; Wed, 11 Feb 2004 05:30:55 -0800 (PST) Received: from starburst.demon.co.uk (adsl-02-143.abel.net.uk [193.109.51.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88AEE43D1D for ; Wed, 11 Feb 2004 05:30:54 -0800 (PST) (envelope-from richard@starburst.demon.co.uk) Received: (from richard@localhost) by starburst.demon.co.uk (8.8.7/8.8.7) id NAA09040; Wed, 11 Feb 2004 13:35:17 GMT From: Richard Wendland Message-Id: <200402111335.NAA09040@starburst.demon.co.uk> To: silby@silby.com (Mike Silbersack) Date: Wed, 11 Feb 2004 13:35:17 +0000 (GMT) In-Reply-To: <20040211025940.J1798@odysseus.silby.com> from "Mike Silbersack" at Feb 11, 2004 03:01:25 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: Bjorn Eikeland cc: freebsd-net@freebsd.org Subject: Re: dummynet = local taffic > 100ms - help! X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: richard@wendland.org.uk List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2004 13:30:55 -0000 > It breaks TCP Timestamp generation slightly, but that's not likely to > break much of anything in practice. Well, with HZ=10000 RFC1323 TCP connections will stop after 59.7 hours, with HZ=100000 after 6 hours. For those with long running TCP connections (eg remote backup) that could be a big deal. See 4.2.3 of RFC1323. It does seem quite a few people want HZ>1000 so I think the time has come to isolate the TCP timestamp option clock from the HZ value to avoid this problem. For now they should set net.inet.tcp.rfc1323=0 to avoid breaking RFC1323. Note this doesn't affect routed packets, only TCP connections to/from that host. Tom Pavel sent some patches to this list on 14 Jan 2004 that he has been using to overcome this HZ/RFC1323 problem. Richard -- Richard Wendland richard@wendland.org.uk From owner-freebsd-net@FreeBSD.ORG Wed Feb 11 05:50:59 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 31EDA16A4CE for ; Wed, 11 Feb 2004 05:50:59 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71F6043D2F for ; Wed, 11 Feb 2004 05:50:58 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 76587 invoked from network); 11 Feb 2004 13:50:57 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 11 Feb 2004 13:50:57 -0000 Message-ID: <402A3339.1BAAF97F@freebsd.org> Date: Wed, 11 Feb 2004 14:50:49 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: richard@wendland.org.uk References: <200402111335.NAA09040@starburst.demon.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: Bjorn Eikeland cc: freebsd-net@freebsd.org Subject: Re: dummynet = local taffic > 100ms - help! 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, 11 Feb 2004 13:50:59 -0000 Richard Wendland wrote: > > > It breaks TCP Timestamp generation slightly, but that's not likely to > > break much of anything in practice. > > Well, with HZ=10000 RFC1323 TCP connections will stop after 59.7 hours, > with HZ=100000 after 6 hours. For those with long running TCP connections > (eg remote backup) that could be a big deal. See 4.2.3 of RFC1323. > > It does seem quite a few people want HZ>1000 so I think the time has > come to isolate the TCP timestamp option clock from the HZ value to > avoid this problem. For now they should set net.inet.tcp.rfc1323=0 to > avoid breaking RFC1323. > > Note this doesn't affect routed packets, only TCP connections to/from > that host. > > Tom Pavel sent some patches to this list on 14 Jan 2004 that he has been > using to overcome this HZ/RFC1323 problem. I remember some comments (by BDE?) to the effect that the patch is not entirely correct. -- Andre From owner-freebsd-net@FreeBSD.ORG Wed Feb 11 08:07: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 CE9E816A4CE for ; Wed, 11 Feb 2004 08:07:16 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 6A9E743D2F for ; Wed, 11 Feb 2004 08:07:16 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 94341 invoked from network); 11 Feb 2004 16:07:15 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 11 Feb 2004 16:07:15 -0000 X-pair-Authenticated: 209.68.2.70 Date: Wed, 11 Feb 2004 10:07:13 -0600 (CST) From: Mike Silbersack To: richard@wendland.org.uk In-Reply-To: <200402111335.NAA09040@starburst.demon.co.uk> Message-ID: <20040211100522.T1798@odysseus.silby.com> References: <200402111335.NAA09040@starburst.demon.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Bjorn Eikeland cc: freebsd-net@freebsd.org Subject: Re: dummynet = local taffic > 100ms - help! 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, 11 Feb 2004 16:07:16 -0000 On Wed, 11 Feb 2004, Richard Wendland wrote: > Well, with HZ=10000 RFC1323 TCP connections will stop after 59.7 hours, > with HZ=100000 after 6 hours. For those with long running TCP connections > (eg remote backup) that could be a big deal. See 4.2.3 of RFC1323. > > It does seem quite a few people want HZ>1000 so I think the time has > come to isolate the TCP timestamp option clock from the HZ value to > avoid this problem. For now they should set net.inet.tcp.rfc1323=0 to > avoid breaking RFC1323. > > Note this doesn't affect routed packets, only TCP connections to/from > that host. > > Tom Pavel sent some patches to this list on 14 Jan 2004 that he has been > using to overcome this HZ/RFC1323 problem. > > Richard > -- > Richard Wendland richard@wendland.org.uk I'm aware of those patches, looking at and committing them is on my to-do list. I don't have any immediate plans to work on it, although I will make sure to get it in before 5.3. Mike "Silby" Silbersack From owner-freebsd-net@FreeBSD.ORG Wed Feb 11 15:28: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 2C8F216A4CE; Wed, 11 Feb 2004 15:28:03 -0800 (PST) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84D9543D2F; Wed, 11 Feb 2004 15:28:02 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86])i1BNRvLE006320; Thu, 12 Feb 2004 10:27:57 +1100 Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) i1BNRsi1012371; Thu, 12 Feb 2004 10:27:54 +1100 Date: Thu, 12 Feb 2004 10:27:53 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Andre Oppermann In-Reply-To: <402A3339.1BAAF97F@freebsd.org> Message-ID: <20040212100815.O83287@gamplex.bde.org> References: <200402111335.NAA09040@starburst.demon.co.uk> <402A3339.1BAAF97F@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Bjorn Eikeland cc: freebsd-net@freebsd.org cc: richard@wendland.org.uk Subject: Re: dummynet = local taffic > 100ms - help! 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, 11 Feb 2004 23:28:03 -0000 On Wed, 11 Feb 2004, Andre Oppermann wrote: > Richard Wendland wrote: > > Tom Pavel sent some patches to this list on 14 Jan 2004 that he has been > > using to overcome this HZ/RFC1323 problem. > > I remember some comments (by BDE?) to the effect that the patch is not > entirely correct. It was just inelegant. There are several different tick counters already active. None are quite right, but perhaps one could be adapted. The closest to being right is the implicit one in tc_ticktock(). This defaults to a period of max(1/1000, 1/HZ) seconds but doesn't guarantee a period of > 1/1000 seconds since it can be meddled with using the kern.timecounter.tick sysctl. There is also the implicit one in sched_clock(). sched_clock() is supposed to be called every 1/128 seconds (to within a factor of 2). Bruce From owner-freebsd-net@FreeBSD.ORG Thu Feb 12 09:35:31 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 CCD4516A4CF for ; Thu, 12 Feb 2004 09:35:31 -0800 (PST) Received: from web8203.mail.in.yahoo.com (web8203.mail.in.yahoo.com [203.199.70.117]) by mx1.FreeBSD.org (Postfix) with SMTP id ED92E43D1D for ; Thu, 12 Feb 2004 09:35:30 -0800 (PST) (envelope-from manish_6983@yahoo.co.in) Message-ID: <20040212173529.93598.qmail@web8203.mail.in.yahoo.com> Received: from [203.199.146.111] by web8203.mail.in.yahoo.com via HTTP; Thu, 12 Feb 2004 17:35:29 GMT Date: Thu, 12 Feb 2004 17:35:29 +0000 (GMT) From: =?iso-8859-1?q?manish=20gautam?= To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: netgraph....help 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, 12 Feb 2004 17:35:31 -0000 i want to make my own node with my own specifications. how can i do that and load it and pass data through it. reply as soon as possible... cheers manish ________________________________________________________________________ Yahoo! India Education Special: Study in the UK now. Go to http://in.specials.yahoo.com/index1.html From owner-freebsd-net@FreeBSD.ORG Thu Feb 12 09:46:35 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 2797316A4CE for ; Thu, 12 Feb 2004 09:46:35 -0800 (PST) Received: from fiberpimp.net (true.fiberpimp.net [209.167.68.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BA4343D1D for ; Thu, 12 Feb 2004 09:46:35 -0800 (PST) (envelope-from chris@fiberpimp.net) Received: from true.fiberpimp.net (localhost.fiberpimp.net [127.0.0.1]) by fiberpimp.net (Postfix) with ESMTP id 0BD1854CA83 for ; Thu, 12 Feb 2004 12:46:35 -0500 (EST) Received: from localhost (chris@localhost)i1CHkYxW020784 for ; Thu, 12 Feb 2004 12:46:34 -0500 (EST) X-Authentication-Warning: true.fiberpimp.net: chris owned process doing -bs Date: Thu, 12 Feb 2004 12:46:34 -0500 (EST) From: Christian Malo To: freebsd-net@freebsd.org Message-ID: <20040212124452.O20756-100000@true.fiberpimp.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: NATD / ipfw 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, 12 Feb 2004 17:46:35 -0000 Hi, I setup a computer to act as a natd for our office. Everything works fine but I'm trying to tweak it a little bit to get extra speed. When I download from box itself I easily get 6 or 7 mbytes/sec. but when I do it behind the nat (office pc). I only get ~ 500k/sec. Is there a way to tweak the sysctl to get some more speed ? thanks, -chris From owner-freebsd-net@FreeBSD.ORG Thu Feb 12 10:59:31 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 E31F916A4CE for ; Thu, 12 Feb 2004 10:59:31 -0800 (PST) Received: from portia.cc.emory.edu (portia.cc.emory.edu [170.140.204.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFEB743D2F for ; Thu, 12 Feb 2004 10:59:31 -0800 (PST) (envelope-from jcchapp@emory.edu) Received: from mrhat (localhost [127.0.0.1]) by portia.cc.emory.edu (8.12.10/8.12.10) with SMTP id i1CIxOYm013608; Thu, 12 Feb 2004 13:59:24 -0500 (EST) Message-ID: <002e01c3f19a$53eb8f30$1a0aa8c0@mrhat> From: "Jonathan Chappelow" To: "Christian Malo" , References: <20040212124452.O20756-100000@true.fiberpimp.net> Date: Thu, 12 Feb 2004 13:59:22 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: Re: NATD / ipfw 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, 12 Feb 2004 18:59:32 -0000 Christian, I recall reading some problems like this on this list recently. I don't remember if there was a solution for NATd, but running IPNAT compiled into the kernel has been highly efficient for my small office. I have no problems with transfers up to 3MB/sec. Maybe higher. I have also found that ipf (IPFILTER) works very well and has a number of good features. Good Luck, Jon ----- Original Message ----- From: "Christian Malo" To: Sent: Thursday, February 12, 2004 12:46 PM Subject: NATD / ipfw > Hi, > > I setup a computer to act as a natd for our office. Everything works fine > but I'm trying to tweak it a little bit to get extra speed. > > When I download from box itself I easily get 6 or 7 mbytes/sec. but > when I do it behind the nat (office pc). I only get ~ 500k/sec. > > > Is there a way to tweak the sysctl to get some more speed ? > > > thanks, > > -chris > > > _______________________________________________ > 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 Thu Feb 12 11:31:01 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 5B34616A4CE for ; Thu, 12 Feb 2004 11:31:01 -0800 (PST) Received: from mail.numachi.com (meisai.numachi.com [198.175.254.6]) by mx1.FreeBSD.org (Postfix) with SMTP id D7BC643D2F for ; Thu, 12 Feb 2004 11:31:00 -0800 (PST) (envelope-from reichert@numachi.com) Received: (qmail 73988 invoked from network); 12 Feb 2004 19:31:00 -0000 Received: from natto.numachi.com (198.175.254.216) by meisai.numachi.com with SMTP; 12 Feb 2004 19:31:00 -0000 Received: (qmail 50520 invoked by uid 1001); 12 Feb 2004 19:30:59 -0000 Date: Thu, 12 Feb 2004 14:30:59 -0500 From: Brian Reichert To: freebsd-net@freebsd.org Message-ID: <20040212193059.GX2429@numachi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.5.1i Subject: question: source address on interface w/ aliases? 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, 12 Feb 2004 19:31:01 -0000 I've had an expectation violated recently, and wanted to research whether my expectation was grounded in reality: Given an interface with a primary IP, and one or more aliased IP addresses: When a process opens a connection to another host, which IP address will be chosen as the source address? Steven's just says 'the kernel chooses the IP address and port'. My expectation was that the primary IP address would be used. Is my expectation valid? Is there a spec that describes this, or is it up to an individual OS to do whatever it wants? (I'm sorry to pester this list, as this question isn't actually specific to FreeBSD...) I'm more than willing to do my own research, but a suggestion of useful buzzwords would be appreciated as well. :) Thanks for your time... -- Brian Reichert 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA BSD admin/developer at large From owner-freebsd-net@FreeBSD.ORG Thu Feb 12 11:35: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 928E616A4CE for ; Thu, 12 Feb 2004 11:35:13 -0800 (PST) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C12B43D1F for ; Thu, 12 Feb 2004 11:35:13 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (sccrmhc12) with ESMTP id <2004021219351101200sq127e>; Thu, 12 Feb 2004 19:35:12 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA11147; Thu, 12 Feb 2004 11:35:09 -0800 (PST) Date: Thu, 12 Feb 2004 11:35:06 -0800 (PST) From: Julian Elischer To: Brian Reichert In-Reply-To: <20040212193059.GX2429@numachi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: question: source address on interface w/ aliases? 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, 12 Feb 2004 19:35:13 -0000 On Thu, 12 Feb 2004, Brian Reichert wrote: > I've had an expectation violated recently, and wanted to research > whether my expectation was grounded in reality: > > Given an interface with a primary IP, and one or more aliased IP > addresses: > > When a process opens a connection to another host, which IP address > will be chosen as the source address? > > Steven's just says 'the kernel chooses the IP address and port'. > > My expectation was that the primary IP address would be used. The primary IP address on the interface referred to in the routing table entry that is chosen for the first packet.. (last time I looked) > > Is my expectation valid? Is there a spec that describes this, or > is it up to an individual OS to do whatever it wants? > > (I'm sorry to pester this list, as this question isn't actually > specific to FreeBSD...) > > I'm more than willing to do my own research, but a suggestion of > useful buzzwords would be appreciated as well. :) > > Thanks for your time... > > -- > Brian Reichert > 37 Crystal Ave. #303 Daytime number: (603) 434-6842 > Derry NH 03038-1713 USA BSD admin/developer at large > _______________________________________________ > 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 Thu Feb 12 11:38:57 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 A7E4616A4CE for ; Thu, 12 Feb 2004 11:38:57 -0800 (PST) Received: from web13603.mail.yahoo.com (web13603.mail.yahoo.com [216.136.175.114]) by mx1.FreeBSD.org (Postfix) with SMTP id 8C1E643D1D for ; Thu, 12 Feb 2004 11:38:57 -0800 (PST) (envelope-from g_naveen_k@yahoo.com) Message-ID: <20040212193857.58392.qmail@web13603.mail.yahoo.com> Received: from [139.85.253.184] by web13603.mail.yahoo.com via HTTP; Thu, 12 Feb 2004 11:38:57 PST Date: Thu, 12 Feb 2004 11:38:57 -0800 (PST) From: Naveen Kumar To: Brian Reichert , freebsd-net@freebsd.org In-Reply-To: <20040212193059.GX2429@numachi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: question: source address on interface w/ aliases? 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, 12 Feb 2004 19:38:57 -0000 --- Brian Reichert wrote: > I've had an expectation violated recently, and > wanted to research > whether my expectation was grounded in reality: > > Given an interface with a primary IP, and one or > more aliased IP > addresses: > > When a process opens a connection to another host, > which IP address > will be chosen as the source address? > > Steven's just says 'the kernel chooses the IP > address and port'. Dont you have to give the local ip address(either primary or aliases') when you do a bind on the socket ? If you choose INADDR_ANY I am not sure which ip address it will pick up. > > My expectation was that the primary IP address would > be used. > > Is my expectation valid? Is there a spec that > describes this, or > is it up to an individual OS to do whatever it > wants? > > (I'm sorry to pester this list, as this question > isn't actually > specific to FreeBSD...) > > I'm more than willing to do my own research, but a > suggestion of > useful buzzwords would be appreciated as well. :) > > Thanks for your time... > > -- > Brian Reichert > 37 Crystal Ave. #303 Daytime number: (603) > 434-6842 > Derry NH 03038-1713 USA BSD admin/developer at > large > _______________________________________________ > 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" __________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html From owner-freebsd-net@FreeBSD.ORG Thu Feb 12 11:41:25 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 AFB4716A4CE for ; Thu, 12 Feb 2004 11:41:25 -0800 (PST) Received: from mail.numachi.com (meisai.numachi.com [198.175.254.6]) by mx1.FreeBSD.org (Postfix) with SMTP id CCA4343D31 for ; Thu, 12 Feb 2004 11:41:24 -0800 (PST) (envelope-from reichert@numachi.com) Received: (qmail 74441 invoked from network); 12 Feb 2004 19:40:42 -0000 Received: from natto.numachi.com (198.175.254.216) by meisai.numachi.com with SMTP; 12 Feb 2004 19:40:42 -0000 Received: (qmail 50662 invoked by uid 1001); 12 Feb 2004 19:40:42 -0000 Date: Thu, 12 Feb 2004 14:40:42 -0500 From: Brian Reichert To: Julian Elischer Message-ID: <20040212194042.GZ2429@numachi.com> References: <20040212193059.GX2429@numachi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.5.1i cc: freebsd-net@freebsd.org Subject: Re: question: source address on interface w/ aliases? 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, 12 Feb 2004 19:41:25 -0000 On Thu, Feb 12, 2004 at 11:35:06AM -0800, Julian Elischer wrote: > > My expectation was that the primary IP address would be used. > > > The primary IP address on the interface referred to in the routing table > entry that is chosen for the first packet.. > (last time I looked) Such was my expectation. But: is this a BSD-specific implementation? If I catch a kernel doing otherwise, can I say 'Aha! That's a bug based on documented standards' ? -- Brian Reichert 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA BSD admin/developer at large From owner-freebsd-net@FreeBSD.ORG Thu Feb 12 13:43:00 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 76D5616A4CE for ; Thu, 12 Feb 2004 13:43:00 -0800 (PST) Received: from webmail.emre.de (webmail.emre.de [194.8.203.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38F8C43D1F for ; Thu, 12 Feb 2004 13:43:00 -0800 (PST) (envelope-from info@emre.de) Received: by webmail.emre.de (Postfix, from userid 80) id E454D3A23E; Thu, 12 Feb 2004 22:42:57 +0100 (CET) Received: from 192.168.2.2 ([192.168.2.2]) by webmail.emre.de (Horde) with HTTP for ; Thu, 12 Feb 2004 22:42:57 +0100 Message-ID: <1076622177.584b09df25514@webmail.emre.de> Date: Thu, 12 Feb 2004 22:42:57 +0100 From: Emre Bastuz To: freebsd-net@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) 4.0-cvs Subject: 4.9-STABLE heavily dropping packets? libpcap issue? 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, 12 Feb 2004 21:43:00 -0000 Hi, for sniffing purposes I have a FreeBSD 4.9-STABLE box running on highend, state-of-the-art hardware (Xeon something) with all bells and whistles. The NIC=B4s an onboard copper em0 with gig-e capabilities. Nevertheless I am getting massive packet drops (40%-60%) when I start sniffi= ng a gigabit ehthernet segment although the CPU load is very low. After doing some research in in the appropriate mailing list archives I foun= d out that there are (or were?) sometimes issues with the libpcap. As there wa= s a more current one in the ports collection (0.8.1 as opposed to 0.7 in the bas= e system) I used this instead (with LIBPCAP_OVERWRITE_BASE=3Dyes) but still I = am losing the same amount of packets when doing a tcpdump. I definitly do _not_ know what else I can do to reduce the amount of lost da= ta. *sigh* Things I did to improve the situation so far: - Update from RELEASE to 4.9-STABLE - Compile a custom kernel with reduced drivers and SMP support - Update libpcap and recompile tcpdump Does any of you have an idea else I can do? Any parameters in the kernel that can be tweeked further, like NMBCLUSTERS o= r NMBUFS? Cheers, Emre -- http://www.emre.de UIN: 561260 PGP Key ID: 0xAFAC77FD I don't see why some people even HAVE cars. -- Calvin ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From owner-freebsd-net@FreeBSD.ORG Thu Feb 12 13: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 7305716A4CE for ; Thu, 12 Feb 2004 13:53:32 -0800 (PST) Received: from magellan.palisadesys.com (magellan.palisadesys.com [192.188.162.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42D7A43D31 for ; Thu, 12 Feb 2004 13:53:32 -0800 (PST) (envelope-from ghelmer@palisadesys.com) Received: from mira (mira.palisadesys.com [192.188.162.116]) (authenticated bits=0)i1CLrTKw008474 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 12 Feb 2004 15:53:29 -0600 (CST) (envelope-from ghelmer@palisadesys.com) From: "Guy Helmer" To: "Emre Bastuz" , Date: Thu, 12 Feb 2004 15:53:27 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal In-Reply-To: <1076622177.584b09df25514@webmail.emre.de> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: RE: 4.9-STABLE heavily dropping packets? libpcap issue? 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, 12 Feb 2004 21:53:32 -0000 Emre Bastuz wrote on Thursday, February 12, 2004 3:43 PM > Hi, > > for sniffing purposes I have a FreeBSD 4.9-STABLE box running on highend, > state-of-the-art hardware (Xeon something) with all bells and whistles. > > The NICīs an onboard copper em0 with gig-e capabilities. > > Nevertheless I am getting massive packet drops (40%-60%) when I > start sniffing a > gigabit ehthernet segment although the CPU load is very low. > > After doing some research in in the appropriate mailing list > archives I found > out that there are (or were?) sometimes issues with the libpcap. > As there was a > more current one in the ports collection (0.8.1 as opposed to 0.7 > in the base > system) I used this instead (with LIBPCAP_OVERWRITE_BASE=yes) but > still I am > losing the same amount of packets when doing a tcpdump. I don't know what libpcap in ports does regarding the size of the packet capture read buffer, but I've modified the stock libpcap's pcap-bpf.c so it offers to use a buffer much larger than 32768 bytes (look for the loop that has the line for (v = 32768; v != 0; v >>= 1) { and increase 32768 to something more reasonable (say, 1048576). I've also set the debug.bpf_bufsize and debug.bpf_maxbufsize sysctls to match the number in pcap-bpf.c. Maybe this will help, Guy Helmer From owner-freebsd-net@FreeBSD.ORG Thu Feb 12 14:27: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 C5B9E16A4CE for ; Thu, 12 Feb 2004 14:27:32 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id B301943D1D for ; Thu, 12 Feb 2004 14:27:32 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.10/8.12.3) with ESMTP id i1CMRL2h000848; Thu, 12 Feb 2004 14:27:24 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i1CMRLBF000846; Thu, 12 Feb 2004 14:27:21 -0800 Date: Thu, 12 Feb 2004 14:27:21 -0800 From: Brooks Davis To: Brian Reichert Message-ID: <20040212222718.GB30335@Odin.AC.HMC.Edu> References: <20040212193059.GX2429@numachi.com> <20040212194042.GZ2429@numachi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SkvwRMAIpAhPCcCJ" Content-Disposition: inline In-Reply-To: <20040212194042.GZ2429@numachi.com> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: freebsd-net@freebsd.org cc: Julian Elischer Subject: Re: question: source address on interface w/ aliases? 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, 12 Feb 2004 22:27:32 -0000 --SkvwRMAIpAhPCcCJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 12, 2004 at 02:40:42PM -0500, Brian Reichert wrote: > On Thu, Feb 12, 2004 at 11:35:06AM -0800, Julian Elischer wrote: > > > My expectation was that the primary IP address would be used. > >=20 > >=20 > > The primary IP address on the interface referred to in the routing table > > entry that is chosen for the first packet.. > > (last time I looked) >=20 > Such was my expectation. But: is this a BSD-specific implementation? >=20 > If I catch a kernel doing otherwise, can I say 'Aha! That's a bug > based on documented standards' ? Since Solaris switching to doing round-robin in something like 2.4 or 2.5 (7-8 years ago) I doubt you'll have much luck arguing with Sun and most any other implementation could point to them as a reason for their choice. -- 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 --SkvwRMAIpAhPCcCJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAK/3DXY6L6fI4GtQRAlsoAKCtyMWFym0/rDObJ0s7vPwPTZTySwCgqsLV EyePpDNFMNxoUTTCBknXEh0= =XrId -----END PGP SIGNATURE----- --SkvwRMAIpAhPCcCJ-- From owner-freebsd-net@FreeBSD.ORG Thu Feb 12 14:28: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 E8A8A16A4CE for ; Thu, 12 Feb 2004 14:28:44 -0800 (PST) Received: from mail.palnet.com (mail.palnet.com [217.66.226.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0500343D2F for ; Thu, 12 Feb 2004 14:28:43 -0800 (PST) (envelope-from mustafa@palnet.com) Received: from felfel (dogbert.palnet.com [192.116.17.51]) by mail.palnet.com (8.12.5/8.12.5) with ESMTP id i1CMQE9A033359; Fri, 13 Feb 2004 00:26:14 +0200 (IST) From: "Mustafa N. Deeb" To: "'Emre Bastuz'" , Date: Fri, 13 Feb 2004 01:30:51 +0200 Organization: Palnet Communications Ltd. Message-ID: <004e01c3f1c0$44224fa0$8d00000a@felfel> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal In-Reply-To: <1076622177.584b09df25514@webmail.emre.de> Subject: RE: 4.9-STABLE heavily dropping packets? libpcap issue? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Mustafa@palnet.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2004 22:28:45 -0000 You can start by doing "netstat -m" and take it from there ~~~~~~~~~~~~~~~~~~~~~~ Mustafa N. Deeb Technical Director Palnet Communications Ltd. Tel: +970-2-2403434 Fax: +970-2-2403430 www.palsms.com www.paltime.net www.palnet.com -----Original Message----- From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org] On Behalf Of Emre Bastuz Sent: Thursday, February 12, 2004 11:43 PM To: freebsd-net@freebsd.org Subject: 4.9-STABLE heavily dropping packets? libpcap issue? Hi, for sniffing purposes I have a FreeBSD 4.9-STABLE box running on highend, state-of-the-art hardware (Xeon something) with all bells and whistles. The NIC=B4s an onboard copper em0 with gig-e capabilities. Nevertheless I am getting massive packet drops (40%-60%) when I start sniffing a gigabit ehthernet segment although the CPU load is very low. After doing some research in in the appropriate mailing list archives I found out that there are (or were?) sometimes issues with the libpcap. As there was a more current one in the ports collection (0.8.1 as opposed to 0.7 in the base system) I used this instead (with LIBPCAP_OVERWRITE_BASE=3Dyes) but = still I am losing the same amount of packets when doing a tcpdump. I definitly do _not_ know what else I can do to reduce the amount of lost data. *sigh* Things I did to improve the situation so far: - Update from RELEASE to 4.9-STABLE - Compile a custom kernel with reduced drivers and SMP support - Update libpcap and recompile tcpdump Does any of you have an idea else I can do? Any parameters in the kernel that can be tweeked further, like NMBCLUSTERS or NMBUFS? Cheers, Emre -- http://www.emre.de UIN: 561260 PGP Key ID: 0xAFAC77FD I don't see why some people even HAVE cars. -- Calvin ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ 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 Thu Feb 12 14:43:40 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 7FD4116A4CE for ; Thu, 12 Feb 2004 14:43:40 -0800 (PST) Received: from mail.numachi.com (meisai.numachi.com [198.175.254.6]) by mx1.FreeBSD.org (Postfix) with SMTP id C568143D1D for ; Thu, 12 Feb 2004 14:43:39 -0800 (PST) (envelope-from reichert@numachi.com) Received: (qmail 81365 invoked from network); 12 Feb 2004 22:43:38 -0000 Received: from natto.numachi.com (198.175.254.216) by meisai.numachi.com with SMTP; 12 Feb 2004 22:43:38 -0000 Received: (qmail 53009 invoked by uid 1001); 12 Feb 2004 22:43:38 -0000 Date: Thu, 12 Feb 2004 17:43:38 -0500 From: Brian Reichert To: Brooks Davis Message-ID: <20040212224338.GF2429@numachi.com> References: <20040212193059.GX2429@numachi.com> <20040212194042.GZ2429@numachi.com> <20040212222718.GB30335@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040212222718.GB30335@Odin.AC.HMC.Edu> User-Agent: Mutt/1.5.5.1i cc: freebsd-net@freebsd.org cc: Julian Elischer Subject: Re: question: source address on interface w/ aliases? 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, 12 Feb 2004 22:43:40 -0000 On Thu, Feb 12, 2004 at 02:27:21PM -0800, Brooks Davis wrote: > On Thu, Feb 12, 2004 at 02:40:42PM -0500, Brian Reichert wrote: > > If I catch a kernel doing otherwise, can I say 'Aha! That's a bug > > based on documented standards' ? > > Since Solaris switching to doing round-robin in something like 2.4 or > 2.5 (7-8 years ago) I doubt you'll have much luck arguing with Sun and > most any other implementation could point to them as a reason for their > choice. Fair enough; thanks for the feedback... > -- Brooks > > -- > 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 -- Brian Reichert 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA BSD admin/developer at large From owner-freebsd-net@FreeBSD.ORG Thu Feb 12 14:49: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 B2EC716A4CE for ; Thu, 12 Feb 2004 14:49:06 -0800 (PST) Received: from rms04.rommon.net (rms04.rommon.net [212.54.2.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2985143D1D for ; Thu, 12 Feb 2004 14:49:06 -0800 (PST) (envelope-from pete@he.iki.fi) Received: from he.iki.fi (h81.vuokselantie10.fi [193.64.42.129]) by rms04.rommon.net (8.12.9p1/8.12.9) with ESMTP id i1CMmxcM074175; Fri, 13 Feb 2004 00:48:59 +0200 (EET) (envelope-from pete@he.iki.fi) Message-ID: <402C029B.30103@he.iki.fi> Date: Fri, 13 Feb 2004 00:47:55 +0200 From: Petri Helenius User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Guy Helmer References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit cc: freebsd-net@freebsd.org cc: Emre Bastuz Subject: Re: 4.9-STABLE heavily dropping packets? libpcap issue? 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, 12 Feb 2004 22:49:06 -0000 Guy Helmer wrote: >Emre Bastuz wrote on Thursday, February 12, 2004 3:43 PM > > >>Hi, >> >>for sniffing purposes I have a FreeBSD 4.9-STABLE box running on highend, >>state-of-the-art hardware (Xeon something) with all bells and whistles. >> >>The NICīs an onboard copper em0 with gig-e capabilities. >> >>Nevertheless I am getting massive packet drops (40%-60%) when I >>start sniffing a >>gigabit ehthernet segment although the CPU load is very low. >> >>After doing some research in in the appropriate mailing list >>archives I found >>out that there are (or were?) sometimes issues with the libpcap. >>As there was a >>more current one in the ports collection (0.8.1 as opposed to 0.7 >>in the base >>system) I used this instead (with LIBPCAP_OVERWRITE_BASE=yes) but >>still I am >>losing the same amount of packets when doing a tcpdump. >> >> > >I don't know what libpcap in ports does regarding the size of the packet >capture read buffer, but I've modified the stock libpcap's pcap-bpf.c so it >offers to use a buffer much larger than 32768 bytes (look for the loop that >has the line > > for (v = 32768; v != 0; v >>= 1) { > >and increase 32768 to something more reasonable (say, 1048576). > >I've also set the debug.bpf_bufsize and debug.bpf_maxbufsize sysctls to >match the number in pcap-bpf.c. > > > This is also fixed in more current libpcap version, however that has not been ported to the tree. Pete From owner-freebsd-net@FreeBSD.ORG Thu Feb 12 16:21: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 E32F716A4CE; Thu, 12 Feb 2004 16:21:27 -0800 (PST) Received: from ikarus.gardrail.com (wv-hdgsvle-cmts2b-87.shphwv.adelphia.net [68.67.83.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67BD843D1F; Thu, 12 Feb 2004 16:21:27 -0800 (PST) (envelope-from freebsd@gardrail.com) Received: from mail.gardrail.com (ikarus.gardrail.com [68.67.83.87]) by ikarus.gardrail.com (8.12.8/8.12.8) with ESMTP id i1D0IuqV002814; Thu, 12 Feb 2004 19:18:56 -0500 From: "Bill" To: net@freebsd.org, freebsd-hackers@freebsd.org, freebsd-firewall@freebsd.org, freebsd-performance@freebsd.org Date: Thu, 12 Feb 2004 19:18:56 -0500 Message-Id: <20040213001513.M60613@gardrail.com> X-Mailer: Open WebMail 2.10 20030720 X-OriginatingIP: 172.31.31.130 (wrude) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: Obtaining 75k (active) concurrent tcp sessions.. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Bill List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 00:21:28 -0000 What steps would I need to take in order to obtain 75,000 concurrent TCP sessions on a FreeBSD 5.2 system running on the following hardware: dual xenon 3ghz 1mb cache processors 2 gigs of memory two dual port fibre gigabit nic's 1 onboard copper 10/100 nic I read a post that was sent to freebsd-hackers, which mentioned an individual was able to obtain 1.6 million concurrent tcp sessions, so I assume it's possible. My goal is to setup a server, which is capable of accepting at least 75k tcp connections to perform some firewall stress tests at work. Given that information on this subject is quite scarce, I thought I'd post this question and see what type of response I get back. Any assistance or suggestions would be greatly appreciated, Thanks in advance, -=-Bill-=- From owner-freebsd-net@FreeBSD.ORG Fri Feb 13 01:44:49 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 B8A8116A4CE for ; Fri, 13 Feb 2004 01:44:49 -0800 (PST) Received: from mailgw.servicefactory.se (mailgw.servicefactory.se [192.71.33.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0E5843D1D for ; Fri, 13 Feb 2004 01:44:48 -0800 (PST) (envelope-from xfree@bulow.mine.nu) Received: from ark.servicefactory.se (ark.servicefactory.se [192.71.33.5]) i1D9iiw00667; Fri, 13 Feb 2004 10:44:44 +0100 (CET) Received: from bulow.mine.nu (ark.servicefactory.se [192.71.33.5]) by ark.servicefactory.se (8.12.9/8.12.6) with ESMTP id i1D9gamP008223; Fri, 13 Feb 2004 10:42:37 +0100 (CET) (envelope-from xfree@bulow.mine.nu) Message-ID: <402C9C8A.50203@bulow.mine.nu> Date: Fri, 13 Feb 2004 10:44:42 +0100 From: Jonas Bulow User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6b) Gecko/20031218 X-Accept-Language: en-us, en, sv MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: wpaul@ctr.columbia.edu Subject: ifconfig rl0 does not report status on FreeBSD-4.9 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, 13 Feb 2004 09:44:50 -0000 Hi, The rl driver does not report it's link status on FreeBSD 4.9, at least not when using ifconfig. The chip is a Realtek 8139C+. I could not find anything about it in the archives. Any hints? # ifconfig rl0 rl0: flags=8843 mtu 1500 inet 192.168.2.2 netmask 0xffffff00 broadcast 192.168.2.255 ether 00:90:fb:04:5e:78 media: Ethernet autoselect (none) # ping -c 1 192.168.2.1 PING 192.168.2.1 (192.168.2.1): 56 data bytes 64 bytes from 192.168.2.1: icmp_seq=0 ttl=64 time=0.514 ms --- 192.168.2.1 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.514/0.514/0.514/0.000 ms From dmesg: rl0: port 0xdc00-0xdcff mem 0xe7000000-0xe70000ff irq 12 at device 9.0 on pci0 rl0: Ethernet address: 00:90:fb:04:5e:78 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto /j From owner-freebsd-net@FreeBSD.ORG Fri Feb 13 02:39:00 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 55A7916A4CE for ; Fri, 13 Feb 2004 02:39:00 -0800 (PST) Received: from mailgw.servicefactory.se (mailgw.servicefactory.se [192.71.33.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CC0343D31 for ; Fri, 13 Feb 2004 02:38:59 -0800 (PST) (envelope-from xfree@bulow.mine.nu) Received: from ark.servicefactory.se (ark.servicefactory.se [192.71.33.5]) i1DAcww01602; Fri, 13 Feb 2004 11:38:58 +0100 (CET) Received: from bulow.mine.nu (ark.servicefactory.se [192.71.33.5]) by ark.servicefactory.se (8.12.9/8.12.6) with ESMTP id i1DAapmP011884; Fri, 13 Feb 2004 11:36:51 +0100 (CET) (envelope-from xfree@bulow.mine.nu) Message-ID: <402CA941.3000300@bulow.mine.nu> Date: Fri, 13 Feb 2004 11:38:57 +0100 From: Jonas Bulow User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6b) Gecko/20031218 X-Accept-Language: en-us, en, sv MIME-Version: 1.0 To: manish gautam References: <20040212173529.93598.qmail@web8203.mail.in.yahoo.com> In-Reply-To: <20040212173529.93598.qmail@web8203.mail.in.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: netgraph....help 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, 13 Feb 2004 10:39:00 -0000 Hi, manish gautam wrote: > i want to make my own node with my own specifications. > how can i do that and load it and pass data through > it. A good start is to do it as a userland process and use ng_socket to communicate with the netgraph subsystem. > > reply as soon as possible... I'm sorry if I kept you waiting. /j > > cheers > manish > > ________________________________________________________________________ > Yahoo! India Education Special: Study in the UK now. > Go to http://in.specials.yahoo.com/index1.html > _______________________________________________ > 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 Fri Feb 13 03:35: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 1A16416A4CE; Fri, 13 Feb 2004 03:35:26 -0800 (PST) Received: from nsuncom.rz.hu-berlin.de (nsuncom.rz.hu-berlin.de [141.20.1.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7145743D1F; Fri, 13 Feb 2004 03:35:25 -0800 (PST) (envelope-from h0444lp6@student.hu-berlin.de) Received: from localhost (localhost [127.0.0.1])i1DBZORM018866; Fri, 13 Feb 2004 12:35:24 +0100 (MET) Received: from nsuncom.rz.hu-berlin.de ([127.0.0.1]) by localhost (nsuncom [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18518-06; Fri, 13 Feb 2004 12:35:23 +0100 (MET) Received: from kojo (ppp198-49.rz.hu-berlin.de [141.20.198.49]) i1DBZDXk018449; Fri, 13 Feb 2004 12:35:20 +0100 (MET) From: "h0444lp6" To: , Date: Fri, 13 Feb 2004 19:36:11 +0800 Message-ID: <000e01c3f225$a72c0ea0$31c6148d@kojo> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-Virus-Scanned: by amavisd-new at hu-berlin.de Subject: 802.11g and PCI 2.1 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, 13 Feb 2004 11:35:26 -0000 URGENT!!! I need a 802.11g PCI card supported by FreeBSD 5.2R which will work in a only PCI 2.1 compliant slot. All cards I saw seem to require PCI 2.2. Does anyone know of a PCI 2.1 card? Please ... From owner-freebsd-net@FreeBSD.ORG Fri Feb 13 05:41:17 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 C4ABE16A4CE for ; Fri, 13 Feb 2004 05:41:17 -0800 (PST) Received: from ftp.ccrle.nec.de (ftp.netlab.nec.de [195.37.70.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CE3D43D1D for ; Fri, 13 Feb 2004 05:41:17 -0800 (PST) (envelope-from lars.eggert@netlab.nec.de) Received: from netlab.nec.de (tokyo.netlab.nec.de [195.37.70.2]) by ftp.ccrle.nec.de (Postfix) with ESMTP id CD7EBF5A9; Fri, 13 Feb 2004 14:45:59 +0100 (CET) Message-ID: <402CD3FA.8090706@netlab.nec.de> Date: Fri, 13 Feb 2004 14:41:14 +0100 From: Lars Eggert Organization: NEC Network Laboratories User-Agent: Mozilla Thunderbird 0.5 (Macintosh/20040208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brian Reichert References: <20040212193059.GX2429@numachi.com> <20040212194042.GZ2429@numachi.com> In-Reply-To: <20040212194042.GZ2429@numachi.com> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms030704070504000803060001" cc: freebsd-net@freebsd.org cc: Julian Elischer Subject: Re: question: source address on interface w/ aliases? 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, 13 Feb 2004 13:41:17 -0000 This is a cryptographically signed message in MIME format. --------------ms030704070504000803060001 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Brian Reichert wrote: > On Thu, Feb 12, 2004 at 11:35:06AM -0800, Julian Elischer wrote: > >>>My expectation was that the primary IP address would be used. >> >>The primary IP address on the interface referred to in the routing table >>entry that is chosen for the first packet.. >>(last time I looked) > > Such was my expectation. But: is this a BSD-specific implementation? > > If I catch a kernel doing otherwise, can I say 'Aha! That's a bug > based on documented standards' ? RFC 1122, Section 3.3.4.2 Lars -- Lars Eggert NEC Network Laboratories --------------ms030704070504000803060001 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJ/zCC Az8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQI EwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENv bnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAi BgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVy c29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5 NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBM dGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzAN BgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9Vvy Gna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOC dz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCB kTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhh d3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNV HREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQAD gYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFi w9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpb NU1341YheILcIRk13iSx0x1G/11fZU8wggNaMIICw6ADAgECAgMLU6IwDQYJKoZIhvcNAQEE BQAwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0 ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTAz MTIxNTEyMzEyOFoXDTA0MTIxNDEyMzEyOFowgYQxDzANBgNVBAQTBkVnZ2VydDENMAsGA1UE KhMETGFyczEUMBIGA1UEAxMLTGFycyBFZ2dlcnQxKDAmBgkqhkiG9w0BCQEWGWxhcnMuZWdn ZXJ0QG5ldGxhYi5uZWMuZGUxIjAgBgkqhkiG9w0BCQEWE2xhcnMuZWdnZXJ0QGdteC5uZXQw ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDWps58Zq8Buu2DKDl9crbvzSo6zWsZ TkQLr5zOTqUMs/eU7Mcohv64O4IxWWYGLfYsjDRxUlmdHdJUbyTtUh2lH452DUDJByXidlLm RDgohG0AVwztedqy1+hE3VnCdpMhUGks+6ntrr3dKSxMgLM0AM1kPWsH9lWX6IOPdxOC30gM PiQ65zH9PR70befQLgFPKcAv0wP8210l05n8ekwYAcq2cm3/j+nuDu0HEh5pgsnY7cVELeNJ ODvr4IiE1t3c2w4+0Nc/WJrqGCMl+gZ8c+7FtzjoyDeEsCjNFDeA2ymNd+10O6kjwvPHlzPr 3rW73RDRPAjMJ49HXlueiuoNAgMBAAGjdzB1MCoGBStlAQQBBCEwHwIBADAaMBgCAQQEE0wy dU15ZmZCTlViTkpKY2RaMnMwOQYDVR0RBDIwMIEZbGFycy5lZ2dlcnRAbmV0bGFiLm5lYy5k ZYETbGFycy5lZ2dlcnRAZ214Lm5ldDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUAA4GB AHgrv3SQFD4AS4lY4oKcI3iTHcclEHbYfg3UUb8zzCUsl+OJoz0nmebGmOL+tvNj5GvCrWnN H4LvVLh8ZBhFXms7eKJ1YiHgbKwTRK23P8Y5NDit5ico0ZjpFWeenUWj3ajEbN6n4K8dNp+C 0b2apnSrlFVWY6BucZFIYqQ1Lf91MIIDWjCCAsOgAwIBAgIDC1OiMA0GCSqGSIb3DQEBBAUA MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQu MSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTAeFw0wMzEy MTUxMjMxMjhaFw0wNDEyMTQxMjMxMjhaMIGEMQ8wDQYDVQQEEwZFZ2dlcnQxDTALBgNVBCoT BExhcnMxFDASBgNVBAMTC0xhcnMgRWdnZXJ0MSgwJgYJKoZIhvcNAQkBFhlsYXJzLmVnZ2Vy dEBuZXRsYWIubmVjLmRlMSIwIAYJKoZIhvcNAQkBFhNsYXJzLmVnZ2VydEBnbXgubmV0MIIB IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA1qbOfGavAbrtgyg5fXK2780qOs1rGU5E C6+czk6lDLP3lOzHKIb+uDuCMVlmBi32LIw0cVJZnR3SVG8k7VIdpR+Odg1AyQcl4nZS5kQ4 KIRtAFcM7XnastfoRN1ZwnaTIVBpLPup7a693SksTICzNADNZD1rB/ZVl+iDj3cTgt9IDD4k Oucx/T0e9G3n0C4BTynAL9MD/NtdJdOZ/HpMGAHKtnJt/4/p7g7tBxIeaYLJ2O3FRC3jSTg7 6+CIhNbd3NsOPtDXP1ia6hgjJfoGfHPuxbc46Mg3hLAozRQ3gNspjXftdDupI8Lzx5cz6961 u90Q0TwIzCePR15bnorqDQIDAQABo3cwdTAqBgUrZQEEAQQhMB8CAQAwGjAYAgEEBBNMMnVN eWZmQk5VYk5KSmNkWjJzMDkGA1UdEQQyMDCBGWxhcnMuZWdnZXJ0QG5ldGxhYi5uZWMuZGWB E2xhcnMuZWdnZXJ0QGdteC5uZXQwDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQQFAAOBgQB4 K790kBQ+AEuJWOKCnCN4kx3HJRB22H4N1FG/M8wlLJfjiaM9J5nmxpji/rbzY+Rrwq1pzR+C 71S4fGQYRV5rO3iidWIh4GysE0Sttz/GOTQ4reYnKNGY6RVnnp1Fo92oxGzep+CvHTafgtG9 mqZ0q5RVVmOgbnGRSGKkNS3/dTGCAzswggM3AgEBMGkwYjELMAkGA1UEBhMCWkExJTAjBgNV BAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJz b25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAgMLU6IwCQYFKw4DAhoFAKCCAacwGAYJKoZIhvcN AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDQwMjEzMTM0MTE0WjAjBgkqhkiG 9w0BCQQxFgQUFHqyK12owG8oh79dj68sHJJEHC0wUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgweAYJKwYBBAGCNxAEMWswaTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3Rl IENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt YWlsIElzc3VpbmcgQ0ECAwtTojB6BgsqhkiG9w0BCRACCzFroGkwYjELMAkGA1UEBhMCWkEx JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0 ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAgMLU6IwDQYJKoZIhvcNAQEBBQAEggEA 0POH5+eutnMKoN8sJdoLjHkWnA4QFwGeu4PekBK2QIpbKaAlesjmlsKEXQDCfLXzMEGe2aul GHmKU7nyyYFbal4jCK0g9h3UiPkYYDMaJK6L2P1DLv71uoUxS890de6JerRaKpj7XipQVxk2 3if2OBOKVc5p33ctxXeTpptj41T3pwmr++TGOOxN58XOTXSBq2FQCdO74zWNVvznIh/CaiSS 4cbznN07kzp2pfDnLqvrLRbmHV4MD0cYMYCkpiFi+UgVr9N/9mgKzrwG9W4FQAKWdOdrjFy/ PoCNQYWJuJFqtHTKslh1KSdj9r4v/Nw1LsdXDGw16HeUmE6d30YzywAAAAAAAA== --------------ms030704070504000803060001-- From owner-freebsd-net@FreeBSD.ORG Fri Feb 13 11:19: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 43F8016A4CE for ; Fri, 13 Feb 2004 11:19:11 -0800 (PST) Received: from smtp3.mmedia.is (smtp3.mmedia.is [217.151.160.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF8C343D1D for ; Fri, 13 Feb 2004 11:19:10 -0800 (PST) (envelope-from baldur@foo.is) Received: from smtp.mmedia.is (smtp.mmedia.is [217.151.160.9]) i1DJJ9u5018445 for ; Fri, 13 Feb 2004 19:19:09 GMT Received: from tesla.foo.is (postfix@tesla.foo.is [217.151.166.96]) by smtp.mmedia.is (8.11.7/1.0.0) with ESMTP id i1DJJ8C15236 for ; Fri, 13 Feb 2004 19:19:08 GMT Received: from germanium.foo.is (germanium.foo.is [192.168.1.1]) by tesla.foo.is (Postfix) with ESMTP id BC89CA960 for ; Fri, 13 Feb 2004 19:19:07 +0000 (GMT) From: Baldur Gislason To: freebsd-net@freebsd.org Date: Fri, 13 Feb 2004 19:19:06 +0000 User-Agent: KMail/1.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402131919.06395.baldur@foo.is> Subject: VPN with FreeBSD using some form of encryption 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, 13 Feb 2004 19:19:11 -0000 I have a home network with FreeBSD machines and a laptop running FreeBSD. The laptop connects to various networks but I'd like to access my home machines from the laptop, the home machines are behind a freebsd nat firewall. I've been using mpd for quite a while, doing a PPTP link from my laptop to home but it doesn't offer any useful encryption, and the encryption it claims to offer doesn't seem to work. Hence, limiting what I can do over the link without fear of being sniffed. I'd like being able to dial in from anywhere, yet have an encrypted link. What are my options? I've read about the IPSEC tunneling support but it seems to me that it's limited to static tunnels. Baldur From owner-freebsd-net@FreeBSD.ORG Fri Feb 13 11:59:17 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 A5D5E16A4CE for ; Fri, 13 Feb 2004 11:59:17 -0800 (PST) Received: from mx.sat.corp.rackspace.com (mx.sat.corp.rackspace.com [64.39.1.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id 607D243D1D for ; Fri, 13 Feb 2004 11:59:17 -0800 (PST) (envelope-from amason@rackspace.com) Received: from mail.rackspace.com (mail.rackspace.com [64.39.2.181]) i1DJv152017083; Fri, 13 Feb 2004 13:57:01 -0600 Received: from [10.1.101.24] (office101-24.sat.rackspace.com [10.1.101.24]) by mail.rackspace.com (8.12.10/8.12.10) with ESMTP id i1DJxA32014152; Fri, 13 Feb 2004 13:59:10 -0600 From: Art Mason To: Baldur Gislason In-Reply-To: <200402131919.06395.baldur@foo.is> References: <200402131919.06395.baldur@foo.is> Content-Type: text/plain Organization: Rackspace Managed Hosting Message-Id: <1076702437.20300.35.camel@mizar.rackspace.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Fri, 13 Feb 2004 14:00:38 -0600 Content-Transfer-Encoding: 7bit X-MailScanner: Dd6rvCg9: Found to be clean cc: freebsd-net@freebsd.org Subject: Re: VPN with FreeBSD using some form of encryption 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, 13 Feb 2004 19:59:18 -0000 Not sure if it helps your particular situation, but you might want to take a look at OpenVPN (/usr/ports/security/openvpn). It's an application layer VPN implementation (SSL) as opposed to IPSec, but seems to work well for dynamic IP addresses and endpoints behind NAT devices. Quite stable, as well. -- Art Mason Technical Support - Team F Rackspace Managed Hosting (800) 961-4454 ext. 1223 amason@rackspace.com On Fri, 2004-02-13 at 13:19, Baldur Gislason wrote: > I have a home network with FreeBSD machines and a laptop running FreeBSD. > The laptop connects to various networks but I'd like to access my home > machines from the laptop, the home machines are behind a freebsd nat > firewall. > I've been using mpd for quite a while, doing a PPTP link from my laptop to > home but it doesn't offer any useful encryption, and the encryption it claims > to offer doesn't seem to work. > Hence, limiting what I can do over the link without fear of being sniffed. > I'd like being able to dial in from anywhere, yet have an encrypted link. What > are my options? > I've read about the IPSEC tunneling support but it seems to me that it's > limited to static tunnels. > > Baldur > > _______________________________________________ > 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 Fri Feb 13 12:26:21 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 B02AF16A4CE for ; Fri, 13 Feb 2004 12:26:21 -0800 (PST) Received: from mail.numachi.com (meisai.numachi.com [198.175.254.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 4A60B43D2F for ; Fri, 13 Feb 2004 12:26:18 -0800 (PST) (envelope-from reichert@numachi.com) Received: (qmail 29688 invoked from network); 13 Feb 2004 20:26:14 -0000 Received: from natto.numachi.com (198.175.254.216) by meisai.numachi.com with SMTP; 13 Feb 2004 20:26:14 -0000 Received: (qmail 62735 invoked by uid 1001); 13 Feb 2004 20:26:14 -0000 Date: Fri, 13 Feb 2004 15:26:14 -0500 From: Brian Reichert To: Lars Eggert Message-ID: <20040213202614.GU2429@numachi.com> References: <20040212193059.GX2429@numachi.com> <20040212194042.GZ2429@numachi.com> <402CD3FA.8090706@netlab.nec.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <402CD3FA.8090706@netlab.nec.de> User-Agent: Mutt/1.5.5.1i cc: freebsd-net@freebsd.org cc: Julian Elischer Subject: Re: question: source address on interface w/ aliases? 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, 13 Feb 2004 20:26:21 -0000 On Fri, Feb 13, 2004 at 02:41:14PM +0100, Lars Eggert wrote: > Brian Reichert wrote: > >If I catch a kernel doing otherwise, can I say 'Aha! That's a bug > >based on documented standards' ? > > RFC 1122, Section 3.3.4.2 Cool! Thanks for that pointer... That section refers to 'sending a datagram', which sounds UDP-specific. Regardless of that, that section refers me to '3.3.4.3 Choosing a Source Address', which does more succinctly address my question. All I find upon a first read is: (b) The route cache may be consulted, to see if there is an active route to the specified destination network through any network interface; if so, a local IP address corresponding to that interface may be chosen. But, nothing in RFC 1122 seems to shed any light on a selection algorithm. At least thia RFC grants me more vectors of research; thanks again... > Lars > -- > Lars Eggert NEC Network Laboratories -- Brian Reichert 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA BSD admin/developer at large From owner-freebsd-net@FreeBSD.ORG Fri Feb 13 12:32: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 59A8F16A4CE for ; Fri, 13 Feb 2004 12:32:13 -0800 (PST) Received: from mail.valuehost.co.uk (mail.valuehost.co.uk [62.25.99.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 95AD643D1D for ; Fri, 13 Feb 2004 12:32:12 -0800 (PST) (envelope-from bjorn@eikeland.info) Received: (qmail 6305 invoked by uid 89); 13 Feb 2004 20:31:58 +0000 Received: from unknown (HELO beer.eikeland.info) (bjorn@eikeland.info@80.202.108.144) by mail.valuehost.co.uk with SMTP; 13 Feb 2004 20:31:58 +0000 Date: Fri, 13 Feb 2004 21:30:31 +0100 To: "freebsd-net@freebsd.org" From: Bjorn Eikeland Content-Type: text/plain; format=flowed; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: User-Agent: Opera7.23/FreeBSD M2 build 518 Subject: vlan with its own ether / mac address? 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, 13 Feb 2004 20:32:13 -0000 is it possible to set up a vlan device with its own ether address? I've tried the following: ifconfig vlan0 create ifconfig vlan0 vlan 1 vlandev fxp0 up ifconfig vlan0 inet 10.0.0.10 netmask 255.255.255.0 \ ether 00:a0:c9:f1:4e:6e ifconfig: ether: bad value but changing the ether value after the device is up 'works', but caused me to only have access to the vlan ip. my existing fxp0 device fxp0: flags=8843 mtu 1500 inet 10.0.0.2 netmask 0xff000000 broadcast 10.255.255.255 ether 00:a0:c9:f1:4e:6d media: Ethernet autoselect (100baseTX ) status: active the faked vlan0 device: vlan0: flags=8843 mtu 1500 inet 10.0.0.10 netmask 0xffffff00 broadcast 10.0.0.255 ether 00:a0:c9:f1:4e:6e media: Ethernet autoselect (100baseTX ) status: active vlan: 1 parent interface: fxp0 basically I'm trying to set up dhcp to configure unknown hosts in a seperate network to allow them to register their mac address and then be allocated a ip in the "real" network. And need a way to test with several clients, but I've only got one nic in my box. looks like I'll be buying another nic and use dhcping -h and see if it does the trick - but just wanted to see if there is a all free and nice software solution. From owner-freebsd-net@FreeBSD.ORG Fri Feb 13 12:58: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 1B51D16A4CE for ; Fri, 13 Feb 2004 12:58:22 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA32B43D1D for ; Fri, 13 Feb 2004 12:58:21 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.10/8.12.3) with ESMTP id i1DKwH2h004875; Fri, 13 Feb 2004 12:58:17 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i1DKwGNM004874; Fri, 13 Feb 2004 12:58:16 -0800 Date: Fri, 13 Feb 2004 12:58:16 -0800 From: Brooks Davis To: Bjorn Eikeland Message-ID: <20040213205813.GA1570@Odin.AC.HMC.Edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bp/iNruPH9dso1Pn" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: "freebsd-net@freebsd.org" Subject: Re: vlan with its own ether / mac address? 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, 13 Feb 2004 20:58:22 -0000 --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 13, 2004 at 09:30:31PM +0100, Bjorn Eikeland wrote: > is it possible to set up a vlan device with its own ether address? > I've tried the following: >=20 > ifconfig vlan0 create > ifconfig vlan0 vlan 1 vlandev fxp0 up > ifconfig vlan0 inet 10.0.0.10 netmask 255.255.255.0 \ > ether 00:a0:c9:f1:4e:6e > ifconfig: ether: bad value >=20 > but changing the ether value after the device is up 'works', > but caused me to only have access to the vlan ip. >=20 > my existing fxp0 device > fxp0: flags=3D8843 mtu 1500 > inet 10.0.0.2 netmask 0xff000000 broadcast 10.255.255.255 > ether 00:a0:c9:f1:4e:6d > media: Ethernet autoselect (100baseTX ) > status: active >=20 > the faked vlan0 device: > vlan0: flags=3D8843 mtu 1500 > inet 10.0.0.10 netmask 0xffffff00 broadcast 10.0.0.255 > ether 00:a0:c9:f1:4e:6e > media: Ethernet autoselect (100baseTX ) > status: active > vlan: 1 parent interface: fxp0 You might try putting the interface in promisc mode. I'm not sure that will be sufficent, but it might be. I suspect the problem is likely to be that the recieve filter on many NICs only supports two modes promisc and self+broadcast. You want a mode where you get self1+self2+broadcast. Some multicast filters probably do support this. > basically I'm trying to set up dhcp to configure unknown hosts > in a seperate network to allow them to register their mac address > and then be allocated a ip in the "real" network. And need a way > to test with several clients, but I've only got one nic in my box. You might be able to create virtual ethernet interfaces via tap(4) and then bridge them. -- 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 --bp/iNruPH9dso1Pn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFALTpjXY6L6fI4GtQRApvqAJ9u/+7awYaJM6uJlpmMVjdvwCsONACggtmf gv3EESmDOlkUhq0b+Jp8fKk= =3nNT -----END PGP SIGNATURE----- --bp/iNruPH9dso1Pn--