From owner-freebsd-net@FreeBSD.ORG Sun Mar 7 07:09: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 753A516A4CE for ; Sun, 7 Mar 2004 07:09:03 -0800 (PST) Received: from ctb-mesg4.saix.net (ctb-mesg4.saix.net [196.25.240.76]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA7D943D1D for ; Sun, 7 Mar 2004 07:09:02 -0800 (PST) (envelope-from karnaugh@karnaugh.za.net) Received: from karnaugh.za.net (ndn-ip-nas-1-p196.telkom-ipnet.co.za [155.239.192.196]) by ctb-mesg4.saix.net (Postfix) with ESMTP id 78012AEB8; Sun, 7 Mar 2004 17:08:58 +0200 (SAST) Message-ID: <404B3B35.50602@karnaugh.za.net> Date: Sun, 07 Mar 2004 17:09:41 +0200 From: Colin Alston User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joost Bekkers References: <20040303114738.GA85522@bps.jodocus.org> <20040303041239.A11330@xorpc.icir.org> <20040304073658.GA3991@bps.jodocus.org> In-Reply-To: <20040304073658.GA3991@bps.jodocus.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Luigi Rizzo 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: Sun, 07 Mar 2004 15:09:03 -0000 Joost Bekkers wrote: >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 > > > man ip6fw >> HISTORY A ip6fw utility first appeared in FreeBSD 4.0. << Not that it really works... From owner-freebsd-net@FreeBSD.ORG Sun Mar 7 08:25: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 655BD16A4CE for ; Sun, 7 Mar 2004 08:25:06 -0800 (PST) Received: from isis.lip6.fr (isis.lip6.fr [132.227.60.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38CAC43D1D for ; Sun, 7 Mar 2004 08:25:05 -0800 (PST) (envelope-from Konstantin.Kabassanov@lip6.fr) Received: from tibre.lip6.fr (tibre.lip6.fr [132.227.74.2]) i27GP4lR012676 for ; Sun, 7 Mar 2004 17:25:04 +0100 X-pt: isis.lip6.fr Received: from gargamel (rp [132.227.74.3]) by tibre.lip6.fr (8.11.6p3/8.11.6) with ESMTP id i27GP3T26055 for ; Sun, 7 Mar 2004 17:25:03 +0100 (CET) From: "Konstantin KABASSANOV" To: Date: Sun, 7 Mar 2004 17:26:03 +0100 MIME-Version: 1.0 Message-ID: <005d01c40460$e2a210e0$8748e384@ipv6.lip6.fr> X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; boundary="----=_NextPart_000_0058_01C40469.43365D50"; micalg=SHA1 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-Scanned-By: isis.lip6.fr Subject: atheros driver in adhoc mode 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 16:25:06 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0058_01C40469.43365D50 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Hello, I'm actually trying to make some tests between 2 wireless cards supported by the atheros driver in Freebsd 5.2.1 release. Everything works fine except the adhoc mode. When I put both cards in adhoc mode, no packet is going out through the wireless interface even if the status of the interface is shown as "associated" and both cards have the same channel. Any hints? Thanks. _________________________________ Konstantin K. KABASSANOV LIP6/CNRS 8, rue du Capitaine Scott 75015 Paris, France Phone: +33 (0) 1 44 27 71 26 Fax: +33 (0) 1 44 27 74 95 E-mail: konstantin@kabassanov.com Web: http://www.kabassanov.com _________________________________ IMPORTANT! If you have tried to reply to this mail and you received a stupid message, announcing that the mail had been rejected as spam, please, resend your reply to the address above. ------=_NextPart_000_0058_01C40469.43365D50 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIILszCCA2Qw ggJMoAMCAQICAQAwDQYJKoZIhvcNAQEEBQAwKzELMAkGA1UEBhMCRlIxDTALBgNVBAoTBENOUlMx DTALBgNVBAMTBENOUlMwHhcNMDEwNDI3MDU0NDM2WhcNMjEwNDIyMDU0NDM2WjArMQswCQYDVQQG EwJGUjENMAsGA1UEChMEQ05SUzENMAsGA1UEAxMEQ05SUzCCASIwDQYJKoZIhvcNAQEBBQADggEP ADCCAQoCggEBAN13q/Hq/Hi1FKHcd2JWl4wvt1TCTFSm1H0iR3t0qffjrXxVshTwSF2YjwK9khG2 iE/EFfVvWFv3ibUn6q+g/KCOiIaPnyS2kE4k3GfQT49+Vi0bKAdysRdnoA7bQk7DfLQloviMBLGp gl2Mj9SDe+6qn9fS2/ZbbsKBENaaq12IHDbKBWRoS4uewFCUI/22KLWvXaTdpsXT2FcrPvi1usTY /xIiXyRpB2LkNEoId8owu+zT7XWQaKKMcXIn3hUmLCUhhCqeVxiBciO9Zh8P47e9F9oSuhlU9Bwt j3FSM7G2KLZ6aMuaTVI4+kiMwUuJlo/GF1vLuQ4OgVwaxzQ5V70CAwEAAaOBkjCBjzAMBgNVHRME BTADAQH/MB0GA1UdDgQWBBRW62i50lx+mLWlU8ORb2NYxPlrtzBTBgNVHSMETDBKgBRW62i50lx+ mLWlU8ORb2NYxPlrt6EvpC0wKzELMAkGA1UEBhMCRlIxDTALBgNVBAoTBENOUlMxDTALBgNVBAMT BENOUlOCAQAwCwYDVR0PBAQDAgEGMA0GCSqGSIb3DQEBBAUAA4IBAQA418MpvHp3ol4WR0mGXtAZ OGregQgCuaegAqaIuA3iSTXO5qqiNNL5o4Q3mhXpWSu3vcwRrikhj4+ROfqdd+LoOersLtbKSEci TGWx07ZvWBs0LooQnRKEdKR5UlcAUxTImN6BbsULdada59M1CEWI9YRQmPAHPsWGPi4JWqLctqBr ezernwNwbt31nMAOBey1hFsjtIkhEIit+y0I5AATHFWzj3e+IKzcARx5fGcMWl9PuZSJvquaLBKx qGPGYoAD/Uxwlb3G6AXay74Jph/pbdKFLkPTHxpcdv4TdmFg+WTUWHi/f+/lc6ND2ip/d9s0eXLZ juWl7VLQxEZMXxuqMIIDbTCCAlWgAwIBAgIBAjANBgkqhkiG9w0BAQQFADArMQswCQYDVQQGEwJG UjENMAsGA1UEChMEQ05SUzENMAsGA1UEAxMEQ05SUzAeFw0wMTA0MjcwNTQ2NDlaFw0xMTA0MjUw NTQ2NDlaMDQxCzAJBgNVBAYTAkZSMQ0wCwYDVQQKEwRDTlJTMRYwFAYDVQQDEw1DTlJTLVN0YW5k YXJkMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3OEeIT0Gi+q9XrSI2w+Tl7RtBz2G YgAtyv+1So7nVqSPYSzxoCqr9irdfCy/73VVC6wJTudOYcDnDPCQFUUSAsKM68MSZOJjEBguywcx 2YHl3CmCmzFW4oEeim+n6KlYEURWg12zTnhwLd+2/XKBRdXx7k3O777VPQyQIEWaCYCvD0zaIA6A vzqz6yeAwLkPwKFOQNw6/Woqv0DVLHGA+fi6a+TqKgCrL76a8Kd2bZgpnA8v8ELyGJdbyfbMGV+6 wr4S0lywkJTAt8sGBO+PMO0yLXpK95O7oAmktO4zy9CDm7W1s5DejpAeWZwg1Use7ddMT4b6HDoq oemsBaCdvwIDAQABo4GSMIGPMAwGA1UdEwQFMAMBAf8wHQYDVR0OBBYEFGdZpeUHdEkD7wXPzC6k GNUQyJ48MFMGA1UdIwRMMEqAFFbraLnSXH6YtaVTw5FvY1jE+Wu3oS+kLTArMQswCQYDVQQGEwJG UjENMAsGA1UEChMEQ05SUzENMAsGA1UEAxMEQ05SU4IBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcN AQEEBQADggEBAAYDR4NyRZDCTuEh16sXqQFVBspAbVWiHV7r4hQjWeQJ4pD2PI02Bg9LpyYjZcLq Bppyu7iMy4pf73k2JX4A1/MGlPuDRCkmN8fu6YfObIaAG3E90mKv9s1ibFMP5nqTAIx7LjPgQR2q vmWYdvGVB3Sz5j9TddVLBjZLKcT23I4TgEAQc4KtFXsEcVC1NzPyyGS7oRB+Nsatr29wUqbRrszM urDoWRKPYg2tA91LKuiJOYhRL+1h6Lcwh9snVW1mh6NRCYBhcVEFvhMd2UEw/HVfCpabGP++kIG0 E8ByEQj9appqB730gyy0YDZkB/o9aqewkAR2g90zyzTiF5gEC6EwggTWMIIDvqADAgECAgILQTAN BgkqhkiG9w0BAQQFADA0MQswCQYDVQQGEwJGUjENMAsGA1UEChMEQ05SUzEWMBQGA1UEAxMNQ05S Uy1TdGFuZGFyZDAeFw0wNDAxMDUxMjE4MzFaFw0wNTAxMDUxMjE4MzFaMHwxCzAJBgNVBAYTAkZS MQ0wCwYDVQQKEwRDTlJTMRAwDgYDVQQLEwdVTVI3NjA2MR4wHAYDVQQDExVLb25zdGFudGluIEth YmFzc2Fub3YxLDAqBgkqhkiG9w0BCQEWHUtvbnN0YW50aW4uS2FiYXNzYW5vdkBsaXA2LmZyMIIB IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzMyNgVgMXjrGwkogB8dH3FSBbwkqD6t1XmVV 55yDfdmf+YGsujHf1LYvF6fRCvgm81JufqeyLc3LSlgglXl5QeUOW37Ospp/iAdIh/ZURZiWA1RX imvqo9iTUvx2zUTwqIP8dRJye5bgYGBEJRCmE0TYMwSkmHSmTERpvoDNBNCFVGOrsZTOPYXtNsKf iAfNi7pFdfxE9Ij6/gQNM/0Q3RNiiXmO5IkHAlxgwwqHABx1Ld169HlSfoKAeq6KTsOECkOxAijj mQtgJs/eE5MtMST9IfqQkmhpt7intE2k2TrZ1tEo92pErYkNrNKhYqdM2/jMeGJsdvnlgUsa1HiI mQIDAQABo4IBqDCCAaQwDAYDVR0TAQH/BAIwADARBglghkgBhvhCAQEEBAMCBLAwDgYDVR0PAQH/ BAQDAgXgMHgGCWCGSAGG+EIBDQRrFmlDZXJ0aWZpY2F0IENOUlMtU3RhbmRhcmQuIFBvdXIgdG91 dGUgaW5mb3JtYXRpb24gc2UgcmVwb3J0ZXIg4CBodHRwOi8vaWdjLnNlcnZpY2VzLmNucnMuZnIv Q05SUy1TdGFuZGFyZC8wHQYDVR0OBBYEFBw5elbdCpZR0WnR27EsQjmRr3/EMFMGA1UdIwRMMEqA FGdZpeUHdEkD7wXPzC6kGNUQyJ48oS+kLTArMQswCQYDVQQGEwJGUjENMAsGA1UEChMEQ05SUzEN MAsGA1UEAxMEQ05SU4IBAjAoBgNVHREEITAfgR1Lb25zdGFudGluLkthYmFzc2Fub3ZAbGlwNi5m cjBZBgNVHR8EUjBQME6gTKBKhkhodHRwOi8vaWdjLnNlcnZpY2VzLmNucnMuZnIvY2dpLWJpbi9s b2FkLmNybD9DQT1DTlJTLVN0YW5kYXJkJmZvcm1hdD1ERVIwDQYJKoZIhvcNAQEEBQADggEBAD8m erny2WgvzJkuFcYNqqWA9g/7n1qF32uEgzbb+/lDejf7URAuuZqAeMxzF4uvRgDc8pr3EowjoKuD 5OsPdKboekM7B3Kn5J9IoF/Zq9FIw4A63k+KczTMlmFZXbvqBKHVLmG+Y8/FoEcC3xbYFDvKLP/q OOdXgcDOe60b4886fMFDUSOODryacoDAhCNWzuS6+v9JvZ5vFvR0hbkzGuzn/5ZR1H97BirD6ZlS f/bo3awEbsWEXcdj/tltVvc6kW61l1PieIyTd1RPtU99uhpmcUDtT7v5+Y7tjtvemfONmHHa2Jmp fohq8/1IFkhv0r3xHU0xROff+4sQrt3KjLgxggLDMIICvwIBATA6MDQxCzAJBgNVBAYTAkZSMQ0w CwYDVQQKEwRDTlJTMRYwFAYDVQQDEw1DTlJTLVN0YW5kYXJkAgILQTAJBgUrDgMCGgUAoIIBXjAY BgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wNDAzMDcxNjI2MDFaMCMG CSqGSIb3DQEJBDEWBBQSLhBi2quB4U4R4upwV2F+iVMgAzBJBgkrBgEEAYI3EAQxPDA6MDQxCzAJ BgNVBAYTAkZSMQ0wCwYDVQQKEwRDTlJTMRYwFAYDVQQDEw1DTlJTLVN0YW5kYXJkAgILQTBLBgsq hkiG9w0BCRACCzE8oDowNDELMAkGA1UEBhMCRlIxDTALBgNVBAoTBENOUlMxFjAUBgNVBAMTDUNO UlMtU3RhbmRhcmQCAgtBMGcGCSqGSIb3DQEJDzFaMFgwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwIC AgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMAcGBSsOAwIaMAoGCCqG SIb3DQIFMA0GCSqGSIb3DQEBAQUABIIBAK7YWBQ7ozLKgWRiD8krhX27V0NtqiA92ArchFbE/Z0w T4c2S7OWJD8Q3JagtQFxVbjNTtpsJpY71gzOvNizOxojF9t4jH7YUPU52aSzVHEhgDLv9uP0go3P f+ubAuyWyEAFUwk1rIaq18mFPxbJtVkZgUm60/sta0YZWG039rLdwpxCeD8HJR204I+BB11N+5Xe bkWRzayzFN5lmblLhbWzuORWOXiDJOIL15/4Q570xgxQJYOT86trSycaw5RUxyO8wVGg0panwTI7 YT0PZlF5ZGv6QuJfCcKxXzGBdnreMHOfe4VCGKH759H6bPByEmyvHGSY8v+cQOHxY6khQIEAAAAA AAA= ------=_NextPart_000_0058_01C40469.43365D50-- From owner-freebsd-net@FreeBSD.ORG Sun Mar 7 08:47: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 A20A416A4D0 for ; Sun, 7 Mar 2004 08:47:13 -0800 (PST) Received: from mail.tvnetwork.hu (zion.tvnetwork.hu [80.95.64.67]) by mx1.FreeBSD.org (Postfix) with SMTP id 60EE943D1D for ; Sun, 7 Mar 2004 08:47:12 -0800 (PST) (envelope-from grinder@ip-184-91.tvnetwork.hu) Received: (qmail 30333 invoked by uid 64014); 7 Mar 2004 16:47:07 -0000 Received: from grinder@ip-184-91.tvnetwork.hu by zion by uid 64011 with qmail-scanner-1.20rc3 (clamuko: 0.60. spamassassin: 2.60. Clear:RC:1:. Processed in 0.021241 secs); 07 Mar 2004 16:47:07 -0000 Received: from unknown (HELO ip-184-91.tvnetwork.hu) (80.95.91.184) by zion.tvnetwork.hu with SMTP; 7 Mar 2004 16:47:07 -0000 Received: by ip-184-91.tvnetwork.hu (Postfix, from userid 1001) id 35BBC3FDE0; Sun, 7 Mar 2004 17:54:54 +0000 (GMT) Date: Sun, 7 Mar 2004 17:54:53 +0000 From: Kiss Tibor To: freebsd-net@freebsd.org Message-ID: <20040307175453.GA44645@PSY.tvnetwork.hu> Mail-Followup-To: freebsd-net@freebsd.org, freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i cc: freebsd-hackers@freebsd.org Subject: Strange problem with vnodes and sockets X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: grinder@pro.hu 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 16:47:13 -0000 I want to create a small kernel module which logs the socket operations. So in my module I have a socket structure, and i want to know which process (thread) owns that. I try to solve this problem by this way: ... struct proc *p; struct vnode *vn; struct filedesc *fdp; ... sx_slock(&allproc_lock); LIST_FOREACH(p, &allproc, p_list) { PROC_LOCK(p); if (p->p_fd != NULL) { fdp = p->p_fd; FILEDESC_LOCK(fdp); printf("pid: %d\n", p->p_pid); printf("fdp->fd_nfiles: %d\n", fdp->fd_nfiles); printf("fdp->fd_lastfile: %d\n", fdp->fd_lastfile); for (i=0; i < fdp->fd_nfiles; i++) { if (fdp->fd_ofiles[i] == NULL) { continue; } else { vn = (struct vnode *) fdp->fd_ofiles[i]->f_data; printf("%d: %d\n", i, vn->v_type); if (vn->v_type == VSOCK) { if (vn->v_un.vu_socket->so_gencnt == pcb->inp_socket->so_gencnt) { printf("found the socket, pid: %d\n", p->p_pid); } } } } FILEDESC_UNLOCK(fdp); } PROC_UNLOCK(p); } /* LIST_FOREACH */ sx_sunlock(&allproc_lock); If i compile & insert this module, i found some strange things: ... pid: 816 fdp->fd_nfiles: 20 fdp->fd_lastfile: 6 0: 4 1: 4 2: 4 3: 2048 4: 1 5: 2048 6: 4 pid: 635 fdp->fd_nfiles: 20 fdp->fd_lastfile: 6 0: 4 1: 4 2: 4 3: 2048 4: 4 5: 4 6: 4 ... So how can the v_type 2048? v_type is an enum (vnode.h) with 10 "options": enum vtype { VNON, VREG, VDIR, VBLK, VCHR, VLNK, VSOCK, VFIFO, VBAD }; And the real problem is: why don't find that code any VSOCK type vnode in the active process list? And how can i find the proc struct for a socket? :) Thanks, Tibor Kiss From owner-freebsd-net@FreeBSD.ORG Sun Mar 7 10:07: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 B0E0B16A4CE; Sun, 7 Mar 2004 10:07:58 -0800 (PST) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id A08BA43D39; Sun, 7 Mar 2004 10:07:57 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 7 Mar 2004 18:07:56 +0000 (GMT) Date: Sun, 7 Mar 2004 18:07:56 +0000 From: David Malone To: Andre Oppermann Message-ID: <20040307180756.GB1720@walton.maths.tcd.ie> References: <4043B6BA.B847F081@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4043B6BA.B847F081@freebsd.org> User-Agent: Mutt/1.5.3i Sender: dwmalone@maths.tcd.ie 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: Sun, 07 Mar 2004 18:07:58 -0000 On Mon, Mar 01, 2004 at 11:18:34PM +0100, Andre Oppermann wrote: > [] automatically sizing TCP send buffers to achieve optimal performance > over a wide range of bw*delay situations. (in progress) Hi Andre, This reminded me - do you know what happened to the plan to implement SACK for FreeBSD? I'm working with a research group that's interested in new high speed TCP techniques and they'd prefer to work with FreeBSD, but they've been using Linux 'cos they need SACK. They might actually be interested in spending some time implementing it, if we weren't going to be clashing with anytone else. David. From owner-freebsd-net@FreeBSD.ORG Sun Mar 7 10:13: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 0998316A4CE; Sun, 7 Mar 2004 10:13:43 -0800 (PST) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1A8943D41; Sun, 7 Mar 2004 10:13:42 -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 i27IDe9Q086392; Sun, 7 Mar 2004 10:13: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 i27IDeBR086391; Sun, 7 Mar 2004 10:13:40 -0800 (PST) (envelope-from rizzo) Date: Sun, 7 Mar 2004 10:13:40 -0800 From: Luigi Rizzo To: David Malone Message-ID: <20040307101340.A86374@xorpc.icir.org> References: <4043B6BA.B847F081@freebsd.org> <20040307180756.GB1720@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20040307180756.GB1720@walton.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Sun, Mar 07, 2004 at 06:07:56PM +0000 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: Sun, 07 Mar 2004 18:13:43 -0000 On Sun, Mar 07, 2004 at 06:07:56PM +0000, David Malone wrote: > On Mon, Mar 01, 2004 at 11:18:34PM +0100, Andre Oppermann wrote: > > [] automatically sizing TCP send buffers to achieve optimal performance > > over a wide range of bw*delay situations. (in progress) > > Hi Andre, > > This reminded me - do you know what happened to the plan to implement > SACK for FreeBSD? I'm working with a research group that's interested what plan, there never was one :) cheers luigi (who wrote some FreeBSD SACK code back in 1996!) From owner-freebsd-net@FreeBSD.ORG Sun Mar 7 11:42: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 5E79016A4CE; Sun, 7 Mar 2004 11:42:14 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EA7143D31; Sun, 7 Mar 2004 11:42:14 -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 i27JeoxC002974; Sun, 7 Mar 2004 14:40:50 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i27Jeo2H002971; Sun, 7 Mar 2004 14:40:50 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 7 Mar 2004 14:40:50 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Kiss Tibor In-Reply-To: <20040307175453.GA44645@PSY.tvnetwork.hu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Re: Strange problem with vnodes and sockets 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 19:42:14 -0000 On Sun, 7 Mar 2004, Kiss Tibor wrote: > I want to create a small kernel module which logs the socket operations. > So in my module I have a socket structure, and i want to know which > process (thread) owns that. I try to solve this problem by this way: Sockets, as with files, can be referenced by more than one process at a time. While there is only one process that has created any given socket, references to the socket can be inherited by processes forked from it, as well as passed using UNIX domain sockets. As such, there really isn't a notion of "owner". so_cred is a cached referenced to the process credential of the process that created the socket... > So how can the v_type 2048? v_type is an enum (vnode.h) with 10 > "options": enum vtype { VNON, VREG, VDIR, VBLK, VCHR, VLNK, VSOCK, > VFIFO, VBAD }; > > And the real problem is: why don't find that code any VSOCK type vnode > in the active process list? And how can i find the proc struct for a > socket? :) VSOCK vnodes are rendezvous points for UNIX domain socket communication, not the actual communication vehicles themselves. Very few UNIX domain sockets are used in normal operation, but you might take a look at /var/run/log, and the file descriptors that referenced various sockets to the log subsystem. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research From owner-freebsd-net@FreeBSD.ORG Sun Mar 7 12:41: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 30D6416A4CE for ; Sun, 7 Mar 2004 12:41:45 -0800 (PST) Received: from mail.tvnetwork.hu (zion.tvnetwork.hu [80.95.64.67]) by mx1.FreeBSD.org (Postfix) with SMTP id 4448E43D31 for ; Sun, 7 Mar 2004 12:41:44 -0800 (PST) (envelope-from grinder@ip-184-91.tvnetwork.hu) Received: (qmail 17447 invoked by uid 64014); 7 Mar 2004 20:41:43 -0000 Received: from grinder@ip-184-91.tvnetwork.hu by zion by uid 64011 with qmail-scanner-1.20rc3 (clamuko: 0.60. spamassassin: 2.60. Clear:RC:1:. Processed in 0.020366 secs); 07 Mar 2004 20:41:43 -0000 Received: from unknown (HELO ip-184-91.tvnetwork.hu) (80.95.91.184) by zion.tvnetwork.hu with SMTP; 7 Mar 2004 20:41:43 -0000 Received: by ip-184-91.tvnetwork.hu (Postfix, from userid 1001) id 988C53FDE0; Sun, 7 Mar 2004 21:49:30 +0000 (GMT) Date: Sun, 7 Mar 2004 21:49:30 +0000 From: Kiss Tibor To: Robert Watson Message-ID: <20040307214929.GA45799@PSY.tvnetwork.hu> Mail-Followup-To: Robert Watson , freebsd-net@freebsd.org, freebsd-hackers@freebsd.org References: <20040307175453.GA44645@PSY.tvnetwork.hu> 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: freebsd-hackers@freebsd.org Subject: Re: Strange problem with vnodes and sockets 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 20:41:45 -0000 On Sun, Mar 07, 2004 at 02:40:50PM -0500, Robert Watson wrote: > > notion of "owner". so_cred is a cached referenced to the process > credential of the process that created the socket... Yes, but i need the process p_pid. > > VSOCK vnodes are rendezvous points for UNIX domain socket communication, > not the actual communication vehicles themselves. Very few UNIX domain > sockets are used in normal operation, but you might take a look at > /var/run/log, and the file descriptors that referenced various sockets to > the log subsystem. So I was on the really wrong way. I want to find the owner (struct proc) for a _TCP socket_. But now I'm really stucked. I dont have any idea how to do that. Would you be so kind to show me the right way to find the owner proc struct (the creator process; i want to know process p_pid) for a socket (defined in /usr/src/sys/sys/socketvar.h)? Thanks, Kiss Tibor From owner-freebsd-net@FreeBSD.ORG Sun Mar 7 14:50: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 5999216A4CE for ; Sun, 7 Mar 2004 14:50:23 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 646C543D1D for ; Sun, 7 Mar 2004 14:50:22 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 86034 invoked from network); 7 Mar 2004 22:50:20 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.54]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 7 Mar 2004 22:50:20 -0000 Message-ID: <404BA723.C8141806@freebsd.org> Date: Sun, 07 Mar 2004 23:50:11 +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 Malone References: <4043B6BA.B847F081@freebsd.org> <20040307180756.GB1720@walton.maths.tcd.ie> 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: Sun, 07 Mar 2004 22:50:23 -0000 David Malone wrote: > > On Mon, Mar 01, 2004 at 11:18:34PM +0100, Andre Oppermann wrote: > > [] automatically sizing TCP send buffers to achieve optimal performance > > over a wide range of bw*delay situations. (in progress) > > Hi Andre, > > This reminded me - do you know what happened to the plan to implement > SACK for FreeBSD? I'm working with a research group that's interested > in new high speed TCP techniques and they'd prefer to work with > FreeBSD, but they've been using Linux 'cos they need SACK. They > might actually be interested in spending some time implementing it, > if we weren't going to be clashing with anytone else. I don't know of any current project or effort to implement SACK on FreeBSD. It is not on my todo list and it doesn't fit there. But I'm available if someone wants to discuss specifics and implementation details. -- Andre From owner-freebsd-net@FreeBSD.ORG Sun Mar 7 15:37: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 2425316A4CE for ; Sun, 7 Mar 2004 15:37:24 -0800 (PST) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id F045043D1D for ; Sun, 7 Mar 2004 15:37:23 -0800 (PST) (envelope-from scrappy@hub.org) Received: by ganymede.hub.org (Postfix, from userid 1000) id 943F1351B1; Sun, 7 Mar 2004 19:37:24 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 91527350CC; Sun, 7 Mar 2004 19:37:24 -0400 (AST) Date: Sun, 7 Mar 2004 19:37:24 -0400 (AST) From: "Marc G. Fournier" To: Tim Wilde In-Reply-To: Message-ID: <20040307193659.T13247@ganymede.hub.org> References: <20040306150504.Q13247@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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: Sun, 07 Mar 2004 23:37:24 -0000 On Sat, 6 Mar 2004, Tim Wilde wrote: > 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. Actually, just a simple Linksys 10/100 Switch ... I *have* to upgrade it to something managed :( ---- 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 Sun Mar 7 15:37: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 93E2516A4CE for ; Sun, 7 Mar 2004 15:37:55 -0800 (PST) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 687CF43D2F for ; Sun, 7 Mar 2004 15:37:55 -0800 (PST) (envelope-from scrappy@hub.org) Received: by ganymede.hub.org (Postfix, from userid 1000) id 17C7334504; Sun, 7 Mar 2004 19:37:56 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 16CED344FB; Sun, 7 Mar 2004 19:37:56 -0400 (AST) Date: Sun, 7 Mar 2004 19:37:56 -0400 (AST) From: "Marc G. Fournier" To: Tim Wilde In-Reply-To: Message-ID: <20040307193726.R13247@ganymede.hub.org> References: <20040306150504.Q13247@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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: Sun, 07 Mar 2004 23:37:55 -0000 On Sat, 6 Mar 2004, Tim Wilde wrote: > 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. Note that forcing it to 100baseT half-duplex (or 10baseT/UTP half-duplex) corrects the problem ... turns out it is only in full-duplex mode that its hosed ... ---- 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 Sun Mar 7 16:52: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 35DF016A4CE for ; Sun, 7 Mar 2004 16:52:29 -0800 (PST) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB18C43D2F for ; Sun, 7 Mar 2004 16:52:28 -0800 (PST) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Sun, 7 Mar 2004 19:52:27 -0500 Message-ID: From: Don Bowman To: "'Marc G. Fournier'" , Tim Wilde Date: Sun, 7 Mar 2004 19:50:44 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" 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: Mon, 08 Mar 2004 00:52:29 -0000 From: Marc G. Fournier [mailto:scrappy@hub.org] > On Sat, 6 Mar 2004, Tim Wilde wrote: > > > 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. > > Note that forcing it to 100baseT half-duplex (or 10baseT/UTP > half-duplex) > corrects the problem ... turns out it is only in full-duplex > mode that its > hosed ... Actually, this is normal behaviour according to the 802.3u spec. If a device in 'auto' mode is connected to one that is forced 100FDX, the auto one will negotiate 100HDX. For example, see HP faq: http://www.hp.com/rnd/support/faqs/2700.htm#question6 http://roger.friendex.net/duplex_mismatch.htm has a nice table of this. --don From owner-freebsd-net@FreeBSD.ORG Sun Mar 7 20:22: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 ADF1016A4CE for ; Sun, 7 Mar 2004 20:22:53 -0800 (PST) Received: from bes.amduat.net (bes.amduat.net [206.124.149.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 493F743D41 for ; Sun, 7 Mar 2004 20:22:53 -0800 (PST) (envelope-from jbarrett@amduat.net) Received: from osiris.amduat.net (osiris.amduat.net [10.0.0.69]) (AUTH: LOGIN jbarrett, SSL: TLSv1/SSLv3,128bits,RC4-MD5) by bes.amduat.net with esmtp; Sun, 07 Mar 2004 20:22:52 -0800 From: "Jacob S. Barrett" To: freebsd-net@freebsd.org Date: Sun, 7 Mar 2004 20:22:51 -0800 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: <200403072022.51630.jbarrett@amduat.net> Subject: Solution for Resilient VLAN Trunk Bonding 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, 08 Mar 2004 04:22:53 -0000 Now that ng_vlan has been committed to FreeBSD-5 I have come up with a solution for building a resilient VLAN interfaces over a VLAN trunk. I have a machine that exists on multiple VLANs. It has two interfaces that are connected to two different switches. The switches are trunked together as well. Both switches are running Spanning Tree. With this solution if one switch is taken out of commission, either for scheduled maintenance or failure, the other switch and link to the server should failover. I have tested this solution below thourally, but I wanted to get other opinions and comments on it before I put it in production. I would have liked to have used either ng_fec or ng_one2many, but neither of them detects link failures. Using ng_bridge and spanning trees solves that problem. When spanning tree detects a topology change due to link failure the other link tacks over. Unfortunately with this solution it does take quite a while, up to 60 seconds, for the link to failover, but is better than having to drive into the datacenter and manually making adjustments. Is someone working on a solution for either ng_fec or ng_one2many to detect link failures? Here is what I have done in good only ASCII art: sw1--fxp0--\ /--default(ng_eiface)--ngeth0 | bond0(ng_bidge)--vlt0(ng_vlan)--vlan2(ng_eiface)--ngeth1 sw2--xl0---/ \--vlan3(ng_eiface)--ngeth2 BEGIN vlan-bonding.sh: #/bin/sh # Trunk interfaces must be up or setpromisc fails. ifconfig fxp0 up ifconfig xl0 up ngctl -f- < vlt0, link1 => fxp0, link2 => xl0 # fxp0 mkpeer fxp0: bridge lower link1 name fxp0:lower bond0 msg fxp0: setpromisc 1 msg fxp0: setautosrc 0 # xl0 connect xl0: bond0: lower link2 msg xl0: setpromisc 1 msg xl0: setautosrc 0 # VLAN trunk (vlt0) mkpeer bond0: vlan link0 downstream name bond0:link0 vlt0 # VLAN Default (ngeth0) mkpeer vlt0: eiface nomatch ether name vlt0:nomatch default # VLAN 2 (ngeth1) mkpeer vlt0: eiface vlan2 ether msg vlt0: addfilter { vlan=2 hook="vlan2" } name vlt0:vlan2 vlan2 # VLAN 3 (ngeth2) mkpeer vlt0: eiface vlan3 ether msg vlt0: addfilter { vlan=3 hook="vlan3" } name vlt0:vlan3 vlan3 EOF ifconfig ngeth0 link 70:6F:67:6F:00:00 ifconfig ngeth0 link 70:6F:67:6F:00:01 ifconfig ngeth0 link 70:6F:67:6F:00:02 END -- Jacob S. Barrett jbarrett@amduat.net www.amduat.net "I don't suffer from insanity, I enjoy every minute of it." From owner-freebsd-net@FreeBSD.ORG Sun Mar 7 20:50:39 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D89E516A4CE for ; Sun, 7 Mar 2004 20:50:39 -0800 (PST) Received: from bes.amduat.net (bes.amduat.net [206.124.149.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C7F243D1F for ; Sun, 7 Mar 2004 20:50:39 -0800 (PST) (envelope-from jbarrett@amduat.net) Received: from osiris.amduat.net (osiris.amduat.net [10.0.0.69]) (AUTH: LOGIN jbarrett, SSL: TLSv1/SSLv3,128bits,RC4-MD5) by bes.amduat.net with esmtp; Sun, 07 Mar 2004 20:50:38 -0800 From: "Jacob S. Barrett" To: freebsd-net@freebsd.org Date: Sun, 7 Mar 2004 20:50:38 -0800 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: <200403072050.38190.jbarrett@amduat.net> Subject: ng_vlan in FreeBSD-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: Mon, 08 Mar 2004 04:50:40 -0000 When might we see ng_vlan ported to FreeBSD-4? -- Jacob S. Barrett jbarrett@amduat.net www.amduat.net "I don't suffer from insanity, I enjoy every minute of it." From owner-freebsd-net@FreeBSD.ORG Sun Mar 7 22:10: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 0177B16A4CE for ; Sun, 7 Mar 2004 22:10:33 -0800 (PST) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADB6D43D1F for ; Sun, 7 Mar 2004 22:10:32 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (sccrmhc11) with ESMTP id <2004030806103101100hllp6e>; Mon, 8 Mar 2004 06:10:31 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id WAA43135; Sun, 7 Mar 2004 22:10:30 -0800 (PST) Date: Sun, 7 Mar 2004 22:10:29 -0800 (PST) From: Julian Elischer To: "Jacob S. Barrett" In-Reply-To: <200403072022.51630.jbarrett@amduat.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: Solution for Resilient VLAN Trunk Bonding 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, 08 Mar 2004 06:10:33 -0000 On Sun, 7 Mar 2004, Jacob S. Barrett wrote: > Now that ng_vlan has been committed to FreeBSD-5 I have come up with a > solution for building a resilient VLAN interfaces over a VLAN trunk. I have > a machine that exists on multiple VLANs. It has two interfaces that are > connected to two different switches. The switches are trunked together as > well. Both switches are running Spanning Tree. With this solution if one > switch is taken out of commission, either for scheduled maintenance or > failure, the other switch and link to the server should failover. I have > tested this solution below thourally, but I wanted to get other opinions and > comments on it before I put it in production. > > I would have liked to have used either ng_fec or ng_one2many, but neither of > them detects link failures. Using ng_bridge and spanning trees solves that > problem. When spanning tree detects a topology change due to link failure > the other link tacks over. Unfortunately with this solution it does take > quite a while, up to 60 seconds, for the link to failover, but is better than > having to drive into the datacenter and manually making adjustments. Is > someone working on a solution for either ng_fec or ng_one2many to detect link > failures? I have a variant of ng_one2many that does link testing with it's own pings.. unfortunatly it needs to prepend a small header on data so it can separate out its pings from the data.. I'll try find it. Also, mpd does multilink pppp in netgraph nnodes and the multilink can be programmed as to how fast it detects failures. The tradeoff is being too sensitive and cutting off good links too quickly. > > Here is what I have done in good only ASCII art: > > sw1--fxp0--\ /--default(ng_eiface)--ngeth0 > | bond0(ng_bidge)--vlt0(ng_vlan)--vlan2(ng_eiface)--ngeth1 > sw2--xl0---/ \--vlan3(ng_eiface)--ngeth2 > > BEGIN vlan-bonding.sh: > #/bin/sh > > # Trunk interfaces must be up or setpromisc fails. > ifconfig fxp0 up > ifconfig xl0 up > > ngctl -f- < # Bonding (bond0) > # link0 => vlt0, link1 => fxp0, link2 => xl0 > # fxp0 > mkpeer fxp0: bridge lower link1 > name fxp0:lower bond0 > msg fxp0: setpromisc 1 > msg fxp0: setautosrc 0 > # xl0 > connect xl0: bond0: lower link2 > msg xl0: setpromisc 1 > msg xl0: setautosrc 0 > > # VLAN trunk (vlt0) > mkpeer bond0: vlan link0 downstream > name bond0:link0 vlt0 > > # VLAN Default (ngeth0) > mkpeer vlt0: eiface nomatch ether > name vlt0:nomatch default > > # VLAN 2 (ngeth1) > mkpeer vlt0: eiface vlan2 ether > msg vlt0: addfilter { vlan=2 hook="vlan2" } > name vlt0:vlan2 vlan2 > > # VLAN 3 (ngeth2) > mkpeer vlt0: eiface vlan3 ether > msg vlt0: addfilter { vlan=3 hook="vlan3" } > name vlt0:vlan3 vlan3 > EOF > > ifconfig ngeth0 link 70:6F:67:6F:00:00 > ifconfig ngeth0 link 70:6F:67:6F:00:01 > ifconfig ngeth0 link 70:6F:67:6F:00:02 > > END > > -- > Jacob S. Barrett > jbarrett@amduat.net > www.amduat.net > > "I don't suffer from insanity, I enjoy every minute of it." > _______________________________________________ > 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 8 01:19: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 CDC2A16A4CF for ; Mon, 8 Mar 2004 01:19:35 -0800 (PST) Received: from web41811.mail.yahoo.com (web41811.mail.yahoo.com [66.218.93.145]) by mx1.FreeBSD.org (Postfix) with SMTP id 5EFBC43D1D for ; Mon, 8 Mar 2004 01:19:35 -0800 (PST) (envelope-from youknicks@yahoo.com) Message-ID: <20040308091935.59513.qmail@web41811.mail.yahoo.com> Received: from [24.6.220.149] by web41811.mail.yahoo.com via HTTP; Mon, 08 Mar 2004 01:19:35 PST Date: Mon, 8 Mar 2004 01:19:35 -0800 (PST) From: Jerry Jensen To: "."@babolo.ru In-Reply-To: <1078642138.728121.16568.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: Mon, 08 Mar 2004 09:19:36 -0000 How can this be done programmatically rather than from the command line? Code snippets would be handy. Thanks --- .@babolo.ru 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). > 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 > > > _______________________________________________ > 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 Mon Mar 8 02:20: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 CEF9A16A4CE; Mon, 8 Mar 2004 02:20:37 -0800 (PST) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 005C343D41; Mon, 8 Mar 2004 02:20:37 -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 i28AKYQE066329 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Mar 2004 13:20:34 +0300 (MSK) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.9/8.12.6/Submit) id i28AKX9o066328; Mon, 8 Mar 2004 13:20:33 +0300 (MSK) Date: Mon, 8 Mar 2004 13:20:33 +0300 From: Gleb Smirnoff To: Ruslan Ermilov , julian@FreeBSD.org, archie@FreeBSD.org Message-ID: <20040308102033.GA66247@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Ruslan Ermilov , julian@freebsd.org, archie@freebsd.org, freebsd-net@freebsd.org References: <200403072302.i27N2StR008804@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <200403072302.i27N2StR008804@freefall.freebsd.org> User-Agent: Mutt/1.5.6i cc: freebsd-net@FreeBSD.org Subject: Re: kern/63864: [patch] new control message for ng_iface(4) - getifindex 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, 08 Mar 2004 10:20:38 -0000 On Sun, Mar 07, 2004 at 03:02:28PM -0800, Ruslan Ermilov wrote: R> Synopsis: [patch] new control message for ng_iface(4) - getifindex R> R> State-Changed-From-To: open->closed R> State-Changed-By: ru R> State-Changed-When: Sun Mar 7 15:01:03 PST 2004 R> State-Changed-Why: R> Committed with tiny modifications, thanks! I have one more idea. Currently we have got 3 interface nodes: ng_ether, ng_iface, ng_eiface. 2 of them already support "getifindex" message, imagine I (or someone else) send you patch tomorrow, which adds support to ng_eiface. OK, now all three support. May be in future some new interface nodes will be developed. Imagine the following: you have node, which is connected to some generic interface (it doesn't know which node type exactly). This node wants to determine interface index of attached interfac. It would send 3 "getifindex" messages with 3 different cookies. Two of messages will always fail, and one return. This is not nice. What I suggest: create a new semi-generic cookie NGM_GENERICIFACE_COOKIE, which will be supported by all interface nodes. Put NGM_GENERICIFACE_GETIFINDEX message under NGM_GENERICIFACE_COOKIE case brackets. If you like this idea, please reply me. And I'll send patches. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 02:20: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 74FBA16A4CE; Mon, 8 Mar 2004 02:20:44 -0800 (PST) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CE3743D39; Mon, 8 Mar 2004 02:20:43 -0800 (PST) (envelope-from ru@ip.net.ua) Received: from heffalump.office.ipnet (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.10/8.12.9) with ESMTP id i28AO51t024997 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Mar 2004 12:24:06 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.office.ipnet (8.12.11/8.12.11) id i28AKcct028531; Mon, 8 Mar 2004 12:20:38 +0200 (EET) (envelope-from ru) Date: Mon, 8 Mar 2004 12:20:38 +0200 From: Ruslan Ermilov To: Andre Oppermann Message-ID: <20040308102038.GA28502@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx" Content-Disposition: inline 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: Cached IP routes 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, 08 Mar 2004 10:20:44 -0000 --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Andre, I see you've fixed ip_forward() so that it no longer caches (possibly stale) route, which is great. What are the performance impacts of this change, have you measured it? We still have a similar problem in in_gif_output(), and I wonder what would be a correct fix, given the above? Cheers, --=20 Ruslan Ermilov FreeBSD committer ru@FreeBSD.org --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFATEj2Ukv4P6juNwoRAjh7AJ961GC+aA31uKOWkcvYQohmMzSO8gCeKwQF +IDjJMvqoJ/8MXql6DptYi0= =BNVr -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx-- From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 03: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 4D8A316A4CE for ; Mon, 8 Mar 2004 03:56:32 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 979D043D1D for ; Mon, 8 Mar 2004 03:56:31 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 72765 invoked from network); 8 Mar 2004 11:56: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 ; 8 Mar 2004 11:56:30 -0000 Message-ID: <404C5F65.446E20A8@freebsd.org> Date: Mon, 08 Mar 2004 12:56:21 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Ruslan Ermilov References: <20040308102038.GA28502@ip.net.ua> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: net@FreeBSD.org Subject: Re: Cached IP routes 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, 08 Mar 2004 11:56:32 -0000 Ruslan Ermilov wrote: > > Andre, > > I see you've fixed ip_forward() so that it no longer caches (possibly > stale) route, which is great. What are the performance impacts of this > change, have you measured it? I've removed the "route cache" in ip_forward() mainly because it was a major headache for the locking code. I have not measured the impact. However this cache was only caching the last used route. If you only have a default route the routing table is so small that a normal routing table lookup is extremely fast as well. If you have a full default free view of the Internet and push a lot of traffic then it becomes highly unlikely that two packet following each other use the same route. If that happens you have pessimized more than without this route cache because it needs to free the preview entry first. In the end the performance trade-off is essentially equal but without the route cache it's much simpler and less complexity. > We still have a similar problem in in_gif_output(), and I wonder what > would be a correct fix, given the above? in_gif_output() is not the same as the route cache of ip_forward. It just caches the route to the tunnel destination which normally stays the same over long periods of time. The only problem you might run into are route changes. At one point in time your best path is the default route so a pointer to it is being cached in sc->gif_ro. Later you have a better via some other gateway. This won't be picked up by the gif route cache. In 5.2 and -CURRENT you can scrap the route cache and just give a NULL to ip_output instead of a route. This way you will always use the best path to destination. -- Andre From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 06:17: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 08F5816A4CE for ; Mon, 8 Mar 2004 06:17:22 -0800 (PST) Received: from mail.valuehost.co.uk (mail.valuehost.co.uk [62.25.99.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id C455C43D1D for ; Mon, 8 Mar 2004 06:17:20 -0800 (PST) (envelope-from bjorn@eikeland.info) Received: (from mail@localhost) by mail.valuehost.co.uk (8.11.6/8.11.6) id i28EHAv90620 for freebsd-net@freebsd.org; Mon, 8 Mar 2004 17:17:10 +0300 (MSK) (envelope-from bjorn@eikeland.info) X-Authentication-Warning: mail.valuehost.co.uk: mail set sender to bjorn@eikeland.info using -f Received: from 80.202.106.55 ( [80.202.106.55]) as user bjorn@eikeland.info@localhost by mail.eikeland.info with HTTP; Mon, 8 Mar 2004 17:17:10 +0300 Message-ID: <1078755430.404c8066a7453@mail.eikeland.info> Date: Mon, 8 Mar 2004 17:17:10 +0300 From: bjorn@eikeland.info To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs Subject: replacing bridge with router 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, 08 Mar 2004 14:17:22 -0000 I've previously used my freebsd box as a bridge between ath0, fxp1 and fxp0 - but since the bridge doesnt allow me to divert packets I'm wanting to set up routing instead. Network sketch: ,- ath0 --- wireless lan netopia 3351 / 10.0.2.1/24 isp router ----- fxp0 FreeBSD fxp1 ----- wired lan 10.0.0.1/24 10.0.0.2/24 10.0.1.1/24 After a lot of trying and even more faling I fount a RIP option in my isps router, enabled it and started routed on my freebsd box and suddenly routing worked (the isp router didnt work with static routes). Altough I'm able to ping the isp dns server (217.13.4.24) from 10.0.2.0/24 I cant query it - tcpdump shows the query packets leaving fxp0. The FreeBSD box queries it without problems. I take it the problem is the isp router since the dns replies never make it to fxp0, but the isp router does route icmp traffic from 217.13.4.24 to 10.0.2.2/24 but not the dns reply? I suppose I can set up a caching dns server on the FreeBSD box, but just out of curiousity I'd like to know whats causing this somewhat confusing problem. Anyone have any ideas? (firewall is default to accept) From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 07:24: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 C0C0816A4CE for ; Mon, 8 Mar 2004 07:24:33 -0800 (PST) Received: from mail.valuehost.co.uk (mail.valuehost.co.uk [62.25.99.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 766C143D1F for ; Mon, 8 Mar 2004 07:24:32 -0800 (PST) (envelope-from bjorn@eikeland.info) Received: (from mail@localhost) by mail.valuehost.co.uk (8.11.6/8.11.6) id i28FOLU44952 for freebsd-net@freebsd.org; Mon, 8 Mar 2004 18:24:21 +0300 (MSK) (envelope-from bjorn@eikeland.info) X-Authentication-Warning: mail.valuehost.co.uk: mail set sender to bjorn@eikeland.info using -f Received: from 80.202.106.55 ( [80.202.106.55]) as user bjorn@eikeland.info@localhost by mail.eikeland.info with HTTP; Mon, 8 Mar 2004 18:24:21 +0300 Message-ID: <1078759461.404c9025e71cd@mail.eikeland.info> Date: Mon, 8 Mar 2004 18:24:21 +0300 From: bjorn@eikeland.info To: freebsd-net@freebsd.org References: <1078755430.404c8066a7453@mail.eikeland.info> In-Reply-To: <1078755430.404c8066a7453@mail.eikeland.info> MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs Subject: [Solved] Re: replacing bridge with router 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, 08 Mar 2004 15:24:33 -0000 Problem was the firewall in the isp router, is allows icmp everywhere and incomming traffic to 10/8 but only outbound traffic from 10/24 - changed that to 10/16 and viola! From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 07:50: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 F24BB16A4CE for ; Mon, 8 Mar 2004 07:50:39 -0800 (PST) Received: from ints.mail.pike.ru (ints.mail.pike.ru [195.9.45.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17A4A43D1F for ; Mon, 8 Mar 2004 07:50:39 -0800 (PST) (envelope-from babolo@cicuta.babolo.ru) Received: (qmail 68668 invoked from network); 8 Mar 2004 16:08:02 -0000 Received: from babolo.ru (HELO cicuta.babolo.ru) (194.58.226.160) by ints.mail.pike.ru with SMTP; 8 Mar 2004 16:08:02 -0000 Received: (nullmailer pid 38095 invoked by uid 136); Mon, 08 Mar 2004 15:51:37 -0000 X-ELM-OSV: (Our standard violations) hdr-charset=KOI8-R; no-hdr-encoding=1 In-Reply-To: <20040308091935.59513.qmail@web41811.mail.yahoo.com> To: Jerry Jensen Date: Mon, 8 Mar 2004 18:51:37 +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: <1078761097.455893.38094.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: Mon, 08 Mar 2004 15:50:40 -0000 > How can this be done programmatically rather than from > the command line? Code snippets would be handy. What "this" is? ifconfig? execlp("ifconfig", "ifconfig", "lo0", "inet", inetxt); I never ifconfigured from C. Sorry. > --- .@babolo.ru 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). > > 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 From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 08:05: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 EADD216A4CE; Mon, 8 Mar 2004 08:05:42 -0800 (PST) Received: from casselton.net (casselton.net [63.165.140.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31FE743D31; Mon, 8 Mar 2004 08:05:42 -0800 (PST) (envelope-from tinguely@casselton.net) Received: from casselton.net (localhost [127.0.0.1]) by casselton.net (8.12.9p2/8.12.9) with ESMTP id i28G5bd4037145; Mon, 8 Mar 2004 10:05:37 -0600 (CST) (envelope-from tinguely@casselton.net) Received: (from tinguely@localhost) by casselton.net (8.12.9p2/8.12.9/Submit) id i28G5arD037139; Mon, 8 Mar 2004 10:05:36 -0600 (CST) (envelope-from tinguely) Date: Mon, 8 Mar 2004 10:05:36 -0600 (CST) From: Mark Tinguely Message-Id: <200403081605.i28G5arD037139@casselton.net> To: dwmalone@maths.tcd.ie, freebsd-net@freebsd.org, rizzo@icir.org In-Reply-To: <20040307101340.A86374@xorpc.icir.org> X-Spam-Status: No, hits=0.9 required=5.0 tests=REPLY_TO_EMPTY autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on ccn.casselton.net 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: Mon, 08 Mar 2004 16:05:43 -0000 > > This reminded me - do you know what happened to the plan to implement > > SACK for FreeBSD? I'm working with a research group that's interested > > what plan, there never was one :) > > cheers > luigi (who wrote some FreeBSD SACK code back in 1996!) There has been the "enternal" debate, clean up the stack and/or add features or the resistance to commit the clean up and/or new features. IMO, in the world that is growing ever more wireless, SACK, ECN, and RFC3042 *should be* automatically in the TCP stack or we are at a competitive disadvantage. These could be added pretty easily. --Mark Tinguely. From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 08:19: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 B139016A4CE for ; Mon, 8 Mar 2004 08:19:10 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00AEB43D1D for ; Mon, 8 Mar 2004 08:19:10 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 46723 invoked from network); 8 Mar 2004 16:19:09 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 8 Mar 2004 16:19:09 -0000 Message-ID: <404C9CF3.CBC11F30@freebsd.org> Date: Mon, 08 Mar 2004 17:18:59 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Mark Tinguely References: <200403081605.i28G5arD037139@casselton.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: dwmalone@maths.tcd.ie cc: freebsd-net@freebsd.org cc: rizzo@icir.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: Mon, 08 Mar 2004 16:19:10 -0000 Mark Tinguely wrote: > > > > > This reminded me - do you know what happened to the plan to implement > > > SACK for FreeBSD? I'm working with a research group that's interested > > > > what plan, there never was one :) > > > > cheers > > luigi (who wrote some FreeBSD SACK code back in 1996!) > > There has been the "enternal" debate, clean up the stack and/or add features > or the resistance to commit the clean up and/or new features. I think these days are over and I have committed a couple of larger changes in the IP code a couple month ago with more to come. So if you have new stuff, bring it on and we will judge it on its merits and code quality. > IMO, in the world that is growing ever more wireless, SACK, ECN, and RFC3042 > *should be* automatically in the TCP stack or we are at a competitive > disadvantage. These could be added pretty easily. RFC3042 is already in (done by Jeffrey Hsu) and defaults to enable in -CURRENT along with Inflight and RFC3390. -- Andre From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 09:16: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 15A5516A4CE; Mon, 8 Mar 2004 09:16:58 -0800 (PST) Received: from casselton.net (casselton.net [63.165.140.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93CD943D2D; Mon, 8 Mar 2004 09:16:57 -0800 (PST) (envelope-from tinguely@casselton.net) Received: from casselton.net (localhost [127.0.0.1]) by casselton.net (8.12.9p2/8.12.9) with ESMTP id i28HGud4040364; Mon, 8 Mar 2004 11:16:56 -0600 (CST) (envelope-from tinguely@casselton.net) Received: (from tinguely@localhost) by casselton.net (8.12.9p2/8.12.9/Submit) id i28HGuqA040363; Mon, 8 Mar 2004 11:16:56 -0600 (CST) (envelope-from tinguely) Date: Mon, 8 Mar 2004 11:16:56 -0600 (CST) From: Mark Tinguely Message-Id: <200403081716.i28HGuqA040363@casselton.net> To: andre@freebsd.org, tinguely@casselton.net In-Reply-To: <404C9CF3.CBC11F30@freebsd.org> X-Spam-Status: No, hits=0.9 required=5.0 tests=REPLY_TO_EMPTY autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on ccn.casselton.net cc: dwmalone@maths.tcd.ie cc: freebsd-net@freebsd.org cc: rizzo@icir.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: Mon, 08 Mar 2004 17:16:58 -0000 > I think these days are over and I have committed a couple of larger > changes in the IP code a couple month ago with more to come. Great, I haven't been in the -current network code for a few months. Dave Zarzycki posted a SACK / FACK patch for the 22 Aug 2001 version of current. I am not an expert to say whether or not Forward Acknowledgements are necessary. I am sure this is a good starting point for SACK. --Mark Tinguely. From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 09:25: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 53A0016A4CE for ; Mon, 8 Mar 2004 09:25:32 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 985B243D2F for ; Mon, 8 Mar 2004 09:25:31 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 56899 invoked from network); 8 Mar 2004 17:25: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 ; 8 Mar 2004 17:25:30 -0000 Message-ID: <404CAC81.8912E178@freebsd.org> Date: Mon, 08 Mar 2004 18:25:21 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Mark Tinguely References: <200403081716.i28HGuqA040363@casselton.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: dwmalone@maths.tcd.ie cc: freebsd-net@freebsd.org cc: rizzo@icir.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: Mon, 08 Mar 2004 17:25:32 -0000 Mark Tinguely wrote: > > > I think these days are over and I have committed a couple of larger > > changes in the IP code a couple month ago with more to come. > > Great, I haven't been in the -current network code for a few months. > > Dave Zarzycki posted a SACK / FACK patch for > the 22 Aug 2001 version of current. I am not an expert to say whether > or not Forward Acknowledgements are necessary. I am sure this is a > good starting point for SACK. As I have said in another email I don't have space on my todo list to take care of SACK myself. However if someone comes up with an updated patch I'm happy to look into, review and test it. -- Andre From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 10:24: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 08A2416A4CE; Mon, 8 Mar 2004 10:24:33 -0800 (PST) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3B7F43D1F; Mon, 8 Mar 2004 10:24:32 -0800 (PST) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Mon, 08 Mar 2004 10:24:32 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 4FA6D5D08; Mon, 8 Mar 2004 10:24:31 -0800 (PST) To: Andre Oppermann In-reply-to: Your message of "Sun, 07 Mar 2004 23:50:11 +0100." <404BA723.C8141806@freebsd.org> Date: Mon, 08 Mar 2004 10:24:31 -0800 From: "Kevin Oberman" Message-Id: <20040308182431.4FA6D5D08@ptavv.es.net> cc: David Malone 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: Mon, 08 Mar 2004 18:24:33 -0000 > Date: Sun, 07 Mar 2004 23:50:11 +0100 > From: Andre Oppermann > Sender: owner-freebsd-current@freebsd.org > > David Malone wrote: > > > > On Mon, Mar 01, 2004 at 11:18:34PM +0100, Andre Oppermann wrote: > > > [] automatically sizing TCP send buffers to achieve optimal performance > > > over a wide range of bw*delay situations. (in progress) > > > > Hi Andre, > > > > This reminded me - do you know what happened to the plan to implement > > SACK for FreeBSD? I'm working with a research group that's interested > > in new high speed TCP techniques and they'd prefer to work with > > FreeBSD, but they've been using Linux 'cos they need SACK. They > > might actually be interested in spending some time implementing it, > > if we weren't going to be clashing with anytone else. > > I don't know of any current project or effort to implement SACK on > FreeBSD. It is not on my todo list and it doesn't fit there. But > I'm available if someone wants to discuss specifics and implementation > details. I know that our organization would love to see SACK. Much of the high-performance network development that used to be on FreeBSD has moved to Linux simply because SACK is essential. You can't run trans-oceanic TCP streams of gigabit or more throughput without it. Unfortunately, SACK is often looked upon as a waste of effort to those who use nets in more commercial forms where aggregation of lots of small streams is how fat pipes are used. Research big science are about the only ones who have a real need for this kind of performance and it's growing fast. Without SACK, FreeBSD will be a non-starter for these purposes. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 10:37: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 74CAB16A4CE for ; Mon, 8 Mar 2004 10:37:09 -0800 (PST) Received: from smtp.hotbox.ru (smtp.hotbox.ru [80.68.244.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 978F443D2F for ; Mon, 8 Mar 2004 10:37:08 -0800 (PST) (envelope-from lexxmail@front.ru) Received: from duron.lexx.net.ru (mtu-giga.korolev-net.ru [212.188.65.237] (may be forged)) (authenticated bits=0) by smtp.hotbox.ru (8.12.9/8.12.9) with ESMTP id i28IWqnr074504 for ; Mon, 8 Mar 2004 21:32:54 +0300 (MSK) (envelope-from lexxmail@front.ru) Date: Mon, 8 Mar 2004 21:35:47 +0300 From: "Vadim A. Shklyaev" X-Mailer: The Bat! (v1.62i) Business X-Priority: 3 (Normal) Message-ID: <1251903637025.20040308213547@front.ru> To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: mpd-3.16 and PPPoE server mode on 5.2.1-RELEASE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Vadim A. Shklyaev" List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Mar 2004 18:37:09 -0000 Hello, mpd-users. I've decided to migrate from 4.9-STABLE to 5.2.1-RELEASE, and found, that mpd-3.16 on 5.2.1-RELEASE works strange: everything is ok, for example, with generic vpn, but PPPoE server mode crashes system, when loading netgraph modules as kld. When i've recompiled kernel with compiled-in NETGRAPH support, it accepts connection, netgraph reports NGM_PPPOE_SUCCESS, and immediantly after that - NGM_PPPOE_CLOSE. Configuration file used are quite simple, and proved to be ok on 4.9-STABLE system. pppoed works fine, btw, source code for pppoed didn't change since 4.9-STABLE. So, question, does anyone have mpd work as pppoe-server on FreeBSD-5? Or may be any ideas, why does it happen? -- Best Regards, Vadim A. Shklyaev mailto:lexxmail@front.ru From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 10:56:47 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5EC7116A4CE; Mon, 8 Mar 2004 10:56:47 -0800 (PST) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3494243D49; Mon, 8 Mar 2004 10:56:47 -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 i28Iug9Q049682; Mon, 8 Mar 2004 10:56:42 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.9p1/8.12.3/Submit) id i28IugAE049681; Mon, 8 Mar 2004 10:56:42 -0800 (PST) (envelope-from rizzo) Date: Mon, 8 Mar 2004 10:56:42 -0800 From: Luigi Rizzo To: Kevin Oberman Message-ID: <20040308105641.A47564@xorpc.icir.org> References: <404BA723.C8141806@freebsd.org> <20040308182431.4FA6D5D08@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20040308182431.4FA6D5D08@ptavv.es.net>; from oberman@es.net on Mon, Mar 08, 2004 at 10:24:31AM -0800 cc: David Malone 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: Mon, 08 Mar 2004 18:56:47 -0000 On Mon, Mar 08, 2004 at 10:24:31AM -0800, Kevin Oberman wrote: ... > I know that our organization would love to see SACK. Much of the > high-performance network development that used to be on FreeBSD has > moved to Linux simply because SACK is essential. You can't run > trans-oceanic TCP streams of gigabit or more throughput without it. > > Unfortunately, SACK is often looked upon as a waste of effort to those > who use nets in more commercial forms where aggregation of lots of small > streams is how fat pipes are used. Research big science are about the > only ones who have a real need for this kind of performance and it's > growing fast. Without SACK, FreeBSD will be a non-starter for these > purposes. Whenever i hear these comments, i am very annoyed at one thing (which in a smaller scale repeats all over the place): people are more than happy to spend big money for things like routers or bandwidth or any kind of "commercial" stuff, but when it comes to open source it must be free or nothing. I hope it is clear to everyone that an investment in the 50K$ range would provide a professional-grade implementation of SACK for FreeBSD, and this money is in the noise for any organization that uses trans-oceanic gigabit links. The fact that nobody seems to care about funding such a work either means that whatever is available already fits their goals, in which case I agree that there is no point in using something different, or that these discussions are based more on thin air than substance. You certainly raise a valid point on the fact that for the vast majority of people probably SACK is mostly useless. cheers luigi > R. Kevin Oberman, Network Engineer > Energy Sciences Network (ESnet) > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > E-mail: oberman@es.net Phone: +1 510 486-8634 > _______________________________________________ > 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 8 11:01: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 83E6916A4D2 for ; Mon, 8 Mar 2004 11:01:41 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6733643D1D for ; Mon, 8 Mar 2004 11:01:41 -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 i28J1fbv072736 for ; Mon, 8 Mar 2004 11:01:41 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i28J1ekc072729 for freebsd-net@freebsd.org; Mon, 8 Mar 2004 11:01:40 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 8 Mar 2004 11:01:40 -0800 (PST) Message-Id: <200403081901.i28J1ekc072729@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, 08 Mar 2004 19:01:41 -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 8 12:19: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 7041016A4CE; Mon, 8 Mar 2004 12:19:08 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8B7F43D45; Mon, 8 Mar 2004 12:19:07 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id E721B6520C; Mon, 8 Mar 2004 20:19:05 +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 10101-03-2; Mon, 8 Mar 2004 20:19:05 +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 B2252651EB; Mon, 8 Mar 2004 20:19:04 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id 8543ADF; Mon, 8 Mar 2004 20:19:03 +0000 (GMT) Date: Mon, 8 Mar 2004 20:19:02 +0000 From: Bruce M Simpson To: Andre Oppermann Message-ID: <20040308201902.GN826@saboteur.dek.spc.org> Mail-Followup-To: Andre Oppermann , Mark Tinguely , dwmalone@maths.tcd.ie, freebsd-net@freebsd.org, rizzo@icir.org References: <200403081605.i28G5arD037139@casselton.net> <404C9CF3.CBC11F30@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <404C9CF3.CBC11F30@freebsd.org> cc: dwmalone@maths.tcd.ie cc: freebsd-net@freebsd.org cc: Mark Tinguely cc: rizzo@icir.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: Mon, 08 Mar 2004 20:19:08 -0000 On Mon, Mar 08, 2004 at 05:18:59PM +0100, Andre Oppermann wrote: > > There has been the "enternal" debate, clean up the stack and/or add features > > or the resistance to commit the clean up and/or new features. > > I think these days are over and I have committed a couple of larger > changes in the IP code a couple month ago with more to come. > > So if you have new stuff, bring it on and we will judge it on its > merits and code quality. It's all good. Keep rocking FreeBSD. BMS From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 12:20: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 C5A7416A4CE for ; Mon, 8 Mar 2004 12:20:09 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9253843D1F for ; Mon, 8 Mar 2004 12:20:09 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id D5EAC6520C; Mon, 8 Mar 2004 20:20:08 +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 10101-03-6; Mon, 8 Mar 2004 20:20:08 +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 6FC2E651EB; Mon, 8 Mar 2004 20:20:08 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id B7B04DF; Mon, 8 Mar 2004 20:20:07 +0000 (GMT) Date: Mon, 8 Mar 2004 20:20:07 +0000 From: Bruce M Simpson To: Jerry Jensen Message-ID: <20040308202007.GO826@saboteur.dek.spc.org> Mail-Followup-To: Jerry Jensen , freebsd-net@freebsd.org References: <20040306221357.68128.qmail@web41813.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040306221357.68128.qmail@web41813.mail.yahoo.com> 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: Mon, 08 Mar 2004 20:20:09 -0000 On Sat, Mar 06, 2004 at 02:13:57PM -0800, Jerry Jensen 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). You can have multiple instances of lo(4) in 5.x at least, it's a cloneable driver. You can have multiple IP addresses on the same lo(4) instance as with any other IP-capable interface. BMS From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 12:21: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 8205C16A4DF for ; Mon, 8 Mar 2004 12:21:19 -0800 (PST) Received: from mail.a-quadrat.at (mail.a-quadrat.at [81.223.141.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03FFA43D39 for ; Mon, 8 Mar 2004 12:21:19 -0800 (PST) (envelope-from mbretter@a-quadrat.at) Received: from [192.168.90.200] (ras01.a-quadrat.at [192.168.90.200]) by files.a-quadrat.at (Postfix) with ESMTP id ECF715C103; Mon, 8 Mar 2004 21:21:16 +0100 (CET) Date: Mon, 8 Mar 2004 21:21:16 +0100 (CET) From: Michael Bretterklieber To: Luuk van Dijk In-Reply-To: <1078410929.255.270.camel@wonder> Message-ID: <20040308211802.N361@worf.a-quadrat.at> References: <1078406027.29725.27.camel@crazyharry> <1078410929.255.270.camel@wonder> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: ano@du.se cc: c.prevotaux@hexanet.fr cc: freebsd-net@freebsd.org Subject: Re: 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: Mon, 08 Mar 2004 20:21:19 -0000 Hi, On Thu, 4 Mar 2004, Luuk van Dijk wrote: > > 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. > great, just a short remark, if you are going to provide patches for Mpd, then please make them against the HEAD/development branch of Mpd and not against Mpd-3, because we do not have the intention making deeper changes to Mpd-3 anymore. Mpd's CVSrep is hosted on SF.net: http://sourceforge.net/projects/mpd thanx, bye, -- ------------------------------- ---------------------------------- Michael Bretterklieber - http://www.bretterklieber.com A-Quadrat Automation GmbH - http://www.a-quadrat.at Tel: ++43-(0)3172-41679 - GSM: ++43-(0)699 12861847 ------------------------------- ---------------------------------- "...the number of UNIX installations has grown to 10, with more expected..." - Dennis Ritchie and Ken Thompson, June 1972 From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 12:22: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 2047916A4CE for ; Mon, 8 Mar 2004 12:22:18 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5013E43D3F for ; Mon, 8 Mar 2004 12:22:17 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 7C24265213; Mon, 8 Mar 2004 20:22:16 +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 10101-03-9; Mon, 8 Mar 2004 20:22:15 +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 5D041651EB; Mon, 8 Mar 2004 20:22:14 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id 91F78DF; Mon, 8 Mar 2004 20:22:13 +0000 (GMT) Date: Mon, 8 Mar 2004 20:22:13 +0000 From: Bruce M Simpson To: Jerry Jensen Message-ID: <20040308202213.GP826@saboteur.dek.spc.org> Mail-Followup-To: Jerry Jensen , "."@babolo.ru, freebsd-net@freebsd.org References: <1078642138.728121.16568.nullmailer@cicuta.babolo.ru> <20040308091935.59513.qmail@web41811.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Y7xTucakfITjPcLV" Content-Disposition: inline In-Reply-To: <20040308091935.59513.qmail@web41811.mail.yahoo.com> 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: Mon, 08 Mar 2004 20:22:18 -0000 --Y7xTucakfITjPcLV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Mar 08, 2004 at 01:19:35AM -0800, Jerry Jensen wrote: > How can this be done programmatically rather than from > the command line? Code snippets would be handy. This should contain the snippets you need for instantiating cloneable interfaces, including ds(4) and lo(4). BMS --Y7xTucakfITjPcLV Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="rtmhack.c" /* $FreeBSD$ */ /* * This is a hack to demonstrate the concept of hooking for the * RTM_RESOLVE message being sent from the FreeBSD routing code, * as a means of looking up routes on demand using a routing protocol * such as AODV. * This code will probably be vastly cleaned up and tested more thoroughly * before being used as the basis for a user-space BSD AODV implementation. */ /* * Copyright (c) 2003 Bruce M. Simpson * All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * 3. All advertising materials mentioning features or use of this software * must display the following acknowledgement: * This product includes software developed by Bruce M. Simpson. * 4. Neither the name of Bruce M. Simpson nor the names of co- * contributors may be used to endorse or promote products derived * from this software without specific prior written permission. * * THIS SOFTWARE IS PROVIDED BY Bruce M. Simpson AND CONTRIBUTORS * ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED * TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL Bruce M. Simpson OR CONTRIBUTORS * BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF * SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS * INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE * POSSIBILITY OF SUCH DAMAGE. */ #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include union sockunion { struct sockaddr sa; struct sockaddr_in sin; struct sockaddr_dl sdl; struct sockaddr_storage ss; }; typedef union sockunion sockunion_t; void usage(void); int add_xresolve_route(char *ifname, struct sockaddr_in *sin, int bits); int inet_cidr_aton(char *s, struct in_addr *pin, int *bits); int create_if(char *ifname); int destroy_if(char *ifname); int if2sockaddr(char *ifname, struct sockaddr_dl *sdl); int handle_rtmsg(struct rt_msghdr *rtm, int msglen); int handle_rtmsg_resolve(struct rt_msghdr *rtm, int msglen); int reply_rtmsg_resolve(struct sockaddr_in *sin); /* * We check for the existence of ifname. */ #if 1 #define _IFNAME "disc1" #else #define _IFNAME "lo0" #endif int rtsock = -1; int created = 0; char *ifname = _IFNAME; void sighand_term(int sig) { /* * Destroying an interface is sufficient to delete the routes * pointing to it. */ if (created) destroy_if(ifname); exit(EXIT_SUCCESS); } void setup_signals(void) { struct sigaction sa, osa; sa.sa_handler = sighand_term; sa.sa_flags = 0; sigemptyset(&sa.sa_mask); sigaction(SIGTERM, &sa, &osa); sigaction(SIGINT, &sa, &osa); sigaction(SIGQUIT, &sa, &osa); sigaction(SIGKILL, &sa, &osa); } int main(int argc, char *argv[]) { int n; int bits; char msg[2048]; struct sockaddr_in sin; if (geteuid() != 0) errx(1, "must be root to alter routing table"); memset(&sin, 0, sizeof(sin)); sin.sin_family = AF_INET; sin.sin_len = sizeof(sin); /* Parse network argument */ if ((argc != 2) || (inet_cidr_aton(argv[1], &sin.sin_addr, &bits) != 1)) usage(); setup_signals(); /* Open routing socket */ rtsock = socket(PF_ROUTE, SOCK_RAW, 0); if (rtsock == -1) err(EX_OSERR, "socket"); /* Check that the target interface exists; create it if it doesn't. */ if (if_nametoindex(ifname) == 0) { warnx("interface %s does not exist, creating.", ifname); create_if(ifname); created = 1; add_xresolve_route(ifname, &sin, bits); } /* Routing event loop */ for (;;) { n = read(rtsock, msg, sizeof(msg)); handle_rtmsg((struct rt_msghdr *)msg, n); } if (rtsock != -1) close(rtsock); exit (EXIT_SUCCESS); } void usage(void) { fprintf(stderr, "usage: rtmhack \n" " specifies the test network in CIDR notation\n"); exit(EXIT_FAILURE); } /* * Like inet_aton(), but handle an optional CIDR prefix. */ int inet_cidr_aton(char *s, struct in_addr *pin, int *bits) { char *q; q = NULL; *bits = 32; if ((q = strchr(s, '/')) != NULL) { *bits = strtoul(q+1, 0, 0); *q = '\0'; } return (inet_aton(s, pin)); } /* * create an instance of a named clonable interface. * Return 0 if successful, or -1 if an error occurred. */ int create_if(char *ifname) { int s, retval; struct ifreq ifr; retval = 0; s = socket(AF_INET, SOCK_DGRAM, 0); if (s == -1) err(1, "socket"); memset(&ifr, 0, sizeof(ifr)); (void) strlcpy(ifr.ifr_name, ifname, sizeof(ifr.ifr_name)); if (ioctl(s, SIOCIFCREATE, &ifr) < 0) { retval = -1; warn("SIOCIFCREATE"); } close(s); return (retval); } /* * destroy an instance of a named clonable interface. * Return 0 if successful, or -1 if an error occurred. */ int destroy_if(char *ifname) { int s, retval; struct ifreq ifr; retval = 0; s = socket(AF_INET, SOCK_DGRAM, 0); if (s == -1) err(1, "socket"); memset(&ifr, 0, sizeof(ifr)); (void) strlcpy(ifr.ifr_name, ifname, sizeof(ifr.ifr_name)); if (ioctl(s, SIOCIFDESTROY, &ifr) < 0) { retval = -1; warn("SIOCIFDESTROY"); } close(s); return (retval); } /* * Copy the sockaddr_dl structure corresponding to the named interface * into the structure pointed to by sdl. * Returns 0 if successful, or -1 if the structure found was not valid. */ int if2sockaddr(char *ifname, struct sockaddr_dl *sdl) { struct ifaddrs *ifap, *ifa; struct sockaddr_dl *isdl; if (getifaddrs(&ifap)) err(1, "getifaddrs"); isdl = NULL; for (ifa = ifap; ifa; ifa = ifa->ifa_next) { if (ifa->ifa_addr->sa_family != AF_LINK) continue; if (strcmp(ifname, ifa->ifa_name)) continue; isdl = (struct sockaddr_dl *)ifa->ifa_addr; } if (isdl) memcpy(sdl, isdl, isdl->sdl_len); return ((isdl != NULL) ? 0 : -1); } /* * Given the prefix length of an IPv4 CIDR network address, * fill out a sockaddr_in structure accordingly for use with * BSD routing code. * * Return the value of the sin_len member as a hint. */ int inet_makenetmask(int bits, struct sockaddr_in *so_mask) { char *cp; unsigned long mask; int len; const int maxbits = 32; memset(so_mask, 0, sizeof(struct sockaddr_in)); mask = 0xFFFFFFFF << (maxbits - bits); so_mask->sin_addr.s_addr = htonl(mask); /* count number of bytes in mask containing set bits */ cp = (char *)(&so_mask->sin_addr + 1); while (*--cp == 0 && cp > (char *)&so_mask) ; so_mask->sin_len = len = 1 + cp - (char *)&so_mask; return (len); } /* * Bind an cloning XRESOLVE route, for the given network/host, * to a named interface. * * The packing of the rtm message is all important. The kernel * expects it in a certain way. This routine seems to work but * 'route monitor' is reporting some junk at the end of the netmask. * * Return 0 if successful, or -1 if an error occurred. */ int add_xresolve_route(char *ifname, struct sockaddr_in *so_dst, int bits) { #define ROUNDUP(a) \ ((a) > 0 ? (1 + (((a) - 1) | (sizeof(long) - 1))) : sizeof(long)) #define NEXTADDR(cp, l, u) \ do { \ l = (u)->sa.sa_len; \ (l) = ROUNDUP(l); \ memmove((cp), (u), (l)); \ (cp) += (l); \ } while (0) /* */ struct { struct rt_msghdr rtm; sockunion_t addrs[RTAX_MAX]; } r; sockunion_t so_iface; sockunion_t so_mask; int rlen, len, masklen; char *cp; cp = (char *)&r.addrs[0]; masklen = rlen = len = 0; memset(&r, 0, sizeof(r)); memset(&so_iface, 0, sizeof(so_iface)); memset(&so_mask, 0, sizeof(so_mask)); r.rtm.rtm_version = RTM_VERSION; r.rtm.rtm_type = RTM_ADD; r.rtm.rtm_pid = getpid(); r.rtm.rtm_seq = 0; r.rtm.rtm_flags = RTF_XRESOLVE | RTF_CLONING | RTF_UP; r.rtm.rtm_addrs = RTA_DST | RTA_GATEWAY | RTA_NETMASK; if2sockaddr(ifname, &so_iface.sdl); masklen = inet_makenetmask(bits, &so_mask.sin); NEXTADDR(cp, len, (sockunion_t *)so_dst); NEXTADDR(cp, len, &so_iface); NEXTADDR(cp, len, &so_mask); r.rtm.rtm_msglen = len = cp - (char *)&r; rlen = write(rtsock, &r, len); if (rlen < 0) warn("write"); return ((rlen > 0) ? 0 : -1); #undef NEXTADDR #undef ROUNDUP } /* * routing socket message dispatcher */ int handle_rtmsg(struct rt_msghdr *rtm, int msglen) { if (rtm->rtm_version != RTM_VERSION) { (void) printf("bad routing message version %d\n", rtm->rtm_version); return (-1); } switch (rtm->rtm_type) { case RTM_RESOLVE: (void) printf("rtm_type %d: RTM_RESOLVE\n", rtm->rtm_type); handle_rtmsg_resolve(rtm, msglen); break; default: (void) printf("rtm_type %d: ignored\n", rtm->rtm_type); } return (0); } /* * Dispatch routine for RTM_RESOLVE routing messages. * Return 0 if successful; otherwise, return -1 if an error occurred. */ int handle_rtmsg_resolve(struct rt_msghdr *rtm, int msglen) { struct sockaddr_in *sin; struct sockaddr *sa; void *sp; /* * ignore messages from ourselves */ if (rtm->rtm_pid == getpid()) { printf("heard own message, ignoring\n"); return (0); } printf("rtm_index: %04x rtm_addrs: %08x\n", rtm->rtm_index, rtm->rtm_addrs); /* * The message must contain the address for which a route is * being requested, otherwise it is invalid. */ if (!(rtm->rtm_addrs & RTA_DST)) { warnx("RTM_RESOLVE message does not contain destination"); return (-1); } sa = sp = (rtm + 1); if (sa->sa_family != AF_INET) { warnx("RTM_RESOLVE contains non-AF_INET destination %d", sa->sa_family); return (-1); } sin = (struct sockaddr_in *)sa; printf("route requested for %s\n", inet_ntoa(sin->sin_addr)); /* * XXX: Should check if the requested destination is within the * network prefix specified on the command line. */ reply_rtmsg_resolve(sin); printf("route resolved for %s\n", inet_ntoa(sin->sin_addr)); return (0); } /* * Modify a given route in response to an RTM_RESOLVE message from the kernel. * Return 0 if successful; otherwise, return -1. */ int reply_rtmsg_resolve(struct sockaddr_in *sin) { struct { struct rt_msghdr rtm; struct sockaddr addrs[RTAX_MAX]; } r; struct sockaddr_dl sdl; int len; memset(&r, 0, sizeof(r)); r.rtm.rtm_version = RTM_VERSION; r.rtm.rtm_type = RTM_CHANGE; r.rtm.rtm_pid = getpid(); r.rtm.rtm_seq = 0; if2sockaddr("lo0", &sdl); memcpy(&r.addrs[RTAX_DST], sin, sin->sin_len); memcpy(&r.addrs[RTAX_GATEWAY], &sdl, sdl.sdl_len); memset(&r.addrs[RTAX_IFP], 0, sizeof(r.addrs[RTAX_IFP])); memset(&r.addrs[RTAX_IFA], 0, sizeof(r.addrs[RTAX_IFA])); r.rtm.rtm_addrs = RTA_DST | RTA_GATEWAY | RTA_IFP | RTA_IFA; r.rtm.rtm_flags = RTF_DONE; r.rtm.rtm_msglen = sizeof(r); len = write(rtsock, &r, r.rtm.rtm_msglen); if (len != r.rtm.rtm_msglen) warn("write"); return ((len > 0) ? 0 : -1); } --Y7xTucakfITjPcLV-- From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 12:22: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 096DC16A4CE; Mon, 8 Mar 2004 12:22:19 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id E096043D3F; Mon, 8 Mar 2004 12:22:18 -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 i28KMBRH032346; Mon, 8 Mar 2004 12:22:11 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i28KMAJc032345; Mon, 8 Mar 2004 12:22:10 -0800 Date: Mon, 8 Mar 2004 12:22:10 -0800 From: Brooks Davis To: Kevin Oberman Message-ID: <20040308202210.GB485@Odin.AC.HMC.Edu> References: <404BA723.C8141806@freebsd.org> <20040308182431.4FA6D5D08@ptavv.es.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9zSXsLTf0vkW971A" Content-Disposition: inline In-Reply-To: <20040308182431.4FA6D5D08@ptavv.es.net> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: David Malone 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: Mon, 08 Mar 2004 20:22:19 -0000 --9zSXsLTf0vkW971A Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 08, 2004 at 10:24:31AM -0800, Kevin Oberman wrote: > > Date: Sun, 07 Mar 2004 23:50:11 +0100 > > From: Andre Oppermann > > Sender: owner-freebsd-current@freebsd.org > >=20 > > David Malone wrote: > > >=20 > > > On Mon, Mar 01, 2004 at 11:18:34PM +0100, Andre Oppermann wrote: > > > > [] automatically sizing TCP send buffers to achieve optimal perfor= mance > > > > over a wide range of bw*delay situations. (in progress) > > >=20 > > > Hi Andre, > > >=20 > > > This reminded me - do you know what happened to the plan to implement > > > SACK for FreeBSD? I'm working with a research group that's interested > > > in new high speed TCP techniques and they'd prefer to work with > > > FreeBSD, but they've been using Linux 'cos they need SACK. They > > > might actually be interested in spending some time implementing it, > > > if we weren't going to be clashing with anytone else. > >=20 > > I don't know of any current project or effort to implement SACK on > > FreeBSD. It is not on my todo list and it doesn't fit there. But > > I'm available if someone wants to discuss specifics and implementation > > details. >=20 > I know that our organization would love to see SACK. Much of the > high-performance network development that used to be on FreeBSD has > moved to Linux simply because SACK is essential. You can't run > trans-oceanic TCP streams of gigabit or more throughput without it. >=20 > Unfortunately, SACK is often looked upon as a waste of effort to those > who use nets in more commercial forms where aggregation of lots of small > streams is how fat pipes are used. Research big science are about the > only ones who have a real need for this kind of performance and it's > growing fast. Without SACK, FreeBSD will be a non-starter for these > purposes.=20 I've got a co-worker who is part of a research group at ISI that is doing research on long fat pipes with large streams. They are intrested in doing a SACK implementation. I hope to have some more information later this week. -- 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 --9zSXsLTf0vkW971A Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFATNXxXY6L6fI4GtQRAkfvAKDeRdh5gkJpod6C9kONe1WLloyCggCff4Bu PTTvFgTZfFHay+9RqI3DbC8= =2l/m -----END PGP SIGNATURE----- --9zSXsLTf0vkW971A-- From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 12:34: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 9948616A4CE for ; Mon, 8 Mar 2004 12:34:11 -0800 (PST) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74CE343D2F for ; Mon, 8 Mar 2004 12:34:11 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (rwcrmhc12) with ESMTP id <20040308203410014006oep0e>; Mon, 8 Mar 2004 20:34:10 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id MAA51554; Mon, 8 Mar 2004 12:34:09 -0800 (PST) Date: Mon, 8 Mar 2004 12:34:06 -0800 (PST) From: Julian Elischer To: Michael Bretterklieber In-Reply-To: <20040308211802.N361@worf.a-quadrat.at> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: ano@du.se cc: c.prevotaux@hexanet.fr cc: Luuk van Dijk cc: freebsd-net@freebsd.org Subject: Re: 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: Mon, 08 Mar 2004 20:34:11 -0000 On Mon, 8 Mar 2004, Michael Bretterklieber wrote: > Hi, > > On Thu, 4 Mar 2004, Luuk van Dijk wrote: > > > > 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. > > > great, just a short remark, if you are going to provide patches for Mpd, > then please make them against the HEAD/development branch of Mpd and not > against Mpd-3, because we do not have the intention making deeper changes > to Mpd-3 anymore. > > Mpd's CVSrep is hosted on SF.net: > http://sourceforge.net/projects/mpd this seems pretty spartan.. For example no description as to what is going on in mpd.. > > thanx, > bye, > -- > ------------------------------- ---------------------------------- > Michael Bretterklieber - http://www.bretterklieber.com > A-Quadrat Automation GmbH - http://www.a-quadrat.at > Tel: ++43-(0)3172-41679 - GSM: ++43-(0)699 12861847 > ------------------------------- ---------------------------------- > "...the number of UNIX installations has grown to 10, with more > expected..." - Dennis Ritchie and Ken Thompson, June 1972 > _______________________________________________ > 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 8 12:37: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 0D0B716A4CE for ; Mon, 8 Mar 2004 12:37:56 -0800 (PST) Received: from mail.a-quadrat.at (mail.a-quadrat.at [81.223.141.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF7D143D31 for ; Mon, 8 Mar 2004 12:37:55 -0800 (PST) (envelope-from mbretter@a-quadrat.at) Received: from [192.168.90.200] (ras01.a-quadrat.at [192.168.90.200]) by files.a-quadrat.at (Postfix) with ESMTP id 421945CB2D; Mon, 8 Mar 2004 21:37:54 +0100 (CET) Date: Mon, 8 Mar 2004 21:37:53 +0100 (CET) From: Michael Bretterklieber To: Julian Elischer In-Reply-To: Message-ID: <20040308213450.R361@worf.a-quadrat.at> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: ano@du.se cc: c.prevotaux@hexanet.fr cc: Luuk van Dijk cc: freebsd-net@freebsd.org Subject: Re: 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: Mon, 08 Mar 2004 20:37:56 -0000 Hi, On Mon, 8 Mar 2004, Julian Elischer wrote: > > this seems pretty spartan.. For example no description as to what > is going on in mpd.. Currently we are working on Mpd-4, wich is Mpd-3 + libpdel, currently there are no functional changes, we "just" replaced some subsystems of Mpd with the ones provided by libpdel: typed_mem, alog, pevent The only new feature is the EAP-support. bye, -- ------------------------------- ---------------------------------- Michael Bretterklieber - http://www.bretterklieber.com A-Quadrat Automation GmbH - http://www.a-quadrat.at Tel: ++43-(0)3172-41679 - GSM: ++43-(0)699 12861847 ------------------------------- ---------------------------------- "...the number of UNIX installations has grown to 10, with more expected..." - Dennis Ritchie and Ken Thompson, June 1972 From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 12:56: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 667F616A4CE for ; Mon, 8 Mar 2004 12:56:41 -0800 (PST) Received: from kraid.nerim.net (smtp-101-monday.nerim.net [62.4.16.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id C106943D2F for ; Mon, 8 Mar 2004 12:56:40 -0800 (PST) (envelope-from eberkut@minithins.net) Received: from lotus.plug-it.com (lotus.plug-it.com [62.212.108.163]) by kraid.nerim.net (Postfix) with ESMTP id D92C8418A0; Mon, 8 Mar 2004 21:56:37 +0100 (CET) Received: by lotus.plug-it.com (Postfix, from userid 11) id A2179402C; Mon, 8 Mar 2004 21:57:07 +0100 (CET) X-Scanned-By: Plug-It Antivirus System. Received: from mail.plug-it.com (localhost.nerim.net [127.0.0.1]) by lotus.plug-it.com (Postfix) with SMTP id A80A54021; Mon, 8 Mar 2004 21:57:03 +0100 (CET) Received: from eberkut.adsl.speka.net ([213.41.155.24]) (SquirrelMail authenticated user eberkut) by mail.plug-it.com with HTTP; Mon, 8 Mar 2004 21:57:03 +0100 (CET) Message-ID: <3522.213.41.155.24.1078779423.squirrel@mail.plug-it.com> In-Reply-To: <200403072022.51630.jbarrett@amduat.net> References: <200403072022.51630.jbarrett@amduat.net> Date: Mon, 8 Mar 2004 21:57:03 +0100 (CET) From: "eberkut" To: "Jacob S. Barrett" User-Agent: SquirrelMail/1.4.0 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=0.15.13 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on lotus.plug-it.com X-Spam-Status: No, hits=1.2 required=4.0 tests=PRIORITY_NO_NAME autolearn=no version=2.63 X-Spam-Level: * cc: freebsd-net@freebsd.org Subject: Re: Solution for Resilient VLAN Trunk Bonding X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: eberkut@minithins.net List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Mar 2004 20:56:41 -0000 > I would have liked to have used either ng_fec or ng_one2many, but neither > of them detects link failures. According to the original ng_fec announcement [1] on freebsd-net, ng_fec should be able to detect link failure by checking the interfaces in the bundle once every second. Even though I don't "speak" C fluently, I think ng_fec_tick in ng_fec.c [2] should do the trick. [1] http://docs.freebsd.org/cgi/getmsg.cgi?fetch=448009+0+archive/2001/freebsd-net/20010211.freebsd-net [2] http://fxr.watson.org/fxr/source/netgraph/ng_fec.c --vjm "you can tune a file system but you can't tune a fish" (man 8 tunefs, BUGS) From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 13:02:56 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02C8516A4CE for ; Mon, 8 Mar 2004 13:02:55 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AF7843D2F for ; Mon, 8 Mar 2004 13:02:55 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 6DF72654CC for ; Mon, 8 Mar 2004 21:02:54 +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 10670-03 for ; Mon, 8 Mar 2004 21:02:54 +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 0332F654C3 for ; Mon, 8 Mar 2004 21:02:54 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id D9C97DF; Mon, 8 Mar 2004 21:02:52 +0000 (GMT) Date: Mon, 8 Mar 2004 21:02:52 +0000 From: Bruce M Simpson To: freebsd-net@freebsd.org Message-ID: <20040308210252.GS826@saboteur.dek.spc.org> Mail-Followup-To: freebsd-net@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: mpd as PPPoA with NATM 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: Mon, 08 Mar 2004 21:02:56 -0000 Has anybody tried mpd with a NATM interface yet? BMS From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 13:22: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 787EA16A4CE; Mon, 8 Mar 2004 13:22:58 -0800 (PST) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C97C43D31; Mon, 8 Mar 2004 13:22:58 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) i28LMubj052570; Mon, 8 Mar 2004 13:22:56 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)i28LMudb052569; Mon, 8 Mar 2004 13:22:56 -0800 (PST) (envelope-from sgk) Date: Mon, 8 Mar 2004 13:22:55 -0800 From: Steve Kargl To: Brooks Davis Message-ID: <20040308212255.GA52526@troutmask.apl.washington.edu> References: <404BA723.C8141806@freebsd.org> <20040308182431.4FA6D5D08@ptavv.es.net> <20040308202210.GB485@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040308202210.GB485@Odin.AC.HMC.Edu> User-Agent: Mutt/1.4.1i cc: David Malone cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: Andre Oppermann cc: Kevin Oberman 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, 08 Mar 2004 21:22:58 -0000 On Mon, Mar 08, 2004 at 12:22:10PM -0800, Brooks Davis wrote: > On Mon, Mar 08, 2004 at 10:24:31AM -0800, Kevin Oberman wrote: > > > > Unfortunately, SACK is often looked upon as a waste of effort to those > > who use nets in more commercial forms where aggregation of lots of small > > streams is how fat pipes are used. Research big science are about the > > only ones who have a real need for this kind of performance and it's > > growing fast. Without SACK, FreeBSD will be a non-starter for these > > purposes. > > I've got a co-worker who is part of a research group at ISI that > is doing research on long fat pipes with large streams. They are > intrested in doing a SACK implementation. I hope to have some more > information later this week. > Has anyone looked at Luigi's stuff? http://info.iet.unipi.it/~luigi/sack.html The page states that Luigi had SACK available in FreeBSD 2.1R, which was released 8 years ago. -- Steve From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 13:26: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 8442816A4CE; Mon, 8 Mar 2004 13:26:41 -0800 (PST) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1CCA43D31; Mon, 8 Mar 2004 13:26:39 -0800 (PST) (envelope-from ru@ip.net.ua) Received: from heffalump.office.ipnet (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.10/8.12.9) with ESMTP id i28LU31t035736 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Mar 2004 23:30:04 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.office.ipnet (8.12.11/8.12.11) id i28LQYLw030427; Mon, 8 Mar 2004 23:26:34 +0200 (EET) (envelope-from ru) Date: Mon, 8 Mar 2004 23:26:34 +0200 From: Ruslan Ermilov To: Andre Oppermann Message-ID: <20040308212634.GA30394@ip.net.ua> References: <20040308102038.GA28502@ip.net.ua> <404C5F65.446E20A8@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SLDf9lqlvOQaIe6s" Content-Disposition: inline In-Reply-To: <404C5F65.446E20A8@freebsd.org> 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: Cached IP routes 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, 08 Mar 2004 21:26:41 -0000 --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 08, 2004 at 12:56:21PM +0100, Andre Oppermann wrote: [...] > > We still have a similar problem in in_gif_output(), and I wonder what > > would be a correct fix, given the above? >=20 > in_gif_output() is not the same as the route cache of ip_forward. It > just caches the route to the tunnel destination which normally stays > the same over long periods of time. The only problem you might run > into are route changes. At one point in time your best path is the > default route so a pointer to it is being cached in sc->gif_ro. Later > you have a better via some other gateway. This won't be picked up by > the gif route cache. In 5.2 and -CURRENT you can scrap the route > cache and just give a NULL to ip_output instead of a route. This way > you will always use the best path to destination. >=20 Yes, that's exactly the situation I'm faced with (yes, I know how the routing code works). For others. Initially, the route to the gif(4) tunnel's destination is through the default route. I then add an explicit host route to the tunnel destination, and "route change default" to point to the tunnel (gif0). The result is that in_gif_output() caches the default route as the route to "tunnel destination", and doesn't pick up the "best match" host route. Of course, I'm working around this by deleting and re-adding the default route, but I wonder what in your opinion would be the correct fix. As you properly mentioned, in_gif_output() is significantly different from ip_forward() because the rt_dst is always the same. Cheers, --=20 Ruslan Ermilov FreeBSD committer ru@FreeBSD.org --SLDf9lqlvOQaIe6s Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFATOUKUkv4P6juNwoRAjKpAJ9gZm8l/aJi24oAKbM4fp5/9t0YzQCdHbYx 2U4h1bKjXP/azNW2UNG/zuk= =xGAN -----END PGP SIGNATURE----- --SLDf9lqlvOQaIe6s-- From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 13:29:47 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1728C16A4CE; Mon, 8 Mar 2004 13:29:47 -0800 (PST) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B87043D2F; Mon, 8 Mar 2004 13:29:46 -0800 (PST) (envelope-from ru@ip.net.ua) Received: from heffalump.office.ipnet (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.10/8.12.9) with ESMTP id i28LX81t035811 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Mar 2004 23:33:10 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.office.ipnet (8.12.11/8.12.11) id i28LTdLO030451; Mon, 8 Mar 2004 23:29:39 +0200 (EET) (envelope-from ru) Date: Mon, 8 Mar 2004 23:29:39 +0200 From: Ruslan Ermilov To: Gleb Smirnoff , julian@freebsd.org, archie@freebsd.org, freebsd-net@freebsd.org Message-ID: <20040308212939.GB30394@ip.net.ua> References: <200403072302.i27N2StR008804@freefall.freebsd.org> <20040308102033.GA66247@cell.sick.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IrhDeMKUP4DT/M7F" Content-Disposition: inline In-Reply-To: <20040308102033.GA66247@cell.sick.ru> User-Agent: Mutt/1.5.6i X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: Re: kern/63864: [patch] new control message for ng_iface(4) - getifindex 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, 08 Mar 2004 21:29:47 -0000 --IrhDeMKUP4DT/M7F Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 08, 2004 at 01:20:33PM +0300, Gleb Smirnoff wrote: > On Sun, Mar 07, 2004 at 03:02:28PM -0800, Ruslan Ermilov wrote: > R> Synopsis: [patch] new control message for ng_iface(4) - getifindex > R>=20 > R> State-Changed-From-To: open->closed > R> State-Changed-By: ru > R> State-Changed-When: Sun Mar 7 15:01:03 PST 2004 > R> State-Changed-Why:=20 > R> Committed with tiny modifications, thanks! >=20 > I have one more idea. Currently we have got 3 interface nodes: ng_ether= , ng_iface, > ng_eiface. 2 of them already support "getifindex" message, imagine I (or = someone else) send > you patch tomorrow, which adds support to ng_eiface. OK, now all three su= pport. May be > in future some new interface nodes will be developed. >=20 > Imagine the following: you have node, which is connected to some generic > interface (it doesn't know which node type exactly). This node wants to > determine interface index of attached interfac. It would send 3 "getifind= ex" messages with 3 > different cookies. Two of messages will always fail, and one return. This= is not nice. >=20 > What I suggest: create a new semi-generic cookie NGM_GENERICIFACE_COOKIE,= which will be > supported by all interface nodes. Put NGM_GENERICIFACE_GETIFINDEX message= under > NGM_GENERICIFACE_COOKIE case brackets. If you like this idea, please repl= y me. And I'll send > patches. >=20 How do you think "ngctl msg ng0: getifindex" works? ;) Cheers, --=20 Ruslan Ermilov FreeBSD committer ru@FreeBSD.org --IrhDeMKUP4DT/M7F Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFATOXDUkv4P6juNwoRAjcsAJ9iG7fvCw5klJ7niMNWHiy74YxEfwCfS/hg Z0+iqydq1wo52dqKXojhq4A= =7B7V -----END PGP SIGNATURE----- --IrhDeMKUP4DT/M7F-- From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 13:37: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 DD80B16A4CF; Mon, 8 Mar 2004 13:37:23 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDB3643D1F; Mon, 8 Mar 2004 13:37:23 -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 i28LbIRH015506; Mon, 8 Mar 2004 13:37:18 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i28LbIHv015505; Mon, 8 Mar 2004 13:37:18 -0800 Date: Mon, 8 Mar 2004 13:37:18 -0800 From: Brooks Davis To: Steve Kargl Message-ID: <20040308213718.GC485@Odin.AC.HMC.Edu> References: <404BA723.C8141806@freebsd.org> <20040308182431.4FA6D5D08@ptavv.es.net> <20040308202210.GB485@Odin.AC.HMC.Edu> <20040308212255.GA52526@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1SQmhf2mF2YjsYvc" Content-Disposition: inline In-Reply-To: <20040308212255.GA52526@troutmask.apl.washington.edu> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: Andre Oppermann cc: Kevin Oberman cc: freebsd-net@freebsd.org cc: David Malone 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: Mon, 08 Mar 2004 21:37:24 -0000 --1SQmhf2mF2YjsYvc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 08, 2004 at 01:22:55PM -0800, Steve Kargl wrote: > On Mon, Mar 08, 2004 at 12:22:10PM -0800, Brooks Davis wrote: > > On Mon, Mar 08, 2004 at 10:24:31AM -0800, Kevin Oberman wrote: > > >=20 > > > Unfortunately, SACK is often looked upon as a waste of effort to those > > > who use nets in more commercial forms where aggregation of lots of sm= all > > > streams is how fat pipes are used. Research big science are about the > > > only ones who have a real need for this kind of performance and it's > > > growing fast. Without SACK, FreeBSD will be a non-starter for these > > > purposes.=20 > >=20 > > I've got a co-worker who is part of a research group at ISI that > > is doing research on long fat pipes with large streams. They are > > intrested in doing a SACK implementation. I hope to have some more > > information later this week. > >=20 >=20 > Has anyone looked at Luigi's stuff? >=20 > http://info.iet.unipi.it/~luigi/sack.html >=20 > The page states that Luigi had SACK available in FreeBSD 2.1R, > which was released 8 years ago. There are at least three implementations out there. The big issue is actually getting them brought up to current and committed. There may have also been come cultural resistance in the past, but lack of a version that actually applies to the head of the development branch is always a deal-killer. -- 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 --1SQmhf2mF2YjsYvc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFATOeMXY6L6fI4GtQRAggTAJwJc0ZdxLuw2QtgzrJA1mLWztMpPQCgsLWa dOS/2bjyBE3EIcBehsdo0yc= =/Wvo -----END PGP SIGNATURE----- --1SQmhf2mF2YjsYvc-- From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 13:40: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 A215C16A4CE; Mon, 8 Mar 2004 13:40:21 -0800 (PST) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87C8843D46; Mon, 8 Mar 2004 13:40:21 -0800 (PST) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Mon, 08 Mar 2004 13:40:20 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 73C245D07; Mon, 8 Mar 2004 13:40:20 -0800 (PST) To: Steve Kargl In-reply-to: Your message of "Mon, 08 Mar 2004 13:22:55 PST." <20040308212255.GA52526@troutmask.apl.washington.edu> Date: Mon, 08 Mar 2004 13:40:20 -0800 From: "Kevin Oberman" Message-Id: <20040308214020.73C245D07@ptavv.es.net> cc: David Malone 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: Mon, 08 Mar 2004 21:40:21 -0000 > Date: Mon, 8 Mar 2004 13:22:55 -0800 > From: Steve Kargl > > On Mon, Mar 08, 2004 at 12:22:10PM -0800, Brooks Davis wrote: > > On Mon, Mar 08, 2004 at 10:24:31AM -0800, Kevin Oberman wrote: > > > > > > Unfortunately, SACK is often looked upon as a waste of effort to those > > > who use nets in more commercial forms where aggregation of lots of small > > > streams is how fat pipes are used. Research big science are about the > > > only ones who have a real need for this kind of performance and it's > > > growing fast. Without SACK, FreeBSD will be a non-starter for these > > > purposes. > > > > I've got a co-worker who is part of a research group at ISI that > > is doing research on long fat pipes with large streams. They are > > intrested in doing a SACK implementation. I hope to have some more > > information later this week. > > > > Has anyone looked at Luigi's stuff? > > http://info.iet.unipi.it/~luigi/sack.html > > The page states that Luigi had SACK available in FreeBSD 2.1R, > which was released 8 years ago. I am aware of at least 3 implementations of SACK for FreeBSD over the years, none of which ever made it into the system. At least one of the people who submitted a patch (his was for 2.2) also provided some significant enhancements to one of the GigE drivers that was done with DOE funding to support the LBNL developed BRO IDS, but which were globally beneficial. In both cases, the patches were ignored by those with commit bits and the person who did the work says that he will no longer bother to submit his work to FreeBSD. I was not using FreeBSD at the time that this happened, so I don't know what, if any, objections were raised to the GigE patches, but I have since seen SACK disparaged by others as a waste of time that is not really needed. Obviously they have no interest in >Gbps streams where we have an interest in >20Gbps streams. I'm not trying to stat a flame war here, but it is frustrating and this initiative for a major network code overhaul makes me hope that something will actually happen. It's just that FreeBSD's network stack was once the best around and it's simply not today. Andre's proposal could go a LONG way toward fixing this and I am eagerly looking forward to if! -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 13:41: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 A95C516A4CE for ; Mon, 8 Mar 2004 13:41:32 -0800 (PST) Received: from bragi.housing.ufl.edu (bragi.housing.ufl.edu [128.227.47.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DA0843D49 for ; Mon, 8 Mar 2004 13:41:32 -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: Mon, 8 Mar 2004 16:41:30 -0500 Message-ID: <0E972CEE334BFE4291CD07E056C76ED802E867D7@bragi.housing.ufl.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Solution for Resilient VLAN Trunk Bonding Thread-Index: AcQFT+YnJhJyOdxtTYuov4a1RtfV0QABhuaA From: "Will Saxon" To: , "Jacob S. Barrett" cc: freebsd-net@freebsd.org Subject: RE: Solution for Resilient VLAN Trunk Bonding 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, 08 Mar 2004 21:41:32 -0000 > -----Original Message----- > From: eberkut [mailto:eberkut@minithins.net] > Sent: Monday, March 08, 2004 3:57 PM > To: Jacob S. Barrett > Cc: freebsd-net@freebsd.org > Subject: Re: Solution for Resilient VLAN Trunk Bonding >=20 >=20 > > I would have liked to have used either ng_fec or=20 > ng_one2many, but neither > > of them detects link failures. >=20 > According to the original ng_fec announcement [1] on=20 > freebsd-net, ng_fec > should be able to detect link failure by checking the=20 > interfaces in the > bundle once every second. >=20 > Even though I don't "speak" C fluently, I think ng_fec_tick=20 > in ng_fec.c > [2] should do the trick. >=20 > [1] > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D448009+0+archive/ > 2001/freebsd-net/20010211.freebsd-net > [2] http://fxr.watson.org/fxr/source/netgraph/ng_fec.c Regardless, it doesn't look like ng_fec can work with ng_vlan, since it doesn't provide any hooks to work with. -Will From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 13:48: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 0D2D816A4CE; Mon, 8 Mar 2004 13:48:24 -0800 (PST) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 502B243D2F; Mon, 8 Mar 2004 13:48:23 -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 i28LmKQE068873 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Mar 2004 00:48:21 +0300 (MSK) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.9/8.12.6/Submit) id i28LmKHL068872; Tue, 9 Mar 2004 00:48:20 +0300 (MSK) Date: Tue, 9 Mar 2004 00:48:20 +0300 From: Gleb Smirnoff To: Ruslan Ermilov Message-ID: <20040308214820.GA68803@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Ruslan Ermilov , julian@freebsd.org, archie@freebsd.org, freebsd-net@freebsd.org References: <200403072302.i27N2StR008804@freefall.freebsd.org> <20040308102033.GA66247@cell.sick.ru> <20040308212939.GB30394@ip.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20040308212939.GB30394@ip.net.ua> User-Agent: Mutt/1.5.6i cc: freebsd-net@freebsd.org Subject: Re: kern/63864: [patch] new control message for ng_iface(4) - getifindex 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, 08 Mar 2004 21:48:24 -0000 On Mon, Mar 08, 2004 at 11:29:39PM +0200, Ruslan Ermilov wrote: R> > I have one more idea. Currently we have got 3 interface nodes: ng_ether, ng_iface, R> > ng_eiface. 2 of them already support "getifindex" message, imagine I (or someone else) send R> > you patch tomorrow, which adds support to ng_eiface. OK, now all three support. May be R> > in future some new interface nodes will be developed. R> > R> > Imagine the following: you have node, which is connected to some generic R> > interface (it doesn't know which node type exactly). This node wants to R> > determine interface index of attached interfac. It would send 3 "getifindex" messages with 3 R> > different cookies. Two of messages will always fail, and one return. This is not nice. R> > R> > What I suggest: create a new semi-generic cookie NGM_GENERICIFACE_COOKIE, which will be R> > supported by all interface nodes. Put NGM_GENERICIFACE_GETIFINDEX message under R> > NGM_GENERICIFACE_COOKIE case brackets. If you like this idea, please reply me. And I'll send R> > patches. R> > R> How do you think "ngctl msg ng0: getifindex" works? ;) So, you suggest to use ASCII message in situation described above? IMHO, ASCII messages were invented for human interface purposes, not for node interaction. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 14:36: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 8EB8916A4CE; Mon, 8 Mar 2004 14:36:00 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0963943D1F; Mon, 8 Mar 2004 14:36:00 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 4A37D65476; Mon, 8 Mar 2004 22:35:58 +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 11820-01-6; Mon, 8 Mar 2004 22:35:57 +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 4335E653D4; Mon, 8 Mar 2004 22:35:57 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id 1790BDF; Mon, 8 Mar 2004 22:35:55 +0000 (GMT) Date: Mon, 8 Mar 2004 22:35:55 +0000 From: Bruce M Simpson To: Kevin Oberman Message-ID: <20040308223555.GY826@saboteur.dek.spc.org> Mail-Followup-To: Kevin Oberman , Steve Kargl , David Malone , freebsd-current@freebsd.org, Andre Oppermann , freebsd-net@freebsd.org References: <20040308212255.GA52526@troutmask.apl.washington.edu> <20040308214020.73C245D07@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040308214020.73C245D07@ptavv.es.net> cc: David Malone cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: Andre Oppermann cc: Steve Kargl 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, 08 Mar 2004 22:36:00 -0000 On Mon, Mar 08, 2004 at 01:40:20PM -0800, Kevin Oberman wrote: > I'm not trying to stat a flame war here, but it is frustrating and this > initiative for a major network code overhaul makes me hope that > something will actually happen. It's just that FreeBSD's network stack > was once the best around and it's simply not today. Andre's proposal > could go a LONG way toward fixing this and I am eagerly looking forward > to if! We're definitely playing catchup in the feature stakes. Protests have not fallen on deaf ears, but we all have things to do. Rest assured some of this is on my TODO as well. BMS From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 15:26: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 D2EAD16A4CE; Mon, 8 Mar 2004 15:26:09 -0800 (PST) Received: from mtaw6.prodigy.net (mtaw6.prodigy.net [64.164.98.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8DC243D1F; Mon, 8 Mar 2004 15:26:09 -0800 (PST) (envelope-from hsu@freebsd.org) Received: from freebsd.org (adsl-63-193-112-125.dsl.snfc21.pacbell.net [63.193.112.125]) by mtaw6.prodigy.net (8.12.10/8.12.10) with ESMTP id i28NPAa3010399; Mon, 8 Mar 2004 15:25:10 -0800 (PST) Message-Id: <200403082325.i28NPAa3010399@mtaw6.prodigy.net> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: freebsd-net@freebsd.org In-Reply-To: Message from Luigi Rizzo of "Mon, 08 Mar 2004 10:56:42 PST." <20040308105641.A47564@xorpc.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Mar 2004 15:32:37 -0800 From: Jeffrey Hsu cc: freebsd-current@freebsd.org Subject: Who wants SACK? (Re: 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: Mon, 08 Mar 2004 23:26:10 -0000 >> I know that our organization would love to see SACK. Much of the >> high-performance network development that used to be on FreeBSD has >> moved to Linux simply because SACK is essential. You can't run >> trans-oceanic TCP streams of gigabit or more throughput without it. > > Whenever i hear these comments, i am very annoyed at one thing > (which in a smaller scale repeats all over the place): > people are more than happy to spend big money for things like > routers or bandwidth or any kind of "commercial" stuff, but when > it comes to open source it must be free or nothing. > > I hope it is clear to everyone that an investment in the 50K$ > range would provide a professional-grade implementation of SACK > for FreeBSD, and this money is in the noise for any organization > that uses trans-oceanic gigabit links. > The fact that nobody seems to care about funding such a work > either means that whatever is available already fits their What Luigi says is absolutely correct. It doesn't take a lot to get this done. I've talked to a number of companies about implementing SACK for them and while there was interest, no one wanted to fund it all themselves, potentially for the benefit of their competitors. I know of two that went and did it themselves for FreeBSD --- one of which did it wrong and saw zero benefit from SACK and another that did it right, but are keeping it proprietary as an edge. Given that Linux and Windows already have it, these and the multiple past efforts collectively seem like an unnecessary duplication of work. Perhaps if we could pool enough interest, we can raise enough to put this issue to rest once and for all. Jeffrey From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 15:32: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 B95CD16A4CE; Mon, 8 Mar 2004 15:32:31 -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 957D643D1D; Mon, 8 Mar 2004 15:32:31 -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 CB06A2F8F9; Mon, 8 Mar 2004 18:07:53 -0500 (EST) Date: Mon, 8 Mar 2004 18:07:53 -0500 From: James To: Andre Oppermann Message-ID: <20040308230753.GA84279@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: 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: Mon, 08 Mar 2004 23:32:31 -0000 one feedback I can provide to this patch... under [any] interface checks (the loose check mode), if the route is pointed toward a discard interface (e.g. ds0 in freebsd, Null0 in cisco), drop the packet. under cisco, route pointed to null0 creates a null adjacency, even under loose-check mode, causing cef to drop the packets originated with source of the said route. -J On Fri, Mar 05, 2004 at 10:31:35PM +0100, Andre Oppermann wrote: > 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 -- 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 8 15:38: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 244EC16A4CE; Mon, 8 Mar 2004 15:38:09 -0800 (PST) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA11543D31; Mon, 8 Mar 2004 15:38:08 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (sccrmhc12) with ESMTP id <2004030823380601200isbuae>; Mon, 8 Mar 2004 23:38:07 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id PAA53440; Mon, 8 Mar 2004 15:38:05 -0800 (PST) Date: Mon, 8 Mar 2004 15:38:04 -0800 (PST) From: Julian Elischer To: Kevin Oberman In-Reply-To: <20040308214020.73C245D07@ptavv.es.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: David Malone cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: Andre Oppermann cc: Steve Kargl 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, 08 Mar 2004 23:38:09 -0000 On Mon, 8 Mar 2004, Kevin Oberman wrote: > > Date: Mon, 8 Mar 2004 13:22:55 -0800 > > From: Steve Kargl > > > > On Mon, Mar 08, 2004 at 12:22:10PM -0800, Brooks Davis wrote: > > > On Mon, Mar 08, 2004 at 10:24:31AM -0800, Kevin Oberman wrote: > > > > > > > > Unfortunately, SACK is often looked upon as a waste of effort to those > > > > who use nets in more commercial forms where aggregation of lots of small > > > > streams is how fat pipes are used. Research big science are about the > > > > only ones who have a real need for this kind of performance and it's > > > > growing fast. Without SACK, FreeBSD will be a non-starter for these > > > > purposes. > > > > > > I've got a co-worker who is part of a research group at ISI that > > > is doing research on long fat pipes with large streams. They are > > > intrested in doing a SACK implementation. I hope to have some more > > > information later this week. > > > > > > > Has anyone looked at Luigi's stuff? > > > > http://info.iet.unipi.it/~luigi/sack.html > > > > The page states that Luigi had SACK available in FreeBSD 2.1R, > > which was released 8 years ago. > > I am aware of at least 3 implementations of SACK for FreeBSD over the > years, none of which ever made it into the system. At least one of the > people who submitted a patch (his was for 2.2) also provided some > significant enhancements to one of the GigE drivers that was done with > DOE funding to support the LBNL developed BRO IDS, but which were > globally beneficial. > > In both cases, the patches were ignored by those with commit bits and > the person who did the work says that he will no longer bother to submit > his work to FreeBSD. I was not using FreeBSD at the time that this > happened, so I don't know what, if any, objections were raised to the > GigE patches, but I have since seen SACK disparaged by others as a waste > of time that is not really needed. Obviously they have no interest in > >Gbps streams where we have an interest in >20Gbps streams. I believe that sme of the patches were considerred "experimental and just lacked someone to make them production quality. In other cases they were not against 'current' and porting them to -curren twas left as "an exercise for the reader". No-one who had that ime had a need for them. > > I'm not trying to stat a flame war here, but it is frustrating and this > initiative for a major network code overhaul makes me hope that > something will actually happen. It's just that FreeBSD's network stack > was once the best around and it's simply not today. Andre's proposal > could go a LONG way toward fixing this and I am eagerly looking forward > to if! > -- > R. Kevin Oberman, Network Engineer > Energy Sciences Network (ESnet) > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > E-mail: oberman@es.net Phone: +1 510 486-8634 > _______________________________________________ > 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 8 15:39: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 560CD16A4CE for ; Mon, 8 Mar 2004 15:39:56 -0800 (PST) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18D1443D1D for ; Mon, 8 Mar 2004 15:39:56 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (sccrmhc11) with ESMTP id <2004030823395401100jpcele>; Mon, 8 Mar 2004 23:39:55 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id PAA53471; Mon, 8 Mar 2004 15:39:53 -0800 (PST) Date: Mon, 8 Mar 2004 15:39:53 -0800 (PST) From: Julian Elischer To: Will Saxon In-Reply-To: <0E972CEE334BFE4291CD07E056C76ED802E867D7@bragi.housing.ufl.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: eberkut@minithins.net cc: freebsd-net@freebsd.org Subject: RE: Solution for Resilient VLAN Trunk Bonding 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, 08 Mar 2004 23:39:56 -0000 On Mon, 8 Mar 2004, Will Saxon wrote: > > > > -----Original Message----- > > From: eberkut [mailto:eberkut@minithins.net] > > Sent: Monday, March 08, 2004 3:57 PM > > To: Jacob S. Barrett > > Cc: freebsd-net@freebsd.org > > Subject: Re: Solution for Resilient VLAN Trunk Bonding > > > > > > > I would have liked to have used either ng_fec or > > ng_one2many, but neither > > > of them detects link failures. > > > > According to the original ng_fec announcement [1] on > > freebsd-net, ng_fec > > should be able to detect link failure by checking the > > interfaces in the > > bundle once every second. > > > > Even though I don't "speak" C fluently, I think ng_fec_tick > > in ng_fec.c > > [2] should do the trick. > > > > [1] > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=448009+0+archive/ > > 2001/freebsd-net/20010211.freebsd-net > > [2] http://fxr.watson.org/fxr/source/netgraph/ng_fec.c > > Regardless, it doesn't look like ng_fec can work with ng_vlan, since > it doesn't provide any hooks to work with. > It could be rewritten to be a real netgraph node but I don't have teh time to do it.. > -Will > _______________________________________________ > 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 8 17:12: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 91A1716A4CF for ; Mon, 8 Mar 2004 17:12:31 -0800 (PST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BED043D2F for ; Mon, 8 Mar 2004 17:12:31 -0800 (PST) (envelope-from mlaier@vampire.homelinux.org) Received: from [212.227.126.208] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1B0VnK-000615-00 for net@freebsd.org; Tue, 09 Mar 2004 02:12:30 +0100 Received: from [217.227.158.24] (helo=vampire.homelinux.org) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1B0VnK-0003hz-00 for net@freebsd.org; Tue, 09 Mar 2004 02:12:30 +0100 Received: (qmail 87435 invoked by uid 1001); 9 Mar 2004 01:19:08 -0000 Date: Tue, 9 Mar 2004 02:19:08 +0100 From: Max Laier To: current@freebsd.org Message-ID: <20040309011908.GA87400@router.laiers.local> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Dxnq1zWXvFF0Q93v" Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:e28873fbe4dbe612ce62ab869898ff08 cc: net@freebsd.org Subject: HEADS UP: pf linked to the build/install now 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, 09 Mar 2004 01:12:31 -0000 --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, as you may have seen pf is now linked to the build and can be installed from the base system. Make sure to run `mergemaster -p' before the installworld as it requires two additional user accounts/groups. If you do not want to build/install pf you can use the NO_PF knob in /etc/make.conf For the moment you will have troubles with pflog and tcpdump as we are waiting for a vendor branch update of tcpdump/libpcap. To build a kernel that supports pf you have to add at least: options PFIL_HOOKS device pf to the GENERIC kernel configuration. Optional you can use: device pflog device pfsync to build-in logging and syncing. Note that it is currently not possible to pull in these in as a module right now. However it is possible to use pf as a module. To do this you must add the following to GENERIC: options PFIL_HOOKS options RANDOM_IP_ID already existing in GENERIC, but also required by pf as a module: options INET options INET6 device bpf These requirements can be tweaked by editing the modules/pf* Makefiles. I hope you have fun with pf and can make good use of it. Report problems, errors and questions to me or the pf-mailing-list pf4freebsd@freelists.org (see http://pf4freebsd.love2party.net/ for details) I'd try to avoid flooding -net or -current with pf related questions. There might be a freebsd-pf mailing-list some time soon. --=20 Best regards, | mlaier@freebsd.org Max Laier | ICQ #67774661 http://pf4freebsd.love2party.net/ | mlaier@EFnet --Dxnq1zWXvFF0Q93v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFATRuLXyyEoT62BG0RAmuwAJ9/KmCiBkcafER3+KN6PJUK0pv6tACbB2Z8 anvNWTormH9yP0rpDICP6L8= =8QGq -----END PGP SIGNATURE----- --Dxnq1zWXvFF0Q93v-- From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 17: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 0065916A4CE; Mon, 8 Mar 2004 17:20:40 -0800 (PST) Received: from mtaw6.prodigy.net (mtaw6.prodigy.net [64.164.98.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD05A43D2F; Mon, 8 Mar 2004 17:20:39 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (5ead709bfe1a409c6e62a1f95dc87325@adsl-67-119-53-203.dsl.lsan03.pacbell.net [67.119.53.203]) by mtaw6.prodigy.net (8.12.10/8.12.10) with ESMTP id i291Jda3024549; Mon, 8 Mar 2004 17:19:40 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id AC6495139C; Mon, 8 Mar 2004 17:20:38 -0800 (PST) Date: Mon, 8 Mar 2004 17:20:38 -0800 From: Kris Kennaway To: Jeffrey Hsu Message-ID: <20040309012038.GA17083@xor.obsecurity.org> References: <20040308105641.A47564@xorpc.icir.org> <200403082325.i28NPAa3010399@mtaw6.prodigy.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC" Content-Disposition: inline In-Reply-To: <200403082325.i28NPAa3010399@mtaw6.prodigy.net> User-Agent: Mutt/1.4.2.1i cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Who wants SACK? (Re: 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: Tue, 09 Mar 2004 01:20:40 -0000 --wRRV7LY7NUeQGEoC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 08, 2004 at 03:32:37PM -0800, Jeffrey Hsu wrote: > >> I know that our organization would love to see SACK. Much of the > >> high-performance network development that used to be on FreeBSD has > >> moved to Linux simply because SACK is essential. You can't run > >> trans-oceanic TCP streams of gigabit or more throughput without it. > > > > Whenever i hear these comments, i am very annoyed at one thing > > (which in a smaller scale repeats all over the place): > > people are more than happy to spend big money for things like > > routers or bandwidth or any kind of "commercial" stuff, but when > > it comes to open source it must be free or nothing. > > > > I hope it is clear to everyone that an investment in the 50K$ > > range would provide a professional-grade implementation of SACK > > for FreeBSD, and this money is in the noise for any organization > > that uses trans-oceanic gigabit links. > > The fact that nobody seems to care about funding such a work > > either means that whatever is available already fits their >=20 > What Luigi says is absolutely correct. It doesn't take a lot to > get this done. I've talked to a number of companies about implementing > SACK for them and while there was interest, no one wanted to fund > it all themselves, potentially for the benefit of their competitors. > I know of two that went and did it themselves for FreeBSD --- one > of which did it wrong and saw zero benefit from SACK and another > that did it right, but are keeping it proprietary as an edge. Given > that Linux and Windows already have it, these and the multiple past > efforts collectively seem like an unnecessary duplication of work. > Perhaps if we could pool enough interest, we can raise enough to > put this issue to rest once and for all. An angle to try for might be similar to how SoftUpdates was licensed: distribute the code for a period of time under a suitably restrictive license, with a provision that after a certain time (e.g. 12 months) it becomes BSD-licensed. This allowed Kirk to get commercial funding for the SU work while also being able to contribute it to end-users who don't mind the license terms, and eventually for other commercial users. Kris --wRRV7LY7NUeQGEoC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFATRvmWry0BWjoQKURAgtWAKCiXFMYOtsCK5hnGMa7vngVs4ssCACfWewC kPeyqA8jhdLG5u+MHov5p6I= =qH/f -----END PGP SIGNATURE----- --wRRV7LY7NUeQGEoC-- From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 17:55: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 6B42C16A4CE; Mon, 8 Mar 2004 17:55:10 -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 366D943D1D; Mon, 8 Mar 2004 17:55:10 -0800 (PST) (envelope-from mallman@icir.org) Received: from lawyers.icir.org (adsl-68-76-113-50.dsl.bcvloh.ameritech.net [68.76.113.50]) by guns.icir.org (Postfix) with ESMTP id C57FD77A6D4; Mon, 8 Mar 2004 20:55:07 -0500 (EST) Received: from lawyers.icir.org (localhost [127.0.0.1]) by lawyers.icir.org (Postfix) with ESMTP id F38DA10F269; Mon, 8 Mar 2004 20:54:57 -0500 (EST) To: Jeffrey Hsu From: Mark Allman In-Reply-To: <200403082325.i28NPAa3010399@mtaw6.prodigy.net> Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: Moondance MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Date: Mon, 08 Mar 2004 20:54:57 -0500 Sender: mallman@icir.org Message-Id: <20040309015458.F38DA10F269@lawyers.icir.org> cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Who wants SACK? (Re: was 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, 09 Mar 2004 01:55:10 -0000 --=-=-= > > I hope it is clear to everyone that an investment in the 50K$ > > range would provide a professional-grade implementation of SACK > > for FreeBSD, and this money is in the noise for any organization > > that uses trans-oceanic gigabit links. > > What Luigi says is absolutely correct. It doesn't take a lot to get > this done. I've talked to a number of companies about implementing > SACK for them and while there was interest, no one wanted to fund it > all themselves, potentially for the benefit of their competitors. I > know of two that went and did it themselves for FreeBSD --- one of > which did it wrong and saw zero benefit from SACK and another that did > it right, but are keeping it proprietary as an edge. Given that Linux > and Windows already have it, these and the multiple past efforts > collectively seem like an unnecessary duplication of work. Perhaps if > we could pool enough interest, we can raise enough to put this issue > to rest once and for all. On the freebsd web page, there is a note about monetary contributions. I wonder if it would be worth it to make this a bit more verbose and list specific things that are in need of funding. So, companies can tag a small donation for "SACK development" and when there is enough in the pool it can just get done. Would that spurn folks on a bit? Or, would it be useful to setup some sort of committment system whereby a company can say "we'll throw 5K in if you get committments for the 50K you need to make X happen". It might be worth the modest investment to setup something like that and keep it maintained. That way it's a bit more official than some random person running around and trying to put together the required coin. Just a thought .... allman -- Mark Allman -- ICIR -- http://www.icir.org/mallman/ --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (Darwin) iD8DBQFATSPxWyrrWs4yIs4RAjWHAKCO7vREK6gUIsEBzSWcBEC8y+yEtQCcDqza EQ4RabGubBLJE1ruLhr/YPk= =T7/t -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 18:19: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 B155516A4D0 for ; Mon, 8 Mar 2004 18:19:48 -0800 (PST) Received: from smtp.omnis.com (smtp.omnis.com [216.239.128.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id A69C943D53 for ; Mon, 8 Mar 2004 18:19:48 -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 4C8231880401; Mon, 8 Mar 2004 18:19:47 -0800 (PST) From: Wes Peters Organization: Softweyr.com To: "Marc G. Fournier" Date: Mon, 8 Mar 2004 18:19:26 -0800 User-Agent: KMail/1.5.4 References: <20040306150504.Q13247@ganymede.hub.org> <20040307193726.R13247@ganymede.hub.org> In-Reply-To: <20040307193726.R13247@ganymede.hub.org> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200403081109.20032.wes@softweyr.com> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit 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: Tue, 09 Mar 2004 02:19:48 -0000 On Sunday 07 March 2004 15:37, Marc G. Fournier wrote: > > Note that forcing it to 100baseT half-duplex (or 10baseT/UTP half-duplex) > corrects the problem ... turns out it is only in full-duplex mode that > its hosed ... Did you try a cross-over cable? Actually, you shouldn't even need a cross-over cable for gigabit devices, they should auto-select MDI vs. MDIX. Also, I recall reading something about problems with onboard tx cksum errors on em devices recently; you may want to turn off the tx cksum feature in your testing. Or search the archives for txcsum or something like that. -- "Where am I, and what am I doing in this handbasket?" Wes Peters wes@softweyr.com From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 18:23: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 F098416A4CF for ; Mon, 8 Mar 2004 18:23:33 -0800 (PST) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6E3443D45 for ; Mon, 8 Mar 2004 18:23:33 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost.nic.fr [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id i292NTDa093661 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK CN=khavrinen.lcs.mit.edu issuer=SSL+20Client+20CA); Mon, 8 Mar 2004 21:23:30 -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 i292NTJ8093658; Mon, 8 Mar 2004 21:23:29 -0500 (EST) (envelope-from wollman) Date: Mon, 8 Mar 2004 21:23:29 -0500 (EST) From: Garrett Wollman Message-Id: <200403090223.i292NTJ8093658@khavrinen.lcs.mit.edu> To: Julian Elischer In-Reply-To: References: <20040308214020.73C245D07@ptavv.es.net> X-Spam-Score: -19.8 () IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES X-Scanned-By: MIMEDefang 2.37 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, 09 Mar 2004 02:23:34 -0000 < said: > I believe that sme of the patches were considerred "experimental and > just lacked someone to make them production quality. In other cases they > were not against 'current' and porting them to -curren twas left as "an > exercise for the reader". No-one who had that ime had a need for them. Back when I was on core and looked after the network stack, I went around several times with multiple people saying ``please, we would love this code, if only it weren't based on a two-year-old kernel!'' I started my own SACK implementation back in 1996, but it was never finished. (It got caught up in a rewrite of the TCP retransmit queue that proved too difficult to implement.) -GAWollman From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 18:57: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 C604616A4CF for ; Mon, 8 Mar 2004 18:57:20 -0800 (PST) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6018D43D53 for ; Mon, 8 Mar 2004 18:57:20 -0800 (PST) (envelope-from mwade@bluehighway.net) Received: from net-ninja.dyndns.org ([68.59.250.193]) by comcast.net (sccrmhc12) with ESMTP id <2004030902571901200irdhse>; Tue, 9 Mar 2004 02:57:19 +0000 Received: from net-ninja.dyndns.org (net-ninja.dyndns.org [192.168.1.10]) by net-ninja.dyndns.org (Postfix) with ESMTP id 597E71A4; Mon, 8 Mar 2004 21:57:19 -0500 (EST) Date: Mon, 8 Mar 2004 21:57:19 -0500 (EST) From: Mike Wade X-X-Sender: mwade@net-ninja.dyndns.org To: Mark Allman In-Reply-To: <20040309015458.F38DA10F269@lawyers.icir.org> Message-ID: <20040308215444.W53592@net-ninja.dyndns.org> References: <20040309015458.F38DA10F269@lawyers.icir.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: Who wants SACK? (Re: 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: Tue, 09 Mar 2004 02:57:21 -0000 On Mon, 8 Mar 2004, Mark Allman wrote: > > > I hope it is clear to everyone that an investment in the 50K$ > > > range would provide a professional-grade implementation of SACK > > > for FreeBSD, and this money is in the noise for any organization > > > that uses trans-oceanic gigabit links. > > > > What Luigi says is absolutely correct. It doesn't take a lot to get > > this done. I've talked to a number of companies about implementing > > SACK for them and while there was interest, no one wanted to fund it > > all themselves, potentially for the benefit of their competitors. I > > know of two that went and did it themselves for FreeBSD --- one of > > which did it wrong and saw zero benefit from SACK and another that did > > it right, but are keeping it proprietary as an edge. Given that Linux > > and Windows already have it, these and the multiple past efforts > > collectively seem like an unnecessary duplication of work. Perhaps if > > we could pool enough interest, we can raise enough to put this issue > > to rest once and for all. > > On the freebsd web page, there is a note about monetary contributions. > I wonder if it would be worth it to make this a bit more verbose and > list specific things that are in need of funding. So, companies can tag > a small donation for "SACK development" and when there is enough in the > pool it can just get done. Would that spurn folks on a bit? Or, would > it be useful to setup some sort of committment system whereby a company > can say "we'll throw 5K in if you get committments for the 50K you need > to make X happen". It might be worth the modest investment to setup > something like that and keep it maintained. That way it's a bit more > official than some random person running around and trying to put > together the required coin. > > Just a thought .... Personally I think this would be very beneficial. On many occasions I've been willing to donate resources (including cash) for various efforts but I don't have the time or resources to manage such a system... --- Mike Wade (mwade@bluehighway.net) Blue Highway Labs, LLC. From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 20:04: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 AE24C16A4CE for ; Mon, 8 Mar 2004 20:04:59 -0800 (PST) Received: from bes.amduat.net (bes.amduat.net [206.124.149.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A6B743D31 for ; Mon, 8 Mar 2004 20:04:59 -0800 (PST) (envelope-from jbarrett@amduat.net) Received: from osiris.amduat.net (osiris.amduat.net [10.0.0.69]) (AUTH: LOGIN jbarrett, SSL: TLSv1/SSLv3,128bits,RC4-MD5) by bes.amduat.net with esmtp; Mon, 08 Mar 2004 20:04:58 -0800 From: "Jacob S. Barrett" To: "Will Saxon" Date: Mon, 8 Mar 2004 14:16:30 -0800 User-Agent: KMail/1.6 References: <0E972CEE334BFE4291CD07E056C76ED802E867D7@bragi.housing.ufl.edu> In-Reply-To: <0E972CEE334BFE4291CD07E056C76ED802E867D7@bragi.housing.ufl.edu> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200403081416.30233.jbarrett@amduat.net> cc: eberkut@minithins.net cc: freebsd-net@freebsd.org Subject: Re: Solution for Resilient VLAN Trunk Bonding 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, 09 Mar 2004 04:04:59 -0000 On Monday 08 March 2004 01:41 pm, Will Saxon wrote: > Regardless, it doesn't look like ng_fec can work with ng_vlan, since > it doesn't provide any hooks to work with. Couldn't you attach ng_vlan downstream to the ng_ether lower that will created for the ng_fec interface? -- Jacob S. Barrett jbarrett@amduat.net www.amduat.net "I don't suffer from insanity, I enjoy every minute of it." From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 20:05: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 14AFB16A4CE for ; Mon, 8 Mar 2004 20:05:00 -0800 (PST) Received: from bes.amduat.net (bes.amduat.net [206.124.149.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id A647143D39 for ; Mon, 8 Mar 2004 20:04:59 -0800 (PST) (envelope-from jbarrett@amduat.net) Received: from osiris.amduat.net (osiris.amduat.net [10.0.0.69]) (AUTH: LOGIN jbarrett, SSL: TLSv1/SSLv3,128bits,RC4-MD5) by bes.amduat.net with esmtp; Mon, 08 Mar 2004 20:04:58 -0800 From: "Jacob S. Barrett" To: Julian Elischer Date: Mon, 8 Mar 2004 15:53:58 -0800 User-Agent: KMail/1.6 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200403081553.58502.jbarrett@amduat.net> cc: freebsd-net@freebsd.org Subject: Re: Solution for Resilient VLAN Trunk Bonding 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, 09 Mar 2004 04:05:00 -0000 I have some questions about the ng_fec. Would it work if each interface was connected to a different switch? Everything I have read on the list says that they done it only with having "trunking" enabled on the switch as well. I don't see how you could do that across two switches. If no one has an answer I guess I can give it a try at home. I have two really crappy 3Com SuperStack II switches. -- Jacob S. Barrett jbarrett@amduat.net www.amduat.net "I don't suffer from insanity, I enjoy every minute of it." From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 22:04: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 AB72916A4CE for ; Mon, 8 Mar 2004 22:04:58 -0800 (PST) Received: from heisenberg.zen.co.uk (heisenberg.zen.co.uk [212.23.3.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E9E143D2D for ; Mon, 8 Mar 2004 22:04:58 -0800 (PST) (envelope-from zen8061@zen.co.uk) Received: from [217.155.20.225] (helo=auckland) by heisenberg.zen.co.uk with smtp (Exim 4.30) id 1B0aML-0008NQ-Hx for freebsd-net@freebsd.org; Tue, 09 Mar 2004 06:04:57 +0000 From: "Zen" To: Date: Tue, 9 Mar 2004 06:04:05 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-Originating-Heisenberg-IP: [217.155.20.225] Subject: VPN 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, 09 Mar 2004 06:04:58 -0000 Hi, This is this the correct list on how to set up a VPN connection? Thanks Zen From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 22:54: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 DED6116A4CE; Mon, 8 Mar 2004 22:54:05 -0800 (PST) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C904643D1D; Mon, 8 Mar 2004 22:54:04 -0800 (PST) (envelope-from ru@ip.net.ua) Received: from heffalump.office.ipnet (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.10/8.12.9) with ESMTP id i296vR1t042481 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Mar 2004 08:57:29 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.office.ipnet (8.12.11/8.12.11) id i296ruf3055185; Tue, 9 Mar 2004 08:53:56 +0200 (EET) (envelope-from ru) Date: Tue, 9 Mar 2004 08:53:56 +0200 From: Ruslan Ermilov To: Gleb Smirnoff , julian@freebsd.org, archie@freebsd.org, freebsd-net@freebsd.org Message-ID: <20040309065356.GA55139@ip.net.ua> References: <200403072302.i27N2StR008804@freefall.freebsd.org> <20040308102033.GA66247@cell.sick.ru> <20040308212939.GB30394@ip.net.ua> <20040308214820.GA68803@cell.sick.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Dxnq1zWXvFF0Q93v" Content-Disposition: inline In-Reply-To: <20040308214820.GA68803@cell.sick.ru> User-Agent: Mutt/1.5.6i X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: Re: kern/63864: [patch] new control message for ng_iface(4) - getifindex 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, 09 Mar 2004 06:54:06 -0000 --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 09, 2004 at 12:48:20AM +0300, Gleb Smirnoff wrote: > On Mon, Mar 08, 2004 at 11:29:39PM +0200, Ruslan Ermilov wrote: > R> > I have one more idea. Currently we have got 3 interface nodes: ng_= ether, ng_iface, > R> > ng_eiface. 2 of them already support "getifindex" message, imagine I= (or someone else) send > R> > you patch tomorrow, which adds support to ng_eiface. OK, now all thr= ee support. May be > R> > in future some new interface nodes will be developed. > R> >=20 > R> > Imagine the following: you have node, which is connected to some g= eneric > R> > interface (it doesn't know which node type exactly). This node wants= to > R> > determine interface index of attached interfac. It would send 3 "get= ifindex" messages with 3 > R> > different cookies. Two of messages will always fail, and one return.= This is not nice. > R> >=20 > R> > What I suggest: create a new semi-generic cookie NGM_GENERICIFACE_CO= OKIE, which will be > R> > supported by all interface nodes. Put NGM_GENERICIFACE_GETIFINDEX me= ssage under > R> > NGM_GENERICIFACE_COOKIE case brackets. If you like this idea, please= reply me. And I'll send > R> > patches. > R> >=20 > R> How do you think "ngctl msg ng0: getifindex" works? ;) >=20 > So, you suggest to use ASCII message in situation described above? IMHO, = ASCII messages were=20 > invented for human interface purposes, not for node interaction. >=20 OK, how about sending a NGM_NODEINFO message to the node, and picking up XXX for (NGM_XXX_COOKIE, NGM_XXX_GET_IFNAME) based on the returned type? Cheers, --=20 Ruslan Ermilov FreeBSD committer ru@FreeBSD.org --Dxnq1zWXvFF0Q93v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFATWoEUkv4P6juNwoRAhnmAJ9aN+qcR0Ccsk61ldBZrc4RqyUrQgCdGdJQ ojZgAuxOoOGp70cTmR8+zT4= =zrDb -----END PGP SIGNATURE----- --Dxnq1zWXvFF0Q93v-- From owner-freebsd-net@FreeBSD.ORG Mon Mar 8 23:51:47 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0431016A4CE for ; Mon, 8 Mar 2004 23:51:47 -0800 (PST) Received: from mizar.origin-it.net (mizar.origin-it.net [194.8.96.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FC5C43D2F for ; Mon, 8 Mar 2004 23:51:46 -0800 (PST) (envelope-from helge.oldach@atosorigin.com) Received: from matar.hbg.de.int.atosorigin.com (dehsfw3e.origin-it.net [194.8.96.68])i297p35g063427 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Mar 2004 08:51:03 +0100 (CET) (envelope-from helge.oldach@atosorigin.com) Received: from galaxy.hbg.de.ao-srv.com (galaxy.hbg.de.ao-srv.com [161.89.20.4])ESMTP id i297p3bC051369; Tue, 9 Mar 2004 08:51:03 +0100 (CET) (envelope-from helge.oldach@atosorigin.com) Received: (from hmo@localhost) by galaxy.hbg.de.ao-srv.com (8.9.3p2/8.9.3/hmo30mar03) id IAA21292; Tue, 9 Mar 2004 08:50:58 +0100 (MET) Message-Id: <200403090750.IAA21292@galaxy.hbg.de.ao-srv.com> In-Reply-To: <200403081553.58502.jbarrett@amduat.net> from "Jacob S. Barrett" at "Mar 9, 2004 0:53:58 am" To: jbarrett@amduat.net (Jacob S. Barrett) Date: Tue, 9 Mar 2004 08:50:58 +0100 (MET) From: Helge Oldach X-Address: Atos Origin GmbH, Friesenstraße 13, D-20097 Hamburg, Germany X-Phone: +49 40 7886 7464, Fax: +49 40 7886 9464, Mobile: +49 160 4782517 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: julian@elischer.org Subject: Re: Solution for Resilient VLAN Trunk Bonding 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, 09 Mar 2004 07:51:47 -0000 Jacob S. Barrett: >I have some questions about the ng_fec. Would it work if each interface >was connected to a different switch? I'd say this isn't an issue with ng_fec, but rather an architectural point regarding EtherChannel as such. I am not aware of any switch vendor that offers multi-chassis EtherChannel. In fact many even require that the physical links terminate on the same switch blade and don't permit distribution over multiple blades in the same chassis. >Everything I have read on the list says that they done it only with >having "trunking" enabled on the switch as well. That is definitely the case. Both ends must be aware that they belong to a channel, and if you want decent resiliency they should also talk the appropriate channeling protocol. Usually LACP (802.3ad); in the Cisco case PAgP might suit you better. Neither is supported by ng_fec, AFAIK. Be aware that the term "trunking" is commonly used for grouping multiple VLANs onto one link (802.1q) in the switching world. Helge From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 01:19: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 9247916A4CE; Tue, 9 Mar 2004 01:19:09 -0800 (PST) Received: from mailhub.fokus.fraunhofer.de (mailhub.fokus.fraunhofer.de [193.174.154.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1816943D39; Tue, 9 Mar 2004 01:19:08 -0800 (PST) (envelope-from brandt@fokus.fraunhofer.de) Received: from beagle (beagle [193.175.132.100])i299Isd15078; Tue, 9 Mar 2004 10:18:54 +0100 (MET) Date: Tue, 9 Mar 2004 10:18:54 +0100 (CET) From: Harti Brandt To: Gleb Smirnoff In-Reply-To: <20040308102033.GA66247@cell.sick.ru> Message-ID: <20040309101730.O56375@beagle.fokus.fraunhofer.de> References: <200403072302.i27N2StR008804@freefall.freebsd.org> <20040308102033.GA66247@cell.sick.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: kern/63864: [patch] new control message for ng_iface(4) - getifindex X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: harti@freebsd.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Mar 2004 09:19:09 -0000 On Mon, 8 Mar 2004, Gleb Smirnoff wrote: GS>On Sun, Mar 07, 2004 at 03:02:28PM -0800, Ruslan Ermilov wrote: GS>R> Synopsis: [patch] new control message for ng_iface(4) - getifindex GS>R> GS>R> State-Changed-From-To: open->closed GS>R> State-Changed-By: ru GS>R> State-Changed-When: Sun Mar 7 15:01:03 PST 2004 GS>R> State-Changed-Why: GS>R> Committed with tiny modifications, thanks! GS> GS> I have one more idea. Currently we have got 3 interface nodes: ng_ether, ng_iface, GS>ng_eiface. 2 of them already support "getifindex" message, imagine I (or someone else) send GS>you patch tomorrow, which adds support to ng_eiface. OK, now all three support. May be GS>in future some new interface nodes will be developed. Don't forget about ng_atm... harti From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 01:20: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 C78BB16A4D0 for ; Tue, 9 Mar 2004 01:20:01 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 3E3FB43D1F for ; Tue, 9 Mar 2004 01:20:01 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 85349 invoked from network); 9 Mar 2004 09:19:59 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 9 Mar 2004 09:19:59 -0000 X-pair-Authenticated: 209.68.2.70 Date: Tue, 9 Mar 2004 03:19:58 -0600 (CST) From: Mike Silbersack To: Brooks Davis In-Reply-To: <20040308202210.GB485@Odin.AC.HMC.Edu> Message-ID: <20040309031549.L49735@odysseus.silby.com> References: <404BA723.C8141806@freebsd.org> <20040308182431.4FA6D5D08@ptavv.es.net> <20040308202210.GB485@Odin.AC.HMC.Edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: David Malone cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: Andre Oppermann cc: Kevin Oberman 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, 09 Mar 2004 09:20:01 -0000 On Mon, 8 Mar 2004, Brooks Davis wrote: > I've got a co-worker who is part of a research group at ISI that > is doing research on long fat pipes with large streams. They are > intrested in doing a SACK implementation. I hope to have some more > information later this week. > > -- Brooks In order to make SACK easier to digest, perhaps it should be suggested that SACK be implemented in stages: 1. Internal structures are updated to handle SACK, and the stack handles the receive side of SACK properly. (The stack advertises itself as SACK capable, of course.) 2. The transmit side of SACK is implemented. >From what I recall about SACK, the implementation of part 1 would be straightforward to verify and therefore easy to integrate. The send side would, of course, require more attention, and it would be more likely to get it if it could be reviewed seperately. Mike "Silby" Silbersack From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 01:53: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 4715F16A4CE for ; Tue, 9 Mar 2004 01:53:38 -0800 (PST) Received: from fro.boniholding.com (fro.boniholding.com [62.176.87.138]) by mx1.FreeBSD.org (Postfix) with SMTP id 201DB43D49 for ; Tue, 9 Mar 2004 01:53:36 -0800 (PST) (envelope-from fro@fro.boniholding.com) Received: (qmail 23238 invoked by uid 1011); 9 Mar 2004 09:55:19 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 9 Mar 2004 09:55:19 -0000 Date: Tue, 9 Mar 2004 11:55:19 +0200 (EET) From: Frrodo Baggins To: freebsd-net@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: One IP used on more than one interface (gif0 and lo0) 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, 09 Mar 2004 09:53:38 -0000 Hi, What happens if we configure an alias on lo0: ifconfig lo0 alias 192.168.5.1 netmask 255.255.255.0 and then use the same IP on gif0: ifconfig gif0 create ifconfig gif0 tunnel x.x.x.x y.y.y.y ifconfig gif0 192.168.5.1 192.168.5.2 netmask 255.255.255.252 (or netmask 255.255.255.0 - same as that we use in the alias on lo0) In general, what happens if we have the same IP assigned on different interfaces? What this can this be useful for? Best regards, fro@boniholding.com From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 02:53: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 2F6BF16A4CE for ; Tue, 9 Mar 2004 02:53:05 -0800 (PST) Received: from bragi.housing.ufl.edu (bragi.housing.ufl.edu [128.227.47.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7C1A43D3F for ; Tue, 9 Mar 2004 02:53:04 -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: Tue, 9 Mar 2004 05:53:01 -0500 Message-ID: <0E972CEE334BFE4291CD07E056C76ED802E867DD@bragi.housing.ufl.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Solution for Resilient VLAN Trunk Bonding Thread-Index: AcQFi7E+CIr+4DkRRreU5CNPHU1PCwAOMlUQ From: "Will Saxon" To: "Jacob S. Barrett" cc: eberkut@minithins.net cc: freebsd-net@freebsd.org Subject: RE: Solution for Resilient VLAN Trunk Bonding 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, 09 Mar 2004 10:53:05 -0000 > -----Original Message----- > From: Jacob S. Barrett [mailto:jbarrett@amduat.net] > Sent: Monday, March 08, 2004 5:17 PM > To: Will Saxon > Cc: eberkut@minithins.net; freebsd-net@freebsd.org > Subject: Re: Solution for Resilient VLAN Trunk Bonding >=20 >=20 > On Monday 08 March 2004 01:41 pm, Will Saxon wrote: > > Regardless, it doesn't look like ng_fec can work with ng_vlan, since > > it doesn't provide any hooks to work with. >=20 > Couldn't you attach ng_vlan downstream to the ng_ether lower=20 > that will created=20 > for the ng_fec interface? Maybe, but when you load ng_ether it tries to name the node fec0 then = fails since there is already a node named fec0. I don't know how to name = or reference a node that is unnamed and not hooked to anything, so I was = not able to make this work. -Will From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 04:40: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 2972E16A4CE for ; Tue, 9 Mar 2004 04:40:38 -0800 (PST) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80F6043D5F for ; Tue, 9 Mar 2004 04:40:37 -0800 (PST) (envelope-from freebsd-net@m.gmane.org) Received: from root by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1B0gXE-0005DH-00 for ; Tue, 09 Mar 2004 13:40:36 +0100 Received: from seclab01.ces.bth.se ([194.47.141.68]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 09 Mar 2004 13:40:36 +0100 Received: from mda00hpe by seclab01.ces.bth.se with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 09 Mar 2004 13:40:36 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-net@freebsd.org From: Hannes Persson Date: Tue, 09 Mar 2004 13:35:11 +0100 Organization: BTH Lines: 35 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: seclab01.ces.bth.se Mail-Copies-To: mda00cto@student.bth.se User-Agent: KNode/0.7.2 Sender: news Subject: sendto() problem using T/TCP over IPv6 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: mda00hpe@student.bth.se List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Mar 2004 12:40:38 -0000 Hi I have a problem bothering me for days now. Hope some of you have an proposal for a solution... I have some code working over IP4 sending T/TCP transactions. But when switching to IP6 the sendto() complains over "Socket is not connected". As i said it currently working witch the usual sin but when switching to sin6 the error occurs. The OS i am using is FreeBSD4.8. I paste a snippet from the code: struct sockaddr_in6 serv; if ( (sockfd = socket(AF_INET6, SOCK_STREAM, 0)) < 0) printf("socket error"); memset(&serv, sizeof(serv), 0); serv.sin6_family = AF_INET6; serv.sin6_port = htons(80); inet_pton(AF_INET6, argv[1], &serv.sin6_addr); if (sendto(sockfd, request,strlen(request), MSG_EOF, (struct sockaddr*) &serv, sizeof(serv)) != strlen(request)) perror("SENDTO ERROR: "); Thanks in advance -Hannes ----------------- Hannes Persson Master student CS Blekinge Institute of Technology mda00hpe@student.bth.se From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 07:15:52 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5961B16A515; Tue, 9 Mar 2004 07:15:52 -0800 (PST) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4233C43D46; Tue, 9 Mar 2004 07:15:52 -0800 (PST) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: from dibbler.crodrigues.org (h00609772adf0.ne.client2.attbi.com[66.31.45.197]) by comcast.net (rwcrmhc13) with ESMTP id <200403091515510150073q8se>; Tue, 9 Mar 2004 15:15:51 +0000 Received: from dibbler.crodrigues.org (localhost.crodrigues.org [127.0.0.1]) i29FFsiI096279; Tue, 9 Mar 2004 10:15:59 -0500 (EST) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: (from rodrigc@localhost) by dibbler.crodrigues.org (8.12.11/8.12.10/Submit) id i29FFsYt096242; Tue, 9 Mar 2004 10:15:54 -0500 (EST) (envelope-from rodrigc) Date: Tue, 9 Mar 2004 10:15:53 -0500 From: Craig Rodrigues To: Mark Allman Message-ID: <20040309151553.GA82012@crodrigues.org> References: <200403082325.i28NPAa3010399@mtaw6.prodigy.net> <20040309015458.F38DA10F269@lawyers.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040309015458.F38DA10F269@lawyers.icir.org> User-Agent: Mutt/1.4.1i cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Who wants SACK? (Re: 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: Tue, 09 Mar 2004 15:15:52 -0000 On Mon, Mar 08, 2004 at 08:54:57PM -0500, Mark Allman wrote: > On the freebsd web page, there is a note about monetary contributions. > I wonder if it would be worth it to make this a bit more verbose and > list specific things that are in need of funding. So, companies can tag > a small donation for "SACK development" and when there is enough in the > pool it can just get done. Would that spurn folks on a bit? The FreeBSD Foundation is probably the organization which is best equipped to do this: http://www.freebsdfoundation.org/ The FreeBSD Foundation is registered as a 501(c) non-profit organization (for non-U.S. people, 501(c) is a section of the U.S. tax code which designates an organization as non-profit, which gives some tax benefits). They seem to be best equipped to receive donations, and fund specific FreeBSD work. These contributions would be tax-deductible, which is one incentive to donate. -- Craig Rodrigues http://crodrigues.org rodrigc@crodrigues.org From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 07:48: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 3D76B16A4CF for ; Tue, 9 Mar 2004 07:48:24 -0800 (PST) Received: from smtpout.mac.com (A17-250-248-87.apple.com [17.250.248.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04D7743D45 for ; Tue, 9 Mar 2004 07:48:24 -0800 (PST) (envelope-from justin@mac.com) Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id i29FmNgi011576 for ; Tue, 9 Mar 2004 07:48:23 -0800 (PST) Received: from mac.com (c-24-6-87-110.client.comcast.net [24.6.87.110]) (authenticated bits=0) by mac.com (Xserve/smtpin07/MantshX 3.0) with ESMTP id i29FmMBj022250 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 9 Mar 2004 07:48:23 -0800 (PST) Date: Tue, 9 Mar 2004 07:48:20 -0800 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v553) From: Justin Walker To: freebsd-net@freebsd.org Content-Transfer-Encoding: 7bit In-Reply-To: Message-Id: <30D08A02-71E1-11D8-A9B6-00306544D642@mac.com> X-Mailer: Apple Mail (2.553) Subject: Re: One IP used on more than one interface (gif0 and lo0) 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, 09 Mar 2004 15:48:24 -0000 On Tuesday, March 9, 2004, at 01:55 AM, Frrodo Baggins wrote: > Hi, > > What happens if we configure an alias on lo0: > > ifconfig lo0 alias 192.168.5.1 netmask 255.255.255.0 > > and then use the same IP on gif0: What happens if you have the same address on two different houses on the same street? Regards, Justin -- /~\ The ASCII Justin C. Walker, Curmudgeon-at-Large \ / Ribbon Campaign X Help cure HTML Email / \ From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 07:49: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 4736016A4CE; Tue, 9 Mar 2004 07:49:18 -0800 (PST) Received: from smtp.des.no (flood.des.no [217.116.83.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1CA343D2F; Tue, 9 Mar 2004 07:49:15 -0800 (PST) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 666) id D736A530E; Tue, 9 Mar 2004 16:49:14 +0100 (CET) Received: from dwp.des.no (des.no [80.203.228.37]) by smtp.des.no (Pony Express) with ESMTP id 751A0530A; Tue, 9 Mar 2004 16:49:08 +0100 (CET) Received: by dwp.des.no (Postfix, from userid 2602) id 564CB33CA4; Tue, 9 Mar 2004 16:49:08 +0100 (CET) To: Jeffrey Hsu References: <200403082325.i28NPAa3010399@mtaw6.prodigy.net> From: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) Date: Tue, 09 Mar 2004 16:49:08 +0100 In-Reply-To: <200403082325.i28NPAa3010399@mtaw6.prodigy.net> (Jeffrey Hsu's message of "Mon, 08 Mar 2004 15:32:37 -0800") Message-ID: User-Agent: Gnus/5.090024 (Oort Gnus v0.24) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on flood.des.no X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.63 cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Who wants SACK? (Re: 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: Tue, 09 Mar 2004 15:49:18 -0000 Jeffrey Hsu writes: > What Luigi says is absolutely correct. It doesn't take a lot to > get this done. I've talked to a number of companies about implementing > SACK for them and while there was interest, no one wanted to fund > it all themselves, potentially for the benefit of their competitors. Just for giggles, what kind of money are we talking here? I might be able to liberate funds for work that improves network performance in the high end. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 09:26: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 28FDB16A4CE; Tue, 9 Mar 2004 09:26:59 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DC8943D2D; Tue, 9 Mar 2004 09:26:59 -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 i29HQsRH005490; Tue, 9 Mar 2004 09:26:54 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i29HQr8S005489; Tue, 9 Mar 2004 09:26:53 -0800 Date: Tue, 9 Mar 2004 09:26:53 -0800 From: Brooks Davis To: Mike Silbersack Message-ID: <20040309172653.GC19707@Odin.AC.HMC.Edu> References: <404BA723.C8141806@freebsd.org> <20040308182431.4FA6D5D08@ptavv.es.net> <20040308202210.GB485@Odin.AC.HMC.Edu> <20040309031549.L49735@odysseus.silby.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="H8ygTp4AXg6deix2" Content-Disposition: inline In-Reply-To: <20040309031549.L49735@odysseus.silby.com> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: Andre Oppermann cc: Kevin Oberman cc: freebsd-net@freebsd.org cc: David Malone 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, 09 Mar 2004 17:26:59 -0000 --H8ygTp4AXg6deix2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 09, 2004 at 03:19:58AM -0600, Mike Silbersack wrote: >=20 > On Mon, 8 Mar 2004, Brooks Davis wrote: >=20 > > I've got a co-worker who is part of a research group at ISI that > > is doing research on long fat pipes with large streams. They are > > intrested in doing a SACK implementation. I hope to have some more > > information later this week. > > > > -- Brooks >=20 > In order to make SACK easier to digest, perhaps it should be suggested > that SACK be implemented in stages: >=20 > 1. Internal structures are updated to handle SACK, and the stack handles > the receive side of SACK properly. (The stack advertises itself as SACK > capable, of course.) >=20 > 2. The transmit side of SACK is implemented. >=20 > >From what I recall about SACK, the implementation of part 1 would be > straightforward to verify and therefore easy to integrate. The send side > would, of course, require more attention, and it would be more likely to > get it if it could be reviewed seperately. We'll definatly keep this in mind. Thanks. -- 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 --H8ygTp4AXg6deix2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFATf5bXY6L6fI4GtQRAnTvAJ9/7q/2Arn9VZheQLJZ90nTY+a+qgCgs2AH IlpKONSo7H5ejqM6n0d+8ro= =75Ly -----END PGP SIGNATURE----- --H8ygTp4AXg6deix2-- From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 10:10: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 4AD5F16A4CE for ; Tue, 9 Mar 2004 10:10:58 -0800 (PST) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id F38E743D77 for ; Tue, 9 Mar 2004 10:10:55 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (sccrmhc11) with ESMTP id <2004030918104901100fdp7ke>; Tue, 9 Mar 2004 18:10:54 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA64348; Tue, 9 Mar 2004 10:10:47 -0800 (PST) Date: Tue, 9 Mar 2004 10:10:46 -0800 (PST) From: Julian Elischer To: Justin Walker In-Reply-To: <30D08A02-71E1-11D8-A9B6-00306544D642@mac.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: One IP used on more than one interface (gif0 and lo0) 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, 09 Mar 2004 18:10:58 -0000 On Tue, 9 Mar 2004, Justin Walker wrote: > > On Tuesday, March 9, 2004, at 01:55 AM, Frrodo Baggins wrote: > > > Hi, > > > > What happens if we configure an alias on lo0: > > > > ifconfig lo0 alias 192.168.5.1 netmask 255.255.255.0 > > > > and then use the same IP on gif0: > > What happens if you have the same address on two different houses on > the same street? that isn't the question.. it's "why have different numbers on houses on differnt streets?" It is in fact common practice to number all your P2P links using teh address of one of your broadcast interfaces.. this works well, saves you an address and you have a simpler routing table. Point to point links route using the REMOTE address and don't care about teh local address so this always works. julian (lo0 is a P2P link) > > Regards, > > Justin > > -- > /~\ The ASCII Justin C. Walker, Curmudgeon-at-Large > \ / Ribbon Campaign > X Help cure HTML Email > / \ > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 10:14: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 10F2D16A4CE; Tue, 9 Mar 2004 10:14:22 -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 CC2F643D48; Tue, 9 Mar 2004 10:14:21 -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 C7E4377A6D5; Tue, 9 Mar 2004 13:14:19 -0500 (EST) To: Mike Silbersack From: Mark Allman In-Reply-To: <20040309031549.L49735@odysseus.silby.com> Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: Wild Horses MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Date: Tue, 09 Mar 2004 13:14:19 -0500 Sender: mallman@guns.icir.org Message-Id: <20040309181419.C7E4377A6D5@guns.icir.org> cc: Andre Oppermann cc: Kevin Oberman cc: freebsd-net@freebsd.org cc: David Malone 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 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, 09 Mar 2004 18:14:22 -0000 --=-=-= > 1. Internal structures are updated to handle SACK, and the stack handles > the receive side of SACK properly. (The stack advertises itself as SACK > capable, of course.) > > 2. The transmit side of SACK is implemented. > > >From what I recall about SACK, the implementation of part 1 would be > straightforward to verify and therefore easy to integrate. The send > side would, of course, require more attention, and it would be more > likely to get it if it could be reviewed seperately. I think this is a nicely methodical approach. Just being able to generate SACK blocks to the sender provides a good win for receivers. I am no kernel guru, but I don't actually imagine that it is all that tough because all the information you'd need has to be tracked now to make sure you deliver data to the application correctly. The way tougher part is that you need a new data structure (a scoreboard) to track the peer's status if you're going to do something intelligent (e.g., rfc3517) with the information you're being sent. And, you have to add hooks to update the scoreboard, consult it when sending, consult it when making congestion control decisions, etc. allman -- Mark Allman -- ICIR -- http://www.icir.org/mallman/ --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFATgl7WyrrWs4yIs4RAmLLAJ4qYwF3XxdRjflDLcNtPYn8u5CD8gCeIp/+ tuT6TV4Jab2kL4qXVPIWp3U= =X6Bo -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 11:00: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 F3BD916A4CE; Tue, 9 Mar 2004 11:00:03 -0800 (PST) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21A4943D1F; Tue, 9 Mar 2004 11:00:03 -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 i29IxwQE074634 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Mar 2004 21:59:58 +0300 (MSK) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.9/8.12.6/Submit) id i29Ixvnl074633; Tue, 9 Mar 2004 21:59:57 +0300 (MSK) Date: Tue, 9 Mar 2004 21:59:57 +0300 From: Gleb Smirnoff To: Ruslan Ermilov Message-ID: <20040309185957.GB74537@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Ruslan Ermilov , julian@freebsd.org, archie@freebsd.org, freebsd-net@freebsd.org References: <200403072302.i27N2StR008804@freefall.freebsd.org> <20040308102033.GA66247@cell.sick.ru> <20040308212939.GB30394@ip.net.ua> <20040308214820.GA68803@cell.sick.ru> <20040309065356.GA55139@ip.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20040309065356.GA55139@ip.net.ua> User-Agent: Mutt/1.5.6i cc: freebsd-net@freebsd.org Subject: Re: kern/63864: [patch] new control message for ng_iface(4) - getifindex 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, 09 Mar 2004 19:00:04 -0000 On Tue, Mar 09, 2004 at 08:53:56AM +0200, Ruslan Ermilov wrote: R> On Tue, Mar 09, 2004 at 12:48:20AM +0300, Gleb Smirnoff wrote: R> > On Mon, Mar 08, 2004 at 11:29:39PM +0200, Ruslan Ermilov wrote: R> > R> > I have one more idea. Currently we have got 3 interface nodes: ng_ether, ng_iface, R> > R> > ng_eiface. 2 of them already support "getifindex" message, imagine I (or someone else) send R> > R> > you patch tomorrow, which adds support to ng_eiface. OK, now all three support. May be R> > R> > in future some new interface nodes will be developed. R> > R> > R> > R> > Imagine the following: you have node, which is connected to some generic R> > R> > interface (it doesn't know which node type exactly). This node wants to R> > R> > determine interface index of attached interfac. It would send 3 "getifindex" messages with 3 R> > R> > different cookies. Two of messages will always fail, and one return. This is not nice. R> > R> > R> > R> > What I suggest: create a new semi-generic cookie NGM_GENERICIFACE_COOKIE, which will be R> > R> > supported by all interface nodes. Put NGM_GENERICIFACE_GETIFINDEX message under R> > R> > NGM_GENERICIFACE_COOKIE case brackets. If you like this idea, please reply me. And I'll send R> > R> > patches. R> > R> > R> > R> How do you think "ngctl msg ng0: getifindex" works? ;) R> > R> > So, you suggest to use ASCII message in situation described above? IMHO, ASCII messages were R> > invented for human interface purposes, not for node interaction. R> > R> OK, how about sending a NGM_NODEINFO message to the node, and R> picking up XXX for (NGM_XXX_COOKIE, NGM_XXX_GET_IFNAME) based R> on the returned type? First, this requires some dialog-like message interchange (as well as ASCII message). Netgraph does not provide nice API for this. I see the only way to implement: 1) send out NGM_NODEINFO message from some node method 2) catch reply in xxx_rcvmsg(), construct new message and send it 3) catch second reply in xxx_rcvmsg() Second, this will work only with a certain number of nodes. The code of xxx_rcvmsg() will look like: if (msg->header.flags & NGF_RESP) { switch (msg->header.typecookie) { case NGM_GENERIC_COOKIE: switch (msg->header.cmd) { case NGM_NODEINFO: { struct nodeinfo *info = (struct nodeinfo *)msg->data; if (strcmp(info->type, NG_IFACE_NODE_TYPE, strlen(NG_IFACE_NODE_TYPE)) { xxxxx } else if (strcmp(info->type, NG_ETHER_NODE_TYPE ..... { yyyyyy This won't be generic solution. Whenever, a new interface node is implemented (e.g. ng_atm), our imaginary node needs a patch and ng_atm.h to be included. My proposal brings a generic solution for any new interface node type. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 11:25: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 3F26316A4CE; Tue, 9 Mar 2004 11:25:31 -0800 (PST) Received: from vhost109.his.com (vhost109.his.com [216.194.225.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1851143D46; Tue, 9 Mar 2004 11:25:30 -0800 (PST) (envelope-from brad.knowles@skynet.be) Received: from [10.0.1.4] (localhost.his.com [127.0.0.1]) by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id i29JPFxg084340; Tue, 9 Mar 2004 14:25:25 -0500 (EST) (envelope-from brad.knowles@skynet.be) Mime-Version: 1.0 X-Sender: bs663385@127.0.0.1 Message-Id: In-Reply-To: <200403082325.i28NPAa3010399@mtaw6.prodigy.net> References: <200403082325.i28NPAa3010399@mtaw6.prodigy.net> Date: Tue, 9 Mar 2004 20:13:11 +0100 To: Jeffrey Hsu From: Brad Knowles Content-Type: text/plain; charset="us-ascii" ; format="flowed" cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Who wants SACK? (Re: 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: Tue, 09 Mar 2004 19:25:31 -0000 At 3:32 PM -0800 2004/03/08, Jeffrey Hsu wrote: > What Luigi says is absolutely correct. It doesn't take a lot to > get this done. I've talked to a number of companies about implementing > SACK for them and while there was interest, no one wanted to fund > it all themselves, potentially for the benefit of their competitors. Out of curiosity, can someone provide some pointers as to where SACK really helps? Is this just for high-speed WANs and doesn't help on LANs, or is it useful in both contexts? Also, at what speeds/packet sizes does SACK start to become really useful? I'm just wondering if there aren't a lot of people who could benefit from something like this, only they don't know it. If they were to find out, it might help provide funding and other resources to spur development. -- 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 9 13:42: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 195AA16A4CE; Tue, 9 Mar 2004 13:42:06 -0800 (PST) Received: from postal2.es.net (proxy.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07B5243D1D; Tue, 9 Mar 2004 13:42:06 -0800 (PST) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465; Tue, 09 Mar 2004 13:42:05 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 3EE2D5D07; Tue, 9 Mar 2004 13:42:05 -0800 (PST) To: Brad Knowles In-reply-to: Your message of "Tue, 09 Mar 2004 20:13:11 +0100." Date: Tue, 09 Mar 2004 13:42:05 -0800 From: "Kevin Oberman" Message-Id: <20040309214205.3EE2D5D07@ptavv.es.net> cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Who wants SACK? (Re: 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: Tue, 09 Mar 2004 21:42:06 -0000 > Date: Tue, 9 Mar 2004 20:13:11 +0100 > From: Brad Knowles > Sender: owner-freebsd-current@freebsd.org > > At 3:32 PM -0800 2004/03/08, Jeffrey Hsu wrote: > > > What Luigi says is absolutely correct. It doesn't take a lot to > > get this done. I've talked to a number of companies about implementing > > SACK for them and while there was interest, no one wanted to fund > > it all themselves, potentially for the benefit of their competitors. > > Out of curiosity, can someone provide some pointers as to where > SACK really helps? Is this just for high-speed WANs and doesn't help > on LANs, or is it useful in both contexts? Also, at what > speeds/packet sizes does SACK start to become really useful? > > I'm just wondering if there aren't a lot of people who could > benefit from something like this, only they don't know it. If they > were to find out, it might help provide funding and other resources > to spur development. Selective ACKnowledgment (SACK) allows acknowledgment of received packets in a TCP window so that only the missing/damaged packet needs to be re-transmitted. This is normally of little value on a LAN where ACKs arrive quickly and windows are smaller and no use on slow circuits. On fat pipes with latency and big windows it is a huge win as it allows you to recover much faster from a packet drop. If you don't have SACK, you need to re-transmit all of the packets in flight within the window while with SACK, you need only retransmit the dropped packet(s). If you have a 10 or 20 MB window, this is a big deal. Dynamic window sizing will make it of less significance in LANs as the windows will not be very large. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 14:12: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 E67E116A4E1 for ; Tue, 9 Mar 2004 14:12:09 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 683DB43D1D for ; Tue, 9 Mar 2004 14:12:09 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 96889 invoked from network); 9 Mar 2004 22:12:08 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 9 Mar 2004 22:12:08 -0000 X-pair-Authenticated: 209.68.2.70 Date: Tue, 9 Mar 2004 16:12:07 -0600 (CST) From: Mike Silbersack To: Kevin Oberman In-Reply-To: <20040309214205.3EE2D5D07@ptavv.es.net> Message-ID: <20040309160821.P705@odysseus.silby.com> References: <20040309214205.3EE2D5D07@ptavv.es.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Brad Knowles cc: freebsd-current@freebsd.org cc: freebsd-net@freebsd.org Subject: Re: Who wants SACK? (Re: 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: Tue, 09 Mar 2004 22:12:10 -0000 On Tue, 9 Mar 2004, Kevin Oberman wrote: > Selective ACKnowledgment (SACK) allows acknowledgment of received > packets in a TCP window so that only the missing/damaged packet needs to > be re-transmitted. This is normally of little value on a LAN where ACKs > arrive quickly and windows are smaller and no use on slow circuits. On > fat pipes with latency and big windows it is a huge win as it allows you to > recover much faster from a packet drop. If you don't have SACK, you need > to re-transmit all of the packets in flight within the window while > with SACK, you need only retransmit the dropped packet(s). If you have a > 10 or 20 MB window, this is a big deal. That's not correct. Non-SACK TCP doesn't drop any additional packets vs SACK. The difference is that SACK allows the transmitter to transmit the packet which fills the "hole" and then immediately start transmitting new data (or fill other holes.) Non-SACK senders have to wait to receive an ACK after retransmitting the hole in order to find out if there are other holes which must be filled or if new data can be transmitted. SACK itself really doesn't do much, it's all the new congestion control schemes (FACK, Rate Halving, etc) that come shipped with most SACK implementations that do the work and contain most of the complexity. Mike "Silby" Silbersack From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 14:16: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 1B1D016A4CE; Tue, 9 Mar 2004 14:16:15 -0800 (PST) Received: from rms04.rommon.net (rms04.rommon.net [212.54.2.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id E74F743D2F; Tue, 9 Mar 2004 14:16:13 -0800 (PST) (envelope-from pete@he.iki.fi) Received: from he.iki.fi (h81.vuokselantie10.fi [193.64.42.129]) by rms04.rommon.net (8.12.9p1/8.12.9) with ESMTP id i29MG7cM077517; Wed, 10 Mar 2004 00:16:07 +0200 (EET) (envelope-from pete@he.iki.fi) Message-ID: <404E4225.5040700@he.iki.fi> Date: Wed, 10 Mar 2004 00:16:05 +0200 From: Petri Helenius User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Silbersack References: <20040309214205.3EE2D5D07@ptavv.es.net> <20040309160821.P705@odysseus.silby.com> In-Reply-To: <20040309160821.P705@odysseus.silby.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Brad Knowles cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: Kevin Oberman Subject: Re: Who wants SACK? (Re: 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: Tue, 09 Mar 2004 22:16:15 -0000 Mike Silbersack wrote: >SACK itself really doesn't do much, it's all the new congestion control >schemes (FACK, Rate Halving, etc) that come shipped with most SACK >implementations that do the work and contain most of the complexity. > > And all this would be non-issue within normal operational context if routers would contain adequate buffering and not run crappy software which drops packets by default even without congestion. Pete From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 14:35: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 9AF8716A4CE; Tue, 9 Mar 2004 14:35:23 -0800 (PST) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3DB043D2F; Tue, 9 Mar 2004 14:35:22 -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 i29MZJQE075916 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Mar 2004 01:35:20 +0300 (MSK) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.9/8.12.6/Submit) id i29MZJF9075915; Wed, 10 Mar 2004 01:35:19 +0300 (MSK) Date: Wed, 10 Mar 2004 01:35:19 +0300 From: Gleb Smirnoff To: Ruslan Ermilov , julian@FreeBSD.org, archie@FreeBSD.org, freebsd-net@FreeBSD.org Message-ID: <20040309223519.GA75896@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Ruslan Ermilov , julian@freebsd.org, archie@freebsd.org, freebsd-net@freebsd.org References: <200403072302.i27N2StR008804@freefall.freebsd.org> <20040308102033.GA66247@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20040308102033.GA66247@cell.sick.ru> User-Agent: Mutt/1.5.6i Subject: Re: kern/63864: [patch] new control message for ng_iface(4) - getifindex 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, 09 Mar 2004 22:35:23 -0000 On Mon, Mar 08, 2004 at 01:20:33PM +0300, Gleb Smirnoff wrote: T> Imagine the following: you have node, which is connected to some generic T> interface (it doesn't know which node type exactly). This node wants to T> determine interface index of attached interfac. It would send 3 "getifindex" messages with 3 T> different cookies. Two of messages will always fail, and one return. This is not nice. T> T> What I suggest: create a new semi-generic cookie NGM_GENERICIFACE_COOKIE, which will be T> supported by all interface nodes. Put NGM_GENERICIFACE_GETIFINDEX message under T> NGM_GENERICIFACE_COOKIE case brackets. If you like this idea, please reply me. And I'll send T> patches. I've forgot to mention, that NGM_XXX_GET_IFNAME messages can be treated the same way. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 15:17: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 5DB6D16A4CE; Tue, 9 Mar 2004 15:17:34 -0800 (PST) Received: from pd4mo3so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A14B43D1F; Tue, 9 Mar 2004 15:17:34 -0800 (PST) (envelope-from jhanna@shaw.ca) Received: from pd2mr1so.prod.shaw.ca (pd2mr1so-ser.prod.shaw.ca [10.0.141.110])2003)) with ESMTP id <0HUC006AF0CI26@l-daemon>; Tue, 09 Mar 2004 16:09:54 -0700 (MST) Received: from pn2ml8so.prod.shaw.ca (pn2ml8so-qfe0.prod.shaw.ca [10.0.121.152]) by l-daemon (iPlanet Messaging Server 5.2 HotFix 1.18 (built Jul 28 2003)) with ESMTP id <0HUC0006T0CI81@l-daemon>; Tue, 09 Mar 2004 16:09:54 -0700 (MST) Received: from cub.pangolin-systems.com (h24-81-10-24.vc.shawcable.net [24.81.10.24])2003)) with ESMTP id <0HUC00E020CHOI@l-daemon>; Tue, 09 Mar 2004 16:09:54 -0700 (MST) Date: Tue, 09 Mar 2004 15:09:53 -0800 (PST) From: jhanna@shaw.ca In-reply-to: <20040309214205.3EE2D5D07@ptavv.es.net> Sender: jhanna@cub.pangolin-systems.com To: Brad Knowles Message-id: MIME-version: 1.0 X-Mailer: XFMail 1.5.4 on FreeBSD Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Priority: 3 (Normal) cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: Kevin Oberman Subject: Re: Who wants SACK? (Re: was My planned work on networking stack) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jhanna@shaw.ca List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Mar 2004 23:17:34 -0000 On 09-Mar-2004 Kevin Oberman wrote: >> Date: Tue, 9 Mar 2004 20:13:11 +0100 >> From: Brad Knowles >> Sender: owner-freebsd-current@freebsd.org >> >> At 3:32 PM -0800 2004/03/08, Jeffrey Hsu wrote: >> >> > What Luigi says is absolutely correct. It doesn't take a lot to >> > get this done. I've talked to a number of companies about implementing >> > SACK for them and while there was interest, no one wanted to fund >> > it all themselves, potentially for the benefit of their competitors. >> >> Out of curiosity, can someone provide some pointers as to where >> SACK really helps? Is this just for high-speed WANs and doesn't help >> on LANs, or is it useful in both contexts? Also, at what >> speeds/packet sizes does SACK start to become really useful? >> >> I'm just wondering if there aren't a lot of people who could >> benefit from something like this, only they don't know it. If they >> were to find out, it might help provide funding and other resources >> to spur development. > > Selective ACKnowledgment (SACK) allows acknowledgment of received > packets in a TCP window so that only the missing/damaged packet needs to > be re-transmitted. This is normally of little value on a LAN where ACKs > arrive quickly and windows are smaller and no use on slow circuits. On > fat pipes with latency and big windows it is a huge win as it allows you to > recover much faster from a packet drop. If you don't have SACK, you need > to re-transmit all of the packets in flight within the window while > with SACK, you need only retransmit the dropped packet(s). If you have a > 10 or 20 MB window, this is a big deal. > > Dynamic window sizing will make it of less significance in LANs as the > windows will not be very large. Radio links as well, with their latency and higher frame drop rates, can benefit considerably. Cell phones and such may account for a large amount of garden variety traffic as time goes on. jhanna@shaw.ca From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 16:47: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 028F116A4CE for ; Tue, 9 Mar 2004 16:47:01 -0800 (PST) Received: from secure.net2000.com.au (secure.net2000.com.au [203.26.98.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE52A43D39 for ; Tue, 9 Mar 2004 16:46:59 -0800 (PST) (envelope-from ktulu@net2000.com.au) Received: (from apache@localhost) by secure.net2000.com.au (8.11.6/8.11.6) id i2A0reF18330 for freebsd-net@freebsd.org; Wed, 10 Mar 2004 11:53:40 +1100 X-Authentication-Warning: secure.net2000.com.au: apache set sender to ktulu@net2000.com.au using -f Received: from 202.14.179.253 ([202.14.179.253]) by secure.net2000.com.au (IMP) with HTTP for ; Wed, 10 Mar 2004 11:53:40 +1100 Message-ID: <1078880020.404e6714a1235@secure.net2000.com.au> Date: Wed, 10 Mar 2004 11:53:40 +1100 From: ktulu@net2000.com.au To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.1 X-Originating-IP: 202.14.179.253 Subject: natd interface alias 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: Wed, 10 Mar 2004 00:47:01 -0000 Hi All, I've been playing around with this for a few weeks now and searched Google endlessly, but still can't find a solution... I apologise in advance for the length of this post. Basically, I have a freebsd machine that acts as a proxy and web server to a web application we are currently developing. The machine is configured to serve up web pages via Apache on port 80, but forward any traffic requested on port 443 to another machine behind the firewall. Below are the relevant parts of the rc.conf file: network interfaces="fxp1 lo0" ifconfig_lo0="inet 127.0.0.1" ifconfig_fxp1="inet 192.168.1.10 netmask 255.255.0.0" gateway_enable="YES" natd_enable="YES" natd_interface="fxp1" natd_flags="-l -m -redirect_port tcp 192.168.1.20:443 443" I have set the firewall to "allow ip any to any" for the sake of simplifying the problem. The configuration above works fine for one IP - when I request https://192.168.1.10/ it serves the page from 192.168.1.20. I have written a script to add another IP to the machine to perform the same task, which is where the problems begin. Basically the script issues the following commands: # Add the alias to fxp1 ifconfig fxp1 inet 192.168.1.11 netmask 255.255.255.255 alias (still not sure why the subnet mask here has to be 0xffffffff, even if I specify fxp0, which is a physically different port, but anyway it works) # Create a natd instance for the newly configured IP: /sbin/natd -n fxp1 -port 8669 -m -redirect_port tcp 192.168.1.21:443 192.168.1.11 443 # Restart the networking /etc/netstart As far as Apache is concerned this configuration is fine and it serves the correct page as configured in the VirtualHosts (on port 80). The problem is, is that if I request https://192.168.1.11/, the browser times out and does not serve the page from 192.168.1.21. Why is it that it works for one and not the aliased IP? natd does not bind to port 443 (at least nmap doesn't report it), so it's not that port 443 is already bound. If natd/FreeBSD actually capable of such a configuration or am I just overlooking something fundamental?!? Any help would be much appreciated! Thanks, Leigh P.S - I'm running FreeBSD 4.8-RELEASE From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 20:27: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 55A1916A4CE for ; Tue, 9 Mar 2004 20:27:37 -0800 (PST) Received: from secure.net2000.com.au (secure.net2000.com.au [203.26.98.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8573943D41 for ; Tue, 9 Mar 2004 20:27:36 -0800 (PST) (envelope-from ktulu@net2000.com.au) Received: (from apache@localhost) by secure.net2000.com.au (8.11.6/8.11.6) id i2A4YIN18620 for freebsd-net@freebsd.org; Wed, 10 Mar 2004 15:34:18 +1100 X-Authentication-Warning: secure.net2000.com.au: apache set sender to ktulu@net2000.com.au using -f Received: from 202.14.179.253 ([202.14.179.253]) by secure.net2000.com.au (IMP) with HTTP for ; Wed, 10 Mar 2004 15:34:18 +1100 Message-ID: <1078893258.404e9aca7c840@secure.net2000.com.au> Date: Wed, 10 Mar 2004 15:34:18 +1100 From: ktulu@net2000.com.au To: freebsd-net@freebsd.org References: <1078880020.404e6714a1235@secure.net2000.com.au> In-Reply-To: <1078880020.404e6714a1235@secure.net2000.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.1 X-Originating-IP: 202.14.179.253 Subject: Re: natd interface alias 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: Wed, 10 Mar 2004 04:27:37 -0000 > Hi All, > > I've been playing around with this for a few weeks now and searched Google > endlessly, but still can't find a solution... I apologise in advance for > the > length of this post. > > Basically, I have a freebsd machine that acts as a proxy and web server to a > web > application we are currently developing. The machine is configured to serve > up > web pages via Apache on port 80, but forward any traffic requested on port > 443 > to another machine behind the firewall. Below are the relevant parts of the > rc.conf file: > > network interfaces="fxp1 lo0" > ifconfig_lo0="inet 127.0.0.1" > ifconfig_fxp1="inet 192.168.1.10 netmask 255.255.0.0" > gateway_enable="YES" > natd_enable="YES" > natd_interface="fxp1" > natd_flags="-l -m -redirect_port tcp 192.168.1.20:443 443" > > I have set the firewall to "allow ip any to any" for the sake of simplifying > the > problem. The configuration above works fine for one IP - when I request > https://192.168.1.10/ it serves the page from 192.168.1.20. I have written > a > script to add another IP to the machine to perform the same task, which is > where > the problems begin. Basically the script issues the following commands: > > # Add the alias to fxp1 > ifconfig fxp1 inet 192.168.1.11 netmask 255.255.255.255 alias > > (still not sure why the subnet mask here has to be 0xffffffff, even if I > specify > fxp0, which is a physically different port, but anyway it works) > > # Create a natd instance for the newly configured IP: > /sbin/natd -n fxp1 -port 8669 -m -redirect_port tcp 192.168.1.21:443 > 192.168.1.11 443 > > # Restart the networking > /etc/netstart > > As far as Apache is concerned this configuration is fine and it serves the > correct page as configured in the VirtualHosts (on port 80). The problem is, > is > that if I request https://192.168.1.11/, the browser times out and does not > serve the page from 192.168.1.21. > > Why is it that it works for one and not the aliased IP? natd does not bind > to > port 443 (at least nmap doesn't report it), so it's not that port 443 is > already > bound. If natd/FreeBSD actually capable of such a configuration or am I > just > overlooking something fundamental?!? Any help would be much appreciated! > > Thanks, > Leigh > > P.S - I'm running FreeBSD 4.8-RELEASE > One thing I forgot to add were the relevant ipfw rules that I have for the nat daemons: 00050 151 17284 divert 8668 ip from any to any via fxp1 00051 151 17284 divert 8669 ip from any to any via fxp1 Regards, Leigh From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 20:28: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 737E516A4CE; Tue, 9 Mar 2004 20:28:07 -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 376FE43D45; Tue, 9 Mar 2004 20:28:07 -0800 (PST) (envelope-from mallman@icir.org) Received: from lawyers.icir.org (adsl-68-76-113-50.dsl.bcvloh.ameritech.net [68.76.113.50]) by guns.icir.org (Postfix) with ESMTP id 415E077A6D5; Tue, 9 Mar 2004 23:28:04 -0500 (EST) Received: from lawyers.icir.org (localhost [127.0.0.1]) by lawyers.icir.org (Postfix) with ESMTP id E136C10F8AF; Tue, 9 Mar 2004 23:28:04 -0500 (EST) To: Mike Silbersack To: Kevin Oberman To: Brad Knowles From: Mark Allman In-Reply-To: Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: Wild Horses MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Date: Tue, 09 Mar 2004 23:28:04 -0500 Sender: mallman@icir.org Message-Id: <20040310042804.E136C10F8AF@lawyers.icir.org> cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Who wants SACK? (Re: was 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: Wed, 10 Mar 2004 04:28:07 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable Brad Knowles: > Out of curiosity, can someone provide some pointers as to where SACK > really helps? Is this just for high-speed WANs and doesn't help on > LANs, or is it useful in both contexts? Also, at what speeds/packet > sizes does SACK start to become really useful? >=20 > I'm just wondering if there aren't a lot of people who could benefit > from something like this, only they don't know it.=20=20 I think that it is generally a nice addition to TCP. The space where SACK helps quite a lot is when a connection loses more than one packet From=20a window of data (i.e., more than one loss per RTT). Since losses tend to be bursty this happens more often than one might think by just looking at the loss rate. Without SACK, TCP can usually handle one loss per RTT with no problem (using fast retransmit). More losses, however, will cause retransmission via the RTO timer -- which is slow. Kevin Oberman: > If you don't have SACK, you need to re-transmit all of the packets in > flight within the window while with SACK, you need only retransmit the > dropped packet(s).=20 This is not actually quite right on a couple of fronts. First, as mentioned above if you have only a single loss from a window of data then fast retransmit will take care of it without any problem. Second, TCP is not quite a go-back-n protocol even after the RTO. TCP definately resends a lot more data than it has to without SACK. But, it doesn't retransmit the entire window either. Mike Silbersack: > SACK itself really doesn't do much, it's all the new congestion > control schemes (FACK, Rate Halving, etc) that come shipped with most > SACK implementations that do the work and contain most of the > complexity. Right. (And, I'll plug RFC3517 as a very heavily vetted method for using SACK information. I am probably biased. But, I think it is very nice. I have grown to like it more and more since it was published. Its robustness keep surprising me!) allman =2D- Mark Allman -- ICIR -- http://www.icir.org/mallman/ --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (Darwin) iD8DBQFATplUWyrrWs4yIs4RAux+AJ9hkhtz9pbfK7OHw/j8eq9LQInubQCeIJ4d XTnTNOmmZqGgKOPefI6y5cw= =exgs -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 21:22: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 D689016A4CE for ; Tue, 9 Mar 2004 21:22:54 -0800 (PST) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E0DD43D1D for ; Tue, 9 Mar 2004 21:22:54 -0800 (PST) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.11/8.12.11) with ESMTP id i2A5MrSt077442; Wed, 10 Mar 2004 00:22:53 -0500 (EST) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.11/8.12.11/Submit) id i2A5MrQV077441; Wed, 10 Mar 2004 00:22:53 -0500 (EST) (envelope-from barney) Date: Wed, 10 Mar 2004 00:22:53 -0500 From: Barney Wolff To: ktulu@net2000.com.au Message-ID: <20040310052253.GA76705@pit.databus.com> References: <1078880020.404e6714a1235@secure.net2000.com.au> <1078893258.404e9aca7c840@secure.net2000.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1078893258.404e9aca7c840@secure.net2000.com.au> User-Agent: Mutt/1.5.6i X-Scanned-By: MIMEDefang 2.39 cc: freebsd-net@freebsd.org Subject: Re: natd interface alias 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: Wed, 10 Mar 2004 05:22:54 -0000 On Wed, Mar 10, 2004 at 03:34:18PM +1100, ktulu@net2000.com.au wrote: > > 00050 151 17284 divert 8668 ip from any to any via fxp1 > 00051 151 17284 divert 8669 ip from any to any via fxp1 Did you actually want to send every packet through both nat daemons? You might want to use 4 rules to specify separately which packets get diverted, in and out. I suspect the double nat has something to do with your problem. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 21:26: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 3757716A4CE for ; Tue, 9 Mar 2004 21:26:14 -0800 (PST) Received: from diablo.OntheNet.com.au (diablo.OntheNet.com.au [203.10.89.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A9BB43D2D for ; Tue, 9 Mar 2004 21:26:13 -0800 (PST) (envelope-from nicks@diablo.onthenet.com.au) Received: from mail.onthenet.com.au (vdub.OntheNet.net [203.10.89.16]) i2A5QBXd078438 for ; Wed, 10 Mar 2004 15:26:12 +1000 (EST) Received: by mail.onthenet.com.au (Postfix, from userid 1001) id 4FE6F177BF; Wed, 10 Mar 2004 15:25:56 +1000 (EST) Date: Wed, 10 Mar 2004 15:25:56 +1000 From: Nick Slager To: net@freebsd.org Message-ID: <20040310052556.GA33553@OntheNet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2i X-Homer: Whoohooooooo! Subject: IPsec: odd behaviour with policies 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, 10 Mar 2004 05:26:14 -0000 This is perhaps the wrong forum for this question, however, posting on -questions has drawn a blank. I have a newly created VPN between a 4.8 box and a Cisco VPN 3000 Concentrator. The concentrator is not under my control, being owned by an associated company. The policies are extremely restrictive, and permit a single host in our network (behind the FreeBSD end) to communicate with 2 hosts at the other end (behind the concentrator). I am able to establish the VPN from our internal host by pinging one of the hosts in the remote network. The VPN is established and all works fine, but I can only communicate with the one remote host I pinged to establish the VPN link. I am unable to communicate with the other host. If I tear down the IPsec tunnel, and re-establish the VPN by pinging the other remote IP address, communication is fine also, but only for the one single remote host I pinged. Is anyone able to shed light on why this might be the case? Anonymised config files below. Nick 192.168.1.1 Our internal host 203.1.1.1 Our IPsec endpoint (FreeBSD 4.8) 1.2.3.4 Remote internal host #1 1.2.3.5 Remote internal host #2 203.2.2.2 Remote IPsec endpoint (concentrator) /etc/ipsec.conf: flush; spdflush; spdadd 192.168.1.1/32 1.2.3.4/32 any -P out ipsec esp/tunnel/203.1.1.1-203.2.2.2/require; spdadd 1.2.3.4/32 192.168.1.1/32 any -P in ipsec esp/tunnel/203.2.2.2-203.1.1.1/require; spdadd 192.168.1.1/32 1.2.3.5/32 any -P out ipsec esp/tunnel/203.1.1.1-203.2.2.2/require; spdadd 1.2.3.5/32 192.168.1.1/32 any -P in ipsec esp/tunnel/203.2.2.2-203.1.1.1/require; Relevant portions of racoon.conf: remote 203.2.2.2 { exchange_mode main,aggressive; doi ipsec_doi; situation identity_only; my_identifier address "203.1.1.1"; nonce_size 16; lifetime time 86400 sec; initial_contact on; support_proxy on; proposal_check obey; proposal { encryption_algorithm 3des; hash_algorithm sha1; authentication_method pre_shared_key ; dh_group 2 ; } } sainfo address 192.168.1.1/32 any address 1.2.3.4/32 any { pfs_group 2; lifetime time 86400 sec; encryption_algorithm 3des ; authentication_algorithm hmac_sha1; compression_algorithm deflate ; } sainfo address 192.168.1.1/32 any address 1.2.3.5/32 any { pfs_group 2; lifetime time 86400 sec; encryption_algorithm 3des ; authentication_algorithm hmac_sha1; compression_algorithm deflate ; } From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 22:42: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 4497616A4CE; Tue, 9 Mar 2004 22:42:38 -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 10AE143D46; Tue, 9 Mar 2004 22:42:38 -0800 (PST) (envelope-from mike@adept.org) Received: by snafu.adept.org (Postfix, from userid 1000) id D3A7A9EEE8; Tue, 9 Mar 2004 22:42:31 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by snafu.adept.org (Postfix) with ESMTP id CC52E9B148; Tue, 9 Mar 2004 22:42:31 -0800 (PST) Date: Tue, 9 Mar 2004 22:42:31 -0800 (PST) From: Mike Hoskins To: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= In-Reply-To: Message-ID: <20040309223939.O87362@snafu.adept.org> References: <200403082325.i28NPAa3010399@mtaw6.prodigy.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Who wants SACK? (Re: 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, 10 Mar 2004 06:42:38 -0000 On Tue, 9 Mar 2004, Dag-Erling [iso-8859-1] Sm=F8rgrav wrote: > Just for giggles, what kind of money are we talking here? I might be > able to liberate funds for work that improves network performance in > the high end. that'd be cool, and i wish i could as well. with the non-profit status of the foundation though, i can at least make personal donations. all this talk about network features/tuning has me grinning ear to ear. thanks to everyone putting in the time/effort. the thing is... it's kind of sad more of the companies that have built their products on *BSD don't donate regularly. i know plenty of companies with appliances, products, etc. built on FreeBSD... is there any sort of "PR" person for the project that could make a semi-regular habit of soliciting these orgs? i know it'd be hard to do correctly, but it just seems like the "right" thing to do and could get a lot of corporate funding... which seems like what would help the most. -m -- "Information Warfare? Given the state of the industry, what we need is Information Welfare." --Richard A Steenbergen From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 23:16: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 47DF416A4D0 for ; Tue, 9 Mar 2004 23:16:59 -0800 (PST) Received: from mail5.hitachi.co.jp (mail5.hitachi.co.jp [133.145.228.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CDB643D53 for ; Tue, 9 Mar 2004 23:16:56 -0800 (PST) (envelope-from ume@freebsd.org) Received: from mc1.mcg.hitachi.co.jp by mail5.hitachi.co.jp (8.9.3p3/3.7W-ns3) id QAA20241; Wed, 10 Mar 2004 16:16:54 +0900 (JST) Received: (from root@localhost) by mc1.mcg.hitachi.co.jp (8.11.6+Sun/8.11.6) id i2A7GrT10896 for ; Wed, 10 Mar 2004 16:16:53 +0900 (JST) Received: from unknown [192.168.2.1] by mc1.mcg.hitachi.co.jp with SMTP id SAA10894 ; Wed, 10 Mar 2004 16:16:53 +0900 Received: from navsg4.hitachi.co.jp by navsg4.hitachi.co.jp (8.9.3/3.7W-navsg4) id QAA23860; Wed, 10 Mar 2004 16:16:52 +0900 (JST) Received: from mlsv5.itg.hitachi.co.jp ([158.213.165.104]) by navsg4.hitachi.co.jp (NAVGW 2.5.2.17) with SMTP id M2004031016165228324 for ; Wed, 10 Mar 2004 16:16:52 +0900 Received: from mfilter-r2.itg.hitachi.co.jp by mlsv5.itg.hitachi.co.jp (8.12.10/8.12.10) id i2A7GqdL020738; Wed, 10 Mar 2004 16:16:52 +0900 Received: from navgw5.itg.hitachi.co.jp (unverified) by mfilter-r2.itg.hitachi.co.jp (Content Technologies SMTPRS 4.3.10) with SMTP id ; Wed, 10 Mar 2004 16:16:52 +0900 Received: from gmml13.itg.hitachi.co.jp ([158.213.165.43]) by navgw5.itg.hitachi.co.jp (SAVSMTP 3.1.3.37) with SMTP id M2004031016162207834; Wed, 10 Mar 2004 16:16:22 +0900 Received: from plum.ssr.bisd.hitachi.co.jp by gmml13.itg.hitachi.co.jp (AIX5.1/8.11.6p2/8.11.0) id i2A7GqA471394; Wed, 10 Mar 2004 16:16:52 +0900 Date: Wed, 10 Mar 2004 16:16:54 +0900 Message-ID: From: Hajimu UMEMOTO To: mda00hpe@student.bth.se In-Reply-To: References: User-Agent: xcite1.38 > Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=) X-Operating-System: FreeBSD 4.8-RELEASE-p13 MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset="us-ascii" cc: freebsd-net@freebsd.org Subject: Re: sendto() problem using T/TCP over 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, 10 Mar 2004 07:16:59 -0000 Hi, >>>>> On Tue, 09 Mar 2004 13:35:11 +0100 >>>>> mda00hpe@student.bth.se (Hannes Persson) said: mda00hpe> I have some code working over IP4 sending T/TCP transactions. But when mda00hpe> switching to IP6 the sendto() complains over "Socket is not connected". mda00hpe> As i said it currently working witch the usual sin but when switching to mda00hpe> sin6 the error occurs. The OS i am using is FreeBSD4.8. Our IPv6 implementation doesn't support T/TCP. Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org h-umemoto@hitachi-system.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ From owner-freebsd-net@FreeBSD.ORG Tue Mar 9 23:50: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 A1DFC16A4D1 for ; Tue, 9 Mar 2004 23:50:51 -0800 (PST) Received: from hermes.xtec.es (hermes.xtec.es [193.145.88.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE7A543D2D for ; Tue, 9 Mar 2004 23:50:50 -0800 (PST) (envelope-from tonign@pie.xtec.es) Received: from gregal.xtec.es (gregal.xtec.es [193.145.88.16]) by hermes.xtec.es (8.12.10/8.12.10) with ESMTP id i2A7njUs008199 for ; Wed, 10 Mar 2004 08:49:45 +0100 (CET) Received: from [213.176.162.47] (sis47.xtec.es [213.176.162.47]) (authenticated bits=0) by gregal.xtec.es (8.12.9/8.12.8) with ESMTP id i2A7oM40010227 for ; Wed, 10 Mar 2004 08:50:23 +0100 (MET) From: toni To: freebsd-net@FreeBSD.org Content-Type: text/plain Message-Id: <1078905022.5474.18.camel@sis47.xtec.es> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Wed, 10 Mar 2004 08:50:22 +0100 Content-Transfer-Encoding: 7bit X-XTECg-MailScanner-Information: X-XTECg-MailScanner: Found to be clean X-XTECg-MailScanner-SpamCheck: no es spam, SpamAssassin (puntuació=-5, requerit 5, ORIGEN__XTEC -5.00) X-XTECh-MailScanner-Information: X-XTECh-MailScanner: Found to be clean X-XTECh-MailScanner-SpamCheck: no és spam, SpamAssassin (puntuació=-4.9, requerit 5, autolearn=not spam, BAYES_00 -4.90) Subject: ipv6 autoconf on vlan 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: Wed, 10 Mar 2004 07:50:51 -0000 hi all, i'm trying to set up a FreeBSD 5.2 with trunking with 11 vlan interfaces to advertise ipv6 prefixes in an ipv6 native network my purpose is that vlan interfaces will configure their address from the prefix advertised on the same machine i've been following this page to use vlan devices: http://people.freebsd.org/~arved/vlan/vlan_en.html and, if i use: ifconfig_vlan4="vlan 4 vlandev fxp0" in /etc/rc.conf vlan starts but it doesn't listen any prefix and vlan interfaces remain without a global-scope ipv6 address for now, i must to force the addresses (in this way everything works fine) in /etc/rc.conf: ifconfig_vlan4="inet6 2001:x:x:x:x:x:x:x prefixlen 64 vlan 4 vlandev fxp0" but this is not my purpose! do you know if it can be done or i'm missing? in fact, i think network initialisation must be completed before zebra (radvd daemon) could be started, then vlan interfaces cannot listen the prefix at boot time... is this correct? thanks in advance, topi From owner-freebsd-net@FreeBSD.ORG Wed Mar 10 01: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 4B55A16A4CE; Wed, 10 Mar 2004 01:22:23 -0800 (PST) Received: from smtp.des.no (flood.des.no [217.116.83.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id D309343D2D; Wed, 10 Mar 2004 01:22:22 -0800 (PST) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 666) id 7BCFB530E; Wed, 10 Mar 2004 10:22:21 +0100 (CET) Received: from dwp.des.no (des.no [80.203.228.37]) by smtp.des.no (Pony Express) with ESMTP id 2F2F1530A; Wed, 10 Mar 2004 10:22:07 +0100 (CET) Received: by dwp.des.no (Postfix, from userid 2602) id BC92933CA4; Wed, 10 Mar 2004 10:22:06 +0100 (CET) To: Mike Hoskins References: <200403082325.i28NPAa3010399@mtaw6.prodigy.net> <20040309223939.O87362@snafu.adept.org> From: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) Date: Wed, 10 Mar 2004 10:22:06 +0100 In-Reply-To: <20040309223939.O87362@snafu.adept.org> (Mike Hoskins's message of "Tue, 9 Mar 2004 22:42:31 -0800 (PST)") Message-ID: User-Agent: Gnus/5.090024 (Oort Gnus v0.24) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on flood.des.no X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.63 cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Who wants SACK? (Re: 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, 10 Mar 2004 09:22:23 -0000 Mike Hoskins writes: > the thing is... it's kind of sad more of the companies that have built > their products on *BSD don't donate regularly. How do you know they don't? DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-net@FreeBSD.ORG Wed Mar 10 02:19: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 6011816A4CE for ; Wed, 10 Mar 2004 02:19:23 -0800 (PST) Received: from azalorea.propagation.net (156-19-97-216-rev.propagation.net [216.97.19.156]) by mx1.FreeBSD.org (Postfix) with SMTP id E767C43D4C for ; Wed, 10 Mar 2004 02:19:22 -0800 (PST) (envelope-from mpetraschek@adsatcom.es) Received: (qmail 22773 invoked from network); 10 Mar 2004 10:19:06 -0000 Received: from docsis227-24.menta.net (HELO martin) (mpetraschek@adsatcom.es@62.57.227.24) by azalorea.propagation.net with SMTP; 10 Mar 2004 10:19:06 -0000 From: "Martin Petraschek" To: "freebsd-net@freebsd.org" Date: Wed, 10 Mar 2004 11:19:24 +0100 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2380) For Windows 2000 (5.0.2195;4) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <20040310101922.E767C43D4C@mx1.FreeBSD.org> Subject: Dummynet queue reconfiguration X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Martin Petraschek List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Mar 2004 10:19:23 -0000 Hi! We are planning to use dummynet for bandwidth control and are very happy with the abilities of dummynet so far, but recently we ran into a problem we cannot solve: The man page of ipfw says, that the "ipfw queue" command can be used to create OR MODIFY an existing queue. But when I issue a command like ipfw queue 6 config weight 50 pipe 5 the weight of the queue is not changed. Only if I first delete the queue with "ipfw queue delete" and then recreate it with the above command, the weight is changed as expected. Is it not possibly to reconfigure the queue dynamically or am I missing something? Thank you very much, Martin From owner-freebsd-net@FreeBSD.ORG Wed Mar 10 03:37: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 0C44F16A539; Wed, 10 Mar 2004 03:37:21 -0800 (PST) Received: from mailhub.fokus.fraunhofer.de (mailhub.fokus.fraunhofer.de [193.174.154.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCC7943D46; Wed, 10 Mar 2004 03:37:19 -0800 (PST) (envelope-from brandt@fokus.fraunhofer.de) Received: from beagle (beagle [193.175.132.100])i2ABbBd13557; Wed, 10 Mar 2004 12:37:12 +0100 (MET) Date: Wed, 10 Mar 2004 12:37:11 +0100 (CET) From: Harti Brandt To: Mike Silbersack In-Reply-To: <20040309160821.P705@odysseus.silby.com> Message-ID: <20040310123237.V61186@beagle.fokus.fraunhofer.de> References: <20040309214205.3EE2D5D07@ptavv.es.net> <20040309160821.P705@odysseus.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Brad Knowles cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: Kevin Oberman Subject: Re: Who wants SACK? (Re: 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, 10 Mar 2004 11:37:21 -0000 On Tue, 9 Mar 2004, Mike Silbersack wrote: MS> MS>On Tue, 9 Mar 2004, Kevin Oberman wrote: MS> MS>> Selective ACKnowledgment (SACK) allows acknowledgment of received MS>> packets in a TCP window so that only the missing/damaged packet needs to MS>> be re-transmitted. This is normally of little value on a LAN where ACKs MS>> arrive quickly and windows are smaller and no use on slow circuits. On MS>> fat pipes with latency and big windows it is a huge win as it allows you to MS>> recover much faster from a packet drop. If you don't have SACK, you need MS>> to re-transmit all of the packets in flight within the window while MS>> with SACK, you need only retransmit the dropped packet(s). If you have a MS>> 10 or 20 MB window, this is a big deal. MS> MS>That's not correct. Non-SACK TCP doesn't drop any additional packets vs MS>SACK. The difference is that SACK allows the transmitter to transmit the MS>packet which fills the "hole" and then immediately start transmitting new MS>data (or fill other holes.) Non-SACK senders have to wait to receive an MS>ACK after retransmitting the hole in order to find out if there are other MS>holes which must be filled or if new data can be transmitted. MS> MS>SACK itself really doesn't do much, it's all the new congestion control MS>schemes (FACK, Rate Halving, etc) that come shipped with most SACK MS>implementations that do the work and contain most of the complexity. For satellite pipes with drops that are not the result of congestion, but of transmission errors SACK helps. With congestion control only you get no throughput no matter what you do (I did some tests with a simulated 50MBit/sec GEO link with errors). But this is a rather limited application. harti From owner-freebsd-net@FreeBSD.ORG Wed Mar 10 03:45:27 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9205516A4CE for ; Wed, 10 Mar 2004 03:45:27 -0800 (PST) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7D2243D55 for ; Wed, 10 Mar 2004 03:45:26 -0800 (PST) (envelope-from freebsd-net@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1B129O-0002HZ-00 for ; Wed, 10 Mar 2004 12:45:26 +0100 Received: from seclab01.ces.bth.se ([194.47.141.68]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 10 Mar 2004 12:45:26 +0100 Received: from mda00hpe by seclab01.ces.bth.se with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 10 Mar 2004 12:45:26 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-net@freebsd.org From: Hannes Persson Date: Wed, 10 Mar 2004 12:49:47 +0100 Organization: BTH Lines: 33 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: seclab01.ces.bth.se Mail-Copies-To: mda00cto@student.bth.se User-Agent: KNode/0.7.2 Sender: news Subject: Re: sendto() problem using T/TCP over IPv6 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: mda00hpe@student.bth.se List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Mar 2004 11:45:27 -0000 Hi OK, thanks. Then i have to reconsider, you have saved me a lot of time :-) /hannes Hajimu UMEMOTO wrote: > Hi, > >>>>>> On Tue, 09 Mar 2004 13:35:11 +0100 >>>>>> mda00hpe@student.bth.se (Hannes Persson) said: > > mda00hpe> I have some code working over IP4 sending T/TCP transactions. > But when mda00hpe> switching to IP6 the sendto() complains over "Socket is > not connected". mda00hpe> As i said it currently working witch the usual > sin but when switching to mda00hpe> sin6 the error occurs. The OS i am > using is FreeBSD4.8. > > Our IPv6 implementation doesn't support T/TCP. > > Sincerely, > > -- > Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan > ume@mahoroba.org h-umemoto@hitachi-system.co.jp ume@{,jp.}FreeBSD.org > http://www.imasy.org/~ume/ > _______________________________________________ > 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 10 05:50:59 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD84216A4CE for ; Wed, 10 Mar 2004 05:50:59 -0800 (PST) Received: from fro.boniholding.com (fro.boniholding.com [62.176.87.138]) by mx1.FreeBSD.org (Postfix) with SMTP id B671543D41 for ; Wed, 10 Mar 2004 05:50:56 -0800 (PST) (envelope-from root@fro.boniholding.com) Received: (qmail 16487 invoked by uid 0); 10 Mar 2004 13:52:45 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 10 Mar 2004 13:52:45 -0000 Date: Wed, 10 Mar 2004 15:52:45 +0200 (EET) From: Charlie ROOT To: freebsd-net@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: One IP used on more than one interface (gif0 and lo0) 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, 10 Mar 2004 13:50:59 -0000 I was asking because of this: "To make firewalling and managing traffic f lowing thru the ip tunnel a little easier I used virtual interfaces; I added aliases to the loopback interface(lo0) on both gateways to use as inside endpoints for the tunnel. That way I have a chance to control the traffic at the gateway before passing it on out the internal interface to it's local network. Useful for NAT situations, trouble-shooting and easier to setup firewall rules because it is easier to picture/diagram the network flow." "IPsec VPN using FreeBSD" Greg Panula, 2001 GSEC Practical version 1.2e / www.sans.org/rr/papers/21/795.pdf / " ... First setup the aliases On bert I added 5.5.5.1 as the alias ifconfig lo0 alias 5.5.5.1 netmask 255.255.255.252 ... Next actually setup the tunnel On bert I did this: gifconfig gif0 2.2.2.2 3.3.3.3 ifconfig gif0 inet 5.5.5.1 5.5.5.2 netmask 255.255.255.252 " Can somebody picture/diagram me the network flow.. The incoming packets - what exactly happens with them? From which interface they came from - gif0? And if they did - what is the alias on lo0 for? Best regards, Fro From owner-freebsd-net@FreeBSD.ORG Wed Mar 10 07:37: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 8DE8516A4CE for ; Wed, 10 Mar 2004 07:37:00 -0800 (PST) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id D62D343D69 for ; Wed, 10 Mar 2004 07:36:58 -0800 (PST) (envelope-from ru@ip.net.ua) Received: from heffalump.office.ipnet (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.10/8.12.9) with ESMTP id i2AFeVu0090943 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Mar 2004 17:40:32 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.office.ipnet (8.12.11/8.12.11) id i2AFaqhi090779; Wed, 10 Mar 2004 17:36:52 +0200 (EET) (envelope-from ru) Date: Wed, 10 Mar 2004 17:36:52 +0200 From: Ruslan Ermilov To: "Jacob S. Barrett" Message-ID: <20040310153652.GD90219@ip.net.ua> References: <200403072050.38190.jbarrett@amduat.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pZs/OQEoSSbxGlYw" Content-Disposition: inline In-Reply-To: <200403072050.38190.jbarrett@amduat.net> User-Agent: Mutt/1.5.6i X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: freebsd-net@freebsd.org Subject: Re: ng_vlan in FreeBSD-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, 10 Mar 2004 15:37:00 -0000 --pZs/OQEoSSbxGlYw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Mar 07, 2004 at 08:50:38PM -0800, Jacob S. Barrett wrote: > When might we see ng_vlan ported to FreeBSD-4? >=20 Go for it! Cheers, --=20 Ruslan Ermilov FreeBSD committer ru@FreeBSD.org --pZs/OQEoSSbxGlYw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFATzYUUkv4P6juNwoRAohdAJ9xgvLxSCS9npZIzwNkYAsFT2nGXgCeIaIB YchRiEl/fn0Wbak9KCn7AGU= =z5DC -----END PGP SIGNATURE----- --pZs/OQEoSSbxGlYw-- From owner-freebsd-net@FreeBSD.ORG Wed Mar 10 07:41: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 2B4D716A4CE; Wed, 10 Mar 2004 07:41:55 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0647843D46; Wed, 10 Mar 2004 07:41:55 -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 i2AFffRH019119; Wed, 10 Mar 2004 07:41:41 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i2AFffVq019114; Wed, 10 Mar 2004 07:41:41 -0800 Date: Wed, 10 Mar 2004 07:41:41 -0800 From: Brooks Davis To: Harti Brandt Message-ID: <20040310154139.GA14892@Odin.AC.HMC.Edu> References: <20040309214205.3EE2D5D07@ptavv.es.net> <20040309160821.P705@odysseus.silby.com> <20040310123237.V61186@beagle.fokus.fraunhofer.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WIyZ46R2i8wDzkSu" Content-Disposition: inline In-Reply-To: <20040310123237.V61186@beagle.fokus.fraunhofer.de> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: Brad Knowles cc: freebsd-current@freebsd.org cc: Kevin Oberman cc: freebsd-net@freebsd.org Subject: Re: Who wants SACK? (Re: 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, 10 Mar 2004 15:41:55 -0000 --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 10, 2004 at 12:37:11PM +0100, Harti Brandt wrote: > On Tue, 9 Mar 2004, Mike Silbersack wrote: >=20 > MS> > MS>On Tue, 9 Mar 2004, Kevin Oberman wrote: > MS> > MS>> Selective ACKnowledgment (SACK) allows acknowledgment of received > MS>> packets in a TCP window so that only the missing/damaged packet need= s to > MS>> be re-transmitted. This is normally of little value on a LAN where A= CKs > MS>> arrive quickly and windows are smaller and no use on slow circuits. = On > MS>> fat pipes with latency and big windows it is a huge win as it allows= you to > MS>> recover much faster from a packet drop. If you don't have SACK, you = need > MS>> to re-transmit all of the packets in flight within the window while > MS>> with SACK, you need only retransmit the dropped packet(s). If you ha= ve a > MS>> 10 or 20 MB window, this is a big deal. > MS> > MS>That's not correct. Non-SACK TCP doesn't drop any additional packets = vs > MS>SACK. The difference is that SACK allows the transmitter to transmit = the > MS>packet which fills the "hole" and then immediately start transmitting = new > MS>data (or fill other holes.) Non-SACK senders have to wait to receive = an > MS>ACK after retransmitting the hole in order to find out if there are ot= her > MS>holes which must be filled or if new data can be transmitted. > MS> > MS>SACK itself really doesn't do much, it's all the new congestion control > MS>schemes (FACK, Rate Halving, etc) that come shipped with most SACK > MS>implementations that do the work and contain most of the complexity. >=20 > For satellite pipes with drops that are not the result of congestion, but > of transmission errors SACK helps. With congestion control only you get no > throughput no matter what you do (I did some tests with a simulated > 50MBit/sec GEO link with errors). But this is a rather limited > application. For that matter, there are sufficent drops on 10GbE from data errors to insure that two boxes connected back to back won't achieve line speed on a single TCP session. -- 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 --WIyZ46R2i8wDzkSu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFATzcxXY6L6fI4GtQRAqTDAKDlCGkr03SBdrHmE6clLj4KjiLuIQCdFTg7 hsqoox+1LkIhef/yYr4dFvc= =t/mZ -----END PGP SIGNATURE----- --WIyZ46R2i8wDzkSu-- From owner-freebsd-net@FreeBSD.ORG Wed Mar 10 07:48:47 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 942F916A4CE for ; Wed, 10 Mar 2004 07:48:47 -0800 (PST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 421BE43D2F for ; Wed, 10 Mar 2004 07:48:47 -0800 (PST) (envelope-from mlaier@vampire.homelinux.org) Received: from [212.227.126.206] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1B15ws-0008Ps-00 for net@freebsd.org; Wed, 10 Mar 2004 16:48:46 +0100 Received: from [217.83.6.158] (helo=vampire.homelinux.org) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1B15we-0007SH-00 for net@freebsd.org; Wed, 10 Mar 2004 16:48:32 +0100 Received: (qmail 8086 invoked by uid 1001); 10 Mar 2004 15:55:09 -0000 Date: Wed, 10 Mar 2004 16:55:09 +0100 From: Max Laier To: current@freebsd.org Message-ID: <20040310155509.GA7972@router.laiers.local> References: <20040309011908.GA87400@router.laiers.local> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline In-Reply-To: <20040309011908.GA87400@router.laiers.local> User-Agent: Mutt/1.4.1i X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:e28873fbe4dbe612ce62ab869898ff08 cc: net@freebsd.org Subject: Re: HEADS UP: pf linked to the build/install now 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, 10 Mar 2004 15:48:47 -0000 --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Following up to myself to answer one veryFAQ: Q: How about ALTQ? A: It is on my list. The work maintained at rofug.ro (http://www.rofug.ro/projects/freebsd-altq/) is a very good starting point and I am in contact with them. Nonetheless, I like to take one step at a time and the current step is to finish the import! Once that is done (as well as some other more pushing work in the netstack) I will help to update the patchset and work towards an import. On a sidenote to this: Darren Reed told me (on request) that ipfilter 4 will also have the ability to classify for altq, which will make the nasty altqd approach and syntax superfluous. --=20 Best regards, | mlaier@freebsd.org Max Laier | ICQ #67774661 http://pf4freebsd.love2party.net/ | mlaier@EFnet --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFATzpcXyyEoT62BG0RAqtzAJ92xA9jCopBUDCJMi9ttiG7DXNwngCfe4jj uRYQNdPhwBH6zHL/DvHjmMg= =Ioje -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm-- From owner-freebsd-net@FreeBSD.ORG Wed Mar 10 08:03: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 828DF16A4CE; Wed, 10 Mar 2004 08:03:19 -0800 (PST) Received: from bes.amduat.net (bes.amduat.net [206.124.149.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1DDB43D31; Wed, 10 Mar 2004 08:03:18 -0800 (PST) (envelope-from jbarrett@amduat.net) Received: from 149.82.116.80 ([63.115.16.66]) (AUTH: LOGIN jbarrett, SSL: TLSv1/SSLv3,128bits,RC4-MD5) by bes.amduat.net with esmtp; Wed, 10 Mar 2004 08:03:17 -0800 From: "Jacob S. Barrett" To: Ruslan Ermilov Date: Wed, 10 Mar 2004 08:03:15 -0800 User-Agent: KMail/1.6 References: <200403072050.38190.jbarrett@amduat.net> <20040310153652.GD90219@ip.net.ua> In-Reply-To: <20040310153652.GD90219@ip.net.ua> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200403100803.16097.jbarrett@amduat.net> cc: freebsd-net@freebsd.org Subject: Re: ng_vlan in FreeBSD-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, 10 Mar 2004 16:03:19 -0000 On Wednesday 10 March 2004 07:36 am, Ruslan Ermilov wrote: > On Sun, Mar 07, 2004 at 08:50:38PM -0800, Jacob S. Barrett wrote: > > When might we see ng_vlan ported to FreeBSD-4? > > Go for it! How did I guess you would say that. I have started. -- Jacob S. Barrett jbarrett@amduat.net www.amduat.net "I don't suffer from insanity, I enjoy every minute of it." From owner-freebsd-net@FreeBSD.ORG Wed Mar 10 08:23: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 D644E16A4CE; Wed, 10 Mar 2004 08:23:24 -0800 (PST) Received: from rms04.rommon.net (rms04.rommon.net [212.54.2.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id B237043D2F; Wed, 10 Mar 2004 08:23:23 -0800 (PST) (envelope-from pete@he.iki.fi) Received: from he.iki.fi (h81.vuokselantie10.fi [193.64.42.129]) by rms04.rommon.net (8.12.9p1/8.12.9) with ESMTP id i2AGN9cM080696; Wed, 10 Mar 2004 18:23:09 +0200 (EET) (envelope-from pete@he.iki.fi) Message-ID: <404F40EB.6040702@he.iki.fi> Date: Wed, 10 Mar 2004 18:23:07 +0200 From: Petri Helenius User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brooks Davis References: <20040309214205.3EE2D5D07@ptavv.es.net> <20040309160821.P705@odysseus.silby.com> <20040310123237.V61186@beagle.fokus.fraunhofer.de> <20040310154139.GA14892@Odin.AC.HMC.Edu> In-Reply-To: <20040310154139.GA14892@Odin.AC.HMC.Edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Brad Knowles cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: Kevin Oberman Subject: Re: Who wants SACK? (Re: 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, 10 Mar 2004 16:23:25 -0000 Brooks Davis wrote: >> >> > >For that matter, there are sufficent drops on 10GbE from data errors to >insure that two boxes connected back to back won't achieve line speed on >a single TCP session. > > > Do you have data to back this up or are you just using broadcom chipsets? Pete From owner-freebsd-net@FreeBSD.ORG Wed Mar 10 11:17: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 2AD7316A4CF; Wed, 10 Mar 2004 11:17:30 -0800 (PST) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 495BD43D2F; Wed, 10 Mar 2004 11:17:29 -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 i2AJHEQE082056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Mar 2004 22:17:15 +0300 (MSK) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.9/8.12.6/Submit) id i2AJGvPO082055; Wed, 10 Mar 2004 22:16:57 +0300 (MSK) Date: Wed, 10 Mar 2004 22:16:57 +0300 From: Gleb Smirnoff To: Julian Elischer Message-ID: <20040310191657.GB81980@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Julian Elischer , Vasenin Alexander aka BlackSir , freebsd-isp@freebsd.org, "Bjoern A. Zeeb" , freebsd-net@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i cc: freebsd-isp@freebsd.org cc: "Bjoern A. Zeeb" cc: Vasenin Alexander aka BlackSir cc: freebsd-net@freebsd.org Subject: Re: ng_netflow: testers are welcome 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, 10 Mar 2004 19:17:30 -0000 On Mon, Feb 23, 2004 at 03:47:55PM -0800, Julian Elischer wrote: J> > All I've need - just create ksocket with inet/rawip/divert hook connected to J> > ng_netflow iface0 hook (mkpeer netflow: ksocket iface0 inet/raw/divert), J> > then "msg netflow: setdlt { iface=0 dlt=12 }" (Raw ip instead of ethernet), J> > then "msg divert: bind inet/0.0.0.0:8888". And after all add ipfw rule "tee J> > 8888 ip from any to any in"(One may need "via $oif") instead of final allow J> > (or, better, before it). <==skip==> J> This used to work but I have not tried it for some time J> and it may have been broken in ipfw2, as I never tested it.. J> natd is supposed to do this.. Since you can not do a "sendto()" J> in netgraph, you have to have done a "connect" on the socket J> to set the port number ahead of time.. J> J> Other things are also in the sockaddr.. J> in the 8 "unused" bytes of the sockaddr we "hide" the incoming interface J> name (for example) netgraph cannot change that but it should not need J> this as it has the actual mbufs and can just set th eiface pointer in J> the packet header.. (assuming divert doesn't clear it.. J> once again, you'll need to look at the code). I have finally tried this out on CURRENT. Everything works fine as expected: ng_ksocket in divert mode reinjects packets back into the proper firewall rule, netflow collects info about demasqueraded IPs... OK. Here is my config: netgraph: mkpeer tee dummy right2left name .:dummy divert_tee_in mkpeer divert_tee_in: echo right echo mkpeer divert_tee_in: ksocket left inet/raw/divert name divert_tee_in:left divert_sock_in msg divert_sock_in: bind inet/0.0.0.0:8669 disconnect dummy mkpeer divert_tee_in: netflow left2right iface0 name divert_tee_in:left2right netflow msg netflow: setdlt { iface=0 dlt=12 } msg netflow: setifindex { iface=0 index=6 } mkpeer netflow: ksocket export inet/dgram/udp msg netflow:export connect inet/127.0.0.1:4444 ipfw: 00200 divert 8668 ip from any to any in via ${nat_if} 00201 divert 8669 ip from any to any in via ${nat_if} .... some other stuff 00600 divert 8668 ip from any to any out via ${nat_if} -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Wed Mar 10 11:23: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 4C4DB16A4CE; Wed, 10 Mar 2004 11:23:07 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 317AF43D39; Wed, 10 Mar 2004 11:23:07 -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 i2AJMuaN015420; Wed, 10 Mar 2004 11:22:57 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i2AJMunX015415; Wed, 10 Mar 2004 11:22:56 -0800 Date: Wed, 10 Mar 2004 11:22:56 -0800 From: Brooks Davis To: Petri Helenius Message-ID: <20040310192255.GD14892@Odin.AC.HMC.Edu> References: <20040309214205.3EE2D5D07@ptavv.es.net> <20040309160821.P705@odysseus.silby.com> <20040310123237.V61186@beagle.fokus.fraunhofer.de> <20040310154139.GA14892@Odin.AC.HMC.Edu> <404F40EB.6040702@he.iki.fi> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DrWhICOqskFTAXiy" Content-Disposition: inline In-Reply-To: <404F40EB.6040702@he.iki.fi> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: Brad Knowles cc: Kevin Oberman cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Who wants SACK? (Re: 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, 10 Mar 2004 19:23:07 -0000 --DrWhICOqskFTAXiy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 10, 2004 at 06:23:07PM +0200, Petri Helenius wrote: > Brooks Davis wrote: >=20 > >For that matter, there are sufficent drops on 10GbE from data errors to > >insure that two boxes connected back to back won't achieve line speed on > >a single TCP session. > > > Do you have data to back this up or are you just using broadcom chipsets? I looked for the paper I paraphrased, I'm pretty sure if was one by Sally Floyd. I didn't find it, but this paper talks a bit about the issue on page 7: http://www.calit2.net/research/labs/features/CACM/CACMDefanti.pdf The problem is that the BER of a typical optical link is high enough that the link will almost certantly discard at least one packet before you get out of slow-start and once that happens it, AIMK means it take hours or even days to get back up to the top even assuming you don't lose further packets. This isn't a problem for most people, but it's definalty a problem for the HPC community. -- 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 --DrWhICOqskFTAXiy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAT2sPXY6L6fI4GtQRAt8QAJ9PoSpeV5C5XC/QkSqz1ZVYVQ1YyACgsWu2 4WosEDYE2UlkV+6gvX+W5/I= =ZZPZ -----END PGP SIGNATURE----- --DrWhICOqskFTAXiy-- From owner-freebsd-net@FreeBSD.ORG Wed Mar 10 11:38: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 42E7A16A4DB; Wed, 10 Mar 2004 11:38: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 137EF43D1F; Wed, 10 Mar 2004 11:38:42 -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 6479F77A6D4; Wed, 10 Mar 2004 14:38:40 -0500 (EST) To: Brooks Davis From: Mark Allman In-Reply-To: <20040310192255.GD14892@Odin.AC.HMC.Edu> Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: Imagine MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Date: Wed, 10 Mar 2004 14:38:40 -0500 Sender: mallman@guns.icir.org Message-Id: <20040310193840.6479F77A6D4@guns.icir.org> cc: Brad Knowles cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: Kevin Oberman Subject: Re: Who wants SACK? (Re: was 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: Wed, 10 Mar 2004 19:38:42 -0000 --=-=-= > I looked for the paper I paraphrased, I'm pretty sure if was one by > Sally Floyd. I don't have the paper reference handy, but it's Sally's HighSpeed TCP work. I do happen to have a blurb on it sitting here that I think captures it well... Think of a network with an RTT of 100ms, a 1500 byte packet size and 10Gbps capacity. That means the congestion window needs to be 83,333 packets to fill the pipe (just by looking at the delay*bandwidth product of the network). And, to sustain this rate you need at most one loss every 5,000,000,000 packets (from the TCP model). That translates into about one loss every 100 minutes. And, that seems like a fairly large stretch. (This actually might be laid out in RFC3649.) However, this is a bit off-topic from SACK. Because this is all based on the AIMD nature of TCP's congestion control, not really on whether you employ SACK. (The world would be worse than described above if you didn't use SACK. But, if you have to take at most one loss every 100 minutes that's pretty bad already.) There is an experimental change to TCP's algorithms specified in RFC3649 (that only applies when you are going quite fast). allman -- Mark Allman -- ICIR -- http://www.icir.org/mallman/ --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFAT27AWyrrWs4yIs4RAu8tAJ9GguPWqUuyEUzdCoNTmECVS+dlLwCeI8zU LVuiXT0+1FHf03QjAW4NaJk= =zGI3 -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-net@FreeBSD.ORG Wed Mar 10 13:08: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 B035A16A4CE; Wed, 10 Mar 2004 13:08:19 -0800 (PST) Received: from rms04.rommon.net (rms04.rommon.net [212.54.2.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id A917743D1F; Wed, 10 Mar 2004 13:08:18 -0800 (PST) (envelope-from pete@he.iki.fi) Received: from he.iki.fi (h81.vuokselantie10.fi [193.64.42.129]) by rms04.rommon.net (8.12.9p1/8.12.9) with ESMTP id i2AL82cM081405; Wed, 10 Mar 2004 23:08:02 +0200 (EET) (envelope-from pete@he.iki.fi) Message-ID: <404F83B0.7020803@he.iki.fi> Date: Wed, 10 Mar 2004 23:08:00 +0200 From: Petri Helenius User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brooks Davis References: <20040309214205.3EE2D5D07@ptavv.es.net> <20040309160821.P705@odysseus.silby.com> <20040310123237.V61186@beagle.fokus.fraunhofer.de> <20040310154139.GA14892@Odin.AC.HMC.Edu> <404F40EB.6040702@he.iki.fi> <20040310192255.GD14892@Odin.AC.HMC.Edu> In-Reply-To: <20040310192255.GD14892@Odin.AC.HMC.Edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Brad Knowles cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: Kevin Oberman Subject: Re: Who wants SACK? (Re: 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, 10 Mar 2004 21:08:20 -0000 Brooks Davis wrote: >The problem is that the BER of a typical optical link is high enough >that the link will almost certantly discard at least one packet before >you get out of slow-start and once that happens it, AIMK means it take >hours or even days to get back up to the top even assuming you don't >lose further packets. This isn't a problem for most people, but it's >definalty a problem for the HPC community. > > > BER is usually combatted with technologies which embed redundant bits into the datastream so an occasional bit error does not take out a packet. In conjuction of 10GbE this would probably mean G.709. I would be happy to learn whether the typical link has BER of 10E-15 or 10E-12 and how fast retransmit plays in the picture of losing a bit every ten minutes or so. Pete From owner-freebsd-net@FreeBSD.ORG Wed Mar 10 13:53: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 DE02B16A4CE; Wed, 10 Mar 2004 13:53:09 -0800 (PST) Received: from ob.icann.org (unknown [192.0.35.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9EC343D1D; Wed, 10 Mar 2004 13:53:09 -0800 (PST) (envelope-from DougB@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by ob.icann.org (8.12.11/8.12.11) with ESMTP id i2ALr9wc001390; Wed, 10 Mar 2004 13:53:09 -0800 (PST) (envelope-from DougB@FreeBSD.org) Date: Wed, 10 Mar 2004 13:53:08 -0800 (PST) From: Doug Barton To: "freebsd-net@freebsd.org" In-Reply-To: Message-ID: <20040310134953.W875@bo.vpnaa.bet> References: Organization: http://www.FreeBSD.org/ X-message-flag: Outlook -- Not just for spreading viruses anymore! MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "freebsd-current@freebsd.org" Subject: Re: Who wants SACK? (Re: 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, 10 Mar 2004 21:53:10 -0000 FWIW, I have heard the same type of stuff during my travels that's been reported here already. "We'd like to have used FreeBSD for this project, but it doesn't support SACK. We're at a difficult juncture here, since on the one hand it's widely acknowledged that we're (almost) all volunteers, so no one can tell us what to work on. :) OTOH, some members of the project have said that they'd like $SOMEONE to provide guidance to the project as a whole. I think this might be a good area for someone official (which is certainly not me) to stand up and say, "Yes, the project wants SACK, who's up for it?" Doug -- This .signature sanitized for your protection From owner-freebsd-net@FreeBSD.ORG Wed Mar 10 15:17: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 C2F0316A4CF for ; Wed, 10 Mar 2004 15:17:58 -0800 (PST) Received: from tx3.oucs.ox.ac.uk (tx3.oucs.ox.ac.uk [163.1.2.167]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D2B943D48 for ; Wed, 10 Mar 2004 15:17:58 -0800 (PST) (envelope-from colin.percival@wadham.ox.ac.uk) Received: from scan3.oucs.ox.ac.uk ([163.1.2.166] helo=localhost) by tx3.oucs.ox.ac.uk with esmtp (Exim 4.24) id 1B1CxZ-0005lY-N9 for freebsd-net@freebsd.org; Wed, 10 Mar 2004 23:17:57 +0000 Received: from rx3.oucs.ox.ac.uk ([163.1.2.165]) by localhost (scan3.oucs.ox.ac.uk [163.1.2.166]) (amavisd-new, port 25) with ESMTP id 21879-06 for ; Wed, 10 Mar 2004 23:17:57 +0000 (GMT) Received: from gateway.wadham.ox.ac.uk ([163.1.161.253]) by rx3.oucs.ox.ac.uk with smtp (Exim 4.24) id 1B1CxZ-0005lV-9m for freebsd-net@freebsd.org; Wed, 10 Mar 2004 23:17:57 +0000 Received: (qmail 26187 invoked by uid 1004); 10 Mar 2004 23:17:57 -0000 Received: from colin.percival@wadham.ox.ac.uk by gateway by uid 71 with qmail-scanner-1.20 (clamscan: 0.67. sweep: 2.18/3.79. Clear:RC:1(163.1.161.131):. Processed in 0.018151 secs); 10 Mar 2004 23:17:57 -0000 Received: from dhcp1131.wadham.ox.ac.uk (HELO piii600.wadham.ox.ac.uk) (163.1.161.131) by gateway.wadham.ox.ac.uk with SMTP; 10 Mar 2004 23:17:56 -0000 Message-Id: <6.0.1.1.1.20040310231226.03cee598@imap.sfu.ca> X-Sender: cperciva@imap.sfu.ca (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Wed, 10 Mar 2004 23:17:54 +0000 To: freebsd-net@freebsd.org From: Colin Percival Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: secteam@freebsd.org Subject: Broadcast storming 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, 10 Mar 2004 23:17:59 -0000 [CC: secteam, since this relates to a recent advisory] In http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/64053 a problem is reported as having been introduced by the recent TCP reassembly patch. Could someone look into this please? Colin Percival From owner-freebsd-net@FreeBSD.ORG Wed Mar 10 15:53: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 3A83316A4CE; Wed, 10 Mar 2004 15:53:41 -0800 (PST) Received: from mail.dt.e-technik.uni-dortmund.de (mail.dt.E-Technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8CF243D2D; Wed, 10 Mar 2004 15:53:40 -0800 (PST) (envelope-from matthias.andree@gmx.de) Received: from m2a2.dyndns.org (krusty.dt.e-technik.uni-dortmund.de [129.217.163.1])D0AFB23D94; Thu, 11 Mar 2004 00:53:39 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id DA1BF1CF0; Thu, 11 Mar 2004 00:53:36 +0100 (CET) Received: from merlin.emma.line.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 29212-03; Thu, 11 Mar 2004 00:53:36 +0100 (CET) Received: from sigma.emma.line.org (sigma.emma.line.org [192.168.0.49]) by merlin.emma.line.org (Postfix) with ESMTP id 56651DE7; Thu, 11 Mar 2004 00:53:36 +0100 (CET) Received: by sigma.emma.line.org (Postfix, from userid 500) id 1C3AC5C33; Thu, 11 Mar 2004 00:53:36 +0100 (CET) To: FreeBSD-gnats-submit@freebsd.org From: Matthias Andree X-send-pr-version: 3.113 X-GNATS-Notify: Message-Id: <20040310235336.1C3AC5C33@sigma.emma.line.org> Date: Thu, 11 Mar 2004 00:53:36 +0100 (CET) X-Virus-Scanned: by amavisd-new at !change-mydomain-variable!.example.com cc: Max Laier cc: gshapiro@freebsd.org cc: current@freebsd.org cc: peter@freebsd.org cc: net@freebsd.org Subject: PATCH: Makefile.inc1 r1.411 jams make installworld 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, 10 Mar 2004 23:53:41 -0000 >Submitter-Id: current-users >Originator: Matthias Andree >Organization: >Confidential: no >Synopsis: PATCH: Makefile.inc1 r1.411 jams make installworld >Severity: critical >Priority: low >Category: misc >Class: sw-bug >Release: FreeBSD 5.2-CURRENT i386 >Environment: System: FreeBSD sigma.emma.line.org 5.2-CURRENT FreeBSD 5.2-CURRENT #3: Wed Mar 10 22:29:45 CET 2004 root@sigma.emma.line.org:/usr/src/sys/i386/compile/SIGMA i386 >Description: "make installworld" fails, complaining the required authpf group was missing: -bash-2.05b# grep -w authpf /etc/group authpf:*:63: -bash-2.05b# make installworld id: authpf: no such user ERROR: Required authpf group is missing, see /usr/src/UPDATING. *** Error code 1 Cause: The recent Makefile.inc1 change in rev. 1.411 of that file is bogus, it is a copy of a bogus line further up in the file that was shadowed by a mandatory user account with the same name as the group that was supposed to be checked. "id -g authpf" does not check if a *group* "authpf" exists but returns the primary group ID of the *user* "authpf". Result as above. Looking closer, the same problem applies to the "id -g smmsp" check that used to be fine (albeit inefficient) but was repaired broken in revision 1.376 on 2003-07-06 by gshapiro after suggestion from peter. I am suggesting the patch below that checks /etc/group with grep and then NIS with ypmatch. This is a bit ugly but will serve for now. A more complex but nsswitch-proof alternative would be to create a dummy file, for instance: echo "delete me" >${DECENTPATH}/dummy$$ chgrp smmsp ${DECENTPATH}/dummy$$ DECENTPATH should be somewhere writable below the installation location, it won't hurt there, or in a temporary directory that is not prone to symlink attacks (i. e. that is not world writable). >How-To-Repeat: Update the FreeBSD -CURRENT base system as usual. >Fix: Patch /usr/src/Makefile.inc1 as follows: --- Makefile.inc1~ Wed Mar 10 22:10:11 2004 +++ Makefile.inc1 Thu Mar 11 00:35:58 2004 @@ -409,25 +409,28 @@ # installcheck: ${SPECIAL_INSTALLCHECKS} .if !defined(NO_SENDMAIL) - @if ! `id -u smmsp > /dev/null`; then \ + @if ! id -u smmsp > /dev/null; then \ echo "ERROR: Required smmsp user is missing, see /usr/src/UPDATING."; \ false; \ fi - @if ! `id -g smmsp > /dev/null`; then \ + @if ! grep '^smmsp:' /etc/group > /dev/null \ + && ! ypmatch smmsp group >/dev/null ; then \ echo "ERROR: Required smmsp group is missing, see /usr/src/UPDATING."; \ false; \ fi .endif .if !defined(NO_PF) - @if ! `id -u proxy > /dev/null`; then \ + @if ! id -u proxy > /dev/null; then \ echo "ERROR: Required proxy user is missing, see /usr/src/UPDATING."; \ false; \ fi - @if ! `id -g proxy > /dev/null`; then \ + @if ! grep '^proxy:' /etc/group > /dev/null \ + && ! ypmatch proxy group >/dev/null ; then \ echo "ERROR: Required proxy group is missing, see /usr/src/UPDATING."; \ false; \ fi - @if ! `id -g authpf > /dev/null`; then \ + @if ! grep '^authpf:' /etc/group > /dev/null \ + && ! ypmatch authpf group >/dev/null ; then \ echo "ERROR: Required authpf group is missing, see /usr/src/UPDATING."; \ false; \ fi From owner-freebsd-net@FreeBSD.ORG Wed Mar 10 17:36: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 BB36816A4CE for ; Wed, 10 Mar 2004 17:36:02 -0800 (PST) Received: from smtp09.wxs.nl (smtp09.wxs.nl [195.121.6.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AF0943D1F for ; Wed, 10 Mar 2004 17:36:02 -0800 (PST) (envelope-from pblok@bsd4all.org) Received: from mail.bsd4all.org (ip503cf841.speed.planet.nl [80.60.248.65]) by smtp09.wxs.nl (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with ESMTP id <0HUE00M8D1S037@smtp09.wxs.nl> for freebsd-net@freebsd.org; Thu, 11 Mar 2004 02:36:00 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by mail.bsd4all.org (Postfix) with ESMTP id 109F5A924 for ; Thu, 11 Mar 2004 02:36:01 +0100 (CET) Received: from mail.bsd4all.org ([127.0.0.1]) by localhost (fwgw [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 58707-02-2 for ; Thu, 11 Mar 2004 02:35:59 +0100 (CET) Received: from localhost.invalid (bsdpc [192.168.1.135]) by mail.bsd4all.org (Postfix) with ESMTP id 34C3BA923 for ; Thu, 11 Mar 2004 02:35:59 +0100 (CET) Date: Thu, 11 Mar 2004 02:35:33 +0000 From: Peter Blok To: freebsd-net@freebsd.org Message-id: <200403110235.33955.pblok@bsd4all.org> Organization: bsd4all MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: KMail/1.6 X-Virus-Scanned: by amavisd-new at bsd4all.org Subject: test - ignore 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, 11 Mar 2004 01:36:02 -0000 From owner-freebsd-net@FreeBSD.ORG Thu Mar 11 01:29: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 4523316A4CE for ; Thu, 11 Mar 2004 01:29:41 -0800 (PST) Received: from kozlik.carrier.kiev.ua (kozlik.carrier.kiev.ua [193.193.193.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DCF343D53 for ; Thu, 11 Mar 2004 01:29:40 -0800 (PST) (envelope-from news@pandora.alkar.net) Received: from news.lucky.net (IDENT:root@news.lucky.net [193.193.193.102]) by kozlik.carrier.kiev.ua with ESMTP id i3B9TZ8R005616 for ; Thu, 11 Mar 2004 11:29:37 +0200 (EET) (envelope-from news@pandora.alkar.net) Received: (from mail@localhost) by news.lucky.net (8.Who.Cares/8.Who.Cares) id LJL32294 for freebsd-net@freebsd.org; Thu, 11 Mar 2004 11:24:34 +0200 (envelope-from news@pandora.alkar.net) From: Alexander Motin To: freebsd-net@freebsd.org Date: Wed, 10 Mar 2004 20:11:40 +0200 Organization: Alkar Teleport News Server Message-ID: <404F5A5C.7010704@alkar.net> References: <1078786384.00003365.1078771201@10.7.7.3> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: pandora.alkar.net 1078942301 65437 212.86.226.11 (10 Mar 2004 18:11:41 GMT) X-Complaints-To: abuse@alkar.net User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040119 X-Accept-Language: ru, en-us, en In-Reply-To: <1078786384.00003365.1078771201@10.7.7.3> Sender: Alkar Teleport News Subsystem X-Verify-Sender: verified Subject: Re: mpd-3.16 and PPPoE server mode on 5.2.1-RELEASE 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, 11 Mar 2004 09:29:41 -0000 Hi. There is a two problems with support of PPPoE in mpd under 5.x: 1. sometimes loading of netgraph modules on request cause system crash. (You can compile in all required modules.) 2. PPPoE in mpd do not works now on 5.x because of ununderstandible changes in ng_tee shutdown mechanism. (Now ng_tee don't connect left and right hooks on shutdown) So mpd now can't handle incoming PPPoE connections right. Vadim A. Shklyaev wrote: > I've decided to migrate from 4.9-STABLE to 5.2.1-RELEASE, and found, > that mpd-3.16 on 5.2.1-RELEASE works strange: everything is ok, for > example, with generic vpn, but PPPoE server mode crashes system, > when loading netgraph modules as kld. When i've recompiled kernel > with compiled-in NETGRAPH support, it accepts connection, netgraph > reports NGM_PPPOE_SUCCESS, and immediantly after that - > NGM_PPPOE_CLOSE. > > Configuration file used are quite simple, and proved to be ok on > 4.9-STABLE system. > > pppoed works fine, btw, source code for pppoed didn't change since > 4.9-STABLE. > > So, question, does anyone have mpd work as pppoe-server on > FreeBSD-5? Or may be any ideas, why does it happen? -- Alexander Motin mav@alkar.net ISP "Alkar-Teleport" From owner-freebsd-net@FreeBSD.ORG Thu Mar 11 01:29: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 BFB7E16A4CE for ; Thu, 11 Mar 2004 01:29:56 -0800 (PST) Received: from mizar.origin-it.net (mizar.origin-it.net [194.8.96.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAFAE43D46 for ; Thu, 11 Mar 2004 01:29:55 -0800 (PST) (envelope-from helge.oldach@atosorigin.com) Received: from matar.hbg.de.int.atosorigin.com (dehsfw3e.origin-it.net [194.8.96.68])i2B9TqbP028105 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Mar 2004 10:29:53 +0100 (CET) (envelope-from helge.oldach@atosorigin.com) Received: from galaxy.hbg.de.ao-srv.com (galaxy.hbg.de.ao-srv.com [161.89.20.4])ESMTP id i2B9TqRu021766; Thu, 11 Mar 2004 10:29:52 +0100 (CET) (envelope-from helge.oldach@atosorigin.com) Received: (from hmo@localhost) by galaxy.hbg.de.ao-srv.com (8.9.3p2/8.9.3/hmo30mar03) id KAA27502; Thu, 11 Mar 2004 10:29:51 +0100 (MET) Message-Id: <200403110929.KAA27502@galaxy.hbg.de.ao-srv.com> In-Reply-To: <20040310052556.GA33553@OntheNet.com.au> from Nick Slager at "Mar 10, 2004 6:25:56 am" To: nicks@OntheNet.com.au (Nick Slager) Date: Thu, 11 Mar 2004 10:29:51 +0100 (MET) From: Helge Oldach X-Address: Atos Origin GmbH, Friesenstraße 13, D-20097 Hamburg, Germany X-Phone: +49 40 7886 7464, Fax: +49 40 7886 9464, Mobile: +49 160 4782517 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: net@freebsd.org Subject: Re: IPsec: odd behaviour with policies 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, 11 Mar 2004 09:29:56 -0000 Nick Slager: >I have a newly created VPN between a 4.8 box and a Cisco VPN 3000 >Concentrator. > >/etc/ipsec.conf: > >flush; >spdflush; >spdadd 192.168.1.1/32 1.2.3.4/32 any -P out ipsec >esp/tunnel/203.1.1.1-203.2.2.2/require; >spdadd 1.2.3.4/32 192.168.1.1/32 any -P in ipsec >esp/tunnel/203.2.2.2-203.1.1.1/require; > >spdadd 192.168.1.1/32 1.2.3.5/32 any -P out ipsec >esp/tunnel/203.1.1.1-203.2.2.2/require; >spdadd 1.2.3.5/32 192.168.1.1/32 any -P in ipsec >esp/tunnel/203.2.2.2-203.1.1.1/require; Try using "unique" instead of "require". (This is my standard answer on the subject. :-)) Helge From owner-freebsd-net@FreeBSD.ORG Thu Mar 11 04:01: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 D60EF16A4CF for ; Thu, 11 Mar 2004 04:01:19 -0800 (PST) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1721543D3F for ; Thu, 11 Mar 2004 04:01:19 -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 i2BC1AQE086948 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Mar 2004 15:01:11 +0300 (MSK) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.9/8.12.6/Submit) id i2BC1AGS086947; Thu, 11 Mar 2004 15:01:10 +0300 (MSK) Date: Thu, 11 Mar 2004 15:01:10 +0300 From: Gleb Smirnoff To: Alexander Motin Message-ID: <20040311120110.GA86830@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Alexander Motin , freebsd-net@freebsd.org References: <1078786384.00003365.1078771201@10.7.7.3> <404F5A5C.7010704@alkar.net> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <404F5A5C.7010704@alkar.net> User-Agent: Mutt/1.5.6i cc: freebsd-net@freebsd.org Subject: Re: mpd-3.16 and PPPoE server mode on 5.2.1-RELEASE 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, 11 Mar 2004 12:01:20 -0000 On Wed, Mar 10, 2004 at 08:11:40PM +0200, Alexander Motin wrote: A> There is a two problems with support of PPPoE in mpd under 5.x: A> 1. sometimes loading of netgraph modules on request cause system crash. A> (You can compile in all required modules.) Have you run kldxref after installing modules? A> 2. PPPoE in mpd do not works now on 5.x because of ununderstandible A> changes in ng_tee shutdown mechanism. (Now ng_tee don't connect left and A> right hooks on shutdown) So mpd now can't handle incoming PPPoE A> connections right. In CURRENT netgraph method xxx_shutdown() is called _after_ all hooks has been disconnected. I think this is not very good idea. In some cases node needs to send some data before shutdown, for example ng_pppoe should close all active sessions sending PADT message, otherwise we have got hanging sessions on remote side. Some other protocols implementations may require sending of data before shutting down. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Thu Mar 11 06:09: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 2A8F816A4CF for ; Thu, 11 Mar 2004 06:09:01 -0800 (PST) Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6280943D54 for ; Thu, 11 Mar 2004 06:09:00 -0800 (PST) (envelope-from andre@freebsd.org) Received: (qmail 55706 invoked from network); 11 Mar 2004 14:08:56 -0000 Received: from unknown (HELO freebsd.org) ([213.187.67.40]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 11 Mar 2004 14:08:56 -0000 Message-ID: <405072E8.9A333E99@freebsd.org> Date: Thu, 11 Mar 2004 15:08:40 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Colin Percival References: <6.0.1.1.1.20040310231226.03cee598@imap.sfu.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: secteam@freebsd.org Subject: Re: Broadcast storming 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: Thu, 11 Mar 2004 14:09:01 -0000 Colin Percival wrote: > > [CC: secteam, since this relates to a recent advisory] > > In http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/64053 a > problem is reported as having been introduced by the recent > TCP reassembly patch. > Could someone look into this please? Reading the description of the problem I find it highly unlikely that the TCP reassembly changes would have caused this. The TCP reassembly code only comes into play when a packet belongs to an established TCP session. And it doesn't generate any kind of packet by itself, it only drops them if there are too many. The problem in this PR must come from something else in IP stack. I don't have a clear idea what it can be and I'm at conference till tomorrow and only have slow modem access. -- Andre From owner-freebsd-net@FreeBSD.ORG Thu Mar 11 14:53: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 1EBB116A4CE; Thu, 11 Mar 2004 14:53:50 -0800 (PST) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 24D2143D1D; Thu, 11 Mar 2004 14:53:49 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 11 Mar 2004 22:53:48 +0000 (GMT) Date: Thu, 11 Mar 2004 22:53:47 +0000 From: David Malone To: Mark Allman Message-ID: <20040311225347.GA66644@walton.maths.tcd.ie> References: <20040310192255.GD14892@Odin.AC.HMC.Edu> <20040310193840.6479F77A6D4@guns.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040310193840.6479F77A6D4@guns.icir.org> User-Agent: Mutt/1.5.3i Sender: dwmalone@maths.tcd.ie cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Who wants SACK? (Re: 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: Thu, 11 Mar 2004 22:53:50 -0000 On Wed, Mar 10, 2004 at 02:38:40PM -0500, Mark Allman wrote: > > I looked for the paper I paraphrased, I'm pretty sure if was one by > > Sally Floyd. > > I don't have the paper reference handy, but it's Sally's HighSpeed TCP > work. I do happen to have a blurb on it sitting here that I think > captures it well... Think of a network with an RTT of 100ms, a 1500 Mind you, Petri originally asked about evidence for two machines back-to-back, and 100ms is rather long for that (unless you're at Steven Low's lab ;-) David. From owner-freebsd-net@FreeBSD.ORG Thu Mar 11 18:17: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 CEE6216A4CE; Thu, 11 Mar 2004 18:17:19 -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 9C74843D41; Thu, 11 Mar 2004 18:17:19 -0800 (PST) (envelope-from mallman@icir.org) Received: from lawyers.icir.org (adsl-68-76-113-50.dsl.bcvloh.ameritech.net [68.76.113.50]) by guns.icir.org (Postfix) with ESMTP id 55DAC77A6D4; Thu, 11 Mar 2004 21:17:17 -0500 (EST) Received: from lawyers.icir.org (localhost [127.0.0.1]) by lawyers.icir.org (Postfix) with ESMTP id C531610FFC3; Thu, 11 Mar 2004 21:17:17 -0500 (EST) To: David Malone From: Mark Allman In-Reply-To: <20040311225347.GA66644@walton.maths.tcd.ie> Organization: ICSI Center for Internet Research (ICIR) Song-of-the-Day: Ain't Even Done With the Night MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Date: Thu, 11 Mar 2004 21:17:17 -0500 Sender: mallman@icir.org Message-Id: <20040312021717.C531610FFC3@lawyers.icir.org> cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Who wants SACK? (Re: was 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: Fri, 12 Mar 2004 02:17:19 -0000 --=-=-= > On Wed, Mar 10, 2004 at 02:38:40PM -0500, Mark Allman wrote: > > > I looked for the paper I paraphrased, I'm pretty sure if was one by > > > Sally Floyd. > > > > I don't have the paper reference handy, but it's Sally's HighSpeed TCP > > work. I do happen to have a blurb on it sitting here that I think > > captures it well... Think of a network with an RTT of 100ms, a 1500 > > Mind you, Petri originally asked about evidence for two machines > back-to-back, and 100ms is rather long for that (unless you're at > Steven Low's lab ;-) (I gave what was a handy example that happened to be in the ICSI annual report that arrived on my desk yesterday. Check the RFC reference and re-compute as needed.) allman -- Mark Allman -- ICIR -- http://www.icir.org/mallman/ --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (Darwin) iD8DBQFAUR2tWyrrWs4yIs4RAnnVAJ9UWx0ApxKo6hubo1vTBXDj13RmDQCdGRNu KkblOCosm+RAClfalxqmd3w= =L9WQ -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-net@FreeBSD.ORG Thu Mar 11 20:30:27 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DEF7116A4CE; Thu, 11 Mar 2004 20:30:27 -0800 (PST) Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9B1F43D54; Thu, 11 Mar 2004 20:30:27 -0800 (PST) (envelope-from thomas.r.henderson@boeing.com) Received: from slb-av-02.boeing.com ([129.172.13.7])id UAA18242; Thu, 11 Mar 2004 20:30:26 -0800 (PST) Received: from slb-hub-01.boeing.com (localhost [127.0.0.1])UAA17102; Thu, 11 Mar 2004 20:30:26 -0800 (PST) Received: from XCH-NWBH-01.nw.nos.boeing.com (xch-nwbh-01.nw.nos.boeing.com [192.33.62.231])i2C4T8E04469; Thu, 11 Mar 2004 20:29:08 -0800 (PST) Received: from XCH-NW-27.nw.nos.boeing.com ([192.48.4.101]) by XCH-NWBH-01.nw.nos.boeing.com with Microsoft SMTPSVC(5.0.2195.6662); Thu, 11 Mar 2004 20:29:08 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6521.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Thu, 11 Mar 2004 20:29:07 -0800 Message-ID: <6938661A6EDA8A4EA8D1419BCE46F24C040604EF@xch-nw-27.nw.nos.boeing.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Who wants SACK? (Re: was My planned work on networking stack) Thread-Index: AcQGI8WG23sACpizT6mVSTsOiKvaRQBwnCPQ From: "Henderson, Thomas R" To: "Mike Silbersack" , "Kevin Oberman" X-OriginalArrivalTime: 12 Mar 2004 04:29:08.0449 (UTC) FILETIME=[8F800510:01C407EA] cc: Brad Knowles cc: freebsd-current@freebsd.org cc: freebsd-net@freebsd.org Subject: RE: Who wants SACK? (Re: 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: Fri, 12 Mar 2004 04:30:28 -0000 > -----Original Message----- > From: Mike Silbersack [mailto:silby@silby.com] > Sent: Tuesday, March 09, 2004 2:12 PM > To: Kevin Oberman > Cc: Brad Knowles; freebsd-current@freebsd.org; freebsd-net@freebsd.org > Subject: Re: Who wants SACK? (Re: was My planned work on networking > stack)=20 >=20 >=20 > SACK itself really doesn't do much, it's all the new=20 > congestion control > schemes (FACK, Rate Halving, etc) that come shipped with most SACK > implementations that do the work and contain most of the complexity. >=20 That's not quite true. Basic SACK by itself can be very helpful,=20 especially if NewReno is the non-SACK fallback, in long delay = environments=20 characterized by bursty losses (multiple packets in one window). =20 With NewReno, you end up only recovering one packet per RTT, which=20 can in some cases be much worse than just taking a timeout and=20 starting over. See below paper for some experimental traces=20 of this: http://citeseer.ist.psu.edu/henderson99transport.html (not that I don't think that the more recent RFCs are an improvement on basic SACK) As for who/when to do this, I and perhaps others have been discouraged=20 from taking a stab at a SACK patch in the past, because of a sentiment that it should be undertaken as part of a bigger rewrite of TCP. =20 Tom p.s. Niels Provos ported our Berkeley BSDi-based SACK extension to OpenBSD several years ago-- that might be something to look at as a starting point. From owner-freebsd-net@FreeBSD.ORG Thu Mar 11 20:46: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 ECCC016A4CE for ; Thu, 11 Mar 2004 20:46:23 -0800 (PST) Received: from diablo.OntheNet.com.au (diablo.OntheNet.com.au [203.10.89.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E32143D45 for ; Thu, 11 Mar 2004 20:46:23 -0800 (PST) (envelope-from nicks@diablo.onthenet.com.au) Received: from mail.onthenet.com.au (vdub.OntheNet.net [203.10.89.16]) i2C4kHM5056085; Fri, 12 Mar 2004 14:46:18 +1000 (EST) Received: by mail.onthenet.com.au (Postfix, from userid 1001) id 59ECC1762A; Fri, 12 Mar 2004 14:45:59 +1000 (EST) Date: Fri, 12 Mar 2004 14:45:59 +1000 From: Nick Slager To: Helge Oldach Message-ID: <20040312044559.GA1083@OntheNet.com.au> References: <20040310052556.GA33553@OntheNet.com.au> <200403110929.KAA27502@galaxy.hbg.de.ao-srv.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200403110929.KAA27502@galaxy.hbg.de.ao-srv.com> User-Agent: Mutt/1.4.2i X-Homer: Whoohooooooo! cc: net@freebsd.org Subject: Re: IPsec: odd behaviour with policies 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, 12 Mar 2004 04:46:24 -0000 Thus spake Helge Oldach (helge.oldach@atosorigin.com): > Nick Slager: > >I have a newly created VPN between a 4.8 box and a Cisco VPN 3000 > >Concentrator. > > [ ... ] > Try using "unique" instead of "require". > > (This is my standard answer on the subject. :-)) Thanks, it works great. After re-reading the manpage, it actually makes sense. cheers, Nick From owner-freebsd-net@FreeBSD.ORG Thu Mar 11 21:41: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 8A42316A4CE; Thu, 11 Mar 2004 21:41:18 -0800 (PST) Received: from rms04.rommon.net (rms04.rommon.net [212.54.2.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70EAB43D2D; Thu, 11 Mar 2004 21:41:17 -0800 (PST) (envelope-from pete@he.iki.fi) Received: from he.iki.fi (h81.vuokselantie10.fi [193.64.42.129]) by rms04.rommon.net (8.12.9p1/8.12.9) with ESMTP id i2C5fEcM087064; Fri, 12 Mar 2004 07:41:14 +0200 (EET) (envelope-from pete@he.iki.fi) Message-ID: <40514D78.6020605@he.iki.fi> Date: Fri, 12 Mar 2004 07:41:12 +0200 From: Petri Helenius User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Malone References: <20040310192255.GD14892@Odin.AC.HMC.Edu> <20040310193840.6479F77A6D4@guns.icir.org> <20040311225347.GA66644@walton.maths.tcd.ie> In-Reply-To: <20040311225347.GA66644@walton.maths.tcd.ie> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: Mark Allman Subject: Re: Who wants SACK? (Re: 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: Fri, 12 Mar 2004 05:41:18 -0000 David Malone wrote: >Mind you, Petri originally asked about evidence for two machines >back-to-back, and 100ms is rather long for that (unless you're at >Steven Low's lab ;-) > > Another interesting figure which comes to mind is whether "bursty loss" is the usual way a multigigabit optical link loses IP packets or if the flipping of single bit hits only one packet. This influences the actual real life problem a lot and in my understanding of 8B/10B coding, it´s designed not to lose sync over a single bit error so with a probability of bit error every few minutes, hitting two in close succession (in the window) is unlikely. Some time ago we did experiments implementing FEC at IP layer to make the multimedia which run over the network zero loss. While doing the experiment we recognized that the clustered loss we saw was caused by software issues in routers, not at any transmission devices. Using somewhat deeper interleaving of packets solved the issue with this application. Pete From owner-freebsd-net@FreeBSD.ORG Thu Mar 11 21:51: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 E52FB16A4CE; Thu, 11 Mar 2004 21:51:33 -0800 (PST) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 235DF43D45; Thu, 11 Mar 2004 21:51:32 -0800 (PST) (envelope-from eugen@kuzbass.ru) Received: from kuzbass.ru (kost [213.184.65.82])i2C5pSLJ013339; Fri, 12 Mar 2004 12:51:28 +0700 (KRAT) (envelope-from eugen@kuzbass.ru) Message-ID: <40514FB2.EEA7E0F0@kuzbass.ru> Date: Fri, 12 Mar 2004 12:50:42 +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: SOLVED: 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: Fri, 12 Mar 2004 05:51:34 -0000 Don Lewis wrote: > > 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). > 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? That was AtGuard 3.22. It does strange things under Windows 2000SP4 while works OK under Win9x. Thanks! Eugene Grosbein From owner-freebsd-net@FreeBSD.ORG Fri Mar 12 16:08: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 A031016A4CE for ; Fri, 12 Mar 2004 16:08:13 -0800 (PST) Received: from sage.ts.co.nz (sage.tasman.net [202.49.92.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15CF343D41 for ; Fri, 12 Mar 2004 16:08:13 -0800 (PST) (envelope-from Neil@ts.co.nz) Received: from sage.ts.co.nz ([172.16.21.1]) by sage.ts.co.nz (8.12.3/8.12.10) with ESMTP id i2D056rb014039 for ; Sat, 13 Mar 2004 13:05:06 +1300 Received: from 6-allhosts (gateway-nelson.thepacific.net [202.49.95.33]) by sage.ts.co.nz (8.12.3/8.12.10) with ESMTP id i2D03wWZ013783 for ; Sat, 13 Mar 2004 13:03:59 +1300 From: Neil Fenemor To: freebsd-net@freebsd.org Content-Type: text/plain Message-Id: <1079136183.29695.7.camel@acer> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Sat, 13 Mar 2004 13:03:03 +1300 Content-Transfer-Encoding: 7bit Subject: IPSEC/NAT/Gateway Query 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, 13 Mar 2004 00:08:13 -0000 Hi all, I currently have an issue of how "open" the whole WiFi tends to be, so, as all good people should do, I've started implementing a IPSec encryption system rather than the rather disappointing WEP. I'm encrypting all data to and from the gateway, which isn't a problem. This was documented rather well all over the internet. What I'm having an issue, is if the "client" has a range of RFC 1918 addresses behind it, and I have to introduce NAT into the equation. I've best tracked it down to the order that the kernel looks at the packets to decide what to do with it. This is where I stand at the moment. x.y.z.11 -> x.y.z.254 : works perfectly x.y.z.11 -> x.y.z.254 -> 0.0.0.0 : works perfectly rfc 1918 -> x.y.z.11 -> x.y.z.254 : Fails rfc 1918 -> x.y.z.11 -> x.y.z.254 -> 0.0.0.0 : Fails The connection between x.y.z.11 and x.y.z.254 is there the IPSec takes place, and is the only part "off the wire" as it were. The issue presents itself as the packet, from an rfc 1918 address, goes to the client box, gets inspected by the VPN rules, which are currently set to match on the external address of the client machine, and is subsequently overlooked by the VPN. The packet then goes on, gets NATed, and goes out as a unencrypted packet, from x.y.z.11. Thats a generally undesired transport mode. On x.y.z.254, the packet goes back via the IPSec tunnel, but is then not un-NATed. All I believe should be required, is for the RFC 1918 packet to be NATed to the external IP address, BEFORE it is inspected by the IPSec system. So basically, all I'm really asking, is am I on the right line of thinking, or have I just gone off on a complete tangent to where I should be headed. Any ideas/input would be greatly appreciated. Regards Neil Fenemor Senior Systems Administrator ThePacific.net Ltd. From owner-freebsd-net@FreeBSD.ORG Sat Mar 13 01:20: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 4F94116A4CE for ; Sat, 13 Mar 2004 01:20:17 -0800 (PST) Received: from istanbul.enderunix.org (freefall.marmara.edu.tr [193.140.143.23]) by mx1.FreeBSD.org (Postfix) with SMTP id 366FC43D3F for ; Sat, 13 Mar 2004 01:20:14 -0800 (PST) (envelope-from ofsen@enderunix.org) Received: (qmail 79498 invoked by uid 89); 14 Mar 2004 09:18:14 -0000 Message-ID: <20040314091814.79495.qmail@istanbul.enderunix.org> From: Omer Faruk Sen To: freebsd-net@freebsd.org Date: Sun, 14 Mar 2004 11:18:14 +0200 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="ISO-8859-9" Content-Transfer-Encoding: 7bit Subject: mpd lcp 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: Sat, 13 Mar 2004 09:20:17 -0000 Hi, I have set up an mpd server. But there is a problem. When I try to connect with my home pc logs are generated like this: ------------------------------------------------------ [pptp] LCP: state change Req-Sent --> Ack-Sent [pptp] LCP: SendConfigReq #2 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM d3dbc780 AUTHPROTO CHAP MSOFTv2 MP MRRU 1600 MP SHORTSEQ ENDPOINTDISC [802.1] 00 90 27 d6 1c 0b [pptp] LCP: rec'd Configure Reject #2 link 0 (Ack-Sent) MP MRRU 1600 MP SHORTSEQ ENDPOINTDISC [802.1] 00 90 27 d6 1c 0b [pptp] LCP: SendConfigReq #3 ACFCOMP PROTOCOMP MRU 1500 MAGICNUM d3dbc780 AUTHPROTO CHAP MSOFTv2 [pptp] LCP: rec'd Configure Ack #3 link 0 (Ack-Sent) ACFCOMP PROTOCOMP MRU 1500 MAGICNUM d3dbc780 AUTHPROTO CHAP MSOFTv2 [pptp] LCP: state change Ack-Sent --> Opened ------------------------------------------------- As you see from above and below (which is a partial copy of above) [pptp] LCP: rec'd Configure Reject #2 link 0 (Ack-Sent) MP MRRU 1600 MP SHORTSEQ ENDPOINTDISC [802.1] 00 90 27 d6 1c 0b As far as I understand "mp mrru 1600", "mp shortseq" and "endpoint ..." capabilities are rejected by mpd server. My windowsXP client sends connection request with removing those capabilities and vpn connection is established perfectly.. But some XP and most Windows2k clients insists on those capabilities rejected by mpd server thus connection is no established with an LCP error. Is there a workaround or a way to enable "mp mrru 1600", "mp shortseq" and "endpoint ..." properties on mpd server? My configuration is like this: -----mpd.conf----------- default: load pptp pptp: new -i ng0 pptp pptp set iface disable on-demand set iface enable proxy-arp set iface idle 1800 set iface enable tcpmssfix # set bundle enable multilink # enable TCP-Wrapper (hosts_access(5)) to block unfriendly clients # set bundle enable tcp-wrapper # use RADIUS servers # load radius set link yes acfcomp protocomp #set iface route default set iface route 10.0.0.0/22 set link no pap chap set link enable chap set link keep-alive 10 60 set link mtu 1460 set link mtu 1500 set ipcp yes vjcomp set ipcp ranges 10.0.0.26/32 10.0.0.54/32 #set ipcp dns 192.168.1.3 # The five lines below enable Microsoft Point-to-Point encryption # (MPPE) using the ng_mppc(8) netgraph node type. # set bundle enable compression set ccp yes mppc set ccp yes mpp-e40 set ccp yes mpp-e128 set ccp yes mpp-stateless -----------mpd.conf------------ -----mpd.links------- pptp: set link type pptp set pptp self SERVER_IP set pptp enable incoming set pptp disable originate -------mpd.links--------- ----------------------- Omer Faruk Sen http://www.EnderUNIX.ORG Software Development Team @ Turkey http://www.Faruk.NET For Public key: http://www.enderunix.org/ofsen/ofsen.asc ******************************************************** From owner-freebsd-net@FreeBSD.ORG Sat Mar 13 05:50: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 4886416A4CE for ; Sat, 13 Mar 2004 05:50:53 -0800 (PST) Received: from web41510.mail.yahoo.com (web41510.mail.yahoo.com [66.218.93.93]) by mx1.FreeBSD.org (Postfix) with SMTP id 3D25943D3F for ; Sat, 13 Mar 2004 05:50:53 -0800 (PST) (envelope-from sv_p3@yahoo.com) Message-ID: <20040313135053.49230.qmail@web41510.mail.yahoo.com> Received: from [202.131.103.100] by web41510.mail.yahoo.com via HTTP; Sat, 13 Mar 2004 05:50:53 PST Date: Sat, 13 Mar 2004 05:50:53 -0800 (PST) From: sumit panchasara To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: ipip tunnel!!! Please Help! X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Mar 2004 13:50:53 -0000 Hi! I am Sumit Panchasara. I am developing IP-IP-UDP -IP Encapsulation kernel module fro DVB-RCS system. I want to test it other than Ping Application, I mean with some UDP kind of application that passes the packet to destination via specified tunnel by me. I want that code if available or if any have idea about this thing please tell me something aboute this. This is my BE level final semester Project. And this will be my Last stage of Project. Thanks, Regards Sumit __________________________________ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com From owner-freebsd-net@FreeBSD.ORG Sat Mar 13 13:47: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 58C4516A4CE for ; Sat, 13 Mar 2004 13:47:20 -0800 (PST) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A4FD43D1F for ; Sat, 13 Mar 2004 13:47:20 -0800 (PST) (envelope-from justin@mac.com) Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id i2DL66Yx019413 for ; Sat, 13 Mar 2004 13:06:06 -0800 (PST) Received: from mac.com (c-24-6-87-110.client.comcast.net [24.6.87.110]) (authenticated bits=0) by mac.com (Xserve/smtpin07/MantshX 3.0) with ESMTP id i2DL657k016589 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 13 Mar 2004 13:06:06 -0800 (PST) Date: Sat, 13 Mar 2004 13:06:04 -0800 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v553) From: Justin Walker To: freebsd-net@freebsd.org Content-Transfer-Encoding: 7bit In-Reply-To: Message-Id: <3D08F840-7532-11D8-8D02-00306544D642@mac.com> X-Mailer: Apple Mail (2.553) Subject: Re: One IP used on more than one interface (gif0 and lo0) 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, 13 Mar 2004 21:47:20 -0000 On Tuesday, March 9, 2004, at 10:10 AM, Julian Elischer wrote: > > > On Tue, 9 Mar 2004, Justin Walker wrote: > >> >> On Tuesday, March 9, 2004, at 01:55 AM, Frrodo Baggins wrote: >> >>> Hi, >>> >>> What happens if we configure an alias on lo0: >>> >>> ifconfig lo0 alias 192.168.5.1 netmask 255.255.255.0 >>> >>> and then use the same IP on gif0: >> >> What happens if you have the same address on two different houses on >> the same street? > > > that isn't the question.. > it's > "why have different numbers on houses on differnt streets?" > > It is in fact common practice to number all your P2P links using teh > address of one of your broadcast interfaces.. > > this works well, saves you an address and you have a simpler routing > table. > > Point to point links route using the REMOTE address and don't care > about > teh local address so this always works. Thanks for pointing this out; I got caught in the "all the world's an ethernet" trap, and overdid it. Cheers, Justin -- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | It's not whether you win or lose... | It's whether *I* win or lose. *--------------------------------------*-------------------------------*