From owner-freebsd-net@FreeBSD.ORG Sun Feb 29 08:15: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 B12A316A4CE for ; Sun, 29 Feb 2004 08:15:37 -0800 (PST) Received: from hotmail.com (law11-f114.law11.hotmail.com [64.4.17.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id A270943D39 for ; Sun, 29 Feb 2004 08:15:37 -0800 (PST) (envelope-from weiwuzhang@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 29 Feb 2004 08:15:37 -0800 Received: from 218.85.102.35 by lw11fd.law11.hotmail.msn.com with HTTP; Sun, 29 Feb 2004 16:15:37 GMT X-Originating-IP: [218.85.102.35] X-Originating-Email: [weiwuzhang@hotmail.com] X-Sender: weiwuzhang@hotmail.com From: "Zhang Weiwu" To: freebsd-net@freebsd.org Date: Mon, 01 Mar 2004 00:15:37 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312; format=flowed Message-ID: X-OriginalArrivalTime: 29 Feb 2004 16:15:37.0530 (UTC) FILETIME=[446779A0:01C3FEDF] Subject: ppp server request IP address for client from local DHCP server? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: zhangweiwu@realss.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Feb 2004 16:15:37 -0000 Hello. I have configured a ppp server, works great now. Only that the client address arrange is specified in ppp.conf. That was two years ago, I setup a ppp link on the Win2k server, on the tcp/ip setup I select "use DHCP", where there is another DHCP server in the LAN. A client dials in, pppserver request an IP address from DHCP server, assign it to pppclient. Can FreeBSD ppp(8) be configured that way? Just kinda curious. Thank you. _________________________________________________________________ ÓëÁª»úµÄÅóÓѽøÐн»Á÷£¬ÇëʹÓà MSN Messenger: http://messenger.msn.com/cn From owner-freebsd-net@FreeBSD.ORG Sun Feb 29 14:10: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 40DEC16A4CE for ; Sun, 29 Feb 2004 14:10:21 -0800 (PST) Received: from tea.blinkenlights.nl (tea.blinkenlights.nl [62.58.162.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE5A843D1F for ; Sun, 29 Feb 2004 14:10:20 -0800 (PST) (envelope-from sten@blinkenlights.nl) Received: by tea.blinkenlights.nl (Postfix, from userid 101) id 88FA03A8; Sun, 29 Feb 2004 23:05:33 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by tea.blinkenlights.nl (Postfix) with ESMTP id 81E55127 for ; Sun, 29 Feb 2004 23:05:33 +0100 (CET) Date: Sun, 29 Feb 2004 23:05:33 +0100 (CET) From: Sten Spans To: freebsd-net@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Strange ipf ipv6 issues on alpha 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, 29 Feb 2004 22:10:21 -0000 I have an alpha running freebsd 4.9p2, and somehow ipf seems to have gone on strike just recently. I'm guessing this started ocurring when going from 4.9p1 to p2. towel# ipf -6 -F o towel# cat /etc/ipf6.rules pass out quick on fxp1 to gif0:3ffe:8114:1000::2a8 from 3ffe:8114:2000:10E0::/60 to any pass out quick on fxp1 to gif0:3ffe:8114:1000::2a8 from 3ffe:8114:1000::2a9 to any towel# ipf -6 -f /etc/ipf6.rules towel# ipfstat -o -6 pass out quick on fxp1 to gif0:v from 3ffe:8114:2000:10e0::/60 to any pass out quick on fxp1 to gif0:v from 3ffe:8114:1000::2a9/128 to any The ipv6 address folowing gif0 is replaced by some binary character. Anyone got a clue ? ( please cc me, since I don't subscribe to fbsd-net ) -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - Anthem From owner-freebsd-net@FreeBSD.ORG Mon Mar 1 00:37: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 3315816A4CE for ; Mon, 1 Mar 2004 00:37:50 -0800 (PST) Received: from proto.mstu.gov.ua (uintei.kiev.ua [62.244.14.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01DD543D2D for ; Mon, 1 Mar 2004 00:37:45 -0800 (PST) (envelope-from tor@mstu.gov.ua) Received: from proto.mstu.gov.ua (localhost [127.0.0.1]) by proto.mstu.gov.ua (8.12.8/8.12.6) with ESMTP id i218bPLE018103 for ; Mon, 1 Mar 2004 10:37:31 +0200 (EET) (envelope-from tor@mstu.gov.ua) Received: (from tor@localhost) by proto.mstu.gov.ua (8.12.8/8.12.6/Submit) id i218a09l018086 for freebsd-net@freebsd.org; Mon, 1 Mar 2004 10:36:00 +0200 (EET) X-Authentication-Warning: proto.mstu.gov.ua: tor set sender to tor@mstu.gov.ua using -f Date: Mon, 1 Mar 2004 10:36:00 +0200 From: My Realname To: freebsd-net@freebsd.org Message-ID: <20040301083600.GA16708@proto.mstu.gov.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: 3COM BCM5701 nic trouble 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, 01 Mar 2004 08:37:50 -0000 Hi everyone I have a some difficalties with installing a bge0 (BCM5701TKHB nic from 3COM) on FreeBSD 4.9 i already chenaged 18000 to 10000 in if_bge.c and patch some files by files from freebsd.org/~wpaul and download 60M from 3com, but those driver for linux only at 1000baseTX it can't get carrier at 100baseTX it got carrier, but don't ping host at over side of crossover (crossover tested ok) at all variants in /var/log/messages appear: "bge0: watchdog timeout -- reseting" can anybody help me ? -- WBR Anton Yatsuna tor@mstu.gov.ua From owner-freebsd-net@FreeBSD.ORG Mon Mar 1 02:49: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 D16FD16A4CE for ; Mon, 1 Mar 2004 02:49:23 -0800 (PST) Received: from us.svf.stuba.sk (us.svf.stuba.sk [147.175.16.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A1B343D2F for ; Mon, 1 Mar 2004 02:49:23 -0800 (PST) (envelope-from md@us.svf.stuba.sk) Received: from us.svf.stuba.sk (localhost [127.0.0.1]) by us.svf.stuba.sk (8.12.11/8.12.11) with ESMTP id i21An6qu052187; Mon, 1 Mar 2004 11:49:06 +0100 (CET) (envelope-from md@us.svf.stuba.sk) Received: (from md@localhost) by us.svf.stuba.sk (8.12.11/8.12.11/Submit) id i21An0CU052186; Mon, 1 Mar 2004 11:49:00 +0100 (CET) (envelope-from md) Date: Mon, 1 Mar 2004 11:49:00 +0100 From: Marian Durkovic To: david.burns@dugeem.net, freebsd-net@freebsd.org Message-ID: <20040301104900.GA51193@us.svf.stuba.sk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on us.svf.stuba.sk Subject: Re: Solution: TX performance problems with 3Com 905C cards 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, 01 Mar 2004 10:49:23 -0000 On Sun, 22 Feb 2004, David Burns wrote: > The modification was to reduce the NIC interrupt rate via a rudimentary > hardware polling scheme based on the 3c905x countdown timer. Well, the number of interrupts per second is really much higher than e.g. with the fxp driver: xl driver TX: 13500 intrs/sec RX: 13800 intrs/sec fxp driver TX: 5700 intrs/sec RX: 8500 intrs/sec David, could you perhaps send me your if_xl* files so I can test your modifications here? Thanks & kind regards, M. -------------------------------------------------------------------------- ---- ---- ---- Marian Durkovic network manager ---- ---- ---- ---- Slovak Technical University Tel: +421 2 524 51 301 ---- ---- Computer Centre, Nam. Slobody 17 Fax: +421 2 524 94 351 ---- ---- 812 43 Bratislava, Slovak Republic E-mail/sip: md@bts.sk ---- ---- ---- -------------------------------------------------------------------------- From owner-freebsd-net@FreeBSD.ORG Mon Mar 1 09:11:43 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 87A5016A4CE for ; Mon, 1 Mar 2004 09:11:43 -0800 (PST) Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96ED643D3F for ; Mon, 1 Mar 2004 09:11:42 -0800 (PST) (envelope-from rik@cronyx.ru) Received: (from root@localhost) by hanoi.cronyx.ru id i21HB2BF051020 for freebsd-net@freebsd.org.checked; (8.12.8/vak/2.1) Mon, 1 Mar 2004 20:11:02 +0300 (MSK) (envelope-from rik@cronyx.ru) Received: from cronyx.ru (hi.cronyx.ru [144.206.181.94]) by hanoi.cronyx.ru with ESMTP id i21H873d050922 for ; (8.12.8/vak/2.1) Mon, 1 Mar 2004 20:08:07 +0300 (MSK) (envelope-from rik@cronyx.ru) Message-ID: <40436EB5.70503@cronyx.ru> Date: Mon, 01 Mar 2004 20:11:17 +0300 From: Roman Kurakin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031208 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Subject: Review request (ng_sppp) 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, 01 Mar 2004 17:11:43 -0000 Hi, I just release new version (1.3) of ng_sppp, that implements netgraph sppp node. This version from now should work on both 4.x and 5.x branches. I want to commit it to CURRENT, so if you have any suggestions/objections please let me know. Code can be downloaded from: http://users.inse.ru/~rik/ng_sppp/ng_sppp.tgz Best regards, Roman Kurakin From owner-freebsd-net@FreeBSD.ORG Mon Mar 1 09:56: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 F3DA516A4CE for ; Mon, 1 Mar 2004 09:56:31 -0800 (PST) Received: from relay2.mecon.ar (relay2.mecon.gov.ar [168.101.16.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 804A943D41 for ; Mon, 1 Mar 2004 09:56:30 -0800 (PST) (envelope-from juan@mecon.gov.ar) Received: from racing.mecon.ar (racing.mecon.gov.ar [168.101.133.15]) by relay2.mecon.ar (8.12.8p2/8.12.8) with ESMTP id i21HuSpf079862 for ; Mon, 1 Mar 2004 14:56:28 -0300 (ART) (envelope-from juan@mecon.gov.ar) Received: from racing.mecon.ar (meyosp.mecon.gov.ar [10.11.0.149]) by racing.mecon.ar (8.12.8p2/8.12.8) with ESMTP id i21HuSDR097614 for ; Mon, 1 Mar 2004 14:56:28 -0300 (ART) (envelope-from juan@mecon.gov.ar) Received: from bal740v0.mecon.gov.ar (bal740v0.mecon.ar [10.11.1.26]) by racing.mecon.ar (8.12.8p2/8.12.8) with ESMTP id i21HuR5T097597 for ; Mon, 1 Mar 2004 14:56:27 -0300 (ART) (envelope-from juan@mecon.gov.ar) Message-Id: <5.2.1.1.2.20040301142850.01edaf20@10.11.0.173> X-Sender: juan@10.11.0.173 (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Mon, 01 Mar 2004 14:56:26 -0300 To: freebsd-net@freebsd.org From: Juan Angel Menendez Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Multipath patches for FreeBSD 4.8, working on a single interface 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, 01 Mar 2004 17:56:32 -0000 Hi everyone I've just applied Tanzer's multipath routing patches over FreeBSD 4.8, compiled the kernel and everything worked fine. Basically, my idea is to load share default outgoing traffic over 2 redundant routers which are on the same LAN. I've tried the following: #test route add default -pathmetric 1 -gateway 10.10.16.2 -pathmetric 1 -gateway 10.10.17.2 add net default test# netstat -nr Routing tables Internet: Destination Gateway Flags/ Refs/ Use Netif Expire metric left default UGSc 114 100 xl0 10.10.16.2 1 0 xl0 *10.10.17.2 1 0 0 xl0 127.0.0.1 127.0.0.1 UH 10 1000001 lo0 10.10.16/21 link#1 UC 8 0 xl0 test# route -n get default route to: default destination: default mask: default cur gateway: 10.10.17.2 multipaths: 10.10.16.2 metric: 1 10.10.17.2 metric: 1 interface: xl0 flags: recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu expire 0 0 0 0 0 0 1500 0 sockaddrs: test# ifconfig xl0 xl0: flags=8843 mtu 1500 inet 10.10.16.11 netmask 0xfffff800 broadcast 10.10.23.255 inet6 fe80::260:8ff:fecc:bc81%xl0 prefixlen 64 scopeid 0x1 ether 00:60:08:cc:bc:81 media: Ethernet autoselect (100baseTX ) status: active I've tried getting a file from the server using ftp, but the kernel always seems to choose the same path, it doesn't round robin over different paths. I checked that watching the routers interface's counters. I've also tried -pathmetric 10 and no -pathmetric at all without luck. Configuration examples showed how to make it to work using 2 different NICs, has anyone managed to make it to work using a single NIC ? Maybe using aliasing ? Any help will be appreciated. Juan From owner-freebsd-net@FreeBSD.ORG Mon Mar 1 11:01: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 8603116A552 for ; Mon, 1 Mar 2004 11:01:42 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6891143D1D for ; Mon, 1 Mar 2004 11:01:42 -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 i21J1gbv054078 for ; Mon, 1 Mar 2004 11:01:42 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i21J1fD1054072 for freebsd-net@freebsd.org; Mon, 1 Mar 2004 11:01:41 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 1 Mar 2004 11:01:41 -0800 (PST) Message-Id: <200403011901.i21J1fD1054072@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, 01 Mar 2004 19:01:42 -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 Mar 1 14:18: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 309B316A4CF for ; Mon, 1 Mar 2004 14:18:35 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B4CE43D2F for ; Mon, 1 Mar 2004 14:18:34 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 96649 invoked from network); 1 Mar 2004 22:18:33 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.54]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 1 Mar 2004 22:18:33 -0000 Message-ID: <4043B6BA.B847F081@freebsd.org> Date: Mon, 01 Mar 2004 23:18:34 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-net@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: My planned work on networking stack 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, 01 Mar 2004 22:18:35 -0000 Hi all, I put this up for coordination and cooperation in my planned work on the FreeBSD networking system. This is my todo list of things I want to do from now through summer 04. If you are or intend to work on one of these please step forward so we can coordinate. :-) [] move ARP out of the routing table and instantiate it once per ethernet broadcast domain. (started) [] automatically sizing TCP send buffers to achieve optimal performance over a wide range of bw*delay situations. (in progress) [] establish a testbed for testing and qualification of TCP performance and optimizations over a wide range of network conditions (types, speeds, packet loss ratios, out of order, etc). (started) [] update and write more documentation for the network stack and related code. (started) [] adjust or rewrite the IPFW API to use the PFIL_HOOKS instead of being woven directly into ip input/output. (unless someone else does it) [] move IPv4 routing to its own optimized routing table structure and add multi-path and policy-routing options. (planned) [] profile (don't speculate) common network server usages overall and in specific detail in depth in the network code. (planned) [] write a network statistics (only local, no sniffing) gathering daemon that collects vital real world IP and TCP behaviourial statistics. (planned) [] rewrite (or port over NetBSDs) tcp_reass() function which is currently rather inefficient. (planned) [] remove TTCP complexity and replace it with something along the lines of TCP_MD5SIG to continue to allow fast connection setups but simpler in implementation. (Nothing fixed yet, up for discussion) [] other stuff that I happen to stumble over... ;-) -- Andre From owner-freebsd-net@FreeBSD.ORG Mon Mar 1 15:06: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 DE0A616A4CE for ; Mon, 1 Mar 2004 15:06:25 -0800 (PST) Received: from venus.vincentjardin.net (lns-th2-2-82-64-30-74.adsl.proxad.net [82.64.30.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id C168143D3F for ; Mon, 1 Mar 2004 15:06:24 -0800 (PST) (envelope-from jardin@venus.vincentjardin.net) Received: from venus.vincentjardin.net (localhost [127.0.0.1]) i21NAbi8000771; Tue, 2 Mar 2004 00:10:38 +0100 (CET) (envelope-from jardin@venus.vincentjardin.net) Received: from localhost (localhost [[UNIX: localhost]]) by venus.vincentjardin.net (8.12.9/8.12.9/Submit) id i21NAbTV000770; Tue, 2 Mar 2004 00:10:37 +0100 (CET) From: Vincent Jardin To: Roman Kurakin , freebsd-net@freebsd.org Date: Tue, 2 Mar 2004 00:10:33 +0100 User-Agent: KMail/1.5.2 References: <40436EB5.70503@cronyx.ru> In-Reply-To: <40436EB5.70503@cronyx.ru> MIME-Version: 1.0 Content-Type: Text/Plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Content-Description: clearsigned data Content-Disposition: inline Message-Id: <200403020010.37036.vjardin@free.fr> Subject: Re: Review request (ng_sppp) 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, 01 Mar 2004 23:06:26 -0000 Hi, I am wondering why do we need a new PPP node. There are already so many=20 implementations. If we need a Netgraph PPP support, mpd + ng_ppp seems to b= e=20 enough, doesn't it ? Regards, Vincent On Monday 01 March 2004 18:11, Roman Kurakin wrote: > Hi, > > I just release new version (1.3) of ng_sppp, that implements > netgraph sppp node. > This version from now should work on both 4.x and 5.x branches. > > I want to commit it to CURRENT, so if you have any > suggestions/objections > please let me know. > > Code can be downloaded from: > > http://users.inse.ru/~rik/ng_sppp/ng_sppp.tgz > > Best regards, > Roman Kurakin > > > > _______________________________________________ > 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 Mon Mar 1 15:07: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 88AE616A4CF; Mon, 1 Mar 2004 15:07:59 -0800 (PST) Received: from smtp.omnis.com (smtp.omnis.com [216.239.128.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 560C843D1D; Mon, 1 Mar 2004 15:07:59 -0800 (PST) (envelope-from wes@softweyr.com) Received: from salty.rapid.stbernard.com (unknown [198.147.128.71]) by smtp-relay.omnis.com (Postfix) with ESMTP id 9B2C1FCECB; Mon, 1 Mar 2004 15:07:57 -0800 (PST) From: Wes Peters Organization: Softweyr.com To: Andre Oppermann , freebsd-current@freebsd.org, freebsd-net@freebsd.org Date: Mon, 1 Mar 2004 15:07:52 -0800 User-Agent: KMail/1.5.4 References: <4043B6BA.B847F081@freebsd.org> In-Reply-To: <4043B6BA.B847F081@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200403011507.52238.wes@softweyr.com> Subject: Re: My planned work on networking stack 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, 01 Mar 2004 23:07:59 -0000 On Monday 01 March 2004 14:18, Andre Oppermann wrote: > Hi all, > > I put this up for coordination and cooperation in my planned work on the > FreeBSD networking system. This is my todo list of things I want to do > from now through summer 04. If you are or intend to work on one of these > please step forward so we can coordinate. :-) > > [] move ARP out of the routing table and instantiate it once per > ethernet broadcast domain. (started) Yay! > [] automatically sizing TCP send buffers to achieve optimal performance > over a wide range of bw*delay situations. (in progress) What a wonderful idea. Can't wait for the bikesheds... > [] establish a testbed for testing and qualification of TCP performance > and optimizations over a wide range of network conditions (types, > speeds, packet loss ratios, out of order, etc). (started) Be sure to coordinate with the donations officer for help in getting equipment you may need. > [] update and write more documentation for the network stack and related > code. (started) Yay! > [] adjust or rewrite the IPFW API to use the PFIL_HOOKS instead of being > woven directly into ip input/output. (unless someone else does it) > > [] move IPv4 routing to its own optimized routing table structure and > add multi-path and policy-routing options. (planned) Will the table code in PF be helpful in this area? They seem to have developed a reasonably small notation for CIDR-type address ranges and code that does best-fit matching. > [] profile (don't speculate) common network server usages overall and > in specific detail in depth in the network code. (planned) > > [] write a network statistics (only local, no sniffing) gathering daemon > that collects vital real world IP and TCP behaviourial statistics. > (planned) > > [] rewrite (or port over NetBSDs) tcp_reass() function which is > currently rather inefficient. (planned) > > [] remove TTCP complexity and replace it with something along the lines > of TCP_MD5SIG to continue to allow fast connection setups but simpler > in implementation. (Nothing fixed yet, up for discussion) > > [] other stuff that I happen to stumble over... ;-) Wowsers. I can't wait to hear more. When do you expect to have a design for the ARP stuff and TCP buffer sizing, since they are underway? -- "Where am I, and what am I doing in this handbasket?" Wes Peters wes@softweyr.com From owner-freebsd-net@FreeBSD.ORG Mon Mar 1 17:37: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 A4E6016A4CE; Mon, 1 Mar 2004 17:37:57 -0800 (PST) Received: from ftp.ccrle.nec.de (ftp.netlab.nec.de [195.37.70.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B381343D3F; Mon, 1 Mar 2004 17:37:56 -0800 (PST) (envelope-from lars.eggert@netlab.nec.de) Received: from netlab.nec.de (unknown [218.145.160.102]) by ftp.ccrle.nec.de (Postfix) with ESMTP id BBE61F5A9; Tue, 2 Mar 2004 02:42:35 +0100 (CET) Message-ID: <4043E565.6070703@netlab.nec.de> Date: Tue, 02 Mar 2004 10:37:41 +0900 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: Wes Peters References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> In-Reply-To: <200403011507.52238.wes@softweyr.com> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms090905090505090104050505" cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: Andre Oppermann Subject: Re: My planned work on networking stack 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, 02 Mar 2004 01:37:57 -0000 This is a cryptographically signed message in MIME format. --------------ms090905090505090104050505 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi, Wes Peters wrote: > On Monday 01 March 2004 14:18, Andre Oppermann wrote: > >> [] establish a testbed for testing and qualification of TCP performance >> and optimizations over a wide range of network conditions (types, >> speeds, packet loss ratios, out of order, etc). (started) > > Be sure to coordinate with the donations officer for help in getting > equipment you may need. this sounds like something you could do with planetlab (http://planet-lab.org/). Do you have access? (Or maybe I misunderstood what you meant by "testbed".) Lars -- Lars Eggert NEC Network Laboratories --------------ms090905090505090104050505 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 AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDQwMzAyMDEzNzQxWjAjBgkqhkiG 9w0BCQQxFgQU7mBcRRPDBZQF4zWm2oFqDeoKTvowUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgweAYJKwYBBAGCNxAEMWswaTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3Rl IENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt YWlsIElzc3VpbmcgQ0ECAwtTojB6BgsqhkiG9w0BCRACCzFroGkwYjELMAkGA1UEBhMCWkEx JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0 ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAgMLU6IwDQYJKoZIhvcNAQEBBQAEggEA TsIW20zOsIiJ5qngZ9OCnaOjxn2Vg6OXvFGqdid0lbRkF9Nvojq9jj6Pg1X3N9IWcmkOxbbE usATAVUTBEpoZg3aAJ4E5RmGfVedgVH/bWzU9jl5oXUmjXfIzsE5915xn+FBkaNUBp03HpDd aBFhgNTNeQVaa4e2o4ZiNNtZpnr2i6SVkKNCZ1zLaqoRNGAJWPn9PtsmajK8UWd7+NFyzNhz vsomQiDz46mhQ1e97Oi3fSXDJzftJ7i2Ikj/kyZYOSFGVuJ2uspN8vRiFcaeYIFIuQnO5K+o r9oSNM2d9RwkeSiv5aX9AFcroLX0OIXPgTICtaRKYgPEBE5rWPNJ8gAAAAAAAA== --------------ms090905090505090104050505-- From owner-freebsd-net@FreeBSD.ORG Mon Mar 1 17:42: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 D81BD16A4CE; Mon, 1 Mar 2004 17:42:37 -0800 (PST) Received: from ftp.ccrle.nec.de (ftp.netlab.nec.de [195.37.70.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4828443D2D; Mon, 1 Mar 2004 17:42:37 -0800 (PST) (envelope-from lars.eggert@netlab.nec.de) Received: from netlab.nec.de (unknown [218.145.160.102]) by ftp.ccrle.nec.de (Postfix) with ESMTP id 1ACEDF5A9; Tue, 2 Mar 2004 02:47:19 +0100 (CET) Message-ID: <4043E681.3090705@netlab.nec.de> Date: Tue, 02 Mar 2004 10:42:25 +0900 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: Lars Eggert References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <4043E565.6070703@netlab.nec.de> In-Reply-To: <4043E565.6070703@netlab.nec.de> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms080304060608040905080908" cc: freebsd-current@freebsd.org cc: Andre Oppermann cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 01:42:38 -0000 This is a cryptographically signed message in MIME format. --------------ms080304060608040905080908 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Lars Eggert wrote: > > this sounds like something you could do with planetlab > (http://planet-lab.org/). Do you have access? (Or maybe I misunderstood > what you meant by "testbed".) Argh. Yes, it runs Linux. Yes, I'm jet lagged. (But there was some talk about running something else on planetlab at some point.) Sorry for the noise, Lars -- Lars Eggert NEC Network Laboratories --------------ms080304060608040905080908 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 AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDQwMzAyMDE0MjI1WjAjBgkqhkiG 9w0BCQQxFgQUyF08Bd/jxOsDOWAGyZLXX5A4Dp8wUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG 9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN AwICASgweAYJKwYBBAGCNxAEMWswaTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3Rl IENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt YWlsIElzc3VpbmcgQ0ECAwtTojB6BgsqhkiG9w0BCRACCzFroGkwYjELMAkGA1UEBhMCWkEx JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0 ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAgMLU6IwDQYJKoZIhvcNAQEBBQAEggEA KL5JPFrF8xPJbFWmdzipSO2KEx99QzVyQARASf8hV9e/nE82Vz210SpvbGvVP8DvJsN8vrRD QHlenjPEGNC0MlnbMVbuhEvq+revuEyrDUx2Zo2MFb+JG2m87hipnUtZ8dYqBqKJws051FQZ Dktrtw1t5M41aJRyi0pk1TQOGYU6JB81qLJ7fVxkb/U3KUOLGwPSFm8p15ZmguFsyGcQlGU8 1I5L97oGaU0MwWlQsa1MfzAHcBUO+JzCpineA6dmTLkZBtSicVgbq3hYVv/kyzn1HIpo+l4e a/K/gwfB9hP36WkpKmR8VvXV1ewnMGgKGIXo8vaIWxUd0sJtAbM5ngAAAAAAAA== --------------ms080304060608040905080908-- From owner-freebsd-net@FreeBSD.ORG Mon Mar 1 17:43:33 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 87F4516A4CE; Mon, 1 Mar 2004 17:43:33 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 639FE43D2F; Mon, 1 Mar 2004 17:43:33 -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 i221hLKH026168; Mon, 1 Mar 2004 17:43:24 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i221hKoD026157; Mon, 1 Mar 2004 17:43:20 -0800 Date: Mon, 1 Mar 2004 17:43:19 -0800 From: Brooks Davis To: Lars Eggert Message-ID: <20040302014319.GA24639@Odin.AC.HMC.Edu> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <4043E565.6070703@netlab.nec.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bg08WKrSYDhXBjb5" Content-Disposition: inline In-Reply-To: <4043E565.6070703@netlab.nec.de> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: freebsd-current@freebsd.org cc: Andre Oppermann cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 01:43:33 -0000 --bg08WKrSYDhXBjb5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 02, 2004 at 10:37:41AM +0900, Lars Eggert wrote: > Hi, >=20 > Wes Peters wrote: > >On Monday 01 March 2004 14:18, Andre Oppermann wrote: > > > >>[] establish a testbed for testing and qualification of TCP performance > >> and optimizations over a wide range of network conditions (types, > >> speeds, packet loss ratios, out of order, etc). (started) > > > >Be sure to coordinate with the donations officer for help in getting=20 > >equipment you may need. >=20 > this sounds like something you could do with planetlab=20 > (http://planet-lab.org/). Do you have access? (Or maybe I misunderstood= =20 > what you meant by "testbed".) =46rom the list of metrics, Emulab (http://www.emulab.net/) is probably more what he's thinking, but we probably ought to let Andre speak for him self. :-) -- 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 --bg08WKrSYDhXBjb5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAQ+arXY6L6fI4GtQRAhanAKDKdTy5RNVu1lLixbUblt1gxitX8gCfa35p ozwSvFI6N5E4Bgy20+qDYzE= =JOOf -----END PGP SIGNATURE----- --bg08WKrSYDhXBjb5-- From owner-freebsd-net@FreeBSD.ORG Mon Mar 1 17:57:41 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 7A20016A4CE; Mon, 1 Mar 2004 17:57:41 -0800 (PST) Received: from daemon.kr.FreeBSD.org (daemon.kr.freebsd.org [61.78.53.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C7CB43D1F; Mon, 1 Mar 2004 17:57:41 -0800 (PST) (envelope-from cjh@kr.FreeBSD.org) Received: from localhost (gradius [211.44.63.164]) by daemon.kr.FreeBSD.org (Postfix) with ESMTP id 681931A773; Tue, 2 Mar 2004 10:57:37 +0900 (KST) Date: Tue, 02 Mar 2004 10:57:38 +0900 (KST) Message-Id: <20040302.105738.112592844.cjh@kr.FreeBSD.org> To: andre@freebsd.org, freebsd-current@freebsd.org, freebsd-net@freebsd.org From: CHOI Junho In-Reply-To: <200403011507.52238.wes@softweyr.com> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> Organization: Korea FreeBSD Users Group X-URL: http://www.kr.FreeBSD.org/~cjh X-Mailer: Mew version 4.0.64 on Emacs 21.3.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: My planned work on networking stack 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, 02 Mar 2004 01:57:41 -0000 From: Wes Peters Subject: Re: My planned work on networking stack Date: Mon, 1 Mar 2004 15:07:52 -0800 > On Monday 01 March 2004 14:18, Andre Oppermann wrote: > > Hi all, > > > > [] automatically sizing TCP send buffers to achieve optimal performance > > over a wide range of bw*delay situations. (in progress) > > What a wonderful idea. Can't wait for the bikesheds... Me too. Also it would be very helpful if we have Selective ACK(SACK) feature. -- CHOI Junho KFUG FreeBSD Project Web Data Bank Key fingerprint = 1369 7374 A45F F41A F3C0 07E3 4A01 C020 E602 60F5 From owner-freebsd-net@FreeBSD.ORG Mon Mar 1 17:59:48 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 DA74516A4CE; Mon, 1 Mar 2004 17:59:48 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2F7143D2F; Mon, 1 Mar 2004 17:59:48 -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 i221xhKH030408; Mon, 1 Mar 2004 17:59:43 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i221xhsS030407; Mon, 1 Mar 2004 17:59:43 -0800 Date: Mon, 1 Mar 2004 17:59:42 -0800 From: Brooks Davis To: CHOI Junho Message-ID: <20040302015942.GA30219@Odin.AC.HMC.Edu> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302.105738.112592844.cjh@kr.FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sdtB3X0nJg68CQEu" Content-Disposition: inline In-Reply-To: <20040302.105738.112592844.cjh@kr.FreeBSD.org> 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: freebsd-current@freebsd.org cc: andre@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 01:59:49 -0000 --sdtB3X0nJg68CQEu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 02, 2004 at 10:57:38AM +0900, CHOI Junho wrote: > From: Wes Peters > Subject: Re: My planned work on networking stack > Date: Mon, 1 Mar 2004 15:07:52 -0800 >=20 > > On Monday 01 March 2004 14:18, Andre Oppermann wrote: > > > Hi all, > > > > > > [] automatically sizing TCP send buffers to achieve optimal performa= nce > > > over a wide range of bw*delay situations. (in progress) > >=20 > > What a wonderful idea. Can't wait for the bikesheds... >=20 > Me too. Also it would be very helpful if we have Selective ACK(SACK) feat= ure. I may have someone intrested in doing this work. I'll ask them again and see if I can pin them down. -- 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 --sdtB3X0nJg68CQEu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAQ+qOXY6L6fI4GtQRAhy7AJ9Bl60kI33xENJRPJyfgPnp5iJ8ZwCeLEes r+lCA5lwxV6Ft5JnFGe65iY= =cY84 -----END PGP SIGNATURE----- --sdtB3X0nJg68CQEu-- From owner-freebsd-net@FreeBSD.ORG Mon Mar 1 19:15: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 682DE16A4CE; Mon, 1 Mar 2004 19:15:59 -0800 (PST) Received: from mx01.bos.ma.towardex.com (a65-124-16-8.svc.towardex.com [65.124.16.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DB4143D31; Mon, 1 Mar 2004 19:15:59 -0800 (PST) (envelope-from haesu@mx01.bos.ma.towardex.com) Received: by mx01.bos.ma.towardex.com (TowardEX ESMTP 3.0p11_DAKN, from userid 1001) id 523652F91A; Mon, 1 Mar 2004 22:16:25 -0500 (EST) Date: Mon, 1 Mar 2004 22:16:25 -0500 From: James To: Wes Peters Message-ID: <20040302031625.GA4061@scylla.towardex.com> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200403011507.52238.wes@softweyr.com> User-Agent: Mutt/1.4.1i cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: Andre Oppermann Subject: Re: My planned work on networking stack 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, 02 Mar 2004 03:15:59 -0000 > > [] move IPv4 routing to its own optimized routing table structure and finally it's about time :) > > add multi-path and policy-routing options. (planned) would the policy-routing optioned table sort of similar to VRF's or different routing instances that could potentially be tied to userlands like Quagga? -J -- James Jun TowardEX Technologies, Inc. Technical Lead Network Design, Consulting, IT Outsourcing james@towardex.com Boston-based Colocation & Bandwidth Services cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net From owner-freebsd-net@FreeBSD.ORG Mon Mar 1 20:30: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 5405316A4CE; Mon, 1 Mar 2004 20:30:00 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2261043D1D; Mon, 1 Mar 2004 20:30:00 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 3157E6520E; Tue, 2 Mar 2004 04:29:59 +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 19689-01-2; Tue, 2 Mar 2004 04:29:58 +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 00F6B651FA; Tue, 2 Mar 2004 04:29:58 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id 278D637; Tue, 2 Mar 2004 04:29:57 +0000 (GMT) Date: Tue, 2 Mar 2004 04:29:57 +0000 From: Bruce M Simpson To: James Message-ID: <20040302042957.GH3841@saboteur.dek.spc.org> Mail-Followup-To: James , Wes Peters , freebsd-net@freebsd.org, freebsd-current@freebsd.org, Andre Oppermann References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040302031625.GA4061@scylla.towardex.com> cc: freebsd-current@freebsd.org cc: Andre Oppermann cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 04:30:00 -0000 On Mon, Mar 01, 2004 at 10:16:25PM -0500, James wrote: > > > [] move IPv4 routing to its own optimized routing table structure and > > finally it's about time :) I've been fielding suggestions from individuals who feel using a multi-bit trie might be more suitable for achieving higher PPS rates. > > > add multi-path and policy-routing options. (planned) > > would the policy-routing optioned table sort of similar to VRF's or > different routing instances that could potentially be tied to userlands > like Quagga? That's the plan, I believe, anyway... It would be nice if Quagga could be taught about how to add TCP-MD5 keys to both FreeBSD and OpenBSD SADBs. BMS From owner-freebsd-net@FreeBSD.ORG Mon Mar 1 20:31:56 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A588E16A4CE; Mon, 1 Mar 2004 20:31:56 -0800 (PST) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 652DE43D1D; Mon, 1 Mar 2004 20:31:56 -0800 (PST) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i224Vl7E096787; Mon, 1 Mar 2004 20:31:51 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200403020431.i224Vl7E096787@gw.catspoiler.org> Date: Mon, 1 Mar 2004 20:31:47 -0800 (PST) From: Don Lewis To: andre@FreeBSD.org In-Reply-To: <4043B6BA.B847F081@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: freebsd-net@FreeBSD.org cc: freebsd-current@FreeBSD.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 04:31:56 -0000 On 1 Mar, Andre Oppermann wrote: > [] move ARP out of the routing table and instantiate it once per ethernet > broadcast domain. (started) Applause! From owner-freebsd-net@FreeBSD.ORG Mon Mar 1 23:57:52 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDFAD16A4CE for ; Mon, 1 Mar 2004 23:57:51 -0800 (PST) Received: from mail019.syd.optusnet.com.au (mail019.syd.optusnet.com.au [211.29.132.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id E252943D2F for ; Mon, 1 Mar 2004 23:57:47 -0800 (PST) (envelope-from tfrank@optushome.com.au) Received: from marvin.home.local (c211-28-241-126.eburwd5.vic.optusnet.com.au [211.28.241.126])i227vgB08930; Tue, 2 Mar 2004 18:57:43 +1100 Received: by marvin.home.local (Postfix, from userid 1001) id 41F7C1FBA7; Tue, 2 Mar 2004 18:57:42 +1100 (EST) Date: Tue, 2 Mar 2004 18:57:42 +1100 From: Tony Frank To: Ian Smith Message-ID: <20040302075742.GA18966@marvin.home.local> References: <20040227151405.GA5540@marvin.home.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: freebsd-net@freebsd.org Subject: Re: Bad loopback traffic not stopped by 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: Tue, 02 Mar 2004 07:57:52 -0000 Hi, Bit of a delayed response I'm afraid - PC troubles. On Sun, Feb 29, 2004 at 01:28:23AM +1100, Ian Smith wrote: > On Sat, 28 Feb 2004, Tony Frank wrote (in freebsd-net@freebsd.org): > > > On Wed, Feb 25, 2004 at 05:21:34PM +0300, Gleb Smirnoff wrote: > > > On Wed, Feb 25, 2004 at 04:19:51PM +0200, Iasen Kostov wrote: > > > I> >>16:26:23.287642 0:1:2:9>c:cf:e2 0:02:55:b0:90:e4 0800 60: 127.0.0.1.80 > > > > I> >>192.168.118.205.1046: R 0:0(0) ack 1959723009 win 0 > > > I> > > > > I> >This is some kind of Win32 virus. This floods can be easily > > > I> >stopped by ipfw rule: > > > I> > > > > I> >deny tcp from any to any tcpflags rst,ack > > > I> > > > > I> These packets never reach IPFW as we can see. > > > > > > Ughu. Really. > > > But I have millions of them from non-localhost addresses. > > > > > > > This maybe is of interest? > > > > http://www.dshield.org/pipermail/list/2004-January/014027.php > > I'm sorry Tony, call me thick, but I couldn't see the relevance of this > posting "[Dshield] ISPs - How much monitoring is enough?" to the topic > regarding these inbound packets 'from' 127.0.0.1:80 ? I'm kind of > curious though, having seen several hundred of these (blocked by ipfw on > an ol' 2.2.6 system) over the last couple of weeks. > > Looks like an interesting list for such stuff, though; had a browse. The link seems to have changed. Checking it now I find something unrelated. Too much mail, too little sleep. Specifically on the question at hand regarding 127.0.0.1.80 business it seems to be relating to blaster and some aspects of how some admins tried to stop it. I'm including the message text (was a cross from securityfocus): -----Forwarded Message----- From: Dan Hanson To: incidents at securityfocus.com Subject: Administrivia: Are you seeing portscans from source 127.0.0.1 source port 80? Date: Tue, 28 Oct 2003 08:59:56 -0700 I am posting this in the hopes of dulling the 5-6 messages I get every day that are reporting port scans to their network all of which have a source IP of 127.0.0.1 and source port 80. It is likely Blaster (check your favourite AV site for a writeup, I won't summarize here). The reason that people are seeing this has to do with some very bad advice that was given early in the blaster outbreak. The advice basically was that to protect the Internet from the DoS attack that was to hit windowsupdate.com, all DNS servers should return 127.0.0.1 for queries to windowsupdate.com. Essentially these suggestions were suggesting that hosts should commit suicide to protect the Internet. The problem is that the DoS routine spoofs the source address, so when windowsupdate.com resolves to 127.0.0.1 the following happens. Infected host picks address as source address and sends Syn packet to 127.0.0.1 port 80. (Sends it to itself) (This never makes it on the wire, you will not see this part) TCP/IP stack receives packet, responds with reset (if there is nothing listening on that port), sending the reset to the host with the spoofed source address (this is what people are seeing and mistaking for portscans) Result: It looks like a host is port scanning ephemeral posts using packets with source address:port of 127.0.0.1:80 Solution: track back the packets by MAC address to find hte infected machine. Turn of NS resolution of windowsupdate.com to 127.0.0.1. Hope that helps D --------------------------------------------------------------------------- Regards, Tony From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 00:26: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 F04B716A4CE; Tue, 2 Mar 2004 00:26:28 -0800 (PST) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id E286E43D2F; Tue, 2 Mar 2004 00:26:27 -0800 (PST) (envelope-from glebius@cell.sick.ru) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.9/8.12.8) with ESMTP id i228QPQE023512 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Mar 2004 11:26:26 +0300 (MSK) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.9/8.12.6/Submit) id i228QPV2023511; Tue, 2 Mar 2004 11:26:25 +0300 (MSK) Date: Tue, 2 Mar 2004 11:26:25 +0300 From: Gleb Smirnoff To: Wes Peters , Andre Oppermann Message-ID: <20040302082625.GE22985@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Wes Peters , Andre Oppermann , freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20040302042957.GH3841@saboteur.dek.spc.org> User-Agent: Mutt/1.5.6i cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 08:26:29 -0000 Dear sirs, On Tue, Mar 02, 2004 at 04:29:57AM +0000, Bruce M Simpson wrote: B> > > > add multi-path and policy-routing options. (planned) B> > B> > would the policy-routing optioned table sort of similar to VRF's or B> > different routing instances that could potentially be tied to userlands B> > like Quagga? B> B> That's the plan, I believe, anyway... It would be nice if Quagga could be B> taught about how to add TCP-MD5 keys to both FreeBSD and OpenBSD SADBs. Is there any plans about integration of BGP routing daemon (Zebra or Quagga) into FreeBSD? With BGP routing daemon onboard, FreeBSD will be a strong alternative against expensive commercial routers. I have successfull experience of running FreeBSD STABLE with 2 full BGP views for half a year. Modern i386 PC can route/filter/shape much more traffic than expensive Cisco 36xx. I haven't yet compared with 7000 series... Currently I'm working on my Netflow implementation, and I have faced the following problem: I've already got global routing in my routing table, but it lacks AS (Autonomous System) information. The routing daemon (zebra in my case) already knows ASes, but this informations is lost when routing information is injected into kernel. It'll be nice to add AS path to struct rtentry. Seems like there is no problem with extending struct rtentry, but injecting this info from userland requires changes to routing API. I see two ways of implementing it: 1) Simply add new field into struct rt_msghdr, and bump RTM_VERSION. I have done this, it works. But I don't like it, since RTM_VERSION has changed. 2) Create new sockaddr, called sockaddr_aspath. Define RTAX_ASPATH, increase RTAX_MAX. Pass this sockaddr_aspath in rti_info[] array of a routing message into kernel. Unparse it in the kernel, fill in new field of struct rtentry. While I haven't yet started working on 2), I'd be very glad to hear comments from FreeBSD developers. Thanks in advance. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 00:43: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 2BFF216A4CE; Tue, 2 Mar 2004 00:43:36 -0800 (PST) Received: from mtaw4.prodigy.net (mtaw4.prodigy.net [64.164.98.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id D24EF43D2D; Tue, 2 Mar 2004 00:43:32 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (2f35a21d9d0e5b0422487a99eb48a3d3@adsl-67-119-53-203.dsl.lsan03.pacbell.net [67.119.53.203]) by mtaw4.prodigy.net (8.12.10/8.12.10) with ESMTP id i228hMd6006710; Tue, 2 Mar 2004 00:43:23 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B03D051377; Tue, 2 Mar 2004 00:43:21 -0800 (PST) Date: Tue, 2 Mar 2004 00:43:21 -0800 From: Kris Kennaway To: Gleb Smirnoff , Wes Peters , Andre Oppermann , freebsd-net@freebsd.org, freebsd-current@freebsd.org Message-ID: <20040302084321.GA21729@xor.obsecurity.org> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline In-Reply-To: <20040302082625.GE22985@cell.sick.ru> User-Agent: Mutt/1.4.2.1i Subject: Re: My planned work on networking stack 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, 02 Mar 2004 08:43:36 -0000 --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 02, 2004 at 11:26:25AM +0300, Gleb Smirnoff wrote: > Dear sirs, >=20 > On Tue, Mar 02, 2004 at 04:29:57AM +0000, Bruce M Simpson wrote: > B> > > > add multi-path and policy-routing options. (planned) > B> >=20 > B> > would the policy-routing optioned table sort of similar to VRF's or > B> > different routing instances that could potentially be tied to userl= ands > B> > like Quagga? > B>=20 > B> That's the plan, I believe, anyway... It would be nice if Quagga could= be > B> taught about how to add TCP-MD5 keys to both FreeBSD and OpenBSD SADBs. >=20 > Is there any plans about integration of BGP routing daemon (Zebra or Qu= agga) > into FreeBSD? With BGP routing daemon onboard, FreeBSD will be a strong > alternative against expensive commercial routers. What's wrong with installing the port if you want this? Kris --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAREkpWry0BWjoQKURAheTAJ4rH4QHDx/hhQasvk2FlFeUWoZEfgCfQu6G LvJ5q++fibxdEaHStlBPnpo= =2quf -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o-- From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 00:56: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 062D516A4D1; Tue, 2 Mar 2004 00:56:00 -0800 (PST) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 426C343D1F; Tue, 2 Mar 2004 00:55:59 -0800 (PST) (envelope-from glebius@cell.sick.ru) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.9/8.12.8) with ESMTP id i228tuQE023793 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Mar 2004 11:55:57 +0300 (MSK) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.9/8.12.6/Submit) id i228tu0i023792; Tue, 2 Mar 2004 11:55:56 +0300 (MSK) Date: Tue, 2 Mar 2004 11:55:56 +0300 From: Gleb Smirnoff To: Kris Kennaway Message-ID: <20040302085556.GA23734@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Kris Kennaway , Wes Peters , Andre Oppermann , freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20040302084321.GA21729@xor.obsecurity.org> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org cc: Andre Oppermann cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 08:56:00 -0000 On Tue, Mar 02, 2004 at 12:43:21AM -0800, Kris Kennaway wrote: K> > B> That's the plan, I believe, anyway... It would be nice if Quagga could be K> > B> taught about how to add TCP-MD5 keys to both FreeBSD and OpenBSD SADBs. K> > K> > Is there any plans about integration of BGP routing daemon (Zebra or Quagga) K> > into FreeBSD? With BGP routing daemon onboard, FreeBSD will be a strong K> > alternative against expensive commercial routers. K> K> What's wrong with installing the port if you want this? Read on my previous mail pls. I'm speaking of some changes that require altering both FreeBSD and routing daemon. Currently I'm thinking of AS path only, but in future some other issues can appear. Routing daemon should be close to operating system it is running on. FreeBSD has RIP routing daemon - routed, but no OSPF/BGP one. I think OSPF and BGP are much more used nowadays, than RIP. Also, I'd be appreciated if you comment the second part of my mail. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 01:02: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 2AD9716A4CE; Tue, 2 Mar 2004 01:02:32 -0800 (PST) Received: from tiamat.astral-on.net (mail.astral-on.net [193.41.4.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2759843D3F; Tue, 2 Mar 2004 01:02:30 -0800 (PST) (envelope-from ad@astral-on.net) Received: from odin.astral-on.net (odin.astral-on.net [193.41.4.6]) by mail.astral-on.net (8.12.11/8.12.11) with ESMTP id i2292LfS018910 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Mar 2004 11:02:21 +0200 (EET) (envelope-from ad@astral-on.net) Received: from odin.astral-on.net (localhost.astral-on.net [127.0.0.1]) by odin.astral-on.net (8.12.8p2/8.12.8) with ESMTP id i2292L41008953; Tue, 2 Mar 2004 11:02:21 +0200 (EET) (envelope-from ad@odin.astral-on.net) Received: (from ad@localhost) by odin.astral-on.net (8.12.8p2/8.12.8/Submit) id i2292KQq008952; Tue, 2 Mar 2004 11:02:20 +0200 (EET) Date: Tue, 2 Mar 2004 11:02:19 +0200 From: Andrew Degtiariov To: freebsd-net@freebsd.org, freebsd-current@freebsd.org Message-ID: <20040302090219.GC3438@astral-on.net> Mail-Followup-To: freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040302084321.GA21729@xor.obsecurity.org> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,DEAR_SOMETHING autolearn=no version=2.63 X-Spam-Report: * 2.3 DEAR_SOMETHING BODY: Contains 'Dear (something)' * -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on tiamat.astral-on.net Subject: Re: My planned work on networking stack X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ad@astral-on.net List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2004 09:02:32 -0000 On Tue, Mar 02, 2004 at 12:43:21AM -0800, Kris Kennaway wrote: > On Tue, Mar 02, 2004 at 11:26:25AM +0300, Gleb Smirnoff wrote: > > Dear sirs, > > > > On Tue, Mar 02, 2004 at 04:29:57AM +0000, Bruce M Simpson wrote: > > B> > > > add multi-path and policy-routing options. (planned) > > B> > > > B> > would the policy-routing optioned table sort of similar to VRF's or > > B> > different routing instances that could potentially be tied to userlands > > B> > like Quagga? > > B> > > B> That's the plan, I believe, anyway... It would be nice if Quagga could be > > B> taught about how to add TCP-MD5 keys to both FreeBSD and OpenBSD SADBs. > > > > Is there any plans about integration of BGP routing daemon (Zebra or Quagga) > > into FreeBSD? With BGP routing daemon onboard, FreeBSD will be a strong > > alternative against expensive commercial routers. > > What's wrong with installing the port if you want this? What's difference (*currently*) beetwen FreeBSD+Zebra and Cisco routers? FreeBSD+Zebra does not provide that functionality, what alredy have Cisco routers. But is possible to reduce its difference by slightly modifying kernel routing API. -- Andrew Degtiariov DA-RIPE From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 01:26: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 BB9A416A4CE for ; Tue, 2 Mar 2004 01:26:31 -0800 (PST) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B7FC43D31 for ; Tue, 2 Mar 2004 01:26:31 -0800 (PST) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.30; FreeBSD) id 1Ay6Bt-0003ba-8N; Tue, 02 Mar 2004 12:27:53 +0300 From: Vladimir Grebenschikov To: Gleb Smirnoff , freebsd-net In-Reply-To: <20040302082625.GE22985@cell.sick.ru> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: TSB "Russian Express" Message-Id: <1078219671.1054.26.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.5.4FreeBSD GNOME Team Port Date: Tue, 02 Mar 2004 12:27:52 +0300 Sender: Vladimir Grebenschikov Subject: Re: My planned work on networking stack X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: vova@express.ru List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2004 09:26:31 -0000 On =D7=D4, 2004-03-02 at 11:26 +0300, Gleb Smirnoff wrote: Hi > Currently I'm working on my Netflow implementation, and I have faced th= e > following problem: I've already got global routing in my routing table, b= ut it > lacks AS (Autonomous System) information. The routing daemon (zebra in my= case) > already knows ASes, but this informations is lost when routing informatio= n is > injected into kernel. It'll be nice to add AS path to struct rtentry. > Seems like there is no problem with extending struct rtentry, but injec= ting > this info from userland requires changes to routing API. I see two ways o= f > implementing it: What for you need have as-path in FIB (forwarding information base) ? If you are going to do as-path policy routing then , I think, it is invalid solution, because on next step you will import community-list into FIB, and etc. IMHO, Better solution will be ability to refer from route entry some additional route information block, and then (on phase of routing decision) examine this block by loadable routing decisions modules. So, any 3rd-party software (like zebra) will install it's own routing decisions module(s) and supply additional routing information blocks (not stored in rtentry). Anyway kernel still should have ability to add more then one entry for single prefix to FIB. > 1) Simply add new field into struct rt_msghdr, and bump RTM_VERSION. I = have > done this, it works. But I don't like it, since RTM_VERSION has chan= ged. > 2) Create new sockaddr, called sockaddr_aspath. Define RTAX_ASPATH, inc= rease > RTAX_MAX. Pass this sockaddr_aspath in rti_info[] array of a routing= message > into kernel. Unparse it in the kernel, fill in new field of struct r= tentry. >=20 > While I haven't yet started working on 2), I'd be very glad to hear comme= nts > from FreeBSD developers. Thanks in advance. >=20 > --=20 > Totus tuus, Glebius. > GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 01:28: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 D572C16A4CE; Tue, 2 Mar 2004 01:28:30 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id A22FF43D1D; Tue, 2 Mar 2004 01:28:30 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id CFA7D654D3; Tue, 2 Mar 2004 09:28:29 +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 21986-03-9; Tue, 2 Mar 2004 09:28:29 +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 82E0B65490; Tue, 2 Mar 2004 09:28:26 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id AA47218; Tue, 2 Mar 2004 09:28:25 +0000 (GMT) Date: Tue, 2 Mar 2004 09:28:25 +0000 From: Bruce M Simpson To: Gleb Smirnoff , Kris Kennaway , Wes Peters , Andre Oppermann , freebsd-net@freebsd.org, freebsd-current@freebsd.org Message-ID: <20040302092825.GD884@saboteur.dek.spc.org> Mail-Followup-To: Gleb Smirnoff , Kris Kennaway , Wes Peters , Andre Oppermann , freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> <20040302085556.GA23734@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040302085556.GA23734@cell.sick.ru> Subject: Re: My planned work on networking stack 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, 02 Mar 2004 09:28:31 -0000 On Tue, Mar 02, 2004 at 11:55:56AM +0300, Gleb Smirnoff wrote: > Read on my previous mail pls. I'm speaking of some changes that require > altering both FreeBSD and routing daemon. Currently I'm thinking of AS path > only, but in future some other issues can appear. Routing daemon should be close > to operating system it is running on. FreeBSD has RIP routing daemon - routed, but > no OSPF/BGP one. I think OSPF and BGP are much more used nowadays, than RIP. That may be so, but it would be unreasonable to force Quagga/Zebra on all users and add them to the cost of maintaining the base system as it stands; especially so given that there are other alternatives out there (MRTD, for example, gated, and XORP...). routed we support largely out of nostalgia, I guess. I wouldn't mind seeing it retired to ports eventually, but there are still people out there running RIP on their networks (I'm one of them, and before anyone shoots me, it's purely an equipment limitation -- the rest of my network runs OSPF and BGP). However, not including an OSPF/BGP daemon doesn't preclude us from ensuring that APIs which are exposed for advanced routing functionality (multipath, etc) do the right thing across the board, are well defined, etc. As to the second part of your mail: That sounds like a reasonable suggestion, I am sure Andre and others are paying attention to this and will take it on board when an implementation is nearer. BMS From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 01:51: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 780FB16A4CE; Tue, 2 Mar 2004 01:51:37 -0800 (PST) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD20243D31; Tue, 2 Mar 2004 01:51:36 -0800 (PST) (envelope-from glebius@cell.sick.ru) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.9/8.12.8) with ESMTP id i229pYQE024278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Mar 2004 12:51:35 +0300 (MSK) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.9/8.12.6/Submit) id i229pYuA024277; Tue, 2 Mar 2004 12:51:34 +0300 (MSK) Date: Tue, 2 Mar 2004 12:51:34 +0300 From: Gleb Smirnoff To: Kris Kennaway , Wes Peters , Andre Oppermann , freebsd-net@freebsd.org, freebsd-current@freebsd.org Message-ID: <20040302095134.GA24078@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Kris Kennaway , Wes Peters , Andre Oppermann , freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> <20040302085556.GA23734@cell.sick.ru> <20040302092825.GD884@saboteur.dek.spc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20040302092825.GD884@saboteur.dek.spc.org> User-Agent: Mutt/1.5.6i Subject: Re: My planned work on networking stack 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, 02 Mar 2004 09:51:37 -0000 On Tue, Mar 02, 2004 at 09:28:25AM +0000, Bruce M Simpson wrote: B> However, not including an OSPF/BGP daemon doesn't preclude us from ensuring B> that APIs which are exposed for advanced routing functionality (multipath, B> etc) do the right thing across the board, are well defined, etc. Yes, this would be a good alternative. If FreeBSD routing API extends, and routing daemon's developers are notified about these extensions, then they will add support for these features. B> As to the second part of your mail: That sounds like a reasonable suggestion, B> I am sure Andre and others are paying attention to this and will take it on B> board when an implementation is nearer. If this is OK from you, I start working on it (second variant using sockaddr_aspath). I'm willing to see this feature, and I have a good testing conditions for it. Please, can you also comment Vladimir Grebenschikov's mail (he posted to -net only). -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 03:02:41 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 6BFC416A4D7 for ; Tue, 2 Mar 2004 03:02:41 -0800 (PST) Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 868AC43D2F for ; Tue, 2 Mar 2004 03:02:40 -0800 (PST) (envelope-from rik@cronyx.ru) Received: (from root@localhost) by hanoi.cronyx.ru id i22B27CD031816 for freebsd-net@freebsd.org.checked; (8.12.8/vak/2.1) Tue, 2 Mar 2004 14:02:07 +0300 (MSK) (envelope-from rik@cronyx.ru) Received: from cronyx.ru (hi.cronyx.ru [144.206.181.94]) by hanoi.cronyx.ru with ESMTP id i22AxPk7031670; (8.12.8/vak/2.1) Tue, 2 Mar 2004 13:59:25 +0300 (MSK) (envelope-from rik@cronyx.ru) Message-ID: <404469C7.6050108@cronyx.ru> Date: Tue, 02 Mar 2004 14:02:31 +0300 From: Roman Kurakin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031208 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vincent Jardin References: <40436EB5.70503@cronyx.ru> <200403020010.37036.vjardin@free.fr> In-Reply-To: <200403020010.37036.vjardin@free.fr> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: Review request (ng_sppp) 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, 02 Mar 2004 11:02:41 -0000 Hi, Vincent Jardin wrote: >Hi, > >I am wondering why do we need a new PPP node. There are already so many >implementations. If we need a Netgraph PPP support, mpd + ng_ppp seems to be >enough, doesn't it ? > > And we also have sppp that is kernel mode ppp implementation. I don't reinvent whell. This node does not add a new PPP node, it adds only possibility of using sppp as a netgraph node. If we can, why not to join them together? Best regards, Roman Kurakin >Regards, > Vincent > >On Monday 01 March 2004 18:11, Roman Kurakin wrote: > > >>Hi, >> >> I just release new version (1.3) of ng_sppp, that implements >>netgraph sppp node. >>This version from now should work on both 4.x and 5.x branches. >> >> I want to commit it to CURRENT, so if you have any >>suggestions/objections >>please let me know. >> >> Code can be downloaded from: >> >>http://users.inse.ru/~rik/ng_sppp/ng_sppp.tgz >> >>Best regards, >> Roman Kurakin >> >> >> From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 04:33: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 9C69116A4CE; Tue, 2 Mar 2004 04:33:01 -0800 (PST) Received: from vhost109.his.com (vhost109.his.com [216.194.225.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9034C43D1F; Tue, 2 Mar 2004 04:33:00 -0800 (PST) (envelope-from brad.knowles@skynet.be) Received: from [10.0.1.3] (localhost.his.com [127.0.0.1]) by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id i22CWTxe098984; Tue, 2 Mar 2004 07:32:34 -0500 (EST) (envelope-from brad.knowles@skynet.be) Mime-Version: 1.0 X-Sender: bs663385@127.0.0.1 Message-Id: In-Reply-To: <20040302082625.GE22985@cell.sick.ru> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> Date: Tue, 2 Mar 2004 13:07:58 +0100 To: Gleb Smirnoff From: Brad Knowles Content-Type: text/plain; charset="us-ascii" ; format="flowed" cc: Andre Oppermann cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 12:33:01 -0000 At 11:26 AM +0300 2004/03/02, Gleb Smirnoff wrote: > Is there any plans about integration of BGP routing daemon (Zebra or > Quagga) into FreeBSD? With BGP routing daemon onboard, FreeBSD will be > a strong alternative against expensive commercial routers. I have > successfull experience of running FreeBSD STABLE with 2 full BGP views > for half a year. Modern i386 PC can route/filter/shape much more traffic > than expensive Cisco 36xx. I haven't yet compared with 7000 series... Talk to people who have real-world experience in running zebra/quagga in ISP environments with multiple upstreams and taking full views. The guy who is designing bgpd for OpenBSD gave a talk on the subject at FOSDEM, and it was very enlightening to hear about the problems with zebra (which went commercial and the open source version basically hasn't been touched in years) and quagga (which is a community of zebra users trying desperately to fix the worst of the bugs), and how he has used this information during his design of a replacement, and the methodology he used to make sure that the resulting system is robust and capable of being used in real-world production environments. His only issue with using exclusively PC equipment for handling routing is all those strange WAN protocols and cards for which hardware cards are rarely available beyond vendors like cisco or Juniper. That's why he's going pure Ethernet protocols/hardware throughout all his networks, including his upstream feeds, so that he can dump all that expensive ancient legacy routing hardware. If anything, I'd be inclined to look towards his work for OpenBSD and see if that could be imported into FreeBSD (and maybe improved, with contributions given back to him), rather than mess around with crap like zebra or quagga. Oh, and it would be nice if someone somewhere started thinking about a mesh routing implementation for *BSD, either AODV or something else. -- Brad Knowles, "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++) From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 04:33: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 A6DA316A4CF for ; Tue, 2 Mar 2004 04:33:40 -0800 (PST) Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31F7943D39 for ; Tue, 2 Mar 2004 04:33:37 -0800 (PST) (envelope-from smithi@nimnet.asn.au) Received: from localhost (smithi@localhost) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.3) with SMTP id XAA28364; Tue, 2 Mar 2004 23:33:31 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Tue, 2 Mar 2004 23:33:30 +1100 (EST) From: Ian Smith To: Tony Frank In-Reply-To: <20040302075742.GA18966@marvin.home.local> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: Bad loopback traffic not stopped by 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: Tue, 02 Mar 2004 12:33:40 -0000 On Tue, 2 Mar 2004, Tony Frank wrote: > Bit of a delayed response I'm afraid - PC troubles. No worries, and thanks for that. Curiousity sated, nothing to fix, no way to track their real source on $oif anyway, so moving along .. > > > > I> >deny tcp from any to any tcpflags rst,ack > > > > I> > > > > > I> These packets never reach IPFW as we can see. Only point of interest being that the old 2.2.6+ IPFW sees them fine, ie they're being picked up by 'deny ip from 127.0.0.0/8 to any' here. Cheers, Ian > On Sun, Feb 29, 2004 at 01:28:23AM +1100, Ian Smith wrote: > > On Sat, 28 Feb 2004, Tony Frank wrote (in freebsd-net@freebsd.org): > > > > > On Wed, Feb 25, 2004 at 05:21:34PM +0300, Gleb Smirnoff wrote: > > > > On Wed, Feb 25, 2004 at 04:19:51PM +0200, Iasen Kostov wrote: [..] From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 04:53: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 60F0116A4CE for ; Tue, 2 Mar 2004 04:53:46 -0800 (PST) Received: from proton.hexanet.fr (proton.hexanet.fr [81.23.32.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id A156943D2F for ; Tue, 2 Mar 2004 04:53:45 -0800 (PST) (envelope-from c.prevotaux@hexanet.fr) Received: from hexanet.fr (localhost [127.0.0.1]) by proton.hexanet.fr (Postfix) with SMTP id 3BB7F4C97A for ; Tue, 2 Mar 2004 13:53:43 +0100 (CET) Date: Tue, 2 Mar 2004 13:53:43 +0100 From: Christophe Prevotaux To: freebsd-net@freebsd.org Message-Id: <20040302135343.1a8e9254.c.prevotaux@hexanet.fr> Organization: HEXANET Sarl X-Mailer: Sylpheed version 0.9.6 (GTK+ 1.2.10; i386-portbld-freebsd4.9) X-NCC-RegID: fr.hexanet Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: FreeBSD LNS (L2TP) 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, 02 Mar 2004 12:53:46 -0000 Hi, Has anyone succeeded in using FreeBSD as an LNS and/or a LAC ?=20 If yes, I'd interested in knowing the details. -- =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Christophe Prevotaux Email: c.prevotaux@hexanet.fr HEXANET SARL URL: http://www.hexanet.fr/ Z.A.C Les Charmilles Tel: +33 (0)3 26 79 30 05=20 3 All=E9e Thierry Sabine Direct: +33 (0)3 26 61 77 72=20 BP202 Fax: +33 (0)3 26 79 30 06 51686 Reims Cedex 2 =20 FRANCE HEXANET Network Operation Center =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 04:59: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 28CDB16A4CE; Tue, 2 Mar 2004 04:59:40 -0800 (PST) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B58543D1D; Tue, 2 Mar 2004 04:59:39 -0800 (PST) (envelope-from glebius@cell.sick.ru) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.9/8.12.8) with ESMTP id i22CxZQE025918 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Mar 2004 15:59:36 +0300 (MSK) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.9/8.12.6/Submit) id i22CxZ9O025917; Tue, 2 Mar 2004 15:59:35 +0300 (MSK) Date: Tue, 2 Mar 2004 15:59:35 +0300 From: Gleb Smirnoff To: Brad Knowles Message-ID: <20040302125935.GA25835@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Brad Knowles , Wes Peters , Andre Oppermann , freebsd-net@freebsd.org References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i cc: Andre Oppermann cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 12:59:40 -0000 On Tue, Mar 02, 2004 at 01:07:58PM +0100, Brad Knowles wrote: B> > Is there any plans about integration of BGP routing daemon (Zebra or B> > Quagga) into FreeBSD? With BGP routing daemon onboard, FreeBSD will be B> > a strong alternative against expensive commercial routers. I have B> > successfull experience of running FreeBSD STABLE with 2 full BGP views B> > for half a year. Modern i386 PC can route/filter/shape much more traffic B> > than expensive Cisco 36xx. I haven't yet compared with 7000 series... B> B> Talk to people who have real-world experience in running B> zebra/quagga in ISP environments with multiple upstreams and taking B> full views. The guy who is designing bgpd for OpenBSD gave a talk on Haven't you understand? I'm the "person who has real-world experience in running zebra in ISP environments with multiple upstreams and taking full views". B> the subject at FOSDEM, and it was very enlightening to hear about the B> problems with zebra (which went commercial and the open source B> version basically hasn't been touched in years) and quagga (which is Browse zebra CVS to make sure that author is commiting bugfixes. For example: last commit to BGP code is done 2 weeks ago. B> a community of zebra users trying desperately to fix the worst of the B> bugs), and how he has used this information during his design of a I can't say a word about quagga, since I haven't use it, but I have positive experience with zebra (see above). B> If anything, I'd be inclined to look towards his work for OpenBSD B> and see if that could be imported into FreeBSD (and maybe improved, B> with contributions given back to him), rather than mess around with B> crap like zebra or quagga. I stop replying... Do not like flame. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 05:31:48 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 8E16016A4CE; Tue, 2 Mar 2004 05:31:48 -0800 (PST) Received: from vhost109.his.com (vhost109.his.com [216.194.225.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BE0D43D45; Tue, 2 Mar 2004 05:31:48 -0800 (PST) (envelope-from brad.knowles@skynet.be) Received: from [10.0.1.3] (localhost.his.com [127.0.0.1]) by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id i22DVPxe001162; Tue, 2 Mar 2004 08:31:26 -0500 (EST) (envelope-from brad.knowles@skynet.be) Mime-Version: 1.0 X-Sender: bs663385@127.0.0.1 Message-Id: In-Reply-To: <20040302125935.GA25835@cell.sick.ru> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302125935.GA25835@cell.sick.ru> Date: Tue, 2 Mar 2004 14:24:50 +0100 To: Gleb Smirnoff From: Brad Knowles Content-Type: text/plain; charset="us-ascii" ; format="flowed" cc: Brad Knowles cc: freebsd-net@freebsd.org cc: Andre Oppermann Subject: Re: My planned work on networking stack 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, 02 Mar 2004 13:31:48 -0000 At 3:59 PM +0300 2004/03/02, Gleb Smirnoff wrote: > Haven't you understand? I'm the "person who has real-world experience > in running zebra in ISP environments with multiple upstreams and taking > full views". Do you have multiple connectivity to two separate metro area exchanges, with multiple upstreams at each? Most large cities are lucky to have a single major metro area exchange, and the author of bgpd for OpenBSD works at an ISP located in Hamburg which is lucky enough to have two major NAPs, and he has multiple connectivity to both. He was the one ragging on zebra/quagga. Among other things, he said he had real problems keeping sessions up with zebra/quagga when neighbors were flapping. IIRC, he's also got some pretty big cisco equipment (75xx or whatever), and he is going to be switching over to OpenBSD+bgpd as his secondary core router in the very near future, with plans to complete the switch over soon thereafter. He's putting his money where his mouth is. Certainly, I have noticed that zebra hasn't done much recently, and at least on the surface quagga doesn't seem to have gone that far beyond where zebra was a couple of years ago. > Browse zebra CVS to make sure that author is commiting bugfixes. > For example: last commit to BGP code is done 2 weeks ago. Right, and that bugfix took how long to apply? When was the previous bugfix before that? When was the last real "new" development for zebra? > I can't say a word about quagga, since I haven't use it, but I have positive > experience with zebra (see above). If you're a zebra fan, then I suggest you check out quagga. > I stop replying... Do not like flame. Before flaming anyone further, you might want to check out pages like , and then take a look and see what Henning Brauer has actually been up to. You might also want to check out and ask yourself if zebra/quagga handles resiliency the way it should. If this problem isn't already addressed by bgpd, I'm sure it will be before Henning can go production with using this for his core routers at his ISP. -- Brad Knowles, "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++) From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 05:40: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 04D9116A4CF; Tue, 2 Mar 2004 05:40:13 -0800 (PST) Received: from vhost109.his.com (vhost109.his.com [216.194.225.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id E410D43D2F; Tue, 2 Mar 2004 05:40:11 -0800 (PST) (envelope-from brad.knowles@skynet.be) Received: from [10.0.1.3] (localhost.his.com [127.0.0.1]) by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id i22Ddrxe001412; Tue, 2 Mar 2004 08:39:55 -0500 (EST) (envelope-from brad.knowles@skynet.be) Mime-Version: 1.0 X-Sender: bs663385@127.0.0.1 Message-Id: In-Reply-To: <20040302090219.GC3438@astral-on.net> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> <20040302090219.GC3438@astral-on.net> Date: Tue, 2 Mar 2004 14:36:50 +0100 To: ad@astral-on.net From: Brad Knowles Content-Type: text/plain; charset="us-ascii" ; format="flowed" cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 13:40:13 -0000 At 11:02 AM +0200 2004/03/02, Andrew Degtiariov wrote: > What's difference (*currently*) beetwen FreeBSD+Zebra and Cisco routers? Support for VRRP? Support for various other routing protocols not covered by zebra/quagga -- at least not yet, if ever? Support for line cards and other devices that do not exist in a format you can plug into a PC? Maybe there's nothing you can do about this last item, but there's plenty that can be done on the software side -- just take a look at all the protocols that have been identified as being desirable, but not yet implemented by zebra/quagga. Oh, and then there are all the operational issues where zebra/quagga can't keep sessions going when a neighbor flaps, etc.... Those would require re-architecting the whole routing system, at which point it might make a lot more sense to go with a different implementation -- such as bgpd from OpenBSD. -- Brad Knowles, "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++) From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 05:53:10 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2248916A4CE; Tue, 2 Mar 2004 05:53:10 -0800 (PST) Received: from tiamat.astral-on.net (mail.astral-on.net [193.41.4.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 480AB43D1D; Tue, 2 Mar 2004 05:53:08 -0800 (PST) (envelope-from ad@astral-on.net) Received: from odin.astral-on.net (odin.astral-on.net [193.41.4.6]) by mail.astral-on.net (8.12.11/8.12.11) with ESMTP id i22DqWA2052166 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Mar 2004 15:52:32 +0200 (EET) (envelope-from ad@astral-on.net) Received: from odin.astral-on.net (localhost.astral-on.net [127.0.0.1]) by odin.astral-on.net (8.12.8p2/8.12.8) with ESMTP id i22DqW41020530; Tue, 2 Mar 2004 15:52:32 +0200 (EET) (envelope-from ad@odin.astral-on.net) Received: (from ad@localhost) by odin.astral-on.net (8.12.8p2/8.12.8/Submit) id i22DqU5Z020529; Tue, 2 Mar 2004 15:52:30 +0200 (EET) Date: Tue, 2 Mar 2004 15:52:30 +0200 From: Andrew Degtiariov To: freebsd-net@freebsd.org, freebsd-current@freebsd.org Message-ID: <20040302135230.GF3438@astral-on.net> Mail-Followup-To: freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> <20040302090219.GC3438@astral-on.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.63 X-Spam-Report: * -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on tiamat.astral-on.net Subject: Re: My planned work on networking stack X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ad@astral-on.net List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2004 13:53:10 -0000 On Tue, Mar 02, 2004 at 02:36:50PM +0100, Brad Knowles wrote: > At 11:02 AM +0200 2004/03/02, Andrew Degtiariov wrote: > > > What's difference (*currently*) beetwen FreeBSD+Zebra and Cisco routers? > > Support for VRRP? Support for various other routing protocols > not covered by zebra/quagga -- at least not yet, if ever? Support > for line cards and other devices that do not exist in a format you > can plug into a PC? > > Maybe there's nothing you can do about this last item, but > there's plenty that can be done on the software side -- just take a > look at all the protocols that have been identified as being > desirable, but not yet implemented by zebra/quagga. > > > Oh, and then there are all the operational issues where > zebra/quagga can't keep sessions going when a neighbor flaps, etc.... > Those would require re-architecting the whole routing system, at ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Congratulation. That's namely what the conversation was about. > which point it might make a lot more sense to go with a different > implementation -- such as bgpd from OpenBSD. -- Andrew Degtiariov DA-RIPE From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 05:56:29 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB4FA16A4CE for ; Tue, 2 Mar 2004 05:56:29 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id E17AE43D2D for ; Tue, 2 Mar 2004 05:56:28 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 37681 invoked from network); 2 Mar 2004 13:56:28 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 13:56:28 -0000 Message-ID: <4044928C.AF49FD38@freebsd.org> Date: Tue, 02 Mar 2004 14:56:28 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Wes Peters References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 13:56:29 -0000 Wes Peters wrote: > > > [] automatically sizing TCP send buffers to achieve optimal performance > > over a wide range of bw*delay situations. (in progress) > > What a wonderful idea. Can't wait for the bikesheds... What bikesheds? > > [] establish a testbed for testing and qualification of TCP performance > > and optimizations over a wide range of network conditions (types, > > speeds, packet loss ratios, out of order, etc). (started) > > Be sure to coordinate with the donations officer for help in getting > equipment you may need. My plan is to do it with a couple of boxes and dummynet. The harder part is not to make the setup but to figure out what network conditions to simulate and how often they happen. If you have any traffic generators spare I'd be interested surely. ;-) > > [] move IPv4 routing to its own optimized routing table structure and > > add multi-path and policy-routing options. (planned) > > Will the table code in PF be helpful in this area? They seem to have > developed a reasonably small notation for CIDR-type address ranges and code > that does best-fit matching. Maybe. I'll evaluate the various available implementations and research in that area when I get to it. However the multi-path and policy-routing stuff will be part of the routing engine and not any of the firewalling systems. They may have an option to tag a packet with a certain policy to override the routing system. > > [] other stuff that I happen to stumble over... ;-) > > Wowsers. I can't wait to hear more. When do you expect to have a design > for the ARP stuff and TCP buffer sizing, since they are underway? The ARP stuff is pretty simple and is a hash list IP->MAC per ethernet (actually 802.1) broadcast domain. The harder part is to move all the code to one place from it's various net/* and netinet/* files. As a nice side effect we get per-MAC accounting (octets, frames) for free. TCP buffer sizing involves mainly two areas. One is good RTT measurements to be able to estimate the bw*delay product well and the other is information about memory (mbuf) usage in the networking system to do the right thing if memory gets low. -- Andre From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 06:00: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 80DB016A4CF for ; Tue, 2 Mar 2004 06:00:16 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF89643D31 for ; Tue, 2 Mar 2004 06:00:15 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 38505 invoked from network); 2 Mar 2004 14:00:15 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 14:00:15 -0000 Message-ID: <4044936F.B042C476@freebsd.org> Date: Tue, 02 Mar 2004 15:00:15 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Brooks Davis References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <4043E565.6070703@netlab.nec.de> <20040302014319.GA24639@Odin.AC.HMC.Edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: Lars Eggert cc: freebsd-current@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 14:00:16 -0000 Brooks Davis wrote: > > On Tue, Mar 02, 2004 at 10:37:41AM +0900, Lars Eggert wrote: > > Hi, > > > > Wes Peters wrote: > > >On Monday 01 March 2004 14:18, Andre Oppermann wrote: > > > > > >>[] establish a testbed for testing and qualification of TCP performance > > >> and optimizations over a wide range of network conditions (types, > > >> speeds, packet loss ratios, out of order, etc). (started) > > > > > >Be sure to coordinate with the donations officer for help in getting > > >equipment you may need. > > > > this sounds like something you could do with planetlab > > (http://planet-lab.org/). Do you have access? (Or maybe I misunderstood > > what you meant by "testbed".) > > From the list of metrics, Emulab (http://www.emulab.net/) is probably > more what he's thinking, but we probably ought to let Andre speak for > him self. :-) No, I want to have something that emulates real-world line conditions. For example ADSL connections and so on. Or links Europe-USA etc. This is not about performance of server applications like apache benchmarking. -- Andre From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 06:10:43 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 9891316A4D4; Tue, 2 Mar 2004 06:10:43 -0800 (PST) Received: from vhost109.his.com (vhost109.his.com [216.194.225.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57CE943D2F; Tue, 2 Mar 2004 06:10:43 -0800 (PST) (envelope-from brad.knowles@skynet.be) Received: from [10.0.1.3] (localhost.his.com [127.0.0.1]) by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id i22EAXxe002845; Tue, 2 Mar 2004 09:10:34 -0500 (EST) (envelope-from brad.knowles@skynet.be) Mime-Version: 1.0 X-Sender: bs663385@127.0.0.1 Message-Id: In-Reply-To: <20040302135230.GF3438@astral-on.net> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> <20040302090219.GC3438@astral-on.net> <20040302135230.GF3438@astral-on.net> Date: Tue, 2 Mar 2004 15:10:33 +0100 To: ad@astral-on.net From: Brad Knowles Content-Type: text/plain; charset="us-ascii" ; format="flowed" cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 14:10:43 -0000 At 3:52 PM +0200 2004/03/02, Andrew Degtiariov wrote: >> Oh, and then there are all the operational issues where >> zebra/quagga can't keep sessions going when a neighbor flaps, etc.... >> Those would require re-architecting the whole routing system, at > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > Congratulation. That's namely what the conversation was about. Right. We can either re-architect zebra/quagga, or we can start with something that addresses the weaknesses in these tools, or we can do something else. I'm advocating that we at least take a long hard look at what Henning Brauer has done, and seriously consider whether it would make sense for us to start with that to give us a leg up on the re-architecting process. If nothing else, this would at least give us an interesting insight to what some of the weaknesses are in this category, and maybe help us identify better solutions faster and more easily. In particular, if there are such serious problems with zebra/quagga that they would need to be completely re-architected in order to be useful, then I don't see that as being a particularly fruitful line of work to pursue. I'd rather start with something that requires less re-work, and would presumably allow us to more easily add in any additional bits that we feel are necessary or desirable. -- Brad Knowles, "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++) From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 06:11: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 8C44216A4CE for ; Tue, 2 Mar 2004 06:11:55 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB0F043D45 for ; Tue, 2 Mar 2004 06:11:54 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 40977 invoked from network); 2 Mar 2004 14:11:54 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 14:11:54 -0000 Message-ID: <4044962A.7F6ECE9A@freebsd.org> Date: Tue, 02 Mar 2004 15:11:54 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: James References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 14:11:55 -0000 James wrote: > > > > [] move IPv4 routing to its own optimized routing table structure and > > finally it's about time :) > > > > add multi-path and policy-routing options. (planned) > > would the policy-routing optioned table sort of similar to VRF's or > different routing instances that could potentially be tied to userlands > like Quagga? Policy-routing in this context means to have multiple forwarding tables which are being selected based on something else than the destination address. Normally that is the source address or source/incoming interface. Optionally it can be anything one of our firewall systems can match on and then tag the packet. The routing tables for source and destination address matches are opaque or non-opaque. That means you can have a table with exceptions and if an address doesn't match there it will fall through onto the next or default table. Or, if it's a opaque table, it will result in an unreach message. Etc. It's not VRF as such but can be set up to work like it. The userland routing daemons have the option to specify the table they want to modify. This requires certain changes to the routing daemons and a redesign of the routing message format (but not the routing socket). -- Andre From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 06:14:08 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56C1816A4CE for ; Tue, 2 Mar 2004 06:14:08 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86E9943D2D for ; Tue, 2 Mar 2004 06:14:07 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 41501 invoked from network); 2 Mar 2004 14:14:06 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 14:14:06 -0000 Message-ID: <404496AE.300E1457@freebsd.org> Date: Tue, 02 Mar 2004 15:14:06 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Bruce M Simpson References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: James Subject: Re: My planned work on networking stack 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, 02 Mar 2004 14:14:08 -0000 Bruce M Simpson wrote: > > On Mon, Mar 01, 2004 at 10:16:25PM -0500, James wrote: > > > > [] move IPv4 routing to its own optimized routing table structure and > > > > finally it's about time :) > > I've been fielding suggestions from individuals who feel using a multi-bit > trie might be more suitable for achieving higher PPS rates. Yes. Which one should not matter. I want to make an API for the IPv4 routing code. Different routing implementations then can be loaded or changed at runtime or boot time. > > > > add multi-path and policy-routing options. (planned) > > > > would the policy-routing optioned table sort of similar to VRF's or > > different routing instances that could potentially be tied to userlands > > like Quagga? > > That's the plan, I believe, anyway... It would be nice if Quagga could be > taught about how to add TCP-MD5 keys to both FreeBSD and OpenBSD SADBs. What is the relationship tcp-md5 --> policy-routing? -- Andre From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 06:29: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 CEA6916A4CE for ; Tue, 2 Mar 2004 06:29:54 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11C0C43D46 for ; Tue, 2 Mar 2004 06:29:54 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 44862 invoked from network); 2 Mar 2004 14:29:53 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 14:29:53 -0000 Message-ID: <40449A61.DBFFC148@freebsd.org> Date: Tue, 02 Mar 2004 15:29:53 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Gleb Smirnoff References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 14:29:54 -0000 Gleb Smirnoff wrote: > > Dear sirs, > > On Tue, Mar 02, 2004 at 04:29:57AM +0000, Bruce M Simpson wrote: > B> > > > add multi-path and policy-routing options. (planned) > B> > > B> > would the policy-routing optioned table sort of similar to VRF's or > B> > different routing instances that could potentially be tied to userlands > B> > like Quagga? > B> > B> That's the plan, I believe, anyway... It would be nice if Quagga could be > B> taught about how to add TCP-MD5 keys to both FreeBSD and OpenBSD SADBs. > > Is there any plans about integration of BGP routing daemon (Zebra or Quagga) > into FreeBSD? With BGP routing daemon onboard, FreeBSD will be a strong > alternative against expensive commercial routers. I have successfull experience > of running FreeBSD STABLE with 2 full BGP views for half a year. Modern i386 PC > can route/filter/shape much more traffic than expensive Cisco 36xx. I haven't > yet compared with 7000 series... No, Zebra/Quagga will not be integrated into FreeBSD but available from Ports. There is no reason why a routing daemon needs to be part of the base system. FreeBSD will provided the appropriate APIs to a routing daemon to make full use of the kernel packet forwarding engine. > Currently I'm working on my Netflow implementation, and I have faced the > following problem: I've already got global routing in my routing table, but it > lacks AS (Autonomous System) information. The routing daemon (zebra in my case) > already knows ASes, but this informations is lost when routing information is > injected into kernel. It'll be nice to add AS path to struct rtentry. The AS path does not belong into the kernel or the FIB. If you want to do per-AS accounting a much better solution is simply to take a MRT dump and load it into a BPF/PCAP application which is collecting statistics. > Seems like there is no problem with extending struct rtentry, but injecting > this info from userland requires changes to routing API. I see two ways of > implementing it: > > 1) Simply add new field into struct rt_msghdr, and bump RTM_VERSION. I have > done this, it works. But I don't like it, since RTM_VERSION has changed. > 2) Create new sockaddr, called sockaddr_aspath. Define RTAX_ASPATH, increase > RTAX_MAX. Pass this sockaddr_aspath in rti_info[] array of a routing message > into kernel. Unparse it in the kernel, fill in new field of struct rtentry. > > While I haven't yet started working on 2), I'd be very glad to hear comments > from FreeBSD developers. Thanks in advance. The routing message format needs to be redisigned. That is nothing that happens on short notice. -- Andre From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 06:32:15 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CF0216A4CE for ; Tue, 2 Mar 2004 06:32:15 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29AE343D1F for ; Tue, 2 Mar 2004 06:32:14 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 45475 invoked from network); 2 Mar 2004 14:32:13 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 14:32:13 -0000 Message-ID: <40449AED.1A4580E5@freebsd.org> Date: Tue, 02 Mar 2004 15:32:13 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Bruce M Simpson References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> <20040302085556.GA23734@cell.sick.ru> <20040302092825.GD884@saboteur.dek.spc.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: freebsd-net@freebsd.org cc: Kris Kennaway Subject: Re: My planned work on networking stack 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, 02 Mar 2004 14:32:15 -0000 Bruce M Simpson wrote: > > However, not including an OSPF/BGP daemon doesn't preclude us from ensuring > that APIs which are exposed for advanced routing functionality (multipath, > etc) do the right thing across the board, are well defined, etc. > > As to the second part of your mail: That sounds like a reasonable suggestion, > I am sure Andre and others are paying attention to this and will take it on > board when an implementation is nearer. Yes, exactly! -- Andre From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 06:34:56 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8401116A4CF for ; Tue, 2 Mar 2004 06:34:56 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id B60AD43D1D for ; Tue, 2 Mar 2004 06:34:55 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 46067 invoked from network); 2 Mar 2004 14:34:54 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 14:34:54 -0000 Message-ID: <40449B8E.A48B39B0@freebsd.org> Date: Tue, 02 Mar 2004 15:34:54 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Gleb Smirnoff References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> <20040302085556.GA23734@cell.sick.ru> <20040302092825.GD884@saboteur.dek.spc.org> <20040302095134.GA24078@cell.sick.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: Kris Kennaway Subject: Re: My planned work on networking stack 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, 02 Mar 2004 14:34:56 -0000 Gleb Smirnoff wrote: > > On Tue, Mar 02, 2004 at 09:28:25AM +0000, Bruce M Simpson wrote: > B> However, not including an OSPF/BGP daemon doesn't preclude us from ensuring > B> that APIs which are exposed for advanced routing functionality (multipath, > B> etc) do the right thing across the board, are well defined, etc. > > Yes, this would be a good alternative. If FreeBSD routing API extends, and > routing daemon's developers are notified about these extensions, then they > will add support for these features. I will make sure to notify them. > B> As to the second part of your mail: That sounds like a reasonable suggestion, > B> I am sure Andre and others are paying attention to this and will take it on > B> board when an implementation is nearer. > > If this is OK from you, I start working on it (second variant using sockaddr_aspath). > I'm willing to see this feature, and I have a good testing conditions for it. Putting the AS path into the kernel routing table is certainly not the right thing to do. The kernel fib must be as small as possible. All information how a route made it there is pretty much irrelevant and only the business of the routing protocol daemons. -- Andre From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 06:41: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 3EA1616A4CE; Tue, 2 Mar 2004 06:41:11 -0800 (PST) Received: from sizone.org (mortar.sizone.org [65.126.154.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 077C343D2F; Tue, 2 Mar 2004 06:41:11 -0800 (PST) (envelope-from dgilbert@daveg.ca) Received: by sizone.org (Postfix, from userid 66) id 70766308FD; Tue, 2 Mar 2004 09:41:10 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id 76C1F1D2444; Tue, 2 Mar 2004 09:41:09 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16452.40197.327006.651617@canoe.dclg.ca> Date: Tue, 2 Mar 2004 09:41:09 -0500 To: Andre Oppermann In-Reply-To: <4043B6BA.B847F081@freebsd.org> References: <4043B6BA.B847F081@freebsd.org> X-Mailer: VM 7.17 under 21.4 (patch 14) "Reasonable Discussion" XEmacs Lucid cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: My planned work on networking stack 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, 02 Mar 2004 14:41:11 -0000 >>>>> "Andre" == Andre Oppermann writes: Andre> [] move IPv4 routing to its own optimized routing table Andre> structure and add multi-path and policy-routing options. Andre> (planned) Andre> [] profile (don't speculate) common network server usages Andre> overall and in specific detail in depth in the network code. Andre> (planned) I'm partiularly interested in these two items. I would like to be involved. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 06:48:43 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 6B2B616A4CE; Tue, 2 Mar 2004 06:48:43 -0800 (PST) Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E12E43D1F; Tue, 2 Mar 2004 06:48:41 -0800 (PST) (envelope-from smithi@nimnet.asn.au) Received: from localhost (smithi@localhost) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.3) with SMTP id BAA01631; Wed, 3 Mar 2004 01:48:36 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Wed, 3 Mar 2004 01:48:35 +1100 (EST) From: Ian Smith To: Andre Oppermann In-Reply-To: <4044928C.AF49FD38@freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 14:48:43 -0000 [-current out of ccs, I'm not subscribed] On Tue, 2 Mar 2004, Andre Oppermann wrote to Wes Peters: > > Wowsers. I can't wait to hear more. When do you expect to have a design > > for the ARP stuff and TCP buffer sizing, since they are underway? > > The ARP stuff is pretty simple and is a hash list IP->MAC per ethernet > (actually 802.1) broadcast domain. The harder part is to move all the > code to one place from it's various net/* and netinet/* files. As a > nice side effect we get per-MAC accounting (octets, frames) for free. What about bridged interfaces that have a MAC, but no IP address? I'm still trying to figure this one out for a (4.8-R) bridge that's working fine but still has some issues with ARP confusion and thus repeated ARP requests from the upstream / outside router, esp regarding broadcast UDP traffic, where the inside interface has the one IP and thus broadcast address, for broadcast packets delivered locally to the bridge's IP? I realise this is a bridge issue, but it's how it interacts with ARP. The rest of this is well out of my league, but fascinating reading :) Cheers, Ian From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 06:52: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 AD87716A4CE; Tue, 2 Mar 2004 06:52:17 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8028643D41; Tue, 2 Mar 2004 06:52:17 -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 i22EqCKH016624; Tue, 2 Mar 2004 06:52:12 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i22EqCUk016623; Tue, 2 Mar 2004 06:52:12 -0800 Date: Tue, 2 Mar 2004 06:52:12 -0800 From: Brooks Davis To: Andre Oppermann Message-ID: <20040302145212.GB30219@Odin.AC.HMC.Edu> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <4043E565.6070703@netlab.nec.de> <20040302014319.GA24639@Odin.AC.HMC.Edu> <4044936F.B042C476@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="i9LlY+UWpKt15+FH" Content-Disposition: inline In-Reply-To: <4044936F.B042C476@freebsd.org> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: Lars Eggert cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 14:52:17 -0000 --i9LlY+UWpKt15+FH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 02, 2004 at 03:00:15PM +0100, Andre Oppermann wrote: > Brooks Davis wrote: > >=20 > > On Tue, Mar 02, 2004 at 10:37:41AM +0900, Lars Eggert wrote: > > > Hi, > > > > > > Wes Peters wrote: > > > >On Monday 01 March 2004 14:18, Andre Oppermann wrote: > > > > > > > >>[] establish a testbed for testing and qualification of TCP perform= ance > > > >> and optimizations over a wide range of network conditions (types, > > > >> speeds, packet loss ratios, out of order, etc). (started) > > > > > > > >Be sure to coordinate with the donations officer for help in getting > > > >equipment you may need. > > > > > > this sounds like something you could do with planetlab > > > (http://planet-lab.org/). Do you have access? (Or maybe I misundersto= od > > > what you meant by "testbed".) > >=20 > > From the list of metrics, Emulab (http://www.emulab.net/) is probably > > more what he's thinking, but we probably ought to let Andre speak for > > him self. :-) >=20 > No, I want to have something that emulates real-world line conditions. > For example ADSL connections and so on. Or links Europe-USA etc. This > is not about performance of server applications like apache benchmarking. This is definatly something you could do with Emulab (that's why we have one), but if you just need to simulate agrigate link characteristics, Emulab would be massive overkill. -- 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 --i9LlY+UWpKt15+FH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFARJ+bXY6L6fI4GtQRAhQOAKCNz1QY84F+Zjeal9qSHihn3TtskACgnxUZ lSTmI7vvFhKeU7bD7bCbqJo= =w65F -----END PGP SIGNATURE----- --i9LlY+UWpKt15+FH-- From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 06:59: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 1440216A4CE for ; Tue, 2 Mar 2004 06:59:06 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2ED6343D46 for ; Tue, 2 Mar 2004 06:59:05 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 51278 invoked from network); 2 Mar 2004 14:59:04 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 14:59:04 -0000 Message-ID: <4044A138.F444D224@freebsd.org> Date: Tue, 02 Mar 2004 15:59:04 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Brad Knowles References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 14:59:06 -0000 Brad Knowles wrote: > > At 11:26 AM +0300 2004/03/02, Gleb Smirnoff wrote: > > > Is there any plans about integration of BGP routing daemon (Zebra or > > Quagga) into FreeBSD? With BGP routing daemon onboard, FreeBSD will be > > a strong alternative against expensive commercial routers. I have > > successfull experience of running FreeBSD STABLE with 2 full BGP views > > for half a year. Modern i386 PC can route/filter/shape much more traffic > > than expensive Cisco 36xx. I haven't yet compared with 7000 series... > > Talk to people who have real-world experience in running > zebra/quagga in ISP environments with multiple upstreams and taking > full views. The guy who is designing bgpd for OpenBSD gave a talk on > the subject at FOSDEM, and it was very enlightening to hear about the > problems with zebra (which went commercial and the open source > version basically hasn't been touched in years) and quagga (which is > a community of zebra users trying desperately to fix the worst of the > bugs), and how he has used this information during his design of a > replacement, and the methodology he used to make sure that the > resulting system is robust and capable of being used in real-world > production environments. Zebra or Quagga are not broken, just not very optimal in their implementation. I'm running Zebra with several full-feeds and about 150 peerings for four years now on FreeBSD routers with uptimes of 300-400 days. It is true that Zebra's bgpd is un- responsive for a couple of seconds when is has to walk the routing table when large feeds flap but it doesn't crash. Zebra is definatly *not* a piece of s*** as you make it sound here. > His only issue with using exclusively PC equipment for handling > routing is all those strange WAN protocols and cards for which > hardware cards are rarely available beyond vendors like cisco or > Juniper. That's why he's going pure Ethernet protocols/hardware > throughout all his networks, including his upstream feeds, so that he > can dump all that expensive ancient legacy routing hardware. You need GigE, T1/E1, E3/T3 and STM-1 these days. Everything else is dead. > If anything, I'd be inclined to look towards his work for OpenBSD > and see if that could be imported into FreeBSD (and maybe improved, > with contributions given back to him), rather than mess around with > crap like zebra or quagga. Ok, again Zebra/Quagga is not "crap". The same with DJBware which is no "crap" either. If you don't like it just say so but refrain from dirt-talking it. It doesn't make your point any stronger. The bgpd from OpenBSD will surely make it's way into FreeBSD [*]. The main developer besides Henning sits about 5 meters away from me in my office. If you look at it then you'll find out that I'm not really innocent that bgpd ;-) http://www.openbsd.org/cgi-bin/cvsweb/src/usr.sbin/bgpd/rde.h?rev=1.33&content-type=text/x-cvsweb-markup [*] In FreeBSD it will be a port. I don't know why a bgpd should be in the base system. > Oh, and it would be nice if someone somewhere started thinking > about a mesh routing implementation for *BSD, either AODV or > something else. It would be nice if you could calm down, stop your mis-informed accusations and rants and actually try to be helpful and progressive to the projects which try to do it better. Thank you very much. -- Andre From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 07:08: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 6F93B16A4CE for ; Tue, 2 Mar 2004 07:08:28 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AAF143D1F for ; Tue, 2 Mar 2004 07:08:27 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 53324 invoked from network); 2 Mar 2004 15:08:26 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 15:08:26 -0000 Message-ID: <4044A36A.64E885BE@freebsd.org> Date: Tue, 02 Mar 2004 16:08:26 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Brad Knowles References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 15:08:28 -0000 Brad Knowles wrote: > > At 3:59 PM +0300 2004/03/02, Gleb Smirnoff wrote: > > > Haven't you understand? I'm the "person who has real-world experience > > in running zebra in ISP environments with multiple upstreams and taking > > full views". > > IIRC, he's also got some pretty big cisco equipment (75xx or > whatever), and he is going to be switching over to OpenBSD+bgpd as > his secondary core router in the very near future, with plans to > complete the switch over soon thereafter. He's putting his money > where his mouth is. Gleb is doing the same, and so am I. However you are not. Do you run BGP in your network? > Certainly, I have noticed that zebra hasn't done much recently, > and at least on the surface quagga doesn't seem to have gone that far > beyond where zebra was a couple of years ago. At least for me on FreeBSD Zebra has been very stable for me. There is no need to always "change" things. > > Browse zebra CVS to make sure that author is commiting bugfixes. > > For example: last commit to BGP code is done 2 weeks ago. > > Right, and that bugfix took how long to apply? When was the > previous bugfix before that? When was the last real "new" > development for zebra? What is you point? Do you use Zebra? Are you affected by it? Or are you just ranting? > > I stop replying... Do not like flame. > > Before flaming anyone further, you might want to check out pages > like , > and then take a look and see what Henning Brauer has actually been up > to. And you should stop flaming anyone if you haven't ever used or done what you are blabbering about. > You might also want to check out > and ask > yourself if zebra/quagga handles resiliency the way it should. If > this problem isn't already addressed by bgpd, I'm sure it will be > before Henning can go production with using this for his core routers > at his ISP. Sorry, but OpenBSDs bgpd wont to any of that either. This is mostly hardware that needs to be redundant. Not much you can in bgpd. -- Andre From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 07:11: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 8CACD16A4CE for ; Tue, 2 Mar 2004 07:11:16 -0800 (PST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3E1E43D49 for ; Tue, 2 Mar 2004 07:11:15 -0800 (PST) (envelope-from max@love2party.net) Received: from [212.227.126.161] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1AyBYB-0002Ws-00 for net@freebsd.org; Tue, 02 Mar 2004 16:11:15 +0100 Received: from [217.227.153.50] (helo=vampire.homelinux.org) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1AyBYA-0005Co-00 for net@freebsd.org; Tue, 02 Mar 2004 16:11:14 +0100 Received: (qmail 9109 invoked from network); 2 Mar 2004 15:17:52 -0000 Received: from unknown (HELO fbsd52.laiers.local) (192.168.4.88) by 192.168.4.1 with SMTP; 2 Mar 2004 15:17:52 -0000 From: Max Laier To: Brad Knowles , Gleb Smirnoff Date: Tue, 2 Mar 2004 16:11:07 +0100 User-Agent: KMail/1.5.4 References: <4043B6BA.B847F081@freebsd.org> <20040302082625.GE22985@cell.sick.ru> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200403021611.07590.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:e28873fbe4dbe612ce62ab869898ff08 cc: Andre Oppermann cc: net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 15:11:16 -0000 On Tuesday 02 March 2004 13:07, Brad Knowles wrote: > At 11:26 AM +0300 2004/03/02, Gleb Smirnoff wrote: > > Is there any plans about integration of BGP routing daemon (Zebra > > or Quagga) into FreeBSD? With BGP routing daemon onboard, FreeBSD > > will be a strong alternative against expensive commercial routers. I > > have successfull experience of running FreeBSD STABLE with 2 full BGP > > views for half a year. Modern i386 PC can route/filter/shape much > > more traffic than expensive Cisco 36xx. I haven't yet compared with > > 7000 series... > > Talk to people who have real-world experience in running > zebra/quagga in ISP environments with multiple upstreams and taking > full views. The guy who is designing bgpd for OpenBSD gave a talk on > the subject at FOSDEM, and it was very enlightening to hear about the > problems with zebra (which went commercial and the open source > version basically hasn't been touched in years) and quagga (which is > a community of zebra users trying desperately to fix the worst of the > bugs), and how he has used this information during his design of a > replacement, and the methodology he used to make sure that the > resulting system is robust and capable of being used in real-world > production environments. > <...> > > If anything, I'd be inclined to look towards his work for OpenBSD > and see if that could be imported into FreeBSD (and maybe improved, > with contributions given back to him), rather than mess around with > crap like zebra or quagga. Yes, please! Henning is a hero ;) still I'd give him some time to get this stable at OpenBSD before porting it over. I believe that he has plans to have it stable for 3.5 (due date May 1st), but I'd give it another release before speaking of a really stable system. With other things on my list: ALTQ and CARP most noteable, FreeBSD could make a very good routing solution. -- Best regards, | mlaier@freebsd.org Max Laier | ICQ #67774661 http://pf4freebsd.love2party.net/ | mlaier@EFnet From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 07:18:14 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F327216A4CE for ; Tue, 2 Mar 2004 07:18:13 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D8D443D31 for ; Tue, 2 Mar 2004 07:18:13 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 55442 invoked from network); 2 Mar 2004 15:18:12 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 15:18:12 -0000 Message-ID: <4044A5B4.789778D8@freebsd.org> Date: Tue, 02 Mar 2004 16:18: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: Brad Knowles References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> <20040302090219.GC3438@astral-on.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: ad@astral-on.net Subject: Re: My planned work on networking stack 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, 02 Mar 2004 15:18:14 -0000 Brad Knowles wrote: > > At 3:52 PM +0200 2004/03/02, Andrew Degtiariov wrote: > > >> Oh, and then there are all the operational issues where > >> zebra/quagga can't keep sessions going when a neighbor flaps, etc.... > >> Those would require re-architecting the whole routing system, at > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Congratulation. That's namely what the conversation was about. > > Right. We can either re-architect zebra/quagga, or we can start > with something that addresses the weaknesses in these tools, or we > can do something else. The best thing would be to stay by the sideline, be quiet and let the people who know what they do solve these things for everyones benefit. > I'm advocating that we at least take a long hard look at what > Henning Brauer has done, and seriously consider whether it would make > sense for us to start with that to give us a leg up on the > re-architecting process. What Henning, Claudio and me are doing is certainly a step forward. Although there is no re-architecting of the routing system going on. It's just a different and more efficient implementation approach. We do not reinvent the world. > If nothing else, this would at least give us an interesting > insight to what some of the weaknesses are in this category, and > maybe help us identify better solutions faster and more easily. > > In particular, if there are such serious problems with > zebra/quagga that they would need to be completely re-architected in > order to be useful, then I don't see that as being a particularly > fruitful line of work to pursue. I'd rather start with something > that requires less re-work, and would presumably allow us to more > easily add in any additional bits that we feel are necessary or > desirable. I'd like to see you do any real work in this area instead of producing many and longs emails with lots of mis-informed rants in them. Yes, this my official put-up-or-shut-up call to you. -- Andre From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 07:19:15 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7CBEA16A4CF for ; Tue, 2 Mar 2004 07:19:15 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5D3C43D45 for ; Tue, 2 Mar 2004 07:19:14 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 55669 invoked from network); 2 Mar 2004 15:19:14 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 15:19:14 -0000 Message-ID: <4044A5F2.1C3BEEDC@freebsd.org> Date: Tue, 02 Mar 2004 16:19:14 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: David Gilbert References: <4043B6BA.B847F081@freebsd.org> <16452.40197.327006.651617@canoe.dclg.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 15:19:15 -0000 David Gilbert wrote: > > >>>>> "Andre" == Andre Oppermann writes: > > Andre> [] move IPv4 routing to its own optimized routing table > Andre> structure and add multi-path and policy-routing options. > Andre> (planned) > > Andre> [] profile (don't speculate) common network server usages > Andre> overall and in specific detail in depth in the network code. > Andre> (planned) > > I'm partiularly interested in these two items. I would like to be > involved. I'll post on these lists when I get there. -- Andre From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 07:27:34 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15B5016A4CE for ; Tue, 2 Mar 2004 07:27:34 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 362EF43D39 for ; Tue, 2 Mar 2004 07:27:33 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 57433 invoked from network); 2 Mar 2004 15:27:32 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 15:27:32 -0000 Message-ID: <4044A7E4.B109121B@freebsd.org> Date: Tue, 02 Mar 2004 16:27:32 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Ian Smith References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 15:27:34 -0000 Ian Smith wrote: > > [-current out of ccs, I'm not subscribed] > > On Tue, 2 Mar 2004, Andre Oppermann wrote to Wes Peters: > > > > Wowsers. I can't wait to hear more. When do you expect to have a design > > > for the ARP stuff and TCP buffer sizing, since they are underway? > > > > The ARP stuff is pretty simple and is a hash list IP->MAC per ethernet > > (actually 802.1) broadcast domain. The harder part is to move all the > > code to one place from it's various net/* and netinet/* files. As a > > nice side effect we get per-MAC accounting (octets, frames) for free. > > What about bridged interfaces that have a MAC, but no IP address? I'm > still trying to figure this one out for a (4.8-R) bridge that's working > fine but still has some issues with ARP confusion and thus repeated ARP > requests from the upstream / outside router, esp regarding broadcast UDP > traffic, where the inside interface has the one IP and thus broadcast > address, for broadcast packets delivered locally to the bridge's IP? ARP will only be there if an IP address is configured on a interface. A bridge doesn't need any ARP for its bridging functionality, it is just relaying a frame from one side to the other. To do that it maintains a table with MAC addresses it sees on the particitpating interfaces. But that is entirely unreated to ARP which only does IP->MAC mappings. > I realise this is a bridge issue, but it's how it interacts with ARP. > > The rest of this is well out of my league, but fascinating reading :) -- Andre From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 07:28: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 CEBAF16A4CF for ; Tue, 2 Mar 2004 07:28:31 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFDE543D1F for ; Tue, 2 Mar 2004 07:28:30 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 57643 invoked from network); 2 Mar 2004 15:28:30 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 15:28:30 -0000 Message-ID: <4044A81E.C5517D08@freebsd.org> Date: Tue, 02 Mar 2004 16:28:30 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Brooks Davis References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <4043E565.6070703@netlab.nec.de> <20040302014319.GA24639@Odin.AC.HMC.Edu> <4044936F.B042C476@freebsd.org> <20040302145212.GB30219@Odin.AC.HMC.Edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: Lars Eggert cc: freebsd-current@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 15:28:32 -0000 Brooks Davis wrote: > > On Tue, Mar 02, 2004 at 03:00:15PM +0100, Andre Oppermann wrote: > > Brooks Davis wrote: > > > > > > On Tue, Mar 02, 2004 at 10:37:41AM +0900, Lars Eggert wrote: > > > > Hi, > > > > > > > > Wes Peters wrote: > > > > >On Monday 01 March 2004 14:18, Andre Oppermann wrote: > > > > > > > > > >>[] establish a testbed for testing and qualification of TCP performance > > > > >> and optimizations over a wide range of network conditions (types, > > > > >> speeds, packet loss ratios, out of order, etc). (started) > > > > > > > > > >Be sure to coordinate with the donations officer for help in getting > > > > >equipment you may need. > > > > > > > > this sounds like something you could do with planetlab > > > > (http://planet-lab.org/). Do you have access? (Or maybe I misunderstood > > > > what you meant by "testbed".) > > > > > > From the list of metrics, Emulab (http://www.emulab.net/) is probably > > > more what he's thinking, but we probably ought to let Andre speak for > > > him self. :-) > > > > No, I want to have something that emulates real-world line conditions. > > For example ADSL connections and so on. Or links Europe-USA etc. This > > is not about performance of server applications like apache benchmarking. > > This is definatly something you could do with Emulab (that's why we have > one), but if you just need to simulate agrigate link characteristics, > Emulab would be massive overkill. I'm only interesed in aggrigated link characteristics. -- Andre From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 07:28:37 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EFAA16A51D; Tue, 2 Mar 2004 07:28:37 -0800 (PST) Received: from vhost109.his.com (vhost109.his.com [216.194.225.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id D78EF43D1D; Tue, 2 Mar 2004 07:28:35 -0800 (PST) (envelope-from brad.knowles@skynet.be) Received: from [10.0.1.3] (localhost.his.com [127.0.0.1]) by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id i22FSNxg006439; Tue, 2 Mar 2004 10:28:27 -0500 (EST) (envelope-from brad.knowles@skynet.be) Mime-Version: 1.0 X-Sender: bs663385@127.0.0.1 Message-Id: In-Reply-To: <4044A138.F444D224@freebsd.org> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <4044A138.F444D224@freebsd.org> Date: Tue, 2 Mar 2004 16:28:20 +0100 To: Andre Oppermann From: Brad Knowles Content-Type: text/plain; charset="us-ascii" ; format="flowed" cc: Brad Knowles cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 15:28:37 -0000 At 3:59 PM +0100 2004/03/02, Andre Oppermann wrote: > Zebra is definatly *not* a piece of s*** as you make it sound here. Well, that was certainly the impression I got from Henning Brauer at FOSDEM. Maybe I misunderstood him, or maybe he has different views on this software than you do. To properly clarify this matter, you should probably talk to him directly and find out if his opinions on zebra/quagga really are as different from yours, and if so then I'll be glad to make a public apology. However, until then, I will stand by what I remember of his talk, and neither you nor anyone else is going to make me change my mind, certainly not by beating your chest. > You need GigE, T1/E1, E3/T3 and STM-1 these days. Everything else is dead. From what I understand from Henning, he's going to be dumping E-1/T-1, E3-T3, and probably also STM-1, because you can't get those kinds of interfaces for regular PC-type boxes. I'm not sure I agree with him 100%, but I can certainly understand why he'd want to simplify his life. > Ok, again Zebra/Quagga is not "crap". The same with DJBware which is > no "crap" either. If you don't like it just say so but refrain from > dirt-talking it. It doesn't make your point any stronger. Beating your chest louder is not likely to make me believe that you're right. If you want to get off onto a "Church of Dan" rant, I can certainly do that, and I can point out a whole ark-load of flaws -- most of which are simple basic facts which Dan himself admits to, but when he says them they're "facts" and when I say them they're "libel" or "slander". Yeah, riiiiiiiiiiiiiight. > The bgpd from OpenBSD will surely make it's way into FreeBSD [*]. The > main developer besides Henning sits about 5 meters away from me in > my office. If you look at it then you'll find out that I'm not really > innocent that bgpd ;-) I'm glad to hear that. > [*] In FreeBSD it will be a port. I don't know why a bgpd should be > in the base system. I don't know. Why should we have any routing software at all in the base system? > It would be nice if you could calm down, stop your mis-informed > accusations and rants and actually try to be helpful and progressive > to the projects which try to do it better. Thank you very much. Show me the words from Henning himself where I have mis-represented his views on zebra/quagga, and I will gladly apologize in public. Until then, I stand by what I have said. -- Brad Knowles, "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++) From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 07:35: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 5FE0916A4CE; Tue, 2 Mar 2004 07:35:42 -0800 (PST) Received: from guns.icir.org (adsl-68-76-113-50.dsl.bcvloh.ameritech.net [68.76.113.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAAF443D31; Tue, 2 Mar 2004 07:35:41 -0800 (PST) (envelope-from mallman@guns.icir.org) Received: from guns.icir.org (localhost [127.0.0.1]) by guns.icir.org (Postfix) with ESMTP id A84E977A6FA; Tue, 2 Mar 2004 10:35:40 -0500 (EST) To: Andre Oppermann From: Mark Allman In-Reply-To: <4044928C.AF49FD38@freebsd.org> Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: Blow Up the Outside World MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Date: Tue, 02 Mar 2004 10:35:40 -0500 Sender: mallman@guns.icir.org Message-Id: <20040302153540.A84E977A6FA@guns.icir.org> cc: freebsd-current@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: mallman@icir.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2004 15:35:42 -0000 --=-=-= > TCP buffer sizing involves mainly two areas. One is good RTT > measurements to be able to estimate the bw*delay product well and the > other is information about memory (mbuf) usage in the networking > system to do the right thing if memory gets low. Why try to measure the bw*delay? Why not use the trick from PSC's autotuning paper whereby you just try to ensure that the socket buffer size is always some multiple (2-4, I think) of the congestion window? I.e., so the congestion window dictates the performance and the socket buffer is not a factor. Of course, you have to figure out what to do to all the connections when there is not enough memory for such socket buffer sizes. But, fundementally, that seems like a much better approach to me. And, thanks for taking this all on! It sounds wonderful! allman -- Mark Allman -- ICIR -- http://www.icir.org/mallman/ --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFARKnMWyrrWs4yIs4RAuq3AJ9Tu73LDANRPd/Lgz2lbBf0Umm11wCghIwK 4cj9M/HPJMuhPbHtAZw2t7I= =avhH -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 07:45: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 487A816A4CE; Tue, 2 Mar 2004 07:45:59 -0800 (PST) Received: from vhost109.his.com (vhost109.his.com [216.194.225.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id E747243D1D; Tue, 2 Mar 2004 07:45:58 -0800 (PST) (envelope-from brad.knowles@skynet.be) Received: from [10.0.1.3] (localhost.his.com [127.0.0.1]) by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id i22Fjmxe007433; Tue, 2 Mar 2004 10:45:49 -0500 (EST) (envelope-from brad.knowles@skynet.be) Mime-Version: 1.0 X-Sender: bs663385@127.0.0.1 Message-Id: In-Reply-To: <4044A36A.64E885BE@freebsd.org> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302125935.GA25835@cell.sick.ru> <4044A36A.64E885BE@freebsd.org> Date: Tue, 2 Mar 2004 16:39:38 +0100 To: Andre Oppermann From: Brad Knowles Content-Type: text/plain; charset="us-ascii" ; format="flowed" cc: Brad Knowles cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 15:45:59 -0000 At 4:08 PM +0100 2004/03/02, Andre Oppermann wrote: > Gleb is doing the same, and so am I. However you are not. Do you > run BGP in your network? I'm not running an ISP that is multiply connected to at least two metro-area NAPs and has multiple upstreams at both sites, no. I would be very interested to be involved in the network management of a medium to large-sized ISP, however. > At least for me on FreeBSD Zebra has been very stable for me. There > is no need to always "change" things. That's wonderful for you. However, that doesn't change the criticism that Henning has levelled at zebra/quagga. > What is you point? Do you use Zebra? Are you affected by it? Or > are you just ranting? My point is that zebra/quagga have significant limitations that restrict their usefulness, due to the design of the system. Moreover, the development on zebra has effectively stalled since the author got hired away to do that kind of work professionally, and development on quagga has apparently been sporadic and relatively limited, presumably due to the fact that they don't have replacement developers of the same caliber. If we want to get to the point where we can have a reasonable expectation of throwing away all cisco, juniper, Foundry, and other routing hardware and replace them with something that is easier to install, configure, monitor, and manage, then I think we need to be looking beyond zebra/quagga. > And you should stop flaming anyone if you haven't ever used or done > what you are blabbering about. If you think this is flaming, then you have never seen flaming. At this stage, this is nothing more than a luke-warm disagreement. > Sorry, but OpenBSDs bgpd wont to any of that either. This is mostly > hardware that needs to be redundant. Not much you can in bgpd. Not in bgpd per se, no. But by then you'd have added more protocol support to the daemon and that name would no longer be appropriate. -- Brad Knowles, "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++) From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 07:46: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 F328316A519; Tue, 2 Mar 2004 07:46:04 -0800 (PST) Received: from vhost109.his.com (vhost109.his.com [216.194.225.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D62243D2D; Tue, 2 Mar 2004 07:46:04 -0800 (PST) (envelope-from brad.knowles@skynet.be) Received: from [10.0.1.3] (localhost.his.com [127.0.0.1]) by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id i22Fjmxg007433; Tue, 2 Mar 2004 10:45:52 -0500 (EST) (envelope-from brad.knowles@skynet.be) Mime-Version: 1.0 X-Sender: bs663385@127.0.0.1 Message-Id: In-Reply-To: <4044A5B4.789778D8@freebsd.org> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> <20040302090219.GC3438@astral-on.net> <20040302135230.GF3438@astral-on.net> <4044A5B4.789778D8@freebsd.org> Date: Tue, 2 Mar 2004 16:45:47 +0100 To: Andre Oppermann From: Brad Knowles Content-Type: text/plain; charset="us-ascii" ; format="flowed" cc: Brad Knowles cc: freebsd-current@freebsd.org cc: ad@astral-on.net cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 15:46:05 -0000 At 4:18 PM +0100 2004/03/02, Andre Oppermann wrote: > I'd like to see you do any real work in this area instead of > producing many and longs emails with lots of mis-informed rants > in them. Yes, this my official put-up-or-shut-up call to you. I'm not a programmer. I haven't done anything that I consider to be proper "programming" in over fifteen years. If there is anything I can do to help with the skills I have as a senior unix systems administrator and a small network of machines downstairs that I need to put together (four UltraSPARC 10 clones, a dishwasher-size four-processor Intel OEM fileserver-to-be, an ancient SPARC-4 clone, and an ancient Pentium-133 laptop w/ 48MB of RAM), then I'll be glad to do what I can to help. -- Brad Knowles, "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++) From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 07:58:48 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 E636D16A4CE; Tue, 2 Mar 2004 07:58:48 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F07743D2F; Tue, 2 Mar 2004 07:58:46 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id C8AC36543B; Tue, 2 Mar 2004 15:58:45 +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 26017-03-9; Tue, 2 Mar 2004 15:58:45 +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 08FA565216; Tue, 2 Mar 2004 15:58:45 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id 3BFFE18; Tue, 2 Mar 2004 15:58:44 +0000 (GMT) Date: Tue, 2 Mar 2004 15:58:44 +0000 From: Bruce M Simpson To: Brad Knowles Message-ID: <20040302155844.GP4561@saboteur.dek.spc.org> Mail-Followup-To: Brad Knowles , Gleb Smirnoff , Andre Oppermann , freebsd-net@freebsd.org References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: cc: freebsd-net@freebsd.org cc: Andre Oppermann Subject: Re: My planned work on networking stack 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, 02 Mar 2004 15:58:49 -0000 On Tue, Mar 02, 2004 at 01:07:58PM +0100, Brad Knowles wrote: [..] > His only issue with using exclusively PC equipment for handling > routing is all those strange WAN protocols and cards for which > hardware cards are rarely available beyond vendors like cisco or > Juniper. That's why he's going pure Ethernet protocols/hardware > throughout all his networks, including his upstream feeds, so that he > can dump all that expensive ancient legacy routing hardware. That won't necessarily scale... but YMMV... > If anything, I'd be inclined to look towards his work for OpenBSD > and see if that could be imported into FreeBSD (and maybe improved, > with contributions given back to him), rather than mess around with > crap like zebra or quagga. The last time I looked at his code it looked pretty much like a straight lift from the MRTD tree. This was a few months ago... and this was brief... > Oh, and it would be nice if someone somewhere started thinking > about a mesh routing implementation for *BSD, either AODV or > something else. //depot/user/bms/aodv/aodvd/... BMS From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 08:09:08 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 977EB16A4CE; Tue, 2 Mar 2004 08:09:08 -0800 (PST) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD1B343D1D; Tue, 2 Mar 2004 08:09:07 -0800 (PST) (envelope-from glebius@cell.sick.ru) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.9/8.12.8) with ESMTP id i22G94QE027499 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Mar 2004 19:09:05 +0300 (MSK) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.9/8.12.6/Submit) id i22G92Px027498; Tue, 2 Mar 2004 19:09:02 +0300 (MSK) Date: Tue, 2 Mar 2004 19:09:02 +0300 From: Gleb Smirnoff To: Andre Oppermann Message-ID: <20040302160902.GB26977@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Andre Oppermann , Kris Kennaway , Wes Peters , freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> <20040302085556.GA23734@cell.sick.ru> <20040302092825.GD884@saboteur.dek.spc.org> <20040302095134.GA24078@cell.sick.ru> <40449B8E.A48B39B0@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <40449B8E.A48B39B0@freebsd.org> User-Agent: Mutt/1.5.6i cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: Kris Kennaway Subject: Re: My planned work on networking stack 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, 02 Mar 2004 16:09:08 -0000 Andre, On Tue, Mar 02, 2004 at 03:34:54PM +0100, Andre Oppermann wrote: A> > B> As to the second part of your mail: That sounds like a reasonable suggestion, A> > B> I am sure Andre and others are paying attention to this and will take it on A> > B> board when an implementation is nearer. A> > A> > If this is OK from you, I start working on it (second variant using sockaddr_aspath). A> > I'm willing to see this feature, and I have a good testing conditions for it. A> A> Putting the AS path into the kernel routing table is certainly not the A> right thing to do. The kernel fib must be as small as possible. All A> information how a route made it there is pretty much irrelevant and A> only the business of the routing protocol daemons. However, I can imagine at least 2 things, where we need AS pathes in kernel (at least optionally). Nowadays, for continuing my work on bringing netflow implementation I need AS path info in kernel. If we are planning to create routing solution based on FreeBSD, we will need to support netflow. And only in-kernel flow catching can give us high performance. In nearest future, you are going to implement policy routing. Are you going to support constructions like: "match as-path XXX; set nexthop a.b.c.d"? I do not insist that AS pathes in kernel are good idea. If you show me an other way to get AS information when constructing netflow exports in kernel, I'd be thankful. I'd be also thankful if you describe how policy routing can be implemented while no AS info in kernel. What do other FreeBSD networking withards think? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 08:14:09 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 6AF0316A4DD; Tue, 2 Mar 2004 08:14:09 -0800 (PST) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14D6143D41; Tue, 2 Mar 2004 08:14:09 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id i22GE7Da037928 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK CN=khavrinen.lcs.mit.edu issuer=SSL+20Client+20CA); Tue, 2 Mar 2004 11:14:08 -0500 (EST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.9/8.12.9/Submit) id i22GE5mR037925; Tue, 2 Mar 2004 11:14:05 -0500 (EST) (envelope-from wollman) Date: Tue, 2 Mar 2004 11:14:05 -0500 (EST) From: Garrett Wollman Message-Id: <200403021614.i22GE5mR037925@khavrinen.lcs.mit.edu> To: Bruce M Simpson In-Reply-To: <20040302092825.GD884@saboteur.dek.spc.org> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> <20040302085556.GA23734@cell.sick.ru> <20040302092825.GD884@saboteur.dek.spc.org> X-Spam-Score: -9.9 () IN_REP_TO,REFERENCES X-Scanned-By: MIMEDefang 2.37 cc: freebsd-net@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: Re: My planned work on networking stack 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, 02 Mar 2004 16:14:09 -0000 < said: > routed we support largely out of nostalgia, I guess. Modern routed does more than just RIP; it's responsible for all sorts of routing-table management tasks that we mostly just pretend don't exist (e.g., responding to RTM_LOSING messages). -GAWollman From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 08: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 A2F4F16A4CE; Tue, 2 Mar 2004 08:35:31 -0800 (PST) Received: from ran.psg.com (ip166.usw253.dsl-acs2.sea.iinet.com [209.20.253.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AC5443D31; Tue, 2 Mar 2004 08:35:31 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.30; FreeBSD) id 1AyCri-000IRV-Pd; Tue, 02 Mar 2004 08:35:30 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 2 Mar 2004 08:35:30 -0800 To: Brad Knowles References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <4044A138.F444D224@freebsd.org> Message-Id: <20040302163531.6AC5443D31@mx1.FreeBSD.org> cc: freebsd-net@freebsd.org cc: Andre Oppermann Subject: Re: My planned work on networking stack 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, 02 Mar 2004 16:35:31 -0000 >> You need GigE, T1/E1, E3/T3 and STM-1 these days. Everything >> else is dead. > From what I understand from Henning, he's going to be dumping > E-1/T-1, E3-T3, and probably also STM-1, because you can't get > those kinds of interfaces for regular PC-type boxes. I'm not > sure I agree with him 100%, but I can certainly understand why > he'd want to simplify his life. i am confused. just as the fib is quite separate from the rib(s), are not the device drivers quite separate from the routing engine(s)? as far as routing and forwarding go, the data should have been un-framed from the particular layer1/2 encaps, and be simple ip packets (except in the case of is-is). randy From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 09:14:53 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7258B16A4CE; Tue, 2 Mar 2004 09:14:53 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE7B843D1D; Tue, 2 Mar 2004 09:14:52 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 0ABAE654EA; Tue, 2 Mar 2004 17:14:51 +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 26928-03-2; Tue, 2 Mar 2004 17:14:50 +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 EFF0B654CD; Tue, 2 Mar 2004 17:14:49 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id 23C9918; Tue, 2 Mar 2004 17:14:49 +0000 (GMT) Date: Tue, 2 Mar 2004 17:14:49 +0000 From: Bruce M Simpson To: Brad Knowles , Gleb Smirnoff , Andre Oppermann , freebsd-net@freebsd.org Message-ID: <20040302171449.GF6234@saboteur.dek.spc.org> Mail-Followup-To: Brad Knowles , Gleb Smirnoff , Andre Oppermann , freebsd-net@freebsd.org References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302155844.GP4561@saboteur.dek.spc.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kORqDWCi7qDJ0mEj" Content-Disposition: inline In-Reply-To: <20040302155844.GP4561@saboteur.dek.spc.org> Subject: Re: My planned work on networking stack 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, 02 Mar 2004 17:14:53 -0000 --kORqDWCi7qDJ0mEj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [in response to off-list mail] On Tue, Mar 02, 2004 at 03:58:44PM +0000, Bruce M Simpson wrote: > On Tue, Mar 02, 2004 at 01:07:58PM +0100, Brad Knowles wrote: > > If anything, I'd be inclined to look towards his work for OpenBSD=20 > > and see if that could be imported into FreeBSD (and maybe improved,=20 > > with contributions given back to him), rather than mess around with=20 > > crap like zebra or quagga. I'm open to bringing it on board as a port, but I don't feel that carrying a BGP daemon around in the base system is in the best interests of the Project or our user base. > The last time I looked at his code it looked pretty much like a straight > lift from the MRTD tree. This was a few months ago... and this was brief.= =2E. Let me just qualify this statement - I have not had the chance to have anything more than a cursory glance at this code, this was a 'prima facie' impression when I was heavily involved with other work. Not to disrespect anyone else's hard work, as some people mistakenly seem to be under this impression. BMS --kORqDWCi7qDJ0mEj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Comment: '' iD8DBQFARMEIueUpAYYNtTsRAoRgAJ9QACx3sIjzM3StnCxZ5TBP0DWA6ACeJYAf CFSyrGH6ghodwOJ2IWJaAfc= =i4lf -----END PGP SIGNATURE----- --kORqDWCi7qDJ0mEj-- From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 10:10: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 0E8CB16A4CF; Tue, 2 Mar 2004 10:10:11 -0800 (PST) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5184C43D2D; Tue, 2 Mar 2004 10:10:10 -0800 (PST) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 3BCE01FF931; Tue, 2 Mar 2004 19:10:08 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 3DC221FF91D; Tue, 2 Mar 2004 19:10:06 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id A1847154E2; Tue, 2 Mar 2004 18:05:57 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 960C515336; Tue, 2 Mar 2004 18:05:57 +0000 (UTC) Date: Tue, 2 Mar 2004 18:05:57 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: freebsd-net@freebsd.org In-Reply-To: <4043B6BA.B847F081@freebsd.org> Message-ID: References: <4043B6BA.B847F081@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: freebsd-current@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 18:10:11 -0000 On Mon, 1 Mar 2004, Andre Oppermann wrote: Hi, > I put this up for coordination and cooperation in my planned work on the > FreeBSD networking system. This is my todo list of things I want to do > from now through summer 04. If you are or intend to work on one of these > please step forward so we can coordinate. :-) ... > [] other stuff that I happen to stumble over... ;-) I still have in mind that I would like to see vimage[1] in HEAD one day ... I think it would be a pretty cool feature to have. If one can keep this in mind when doing greater modelling on the network stack it might help the one who will - at some time - find the time to ingtegrate it. [1] http://www.tel.fer.hr/zec/BSD/vimage/index.html -- Greetings Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT 56 69 73 69 74 http://www.zabbadoz.net/ From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 11:09: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 D454316A531; Tue, 2 Mar 2004 11:09:22 -0800 (PST) Received: from ptb-relay02.plus.net (ptb-relay02.plus.net [212.159.14.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4395F43D1F; Tue, 2 Mar 2004 11:09:22 -0800 (PST) (envelope-from james@physicalsegment.com) Received: from [81.174.238.178] (helo=mail.physicalsegment.com) by ptb-relay02.plus.net with esmtp (Exim) id 1AyFGa-000KAe-L4; Tue, 02 Mar 2004 19:09:20 +0000 Received: from [10.0.0.192] (helo=jd2400) by mail.physicalsegment.com with smtp (Exim 4.20) id 1AyFGV-0004Ya-Jx; Tue, 02 Mar 2004 19:09:15 +0000 Message-ID: <00d301c40089$8a035410$c000000a@jd2400> From: "James Read" To: "Bjoern A. Zeeb" , References: <4043B6BA.B847F081@freebsd.org> Date: Tue, 2 Mar 2004 19:06:59 -0000 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 X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: freebsd-current@freebsd.org Subject: Re: My planned work on networking stack (vimage) 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, 02 Mar 2004 19:09:23 -0000 > I still have in mind that I would like to see vimage[1] in HEAD one day > ... I think it would be a pretty cool feature to have. If one can keep > this in mind when doing greater modelling on the network stack it > might help the one who will - at some time - find the time to > ingtegrate it. > > > [1] http://www.tel.fer.hr/zec/BSD/vimage/index.html > In my opinion, this would be a _VERY_ good 'feature' to add into the system. As it stands there is minimal 'networking' in a jail from a users point of view, and also an administrators view aswell (granted this isnt exactly what jail was designed to do, and so on). This could be more then an asset to the whole jail architecture, by providing a clone-able network stack within jails. For instance, you could then run programs/services like NFS etc from jail to jail without having to lock down services offered from the jail 'host'. If this can in _any way_ be pushed/implemented (with minimal distruption) so that is it in HEAD/CURRENT then its well on the way to complementing what 'jail' does. This is one thing that I would like to use, without patching systems. But then thats just my 'wish list' opinion of it. Regards, James. ( I apoligise for the cross post, it's my first time posting to -current & -net, I just thought it would be worth my 2c ) -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. Mailscanner thanks transtec Computers for their support. From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 11:33:02 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 7A6A516A4CE; Tue, 2 Mar 2004 11:33:02 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C02A43D1D; Tue, 2 Mar 2004 11:33:02 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 2E0DB6520E; Tue, 2 Mar 2004 19:33:01 +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 28383-02; Tue, 2 Mar 2004 19:33:00 +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 D37BE651FA; Tue, 2 Mar 2004 19:32:59 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id C54CF18; Tue, 2 Mar 2004 19:32:58 +0000 (GMT) Date: Tue, 2 Mar 2004 19:32:58 +0000 From: Bruce M Simpson To: Gleb Smirnoff , Andre Oppermann , Kris Kennaway , Wes Peters , freebsd-net@freebsd.org, freebsd-current@freebsd.org Message-ID: <20040302193258.GD7115@saboteur.dek.spc.org> Mail-Followup-To: Gleb Smirnoff , Andre Oppermann , Kris Kennaway , Wes Peters , freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> <20040302085556.GA23734@cell.sick.ru> <20040302092825.GD884@saboteur.dek.spc.org> <20040302095134.GA24078@cell.sick.ru> <40449B8E.A48B39B0@freebsd.org> <20040302160902.GB26977@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040302160902.GB26977@cell.sick.ru> Subject: Re: My planned work on networking stack 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, 02 Mar 2004 19:33:02 -0000 On Tue, Mar 02, 2004 at 07:09:02PM +0300, Gleb Smirnoff wrote: > I do not insist that AS pathes in kernel are good idea. If you show me an > other way to get AS information when constructing netflow exports in kernel, > I'd be thankful. I'd be also thankful if you describe how policy routing can be > implemented while no AS info in kernel. > What do other FreeBSD networking withards think? I don't see any reason why we couldn't accept, for example, a 32-bit cookie for abuse by a userland daemon, with pid, as it pleases (via an rtmsg extension and PF_ROUTE). That is generic enough to provide the tie-in needed with the userland RIB and the kernel FIB. ABI breakage may occur, but I would consider that the PF_ROUTE code is in need of an overhaul anyway (see my mail to ru@ from some months ago on -current or -net with code able to panic a kernel through malformed rtmsg contents). BMS From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 11: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 19EF116A4CE; Tue, 2 Mar 2004 11:35:31 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82C9943D31; Tue, 2 Mar 2004 11:35:30 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id B574B654D7; Tue, 2 Mar 2004 19:35:28 +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 28383-02-10; Tue, 2 Mar 2004 19:35:28 +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 C210C654D3; Tue, 2 Mar 2004 19:35:27 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id 001B018; Tue, 2 Mar 2004 19:35:26 +0000 (GMT) Date: Tue, 2 Mar 2004 19:35:26 +0000 From: Bruce M Simpson To: Brad Knowles Message-ID: <20040302193526.GE7115@saboteur.dek.spc.org> Mail-Followup-To: Brad Knowles , ad@astral-on.net, freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> <20040302090219.GC3438@astral-on.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: ad@astral-on.net Subject: Re: My planned work on networking stack 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, 02 Mar 2004 19:35:31 -0000 On Tue, Mar 02, 2004 at 02:36:50PM +0100, Brad Knowles wrote: [snip] > Oh, and then there are all the operational issues where > zebra/quagga can't keep sessions going when a neighbor flaps, etc.... > Those would require re-architecting the whole routing system, at > which point it might make a lot more sense to go with a different > implementation -- such as bgpd from OpenBSD. Point taken, Brad. We look forward to your ports submission. BMS From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 11:38: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 3D63216A4CE; Tue, 2 Mar 2004 11:38:38 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB64C43D2D; Tue, 2 Mar 2004 11:38:37 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 00E946520E; Tue, 2 Mar 2004 19:38:37 +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 28383-02-16; Tue, 2 Mar 2004 19:38:36 +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 31850651FA; Tue, 2 Mar 2004 19:38:32 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id 2243018; Tue, 2 Mar 2004 19:38:31 +0000 (GMT) Date: Tue, 2 Mar 2004 19:38:31 +0000 From: Bruce M Simpson To: Andre Oppermann Message-ID: <20040302193831.GF7115@saboteur.dek.spc.org> Mail-Followup-To: Andre Oppermann , Wes Peters , freebsd-net@freebsd.org, freebsd-current@freebsd.org, James References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <404496AE.300E1457@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <404496AE.300E1457@freebsd.org> cc: freebsd-current@freebsd.org cc: James cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 19:38:38 -0000 On Tue, Mar 02, 2004 at 03:14:06PM +0100, Andre Oppermann wrote: > > I've been fielding suggestions from individuals who feel using a multi-bit > > trie might be more suitable for achieving higher PPS rates. > > Yes. Which one should not matter. I want to make an API for the IPv4 > routing code. Different routing implementations then can be loaded or > changed at runtime or boot time. This sounds like an excellent idea. I agree that the PF_ROUTE interface is long in need of an overhaul (see previous mail to this effect in archives). The bit mask extraction sockaddr fandango we do to get things like netmasks in and out is nothing short of evil. The routing code could also benefit from some style cleanup and the use of the UMA zone allocator. > > > would the policy-routing optioned table sort of similar to VRF's or > > > different routing instances that could potentially be tied to userlands > > > like Quagga? > > That's the plan, I believe, anyway... It would be nice if Quagga could be > > taught about how to add TCP-MD5 keys to both FreeBSD and OpenBSD SADBs. > > What is the relationship tcp-md5 --> policy-routing? It's another one of those cross OS features which, whilst deceptively simple on the surface, requires some hacking of the routing daemon to grok PF_KEY messages (a well defined interface). We need a well-defined interface which is hopefully cross OS for policy routing. BMS From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 11:43: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 5174016A4DB; Tue, 2 Mar 2004 11:43:45 -0800 (PST) Received: from snafu.adept.org (adsl-67-117-158-73.dsl.snfc21.pacbell.net [67.117.158.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28CAC43D1F; Tue, 2 Mar 2004 11:43:45 -0800 (PST) (envelope-from mike@adept.org) Received: by snafu.adept.org (Postfix, from userid 1000) id 67DFB9EEF0; Tue, 2 Mar 2004 11:43:40 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by snafu.adept.org (Postfix) with ESMTP id 3826D9B148; Tue, 2 Mar 2004 11:43:40 -0800 (PST) Date: Tue, 2 Mar 2004 11:43:40 -0800 (PST) From: Mike Hoskins To: net@freebsd.org In-Reply-To: Message-ID: <20040302113821.S53840@snafu.adept.org> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302084321.GA21729@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 19:43:45 -0000 On Tue, 2 Mar 2004, Brad Knowles wrote: > > What's difference (*currently*) beetwen FreeBSD+Zebra and Cisco routers? > Support for VRRP? Support for various other routing protocols > not covered by zebra/quagga -- at least not yet, if ever? Support > for line cards and other devices that do not exist in a format you > can plug into a PC? actually, there's a lot of differences at the hardware level (beside available interfaces) -- some of which will probably always be there (on any platform). just post this question to nanog, and wait for your inbox to be flooded. (yes, hard to believe, but there really are technically justifiable reasons a lot of big names use hardware engineered for the task of routing beside paying ridiculous fees to the vendors.) as for vrrp, there is an opensource/RFC-compliant implementation that works on FreeBSD. actually, it was coded specifically for FreeBSD. http://freshmeat.net/projects/freebsd-hut i have never used this on a large-scale (i've never considered pre-1.0 software "stable"), but have used it many places for failover inside clusters with satisfactory results. -m From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 12:01:18 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D39A416A4CF; Tue, 2 Mar 2004 12:01:17 -0800 (PST) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 698A243D2F; Tue, 2 Mar 2004 12:01:17 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (sccrmhc12) with ESMTP id <2004030220011101200h27a8e>; Tue, 2 Mar 2004 20:01:16 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id MAA77452; Tue, 2 Mar 2004 12:01:09 -0800 (PST) Date: Tue, 2 Mar 2004 12:01:08 -0800 (PST) From: Julian Elischer To: James Read In-Reply-To: <00d301c40089$8a035410$c000000a@jd2400> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "Bjoern A. Zeeb" cc: freebsd-current@freebsd.org cc: freebsd-net@freebsd.org Subject: Was: My planned work on networking stack (vimage) 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, 02 Mar 2004 20:01:18 -0000 The major problem with 'vimage' is that all statics are moved to a large structure so that they can be duplicated... e.g. The root of the interface list gets moved there so that each vimage has its own list of interfaces. This is ok for statically compiled modules, but what can you do for adding new modules.. either statically of dynamically.. You end up having to have each module have it's own structure and each vimage has to have its own list or array of such structures.. so to use the example above, ifp = TAILQ_HEAD(ifhead) /* I forget the exact names */ becomes something like: ifp = TAILQ_HEAD((struct netbase_statics*)(p->vimage[netbase_index])->ifhead); Where netbase_index is a global set when the networking base module is loaded or linked in, (no idea by who), and the 'vimage' becomes an array of void * pointers, each pointing to a different structure aof variables that were once static, each structure being variables related to a different module. This could be done but it starts to look a lot like the TLS (Thread Local Storage) stuff. And it would pretty definitly have a performance impact. On Tue, 2 Mar 2004, James Read wrote: > > I still have in mind that I would like to see vimage[1] in HEAD one day > > ... I think it would be a pretty cool feature to have. If one can keep > > this in mind when doing greater modelling on the network stack it > > might help the one who will - at some time - find the time to > > ingtegrate it. > > > > > > [1] http://www.tel.fer.hr/zec/BSD/vimage/index.html > > > > > > > > In my opinion, this would be a _VERY_ good 'feature' to add into the system. > As it stands there is minimal 'networking' in a jail from a users point of > view, and also an administrators view aswell (granted this isnt exactly what > jail was designed to do, and so on). This could be more then an asset to the > whole jail architecture, by providing a clone-able network stack within > jails. For instance, you could then run programs/services like NFS etc from > jail to jail without having to lock down services offered from the jail > 'host'. > > If this can in _any way_ be pushed/implemented (with minimal distruption) so > that is it in HEAD/CURRENT then its well on the way to complementing what > 'jail' does. > > This is one thing that I would like to use, without patching systems. But > then thats just my 'wish list' opinion of it. > > Regards, > > James. > > ( I apoligise for the cross post, it's my first time posting to -current > & -net, I just thought it would be worth my 2c ) > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > Mailscanner thanks transtec Computers for their support. > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 12:17:12 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E900316A4CE; Tue, 2 Mar 2004 12:17:11 -0800 (PST) Received: from vorbis.noc.easynet.net (vorbis.noc.easynet.net [195.40.1.254]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73BEE43D41; Tue, 2 Mar 2004 12:17:11 -0800 (PST) (envelope-from chrisy@vorbis.noc.easynet.net) Received: from chrisy by vorbis.noc.easynet.net with local (Exim 4.10) id 1AyGK9-000J36-00; Tue, 02 Mar 2004 20:17:05 +0000 Date: Tue, 2 Mar 2004 15:17:05 -0500 From: Chris Luke To: Gleb Smirnoff , Wes Peters , Andre Oppermann , freebsd-net@freebsd.org, freebsd-current@freebsd.org Message-ID: <20040302201704.GA72944@flix.net> Mail-Followup-To: Chris Luke , Gleb Smirnoff , Wes Peters , Andre Oppermann , freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040302082625.GE22985@cell.sick.ru> User-Agent: Mutt/1.4.1i Organization: The Flirble Internet Exchange X-URL: http://www.flix.net/ X-FTP: ftp://ftp.flirble.org/ Sender: Chris Luke Subject: Re: My planned work on networking stack 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, 02 Mar 2004 20:17:12 -0000 Gleb Smirnoff wrote (on Mar 02): > Currently I'm working on my Netflow implementation, and I have faced the > following problem: I've already got global routing in my routing table, but it > lacks AS (Autonomous System) information. The routing daemon (zebra in my case) > already knows ASes, but this informations is lost when routing information is > injected into kernel. It'll be nice to add AS path to struct rtentry. I overcame this same problem by hacking a simple query mechanism into bgpd. My netflow categoriser retains a small routing information cache, and queries the bgpd for aspath/community information as and when it's needed. All my netflow stuff is done off-host, and so is my netflow bgp. I use bgpd with a view per router that I collect netflow data from, and my netflow system is configured to relate these things together. Chris. -- == chrisy@flix.net From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 12:22: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 E99F016A4CE; Tue, 2 Mar 2004 12:22:03 -0800 (PST) Received: from mail.tel.fer.hr (zg04-080.dialin.iskon.hr [213.191.137.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id B394943D3F; Tue, 2 Mar 2004 12:22:01 -0800 (PST) (envelope-from zec@tel.fer.hr) Received: from marko-tp.katoda.net (marko@dhcp11.katoda.net [192.168.200.111]) by mail.tel.fer.hr (8.12.6/8.12.6) with ESMTP id i22KLsuP004239; Tue, 2 Mar 2004 21:21:55 +0100 (CET) (envelope-from zec@tel.fer.hr) From: Marko Zec To: "James Read" , "Bjoern A. Zeeb" , Date: Tue, 2 Mar 2004 21:21:13 +0100 User-Agent: KMail/1.5.4 References: <4043B6BA.B847F081@freebsd.org> <00d301c40089$8a035410$c000000a@jd2400> In-Reply-To: <00d301c40089$8a035410$c000000a@jd2400> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200403022121.15400.zec@tel.fer.hr> cc: freebsd-current@freebsd.org Subject: Re: My planned work on networking stack (vimage) 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, 02 Mar 2004 20:22:04 -0000 On Tuesday 02 March 2004 20:06, James Read wrote: > > I still have in mind that I would like to see vimage[1] in HEAD one > > day ... I think it would be a pretty cool feature to have. If one > > can keep this in mind when doing greater modelling on the network > > stack it might help the one who will - at some time - find the time > > to ingtegrate it. > > > > > > [1] http://www.tel.fer.hr/zec/BSD/vimage/index.html > > > > In my opinion, this would be a _VERY_ good 'feature' to add into the > system. As it stands there is minimal 'networking' in a jail from a > users point of view, and also an administrators view aswell (granted > this isnt exactly what jail was designed to do, and so on). This > could be more then an asset to the whole jail architecture, by > providing a clone-able network stack within jails. For instance, you > could then run programs/services like NFS etc from jail to jail > without having to lock down services offered from the jail 'host'. > > If this can in _any way_ be pushed/implemented (with minimal > distruption) so that is it in HEAD/CURRENT then its well on the way > to complementing what 'jail' does. The fact that the virtualization patches are highly disruptive by their nature seem to me as the #1 reason they might never become suitable for inclusion in the main tree. Namely, the basic idea is to replace (most of) the global symbols/variables throughout the entire network stack with their counterparts residing in "clonable" structures or resource containers. While such a concept doesn't introduce any real-life performance penalty worth mentioning, the real issue is that the compatibility / synchronization with any parallel or external code would be unavoidably lost once the patchset would be committed. However I might be wrong... It would be nice if a wider discussion could try to weight out all pros and cons and yield a consensus whether or not any vimage-style patches could have any future in the official FreeBSD tree... Cheers, Marko From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 12:49: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 6FEAE16A4CE; Tue, 2 Mar 2004 12:49:31 -0800 (PST) Received: from mail.tel.fer.hr (zg04-080.dialin.iskon.hr [213.191.137.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26A2043D45; Tue, 2 Mar 2004 12:49:30 -0800 (PST) (envelope-from zec@tel.fer.hr) Received: from marko-tp.katoda.net (marko@dhcp11.katoda.net [192.168.200.111]) by mail.tel.fer.hr (8.12.6/8.12.6) with ESMTP id i22KnGuP004242; Tue, 2 Mar 2004 21:49:17 +0100 (CET) (envelope-from zec@tel.fer.hr) From: Marko Zec To: Julian Elischer , James Read Date: Tue, 2 Mar 2004 21:48:37 +0100 User-Agent: KMail/1.5.4 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200403022148.38002.zec@tel.fer.hr> cc: "Bjoern A. Zeeb" cc: freebsd-current@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: Was: My planned work on networking stack (vimage) 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, 02 Mar 2004 20:49:31 -0000 On Tuesday 02 March 2004 21:01, Julian Elischer wrote: > The major problem with 'vimage' is that all statics are moved to a > large structure so that they can be duplicated... > e.g. The root of the interface list gets moved there so that each > vimage has its own list of interfaces. > > > This is ok for statically compiled modules, but what can you do for > adding new modules.. either statically of dynamically.. > > You end up having to have each module have it's own structure and > each vimage has to have its own list or array of such structures.. > Hi, Julian! True, this can also become an issue. However, the question is how many modules in real-life do require per network stack symbols/structures. For example, the original vimage patch already included the necessary hooks and reserved the appropriate fields for ipfw or dummynet to be loaded / unloaded dynamically with no major problems. On the other hand, no device driver should be affected by the virtualization, and shouldn't require any network-stack specific handling. And IMO the device drivers are those which are most commonly implemented as loadable modules. Cheers, Marko > > so to use the example above, > ifp = TAILQ_HEAD(ifhead) /* I forget the exact names */ > > becomes something like: > > ifp = TAILQ_HEAD((struct > netbase_statics*)(p->vimage[netbase_index])->ifhead); > > Where netbase_index is a global set when the networking base module > is loaded or linked in, (no idea by who), and the 'vimage' becomes an > array of void * pointers, each pointing to a different structure aof > variables that were once static, each structure being variables > related to a different module. > > > This could be done but it starts to look a lot like the TLS (Thread > Local Storage) stuff. > And it would pretty definitly have a performance impact. > From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 12:59:09 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 5BD4916A4CE for ; Tue, 2 Mar 2004 12:59:09 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F10A43D45 for ; Tue, 2 Mar 2004 12:59:08 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 94140 invoked from network); 2 Mar 2004 20:59:07 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 20:59:07 -0000 Message-ID: <4044F59A.E1049B4D@freebsd.org> Date: Tue, 02 Mar 2004 21:59:06 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Bruce M Simpson References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302155844.GP4561@saboteur.dek.spc.org> <20040302171449.GF6234@saboteur.dek.spc.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: Brad Knowles cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 20:59:09 -0000 Bruce M Simpson wrote: > > I'm open to bringing it on board as a port, but I don't feel that carrying > a BGP daemon around in the base system is in the best interests of the > Project or our user base. I share that opinion. A bgpd doesn't have any business in the base tree. > > The last time I looked at his code it looked pretty much like a straight > > lift from the MRTD tree. This was a few months ago... and this was brief... > > Let me just qualify this statement - I have not had the chance to have > anything more than a cursory glance at this code, this was a 'prima facie' > impression when I was heavily involved with other work. Not to disrespect > anyone else's hard work, as some people mistakenly seem to be under this > impression. As one of the guys involved in OpenBSDs new bgpd I can assure you that there is no code lifted from mrtd whatsoever. Henning started with the session handler part and then Claudio and I got involved for the bgp routing table part (RDE, route decision engine). I then delivered the original internal design of the RDE and how to store the bgp path and nexthop information in an optimal way for the common bgp transactions. Which essentially means that all structures are attached together in many linked lists. All the coding is being done by Henning and Claudio. -- Andre From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 13:08: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 E8F2616A4CF for ; Tue, 2 Mar 2004 13:08:57 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C18943D2D for ; Tue, 2 Mar 2004 13:08:57 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 94877 invoked from network); 2 Mar 2004 21:08:56 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 21:08:56 -0000 Message-ID: <4044F7E7.EB1CC703@freebsd.org> Date: Tue, 02 Mar 2004 22:08:55 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "Bjoern A. Zeeb" References: <4043B6BA.B847F081@freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 21:08:58 -0000 "Bjoern A. Zeeb" wrote: > > On Mon, 1 Mar 2004, Andre Oppermann wrote: > > Hi, > > > I put this up for coordination and cooperation in my planned work on the > > FreeBSD networking system. This is my todo list of things I want to do > > from now through summer 04. If you are or intend to work on one of these > > please step forward so we can coordinate. :-) > ... > > [] other stuff that I happen to stumble over... ;-) > > I still have in mind that I would like to see vimage[1] in HEAD one day > ... I think it would be a pretty cool feature to have. If one can keep > this in mind when doing greater modelling on the network stack it > might help the one who will - at some time - find the time to > ingtegrate it. I have seen your work and it is very interesting from a research point of view. For a normal kernel I don't see any benefit to it. Often jails are pointed out for it but I don't think this really makes sense. If you go as far as giving each jail it's own network stack including routing (what for in a jail?) then you can make the full leap and do something like userland BSD akin the userland Linux. Then each jail gets it's own fully virtualized machine. Makes more sense to me than just giving them a network stack on their own. Don't get me wrong, it's very cool but the net benefit and usefulness in realworld situations is pretty small. -- Andre From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 13:13:07 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 9A14516A4CF for ; Tue, 2 Mar 2004 13:13:07 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id D02EF43D39 for ; Tue, 2 Mar 2004 13:13:06 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 95135 invoked from network); 2 Mar 2004 21:13:06 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 21:13:06 -0000 Message-ID: <4044F8E1.F10CFD37@freebsd.org> Date: Tue, 02 Mar 2004 22:13:05 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: James Read References: <4043B6BA.B847F081@freebsd.org> <00d301c40089$8a035410$c000000a@jd2400> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: "Bjoern A. Zeeb" cc: freebsd-current@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack (vimage) 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, 02 Mar 2004 21:13:07 -0000 James Read wrote: > > > I still have in mind that I would like to see vimage[1] in HEAD one day > > ... I think it would be a pretty cool feature to have. If one can keep > > this in mind when doing greater modelling on the network stack it > > might help the one who will - at some time - find the time to > > ingtegrate it. > > > > > > [1] http://www.tel.fer.hr/zec/BSD/vimage/index.html > > > > > > In my opinion, this would be a _VERY_ good 'feature' to add into the system. > As it stands there is minimal 'networking' in a jail from a users point of > view, and also an administrators view aswell (granted this isnt exactly what > jail was designed to do, and so on). This could be more then an asset to the > whole jail architecture, by providing a clone-able network stack within > jails. For instance, you could then run programs/services like NFS etc from > jail to jail without having to lock down services offered from the jail > 'host'. Having a per-jail NFS is not dependend on a dedicated network stack but other things. NFS only uses the network for transport, there is on need to have it separated. > If this can in _any way_ be pushed/implemented (with minimal distruption) so > that is it in HEAD/CURRENT then its well on the way to complementing what > 'jail' does. The patch set is pretty extensive and intrusive and only for 4.x. Adding locking for 5.x would be a pretty nice challenge as well and not easy to get right for all cases. > This is one thing that I would like to use, without patching systems. But > then thats just my 'wish list' opinion of it. I think is makes more sense to get something like userland BSD. -- Andre From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 13:19: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 8433B16A4CE for ; Tue, 2 Mar 2004 13:19:22 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3C0E43D3F for ; Tue, 2 Mar 2004 13:19:21 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 95596 invoked from network); 2 Mar 2004 21:19:20 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Mar 2004 21:19:20 -0000 Message-ID: <4044FA58.87832F22@freebsd.org> Date: Tue, 02 Mar 2004 22:19:20 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Bruce M Simpson References: <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> <20040302085556.GA23734@cell.sick.ru> <20040302092825.GD884@saboteur.dek.spc.org> <20040302095134.GA24078@cell.sick.ru> <40449B8E.A48B39B0@freebsd.org> <20040302160902.GB26977@cell.sick.ru> <20040302193258.GD7115@saboteur.dek.spc.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: freebsd-net@freebsd.org cc: Kris Kennaway Subject: Re: My planned work on networking stack 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, 02 Mar 2004 21:19:22 -0000 Bruce M Simpson wrote: > > On Tue, Mar 02, 2004 at 07:09:02PM +0300, Gleb Smirnoff wrote: > > I do not insist that AS pathes in kernel are good idea. If you show me an > > other way to get AS information when constructing netflow exports in kernel, > > I'd be thankful. I'd be also thankful if you describe how policy routing can be > > implemented while no AS info in kernel. > > What do other FreeBSD networking withards think? > > I don't see any reason why we couldn't accept, for example, a 32-bit cookie > for abuse by a userland daemon, with pid, as it pleases (via an rtmsg > extension and PF_ROUTE). That is generic enough to provide the tie-in > needed with the userland RIB and the kernel FIB. Ugh, I'm happily running my accounting in userland via BPF/PCAP and it adds only 2-3% CPU load. The BGP information I get from MRT routing table dumps. Pretty slick stuff. We (Claudio and me) are preparing it for public release later this week. >From my experience here and a performance point of view there is no need to do netflow and related accounting stuff in the kernel at all. Userland is much more flexible. > ABI breakage may occur, but I would consider that the PF_ROUTE code is in need > of an overhaul anyway (see my mail to ru@ from some months ago on -current or > -net with code able to panic a kernel through malformed rtmsg contents). Please don't break the current RTM5 API. We will design a nice and much more flexible RTM6 message format later this year. It needs a good deal of deep thought and not be rushed just for the sake of it. -- Andre From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 13:40: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 A787416A4CE; Tue, 2 Mar 2004 13:40:31 -0800 (PST) Received: from mx.nsu.ru (mx.nsu.ru [212.192.164.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51BA943D1D; Tue, 2 Mar 2004 13:40:31 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from iclub.nsu.ru ([193.124.215.97] ident=root) by mx.nsu.ru with esmtp (Exim 4.30) id 1AyHf5-0002Pv-56; Wed, 03 Mar 2004 03:42:47 +0600 Received: from iclub.nsu.ru (fjoe@localhost [127.0.0.1]) by iclub.nsu.ru (8.12.10/8.12.10) with ESMTP id i22LeQYw043091; Wed, 3 Mar 2004 03:40:26 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Received: (from fjoe@localhost) by iclub.nsu.ru (8.12.10/8.12.10/Submit) id i22LeMV9043090; Wed, 3 Mar 2004 03:40:22 +0600 (NS) (envelope-from fjoe) Date: Wed, 3 Mar 2004 03:40:22 +0600 From: Max Khon To: Andre Oppermann Message-ID: <20040302214022.GC42471@iclub.nsu.ru> References: <4043B6BA.B847F081@freebsd.org> <00d301c40089$8a035410$c000000a@jd2400> <4044F8E1.F10CFD37@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4044F8E1.F10CFD37@freebsd.org> User-Agent: Mutt/1.4.1i cc: "Bjoern A. Zeeb" cc: James Read cc: freebsd-current@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack (vimage) 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, 02 Mar 2004 21:40:31 -0000 Hello! On Tue, Mar 02, 2004 at 10:13:05PM +0100, Andre Oppermann wrote: > The patch set is pretty extensive and intrusive and only for 4.x. Adding > locking for 5.x would be a pretty nice challenge as well and not easy to > get right for all cases. > > > This is one thing that I would like to use, without patching systems. But > > then thats just my 'wish list' opinion of it. > > I think is makes more sense to get something like userland BSD. Userland BSD might need too many resources. Think of hosting providers who run hundreds or thousands of virtual hosts in a jail. Please take a look at commercial solutions like FreeVPS by H-Sphere or Virtuozzo by SWSoft. Virtualized network stack is not an academic-research only feature. /fjoe From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 13:47:02 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 4B92416A4CE; Tue, 2 Mar 2004 13:47:02 -0800 (PST) Received: from mx.nsu.ru (mx.nsu.ru [212.192.164.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC1C943D1D; Tue, 2 Mar 2004 13:47:01 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from iclub.nsu.ru ([193.124.215.97] ident=root) by mx.nsu.ru with esmtp (Exim 4.30) id 1AyHlP-00039J-27; Wed, 03 Mar 2004 03:49:19 +0600 Received: from iclub.nsu.ru (fjoe@localhost [127.0.0.1]) by iclub.nsu.ru (8.12.10/8.12.10) with ESMTP id i22LkxYw043226; Wed, 3 Mar 2004 03:46:59 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Received: (from fjoe@localhost) by iclub.nsu.ru (8.12.10/8.12.10/Submit) id i22LkwSh043225; Wed, 3 Mar 2004 03:46:58 +0600 (NS) (envelope-from fjoe) Date: Wed, 3 Mar 2004 03:46:58 +0600 From: Max Khon To: Andre Oppermann Message-ID: <20040302214658.GD42471@iclub.nsu.ru> References: <4043B6BA.B847F081@freebsd.org> <00d301c40089$8a035410$c000000a@jd2400> <4044F8E1.F10CFD37@freebsd.org> <20040302214022.GC42471@iclub.nsu.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040302214022.GC42471@iclub.nsu.ru> User-Agent: Mutt/1.4.1i cc: "Bjoern A. Zeeb" cc: James Read cc: freebsd-current@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack (vimage) 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, 02 Mar 2004 21:47:02 -0000 Hello! On Wed, Mar 03, 2004 at 03:40:22AM +0600, Max Khon wrote: > > The patch set is pretty extensive and intrusive and only for 4.x. Adding > > locking for 5.x would be a pretty nice challenge as well and not easy to > > get right for all cases. > > > > > This is one thing that I would like to use, without patching systems. But > > > then thats just my 'wish list' opinion of it. > > > > I think is makes more sense to get something like userland BSD. > > Userland BSD might need too many resources. > Think of hosting providers who run hundreds or thousands of virtual hosts > in a jail. Please take a look at commercial solutions like FreeVPS by H-Sphere > or Virtuozzo by SWSoft. I might add that having userland BSD is very useful feature. But from my experience with UML (User Mode Linux) I can say that it hardly can be useful for anything except development (kernel debugging, userland development for different kernel version etc.). /fjoe From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 14:13: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 9DF3116A4CE; Tue, 2 Mar 2004 14:13:49 -0800 (PST) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39AC143D39; Tue, 2 Mar 2004 14:13:49 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (rwcrmhc12) with ESMTP id <2004030222134801400egd0ie>; Tue, 2 Mar 2004 22:13:48 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA79039; Tue, 2 Mar 2004 14:13:45 -0800 (PST) Date: Tue, 2 Mar 2004 14:13:44 -0800 (PST) From: Julian Elischer To: Marko Zec In-Reply-To: <200403022148.38002.zec@tel.fer.hr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "Bjoern A. Zeeb" cc: James Read cc: freebsd-current@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: Was: My planned work on networking stack (vimage) 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, 02 Mar 2004 22:13:49 -0000 On Tue, 2 Mar 2004, Marko Zec wrote: > On Tuesday 02 March 2004 21:01, Julian Elischer wrote: > > The major problem with 'vimage' is that all statics are moved to a > > large structure so that they can be duplicated... > > e.g. The root of the interface list gets moved there so that each > > vimage has its own list of interfaces. > > > > > > This is ok for statically compiled modules, but what can you do for > > adding new modules.. either statically of dynamically.. > > > > You end up having to have each module have it's own structure and > > each vimage has to have its own list or array of such structures.. > > > > Hi, Julian! > > True, this can also become an issue. However, the question is how many > modules in real-life do require per network stack symbols/structures. > For example, the original vimage patch already included the necessary > hooks and reserved the appropriate fields for ipfw or dummynet to be > loaded / unloaded dynamically with no major problems. > > On the other hand, no device driver should be affected by the > virtualization, and shouldn't require any network-stack specific > handling. And IMO the device drivers are those which are most commonly > implemented as loadable modules. > The trick is that you need to be able to arbitrarily add a protocol, or a firewall stack or other modules. As I said it can be done. What is a problem is that 'static' form of the current vimage structure.. Even struct { #ifdef NETINET ..inet variables #endif #ifdef NETATALK .. appletalk variables #endif [etc.] } vimage; is not tennable because you cannot keep adding parts to the structure.. The whole aim of FreeBSD over the last 10 years has been to move towards modularity, in almost all areas. If you could add modules and have them add themselves to existing (or even only new) vimages, then it could be viable in FreeBSD. > Cheers, > > Marko > > > > > so to use the example above, > > ifp = TAILQ_HEAD(ifhead) /* I forget the exact names */ > > > > becomes something like: > > > > ifp = TAILQ_HEAD((struct > > netbase_statics*)(p->vimage[netbase_index])->ifhead); > > > > Where netbase_index is a global set when the networking base module > > is loaded or linked in, (no idea by who), and the 'vimage' becomes an > > array of void * pointers, each pointing to a different structure aof > > variables that were once static, each structure being variables > > related to a different module. > > > > > > This could be done but it starts to look a lot like the TLS (Thread > > Local Storage) stuff. > > And it would pretty definitly have a performance impact. > > > > From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 14:16: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 56D0E16A4CE; Tue, 2 Mar 2004 14:16:19 -0800 (PST) Received: from ran.psg.com (ip166.usw253.dsl-acs2.sea.iinet.com [209.20.253.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24D4743D31; Tue, 2 Mar 2004 14:16:19 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.30; FreeBSD) id 1AyIBS-0001Pw-6N; Tue, 02 Mar 2004 14:16:14 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 2 Mar 2004 14:16:13 -0800 To: Gleb Smirnoff References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> <20040302085556.GA23734@cell.sick.ru> <20040302092825.GD884@saboteur.dek.spc.org> <20040302095134.GA24078@cell.sick.ru> <40449B8E.A48B39B0@freebsd.org> <20040302160902.GB26977@cell.sick.ru> Message-Id: <20040302221619.24D4743D31@mx1.FreeBSD.org> cc: Kris Kennaway cc: freebsd-current@freebsd.org cc: Andre Oppermann cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 22:16:19 -0000 > I do not insist that AS pathes in kernel are good idea. If you > show me an other way to get AS information when constructing > netflow exports in kernel, I'd be thankful. do we need to rediscover why flow export places a large processor burden on criscos, junipers, prockets, ...? randy From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 14:24: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 731C916A4CF; Tue, 2 Mar 2004 14:24:11 -0800 (PST) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9596943D31; Tue, 2 Mar 2004 14:24:10 -0800 (PST) (envelope-from glebius@cell.sick.ru) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.9/8.12.8) with ESMTP id i22MO7QE029458 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Mar 2004 01:24:08 +0300 (MSK) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.9/8.12.6/Submit) id i22MO6sT029457; Wed, 3 Mar 2004 01:24:06 +0300 (MSK) Date: Wed, 3 Mar 2004 01:24:06 +0300 From: Gleb Smirnoff To: Randy Bush Message-ID: <20040302222406.GA29412@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Randy Bush , Andre Oppermann , Wes Peters , freebsd-net@freebsd.org, freebsd-current@freebsd.org, Kris Kennaway References: <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> <20040302085556.GA23734@cell.sick.ru> <20040302092825.GD884@saboteur.dek.spc.org> <20040302095134.GA24078@cell.sick.ru> <40449B8E.A48B39B0@freebsd.org> <20040302160902.GB26977@cell.sick.ru> <200403022216.i22MGVQE029400@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <200403022216.i22MGVQE029400@cell.sick.ru> User-Agent: Mutt/1.5.6i cc: Kris Kennaway cc: freebsd-current@freebsd.org cc: Andre Oppermann cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 02 Mar 2004 22:24:11 -0000 On Tue, Mar 02, 2004 at 02:16:13PM -0800, Randy Bush wrote: R> > I do not insist that AS pathes in kernel are good idea. If you R> > show me an other way to get AS information when constructing R> > netflow exports in kernel, I'd be thankful. R> R> do we need to rediscover why flow export places a large processor R> burden on criscos, junipers, prockets, ...? Not because of AS path info, definitely. Netflow does route lookup anyway to get nexthop and route masks. If route lookup will return a pointer to a structure with one more field it will not introduce ant additional load. My experience shows, that most load in flow processing is caused by: 1) memory allocation, 2) expiry lookups. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 19:37: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 9F61116A4CE; Tue, 2 Mar 2004 19:37:50 -0800 (PST) Received: from axe-inc.co.jp (axegw.axe-inc.co.jp [61.199.217.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1789943D2D; Tue, 2 Mar 2004 19:37:49 -0800 (PST) (envelope-from takawata@axe-inc.co.jp) Received: from localhost (localhost [127.0.0.1]) by axe-inc.co.jp (8.9.3+3.2W/3.7W) with SMTP id MAA24341; Wed, 3 Mar 2004 12:36:56 +0900 (JST) Message-Id: <200403030336.MAA24341@axe-inc.co.jp> X-Authentication-Warning: axegw.axe-inc.co.jp: localhost [127.0.0.1] didn't use HELO protocol To: Julian Elischer , zec@tel.fer.hr In-reply-to: Your message of "Tue, 02 Mar 2004 14:13:44 PST." Date: Wed, 03 Mar 2004 12:36:56 +0900 From: Takanori Watanabe cc: bzeeb-lists@lists.zabbadoz.net cc: james@physicalsegment.com cc: freebsd-current@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: Was: My planned work on networking stack (vimage) 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, 03 Mar 2004 03:37:50 -0000 In message , Ju lian Elischer wrote: >On Tue, 2 Mar 2004, Marko Zec wrote: > >> On Tuesday 02 March 2004 21:01, Julian Elischer wrote: >> > The major problem with 'vimage' is that all statics are moved to a >> > large structure so that they can be duplicated... >> > e.g. The root of the interface list gets moved there so that each >> > vimage has its own list of interfaces. >> > >> > >> > This is ok for statically compiled modules, but what can you do for >> > adding new modules.. either statically of dynamically.. >> > >> > You end up having to have each module have it's own structure and >> > each vimage has to have its own list or array of such structures.. >> > >> >> Hi, Julian! >> >> True, this can also become an issue. However, the question is how many >> modules in real-life do require per network stack symbols/structures. >> For example, the original vimage patch already included the necessary >> hooks and reserved the appropriate fields for ipfw or dummynet to be >> loaded / unloaded dynamically with no major problems. >> >> On the other hand, no device driver should be affected by the >> virtualization, and shouldn't require any network-stack specific >> handling. And IMO the device drivers are those which are most commonly >> implemented as loadable modules. >> > >The trick is that you need to be able to arbitrarily add a protocol, >or a firewall stack or other modules. As I said it can be done. >What is a problem is that 'static' form of the current vimage >structure.. > >Even > >struct { >#ifdef NETINET > ..inet variables >#endif >#ifdef NETATALK > .. appletalk variables >#endif >[etc.] >} vimage; >is not tennable because you cannot keep adding parts to the structure.. >The whole aim of FreeBSD over the last 10 years has been to move towards >modularity, in almost all areas. Generally #ifdef's are obstacles for making it moduler. >If you could add modules and have them add themselves to existing >(or even only new) vimages, then it could be viable in FreeBSD. But networking stack itself now contains *many* #ifdef's, so we cannot add ethernet protocol by kld, for example NETATALK now. It may be done by all protocols layers are connected by netgraph(4). Static structure definition are certainly obstackles for making moduler, but gathering protocol stack private values into a structure will on the contrally help for it, by figuring out which data should we duplicate . From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 20:43:07 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 AE8DF16A4CE for ; Tue, 2 Mar 2004 20:43:07 -0800 (PST) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BCE543D1F for ; Tue, 2 Mar 2004 20:43:07 -0800 (PST) (envelope-from mwade@bluehighway.net) Received: from net-ninja.dyndns.org ([68.59.250.193]) by comcast.net (rwcrmhc12) with ESMTP id <20040303044307014003gm8he>; Wed, 3 Mar 2004 04:43:07 +0000 Received: from net-ninja.dyndns.org (net-ninja.dyndns.org [192.168.1.10]) by net-ninja.dyndns.org (Postfix) with ESMTP id 50F8E177 for ; Tue, 2 Mar 2004 23:43:06 -0500 (EST) Date: Tue, 2 Mar 2004 23:43:06 -0500 (EST) From: Mike Wade X-X-Sender: mwade@net-ninja.dyndns.org To: freebsd-net@freebsd.org In-Reply-To: <20040228223944.G93302@net-ninja.dyndns.org> Message-ID: <20040302234143.D99665@net-ninja.dyndns.org> References: <20040226171125.Q15617@net-ninja.dyndns.org> <20040228223944.G93302@net-ninja.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [RESOLVED] Re: Persistant random receiving packet drops with wi(4) and IBSS 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, 03 Mar 2004 04:43:07 -0000 On Sat, 28 Feb 2004, Mike Wade wrote: > On Thu, 26 Feb 2004, Mike Wade wrote: > > > Greetings, > > > > I'm experiencing a rather perplexing problem with 2 wireless nodes running > > FreeBSD 4.9-STABLE utilizing the wi(4) driver in IBSS mode. Periodically > > I'm unable to receive packets (transmitting packets is fine) but I'm able > > to see the incoming packets via tcpdump running in promisc mode only. I'm > > not able to see the incoming packets when it's not in promisc mode. > > I've discovered some new facts... If both nodes are in promisc mode then > the receiving packet drops go away. However, several input errors show up > via netstat and the performance drops from 4.0 mbit/sec to 0.16 mbit/sec. > Pretty bizarre stuff... Upgrading to: wi0: Intersil Firmware: Primary 1.01.00, Station 1.08.00 Appears to have fixed the IBSS and promiscuous mode issues I was experiencing before. --- Mike Wade (mwade@bluehighway.net) Blue Highway Labs, LLC. From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 21:08:07 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 2F67116A4CE for ; Tue, 2 Mar 2004 21:08:07 -0800 (PST) Received: from mars.webnext.com (mars.webnext.com [213.161.193.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB54E43D1F for ; Tue, 2 Mar 2004 21:08:06 -0800 (PST) (envelope-from apignard@frontier.fr) Received: from alfarn-153ede4f.frontier.fr (alfortville-6-82-66-251-138.fbx.proxad.net [82.66.251.138]) by mars.webnext.com (Postfix) with ESMTP id CB16B9BE22 for ; Wed, 3 Mar 2004 06:07:09 +0100 (CET) Message-Id: <6.0.3.0.2.20040303054929.06bc9988@213.161.193.184> X-Sender: arnaud@213.161.193.184 X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0 Date: Wed, 03 Mar 2004 06:09:29 +0100 To: freebsd-net@freebsd.org From: Arnaud Pignard In-Reply-To: References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302125935.GA25835@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Subject: Re: My planned work on networking stack 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, 03 Mar 2004 05:08:07 -0000 At 14:24 02/03/2004, Brad Knowles wrote: >At 3:59 PM +0300 2004/03/02, Gleb Smirnoff wrote: > >> Haven't you understand? I'm the "person who has real-world experience >> in running zebra in ISP environments with multiple upstreams and taking >> full views". > > Do you have multiple connectivity to two separate metro area=20 > exchanges, with multiple upstreams at each? Most large cities are lucky= =20 > to have a single major metro area exchange, and the author of bgpd for=20 > OpenBSD works at an ISP located in Hamburg which is lucky enough to have= =20 > two major NAPs, and he has multiple connectivity to both. He was the one= =20 > ragging on zebra/quagga. Among other things, he said he had real=20 > problems keeping sessions up with zebra/quagga when neighbors were= flapping. I know some small/medium ISP in France how are 100% zebra (or quagga) with= =20 at least 2 full net table with at least 130000 pfx When said small they have at least an average of 10-20 Mbps. As far as i=20 know one is 100% zebra more than 100 Mbps and seems stable. On our side, we have a Zebra with receving 2 full table & +130 peers as a=20 backup router without any trouble now (we have 3 cisco & 1 zebra) 0.92 & 0.93 was unstable. BGPD crash many times on peer routing table or=20 full net table. since 0.93b uptime wasn't broken Our zebra router already handle more than 60 Mbps without problem and so=20 few cpu use that's my cisco router was jalious ;) Currently i make so use for peering with ~40 Mbps since some months and i'm= =20 very happy with it. the design of zebra won't be interrested for have fast & evolutive solution= =20 regarding juniper or cisco 7x00 (except 7100 how is soo slow ;) Regarding 1ghz pc vs cisco 7x00 ... bpg & routing use less cpu on pc...=20 filter and such thing are much faster (7206vxr for example when i done some= =20 test) However where zebra bgp daemon is so crap and so slow is when flapping or=20 when clearing big session. But it's a design problem no ? I would like find very usefull to have bgpd integrate into base system. But= =20 maybe i'm not very objective since i work all the day with AS/Routing. Regarding interfaces that's PC router can deliver, All major carrier deliver FastEthernet / GigaEthernet or 10 Gig... OCx or Ex or Tx are mostly dead in Europe for deliver any ISP. Except=20 Global Crossing how was the last in France, *all* major carrier deliver=20 FastEthernet or GIG. All gix are in E/FE/GE (lynx / ams-ix / fr : parix / freeix / sfinx etc...) Regards, --=20 Arnaud Pignard (apignard@frontier.fr) Frontier Online - Op=E9rateur Internet From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 21:29: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 E8E6E16A4CE for ; Tue, 2 Mar 2004 21:29:37 -0800 (PST) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C7BF43D31 for ; Tue, 2 Mar 2004 21:29:36 -0800 (PST) (envelope-from eugen@kuzbass.ru) Received: from kuzbass.ru (kost [213.184.65.82])i235TXrx090880 for ; Wed, 3 Mar 2004 12:29:33 +0700 (KRAT) (envelope-from eugen@kuzbass.ru) Message-ID: <40456D3C.773A3C29@kuzbass.ru> Date: Wed, 03 Mar 2004 12:29:32 +0700 From: Eugene Grosbein Organization: SVZServ X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: ru,en MIME-Version: 1.0 To: net@freebsd.org Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Subject: Frozen connections 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, 03 Mar 2004 05:29:38 -0000 H! I'm experiencing strange problems with HTTP connections between two machines connected using 100Mbit ethernet switch. Client is Windows 2000 SP4 (named kost), server is FreeBSD 4.9/Apache 1.3.27 (named www). Plain HTTP GET request starts the thansfer and it freezes often and reproducably. I've traced this at the server side using tcpdump -n -p -lenx -s 1518 host kost and tcp port 80 | tcpshow -cooked [skip] Packet 84 TIME: 12:06:40.902236 (4.996904) LINK: 00:90:27:AB:08:88 -> 00:90:27:35:05:1B type=IP IP: www -> kost hlen=20 TOS=00 dgramlen=1335 id=608D MF/DF=0/1 frag=0 TTL=64 proto=TCP cksum=A720 TCP: port http -> 2136 seq=0249739568 ack=1566419520 hlen=20 (data=1295) UAPRSF=010000 wnd=58400 cksum=AB01 urg=0 DATA: mic content such as CGI output, SSI pages, and server-generated directory listings will generally not use Keep-Alive connections to HTTP/1.0 cli ents. For HTTP/1.1 clients, persistent connections are the def ault unless otherwise specified. If the client requests it, c hunked encoding will be used in order to send content of unknow n length over persistent connections.

Apache 1.1 only: Set max-request s to the maximum number of requests you want Apache to ent ertain per connection. A limit is imposed to prevent a client f rom hogging your server resources. Set this to 0 to disable support. In Apache 1.2 and 1.3, this is controll ed through the MaxKeepAliveRequests directive instead.

See also MaxKeepAliveRequests.

KeepAliveTimeout directive Syntax: KeepAliveTimeout seconds
Default: KeepAlive Timeout 15
00:90:27:AB:08:88 type=IP IP: kost -> www hlen=20 TOS=00 dgramlen=40 id=10B8 MF/DF=0/1 frag=0 TTL=128 proto=TCP cksum=BC04 TCP: port 2136 -> http seq=1566419520 ack=0249740863 hlen=20 (data=0) UAPRSF=010000 wnd=0 cksum=A459 urg=0 DATA: --------------------------------------------------------------------------- Packet 86 TIME: 12:06:46.000344 (4.988673) LINK: 00:90:27:AB:08:88 -> 00:90:27:35:05:1B type=IP IP: www -> kost hlen=20 TOS=00 dgramlen=41 id=85FD MF/DF=0/1 frag=0 TTL=64 proto=TCP cksum=86BE TCP: port http -> 2136 seq=0249740863 ack=1566419520 hlen=20 (data=1) UAPRSF=010000 wnd=58400 cksum=4C37 urg=0 DATA: t --------------------------------------------------------------------------- Packet 87 TIME: 12:06:46.000689 (0.000345) LINK: 00:90:27:35:05:1B -> 00:90:27:AB:08:88 type=IP IP: kost -> www hlen=20 TOS=00 dgramlen=40 id=10D3 MF/DF=0/1 frag=0 TTL=128 proto=TCP cksum=BBE9 TCP: port 2136 -> http seq=1566419520 ack=0249740863 hlen=20 (data=0) UAPRSF=010000 wnd=0 cksum=A459 urg=0 DATA: --------------------------------------------------------------------------- Packet 88 TIME: 12:06:50.998475 (4.997786) LINK: 00:90:27:AB:08:88 -> 00:90:27:35:05:1B type=IP IP: www -> kost hlen=20 TOS=00 dgramlen=41 id=6A94 MF/DF=0/1 frag=0 TTL=64 proto=TCP cksum=A227 TCP: port http -> 2136 seq=0249740863 ack=1566419520 hlen=20 (data=1) UAPRSF=010000 wnd=58400 cksum=4C37 urg=0 DATA: t --------------------------------------------------------------------------- Packet 89 TIME: 12:06:50.998828 (0.000353) LINK: 00:90:27:35:05:1B -> 00:90:27:AB:08:88 type=IP IP: kost -> www hlen=20 TOS=00 dgramlen=40 id=10E5 MF/DF=0/1 frag=0 TTL=128 proto=TCP cksum=BBD7 TCP: port 2136 -> http seq=1566419520 ack=0249740863 hlen=20 (data=0) UAPRSF=010000 wnd=0 cksum=A459 urg=0 DATA: --------------------------------------------------------------------------- Packet 90 TIME: 12:06:51.278337 (0.279509) LINK: 00:90:27:AB:08:88 -> 00:90:27:35:05:1B type=IP IP: www -> kost hlen=20 TOS=00 dgramlen=41 id=64CE MF/DF=0/1 frag=0 TTL=64 proto=TCP cksum=A7ED TCP: port http -> 2134 seq=1179931920 ack=1524903532 hlen=20 (data=1) UAPRSF=010000 wnd=58400 cksum=FC43 urg=0 DATA: t --------------------------------------------------------------------------- Packet 91 TIME: 12:06:51.278615 (0.000278) LINK: 00:90:27:35:05:1B -> 00:90:27:AB:08:88 type=IP IP: kost -> www hlen=20 TOS=00 dgramlen=40 id=10E6 MF/DF=0/1 frag=0 TTL=128 proto=TCP cksum=BBD6 TCP: port 2134 -> http seq=1524903532 ack=1179931920 hlen=20 (data=0) UAPRSF=010000 wnd=0 cksum=5466 urg=0 DATA: As you see, last pair of packets repeats many times and transfer is stalled here. What's wrong and who is guilty? Eugene Grosbein From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 21:47: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 C2B0D16A4CF for ; Tue, 2 Mar 2004 21:47:11 -0800 (PST) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CD8943D1F for ; Tue, 2 Mar 2004 21:47:11 -0800 (PST) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i235l37E000190; Tue, 2 Mar 2004 21:47:07 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200403030547.i235l37E000190@gw.catspoiler.org> Date: Tue, 2 Mar 2004 21:47:03 -0800 (PST) From: Don Lewis To: eugen@kuzbass.ru In-Reply-To: <40456D3C.773A3C29@kuzbass.ru> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: net@FreeBSD.org Subject: Re: Frozen connections 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, 03 Mar 2004 05:47:11 -0000 On 3 Mar, Eugene Grosbein wrote: > H! > > I'm experiencing strange problems with HTTP connections between > two machines connected using 100Mbit ethernet switch. > Client is Windows 2000 SP4 (named kost), > server is FreeBSD 4.9/Apache 1.3.27 (named www). > --------------------------------------------------------------------------- > Packet 90 > TIME: 12:06:51.278337 (0.279509) > LINK: 00:90:27:AB:08:88 -> 00:90:27:35:05:1B type=IP > IP: www -> kost hlen=20 TOS=00 dgramlen=41 id=64CE > MF/DF=0/1 frag=0 TTL=64 proto=TCP cksum=A7ED > TCP: port http -> 2134 seq=1179931920 ack=1524903532 > hlen=20 (data=1) UAPRSF=010000 wnd=58400 cksum=FC43 urg=0 > DATA: t > --------------------------------------------------------------------------- > Packet 91 > TIME: 12:06:51.278615 (0.000278) > LINK: 00:90:27:35:05:1B -> 00:90:27:AB:08:88 type=IP > IP: kost -> www hlen=20 TOS=00 dgramlen=40 id=10E6 > MF/DF=0/1 frag=0 TTL=128 proto=TCP cksum=BBD6 > TCP: port 2134 -> http seq=1524903532 ack=1179931920 > hlen=20 (data=0) UAPRSF=010000 wnd=0 cksum=5466 urg=0 > DATA: > > As you see, last pair of packets repeats many times > and transfer is stalled here. What's wrong and who is guilty? It looks like the client is the guilty party. The server is sending 1-byte long window probes, and the client is responding with an ACK packet that is advertising a receive window of 0. I'd be suspicious of the application software on the client. Can you try a different web browser, or even fetch the same URL using something like telnet? From owner-freebsd-net@FreeBSD.ORG Tue Mar 2 22:13:20 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 3794616A4CE; Tue, 2 Mar 2004 22:13:20 -0800 (PST) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4146943D2D; Tue, 2 Mar 2004 22:13:19 -0800 (PST) (envelope-from eugen@kuzbass.ru) Received: from kuzbass.ru (kost [213.184.65.82])i236DHrx017294; Wed, 3 Mar 2004 13:13:17 +0700 (KRAT) (envelope-from eugen@kuzbass.ru) Message-ID: <4045777D.41DBBA94@kuzbass.ru> Date: Wed, 03 Mar 2004 13:13:17 +0700 From: Eugene Grosbein Organization: SVZServ X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: ru,en MIME-Version: 1.0 To: Don Lewis References: <200403030547.i235l37E000190@gw.catspoiler.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit cc: net@FreeBSD.org Subject: Re: Frozen connections 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, 03 Mar 2004 06:13:20 -0000 Don Lewis wrote: > > --------------------------------------------------------------------------- > > Packet 90 > > TIME: 12:06:51.278337 (0.279509) > > LINK: 00:90:27:AB:08:88 -> 00:90:27:35:05:1B type=IP > > IP: www -> kost hlen=20 TOS=00 dgramlen=41 id=64CE > > MF/DF=0/1 frag=0 TTL=64 proto=TCP cksum=A7ED > > TCP: port http -> 2134 seq=1179931920 ack=1524903532 > > hlen=20 (data=1) UAPRSF=010000 wnd=58400 cksum=FC43 urg=0 > > DATA: t > > --------------------------------------------------------------------------- > > Packet 91 > > TIME: 12:06:51.278615 (0.000278) > > LINK: 00:90:27:35:05:1B -> 00:90:27:AB:08:88 type=IP > > IP: kost -> www hlen=20 TOS=00 dgramlen=40 id=10E6 > > MF/DF=0/1 frag=0 TTL=128 proto=TCP cksum=BBD6 > > TCP: port 2134 -> http seq=1524903532 ack=1179931920 > > hlen=20 (data=0) UAPRSF=010000 wnd=0 cksum=5466 urg=0 > > DATA: > > > > As you see, last pair of packets repeats many times > > and transfer is stalled here. What's wrong and who is guilty? > > It looks like the client is the guilty party. The server is sending > 1-byte long window probes, and the client is responding with an ACK > packet that is advertising a receive window of 0. > > I'd be suspicious of the application software on the client. Can you > try a different web browser, or even fetch the same URL using something > like telnet? I've tried using Netscape Communicator 4.8 and MSIE 6.0 The picture is the same. Eugene Grosbein From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 00:19: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 51F2416A4CE; Wed, 3 Mar 2004 00:19:17 -0800 (PST) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id C53BC43D2F; Wed, 3 Mar 2004 00:19:16 -0800 (PST) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.30; FreeBSD) id 1AyRc1-0001uL-KB; Wed, 03 Mar 2004 11:20:17 +0300 From: Vladimir Grebenschikov To: Bruce M Simpson In-Reply-To: <20040302193258.GD7115@saboteur.dek.spc.org> References: <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> <20040302085556.GA23734@cell.sick.ru> <20040302092825.GD884@saboteur.dek.spc.org> <20040302095134.GA24078@cell.sick.ru> <40449B8E.A48B39B0@freebsd.org> <20040302160902.GB26977@cell.sick.ru> <20040302193258.GD7115@saboteur.dek.spc.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: quoted-printable Organization: TSB "Russian Express" Message-Id: <1078302016.6838.46.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.5.4FreeBSD GNOME Team Port Date: Wed, 03 Mar 2004 11:20:17 +0300 Sender: Vladimir Grebenschikov cc: Andre Oppermann cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: Kris Kennaway Subject: Re: My planned work on networking stack X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: vova@express.ru List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Mar 2004 08:19:17 -0000 On =D7=D4, 2004-03-02 at 19:32 +0000, Bruce M Simpson wrote: > On Tue, Mar 02, 2004 at 07:09:02PM +0300, Gleb Smirnoff wrote: > > I do not insist that AS pathes in kernel are good idea. If you show m= e an > > other way to get AS information when constructing netflow exports in ke= rnel, > > I'd be thankful. I'd be also thankful if you describe how policy routin= g can be > > implemented while no AS info in kernel. > > What do other FreeBSD networking withards think? >=20 > I don't see any reason why we couldn't accept, for example, a 32-bit cook= ie > for abuse by a userland daemon, with pid, as it pleases (via an rtmsg > extension and PF_ROUTE). That is generic enough to provide the tie-in > needed with the userland RIB and the kernel FIB. This possible solution when you run accounting, but if you are going to do policy-routing, you need to get routing decision based on additional route information, and in this case you need keep this additional data in kerenl. But I agree with you that rtentry is bad place for that information. > ABI breakage may occur, but I would consider that the PF_ROUTE code is in= need > of an overhaul anyway (see my mail to ru@ from some months ago on -curren= t or > -net with code able to panic a kernel through malformed rtmsg contents). We need ability to link rtentry records with custom kernel data handled by extension modules (such as cisco-like accounting or policy-routing) > BMS From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 03:47: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 00ADA16A4CE for ; Wed, 3 Mar 2004 03:47:42 -0800 (PST) Received: from bps.jodocus.org (g157016.upc-g.chello.nl [80.57.157.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0B3F43D1D for ; Wed, 3 Mar 2004 03:47:39 -0800 (PST) (envelope-from joost@jodocus.org) Received: from jodocus.org (localhost [127.0.0.1]) by bps.jodocus.org (8.12.10/8.12.10) with ESMTP id i23BlceF085559 for ; Wed, 3 Mar 2004 12:47:38 +0100 (CET) (envelope-from joost@jodocus.org) Received: (from joost@localhost) by jodocus.org (8.12.10/8.12.10/Submit) id i23Blc5j085558 for net@freebsd.org; Wed, 3 Mar 2004 12:47:38 +0100 (CET) (envelope-from joost) Date: Wed, 3 Mar 2004 12:47:38 +0100 From: Joost Bekkers To: net@freebsd.org Message-ID: <20040303114738.GA85522@bps.jodocus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: IPFW2 for IPv6 ?? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Mar 2004 11:47:42 -0000 Hello Are there any plans to make IPFW2 work for IPv6? Or can someone recommend a statefull firewall for IPv6? Thanks -- greetz Joost joost@jodocus.org From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 04:12:41 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 2705C16A4CE for ; Wed, 3 Mar 2004 04:12:41 -0800 (PST) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D72B43D3F for ; Wed, 3 Mar 2004 04:12:41 -0800 (PST) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.9p1/8.12.8) with ESMTP id i23CCe9Q011716; Wed, 3 Mar 2004 04:12:40 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.9p1/8.12.3/Submit) id i23CCeUv011715; Wed, 3 Mar 2004 04:12:40 -0800 (PST) (envelope-from rizzo) Date: Wed, 3 Mar 2004 04:12:39 -0800 From: Luigi Rizzo To: Joost Bekkers Message-ID: <20040303041239.A11330@xorpc.icir.org> References: <20040303114738.GA85522@bps.jodocus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20040303114738.GA85522@bps.jodocus.org>; from joost@jodocus.org on Wed, Mar 03, 2004 at 12:47:38PM +0100 cc: net@freebsd.org Subject: Re: IPFW2 for IPv6 ?? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Mar 2004 12:12:41 -0000 On Wed, Mar 03, 2004 at 12:47:38PM +0100, Joost Bekkers wrote: > Hello > > Are there any plans to make IPFW2 work for IPv6? i posted some experimental code to the -network (or was it -ipfw ?) list early in january, expect a cleaned up version in a couple of weeks. The patch was for -stable but should be relatively straightworward to apply to -current. cheers luigi > Or can someone recommend a statefull firewall for IPv6? > > Thanks > > -- > greetz Joost > joost@jodocus.org > _______________________________________________ > 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 Wed Mar 3 05:00: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 530F716A4CE for ; Wed, 3 Mar 2004 05:00:38 -0800 (PST) Received: from qhmail2.colt1.inetserver.de (qhmail2.colt1.inetserver.de [195.234.228.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 792FC43D3F for ; Wed, 3 Mar 2004 05:00:37 -0800 (PST) (envelope-from m.oe@x-trader.de) Received: from lupo.gn.qhintra.net (unknown [213.83.51.133]) by qhmail2.colt1.inetserver.de (Postfix) with ESMTP id 9A72CAB678 for ; Wed, 3 Mar 2004 14:00:35 +0100 (CET) Received: from ente (ente.gn.qhintra.net [192.168.192.2]) by lupo.gn.qhintra.net (Postfix) with ESMTP id F15C329F0B for ; Wed, 3 Mar 2004 14:00:34 +0100 (CET) From: "Markus Oestreicher" To: Date: Wed, 3 Mar 2004 14:00:32 +0100 Message-ID: <09be01c4011f$83228cb0$02c0a8c0@gnbuero.qhintra.net> 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.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Subject: freevrrpd (was: My planned work on networking stack) 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, 03 Mar 2004 13:00:38 -0000 > [...] > as for vrrp, there is an opensource/RFC-compliant implementation that > works on FreeBSD. actually, it was coded specifically for FreeBSD. > > http://freshmeat.net/projects/freebsd-hut > > i have never used this on a large-scale (i've never considered pre-1.0 > software "stable"), but have used it many places for failover inside > clusters with satisfactory results. A few months ago I read about problems when using freevrrpd on vlan(4) interfaces. I will going to implement a similar solution this year. Have these been fixed recently or is this impossible by design? Markus From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 05:14: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 B38D716A4CE for ; Wed, 3 Mar 2004 05:14:45 -0800 (PST) Received: from shellma.zin.lublin.pl (shellma.zin.lublin.pl [212.182.126.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A29643D45 for ; Wed, 3 Mar 2004 05:14:45 -0800 (PST) (envelope-from pawmal-posting@freebsd.lublin.pl) Received: by shellma.zin.lublin.pl (Postfix, from userid 1018) id 0DDA45F103; Wed, 3 Mar 2004 14:15:13 +0100 (CET) Date: Wed, 3 Mar 2004 14:15:12 +0100 From: Pawel Malachowski To: Markus Oestreicher Message-ID: <20040303131512.GC35449@shellma.zin.lublin.pl> References: <09be01c4011f$83228cb0$02c0a8c0@gnbuero.qhintra.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <09be01c4011f$83228cb0$02c0a8c0@gnbuero.qhintra.net> User-Agent: Mutt/1.4.2i cc: net@freebsd.org Subject: Re: freevrrpd (was: My planned work on networking stack) 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, 03 Mar 2004 13:14:45 -0000 On Wed, Mar 03, 2004 at 02:00:32PM +0100, Markus Oestreicher wrote: > > http://freshmeat.net/projects/freebsd-hut > > > > i have never used this on a large-scale (i've never considered pre-1.0 > > software "stable"), but have used it many places for failover inside > > clusters with satisfactory results. > > A few months ago I read about problems when using freevrrpd on Thread ,,FreeBSD 4.9 / VRRP / vlan''. > vlan(4) interfaces. I will going to implement a similar solution > this year. > > Have these been fixed recently or is this impossible by design? Probably vlan(4)'s fault. I have no idea if it was fixed. -- Pawe³ Ma³achowski From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 07:21: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 3A42E16A516 for ; Wed, 3 Mar 2004 07:21:42 -0800 (PST) Received: from plouf.absolight.net (plouf.absolight.net [212.43.217.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0124943D2F for ; Wed, 3 Mar 2004 07:21:42 -0800 (PST) (envelope-from mat@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by plouf.absolight.net (Postfix) with ESMTP id DE7516048A1; Wed, 3 Mar 2004 16:21:40 +0100 (CET) Received: from andromede.faubourg.reaumur.net (ATuileries-107-2-1-248.w217-128.abo.wanadoo.fr [217.128.120.248]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by plouf.absolight.net (Postfix) with ESMTP id 12031604888; Wed, 3 Mar 2004 16:21:40 +0100 (CET) Date: Wed, 03 Mar 2004 16:19:34 +0100 From: Mathieu Arnold To: Pawel Malachowski , Markus Oestreicher Message-ID: <1294253421.1078330774@andromede.faubourg.reaumur.net> In-Reply-To: <20040303131512.GC35449@shellma.zin.lublin.pl> References: <09be01c4011f$83228cb0$02c0a8c0@gnbuero.qhintra.net> <20040303131512.GC35449@shellma.zin.lublin.pl> X-Mailer: Mulberry/3.1.1 (Win32) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========C7829CBF97E0DF9D1468==========" X-Virus-Scanned: by amavisd 0.1 cc: net@freebsd.org Subject: Re: freevrrpd (was: My planned work on networking stack) 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, 03 Mar 2004 15:21:42 -0000 --==========C7829CBF97E0DF9D1468========== Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline +-le 03/03/2004 14:15 +0100, Pawel Malachowski a dit : | On Wed, Mar 03, 2004 at 02:00:32PM +0100, Markus Oestreicher wrote: | |> > http://freshmeat.net/projects/freebsd-hut |> > |> > i have never used this on a large-scale (i've never considered pre-1.0 |> > software "stable"), but have used it many places for failover inside |> > clusters with satisfactory results. |> |> A few months ago I read about problems when using freevrrpd on | | Thread ,,FreeBSD 4.9 / VRRP / vlan''. | |> vlan(4) interfaces. I will going to implement a similar solution |> this year. |> |> Have these been fixed recently or is this impossible by design? | | Probably vlan(4)'s fault. I have no idea if it was fixed. Our problem was/is with 5.2 box, and it's not fixed, but freevrrpd's author said he was looking into it. -- Mathieu Arnold --==========C7829CBF97E0DF9D1468========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) iQEVAwUBQEX3iFvROjYJ63c1AQKoDQf+Jhf6BfTwWnK4Vh6xJ4X29Obsrd2iikgE VNXf1g8LNI5dTjwDm0IApmj9kX7xwzepGINz+bmxfo+p0xPsH1MmbW/RFwsOn06a Z/r1vClkRWZYG3PLf8ZxHyfi7ylDCQk5gU4ZkZCfVN8Atg7UQbO+tHI0sBBiRTl5 q5hHNq3kodfqEsUo8JD/ESODjNuqZ7aDKrXGbR7r/qE/Ae6GYlahBKm1ZFgDAc9m /XcALqQ2P6lTAcl+HUNHxrRxrxN4fjxrPtivgXR/IoDA0N6Lg1BnIHtWWhq1ZTg5 JjwecjqTD2EZwXwiztJm39zOHNhuVGN3fbp642Uc0zzKypEhVhks7g== =edZW -----END PGP SIGNATURE----- --==========C7829CBF97E0DF9D1468==========-- From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 08:20: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 4815516A4CE for ; Wed, 3 Mar 2004 08:20:40 -0800 (PST) Received: from mail.joshuabranch.net (ip-66-80-53-4.dsl.lax.megapath.net [66.80.53.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C95543D41 for ; Wed, 3 Mar 2004 08:20:40 -0800 (PST) (envelope-from p500.2004@openstandards.net) Received: from openstandards.net (unknown [192.168.1.3]) by mail.joshuabranch.net (Postfix) with ESMTP id E8EB17E0016 for ; Wed, 3 Mar 2004 11:17:25 -0500 (EST) Message-ID: <404605DC.4030809@openstandards.net> Date: Wed, 03 Mar 2004 11:20:44 -0500 From: Erik Sliman User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5b) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Creating multiple IPs 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, 03 Mar 2004 16:20:40 -0000 How do you give a computer multiple static IPs? I've tried many things, including the ifaliases setting in rc.conf: ifconfig_vr0="inet 192.168.1.3 netmask 255.255.255.0" ifaliases_vr0="192.168.1.36 255.255.255.0" but none seem to work. From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 08:28: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 4EDF916A4CE for ; Wed, 3 Mar 2004 08:28:46 -0800 (PST) Received: from iota.root-servers.ch (iota.root-servers.ch [193.41.193.195]) by mx1.FreeBSD.org (Postfix) with SMTP id 3CEE043D2F for ; Wed, 3 Mar 2004 08:28:43 -0800 (PST) (envelope-from gabriel_ambuehl@buz.ch) Received: (qmail 20793 invoked from network); 3 Mar 2004 16:28:39 -0000 Received: from 217-162-135-163.dclient.hispeed.ch (HELO ga) (217.162.135.163) by 0 with SMTP; 3 Mar 2004 16:28:39 -0000 Date: Wed, 3 Mar 2004 17:31:11 +0100 From: Gabriel Ambuehl Organization: BUZ Internet Services X-Priority: 3 (Normal) Message-ID: <54297371.20040303173111@buz.ch> To: Erik Sliman In-Reply-To: <404604FC.1020506@openstandards.net> References: <404604FC.1020506@openstandards.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: Multiple static IPs X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: gabriel_ambuehl@buz.ch List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Mar 2004 16:28:46 -0000 Hello Erik, Wednesday, March 3, 2004, 5:17:00 PM, you wrote: > How do you give a computer multiple static IPs? > I've tried many things, including the ifaliases setting in rc.conf: > ifconfig_vr0="inet 192.168.1.3 netmask 255.255.255.0" > ifaliases_vr0="192.168.1.36 255.255.255.0" > but none seem to work. Wrong list but anyhow: ifconfig_vr0="inet someip netmask 255.255.255.224" ifconfig_vr0_alias0="inet someip+1 netmask 255.255.255.255" ifconfig_vr0_alias1="inet someip+2 netmask 255.255.255.255" ifconfig_vr0_alias1="inet otherip netmask 255.255.255.128" Or RTFM. Best regards, Gabriel From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 08:30:02 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 89CC216A4CE for ; Wed, 3 Mar 2004 08:30:02 -0800 (PST) Received: from juergen.edv-winter.de (juergen.edv-winter.de [195.226.65.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1CB743D3F for ; Wed, 3 Mar 2004 08:30:00 -0800 (PST) (envelope-from ar@g23.org) Received: from localhost (localhost [127.0.0.1])i23GSbST033750; Wed, 3 Mar 2004 17:28:49 +0100 (CET) (envelope-from ar@g23.org) Date: Wed, 3 Mar 2004 17:28:37 +0100 (CET) From: Andre Rein X-X-Sender: ar@juergen.edv-winter.de To: Erik Sliman In-Reply-To: <404605DC.4030809@openstandards.net> Message-ID: <20040303172617.B47509@juergen.edv-winter.de> References: <404605DC.4030809@openstandards.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: Creating multiple IPs 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, 03 Mar 2004 16:30:02 -0000 [] You've read documentation? grep alias /etc/defaults/rc.conf #ifconfig_lo0_alias0="inet 127.0.0.254 netmask 0xffffffff" # Sample alias entry. On Wed, 3 Mar 2004, Erik Sliman wrote: > How do you give a computer multiple static IPs? > > I've tried many things, including the ifaliases setting in rc.conf: > > ifconfig_vr0="inet 192.168.1.3 netmask 255.255.255.0" > ifaliases_vr0="192.168.1.36 255.255.255.0" > > but none seem to work. > _______________________________________________ > 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" > regards Andre -- "And some greetings from the Toaster" From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 08:40: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 07B1416A4CE for ; Wed, 3 Mar 2004 08:40:04 -0800 (PST) Received: from mail.joshuabranch.net (ip-66-80-53-4.dsl.lax.megapath.net [66.80.53.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4C5A43D1F for ; Wed, 3 Mar 2004 08:40:03 -0800 (PST) (envelope-from p500.2004@openstandards.net) Received: from openstandards.net (unknown [192.168.1.3]) by mail.joshuabranch.net (Postfix) with ESMTP id CF7917E0016; Wed, 3 Mar 2004 11:36:49 -0500 (EST) Message-ID: <40460A67.8070601@openstandards.net> Date: Wed, 03 Mar 2004 11:40:07 -0500 From: Erik Sliman User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5b) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andre Rein References: <404605DC.4030809@openstandards.net> <20040303172617.B47509@juergen.edv-winter.de> In-Reply-To: <20040303172617.B47509@juergen.edv-winter.de> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: Creating multiple IPs 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, 03 Mar 2004 16:40:04 -0000 Andre Rein wrote: >[] You've read documentation? > >grep alias /etc/defaults/rc.conf > >#ifconfig_lo0_alias0="inet 127.0.0.254 netmask 0xffffffff" # Sample alias entry. > > >On Wed, 3 Mar 2004, Erik Sliman wrote: > > > >>How do you give a computer multiple static IPs? >> >>I've tried many things, including the ifaliases setting in rc.conf: >> >> ifconfig_vr0="inet 192.168.1.3 netmask 255.255.255.0" >> ifaliases_vr0="192.168.1.36 255.255.255.0" >> >>but none seem to work. >>_______________________________________________ >>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" >> >> >> >regards > >Andre > > > Thank you. That worked. I read all the documentation I could find, which was very little. Basic networking requirements like this should be in the FreeBSD Manual. rc.conf man pages gave no examples, and differed from one version to another quite a bit. In the future, I'll grep the defaults first. From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 08:59: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 EA0CF16A4CF; Wed, 3 Mar 2004 08:59:59 -0800 (PST) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9852E43D1D; Wed, 3 Mar 2004 08:59:58 -0800 (PST) (envelope-from ru@ip.net.ua) Received: from heffalump.office.ipnet (heffalump.office.ipnet [10.71.1.80]) by tigra.ip.net.ua (8.12.10/8.12.9) with ESMTP id i23H2gj3084847 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Mar 2004 19:02:43 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.office.ipnet (8.12.11/8.12.11) id i23GxnOu022269; Wed, 3 Mar 2004 18:59:49 +0200 (EET) (envelope-from ru) Date: Wed, 3 Mar 2004 18:59:48 +0200 From: Ruslan Ermilov To: Yar Tikhiy Message-ID: <20040303165948.GA22163@ip.net.ua> References: <200403011722.i21HMG1h016273@repoman.freebsd.org> <20040303154554.GA51549@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline In-Reply-To: <20040303154554.GA51549@comp.chem.msu.su> User-Agent: Mutt/1.5.6i X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: net@FreeBSD.org Subject: Re: cvs commit: src/sys/netgraph ng_vlan.c ng_vlan.h src/sys/modules/netgraph Makefile src/sys/modules/netgraph/vlan Makefile src/share/man/man4 Makefile ng_vlan.4 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, 03 Mar 2004 17:00:00 -0000 --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hey Yar, I'm sending my reply to a public mailing list mainly to archive it, but also in a hope to attract some interested developer's attention. On Wed, Mar 03, 2004 at 06:45:55PM +0300, Yar Tikhiy wrote: > Greetings Ruslan, >=20 > On Mon, Mar 01, 2004 at 09:22:16AM -0800, Ruslan Ermilov wrote: > > ru 2004/03/01 09:22:16 PST > >=20 > > FreeBSD src repository > >=20 > > Modified files: > > sys/modules/netgraph Makefile=20 > > share/man/man4 Makefile=20 > > Added files: > > sys/netgraph ng_vlan.c ng_vlan.h=20 > > sys/modules/netgraph/vlan Makefile=20 > > share/man/man4 ng_vlan.4=20 > > Log: > > Netgraph node type for IEEE 802.1Q VLAN tagging. >=20 > Do I understand right that such issues as VLAN-level multicast > filtering and hardware tagging, which are handled by if_vlan, can't > be addressed by ng_vlan due to the nature of Netgraph? >=20 One needs real Ethernet hardware to program its multicast filter. In case of vlan(4) this is the parent interface. In the Netgraph case, the node connected to the "lower" hook is not necessarily ng_ether(4), yet ng_ether(4) doesn't support programming its multicast filter through Netgraph control messages. Similarly with h/w tagging: while ng_vlan(4) supports de-tagging of hardware supplied tags, it doesn't add tags suitable for h/w that support h/w VLAN tagging because it does not know what hardware it's connected to (it may be connected indirectly, or may be not connected to any real hardware at all, after all). It should be pretty easy though to add a new control message to program ng_vlan(4) to supply VLAN tags in the form suitable for hardware that supports it, rather than encapsulating header into ETHERTYPE_VLAN. It's just that I didn't need this functionality. If somebody needs it, it should be pretty trivial to implement, and I would be happy to review, test, and commit such a patch. Cheers, --=20 Ruslan Ermilov FreeBSD committer ru@FreeBSD.org --envbJBWh7q8WU6mo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFARg8EUkv4P6juNwoRArwtAJ46kEdqT9GP3w01bDxVRcJnX3ypBwCfcRNf ktBnVSyoXAtvTWQqDmVbsO4= =jxdF -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo-- From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 09:07: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 AD03816A4CE for ; Wed, 3 Mar 2004 09:07:59 -0800 (PST) Received: from exchange.wan.no (unknown [80.86.128.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id C47B043D4C for ; Wed, 3 Mar 2004 09:07:58 -0800 (PST) (envelope-from sten.daniel.sorsdal@wan.no) Content-class: urn:content-classes:message Date: Wed, 3 Mar 2004 18:08:02 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-ID: <78F980C200F8674DABD0F6D5E414DCDA04E32C@exchange.wanglobal.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Thread-Topic: ifconfig and route problem. Thread-Index: AcP66JadNvuPR31SRaSpzfkPA4fGTgApxUZQ From: =?iso-8859-1?Q?Sten_Daniel_S=F8rsdal?= To: "DrumFire" cc: freebsd-net@freebsd.org Subject: RE: ifconfig and route 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: Wed, 03 Mar 2004 17:07:59 -0000 =20 > > > # ifconfig rl0 $ip (where ip can be also 192.168.100.1),=20 > my default=20 > > > route is deleted, cut off server for my net. > > >=20 > >=20 > > Say you wanted to change from 192.168.100.1/24 to 10.0.0.1/24 With=20 > > default gateway changed from 192.168.100.254 to 10.0.0.254 >=20 > ?? My ask is simple: There's a way to avoid ifconfig reset=20 > default route also when newipaddress is the same of old ipaddress? >=20 > I don't understand your example, and I didn't change my ip=20 > address from 192.168.100.1/24 to 10.0.0.1/24 > =20 Yes there is a way and i showed you one way to do it. Apologies if this was too technical or not what you asked. _// Sten Daniel S=F8rsdal From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 09:09: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 0541816A4CE for ; Wed, 3 Mar 2004 09:09:50 -0800 (PST) Received: from juergen.edv-winter.de (juergen.edv-winter.de [195.226.65.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 550E143D3F for ; Wed, 3 Mar 2004 09:09:49 -0800 (PST) (envelope-from ar@g23.org) Received: from localhost (localhost [127.0.0.1])i23H8NST041164; Wed, 3 Mar 2004 18:08:33 +0100 (CET) (envelope-from ar@g23.org) Date: Wed, 3 Mar 2004 18:08:23 +0100 (CET) From: Andre Rein X-X-Sender: ar@juergen.edv-winter.de To: Gabriel Ambuehl In-Reply-To: <54297371.20040303173111@buz.ch> Message-ID: <20040303180530.N47509@juergen.edv-winter.de> References: <404604FC.1020506@openstandards.net> <54297371.20040303173111@buz.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: Multiple static IPs 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, 03 Mar 2004 17:09:50 -0000 On Wed, 3 Mar 2004, Gabriel Ambuehl wrote: > Hello Erik, > > Wednesday, March 3, 2004, 5:17:00 PM, you wrote: > > > How do you give a computer multiple static IPs? > > > I've tried many things, including the ifaliases setting in rc.conf: > > > ifconfig_vr0="inet 192.168.1.3 netmask 255.255.255.0" > > ifaliases_vr0="192.168.1.36 255.255.255.0" > > > but none seem to work. > > > Wrong list but anyhow: > Why is it the wrong list? About freebsd-net: Discussions of networking in general and TCP/IP source code in particular. correct me if I'm false. gruss/regards Andre -- "And some greetings from the Toaster" From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 09:10: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 45E2916A4DB for ; Wed, 3 Mar 2004 09:10:18 -0800 (PST) Received: from chaos.evolve.za.net (chaos.evolve.za.net [196.34.172.107]) by mx1.FreeBSD.org (Postfix) with ESMTP id 434E943D41 for ; Wed, 3 Mar 2004 09:10:17 -0800 (PST) (envelope-from cole@opteqint.net) Received: from root by chaos.evolve.za.net with scanned-ok (Exim 3.36 #1) id 1AyZss-0004rM-00 for net@freebsd.org; Wed, 03 Mar 2004 19:10:14 +0200 Received: from [196.39.126.250] (helo=stalker) by chaos.evolve.za.net with asmtp (TLSv1:RC4-MD5:128) (Exim 3.36 #1) id 1AyZsr-0004qz-00; Wed, 03 Mar 2004 19:10:14 +0200 Message-ID: <007e01c40142$fe89a780$4206000a@stalker> From: "Cole" To: "Mathieu Arnold" References: <09be01c4011f$83228cb0$02c0a8c0@gnbuero.qhintra.net> <20040303131512.GC35449@shellma.zin.lublin.pl> <1294253421.1078330774@andromede.faubourg.reaumur.net> Date: Wed, 3 Mar 2004 19:14:31 +0200 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 X-Virus-Scanned: by Opteq - www.optec.co.za cc: net@freebsd.org Subject: Re: freevrrpd (was: My planned work on networking stack) 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, 03 Mar 2004 17:10:18 -0000 Hi The problem with freevrrp on vlan is that the ether MAC address gets changed on the vlan device which is then different to the parent device that the vlan was attached to. Since the vlan then has a different ether MAC to the parent device, i dont think the parent device is passing the packets back to the vlan device. What i tried to implement was a patch to the vlan device to update the parent device's ether MAC address. I dont do this kind of programming so i really dont have much skill with device drivers, i asked a few devs that worked on the vlan device, and i either got no reply, and the ones that did reply, only did so once and no further. So if someone is willing to help, i would do whatever i can to help to. Thanx /Cole ----- Original Message ----- From: "Mathieu Arnold" To: "Pawel Malachowski" ; "Markus Oestreicher" Cc: Sent: Wednesday, March 03, 2004 5:19 PM Subject: Re: freevrrpd (was: My planned work on networking stack) From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 09:12: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 E5EB416A4CE for ; Wed, 3 Mar 2004 09:12:30 -0800 (PST) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAB1343D48 for ; Wed, 3 Mar 2004 09:12:29 -0800 (PST) (envelope-from ru@ip.net.ua) Received: from heffalump.office.ipnet (heffalump.office.ipnet [10.71.1.80]) by tigra.ip.net.ua (8.12.10/8.12.9) with ESMTP id i23HFHj3085101 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Mar 2004 19:15:18 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.office.ipnet (8.12.11/8.12.11) id i23HCOin022570; Wed, 3 Mar 2004 19:12:24 +0200 (EET) (envelope-from ru) Date: Wed, 3 Mar 2004 19:12:23 +0200 From: Ruslan Ermilov To: Erik Sliman Message-ID: <20040303171223.GC22435@ip.net.ua> References: <404605DC.4030809@openstandards.net> <20040303172617.B47509@juergen.edv-winter.de> <40460A67.8070601@openstandards.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Y5rl02BVI9TCfPar" Content-Disposition: inline In-Reply-To: <40460A67.8070601@openstandards.net> User-Agent: Mutt/1.5.6i X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: Andre Rein cc: freebsd-net@freebsd.org Subject: Re: Creating multiple IPs 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, 03 Mar 2004 17:12:31 -0000 --Y5rl02BVI9TCfPar Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 03, 2004 at 11:40:07AM -0500, Erik Sliman wrote: [...] > Thank you. That worked. I read all the documentation I could find, which= =20 > was very little. Basic networking requirements like this should be in=20 > the FreeBSD Manual. rc.conf man pages gave no examples, and differed=20 > from one version to another quite a bit. >=20 This is not true. Search for the first word "alias" in the rc.conf(5) manpage. Cheers, --=20 Ruslan Ermilov FreeBSD committer ru@FreeBSD.org --Y5rl02BVI9TCfPar Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFARhH3Ukv4P6juNwoRAhnIAJ9aP+zLte2uK5jY3vh2hK98O0FQpQCeIbl+ OVdqCHKJD1CgGcCNheNoXzI= =tFA6 -----END PGP SIGNATURE----- --Y5rl02BVI9TCfPar-- From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 09:28:53 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C43816A4CE; Wed, 3 Mar 2004 09:28:53 -0800 (PST) Received: from ctb-mesg6.saix.net (ctb-mesg6.saix.net [196.25.240.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 830B343D2D; Wed, 3 Mar 2004 09:28:52 -0800 (PST) (envelope-from karnaugh@karnaugh.za.net) Received: from karnaugh.za.net (ndn-ip-nas-1-p99.telkom-ipnet.co.za [155.239.192.99]) by ctb-mesg6.saix.net (Postfix) with ESMTP id 960467E1E; Wed, 3 Mar 2004 19:28:48 +0200 (SAST) Message-ID: <404615EA.1090305@karnaugh.za.net> Date: Wed, 03 Mar 2004 19:29:14 +0200 From: Colin Alston User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ruslan Ermilov References: <404605DC.4030809@openstandards.net> <20040303172617.B47509@juergen.edv-winter.de> <40460A67.8070601@openstandards.net> <20040303171223.GC22435@ip.net.ua> In-Reply-To: <20040303171223.GC22435@ip.net.ua> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Andre Rein cc: Erik Sliman cc: freebsd-net@freebsd.org Subject: Re: Creating multiple IPs 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, 03 Mar 2004 17:28:53 -0000 Ruslan Ermilov wrote: >On Wed, Mar 03, 2004 at 11:40:07AM -0500, Erik Sliman wrote: >[...] > > >>Thank you. That worked. I read all the documentation I could find, which >>was very little. Basic networking requirements like this should be in >>the FreeBSD Manual. rc.conf man pages gave no examples, and differed >>from one version to another quite a bit. >> >> >> >This is not true. Search for the first word "alias" in the rc.conf(5) >manpage. > > >Cheers, > > The hint here being the netmask, about which the documentation is a little vague on the reasoning IMHO, which seems to trip up alot of people. Other operating systems cater for aliases with a bit more automata from what I've seen, not that this is a good thing. From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 09:52: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 473BE16A4CE; Wed, 3 Mar 2004 09:52:55 -0800 (PST) Received: from xaqua.tel.fer.hr (xaqua.tel.fer.hr [161.53.19.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A82D43D2D; Wed, 3 Mar 2004 09:52:54 -0800 (PST) (envelope-from zec@tel.fer.hr) Received: by xaqua.tel.fer.hr (Postfix, from userid 20006) id D4E4A9B644; Wed, 3 Mar 2004 18:52:52 +0100 (CET) Received: from marko-tp.zavod.tel.fer.hr (marko-tp.zavod.tel.fer.hr [161.53.19.42]) by xaqua.tel.fer.hr (Postfix) with ESMTP id D4CD99B646; Wed, 3 Mar 2004 18:52:41 +0100 (CET) From: Marko Zec To: Takanori Watanabe , Julian Elischer Date: Wed, 3 Mar 2004 18:52:01 +0100 User-Agent: KMail/1.5.4 References: <200403030336.MAA24341@axe-inc.co.jp> In-Reply-To: <200403030336.MAA24341@axe-inc.co.jp> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200403031852.01919.zec@tel.fer.hr> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on xaqua.tel.fer.hr X-Spam-Level: X-Spam-Status: No, hits=-0.2 required=5.0 tests=AWL autolearn=no version=2.63 X-Sanitizer: Advosys mail filter cc: bzeeb-lists@lists.zabbadoz.net cc: james@physicalsegment.com cc: freebsd-current@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: Was: My planned work on networking stack (vimage) 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, 03 Mar 2004 17:52:55 -0000 On Wednesday 03 March 2004 04:36, Takanori Watanabe wrote: > In message > , Ju > > lian Elischer wrote: ... > >The trick is that you need to be able to arbitrarily add a protocol, > >or a firewall stack or other modules. As I said it can be done. > >What is a problem is that 'static' form of the current vimage > >structure.. > > > >Even > > > >struct { > >#ifdef NETINET > > ..inet variables > >#endif > >#ifdef NETATALK > > .. appletalk variables > >#endif > >[etc.] > >} vimage; > > > >is not tennable because you cannot keep adding parts to the > > structure.. The whole aim of FreeBSD over the last 10 years has > > been to move towards modularity, in almost all areas. > > Generally #ifdef's are obstacles for making it moduler. > Exactly, and precisely for that reason the vimage/vnet structures had never included any conditional statements. The current approach is to include any networking symbol in the vnet struct, regardles whether the respective network family is configured / compiled in the kernel or not. As of today the vnet struct, which is less than 30.000 bytes long, includes all virtualized symbols from the net, netinet, and netipx trees. My assesment is that even if all relevant symbols from all supported networking families would be virtualized, the structure wouldn't grow beyond 100 kbytes or so... Which is still small enough for not to worry about a few wasted memory pages if certain network protocol family is not configured in the current kernel, so that the respective fields in struct vnet remain unused. Marko > >If you could add modules and have them add themselves to existing > >(or even only new) vimages, then it could be viable in FreeBSD. > > But networking stack itself now contains *many* #ifdef's, so > we cannot add ethernet protocol by kld, for example NETATALK now. > It may be done by all protocols layers are connected by netgraph(4). > > Static structure definition are certainly obstackles for making > moduler, but gathering protocol stack private values into a structure > will on the contrally help for it, by figuring out which data should > we duplicate From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 10: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 C84AB16A4CE; Wed, 3 Mar 2004 10:10:35 -0800 (PST) Received: from mx01.bos.ma.towardex.com (a65-124-16-8.svc.towardex.com [65.124.16.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3547D43D39; Wed, 3 Mar 2004 10:10:35 -0800 (PST) (envelope-from haesu@mx01.bos.ma.towardex.com) Received: by mx01.bos.ma.towardex.com (TowardEX ESMTP 3.0p11_DAKN, from userid 1001) id A55872F91A; Wed, 3 Mar 2004 13:10:34 -0500 (EST) Date: Wed, 3 Mar 2004 13:10:34 -0500 From: James To: Gleb Smirnoff , Wes Peters , Andre Oppermann , freebsd-net@freebsd.org, freebsd-current@freebsd.org Message-ID: <20040303181034.GA58284@scylla.towardex.com> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040302082625.GE22985@cell.sick.ru> User-Agent: Mutt/1.4.1i Subject: Re: My planned work on networking stack 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, 03 Mar 2004 18:10:36 -0000 hello - > Is there any plans about integration of BGP routing daemon (Zebra or Quagga) > into FreeBSD? With BGP routing daemon onboard, FreeBSD will be a strong > alternative against expensive commercial routers. I have successfull experience > of running FreeBSD STABLE with 2 full BGP views for half a year. before FreeBSD can be a 'strong alternative against expensive commercial routers', there are several things that must be done rewriting of routing stack and implementing FIB-like structure as what andre proposed in this thread is very welcoming. there are still other things freebsd lacks. such as uRPF that _SERVICE_PROVIDER_ can use. ipfw2 has verrevpath but all it does from what i know is strict uRPF only. service providers like myself, if we were to use freebsd boxen to run our network, i am not spending money on a router that doesn't do loose-check uRPF. this sounds like something linux does too but i refuse to use that :P implementation of policy routing similar to vrf's is something i wanted for a while as well. modern router deployments out in service provider core arena requires most people to start implementing "routing processes" using different routing instances. i.e. carrying mpls core routes in one routing instance, and carrying transit routes in the other to prevent core being affected by edge or outside routing failures, etc, etc > Modern i386 PC > can route/filter/shape much more traffic than expensive Cisco 36xx. I haven't > yet compared with 7000 series... comparing a modern x86 box running freebsd against a 3600 is a piece of cake. comparing a modern x86 box running freebsd against a 7000 is a piece of cake. comparing an x86 box running freebsd against a 7500 with old vip's and RSP1 or RSP2 is also piece of cake. there must be something seriously wrong if any of these junk old crisco routers that were supposed to be in dumpster since Jan 1st 2004, can beat modern freebsd box's performance. comparing a modern x86 box against a Cisco 7206VXR with NPE-G1 however is a good challenge :) > > Currently I'm working on my Netflow implementation, and I have faced the > following problem: I've already got global routing in my routing table, but it > lacks AS (Autonomous System) information. The routing daemon (zebra in my case) > already knows ASes, but this informations is lost when routing information is > injected into kernel. It'll be nice to add AS path to struct rtentry. > Seems like there is no problem with extending struct rtentry, but injecting > this info from userland requires changes to routing API. I see two ways of > implementing it: why inject as_path info from userland to kernel "fib"? may be netflow turning into an api that quagga can take advantage of to gather accounting information is more feasible? -- James Jun TowardEX Technologies, Inc. Technical Lead Network Design, Consulting, IT Outsourcing james@towardex.com Boston-based Colocation & Bandwidth Services cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 10:44: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 9558416A4CE; Wed, 3 Mar 2004 10:44: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 7CE5043D1D; Wed, 3 Mar 2004 10:44:22 -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 i23IiCRH015671; Wed, 3 Mar 2004 10:44:15 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i23IiB2j015667; Wed, 3 Mar 2004 10:44:11 -0800 Date: Wed, 3 Mar 2004 10:44:11 -0800 From: Brooks Davis To: Cole Message-ID: <20040303184409.GA1466@Odin.AC.HMC.Edu> References: <09be01c4011f$83228cb0$02c0a8c0@gnbuero.qhintra.net> <20040303131512.GC35449@shellma.zin.lublin.pl> <1294253421.1078330774@andromede.faubourg.reaumur.net> <007e01c40142$fe89a780$4206000a@stalker> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sdtB3X0nJg68CQEu" Content-Disposition: inline In-Reply-To: <007e01c40142$fe89a780$4206000a@stalker> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: Mathieu Arnold cc: net@freebsd.org Subject: Re: freevrrpd (was: My planned work on networking stack) 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, 03 Mar 2004 18:44:22 -0000 --sdtB3X0nJg68CQEu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 03, 2004 at 07:14:31PM +0200, Cole wrote: >=20 > The problem with freevrrp on vlan is that the ether MAC address gets > changed on the vlan device which is then different to the parent > device that the vlan was attached to. Since the vlan then has a > different ether MAC to the parent device, i dont think the parent > device is passing the packets back to the vlan device. > > What i tried to implement was a patch to the vlan device to update the > parent device's ether MAC address. I dont do this kind of programming > so i really dont have much skill with device drivers, i asked a few > devs that worked on the vlan device, and i either got no reply, and > the ones that did reply, only did so once and no further. You can't just change the parent, you will also have to change the MAC of any other vlans of the parent. This requires scanning the interface list for vlans and checking if they are children of the parent interface. This is non-trivial, but doable. If a patch that did this were written and met style(9), I'd probably be willing it commit it. It won't help people who want to abuse vlans to let a server do fail over for multiple machines on different subnets though. The real solution is to modify the Ethernet code to allow processing of select, non-multicast MACs up the the point where they are sent to the vlan which can decide which MACs it's actually going to pay attention to. This means you have to do some filtering in software (probably all filtering on many (most?, all?) nics). I think this could be done by reordering parts of ether_demux and modifying the way packets which don't match our "primary" address are handled. This looks do-able, but care are would have to be taken to ensure things were done correctly and that performance for the other 99.999+% of the world wasn't measurably harmed. -- 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 --sdtB3X0nJg68CQEu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFARid3XY6L6fI4GtQRAqKBAKC+ClweVeyNM8aNSOrLGKztSuv5KgCeJg+i qBnNP+q0OKakkAVnMdyfvgE= =Gng9 -----END PGP SIGNATURE----- --sdtB3X0nJg68CQEu-- From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 13:53: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 A03FD16A4CF for ; Wed, 3 Mar 2004 13:53:35 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDCDB43D1D for ; Wed, 3 Mar 2004 13:53:34 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 77255 invoked from network); 3 Mar 2004 21:53:33 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.54]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 3 Mar 2004 21:53:33 -0000 Message-ID: <404653DB.186DA0C2@freebsd.org> Date: Wed, 03 Mar 2004 22:53:31 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: James References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040303181034.GA58284@scylla.towardex.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 03 Mar 2004 21:53:35 -0000 James wrote: > rewriting of routing stack and implementing FIB-like structure as what andre > proposed in this thread is very welcoming. Just wait a few month and then have a look at what I put up. :-) > there are still other things freebsd lacks. such as uRPF that _SERVICE_PROVIDER_ > can use. ipfw2 has verrevpath but all it does from what i know is strict uRPF > only. service providers like myself, if we were to use freebsd boxen to run our > network, i am not spending money on a router that doesn't do loose-check uRPF. > this sounds like something linux does too but i refuse to use that :P That is pretty easy to implement. I should have it by Friday at latest, depends on when exactly I find time for it. ip verify unicast source reachable-via [any|ifn] The ipfw2 command would look like this: ... versrcreach [fxp0] What else is missing in FreeBSD? -- Andre From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 14:06: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 CBEF916A4CE; Wed, 3 Mar 2004 14:06:45 -0800 (PST) Received: from oahu.WURLDLINK.NET (oahu.wurldlink.net [66.193.144.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A53043D39; Wed, 3 Mar 2004 14:06:45 -0800 (PST) (envelope-from vince@oahu.WURLDLINK.NET) Received: from oahu.WURLDLINK.NET (vince@localhost.WURLDLINK.NET [127.0.0.1]) by oahu.WURLDLINK.NET (8.12.9/8.12.9) with ESMTP id i23M6AqQ089026; Wed, 3 Mar 2004 12:06:10 -1000 (HST) Received: from localhost (vince@localhost)i23M6AkT089023; Wed, 3 Mar 2004 12:06:10 -1000 (HST) Date: Wed, 3 Mar 2004 12:06:10 -1000 (HST) From: Vincent Poy To: freebsd-net@freebsd.org, Message-ID: <20040303120211.O8264-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: ipfw/dummynet pipe size, is there a burst setting? 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, 03 Mar 2004 22:06:45 -0000 Hello everyone: On FreeBSD with ipfw/dummynet for traffic shaping, one uses the pipe with: ipfw pipe 1 config bw size to set the size of the pipe. I noticed on Linux, they can set a burst size so it can burst a x number over the pipe size, is there a similar setting available? Also, I noticed for pipes, one can set the queue size in slots of KBytes, how does one determine what's a good size? Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 16:03: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 E647A16A4CE; Wed, 3 Mar 2004 16:03:23 -0800 (PST) Received: from mx01.bos.ma.towardex.com (a65-124-16-8.svc.towardex.com [65.124.16.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77ECD43D2D; Wed, 3 Mar 2004 16:03:23 -0800 (PST) (envelope-from haesu@mx01.bos.ma.towardex.com) Received: by mx01.bos.ma.towardex.com (TowardEX ESMTP 3.0p11_DAKN, from userid 1001) id DCBC72F920; Wed, 3 Mar 2004 19:03:22 -0500 (EST) Date: Wed, 3 Mar 2004 19:03:22 -0500 From: James To: Brad Knowles Message-ID: <20040304000322.GA68107@scylla.towardex.com> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302125935.GA25835@cell.sick.ru> 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 cc: Andre Oppermann Subject: Re: My planned work on networking stack 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, 04 Mar 2004 00:03:24 -0000 > Do you have multiple connectivity to two separate metro area > exchanges, with multiple upstreams at each? i dont know about europe, but here in the US, finding transits and filling up fib with 130K+ routes is easier than ever. welcome to equinix > Most large cities are > lucky to have a single major metro area exchange, and the author of > bgpd for OpenBSD works at an ISP located in Hamburg which is lucky > enough to have two major NAPs, and he has multiple connectivity to > both. He was the one ragging on zebra/quagga. i don't know man, but we have a zebra box on our corporate network taking 4 full feeds and 5 partial feeds + downstream neighbors for more than 6 months now? havent had any problems other than bgpd taking several seconds to lock up the CLI during session flaps caused by maintenance work on our backbone router thats sending full transit (which isnt bgpd's fault btw) > Among other things, > he said he had real problems keeping sessions up with zebra/quagga > when neighbors were flapping. that's an interesting 'bug' most people including myself didnt have to deal with. perhaps more technical information should be gathered first before blaming zebra/quagga for not being able to keep 1w of bgp session uptime? oh for your amusement, telnet route-views2.oregon-ix.net and type sh ip bgp sum, then type sh ver > > IIRC, he's also got some pretty big cisco equipment (75xx or > whatever), sorry but 7500 isnt pretty big other than a size comparable to a fridge that acts as a good heater in my bedroom. [! multi snips !] [! combining with another emails from you !] > My point is that zebra/quagga have significant limitations that > restrict their usefulness, due to the design of the system. > Moreover, the development on zebra has effectively stalled since the > author got hired away to do that kind of work professionally, and > development on quagga has apparently been sporadic and relatively > limited, presumably due to the fact that they don't have replacement > developers of the same caliber. have you even used zebra taking full routes? or quagga, whatever. or are you just talking out of whatever "YMMV Stories" you are hearing from other people? truth != lack of experience > If we want to get to the point where we can have a reasonable > expectation of throwing away all cisco, juniper, Foundry, and other > routing hardware and replace them with something that is easier to > install, configure, monitor, and manage, then I think we need to be > looking beyond zebra/quagga. if we want to get to the point where we can have a reasonable expectation of throwing away ciscos, (but sorry no, i am not throwing away my junipers), zebra/quagga isn't the place to focus our efforts at on this thread. quagga is doing fine in keeping up with defects of zebra as well what we need now is a FIB that is *better* at handling PPS, which is what andre is trying to do. the FreeBSD project is not a router company, but we do want a good *nix kernel and environment that provides the core api's and the environment needed for good pps forwarding performance and rib->fib interaction with the userlands remember, the point of the discussion on this thread is to update mainly the forwarding plane portion, not control forwarding != zebra/quagga, openbsd bgpd, or any bgpd of that matter -- James Jun TowardEX Technologies, Inc. Technical Lead Network Design, Consulting, IT Outsourcing james@towardex.com Boston-based Colocation & Bandwidth Services cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 19:07: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 49E9416A4CE for ; Wed, 3 Mar 2004 19:07:30 -0800 (PST) Received: from ftp.ccrle.nec.de (ftp.netlab.nec.de [195.37.70.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C80A43D39 for ; Wed, 3 Mar 2004 19:07:29 -0800 (PST) (envelope-from stiemerling@netlab.nec.de) Received: from cgn.wireless.ietf59.or.kr (cgn.wireless.ietf59.or.kr [218.37.227.250]) by ftp.ccrle.nec.de (Postfix) with ESMTP id 21E57F5A9; Thu, 4 Mar 2004 04:12:17 +0100 (CET) Date: Thu, 04 Mar 2004 04:07:31 +0100 From: Martin Stiemerling To: Joost Bekkers , net@freebsd.org Message-ID: <2147483647.1078373251@cgn.wireless.ietf59.or.kr> In-Reply-To: <20040303114738.GA85522@bps.jodocus.org> References: <20040303114738.GA85522@bps.jodocus.org> X-Mailer: Mulberry/3.1.2 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Re: IPFW2 for IPv6 ?? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Mar 2004 03:07:30 -0000 --On Mittwoch, 3. M=E4rz 2004 12:47 Uhr +0100 Joost Bekkers=20 wrote: | Hello | | Are there any plans to make IPFW2 work for IPv6? | | Or can someone recommend a statefull firewall for IPv6? You could try ipfilter, it's included in FreeBSD (man ipf). There is a=20 porting effort to bring OpenBSD's pf to FreeBSD, but I don't know how far=20 it is. Martin From owner-freebsd-net@FreeBSD.ORG Wed Mar 3 23:37:02 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 27FE816A4CE for ; Wed, 3 Mar 2004 23:37:02 -0800 (PST) Received: from bps.jodocus.org (g157016.upc-g.chello.nl [80.57.157.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFF2A43D1D for ; Wed, 3 Mar 2004 23:37:00 -0800 (PST) (envelope-from joost@jodocus.org) Received: from jodocus.org (localhost [127.0.0.1]) by bps.jodocus.org (8.12.10/8.12.10) with ESMTP id i247ax5M004059; Thu, 4 Mar 2004 08:36:59 +0100 (CET) (envelope-from joost@jodocus.org) Received: (from joost@localhost) by jodocus.org (8.12.10/8.12.10/Submit) id i247awSR004058; Thu, 4 Mar 2004 08:36:58 +0100 (CET) (envelope-from joost) Date: Thu, 4 Mar 2004 08:36:58 +0100 From: Joost Bekkers To: Luigi Rizzo Message-ID: <20040304073658.GA3991@bps.jodocus.org> References: <20040303114738.GA85522@bps.jodocus.org> <20040303041239.A11330@xorpc.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040303041239.A11330@xorpc.icir.org> User-Agent: Mutt/1.4.2.1i cc: net@freebsd.org Subject: Re: IPFW2 for IPv6 ?? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Mar 2004 07:37:02 -0000 On Wed, Mar 03, 2004 at 04:12:39AM -0800, Luigi Rizzo wrote: > On Wed, Mar 03, 2004 at 12:47:38PM +0100, Joost Bekkers wrote: > > Hello > > > > Are there any plans to make IPFW2 work for IPv6? > > i posted some experimental code to the -network (or was it -ipfw ?) list > early in january, expect a cleaned up version in a couple of weeks. > The patch was for -stable but should be relatively straightworward > to apply to -current. > patch(1) complaines a lot when I try to use the patch on 5.2.1-R. I tried to patch the rejected bits manually, but decided I'll wait for the cleaned up version. thanks -- greetz Joost joost@jodocus.org From owner-freebsd-net@FreeBSD.ORG Thu Mar 4 01:00: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 3B52916A4E0 for ; Thu, 4 Mar 2004 01:00:29 -0800 (PST) Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.136.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A10143D39 for ; Thu, 4 Mar 2004 01:00:29 -0800 (PST) (envelope-from jrh@it.uc3m.es) Received: from smtp01.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id E6D4C10516 for ; Thu, 4 Mar 2004 10:00:27 +0100 (CET) Received: from localhost.invalid (unknown [163.117.140.30]) by smtp01.uc3m.es (Postfix) with ESMTP id D2D88F159 for ; Thu, 4 Mar 2004 10:00:27 +0100 (CET) From: Juan Rodriguez Hervella Organization: UC3M To: freebsd-net@freebsd.org Date: Thu, 4 Mar 2004 10:00:25 +0100 User-Agent: KMail/1.6 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200403041000.25489.jrh@it.uc3m.es> Subject: openVPN question 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, 04 Mar 2004 09:00:45 -0000 Tuc at the Beach House said: > Hi, > > --redirect-gateway > Automatically execute routing commands to cause all > outgoing IP traffic to be redirected over the VPN. > Currently implemented only on Linux and Windows. An James Yonan said: > Ah, yes, that's a problem. > > The --redirect-gateway implementation needs to be able to get the IP address > of the current default gateway. Unfortunately the standard Berkeley sockets > API doesn't give us a portable way of doing this. Anyone know how to > do this on FreeBSD? So ? :) -- ****** JFRH ****** From owner-freebsd-net@FreeBSD.ORG Thu Mar 4 01:22:08 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CED9716A4CE for ; Thu, 4 Mar 2004 01:22:08 -0800 (PST) Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.136.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16D4443D2D for ; Thu, 4 Mar 2004 01:22:08 -0800 (PST) (envelope-from jrh@it.uc3m.es) Received: from smtp03.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id C7EBA10648 for ; Thu, 4 Mar 2004 10:22:06 +0100 (CET) Received: from localhost.invalid (unknown [163.117.140.30]) by smtp03.uc3m.es (Postfix) with ESMTP id B124A10646 for ; Thu, 4 Mar 2004 10:22:06 +0100 (CET) From: Juan Rodriguez Hervella Organization: UC3M To: freebsd-net@freebsd.org Date: Thu, 4 Mar 2004 10:22:04 +0100 User-Agent: KMail/1.6 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200403041022.04338.jrh@it.uc3m.es> Subject: openVPN question 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, 04 Mar 2004 09:22:09 -0000 (sorry If you receive twice this mail, I'm having problems with my email....) Tuc at the Beach House said: > Hi, > > --redirect-gateway > Automatically execute routing commands to cause all > outgoing IP traffic to be redirected over the VPN. > Currently implemented only on Linux and Windows. An James Yonan said: > Ah, yes, that's a problem. > > The --redirect-gateway implementation needs to be able to get the IP address > of the current default gateway. Unfortunately the standard Berkeley sockets > API doesn't give us a portable way of doing this. Anyone know how to > do this on FreeBSD? So ? :) -- ****** JFRH ****** From owner-freebsd-net@FreeBSD.ORG Thu Mar 4 05:10:09 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 0728B16A57D; Thu, 4 Mar 2004 05:10:09 -0800 (PST) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B57843D49; Thu, 4 Mar 2004 05:10:08 -0800 (PST) (envelope-from glebius@cell.sick.ru) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.9/8.12.8) with ESMTP id i24DA1QE041509 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Mar 2004 16:10:01 +0300 (MSK) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.9/8.12.6/Submit) id i24DA0bt041505; Thu, 4 Mar 2004 16:10:00 +0300 (MSK) Date: Thu, 4 Mar 2004 16:10:00 +0300 From: Gleb Smirnoff To: James Message-ID: <20040304131000.GA41474@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , James , Wes Peters , Andre Oppermann , freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040303181034.GA58284@scylla.towardex.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20040303181034.GA58284@scylla.towardex.com> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org cc: Andre Oppermann cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 04 Mar 2004 13:10:09 -0000 On Wed, Mar 03, 2004 at 01:10:34PM -0500, James wrote: J> > Currently I'm working on my Netflow implementation, and I have faced the J> > following problem: I've already got global routing in my routing table, but it J> > lacks AS (Autonomous System) information. The routing daemon (zebra in my case) J> > already knows ASes, but this informations is lost when routing information is J> > injected into kernel. It'll be nice to add AS path to struct rtentry. J> > Seems like there is no problem with extending struct rtentry, but injecting J> > this info from userland requires changes to routing API. I see two ways of J> > implementing it: J> J> why inject as_path info from userland to kernel "fib"? may be netflow turning J> into an api that quagga can take advantage of to gather accounting information J> is more feasible? James, can you please describe your idea more understandible? I can't understand your last sentence, sorry. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Thu Mar 4 06:38:12 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 250C616A4CE for ; Thu, 4 Mar 2004 06:38:12 -0800 (PST) Received: from wonder.mndmttr.nl (mndmttr.nl [194.109.241.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 860B843D31 for ; Thu, 4 Mar 2004 06:38:09 -0800 (PST) (envelope-from lvd@mndmttr.nl) Received: from wonder.mndmttr.nl (localhost [127.0.0.1]) by wonder.mndmttr.nl (8.12.9p2/8.12.6) with ESMTP id i24EZUlU013677; Thu, 4 Mar 2004 15:35:30 +0100 (CET) (envelope-from lvd@mndmttr.nl) Received: (from lvd@localhost) by wonder.mndmttr.nl (8.12.9p2/8.12.6/Submit) id i24EZUbo013676; Thu, 4 Mar 2004 15:35:30 +0100 (CET) X-Authentication-Warning: wonder.mndmttr.nl: lvd set sender to lvd@mndmttr.nl using -f From: Luuk van Dijk To: ano@du.se, c.prevotaux@hexanet.fr, freebsd-net@freebsd.org In-Reply-To: <1078406027.29725.27.camel@crazyharry> References: <1078406027.29725.27.camel@crazyharry> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Mind over Matter B.V. Message-Id: <1078410929.255.270.camel@wonder> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 04 Mar 2004 15:35:30 +0100 Subject: mpd/netgraph l2tp 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, 04 Mar 2004 14:38:12 -0000 Hi, my colleague just found a message exchange in this newsgroup dated 2003/11/23 about a netgraph version of l2tp. It pleases me to announce that we (www.BuyWays.nl) have just embarked on a project to bring just that. we are developing a setup where a single FreeBSD box will be the endpoint for a few thousand dialup links over l2tp to perform multicast routing between them, and mpd/ng_l2tp is a major part of that. Part one of the project: patching pim6sd so it can handle transient interfaces has just been done, now we have a few weeks to strip lt2pd to the bone, plug in the netgraph machinery and go!. Anyone feeling like lending a hand is more than welcome :-) Eg.: one rather isolated thing on the todo list is to bring ipv6 support in mpd. we'll announce our progres on this list, and hope to publish a prealpha somewhere next week. Regards, Luuk van Dijk CTO BuyWays B.V. From owner-freebsd-net@FreeBSD.ORG Thu Mar 4 09:25: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 51A9316A4CE; Thu, 4 Mar 2004 09:25:30 -0800 (PST) Received: from mx01.bos.ma.towardex.com (a65-124-16-8.svc.towardex.com [65.124.16.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 137AC43D41; Thu, 4 Mar 2004 09:25:30 -0800 (PST) (envelope-from haesu@mx01.bos.ma.towardex.com) Received: by mx01.bos.ma.towardex.com (TowardEX ESMTP 3.0p11_DAKN, from userid 1001) id 06DDC2F898; Thu, 4 Mar 2004 12:25:30 -0500 (EST) Date: Thu, 4 Mar 2004 12:25:30 -0500 From: James To: Gleb Smirnoff , James , Wes Peters , Andre Oppermann , freebsd-net@freebsd.org, freebsd-current@freebsd.org Message-ID: <20040304172529.GA86502@scylla.towardex.com> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040303181034.GA58284@scylla.towardex.com> <20040304131000.GA41474@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040304131000.GA41474@cell.sick.ru> User-Agent: Mutt/1.4.1i Subject: Re: My planned work on networking stack 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, 04 Mar 2004 17:25:30 -0000 > J> why inject as_path info from userland to kernel "fib"? may be netflow turning > J> into an api that quagga can take advantage of to gather accounting information > J> is more feasible? > > James, can you please describe your idea more understandible? I can't understand > your last sentence, sorry. sorry, i wasn't writing clearly :) what i meant is, an implementation of an API for netflow gathering stats from the kernel. once you have that API, perhaps quagga can take advantage of that API, to support netflow accounting by itself, along with as path information and all that.. that was my thought initially, BUT.. actually... you can actually do this no problem using mrtd dumps and pick it up with a program via bgp device :P no need to create another api it seems :) -J -- James Jun TowardEX Technologies, Inc. Technical Lead Network Design, Consulting, IT Outsourcing james@towardex.com Boston-based Colocation & Bandwidth Services cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net From owner-freebsd-net@FreeBSD.ORG Thu Mar 4 09:26:51 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 4242D16A4CE; Thu, 4 Mar 2004 09:26:51 -0800 (PST) Received: from mx01.bos.ma.towardex.com (a65-124-16-8.svc.towardex.com [65.124.16.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 180FC43D31; Thu, 4 Mar 2004 09:26:51 -0800 (PST) (envelope-from haesu@mx01.bos.ma.towardex.com) Received: by mx01.bos.ma.towardex.com (TowardEX ESMTP 3.0p11_DAKN, from userid 1001) id 6B39E2F8D6; Thu, 4 Mar 2004 12:26:51 -0500 (EST) Date: Thu, 4 Mar 2004 12:26:51 -0500 From: James To: James Message-ID: <20040304172651.GA86659@scylla.towardex.com> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040303181034.GA58284@scylla.towardex.com> <20040304131000.GA41474@cell.sick.ru> <20040304172529.GA86502@scylla.towardex.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040304172529.GA86502@scylla.towardex.com> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org cc: Andre Oppermann cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 04 Mar 2004 17:26:51 -0000 > > that was my thought initially, BUT.. actually... you can > actually do this no problem using mrtd dumps and pick it up with a > program via bgp device :P no need to create another api it seems :) errr??? I meant bpf device... > > -J > > > -- > James Jun TowardEX Technologies, Inc. > Technical Lead Network Design, Consulting, IT Outsourcing > james@towardex.com Boston-based Colocation & Bandwidth Services > cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net -- James Jun TowardEX Technologies, Inc. Technical Lead Network Design, Consulting, IT Outsourcing james@towardex.com Boston-based Colocation & Bandwidth Services cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net From owner-freebsd-net@FreeBSD.ORG Thu Mar 4 10:37: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 300A616A4CE for ; Thu, 4 Mar 2004 10:37:38 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D121343D2F for ; Thu, 4 Mar 2004 10:37:37 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.10/8.12.10) with ESMTP id i24IaKDL051645; Thu, 4 Mar 2004 13:36:20 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i24IaCOR051638; Thu, 4 Mar 2004 13:36:20 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Thu, 4 Mar 2004 13:36:12 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Juan Rodriguez Hervella In-Reply-To: <200403041022.04338.jrh@it.uc3m.es> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: openVPN question 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, 04 Mar 2004 18:37:38 -0000 On Thu, 4 Mar 2004, Juan Rodriguez Hervella wrote: > An James Yonan said: > > Ah, yes, that's a problem. > > > > The --redirect-gateway implementation needs to be able to get the IP address > > of the current default gateway. Unfortunately the standard Berkeley sockets > > API doesn't give us a portable way of doing this. Anyone know how to > > do this on FreeBSD? > > So ? :) Take a look at the implementation of 'route get default' in src/sbin/route/route.c. Basically, you ask the routing socket for the route to 0.0.0.0/0.0.0.0 (INADDR_ANY). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research From owner-freebsd-net@FreeBSD.ORG Thu Mar 4 10:51: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 5D7AE16A4CE for ; Thu, 4 Mar 2004 10:51:58 -0800 (PST) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3A0D43D39 for ; Thu, 4 Mar 2004 10:51:55 -0800 (PST) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id D076F1FFDC1; Thu, 4 Mar 2004 19:51:53 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id E3CC61FFDBC; Thu, 4 Mar 2004 19:51:51 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id A8684154F9; Thu, 4 Mar 2004 18:51:41 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id A54FB154C7; Thu, 4 Mar 2004 18:51:41 +0000 (UTC) Date: Thu, 4 Mar 2004 18:51:41 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: James In-Reply-To: <20040304172529.GA86502@scylla.towardex.com> Message-ID: References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040303181034.GA58284@scylla.towardex.com> <20040304172529.GA86502@scylla.towardex.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 04 Mar 2004 18:51:58 -0000 On Thu, 4 Mar 2004, James wrote: > > J> why inject as_path info from userland to kernel "fib"? may be netflow turning > > J> into an api that quagga can take advantage of to gather accounting information > > J> is more feasible? > > > > James, can you please describe your idea more understandible? I can't understand > > your last sentence, sorry. > > sorry, i wasn't writing clearly :) > > what i meant is, an implementation of an API for netflow gathering > stats from the kernel. once you have that API, perhaps quagga can take > advantage of that API, to support netflow accounting by itself, along > with as path information and all that.. quagga is _routing_ software. _accounting_ software is s.th. else. What you want is an interface from quagga and s.th. like ng_netflow or whatever it is called exactly(search the arhive) and a small piece of software that merges information gathered from both called an accounting daemon. PS: I have cut down the Cc: (also removed current@) -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT 56 69 73 69 74 http://www.zabbadoz.net/ From owner-freebsd-net@FreeBSD.ORG Thu Mar 4 15:24: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 5F15816A4CE for ; Thu, 4 Mar 2004 15:24:54 -0800 (PST) Received: from bragi.housing.ufl.edu (bragi.housing.ufl.edu [128.227.47.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id D79F043D3F for ; Thu, 4 Mar 2004 15:24:53 -0800 (PST) (envelope-from WillS@housing.ufl.edu) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Thu, 4 Mar 2004 18:24:52 -0500 Message-ID: <0E972CEE334BFE4291CD07E056C76ED8CBBE80@bragi.housing.ufl.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: netgraph question Thread-Index: AcQCP+VXaSq3s66gSLej0zI1VnZpuw== From: "Will Saxon" To: Subject: netgraph question 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, 04 Mar 2004 23:24:54 -0000 Is it possible to force a name onto an unnamed node? I would like to use = ng_vlan together with ng_fec, but since ng_fec does not seem to provide = any hooks I thought I could create an ng_ether node and use that. = However, the ng_ether node cannot capture the name 'fec0' since it is = already in use by the fec node itself. I have been able to create a round robin channel with vlans using = ng_one2many, but I would like to use etherchannel since at least some of = my switches support the fec implementation. A somewhat related question - does anyone know what the = "Cisco-proprietary hashing algorithm" is for the etherchannel = implementation on new Catalyst devices? Their documentation suggests = that they aren't doing an XOR on the last 2 bits of the MAC addresses = anymore.=20 -Will _____________________________________________ Will Saxon Systems Programmer - Network Services Department of Housing and Residence Education University of Florida Email: wills@housing.ufl.edu Phone: (352) 392-2171 x10148 From owner-freebsd-net@FreeBSD.ORG Fri Mar 5 06:06: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 8052016A4CE; Fri, 5 Mar 2004 06:06:17 -0800 (PST) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91B9143D46; Fri, 5 Mar 2004 06:06:16 -0800 (PST) (envelope-from glebius@cell.sick.ru) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.9/8.12.8) with ESMTP id i25E6DQE049852 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Mar 2004 17:06:14 +0300 (MSK) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.9/8.12.6/Submit) id i25E62Ql049851; Fri, 5 Mar 2004 17:06:02 +0300 (MSK) Date: Fri, 5 Mar 2004 17:06:02 +0300 From: Gleb Smirnoff To: James Message-ID: <20040305140602.GB49148@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , James , Wes Peters , freebsd-current@freebsd.org, Andre Oppermann , freebsd-net@freebsd.org References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040303181034.GA58284@scylla.towardex.com> <20040304131000.GA41474@cell.sick.ru> <20040304172529.GA86502@scylla.towardex.com> <20040304172651.GA86659@scylla.towardex.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20040304172651.GA86659@scylla.towardex.com> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org cc: Andre Oppermann cc: freebsd-net@freebsd.org Subject: Re: My planned work on networking stack 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, 05 Mar 2004 14:06:17 -0000 On Thu, Mar 04, 2004 at 12:26:51PM -0500, James wrote: J> > that was my thought initially, BUT.. actually... you can J> > actually do this no problem using mrtd dumps and pick it up with a J> > program via bgp device :P no need to create another api it seems :) J> J> errr??? I meant bpf device... Implementing traffic accounting like ip accounting or netflow through a bpf is generally a bad idea, because of poor performance of such a solution. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Fri Mar 5 06:22: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 5A3B916A4CF for ; Fri, 5 Mar 2004 06:22:23 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DF0C43D45 for ; Fri, 5 Mar 2004 06:22:22 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 93242 invoked from network); 5 Mar 2004 14:22:20 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 5 Mar 2004 14:22:20 -0000 Message-ID: <40488D18.89A72F34@freebsd.org> Date: Fri, 05 Mar 2004 15:22:16 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Gleb Smirnoff References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040303181034.GA58284@scylla.towardex.com> <20040304131000.GA41474@cell.sick.ru> <20040304172529.GA86502@scylla.towardex.com> <20040304172651.GA86659@scylla.towardex.com> <20040305140602.GB49148@cell.sick.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: James Subject: Re: My planned work on networking stack 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, 05 Mar 2004 14:22:23 -0000 Gleb Smirnoff wrote: > > On Thu, Mar 04, 2004 at 12:26:51PM -0500, James wrote: > J> > that was my thought initially, BUT.. actually... you can > J> > actually do this no problem using mrtd dumps and pick it up with a > J> > program via bgp device :P no need to create another api it seems :) > J> > J> errr??? I meant bpf device... > > Implementing traffic accounting like ip accounting or netflow through > a bpf is generally a bad idea, because of poor performance of such a solution. This is not the case. While common wisdom does indeed suggest that BPF is slow it is in fact not the case. We have a netflow-like per AS-number traffic accounting daemon which takes only 2-3% of the CPU on our core routers. We are currently preparing that software package for public release. -- Andre From owner-freebsd-net@FreeBSD.ORG Fri Mar 5 13:31: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 1686816A4CF for ; Fri, 5 Mar 2004 13:31:42 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 381D943D2D for ; Fri, 5 Mar 2004 13:31:41 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 43774 invoked from network); 5 Mar 2004 21:31:40 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 5 Mar 2004 21:31:40 -0000 Message-ID: <4048F1B7.934AAC89@freebsd.org> Date: Fri, 05 Mar 2004 22:31:35 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: James , freebsd-current@freebsd.org, freebsd-net@freebsd.org References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru><404653DB.186DA0C2@freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: My planned work on networking stack 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, 05 Mar 2004 21:31:42 -0000 Andre Oppermann wrote: > > > there are still other things freebsd lacks. such as uRPF that _SERVICE_PROVIDER_ > > can use. ipfw2 has verrevpath but all it does from what i know is strict uRPF > > only. service providers like myself, if we were to use freebsd boxen to run our > > network, i am not spending money on a router that doesn't do loose-check uRPF. > > this sounds like something linux does too but i refuse to use that :P > > That is pretty easy to implement. I should have it by Friday at latest, > depends on when exactly I find time for it. > > ip verify unicast source reachable-via [any|ifn] > > The ipfw2 command would look like this: ... versrcreach [fxp0] Here you go: http://www.nrg4u.com/freebsd/ipfw_versrcreach.diff This one implements the standard functionality, the definition of an interface through which it has to be reachable is not (yet) supported. Using this option only makes sense when you don't have a default route which naturally always matches. So this is useful for machines acting as routers with a default-free view of the entire Internet as common when running a BGP daemon (Zebra/Quagga or OpenBSD bgpd). One useful way of enabling it globally on a router looks like this: ipfw add xxxx deny ip from any to any not versrcreach or for an individual interface only: ipfw add xxxx deny ip from any to any not versrcreach recv fxp0 I'd like to get some feedback (and a man page draft) before I commit it to -CURRENT. -- Andre From owner-freebsd-net@FreeBSD.ORG Fri Mar 5 16:40:10 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF84516A4CE; Fri, 5 Mar 2004 16:40:10 -0800 (PST) Received: from mta1.lbl.gov (mta1.lbl.gov [128.3.41.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBED043D1D; Fri, 5 Mar 2004 16:40:10 -0800 (PST) (envelope-from j_guojun@lbl.gov) Received: from mta1.lbl.gov (localhost [127.0.0.1]) by mta1.lbl.gov (8.12.10/8.12.10) with ESMTP id i260e6wd017372; Fri, 5 Mar 2004 16:40:08 -0800 (PST) Received: from lbl.gov (gracie.lbl.gov [131.243.2.175]) by mta1.lbl.gov (8.12.10/8.12.10) with ESMTP id i260e6am017369; Fri, 5 Mar 2004 16:40:06 -0800 (PST) Sender: jin@lbl.gov Message-ID: <40491DE2.1EB7707E@lbl.gov> Date: Fri, 05 Mar 2004 16:40:02 -0800 From: "Jin Guojun [DSD]" X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.9-RELEASE i386) X-Accept-Language: zh, zh-CN, en MIME-Version: 1.0 To: bugs@freebds.org, performance@freebsd.org, net@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: sender side Sbuf/Mbuf patch for 5.2.x is ready X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2004 00:40:11 -0000 The sender side patch for fixing Sbuf/Mbuf can be found at: http://dsd.lbl.gov/~jin/network/lion/patches/smbuf.patch.tbz Patch is for both 4.x and 5.2.x. To apply patch: bzip2 -d < smbuf.patch.tbz | tar -xf - cd net-lion ./restore-src backup # backup files will be modified to ???.org # patch will also backup them to ???.orig # so this is not necessary unless you need to modify them further ./netlion.kp # apply patches For more information about this patch, please refer to: http://dsd.lbl.gov/~jin/network/lion/content.html and http://dsd.lbl.gov/~jin/network/lion/content.html#FreeBSD_Patches Hopefully, we can make this into 5.3-RELEASE. Please test and verify it. Patches are in net-lion/FBSD-$R/mbuf.sb directory. -- ------------ Jin Guojun ----------- v --- j_guojun@lbl.gov --- Distributed Systems Department http://www.itg.lbl.gov/~jin M/S 50B-2239 Ph#:(510) 486-7531 Fax: 486-6363 Lawrence Berkeley National Laboratory, Berkeley, CA 94720 From owner-freebsd-net@FreeBSD.ORG Fri Mar 5 17:49:52 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3CA716A4CE for ; Fri, 5 Mar 2004 17:49:52 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA31143D3F for ; Fri, 5 Mar 2004 17:49:51 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 55112 invoked from network); 6 Mar 2004 01:49:51 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.54]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 6 Mar 2004 01:49:51 -0000 Message-ID: <40492E39.1B0D0C7B@freebsd.org> Date: Sat, 06 Mar 2004 02:49:45 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "Jin Guojun [DSD]" References: <40491DE2.1EB7707E@lbl.gov> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: performance@freebsd.org cc: net@freebsd.org Subject: Re: sender side Sbuf/Mbuf patch for 5.2.x is ready X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2004 01:49:52 -0000 "Jin Guojun [DSD]" wrote: > > The sender side patch for fixing Sbuf/Mbuf can be found at: > > http://dsd.lbl.gov/~jin/network/lion/patches/smbuf.patch.tbz > > Patch is for both 4.x and 5.2.x. To apply patch: ... > For more information about this patch, please refer to: > > http://dsd.lbl.gov/~jin/network/lion/content.html > and > http://dsd.lbl.gov/~jin/network/lion/content.html#FreeBSD_Patches > > Hopefully, we can make this into 5.3-RELEASE. > Please test and verify it. I've just looked through your website and the patch and have a couple of comments. The bottleneck you have identified and measured looks interesting. What I'm missing is a more in-depth description of the problem and what exactly your Lion implementation does. From looking over the patch it seems to include and mix debugging routines, mbuf chain optimizations and references to lion_ functions which are stale. It is not clear what is doing what. If you want this to have any chance of being included you should separate that from each other and provide them in its own patchset preferrably as unified diff (diff -u). You also have to observe the style of the surrounding code more. We have a very strict style guide and patches to existing code must be written in the same way as the surrounding code. Two more things, you are talking about the mtu in your Note file. The MTU is not directly relevant for TCP transfers but the MSS is. The MSS is the maximum payload a TCP segment/packet can transport and is always much lower than the link/path MTU. You have the MSS in the tcpcb.maxseg variable. The other things is that I assume you do file transfers at high speed since an application is probably not capable of producing 1Gbit/s geniue date for transfer. Have you checked out sendfile(2) and tested that with high speed links? The advantage of sendfile is to save the copy from userland to kernel but instead it goes directly from disk-io to mbuf. -- Andre From owner-freebsd-net@FreeBSD.ORG Fri Mar 5 17:52:53 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F19516A4CE; Fri, 5 Mar 2004 17:52:53 -0800 (PST) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58E4243D1F; Fri, 5 Mar 2004 17:52:50 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (sccrmhc11) with ESMTP id <2004030601524901100hk95oe>; Sat, 6 Mar 2004 01:52:49 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id RAA16833; Fri, 5 Mar 2004 17:52:47 -0800 (PST) Date: Fri, 5 Mar 2004 17:52:46 -0800 (PST) From: Julian Elischer To: "Jin Guojun [DSD]" In-Reply-To: <40491DE2.1EB7707E@lbl.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: bugs@freebds.org cc: performance@freebsd.org cc: net@freebsd.org Subject: Re: sender side Sbuf/Mbuf patch for 5.2.x is ready X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2004 01:52:53 -0000 The patch for reducing time traversing queues is good.. I have some questions.. It look sas if you have alos included some parts of files and patches that are for other netLION changes.. what is the status of the other changes.. In particular, the comments mention SACK. Are you developing a robist SACK implimentation for FreeBSD? On Fri, 5 Mar 2004, Jin Guojun [DSD] wrote: > The sender side patch for fixing Sbuf/Mbuf can be found at: > > http://dsd.lbl.gov/~jin/network/lion/patches/smbuf.patch.tbz > > Patch is for both 4.x and 5.2.x. To apply patch: > > bzip2 -d < smbuf.patch.tbz | tar -xf - > cd net-lion > ./restore-src backup # backup files will be modified to ???.org > # patch will also backup them to > ???.orig > # so this is not necessary unless you > need to modify them further > > ./netlion.kp # apply patches > > For more information about this patch, please refer to: > > http://dsd.lbl.gov/~jin/network/lion/content.html > and > http://dsd.lbl.gov/~jin/network/lion/content.html#FreeBSD_Patches > > Hopefully, we can make this into 5.3-RELEASE. > Please test and verify it. > > Patches are in net-lion/FBSD-$R/mbuf.sb directory. > > -- > ------------ Jin Guojun ----------- v --- j_guojun@lbl.gov --- > Distributed Systems Department http://www.itg.lbl.gov/~jin > M/S 50B-2239 Ph#:(510) 486-7531 Fax: 486-6363 > Lawrence Berkeley National Laboratory, Berkeley, CA 94720 > > > > _______________________________________________ > 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 Mar 5 19:43:53 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5F5F16A4CE; Fri, 5 Mar 2004 19:43:53 -0800 (PST) Received: from adsl-63-198-35-122.dsl.snfc21.pacbell.net (adsl-63-198-35-122.dsl.snfc21.pacbell.net [63.198.35.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42EF643D31; Fri, 5 Mar 2004 19:43:53 -0800 (PST) (envelope-from j_guojun@lbl.gov) Received: from lbl.gov (localhost.pacbell.net [127.0.0.1]) ESMTP id i263j8CJ000424; Fri, 5 Mar 2004 19:45:08 -0800 (PST) (envelope-from j_guojun@lbl.gov) Sender: jin@adsl-63-198-35-122.dsl.snfc21.pacbell.net Message-ID: <40494944.576A29F9@lbl.gov> Date: Fri, 05 Mar 2004 19:45:08 -0800 From: "Jin Guojun [NCS]" X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.9-RELEASE i386) X-Accept-Language: zh, zh-CN, en-US, en MIME-Version: 1.0 To: Andre Oppermann References: <40491DE2.1EB7707E@lbl.gov> <40492E39.1B0D0C7B@freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: performance@freebsd.org cc: net@freebsd.org Subject: Re: sender side Sbuf/Mbuf patch for 5.2.x is ready X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2004 03:43:53 -0000 Andre Oppermann wrote: > "Jin Guojun [DSD]" wrote: > > > > The sender side patch for fixing Sbuf/Mbuf can be found at: > > > > http://dsd.lbl.gov/~jin/network/lion/patches/smbuf.patch.tbz > > > > Patch is for both 4.x and 5.2.x. To apply patch: > ... > > For more information about this patch, please refer to: > > > > http://dsd.lbl.gov/~jin/network/lion/content.html > > and > > http://dsd.lbl.gov/~jin/network/lion/content.html#FreeBSD_Patches > > > > Hopefully, we can make this into 5.3-RELEASE. > > Please test and verify it. > > I've just looked through your website and the patch and have a couple of > comments. The bottleneck you have identified and measured looks interesting. > What I'm missing is a more in-depth description of the problem and what > exactly your Lion implementation does. From looking over the patch it > seems to include and mix debugging routines, mbuf chain optimizations > and references to lion_ functions which are stale. It is not clear what > is doing what. If you want this to have any chance of being included > you should separate that from each other and provide them in its own > patchset preferrably as unified diff (diff -u). You also have to observe > the style of the surrounding code more. We have a very strict style guide > and patches to existing code must be written in the same way as the > surrounding code. It looks like that you did not read the email closely. Only very short and clear patches are for SBuf/Mbuf in mbuf.sb/ directory. Do not look into other directories which are for LION project, not for TCP. LION is not for TCP/IP. LION is totally different network architecture, but it contains backward compatibility for TCP. That is why there is some code there for this purpose. So, do not be confused. > > Two more things, you are talking about the mtu in your Note file. The > MTU is not directly relevant for TCP transfers but the MSS is. The MSS > is the maximum payload a TCP segment/packet can transport and is always > much lower than the link/path MTU. You have the MSS in the tcpcb.maxseg > variable. The Note is "For future development:" for LION which has nothing to do with TCP. So there is no MSS or tcpcb.maxseg etc. > > The other things is that I assume you do file transfers at high speed > since an application is probably not capable of producing 1Gbit/s geniue > date for transfer. Have you checked out sendfile(2) and tested that with > high speed links? The advantage of sendfile is to save the copy from > userland to kernel but instead it goes directly from disk-io to mbuf. A few things are concerned here. (1) generic I/O for applications. New network architecture has to consider applications that still read//write. (2) computational data may not be on disk but in memory. Scientific programmers may not know mmap. (3) 1 Gbits/s is past. New goal is 100Gbits/s or 1Tbits/s in 200 ms RTT, and wireless networks. -Jin From owner-freebsd-net@FreeBSD.ORG Fri Mar 5 20: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 E38D716A4CE; Fri, 5 Mar 2004 20:23:39 -0800 (PST) Received: from adsl-63-198-35-122.dsl.snfc21.pacbell.net (adsl-63-198-35-122.dsl.snfc21.pacbell.net [63.198.35.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9926643D2D; Fri, 5 Mar 2004 20:23:39 -0800 (PST) (envelope-from j_guojun@lbl.gov) Received: from lbl.gov (localhost.pacbell.net [127.0.0.1]) ESMTP id i264OiCJ000465; Fri, 5 Mar 2004 20:24:47 -0800 (PST) (envelope-from j_guojun@lbl.gov) Sender: jin@adsl-63-198-35-122.dsl.snfc21.pacbell.net Message-ID: <4049528C.AA691FAF@lbl.gov> Date: Fri, 05 Mar 2004 20:24:44 -0800 From: "Jin Guojun [NCS]" X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.9-RELEASE i386) X-Accept-Language: zh, zh-CN, en-US, en MIME-Version: 1.0 To: Julian Elischer References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: bugs@freebsd.org cc: performance@freebsd.org cc: net@freebsd.org Subject: Re: sender side Sbuf/Mbuf patch for 5.2.x is ready X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2004 04:23:40 -0000 The Network LION (aka LION, Net-Lion) is a totally different network architecture that we proposed to replace TCP/IP. It has compatibility to TCP/IP for current stage. Backward compatibility is important to it can be deployed without forcing every one do at the same time, which is impossible to do. The goal is to move L3 on board, and leave L4 in system, so we can use PC to drive NICs as fast as possible. LION has been tested cross some Internet paths, and will be tested over emulation lab. Over emulation network (10 Gb/s), we can manipulate different network situations in order to verify Lion will fit in future network without causing network collapse. I hope that Lion will be soon ready for generic test, that is why I put all TCP/LION API code in FBSD-5/netlion directory, which is not part of the standard TCP patch for fixing SockBuf and Mbuf issues (someone was confused by this -- It is not in FBSD-4/ directory). This is for people who may be interested in using Lion. People may take look the code in advance to understand what these patches do because Lion will be provide as a kernel loadable module till it is matured. This means Lion is BSD only at this moment. In LION architecture, all lost packets will be reported to sender via some mechanism. In TCP backward compatible code (called TCP Lion -- not Network Lion), a better SACK will be implemented. Also notice that TCP Lion can be sender modification only. That is, remote site may run Linux/Solaris/Any TCP. Lion architecture must accommodate such case and be robust. -Jin Julian Elischer wrote: > The patch for reducing time traversing queues is good.. > I have some questions.. > > It look sas if you have alos included some parts of files and patches > that are for other netLION changes.. what is the status of the other > changes.. In particular, the comments mention SACK. Are you developing a > robist SACK implimentation for FreeBSD? > > On Fri, 5 Mar 2004, Jin Guojun [DSD] wrote: > > > The sender side patch for fixing Sbuf/Mbuf can be found at: > > > > http://dsd.lbl.gov/~jin/network/lion/patches/smbuf.patch.tbz > > > > Patch is for both 4.x and 5.2.x. To apply patch: > > > > bzip2 -d < smbuf.patch.tbz | tar -xf - > > cd net-lion > > ./restore-src backup # backup files will be modified to ???.org > > # patch will also backup them to > > ???.orig > > # so this is not necessary unless you > > need to modify them further > > > > ./netlion.kp # apply patches > > > > For more information about this patch, please refer to: > > > > http://dsd.lbl.gov/~jin/network/lion/content.html > > and > > http://dsd.lbl.gov/~jin/network/lion/content.html#FreeBSD_Patches > > > > Hopefully, we can make this into 5.3-RELEASE. > > Please test and verify it. > > > > Patches are in net-lion/FBSD-$R/mbuf.sb directory. > > > > -- > > ------------ Jin Guojun ----------- v --- j_guojun@lbl.gov --- > > Distributed Systems Department http://www.itg.lbl.gov/~jin > > M/S 50B-2239 Ph#:(510) 486-7531 Fax: 486-6363 > > Lawrence Berkeley National Laboratory, Berkeley, CA 94720 From owner-freebsd-net@FreeBSD.ORG Fri Mar 5 20:39:08 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A220216A4CE for ; Fri, 5 Mar 2004 20:39:08 -0800 (PST) Received: from babyruth.hotpop.com (babyruth.hotpop.com [38.113.3.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5586A43D2F for ; Fri, 5 Mar 2004 20:39:08 -0800 (PST) (envelope-from do-not-reply@hotpop.com) Received: from hotpop.com (kubrick.hotpop.com [38.113.3.103]) by babyruth.hotpop.com (Postfix) with SMTP id 74989150512 for ; Sat, 6 Mar 2004 04:30:43 +0000 (UTC) To: net@freebsd.org From: HotPOP Message-Id: <20040306043043.74989150512@babyruth.hotpop.com> Date: Sat, 6 Mar 2004 04:30:43 +0000 (UTC) Subject: Please confirm your HotPOP Forwarding 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: Sat, 06 Mar 2004 04:39:08 -0000 DO NOT REPLY TO THIS MESSAGE Someone (hopefully you) has recently requested that all mail sent to sukenwoo@HotPOP.com be forwarded to this address (net@freebsd.org). If you wish to authorize this, please click on the link below, or copy and paste it into your web browser. http://www.hotpop.com/confirmforward?USERADDR=sukenwoo@HotPOP.com&ADDRESS=net@freebsd.org&AUTH=S9V5B7X5P1M5N9B6 If the link above does not work, you can also authorize this address by typing the following code into the "Mail Forwarding" page in your HotPOP account setup page. Authorization Code: S9V5B7X5P1M5N9B6 No mail will be forwarded until authorization is complete. If you do not wish to authorize this, please ignore this message. Thank you, The HotPOP Team From owner-freebsd-net@FreeBSD.ORG Sat Mar 6 00:21:41 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 63DF416A4CE; Sat, 6 Mar 2004 00:21:41 -0800 (PST) Received: from silver.he.iki.fi (helenius.fi [193.64.42.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D1AE43D45; Sat, 6 Mar 2004 00:21:40 -0800 (PST) (envelope-from pete@he.iki.fi) Received: from he.iki.fi (helenius.fi [193.64.42.241]) by silver.he.iki.fi (8.12.10/8.11.4) with ESMTP id i268LSeU097898; Sat, 6 Mar 2004 10:21:30 +0200 (EET) (envelope-from pete@he.iki.fi) Message-ID: <40498A08.2040606@he.iki.fi> Date: Sat, 06 Mar 2004 10:21:28 +0200 From: Petri Helenius User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6b) Gecko/20040228 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andre Oppermann References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040303181034.GA58284@scylla.towardex.com> <404653DB.186DA0C2@freebsd.org> In-Reply-To: <404653DB.186DA0C2@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: James Subject: Re: My planned work on networking stack X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2004 08:21:41 -0000 Andre Oppermann wrote: > > >What else is missing in FreeBSD? > > > Cannot resist.... MPLS? 1/2 :-) Pete From owner-freebsd-net@FreeBSD.ORG Sat Mar 6 11:05: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 4316D16A4CE for ; Sat, 6 Mar 2004 11:05:55 -0800 (PST) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6B3F43D1D for ; Sat, 6 Mar 2004 11:05:54 -0800 (PST) (envelope-from scrappy@hub.org) Received: by ganymede.hub.org (Postfix, from userid 1000) id DB96234592; Sat, 6 Mar 2004 15:05:54 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id DA88F34517 for ; Sat, 6 Mar 2004 15:05:54 -0400 (AST) Date: Sat, 6 Mar 2004 15:05:54 -0400 (AST) From: "Marc G. Fournier" To: freebsd-net@freebsd.org Message-ID: <20040306150504.Q13247@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Odd network issue ... *very* slow scp between two servers X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2004 19:05:55 -0000 I have two servers on the same network switch, sitting one on top of the other ... one is running an em (Dual-Xeon 2.4Ghz) device, the other an fxp (Dual-PIII 1.3Ghz) device ... Doing a straight (not sftp/scp) ftp between the two servers, of a 1Meg file, shows: 1038785 bytes received in 85.91 seconds (11.81 KB/s) Going between two servers, same switch, both running fxp devices, for the exact same file, shows: 1038785 bytes received in 0.09 seconds (10.64 MB/s) Now, I have ipaudit running on all the servers, to monitor bandwidth ... the server with the fxp device on it, that I just downloaded to from another fxp server @ 10.64MB/s, did 11535.73M of traffic total yesterday ... the one with the em device did 11766.46M ... Now, in my /var/log/messages file, I am getting the RST lines: Mar 6 12:35:38 neptune /kernel: Limiting open port RST response from 700 to 200 packets per second Mar 6 12:35:39 neptune /kernel: Limiting open port RST response from 636 to 200 packets per second Mar 6 12:35:41 neptune /kernel: Limiting open port RST response from 523 to 200 packets per second Mar 6 12:35:46 neptune /kernel: Limiting open port RST response from 386 to 200 packets per second Mar 6 12:35:55 neptune /kernel: Limiting open port RST response from 238 to 200 packets per second Mar 6 13:34:25 neptune /kernel: Limiting open port RST response from 799 to 200 packets per second Mar 6 13:34:27 neptune /kernel: Limiting open port RST response from 637 to 200 packets per second Mar 6 13:34:28 neptune /kernel: Limiting open port RST response from 503 to 200 packets per second Mar 6 13:34:32 neptune /kernel: Limiting open port RST response from 343 to 200 packets per second Mar 6 13:34:42 neptune /kernel: Limiting open port RST response from 206 to 200 packets per second And seems to be quite regular: neptune# gzcat /var/log/messages.0.gz | grep RST | wc -l 95 where 0.gz is from Mar 5 14:47:28 -> Mar 6 11:30:52 but, shouldn't: net.inet.tcp.blackhole: 0 -> 2 help? or did I read the man page wrong? If it should, I'm still only getting ~13k/s on that same file ... there is nothing else in messages to indicate a problem, either with processes, or drives, or anything, and load on the machine, right now, is only 1.3 ... vmstat -i shows a high rate of interrupts for the em device: neptune# uptime 1:43PM up 57 days, 3:08, 5 users, load averages: 1.38, 1.32, 0.97 neptune# vmstat -i interrupt total rate ahd0 irq16 15 0 ahd1 irq17 932228686 188 em0 irq18 1205773331 244 clk irq0 493596903 99 rtc irq8 631819522 128 Total 3263418457 661 vs mars# uptime 1:43PM up 77 days, 9:50, 3 users, load averages: 7.44, 7.73, 6.28 mars# vmstat -i interrupt total rate fxp0 irq5 499794285 74 ahc0 irq11 15 0 ahc1 irq15 915710622 136 fdc0 irq6 4 0 clk irq0 668800403 99 rtc irq8 856196939 128 Total 2940502268 439 the fxp device is running: media: Ethernet autoselect (100baseTX ) the em device is running: media: Ethernet 100baseTX and, finally, the em server was last upgraded: 4.9-STABLE #4: Tue Jan 6 00:59:37 AST 2004 while the fxp server is almost ancient: 4.9-PRERELEASE #2: Sat Sep 20 14:42:25 ADT 2003 I'm going to do a reboot on the server Monday, when a tech is easily accessible in case of a problem ... but, before I do that, is there anything I can do to possible debug this? Maybe something I can look at that would show a 'leak', maybe? Thanks ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-net@FreeBSD.ORG Sat Mar 6 13:05: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 5EAAE16A4CE; Sat, 6 Mar 2004 13:05:44 -0800 (PST) Received: from mx01.bos.ma.towardex.com (a65-124-16-8.svc.towardex.com [65.124.16.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CFF843D2F; Sat, 6 Mar 2004 13:05:22 -0800 (PST) (envelope-from haesu@mx01.bos.ma.towardex.com) Received: by mx01.bos.ma.towardex.com (TowardEX ESMTP 3.0p11_DAKN, from userid 1001) id 7A7752F8F9; Sat, 6 Mar 2004 16:05:23 -0500 (EST) Date: Sat, 6 Mar 2004 16:05:23 -0500 From: James To: Andre Oppermann Message-ID: <20040306210523.GA10214@scylla.towardex.com> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040303181034.GA58284@scylla.towardex.com> <404653DB.186DA0C2@freebsd.org> <4048F1B7.934AAC89@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4048F1B7.934AAC89@freebsd.org> User-Agent: Mutt/1.4.1i cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: James Subject: Re: My planned work on networking stack X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2004 21:05:44 -0000 thank you! :) i'll try this sometime next week and let you know of any feedbacks i have. -J > > Here you go: > > http://www.nrg4u.com/freebsd/ipfw_versrcreach.diff > > This one implements the standard functionality, the definition of an > interface through which it has to be reachable is not (yet) supported. > > Using this option only makes sense when you don't have a default route > which naturally always matches. So this is useful for machines acting > as routers with a default-free view of the entire Internet as common > when running a BGP daemon (Zebra/Quagga or OpenBSD bgpd). > > One useful way of enabling it globally on a router looks like this: > > ipfw add xxxx deny ip from any to any not versrcreach > > or for an individual interface only: > > ipfw add xxxx deny ip from any to any not versrcreach recv fxp0 > > I'd like to get some feedback (and a man page draft) before I commit it > to -CURRENT. > > -- > Andre -- James Jun TowardEX Technologies, Inc. Technical Lead Network Design, Consulting, IT Outsourcing james@towardex.com Boston-based Colocation & Bandwidth Services cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net From owner-freebsd-net@FreeBSD.ORG Sat Mar 6 14:14: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 531ED16A4CE for ; Sat, 6 Mar 2004 14:14:00 -0800 (PST) Received: from web41813.mail.yahoo.com (web41813.mail.yahoo.com [66.218.93.147]) by mx1.FreeBSD.org (Postfix) with SMTP id 35D5043D4C for ; Sat, 6 Mar 2004 14:13:58 -0800 (PST) (envelope-from youknicks@yahoo.com) Message-ID: <20040306221357.68128.qmail@web41813.mail.yahoo.com> Received: from [24.6.220.149] by web41813.mail.yahoo.com via HTTP; Sat, 06 Mar 2004 14:13:57 PST Date: Sat, 6 Mar 2004 14:13:57 -0800 (PST) From: Jerry Jensen To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: multiple logical interfaces X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2004 22:14:00 -0000 is it possible in freebsd to have multiple logical interfaces associated with say the loopback interface? if so, how does one do this programmatically (as opposed to from the command line). need this for building traffic generators that need to simulate a bunch of different ip sources. solaris allows it as does linux i believe. thx. __________________________________ Do you Yahoo!? Yahoo! Search - Find what you’re looking for faster http://search.yahoo.com From owner-freebsd-net@FreeBSD.ORG Sat Mar 6 14:35:14 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94E4416A4CE for ; Sat, 6 Mar 2004 14:35:14 -0800 (PST) Received: from manganese.bos.dyndns.org (manganese.bos.dyndns.org [63.208.196.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2911243D2D for ; Sat, 6 Mar 2004 14:35:14 -0800 (PST) (envelope-from twilde@dyndns.org) Received: from manganese.bos.dyndns.org (twilde@localhost [127.0.0.1]) i26MZDPn013885; Sat, 6 Mar 2004 17:35:13 -0500 (EST) (envelope-from twilde@dyndns.org) Received: from localhost (twilde@localhost)i26MZCFw013882; Sat, 6 Mar 2004 17:35:13 -0500 (EST) X-Authentication-Warning: manganese.bos.dyndns.org: twilde owned process doing -bs Date: Sat, 6 Mar 2004 17:35:12 -0500 (EST) From: Tim Wilde X-X-Sender: twilde@manganese.bos.dyndns.org To: "Marc G. Fournier" In-Reply-To: <20040306150504.Q13247@ganymede.hub.org> Message-ID: References: <20040306150504.Q13247@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: -4.9 () BAYES_00 X-Scanned-By: MIMEDefang 2.39 cc: freebsd-net@freebsd.org Subject: Re: Odd network issue ... *very* slow scp between two servers X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2004 22:35:14 -0000 On Sat, 6 Mar 2004, Marc G. Fournier wrote: > I have two servers on the same network switch, sitting one on top of the > other ... one is running an em (Dual-Xeon 2.4Ghz) device, the other an fxp > (Dual-PIII 1.3Ghz) device ... Is it a Cisco Catalyst switch? If so, you need to switch the em's to autoselect, on both the server and switch end. For some reason, the em driver will not properly lock down its rate when talking to a Cisco Catalyst switch. At least, I had an identical problem with em's talking to a Catalyst 2950 and that was the fix I came up with. Give it a try and see how your results go. Tim Wilde -- Tim Wilde twilde@dyndns.org Systems Administrator Dynamic Network Services, Inc. http://www.dyndns.org/ From owner-freebsd-net@FreeBSD.ORG Sat Mar 6 19:47:41 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 5B5BC16A4CE for ; Sat, 6 Mar 2004 19:47:41 -0800 (PST) Received: from ints.mail.pike.ru (ints.mail.pike.ru [195.9.45.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75E3B43D1D for ; Sat, 6 Mar 2004 19:47:40 -0800 (PST) (envelope-from babolo@cicuta.babolo.ru) Received: (qmail 84057 invoked from network); 7 Mar 2004 04:04:57 -0000 Received: from babolo.ru (HELO cicuta.babolo.ru) (194.58.226.160) by ints.mail.pike.ru with SMTP; 7 Mar 2004 04:04:57 -0000 Received: (nullmailer pid 16336 invoked by uid 136); Sun, 07 Mar 2004 03:48:40 -0000 X-ELM-OSV: (Our standard violations) hdr-charset=KOI8-R; no-hdr-encoding=1 In-Reply-To: <20040306221357.68128.qmail@web41813.mail.yahoo.com> To: Jerry Jensen Date: Sun, 7 Mar 2004 06:48:40 +0300 (MSK) From: "."@babolo.ru X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <1078631320.114327.16335.nullmailer@cicuta.babolo.ru> cc: freebsd-net@freebsd.org Subject: Re: multiple logical interfaces 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, 07 Mar 2004 03:47:41 -0000 > is it possible in freebsd to have multiple logical > interfaces associated with say the loopback interface? > if so, how does one do this programmatically (as > opposed to from the command line). > > need this for building traffic generators that need to > simulate a bunch of different ip sources. solaris > allows it as does linux i believe. > thx. Is it what you want? > ifconfig -a | grep lo lo0: flags=8049 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0xa lo1: flags=8049 mtu 16384 lo2: flags=8008 mtu 16384 lo3: flags=8008 mtu 16384 If it is, there is from kernel config: > grep loop /sys/i386/conf/garkin pseudo-device loop 4 # Network loopback From owner-freebsd-net@FreeBSD.ORG Sat Mar 6 22:06: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 5F0F816A4CE for ; Sat, 6 Mar 2004 22:06:35 -0800 (PST) Received: from web41802.mail.yahoo.com (web41802.mail.yahoo.com [66.218.93.136]) by mx1.FreeBSD.org (Postfix) with SMTP id 4FFF543D1F for ; Sat, 6 Mar 2004 22:06:35 -0800 (PST) (envelope-from youknicks@yahoo.com) Message-ID: <20040307060634.65073.qmail@web41802.mail.yahoo.com> Received: from [24.6.220.149] by web41802.mail.yahoo.com via HTTP; Sat, 06 Mar 2004 22:06:34 PST Date: Sat, 6 Mar 2004 22:06:34 -0800 (PST) From: Jerry Jensen To: "."@babolo.ru In-Reply-To: <1078631320.114327.16335.nullmailer@cicuta.babolo.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-net@freebsd.org Subject: Re: multiple logical interfaces 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, 07 Mar 2004 06:06:35 -0000 Actually, what I want is the equivalent of this (which is in Linux) on FreeBSD. Note the ip address associated with each of the logical interfaces (lo:XX). eth0 Link encap:Ethernet HWaddr 00:06:5B:19:55:EE inet addr:10.2.1.122 Bcast:10.255.255.255 Mask:255.0.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5903525 errors:0 dropped:0 overruns:0 frame:0 TX packets:5337692 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 Interrupt:16 Base address:0xecc0 Memory:fe2ff000-fe2ff038 eth1 Link encap:Ethernet HWaddr 00:06:5B:19:55:EF inet addr:192.168.6.122 Bcast:192.168.6.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1818518022 errors:2 dropped:0 overruns:263 frame:2 TX packets:1182175968 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 Interrupt:17 Base address:0xec80 Memory:fe2fe000-fe2fe038 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:199 errors:0 dropped:0 overruns:0 frame:0 TX packets:199 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 lo:10 Link encap:Local Loopback inet addr:202.175.33.10 Mask:255.255.255.255 UP LOOPBACK RUNNING MTU:16436 Metric:1 lo:11 Link encap:Local Loopback inet addr:193.65.100.99 Mask:255.255.255.255 UP LOOPBACK RUNNING MTU:16436 Metric:1 lo:12 Link encap:Local Loopback inet addr:193.65.100.100 Mask:255.255.255.255 UP LOOPBACK RUNNING MTU:16436 Metric:1 lo:13 Link encap:Local Loopback inet addr:210.183.28.42 Mask:255.255.255.255 UP LOOPBACK RUNNING MTU:16436 Metric:1 --- .@babolo.ru wrote: > > is it possible in freebsd to have multiple logical > > interfaces associated with say the loopback > interface? > > if so, how does one do this programmatically (as > > opposed to from the command line). > > > > need this for building traffic generators that > need to > > simulate a bunch of different ip sources. solaris > > allows it as does linux i believe. > > thx. > Is it what you want? > > > ifconfig -a | grep lo > lo0: flags=8049 mtu > 16384 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0xa > lo1: flags=8049 mtu > 16384 > lo2: flags=8008 mtu 16384 > lo3: flags=8008 mtu 16384 > > If it is, there is from kernel config: > > > grep loop /sys/i386/conf/garkin > pseudo-device loop 4 # Network loopback > > _______________________________________________ > 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! Search - Find what you’re looking for faster http://search.yahoo.com From owner-freebsd-net@FreeBSD.ORG Sat Mar 6 22:35: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 0880D16A4CE for ; Sat, 6 Mar 2004 22:35:06 -0800 (PST) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF14243D1F for ; Sat, 6 Mar 2004 22:35:04 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (sccrmhc13) with ESMTP id <2004030706350201600gjt39e>; Sun, 7 Mar 2004 06:35:03 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id WAA30310; Sat, 6 Mar 2004 22:35:00 -0800 (PST) Date: Sat, 6 Mar 2004 22:34:59 -0800 (PST) From: Julian Elischer To: Jerry Jensen In-Reply-To: <20040307060634.65073.qmail@web41802.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "."@babolo.ru cc: freebsd-net@freebsd.org Subject: Re: multiple logical interfaces 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, 07 Mar 2004 06:35:06 -0000 On Sat, 6 Mar 2004, Jerry Jensen wrote: > Actually, what I want is the equivalent of this (which > is in Linux) on FreeBSD. Note the ip address > associated with each of the logical interfaces > (lo:XX). how is this different from what was showed below? > > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:199 errors:0 dropped:0 overruns:0 > frame:0 > TX packets:199 errors:0 dropped:0 overruns:0 > carrier:0 > collisions:0 txqueuelen:0 > > lo:10 Link encap:Local Loopback > inet addr:202.175.33.10 > Mask:255.255.255.255 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > lo:11 Link encap:Local Loopback > inet addr:193.65.100.99 > Mask:255.255.255.255 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > lo:12 Link encap:Local Loopback > inet addr:193.65.100.100 > Mask:255.255.255.255 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > lo:13 Link encap:Local Loopback > inet addr:210.183.28.42 > Mask:255.255.255.255 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > --- .@babolo.ru wrote: > ifconfig -a | grep lo > lo0: flags=8049 mtu 16384 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0xa > lo1: flags=8049 mtu 16384 > lo2: flags=8008 mtu 16384 > lo3: flags=8008 mtu 16384 > From owner-freebsd-net@FreeBSD.ORG Sat Mar 6 22:48: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 6CAFA16A4CE for ; Sat, 6 Mar 2004 22:48:00 -0800 (PST) Received: from ints.mail.pike.ru (ints.mail.pike.ru [195.9.45.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A3D043D1F for ; Sat, 6 Mar 2004 22:47:59 -0800 (PST) (envelope-from babolo@cicuta.babolo.ru) Received: (qmail 86389 invoked from network); 7 Mar 2004 07:05:16 -0000 Received: from babolo.ru (HELO cicuta.babolo.ru) (194.58.226.160) by ints.mail.pike.ru with SMTP; 7 Mar 2004 07:05:16 -0000 Received: (nullmailer pid 16569 invoked by uid 136); Sun, 07 Mar 2004 06:48:58 -0000 X-ELM-OSV: (Our standard violations) hdr-charset=KOI8-R; no-hdr-encoding=1 In-Reply-To: <20040307060634.65073.qmail@web41802.mail.yahoo.com> To: Jerry Jensen Date: Sun, 7 Mar 2004 09:48:58 +0300 (MSK) From: "."@babolo.ru X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <1078642138.728121.16568.nullmailer@cicuta.babolo.ru> cc: freebsd-net@freebsd.org Subject: Re: multiple logical interfaces 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, 07 Mar 2004 06:48:00 -0000 > Actually, what I want is the equivalent of this (which > is in Linux) on FreeBSD. Note the ip address > associated with each of the logical interfaces > (lo:XX). And what? 0cicuta~(11)#ifconfig lo0 lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7 inet 127.0.0.1 netmask 0xffffff00 0cicuta~(12)#ifconfig lo1 lo1: flags=8049 mtu 16384 inet 127.0.1.1 netmask 0xffffff00 inet 127.0.1.2 netmask 0xffffffff 0cicuta~(13)#ifconfig lo2 lo2: flags=8008 mtu 16384 0cicuta~(14)#ifconfig lo3 lo3: flags=8008 mtu 16384 0cicuta~(15)#ifconfig lo3 192.168.0.1/24 0cicuta~(16)#ifconfig lo3 lo3: flags=8049 mtu 16384 inet 192.168.0.1 netmask 0xffffff00 The only disadvantage in 0cicuta~(17)#uname -a FreeBSD cicuta.babolo.ru 4.9-RC FreeBSD 4.9-RC #0: Fri Oct 10 11:37:45 MSD 2003 babolo@cicuta.babolo.ru:/tmp/babolo/usr/src/sys/cicuta i386 is that lo can't be created dynamically. One more quection: why not alias the lo0 ? > eth0 Link encap:Ethernet HWaddr > 00:06:5B:19:55:EE > inet addr:10.2.1.122 Bcast:10.255.255.255 > Mask:255.0.0.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 > Metric:1 > RX packets:5903525 errors:0 dropped:0 > overruns:0 frame:0 > TX packets:5337692 errors:0 dropped:0 > overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > Interrupt:16 Base address:0xecc0 > Memory:fe2ff000-fe2ff038 > > eth1 Link encap:Ethernet HWaddr > 00:06:5B:19:55:EF > inet addr:192.168.6.122 Bcast:192.168.6.255 > Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 > Metric:1 > RX packets:1818518022 errors:2 dropped:0 > overruns:263 frame:2 > TX packets:1182175968 errors:0 dropped:0 > overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > Interrupt:17 Base address:0xec80 > Memory:fe2fe000-fe2fe038 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:199 errors:0 dropped:0 overruns:0 > frame:0 > TX packets:199 errors:0 dropped:0 overruns:0 > carrier:0 > collisions:0 txqueuelen:0 > > lo:10 Link encap:Local Loopback > inet addr:202.175.33.10 > Mask:255.255.255.255 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > lo:11 Link encap:Local Loopback > inet addr:193.65.100.99 > Mask:255.255.255.255 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > lo:12 Link encap:Local Loopback > inet addr:193.65.100.100 > Mask:255.255.255.255 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > lo:13 Link encap:Local Loopback > inet addr:210.183.28.42 > Mask:255.255.255.255 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > --- .@babolo.ru wrote: > > > is it possible in freebsd to have multiple logical > > > interfaces associated with say the loopback > > interface? > > > if so, how does one do this programmatically (as > > > opposed to from the command line). > > > > > > need this for building traffic generators that > > need to > > > simulate a bunch of different ip sources. solaris > > > allows it as does linux i believe. > > > thx. > > Is it what you want? > > > > > ifconfig -a | grep lo > > lo0: flags=8049 mtu > > 16384 > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0xa > > lo1: flags=8049 mtu > > 16384 > > lo2: flags=8008 mtu 16384 > > lo3: flags=8008 mtu 16384 > > > > If it is, there is from kernel config: > > > > > grep loop /sys/i386/conf/garkin > > pseudo-device loop 4 # Network loopback > > > > _______________________________________________ > > 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! Search - Find what you?re looking for faster > http://search.yahoo.com >