From owner-freebsd-net@FreeBSD.ORG Sun Jun 16 00:46:56 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 7468D99C for ; Sun, 16 Jun 2013 00:46:56 +0000 (UTC) (envelope-from fernando@gont.com.ar) Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by mx1.freebsd.org (Postfix) with ESMTP id 3FA101FB3 for ; Sun, 16 Jun 2013 00:46:56 +0000 (UTC) Received: from [186.134.15.116] (helo=[192.168.0.6]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from ) id 1Uo17I-0006cN-2I; Sun, 16 Jun 2013 02:46:49 +0200 Message-ID: <51BD0458.3030003@gont.com.ar> Date: Sun, 16 Jun 2013 02:18:32 +0200 From: Fernando Gont User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 MIME-Version: 1.0 To: "Bruce A. Mah" Subject: Re: Show multicast groups joined? References: <51BCF068.9000207@gont.com.ar> <51BCFE13.7010703@kitchenlab.org> In-Reply-To: <51BCFE13.7010703@kitchenlab.org> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jun 2013 00:46:56 -0000 On 06/16/2013 01:51 AM, Bruce A. Mah wrote: > If memory serves me right, Fernando Gont wrote: > >> What would be the appropriate command to show the IPv6 multicast >> groups joined by all/each interface? > > Try ifmcstat(8). That's exactly what I wanted. Thanks so much! -- Fernando Gont e-mail: fernando@gont.com.ar || fgont@si6networks.com PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1 From owner-freebsd-net@FreeBSD.ORG Sun Jun 16 06:59:55 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 7C025410 for ; Sun, 16 Jun 2013 06:59:55 +0000 (UTC) (envelope-from s.khanchi@gmail.com) Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) by mx1.freebsd.org (Postfix) with ESMTP id 17D031CA0 for ; Sun, 16 Jun 2013 06:59:54 +0000 (UTC) Received: by mail-wg0-f43.google.com with SMTP id z11so1549693wgg.22 for ; Sat, 15 Jun 2013 23:59:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; bh=F9krEPVesZmw1M7H7KYO0zvBN09cFKjDL4GLswPkEmg=; b=0m9chnXoJPhARBFBLCVOGSvYyl3/aIQF2wS9RlTyj0qTTU730j25YA7kVEbqwOZtx1 r7xbkgJPAAJLXMDWCQaHd+Gn4r7UDmiT6KRMOSdAGcMU8ZLfRmM1jxUVPITx9tTxwQnT l+BrmdANkxD9W/QSHCkSFKohYF8gtWTPwn3oXZRLiC4KZIUjN+Sj1tUWjEhIzD4BhwLO 12xSEZAMWYACA1c2GiBI/pUSnbHgDwhyYxtK5IXyOLjiHA5DPYUjfSTp0zvdui865D4B Sb9HtCScT5XhPoTHdSeiMS5kgxQPE4GbLrgjGEnJqyiG8nBDWu3OG2x0ZBNcrauGc9NL TqFg== X-Received: by 10.180.105.231 with SMTP id gp7mr2250184wib.23.1371365994297; Sat, 15 Jun 2013 23:59:54 -0700 (PDT) MIME-Version: 1.0 Sender: s.khanchi@gmail.com Received: by 10.194.22.195 with HTTP; Sat, 15 Jun 2013 23:59:34 -0700 (PDT) From: h bagade Date: Sun, 16 Jun 2013 11:29:34 +0430 X-Google-Sender-Auth: MclvhTDTSend2M0AGt69QfgzOhE Message-ID: Subject: How not allow setting ip changes interface down status? To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jun 2013 06:59:55 -0000 Hi all, I want to know if there is any way to change the current freebsd behavior when setting interface ip address. In current method, when assigning ip address to an interface, the interface is set to UP. I need not allowing this change to be done! If an interface is in down state, setting ip address doesn't change its sate. I'm ready to hear your ideas on my question and what's the pros and cons of the change I'm going to make. From owner-freebsd-net@FreeBSD.ORG Sun Jun 16 07:48:51 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8D158D61 for ; Sun, 16 Jun 2013 07:48:51 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-f42.google.com (mail-qe0-f42.google.com [209.85.128.42]) by mx1.freebsd.org (Postfix) with ESMTP id 53B9A1DDC for ; Sun, 16 Jun 2013 07:48:51 +0000 (UTC) Received: by mail-qe0-f42.google.com with SMTP id s14so1139438qeb.1 for ; Sun, 16 Jun 2013 00:48:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=hxWvEjTyidhyChtkmJ9BhmpIgT1JXeoE1Or3H9wH7BQ=; b=kl0PfAl8U9gShM3RGHGXli/JS9+cNJk7eea4N8Y/kVV+0l/T8ovC4joJ/KA11haeAo oU+B8g3BuelDGdXUxVGwFzQndlv/G1+uC80wzS3ScvO0MZ5YinoJ4twujiswyzVAoj62 W08xTiG9hhJWNODMjaQWIleNO15s3WB/XJcI7vQlTfGkl09VSDU6ifFVFIRY2z4Zow5V A/4356hYQoJ+uNjy+n/SL4rwIlikJiubuWiIhgEr76pOnL7SfNkNtxnk56aYDk+Qqyic vGLb5UxJNMNh5JDk18/MlnBmp7TIi2Svmt0HYIF+VL4HD7X/LjG+F2vhhbHVYV7cRzNC Po4A== MIME-Version: 1.0 X-Received: by 10.229.106.18 with SMTP id v18mr4093472qco.49.1371368924773; Sun, 16 Jun 2013 00:48:44 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.5.65 with HTTP; Sun, 16 Jun 2013 00:48:44 -0700 (PDT) In-Reply-To: References: Date: Sun, 16 Jun 2013 00:48:44 -0700 X-Google-Sender-Auth: T-Mf8fD0bYRIdYKvaWf5FpQP428 Message-ID: Subject: Re: How not allow setting ip changes interface down status? From: Adrian Chadd To: h bagade Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jun 2013 07:48:51 -0000 That'd actually be nice to have. I've noticed this with wifi and it's irritating. adrian On 15 June 2013 23:59, h bagade wrote: > Hi all, > > I want to know if there is any way to change the current freebsd behavior > when setting interface ip address. In current method, when assigning ip > address to an interface, the interface is set to UP. I need not allowing > this change to be done! If an interface is in down state, setting ip > address doesn't change its sate. > > I'm ready to hear your ideas on my question and what's the pros and cons of > the change I'm going to make. > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Sun Jun 16 09:28:19 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 023BD139 for ; Sun, 16 Jun 2013 09:28:19 +0000 (UTC) (envelope-from jhellenthal@dataix.net) Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) by mx1.freebsd.org (Postfix) with ESMTP id BE083111B for ; Sun, 16 Jun 2013 09:28:18 +0000 (UTC) Received: by mail-ie0-f169.google.com with SMTP id 10so4670930ied.14 for ; Sun, 16 Jun 2013 02:28:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dataix.net; s=rsa; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=WMo6c2HJ4n5/Fpu5B3yKtwEF6Llgf99r8sY+mM0Jd9I=; b=UqhpdIdCFB8qXSzn/1QmX5uFfEUBmRHNcwR/TAg/DSNRnxTrZZqBhbB4jFQ+WM8PkB rbsXDl0W/eXCdqMI1kt2wcypBNSF+p3cbiSxU+csoA3Ui+dtQ1KeySV7wxjPwZ0JBRye LyJEyNNotp/zcaDn8CYDUeHvfIwaoXggb2R0o= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=WMo6c2HJ4n5/Fpu5B3yKtwEF6Llgf99r8sY+mM0Jd9I=; b=O//0IsrkOOGPE3hQ6c9SsjkBmvH+sg/ErZfhksduMaJjWuuQSPbyDA7uOJs3gs2V39 Prb6Qpteqo4aOvGKrkEPHLeHbXIBK+mEBQgb1+Sv34QqHBMsuuoel5xE8BVQu4ntTYm0 bMDwIAriOdJhqfCy7siQUiZJND7ZoABsFR1GBC6z77XzjWaQKhZ3FHHvrxXxjXrg57aA XU7f+stR/sp6MCxwQBT/e2u3dehKYl374QrARhwyAAbiybpaXi7sqaIsR31kMt6VybBo NXIsh0VaLK2KN1fJjkbWzFQYHw8joa5pVpMjuq9r/zy1XlllbvSz3orEs8SHGmL1+Dza 86ew== X-Received: by 10.50.83.35 with SMTP id n3mr2547697igy.83.1371374898149; Sun, 16 Jun 2013 02:28:18 -0700 (PDT) Received: from [192.168.31.77] (24-236-152-143.dhcp.aldl.mi.charter.com. [24.236.152.143]) by mx.google.com with ESMTPSA id k10sm11477815ige.0.2013.06.16.02.28.15 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 16 Jun 2013 02:28:16 -0700 (PDT) References: Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-948942E8-DE54-4DCC-9C20-95F98684A754; protocol="application/pkcs7-signature" Content-Transfer-Encoding: 7bit Message-Id: <69CF1AAF-230D-4B2B-9C95-20DDD772997E@dataix.net> X-Mailer: iPhone Mail (10B329) From: Jason Hellenthal Subject: Re: How not allow setting ip changes interface down status? Date: Sun, 16 Jun 2013 05:28:15 -0400 To: Adrian Chadd X-Gm-Message-State: ALoCoQkSHtN4dI34dutVsvaMjy/mcSp3MQNk5CDMDaqb+BM54co4OAibAXHFM6EbHgDqe6cqLbNj X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: h bagade , "freebsd-net@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jun 2013 09:28:19 -0000 --Apple-Mail-948942E8-DE54-4DCC-9C20-95F98684A754 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Seconded. But to answer you must specify "down" with every command. ifconfig wlan0 inet ipa.ddr.her.e/24 down It's a PITA --=20 Jason Hellenthal Inbox: jhellenthal@DataIX.net Voice: +1 (616) 953-0176 JJH48-ARIN On Jun 16, 2013, at 3:48, Adrian Chadd wrote: > That'd actually be nice to have. I've noticed this with wifi and it's > irritating. >=20 >=20 > adrian >=20 > On 15 June 2013 23:59, h bagade wrote: >> Hi all, >>=20 >> I want to know if there is any way to change the current freebsd behavior= >> when setting interface ip address. In current method, when assigning ip >> address to an interface, the interface is set to UP. I need not allowing >> this change to be done! If an interface is in down state, setting ip >> address doesn't change its sate. >>=20 >> I'm ready to hear your ideas on my question and what's the pros and cons o= f >> the change I'm going to make. >> _______________________________________________ >> 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" > _______________________________________________ > 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" --Apple-Mail-948942E8-DE54-4DCC-9C20-95F98684A754 Content-Type: application/pkcs7-signature; name=smime.p7s Content-Disposition: attachment; filename=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGNDCCBjAw ggUYoAMCAQICAwaijjANBgkqhkiG9w0BAQsFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0 YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcx ODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENB MB4XDTEzMDUxODA4NTA0OFoXDTE0MDUxOTIyMDk0N1owSDEfMB0GA1UEAwwWamhlbGxlbnRoYWxA ZGF0YWl4Lm5ldDElMCMGCSqGSIb3DQEJARYWamhlbGxlbnRoYWxAZGF0YWl4Lm5ldDCCASIwDQYJ KoZIhvcNAQEBBQADggEPADCCAQoCggEBALgnYFS1bWZr3KhKBzWAdRwrY+En+RRV8nCaYubqrMG+ YJbuenaIKSbIuFiDWipW4RHYTpE28pKaSnaVTG9WtAZvsWj0gYN9g2fYCnCOUceES2Yvi3RavxpB hsuzKIfsHb8iNNSEuczLu6gn4mQyaHwE4x6xSUKmbK8njR+YoF522F60wjsnq5dlOJdTrhDfObE5 5P23279WbRp8azgZX1VRB66wdKRDuSI1vBts4Nsha2paXd6HUUduHrPACBQREJTGXN8XtEKVwo63 aKUhRgtUwHNEuSWck/xwVl7PBUWH2dORAWTCqHjNuCKNOQ1/0LMiyMj7FdsBjN4dgL4YZpsCAwEA AaOCAtwwggLYMAkGA1UdEwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggr BgEFBQcDBDAdBgNVHQ4EFgQU29qUrmZtgQ7ZVoDKogfpJOSfk+YwHwYDVR0jBBgwFoAUU3Ltkpzg 2ssBXHx+ljVO8tS4UYIwIQYDVR0RBBowGIEWamhlbGxlbnRoYWxAZGF0YWl4Lm5ldDCCAUwGA1Ud IASCAUMwggE/MIIBOwYLKwYBBAGBtTcBAgMwggEqMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0 YXJ0c3NsLmNvbS9wb2xpY3kucGRmMIH3BggrBgEFBQcCAjCB6jAnFiBTdGFydENvbSBDZXJ0aWZp Y2F0aW9uIEF1dGhvcml0eTADAgEBGoG+VGhpcyBjZXJ0aWZpY2F0ZSB3YXMgaXNzdWVkIGFjY29y ZGluZyB0byB0aGUgQ2xhc3MgMSBWYWxpZGF0aW9uIHJlcXVpcmVtZW50cyBvZiB0aGUgU3RhcnRD b20gQ0EgcG9saWN5LCByZWxpYW5jZSBvbmx5IGZvciB0aGUgaW50ZW5kZWQgcHVycG9zZSBpbiBj b21wbGlhbmNlIG9mIHRoZSByZWx5aW5nIHBhcnR5IG9ibGlnYXRpb25zLjA2BgNVHR8ELzAtMCug KaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1MS1jcmwuY3JsMIGOBggrBgEFBQcBAQSB gTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2NzcC5zdGFydHNzbC5jb20vc3ViL2NsYXNzMS9jbGll bnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFz czEuY2xpZW50LmNhLmNydDAjBgNVHRIEHDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJ KoZIhvcNAQELBQADggEBAHsw8/Hw07gsNTKYnld74NBFtHnQOPkXYuccWx3j0PGQe9nqNxeingBf 2yvx+xBQzBoi4J1u84Jbrbe8Ii3+LLD/QMW9cN0SBIgRStPQLVee4STdjeabGmpXQa7omC02wYYO 83qh6CgJEIbmrsBSZH8ZSVrjkC4UmZS8wAQMS3qTWAPF0ZQGWx2+Gks2fXuacyt2LpNR+p9ogjAZ 1/rmUKjNhQZLswytaLRUdwAwSfQ3+TNs68h6Kv1LC3bNGBT3NEtr2q/nzzb5MzuFcDE6f9exroAC 4BHmokAprhna/vZdb6BrPjpXgRAlWAh3wEMxw75M9S/Nbzj/jNp+I+lvUJYxggNvMIIDawIBATCB lDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3Vy ZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEg UHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMGoo4wCQYFKw4DAhoFAKCCAa8wGAYJKoZI hvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwNjE2MDkyODE3WjAjBgkqhkiG 9w0BCQQxFgQU0nqOM3R8SOGRks/7Lg3oqlTYzUwwgaUGCSsGAQQBgjcQBDGBlzCBlDCBjDELMAkG A1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs IENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJ bnRlcm1lZGlhdGUgQ2xpZW50IENBAgMGoo4wgacGCyqGSIb3DQEJEAILMYGXoIGUMIGMMQswCQYD VQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwg Q2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IElu dGVybWVkaWF0ZSBDbGllbnQgQ0ECAwaijjANBgkqhkiG9w0BAQEFAASCAQCmL3iVfsmx0GjEE/wB gRE4vC7vFeo6bVAiP4Teb1S7CQX2eUKW8iDSvhu/WKArEbRF/uDjauREYAeFbkDw5YifTL8IgSbp nF70NHN29dVHkOt6C5LEg0DsoVLwwR6PfnZ++tVCkjAvhjV6a7lZ5j4c7uqQMvUDD5+swA+yh/1t FCywJ0sfxZgEfhIOZ/F/S3ASZOuxJaM3WGvFeQjl9Ykd3Vdn8Wa9l2ykpGQpOuqBzMw0fMeAO19U HteVy34OZv3+WZCN21KYjp6dho8oxN+Q8detQYf4mXku/aUEzC1FfI2Ha4veIQZBlqDaPpIat40x 1oLtspy/+GpogVnscNX8AAAAAAAA --Apple-Mail-948942E8-DE54-4DCC-9C20-95F98684A754-- From owner-freebsd-net@FreeBSD.ORG Sun Jun 16 10:22:49 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 56CF2CE2 for ; Sun, 16 Jun 2013 10:22:49 +0000 (UTC) (envelope-from bthcom@higonnet.net) Received: from smtp2-g21.free.fr (smtp2-g21.free.fr [IPv6:2a01:e0c:1:1599::11]) by mx1.freebsd.org (Postfix) with ESMTP id 09F0712AA for ; Sun, 16 Jun 2013 10:22:41 +0000 (UTC) Received: from freebsd.higonnet.net (unknown [82.238.41.134]) by smtp2-g21.free.fr (Postfix) with ESMTP id 676E84B018B for ; Sun, 16 Jun 2013 12:22:34 +0200 (CEST) Received: from [127.0.0.1] (unknown [192.168.4.77]) by freebsd.higonnet.net (Postfix) with ESMTP id 30D5828419 for ; Sun, 16 Jun 2013 12:27:50 +0200 (CEST) Message-ID: <51BD91E8.8060501@higonnet.net> Date: Sun, 16 Jun 2013 12:22:32 +0200 From: Bernard Higonnet User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: How to find out a VPN link has gone down (or better, come back up)? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 130615-1, 15/06/2013), Outbound message X-Antivirus-Status: Clean X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jun 2013 10:22:49 -0000 I have a machine, FreeBSD 8.1-RELEASE #0, running a VPN (MPD5) server. Every once in a while, the link goes down, presumably because of some third-party event on the network. When this happens, an element placed in the routing table by hand disappears since the node on the VPN server to the far-off client machine no longer exists (even though the entry in the routing table is marked "permanent" when it does exist). When the network problem goes away, the VPN link is automatically restored, but not the routing table. Can someone tell me if there is a way to be notified that the link has been restored so that I can run a script etc. to restore the routing table to what I want? TIA Bernard Higonnet From owner-freebsd-net@FreeBSD.ORG Sun Jun 16 12:52:18 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 24AFBEFD for ; Sun, 16 Jun 2013 12:52:18 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-wg0-x235.google.com (mail-wg0-x235.google.com [IPv6:2a00:1450:400c:c00::235]) by mx1.freebsd.org (Postfix) with ESMTP id B0033182A for ; Sun, 16 Jun 2013 12:52:17 +0000 (UTC) Received: by mail-wg0-f53.google.com with SMTP id y10so1663142wgg.20 for ; Sun, 16 Jun 2013 05:52:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=/OGXZ6/4ryQv/iA5eywxwL+ZMe04yxqS4mmYRNIaOSo=; b=FaAehpsV8EMQocv8Bap4iH8QG5txLSsju26ki5w+y4TNfk+Htz5WCuh0KJGuw7zXG8 r7mmC7BunRVEcZ+0jLMRLTVPVPkcv5pDAPCwaE1lllanKpB/NLLkDst8ucrONhNb1Ag9 Y2EFbavTP5dxbBiZgKi8PDDyQ5qJ//OvBh38i2myA7tdcerI1HLgXAQCvYNrWN8qJg4/ j8qWjIVq8ftbewMFBnTBuvht8QJ8YuB4PU9ajiJiMazWk/PJUcUxSib/WohLSaK3hse4 s0j8fTGLj30K+9OsPSNmtPWW83eHdtHwrOkW9x83Sdmwxq+fM1GMX0BLkk+hqIDFYeQ2 kC8Q== X-Received: by 10.180.107.163 with SMTP id hd3mr1741099wib.13.1371387136883; Sun, 16 Jun 2013 05:52:16 -0700 (PDT) Received: from [10.41.54.130] (94.16.90.92.rev.sfr.net. [92.90.16.94]) by mx.google.com with ESMTPSA id x13sm15316362wib.3.2013.06.16.05.52.14 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 16 Jun 2013 05:52:15 -0700 (PDT) References: <51BD91E8.8060501@higonnet.net> Mime-Version: 1.0 (1.0) In-Reply-To: <51BD91E8.8060501@higonnet.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <5DD08E44-E481-4FF9-A5A8-AFE3E341A57C@my.gd> X-Mailer: iPhone Mail (10B144) From: Damien Fleuriot Subject: Re: How to find out a VPN link has gone down (or better, come back up)? Date: Sun, 16 Jun 2013 14:51:06 +0200 To: Bernard Higonnet X-Gm-Message-State: ALoCoQnH8qKTEpVhmK6VKWn5wB5bejbHXHQeFKasWHAThN6h0lrEw+krvYgXIYPXjL+SzAJqtdB0 Cc: "freebsd-net@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jun 2013 12:52:18 -0000 I might be wrong but wouldn't that be a job for devd ? Alternatively set a cron job every minute to reinstall the route. On 16 Jun 2013, at 12:22, Bernard Higonnet wrote: > I have a machine, FreeBSD 8.1-RELEASE #0, running a VPN (MPD5) server. >=20 > Every once in a while, the link goes down, presumably because of some thir= d-party event on the network. >=20 > When this happens, an element placed in the routing table by hand disappea= rs since the node on the VPN server to the far-off client machine no longer e= xists (even though the entry in the routing table is marked "permanent" when= it does exist). When the network problem goes away, the VPN link is automat= ically restored, but not the routing table. >=20 > Can someone tell me if there is a way to be notified that the link has bee= n restored so that I can run a script etc. to restore the routing table to w= hat I want? >=20 > TIA > Bernard Higonnet > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Sun Jun 16 14:40:25 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E18622D2 for ; Sun, 16 Jun 2013 14:40:25 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id B74A81AF8 for ; Sun, 16 Jun 2013 14:40:25 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-237-17.lns20.per1.internode.on.net [121.45.237.17]) (authenticated bits=0) by vps1.elischer.org (8.14.5/8.14.5) with ESMTP id r5GEeD3s005890 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 16 Jun 2013 07:40:17 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <51BDCE49.1000207@freebsd.org> Date: Sun, 16 Jun 2013 22:40:09 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Damien Fleuriot Subject: Re: How to find out a VPN link has gone down (or better, come back up)? References: <51BD91E8.8060501@higonnet.net> <5DD08E44-E481-4FF9-A5A8-AFE3E341A57C@my.gd> In-Reply-To: <5DD08E44-E481-4FF9-A5A8-AFE3E341A57C@my.gd> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-net@freebsd.org" , Bernard Higonnet X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jun 2013 14:40:25 -0000 On 6/16/13 8:51 PM, Damien Fleuriot wrote: > I might be wrong but wouldn't that be a job for devd ? > > Alternatively set a cron job every minute to reinstall the route. use the up/down scripts to install the routes... that's what they are for. > > > On 16 Jun 2013, at 12:22, Bernard Higonnet wrote: > >> I have a machine, FreeBSD 8.1-RELEASE #0, running a VPN (MPD5) server. >> >> Every once in a while, the link goes down, presumably because of some third-party event on the network. >> >> When this happens, an element placed in the routing table by hand disappears since the node on the VPN server to the far-off client machine no longer exists (even though the entry in the routing table is marked "permanent" when it does exist). When the network problem goes away, the VPN link is automatically restored, but not the routing table. >> >> Can someone tell me if there is a way to be notified that the link has been restored so that I can run a script etc. to restore the routing table to what I want? >> >> TIA >> Bernard Higonnet >> _______________________________________________ >> 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" > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > From owner-freebsd-net@FreeBSD.ORG Sun Jun 16 16:50:19 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 16420731; Sun, 16 Jun 2013 16:50:19 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-ve0-x233.google.com (mail-ve0-x233.google.com [IPv6:2607:f8b0:400c:c01::233]) by mx1.freebsd.org (Postfix) with ESMTP id B8B2F1EED; Sun, 16 Jun 2013 16:50:18 +0000 (UTC) Received: by mail-ve0-f179.google.com with SMTP id d10so1547980vea.38 for ; Sun, 16 Jun 2013 09:50:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=UoxZEecdmPvhuEo6Zc+nm4ZPQFzUPx9xTMKCViUcFbs=; b=kGd5v5fmvmhIR1yYv94xCoLLWyc3IBWU/6ddZwa9sEdxjPog0yWrTm6MQ3YVUlCXZP 3P0F3AQIl21ECPu/+KG9V+ende1Ka8nInOF/BX3ZMDfk/w8Epkja/iS/h1BksAIEb6lH 3XzwGt0cH4jpCZAwQDdzn5rpkqVxpPv+r4O+cN4Og7cZt++Giw2UAQT3cPcqs2WGpTCo wy7J2FJlo9eEDH/dzzL7/vjZtwR4q6VhrQSHY7pcvHCL2K7Uhn3TQfXffQrwZGcXJ2eA i5v8bCDrtH/gKSsDmn1FhOLRb1QczlT8T1R3Fxvl+r3kWy3nAdzci7C2moiW0Nijx2bc n1uw== MIME-Version: 1.0 X-Received: by 10.58.204.195 with SMTP id la3mr2401411vec.66.1371401418233; Sun, 16 Jun 2013 09:50:18 -0700 (PDT) Received: by 10.220.52.200 with HTTP; Sun, 16 Jun 2013 09:50:18 -0700 (PDT) In-Reply-To: <69CF1AAF-230D-4B2B-9C95-20DDD772997E@dataix.net> References: <69CF1AAF-230D-4B2B-9C95-20DDD772997E@dataix.net> Date: Sun, 16 Jun 2013 09:50:18 -0700 Message-ID: Subject: Re: How not allow setting ip changes interface down status? From: Jack Vogel To: Jason Hellenthal Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: h bagade , "freebsd-net@freebsd.org" , Adrian Chadd X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jun 2013 16:50:19 -0000 How is adding a small token 'down' with the command a 'PITA', seems completely reasonable to me? Further, if you changed it so if didn't bring the interface up you'd probably have a bunch of people complain because that was the expected behavior :) Jack On Sun, Jun 16, 2013 at 2:28 AM, Jason Hellenthal wrote: > Seconded. > > But to answer you must specify "down" with every command. > > ifconfig wlan0 inet ipa.ddr.her.e/24 down > > It's a PITA > > -- > Jason Hellenthal > Inbox: jhellenthal@DataIX.net > Voice: +1 (616) 953-0176 > JJH48-ARIN > > > On Jun 16, 2013, at 3:48, Adrian Chadd wrote: > > > That'd actually be nice to have. I've noticed this with wifi and it's > > irritating. > > > > > > adrian > > > > On 15 June 2013 23:59, h bagade wrote: > >> Hi all, > >> > >> I want to know if there is any way to change the current freebsd > behavior > >> when setting interface ip address. In current method, when assigning ip > >> address to an interface, the interface is set to UP. I need not allowing > >> this change to be done! If an interface is in down state, setting ip > >> address doesn't change its sate. > >> > >> I'm ready to hear your ideas on my question and what's the pros and > cons of > >> the change I'm going to make. > >> _______________________________________________ > >> 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" > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Sun Jun 16 17:13:28 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8317919B for ; Sun, 16 Jun 2013 17:13:28 +0000 (UTC) (envelope-from jhellenthal@dataix.net) Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) by mx1.freebsd.org (Postfix) with ESMTP id 45E341058 for ; Sun, 16 Jun 2013 17:13:28 +0000 (UTC) Received: by mail-ie0-f173.google.com with SMTP id k13so5123986iea.32 for ; Sun, 16 Jun 2013 10:13:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dataix.net; s=rsa; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=HctPosgkQPqBIZjth7khnJtPAo7hDrpe/YknrcjU6bY=; b=e4oSI/4ocp+NH5ocBzT+HQFFJlkA3JX7OAZDTreQS3IhCo+JeO7ngZ+wud5mWtehIL vizkmzrQkKNwxOrMpVX3Dzwr0tckxEml2q1vJjH/8IpyaRc3rqMChS+w4e+lEkxoBa2c 24ICDnZtt6+hw8M+PQ2DNCQPfsnudkKw8uIfg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=HctPosgkQPqBIZjth7khnJtPAo7hDrpe/YknrcjU6bY=; b=M632yvn6xv2M2Ae+fc7rdCUMxCkAn3+Hm3aa9BkOB6QOYw4+CO/xVRRlaHUaDZRFHe aZbEODA05Bfv+Gxj9LNhwwoXMTTjflRZwNylkeAJmpVbM5tUc6lqx5Cmg09XTKJ+oFcl kHtQL5LuFHM6xi/D7E59bGWkU9xlJUiQ9qHjogGC5szYrzOZQ505B544rO36NbSVPekk MJur6QuTpM15mdqYf/1FbyibZzk/jiMw73X9i8+u7HrAfNNnwdCNWE18yFReWAYY7uG+ P7wz7EeJ9hKaq2EtaRYPCQ+xMTo6JZxvXcN2HMK6vDHc3YvCcatkv3Cn1IOviQSCYUII yPrg== X-Received: by 10.50.16.36 with SMTP id c4mr3200576igd.60.1371402808028; Sun, 16 Jun 2013 10:13:28 -0700 (PDT) Received: from [192.168.31.77] (24-236-152-143.dhcp.aldl.mi.charter.com. [24.236.152.143]) by mx.google.com with ESMTPSA id nm17sm12856618igb.5.2013.06.16.10.13.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 16 Jun 2013 10:13:26 -0700 (PDT) References: <69CF1AAF-230D-4B2B-9C95-20DDD772997E@dataix.net> Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-36F8F348-6D52-4705-B436-E7F1D4D8402E; protocol="application/pkcs7-signature" Content-Transfer-Encoding: 7bit Message-Id: X-Mailer: iPhone Mail (10B329) From: Jason Hellenthal Subject: Re: How not allow setting ip changes interface down status? Date: Sun, 16 Jun 2013 13:13:25 -0400 To: Jack Vogel X-Gm-Message-State: ALoCoQklKWmv+Uh9tgG0Hns4kKVCG1t7CRMgXo0csuRw+1RMK/R7f6aw82amHOryyu3bI8YgLUtx X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: h bagade , "freebsd-net@freebsd.org" , Adrian Chadd X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jun 2013 17:13:28 -0000 --Apple-Mail-36F8F348-6D52-4705-B436-E7F1D4D8402E Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Off the top of my head I don't know of another OS that does this. But yes agreed changing that behavior would probably effect a lot of people i= n a negative way at this point. Not to mention script breakage. But a tunable in the stack somewhere would be awesome to change this behavio= r. Either interface specific or global or both. Sometimes installing a new faucet you don't want the water to run until all t= he nuts, bolts and washers are installed. --=20 Jason Hellenthal Inbox: jhellenthal@DataIX.net Voice: +1 (616) 953-0176 JJH48-ARIN On Jun 16, 2013, at 12:50, Jack Vogel wrote: > How is adding a small token 'down' with the command a 'PITA', > seems completely reasonable to me? Further, if you changed it > so if didn't bring the interface up you'd probably have a bunch of > people complain because that was the expected behavior :) >=20 > Jack >=20 >=20 >=20 > On Sun, Jun 16, 2013 at 2:28 AM, Jason Hellenthal = wrote: >> Seconded. >>=20 >> But to answer you must specify "down" with every command. >>=20 >> ifconfig wlan0 inet ipa.ddr.her.e/24 down >>=20 >> It's a PITA >>=20 >> -- >> Jason Hellenthal >> Inbox: jhellenthal@DataIX.net >> Voice: +1 (616) 953-0176 >> JJH48-ARIN >>=20 >>=20 >> On Jun 16, 2013, at 3:48, Adrian Chadd wrote: >>=20 >> > That'd actually be nice to have. I've noticed this with wifi and it's >> > irritating. >> > >> > >> > adrian >> > >> > On 15 June 2013 23:59, h bagade wrote: >> >> Hi all, >> >> >> >> I want to know if there is any way to change the current freebsd behav= ior >> >> when setting interface ip address. In current method, when assigning i= p >> >> address to an interface, the interface is set to UP. I need not allowi= ng >> >> this change to be done! If an interface is in down state, setting ip >> >> address doesn't change its sate. >> >> >> >> I'm ready to hear your ideas on my question and what's the pros and co= ns of >> >> the change I'm going to make. >> >> _______________________________________________ >> >> 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"= >> > _______________________________________________ >> > 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" >=20 --Apple-Mail-36F8F348-6D52-4705-B436-E7F1D4D8402E Content-Type: application/pkcs7-signature; name=smime.p7s Content-Disposition: attachment; filename=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGNDCCBjAw ggUYoAMCAQICAwaijjANBgkqhkiG9w0BAQsFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0 YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcx ODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENB MB4XDTEzMDUxODA4NTA0OFoXDTE0MDUxOTIyMDk0N1owSDEfMB0GA1UEAwwWamhlbGxlbnRoYWxA ZGF0YWl4Lm5ldDElMCMGCSqGSIb3DQEJARYWamhlbGxlbnRoYWxAZGF0YWl4Lm5ldDCCASIwDQYJ KoZIhvcNAQEBBQADggEPADCCAQoCggEBALgnYFS1bWZr3KhKBzWAdRwrY+En+RRV8nCaYubqrMG+ YJbuenaIKSbIuFiDWipW4RHYTpE28pKaSnaVTG9WtAZvsWj0gYN9g2fYCnCOUceES2Yvi3RavxpB hsuzKIfsHb8iNNSEuczLu6gn4mQyaHwE4x6xSUKmbK8njR+YoF522F60wjsnq5dlOJdTrhDfObE5 5P23279WbRp8azgZX1VRB66wdKRDuSI1vBts4Nsha2paXd6HUUduHrPACBQREJTGXN8XtEKVwo63 aKUhRgtUwHNEuSWck/xwVl7PBUWH2dORAWTCqHjNuCKNOQ1/0LMiyMj7FdsBjN4dgL4YZpsCAwEA AaOCAtwwggLYMAkGA1UdEwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggr BgEFBQcDBDAdBgNVHQ4EFgQU29qUrmZtgQ7ZVoDKogfpJOSfk+YwHwYDVR0jBBgwFoAUU3Ltkpzg 2ssBXHx+ljVO8tS4UYIwIQYDVR0RBBowGIEWamhlbGxlbnRoYWxAZGF0YWl4Lm5ldDCCAUwGA1Ud IASCAUMwggE/MIIBOwYLKwYBBAGBtTcBAgMwggEqMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0 YXJ0c3NsLmNvbS9wb2xpY3kucGRmMIH3BggrBgEFBQcCAjCB6jAnFiBTdGFydENvbSBDZXJ0aWZp Y2F0aW9uIEF1dGhvcml0eTADAgEBGoG+VGhpcyBjZXJ0aWZpY2F0ZSB3YXMgaXNzdWVkIGFjY29y ZGluZyB0byB0aGUgQ2xhc3MgMSBWYWxpZGF0aW9uIHJlcXVpcmVtZW50cyBvZiB0aGUgU3RhcnRD b20gQ0EgcG9saWN5LCByZWxpYW5jZSBvbmx5IGZvciB0aGUgaW50ZW5kZWQgcHVycG9zZSBpbiBj b21wbGlhbmNlIG9mIHRoZSByZWx5aW5nIHBhcnR5IG9ibGlnYXRpb25zLjA2BgNVHR8ELzAtMCug KaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1MS1jcmwuY3JsMIGOBggrBgEFBQcBAQSB gTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2NzcC5zdGFydHNzbC5jb20vc3ViL2NsYXNzMS9jbGll bnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFz czEuY2xpZW50LmNhLmNydDAjBgNVHRIEHDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJ KoZIhvcNAQELBQADggEBAHsw8/Hw07gsNTKYnld74NBFtHnQOPkXYuccWx3j0PGQe9nqNxeingBf 2yvx+xBQzBoi4J1u84Jbrbe8Ii3+LLD/QMW9cN0SBIgRStPQLVee4STdjeabGmpXQa7omC02wYYO 83qh6CgJEIbmrsBSZH8ZSVrjkC4UmZS8wAQMS3qTWAPF0ZQGWx2+Gks2fXuacyt2LpNR+p9ogjAZ 1/rmUKjNhQZLswytaLRUdwAwSfQ3+TNs68h6Kv1LC3bNGBT3NEtr2q/nzzb5MzuFcDE6f9exroAC 4BHmokAprhna/vZdb6BrPjpXgRAlWAh3wEMxw75M9S/Nbzj/jNp+I+lvUJYxggNvMIIDawIBATCB lDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3Vy ZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEg UHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMGoo4wCQYFKw4DAhoFAKCCAa8wGAYJKoZI hvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwNjE2MTcxMzI3WjAjBgkqhkiG 9w0BCQQxFgQU/XUJozIeN9fP+vudu2utpWoTkWwwgaUGCSsGAQQBgjcQBDGBlzCBlDCBjDELMAkG A1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs IENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJ bnRlcm1lZGlhdGUgQ2xpZW50IENBAgMGoo4wgacGCyqGSIb3DQEJEAILMYGXoIGUMIGMMQswCQYD VQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwg Q2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IElu dGVybWVkaWF0ZSBDbGllbnQgQ0ECAwaijjANBgkqhkiG9w0BAQEFAASCAQCUofJx1ca8iNVaZ8CA 3vFVl5Eui1YeXi9w4oAkKN1CAQjZIcB930b1Fq95JRYfDj6NUSnPf/2RokUpAuQrTsGWWRjhq5oK qlDWZXNIgFWOxsOCrZ26C/eC33x48kQN5pQB5lJaFZ829zOBu46Atq/YDaXC9Fp4kGMmTcENs8Wc gtZuPD9b6RlyPX2+b6S/mHX3+CLRWAjErqEonp4pUe65CV15EOdXLIoe5QeMOB/OSpODOHe4Cf+I 6YbMacRqO7dfAoU5oSbh7IUSpX0WyObXaMesyef/aeOinqef+49Zk9nYtKHyZNVPj9UsHmspt8ne 6oS+hOPQBd/ze08t3JACAAAAAAAA --Apple-Mail-36F8F348-6D52-4705-B436-E7F1D4D8402E-- From owner-freebsd-net@FreeBSD.ORG Sun Jun 16 21:03:04 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2579A95D for ; Sun, 16 Jun 2013 21:03:04 +0000 (UTC) (envelope-from bthcom@higonnet.net) Received: from smtp2-g21.free.fr (smtp2-g21.free.fr [IPv6:2a01:e0c:1:1599::11]) by mx1.freebsd.org (Postfix) with ESMTP id B731318E1 for ; Sun, 16 Jun 2013 21:03:02 +0000 (UTC) Received: from freebsd.higonnet.net (unknown [82.238.41.134]) by smtp2-g21.free.fr (Postfix) with ESMTP id 158534B018B for ; Sun, 16 Jun 2013 23:02:56 +0200 (CEST) Received: from [127.0.0.1] (unknown [192.168.4.77]) by freebsd.higonnet.net (Postfix) with ESMTP id 195C228424 for ; Sun, 16 Jun 2013 23:02:57 +0200 (CEST) Message-ID: <51BE27FF.1020502@higonnet.net> Date: Sun, 16 Jun 2013 23:02:55 +0200 From: Bernard Higonnet User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: "freebsd-net@freebsd.org" Subject: Re: How to find out a VPN link has gone down (or better, come back up)? References: <51BD91E8.8060501@higonnet.net> <5DD08E44-E481-4FF9-A5A8-AFE3E341A57C@my.gd> <51BDCE49.1000207@freebsd.org> In-Reply-To: <51BDCE49.1000207@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 130616-0, 16/06/2013), Outbound message X-Antivirus-Status: Clean X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jun 2013 21:03:04 -0000 Well it does seem to work and is the most straight-forward solution, though presumably the devd approach should work. Thanks to both! Bernard Higonnet On 16/06/2013 16:40, Julian Elischer wrote: > On 6/16/13 8:51 PM, Damien Fleuriot wrote: >> I might be wrong but wouldn't that be a job for devd ? >> >> Alternatively set a cron job every minute to reinstall the route. > > use the up/down scripts to install the routes... that's what they are for. > >> >> >> On 16 Jun 2013, at 12:22, Bernard Higonnet wrote: >> >>> I have a machine, FreeBSD 8.1-RELEASE #0, running a VPN (MPD5) server. >>> >>> Every once in a while, the link goes down, presumably because of some >>> third-party event on the network. >>> >>> When this happens, an element placed in the routing table by hand >>> disappears since the node on the VPN server to the far-off client >>> machine no longer exists (even though the entry in the routing table >>> is marked "permanent" when it does exist). When the network problem >>> goes away, the VPN link is automatically restored, but not the >>> routing table. >>> >>> Can someone tell me if there is a way to be notified that the link >>> has been restored so that I can run a script etc. to restore the >>> routing table to what I want? >>> >>> TIA >>> Bernard Higonnet >>> _______________________________________________ >>> 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" >> _______________________________________________ >> 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" >> >> > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Sun Jun 16 23:32:08 2013 Return-Path: Delivered-To: freebsd-net@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5F062C5B; Sun, 16 Jun 2013 23:32:08 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 399851E49; Sun, 16 Jun 2013 23:32:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r5GNW8Qc050868; Sun, 16 Jun 2013 23:32:08 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5GNW8ma050867; Sun, 16 Jun 2013 23:32:08 GMT (envelope-from linimon) Date: Sun, 16 Jun 2013 23:32:08 GMT Message-Id: <201306162332.r5GNW8ma050867@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/179429: [tap] STP enabled tap bridge X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jun 2013 23:32:08 -0000 Old Synopsis: STP enabled tap bridge New Synopsis: [tap] STP enabled tap bridge Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sun Jun 16 23:31:09 UTC 2013 Responsible-Changed-Why: I'm not 100% sure if this is a suggestion or a problem, but in any case, it belongs to -net. http://www.freebsd.org/cgi/query-pr.cgi?pr=179429 From owner-freebsd-net@FreeBSD.ORG Mon Jun 17 04:54:25 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4A86DC2A for ; Mon, 17 Jun 2013 04:54:25 +0000 (UTC) (envelope-from HomeRetailGroup_EmailFilter@Homeretailgroup.com) Received: from mx08-000ff402.pphosted.com (mx08-000ff402.pphosted.com [91.207.212.48]) by mx1.freebsd.org (Postfix) with ESMTP id C14851AFB for ; Mon, 17 Jun 2013 04:54:24 +0000 (UTC) Received: from pps.filterd (m0040910 [127.0.0.1]) by mx08-000ff402.pphosted.com (8.14.5/8.14.5) with SMTP id r5H42TUI023401 for ; Mon, 17 Jun 2013 05:05:12 +0100 Received: from argos.co.uk (localhost [127.0.0.1]) by mx08-000ff402.pphosted.com with ESMTP id 1d1ttx817s-1 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for ; Mon, 17 Jun 2013 05:05:12 +0100 Received: from m0040910 (m0040910 [127.0.0.1]) by pps.default (8.14.5/8.14.5) with SMTP id r5H45B5O026616 for ; Mon, 17 Jun 2013 05:05:11 +0100 Date: Mon, 17 Jun 2013 05:05:11 +0100 TO: freebsd-net@freebsd.org FROM: HomeRetailGroup_EmailFilter@Homeretailgroup.com Subject: RETURNED MAIL: DATA FORMAT ERROR - Content Violation Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Message-ID: X-Proofpoint-Sentinel: stfsU2FsdGVkX1+2vFd4uoGd+Zgh7EeBF/LsFcn53Krlb5GUeUkE/OcU1A+l mB6zUtE5td7HhQtpfzuQJCbbaCFGlCOMlP813ubVaP9CZq0ULywgYgU9VbmzO5SqL3Y5mvn0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jun 2013 04:54:25 -0000 Hello, this is the Electronic Mail Monitoring Service at Home Retail Group. We recently received an eMail sent from this address to customerservices@habitat.co.uk. I’m sorry, but were unable to deliver this mail as it contains an executable which could pose a threat to our Information Systems. If the eMail is genuinely business related please contact the recipient directly and ask them to contact the Home Retail Group IT Service Desk, who will be able to assist you. Thank you for your attention; apologies for any inconvenience caused. From owner-freebsd-net@FreeBSD.ORG Mon Jun 17 10:04:29 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 02ABDF40; Mon, 17 Jun 2013 10:04:29 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.69.10]) by mx1.freebsd.org (Postfix) with ESMTP id 66CB018B2; Mon, 17 Jun 2013 10:04:27 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.7/8.14.7) with ESMTP id r5HA4Ro3016819; Mon, 17 Jun 2013 14:04:27 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.7/8.14.7/Submit) id r5HA4RRw016818; Mon, 17 Jun 2013 14:04:27 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Mon, 17 Jun 2013 14:04:27 +0400 From: Gleb Smirnoff To: Ermal Lu?i Subject: Re: [PATH] ALTQ(9) codel algorithm implementation Message-ID: <20130617100427.GH1400@glebius.int.ru> References: <20130614095125.GQ12443@FreeBSD.org> <51BAF1BA.8000603@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-net , Andre Oppermann X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jun 2013 10:04:29 -0000 Ermal, On Fri, Jun 14, 2013 at 03:05:16PM +0200, Ermal Lu?i wrote: E> >> I'm afraid we can't grow mbuf packet header with 8 bytes just to satisfy E> >> the ALTQ codel algo, which would definitely have a limited usage among E> >> FreeBSD users. Thus, "enqueue_time" should go into mbuf_tags(9) not into E> >> mbuf packet header. E> >> E> > E> > Agreed. We don't have space for that in the mbuf header. There's some E> > other E> > fields that may be repurposed though, the header pointer for example which E> > is E> > almost entirely unused. With some updates to the TSO and Checksum offload E> > mechanism I have in the pipeline the "header" field can be easily E> > repurposed. E> > E> > Though I'm against an "obscure" ALTQ mechanism having its own mbuf header E> > field E> > as such. It must be a generic field that can be used by others as well. E> > E> > Yeah i forgot to clarify that. E> The initial implementation had the added field in tag of pf but for some E> reason i did not investigate, E> and this can be a more deep problem the tag not always made it up to ALTQ. E> Hence it was put in the mbuf header. E> E> I did not find a direct way on why the mbuf tag was lost. E> Also with codel this does give lots of dropped packet hence i choose this E> way. E> I do not like to grow the mbuf tag as well but that was the only consistent E> way to get this to work reliably. My guess is, that's because in FreeBSD 10 the pf mtag isn't allocated unconditionally, like it was in 9.x. Packets can flow through pf w/o pf mtag. You don't need to pollute the pf mtag, you just need to create a new tag for the codel. Sorry, but failure to find why smth doesn't works as expected isn't an excuse for a gross hack that affects entire network stack. -- Totus tuus, Glebius. From owner-freebsd-net@FreeBSD.ORG Mon Jun 17 11:06:49 2013 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F41B31F0 for ; Mon, 17 Jun 2013 11:06:48 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id E5CB21C17 for ; Mon, 17 Jun 2013 11:06:48 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r5HB6msU012803 for ; Mon, 17 Jun 2013 11:06:48 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5HB6mVg012801 for freebsd-net@FreeBSD.org; Mon, 17 Jun 2013 11:06:48 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 17 Jun 2013 11:06:48 GMT Message-Id: <201306171106.r5HB6mVg012801@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Subject: Current problem reports assigned to freebsd-net@FreeBSD.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jun 2013 11:06:49 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/179429 net [tap] STP enabled tap bridge o kern/179299 net [igb] Intel X540-T2 - unstable driver a kern/179264 net [vimage] [pf] Core dump with Packet filter and VIMAGE o kern/178947 net [arp] arp rejecting not working o kern/178782 net [ixgbe] 82599EB SFP does not work with passthrough und o kern/178612 net [run] kernel panic due the problems with run driver o kern/178472 net [ip6] [patch] make return code consistent with IPv4 co o kern/178116 net [ipfilter] [panic] Kernel panic: general protection fa o kern/178079 net [tcp] Switching TCP CC algorithm panics on sparc64 wit s kern/178071 net FreeBSD unable to recongize Kontron (Industrial Comput o kern/177905 net [xl] [panic] ifmedia_set when pluging CardBus LAN card o kern/177618 net [bridge] Problem with bridge firewall with trunk ports o kern/177417 net [ip6] Invalid protocol value in ipsec6_common_input_cb o kern/177402 net [igb] [pf] problem with ethernet driver igb + pf / alt o kern/177400 net [jme] JMC25x 1000baseT establishment issues o kern/177366 net [ieee80211] negative malloc(9) statistics for 80211nod f kern/177362 net [netinet] [patch] Wrong control used to return TOS o kern/177194 net [netgraph] Unnamed netgraph nodes for vlan interfaces o kern/177139 net [igb] igb drops ethernet ports 2 and 3 o kern/176884 net [re] re0 flapping up/down o kern/176671 net [epair] MAC address for epair device not unique o kern/176484 net [ipsec] [enc] [patch] panic: IPsec + enc(4); device na o kern/176446 net [netinet] [patch] Concurrency in ixgbe driving out-of- o kern/176420 net [kernel] [patch] incorrect errno for LOCAL_PEERCRED o kern/176419 net [kernel] [patch] socketpair support for LOCAL_PEERCRED o kern/176401 net [netgraph] page fault in netgraph o kern/176167 net [ipsec][lagg] using lagg and ipsec causes immediate pa o kern/176097 net [lagg] [patch] lagg/lacp broken when aggregated interf o kern/176027 net [em] [patch] flow control systcl consistency for em dr o kern/176026 net [tcp] [patch] TCP wrappers caused quite a lot of warni o bin/175974 net ppp(8): logic issue o kern/175864 net [re] Intel MB D510MO, onboard ethernet not working aft o kern/175852 net [amd64] [patch] in_cksum_hdr() behaves differently on o kern/175734 net no ethernet detected on system with EG20T PCH chipset o kern/175267 net [pf] [tap] pf + tap keep state problem o kern/175236 net [epair] [gif] epair and gif Devices On Bridge o kern/175182 net [panic] kernel panic on RADIX_MPATH when deleting rout o kern/175153 net [tcp] will there miss a FIN when do TSO? o kern/174959 net [net] [patch] rnh_walktree_from visits spurious nodes o kern/174958 net [net] [patch] rnh_walktree_from makes unreasonable ass o kern/174897 net [route] Interface routes are broken o kern/174851 net [bxe] [patch] UDP checksum offload is wrong in bxe dri o kern/174850 net [bxe] [patch] bxe driver does not receive multicasts o kern/174849 net [bxe] [patch] bxe driver can hang kernel when reset o kern/174822 net [tcp] Page fault in tcp_discardcb under high traffic o kern/174602 net [gif] [ipsec] traceroute issue on gif tunnel with ipse o kern/174535 net [tcp] TCP fast retransmit feature works strange o kern/173871 net [gif] process of 'ifconfig gif0 create hangs' when if_ o kern/173475 net [tun] tun(4) stays opened by PID after process is term o kern/173201 net [ixgbe] [patch] Missing / broken ixgbe sysctl's and tu o kern/173137 net [em] em(4) unable to run at gigabit with 9.1-RC2 o kern/173002 net [patch] data type size problem in if_spppsubr.c o kern/172895 net [ixgb] [ixgbe] do not properly determine link-state o kern/172683 net [ip6] Duplicate IPv6 Link Local Addresses o kern/172675 net [netinet] [patch] sysctl_tcp_hc_list (net.inet.tcp.hos o kern/172113 net [panic] [e1000] [patch] 9.1-RC1/amd64 panices in igb(4 o kern/171840 net [ip6] IPv6 packets transmitting only on queue 0 o kern/171739 net [bce] [panic] bce related kernel panic o kern/171711 net [dummynet] [panic] Kernel panic in dummynet o kern/171532 net [ndis] ndis(4) driver includes 'pccard'-specific code, o kern/171531 net [ndis] undocumented dependency for ndis(4) o kern/171524 net [ipmi] ipmi driver crashes kernel by reboot or shutdow s kern/171508 net [epair] [request] Add the ability to name epair device o kern/171228 net [re] [patch] if_re - eeprom write issues o kern/170701 net [ppp] killl ppp or reboot with active ppp connection c o kern/170267 net [ixgbe] IXGBE_LE32_TO_CPUS is probably an unintentiona o kern/170081 net [fxp] pf/nat/jails not working if checksum offloading o kern/169898 net ifconfig(8) fails to set MTU on multiple interfaces. o kern/169676 net [bge] [hang] system hangs, fully or partially after re o kern/169664 net [bgp] Wrongful replacement of interface connected net o kern/169620 net [ng] [pf] ng_l2tp incoming packet bypass pf firewall o kern/169459 net [ppp] umodem/ppp/3g stopped working after update from o kern/169438 net [ipsec] ipv4-in-ipv6 tunnel mode IPsec does not work p kern/168294 net [ixgbe] [patch] ixgbe driver compiled in kernel has no o kern/168246 net [em] Multiple em(4) not working with qemu o kern/168245 net [arp] [regression] Permanent ARP entry not deleted on o kern/168244 net [arp] [regression] Unable to manually remove permanent o kern/168183 net [bce] bce driver hang system o kern/167947 net [setfib] [patch] arpresolve checks only the default FI o kern/167603 net [ip] IP fragment reassembly's broken: file transfer ov o kern/167500 net [em] [panic] Kernel panics in em driver o kern/167325 net [netinet] [patch] sosend sometimes return EINVAL with o kern/167202 net [igmp]: Sending multiple IGMP packets crashes kernel o kern/166940 net [ipfilter] [panic] Double fault in kern 8.2 o kern/166462 net [gre] gre(4) when using a tunnel source address from c o kern/166372 net [patch] [ipfilter] drops UDP packets with zero checksu o kern/166285 net [arp] FreeBSD v8.1 REL p8 arp: unknown hardware addres o kern/166255 net [net] [patch] It should be possible to disable "promis o kern/165963 net [panic] [ipfilter] ipfilter/nat NULL pointer deference p kern/165903 net mbuf leak o kern/165622 net [ndis][panic][patch] Unregistered use of FPU in kernel s kern/165562 net [request] add support for Intel i350 in FreeBSD 7.4 o kern/165526 net [bxe] UDP packets checksum calculation whithin if_bxe o kern/165488 net [ppp] [panic] Fatal trap 12 jails and ppp , kernel wit o kern/165305 net [ip6] [request] Feature parity between IP_TOS and IPV6 o kern/165296 net [vlan] [patch] Fix EVL_APPLY_VLID, update EVL_APPLY_PR o kern/165181 net [igb] igb freezes after about 2 weeks of uptime o kern/165174 net [patch] [tap] allow tap(4) to keep its address on clos o kern/165152 net [ip6] Does not work through the issue of ipv6 addresse o kern/164495 net [igb] connect double head igb to switch cause system t o kern/164490 net [pfil] Incorrect IP checksum on pfil pass from ip_outp o kern/164475 net [gre] gre misses RUNNING flag after a reboot o kern/164265 net [netinet] [patch] tcp_lro_rx computes wrong checksum i o kern/163903 net [igb] "igb0:tx(0)","bpf interface lock" v2.2.5 9-STABL o kern/163481 net freebsd do not add itself to ping route packet o kern/162927 net [tun] Modem-PPP error ppp[1538]: tun0: Phase: Clearing o kern/162926 net [ipfilter] Infinite loop in ipfilter with fragmented I o kern/162558 net [dummynet] [panic] seldom dummynet panics o kern/162153 net [em] intel em driver 7.2.4 don't compile o kern/162110 net [igb] [panic] RELENG_9 panics on boot in IGB driver - o kern/162028 net [ixgbe] [patch] misplaced #endif in ixgbe.c o kern/161277 net [em] [patch] BMC cannot receive IPMI traffic after loa o kern/160873 net [igb] igb(4) from HEAD fails to build on 7-STABLE o kern/160750 net Intel PRO/1000 connection breaks under load until rebo o kern/160693 net [gif] [em] Multicast packet are not passed from GIF0 t o kern/160293 net [ieee80211] ppanic] kernel panic during network setup o kern/160206 net [gif] gifX stops working after a while (IPv6 tunnel) o kern/159817 net [udp] write UDPv4: No buffer space available (code=55) o kern/159629 net [ipsec] [panic] kernel panic with IPsec in transport m o kern/159621 net [tcp] [panic] panic: soabort: so_count o kern/159603 net [netinet] [patch] in_ifscrubprefix() - network route c o kern/159601 net [netinet] [patch] in_scrubprefix() - loopback route re o kern/159294 net [em] em watchdog timeouts o kern/159203 net [wpi] Intel 3945ABG Wireless LAN not support IBSS o kern/158930 net [bpf] BPF element leak in ifp->bpf_if->bif_dlist o kern/158726 net [ip6] [patch] ICMPv6 Router Announcement flooding limi o kern/158694 net [ix] [lagg] ix0 is not working within lagg(4) o kern/158665 net [ip6] [panic] kernel pagefault in in6_setscope() o kern/158635 net [em] TSO breaks BPF packet captures with em driver f kern/157802 net [dummynet] [panic] kernel panic in dummynet o kern/157785 net amd64 + jail + ipfw + natd = very slow outbound traffi o kern/157418 net [em] em driver lockup during boot on Supermicro X9SCM- o kern/157410 net [ip6] IPv6 Router Advertisements Cause Excessive CPU U o kern/157287 net [re] [panic] INVARIANTS panic (Memory modified after f o kern/157200 net [network.subr] [patch] stf(4) can not communicate betw o kern/157182 net [lagg] lagg interface not working together with epair o kern/156877 net [dummynet] [panic] dummynet move_pkt() null ptr derefe o kern/156667 net [em] em0 fails to init on CURRENT after March 17 o kern/156408 net [vlan] Routing failure when using VLANs vs. Physical e o kern/156328 net [icmp]: host can ping other subnet but no have IP from o kern/156317 net [ip6] Wrong order of IPv6 NS DAD/MLD Report o kern/156283 net [ip6] [patch] nd6_ns_input - rtalloc_mpath does not re o kern/156279 net [if_bridge][divert][ipfw] unable to correctly re-injec o kern/156226 net [lagg]: failover does not announce the failover to swi o kern/156030 net [ip6] [panic] Crash in nd6_dad_start() due to null ptr o kern/155680 net [multicast] problems with multicast s kern/155642 net [new driver] [request] Add driver for Realtek RTL8191S o kern/155597 net [panic] Kernel panics with "sbdrop" message o kern/155420 net [vlan] adding vlan break existent vlan o kern/155177 net [route] [panic] Panic when inject routes in kernel p kern/155030 net [igb] igb(4) DEVICE_POLLING does not work with carp(4) o kern/155010 net [msk] ntfs-3g via iscsi using msk driver cause kernel o kern/154943 net [gif] ifconfig gifX create on existing gifX clears IP s kern/154851 net [new driver] [request]: Port brcm80211 driver from Lin o kern/154850 net [netgraph] [patch] ng_ether fails to name nodes when t o kern/154679 net [em] Fatal trap 12: "em1 taskq" only at startup (8.1-R o kern/154600 net [tcp] [panic] Random kernel panics on tcp_output o kern/154557 net [tcp] Freeze tcp-session of the clients, if in the gat o kern/154443 net [if_bridge] Kernel module bridgestp.ko missing after u o kern/154286 net [netgraph] [panic] 8.2-PRERELEASE panic in netgraph o kern/154255 net [nfs] NFS not responding o kern/154214 net [stf] [panic] Panic when creating stf interface o kern/154185 net race condition in mb_dupcl p kern/154169 net [multicast] [ip6] Node Information Query multicast add o kern/154134 net [ip6] stuck kernel state in LISTEN on ipv6 daemon whic o kern/154091 net [netgraph] [panic] netgraph, unaligned mbuf? o conf/154062 net [vlan] [patch] change to way of auto-generatation of v o kern/153937 net [ral] ralink panics the system (amd64 freeBSDD 8.X) wh o kern/153936 net [ixgbe] [patch] MPRC workaround incorrectly applied to o kern/153816 net [ixgbe] ixgbe doesn't work properly with the Intel 10g o kern/153772 net [ixgbe] [patch] sysctls reference wrong XON/XOFF varia o kern/153497 net [netgraph] netgraph panic due to race conditions o kern/153454 net [patch] [wlan] [urtw] Support ad-hoc and hostap modes o kern/153308 net [em] em interface use 100% cpu o kern/153244 net [em] em(4) fails to send UDP to port 0xffff o kern/152893 net [netgraph] [panic] 8.2-PRERELEASE panic in netgraph o kern/152853 net [em] tftpd (and likely other udp traffic) fails over e o kern/152828 net [em] poor performance on 8.1, 8.2-PRE o kern/152569 net [net]: Multiple ppp connections and routing table prob o kern/152235 net [arp] Permanent local ARP entries are not properly upd o kern/152141 net [vlan] [patch] encapsulate vlan in ng_ether before out o kern/152036 net [libc] getifaddrs(3) returns truncated sockaddrs for n o kern/151690 net [ep] network connectivity won't work until dhclient is o kern/151681 net [nfs] NFS mount via IPv6 leads to hang on client with o kern/151593 net [igb] [panic] Kernel panic when bringing up igb networ o kern/150920 net [ixgbe][igb] Panic when packets are dropped with heade o kern/150557 net [igb] igb0: Watchdog timeout -- resetting o kern/150251 net [patch] [ixgbe] Late cable insertion broken o kern/150249 net [ixgbe] Media type detection broken o bin/150224 net ppp(8) does not reassign static IP after kill -KILL co f kern/149969 net [wlan] [ral] ralink rt2661 fails to maintain connectio o kern/149937 net [ipfilter] [patch] kernel panic in ipfilter IP fragmen o kern/149643 net [rum] device not sending proper beacon frames in ap mo o kern/149609 net [panic] reboot after adding second default route o kern/149117 net [inet] [patch] in_pcbbind: redundant test o kern/149086 net [multicast] Generic multicast join failure in 8.1 o kern/148018 net [flowtable] flowtable crashes on ia64 o kern/147912 net [boot] FreeBSD 8 Beta won't boot on Thinkpad i1300 11 o kern/147894 net [ipsec] IPv6-in-IPv4 does not work inside an ESP-only o kern/147155 net [ip6] setfb not work with ipv6 o kern/146845 net [libc] close(2) returns error 54 (connection reset by f kern/146792 net [flowtable] flowcleaner 100% cpu's core load o kern/146719 net [pf] [panic] PF or dumynet kernel panic o kern/146534 net [icmp6] wrong source address in echo reply o kern/146427 net [mwl] Additional virtual access points don't work on m f kern/146394 net [vlan] IP source address for outgoing connections o bin/146377 net [ppp] [tun] Interface doesn't clear addresses when PPP o kern/146358 net [vlan] wrong destination MAC address o kern/146165 net [wlan] [panic] Setting bssid in adhoc mode causes pani o kern/146082 net [ng_l2tp] a false invaliant check was performed in ng_ o kern/146037 net [panic] mpd + CoA = kernel panic o kern/145825 net [panic] panic: soabort: so_count o kern/145728 net [lagg] Stops working lagg between two servers. p kern/145600 net TCP/ECN behaves different to CE/CWR than ns2 reference f kern/144917 net [flowtable] [panic] flowtable crashes system [regressi o kern/144882 net MacBookPro =>4.1 does not connect to BSD in hostap wit o kern/144874 net [if_bridge] [patch] if_bridge frees mbuf after pfil ho o conf/144700 net [rc.d] async dhclient breaks stuff for too many people o kern/144616 net [nat] [panic] ip_nat panic FreeBSD 7.2 f kern/144315 net [ipfw] [panic] freebsd 8-stable reboot after add ipfw o kern/144231 net bind/connect/sendto too strict about sockaddr length o kern/143846 net [gif] bringing gif3 tunnel down causes gif0 tunnel to s kern/143673 net [stf] [request] there should be a way to support multi s kern/143666 net [ip6] [request] PMTU black hole detection not implemen o kern/143622 net [pfil] [patch] unlock pfil lock while calling firewall o kern/143593 net [ipsec] When using IPSec, tcpdump doesn't show outgoin o kern/143591 net [ral] RT2561C-based DLink card (DWL-510) fails to work o kern/143208 net [ipsec] [gif] IPSec over gif interface not working o kern/143034 net [panic] system reboots itself in tcp code [regression] o kern/142877 net [hang] network-related repeatable 8.0-STABLE hard hang o kern/142774 net Problem with outgoing connections on interface with mu o kern/142772 net [libc] lla_lookup: new lle malloc failed f kern/142518 net [em] [lagg] Problem on 8.0-STABLE with em and lagg o kern/142018 net [iwi] [patch] Possibly wrong interpretation of beacon- o kern/141861 net [wi] data garbled with WEP and wi(4) with Prism 2.5 f kern/141741 net Etherlink III NIC won't work after upgrade to FBSD 8, o kern/140742 net rum(4) Two asus-WL167G adapters cannot talk to each ot o kern/140682 net [netgraph] [panic] random panic in netgraph f kern/140634 net [vlan] destroying if_lagg interface with if_vlan membe o kern/140619 net [ifnet] [patch] refine obsolete if_var.h comments desc o kern/140346 net [wlan] High bandwidth use causes loss of wlan connecti o kern/140142 net [ip6] [panic] FreeBSD 7.2-amd64 panic w/IPv6 o kern/140066 net [bwi] install report for 8.0 RC 2 (multiple problems) o kern/139565 net [ipfilter] ipfilter ioctl SIOCDELST broken o kern/139387 net [ipsec] Wrong lenth of PF_KEY messages in promiscuous o bin/139346 net [patch] arp(8) add option to remove static entries lis o kern/139268 net [if_bridge] [patch] allow if_bridge to forward just VL p kern/139204 net [arp] DHCP server replies rejected, ARP entry lost bef o kern/139117 net [lagg] + wlan boot timing (EBUSY) o kern/139058 net [ipfilter] mbuf cluster leak on FreeBSD 7.2 o kern/138850 net [dummynet] dummynet doesn't work correctly on a bridge o kern/138782 net [panic] sbflush_internal: cc 0 || mb 0xffffff004127b00 o kern/138688 net [rum] possibly broken on 8 Beta 4 amd64: able to wpa a o kern/138678 net [lo] FreeBSD does not assign linklocal address to loop o kern/138407 net [gre] gre(4) interface does not come up after reboot o kern/138332 net [tun] [lor] ifconfig tun0 destroy causes LOR if_adata/ o kern/138266 net [panic] kernel panic when udp benchmark test used as r o kern/138177 net [ipfilter] FreeBSD crashing repeatedly in ip_nat.c:257 f kern/138029 net [bpf] [panic] periodically kernel panic and reboot o kern/137881 net [netgraph] [panic] ng_pppoe fatal trap 12 p bin/137841 net [patch] wpa_supplicant(8) cannot verify SHA256 signed p kern/137776 net [rum] panic in rum(4) driver on 8.0-BETA2 o bin/137641 net ifconfig(8): various problems with "vlan_device.vlan_i o kern/137392 net [ip] [panic] crash in ip_nat.c line 2577 o kern/137372 net [ral] FreeBSD doesn't support wireless interface from o kern/137089 net [lagg] lagg falsely triggers IPv6 duplicate address de o kern/136911 net [netgraph] [panic] system panic on kldload ng_bpf.ko t o kern/136618 net [pf][stf] panic on cloning interface without unit numb o kern/135502 net [periodic] Warning message raised by rtfree function i o kern/134583 net [hang] Machine with jail freezes after random amount o o kern/134531 net [route] [panic] kernel crash related to routes/zebra o kern/134157 net [dummynet] dummynet loads cpu for 100% and make a syst o kern/133969 net [dummynet] [panic] Fatal trap 12: page fault while in o kern/133968 net [dummynet] [panic] dummynet kernel panic o kern/133736 net [udp] ip_id not protected ... o kern/133595 net [panic] Kernel Panic at pcpu.h:195 o kern/133572 net [ppp] [hang] incoming PPTP connection hangs the system o kern/133490 net [bpf] [panic] 'kmem_map too small' panic on Dell r900 o kern/133235 net [netinet] [patch] Process SIOCDLIFADDR command incorre f kern/133213 net arp and sshd errors on 7.1-PRERELEASE o kern/133060 net [ipsec] [pfsync] [panic] Kernel panic with ipsec + pfs o kern/132889 net [ndis] [panic] NDIS kernel crash on load BCM4321 AGN d o conf/132851 net [patch] rc.conf(5): allow to setfib(1) for service run o kern/132734 net [ifmib] [panic] panic in net/if_mib.c o kern/132705 net [libwrap] [patch] libwrap - infinite loop if hosts.all o kern/132672 net [ndis] [panic] ndis with rt2860.sys causes kernel pani o kern/132554 net [ipfilter] There is no ippool start script/ipfilter ma o kern/132354 net [nat] Getting some packages to ipnat(8) causes crash o kern/132277 net [crypto] [ipsec] poor performance using cryptodevice f o kern/131781 net [ndis] ndis keeps dropping the link o kern/131776 net [wi] driver fails to init o kern/131753 net [altq] [panic] kernel panic in hfsc_dequeue o kern/131601 net [ipfilter] [panic] 7-STABLE panic in nat_finalise (tcp o bin/131365 net route(8): route add changes interpretation of network f kern/130820 net [ndis] wpa_supplicant(8) returns 'no space on device' o kern/130628 net [nfs] NFS / rpc.lockd deadlock on 7.1-R o conf/130555 net [ipfilter] [rc.d] [patch] No good way to set ipfilter o kern/130525 net [ndis] [panic] 64 bit ar5008 ndisgen-erated driver cau o kern/130311 net [wlan_xauth] [panic] hostapd restart causing kernel pa o kern/130109 net [ipfw] Can not set fib for packets originated from loc f kern/130059 net [panic] Leaking 50k mbufs/hour f kern/129719 net [nfs] [panic] Panic during shutdown, tcp_ctloutput: in o kern/129517 net [ipsec] [panic] double fault / stack overflow f kern/129508 net [carp] [panic] Kernel panic with EtherIP (may be relat o kern/129219 net [ppp] Kernel panic when using kernel mode ppp o kern/129197 net [panic] 7.0 IP stack related panic o bin/128954 net ifconfig(8) deletes valid routes o bin/128602 net [an] wpa_supplicant(8) crashes with an(4) o kern/128448 net [nfs] 6.4-RC1 Boot Fails if NFS Hostname cannot be res o bin/128295 net [patch] ifconfig(8) does not print TOE4 or TOE6 capabi o bin/128001 net wpa_supplicant(8), wlan(4), and wi(4) issues o kern/127826 net [iwi] iwi0 driver has reduced performance and connecti o kern/127815 net [gif] [patch] if_gif does not set vlan attributes from o kern/127724 net [rtalloc] rtfree: 0xc5a8f870 has 1 refs f bin/127719 net [arp] arp: Segmentation fault (core dumped) f kern/127528 net [icmp]: icmp socket receives icmp replies not owned by p kern/127360 net [socket] TOE socket options missing from sosetopt() o bin/127192 net routed(8) removes the secondary alias IP of interface f kern/127145 net [wi]: prism (wi) driver crash at bigger traffic o kern/126895 net [patch] [ral] Add antenna selection (marked as TBD) o kern/126874 net [vlan]: Zebra problem if ifconfig vlanX destroy o kern/126695 net rtfree messages and network disruption upon use of if_ o kern/126339 net [ipw] ipw driver drops the connection o kern/126075 net [inet] [patch] internet control accesses beyond end of o bin/125922 net [patch] Deadlock in arp(8) o kern/125920 net [arp] Kernel Routing Table loses Ethernet Link status o kern/125845 net [netinet] [patch] tcp_lro_rx() should make use of hard o kern/125258 net [socket] socket's SO_REUSEADDR option does not work o kern/125239 net [gre] kernel crash when using gre o kern/124341 net [ral] promiscuous mode for wireless device ral0 looses o kern/124225 net [ndis] [patch] ndis network driver sometimes loses net o kern/124160 net [libc] connect(2) function loops indefinitely o kern/124021 net [ip6] [panic] page fault in nd6_output() o kern/123968 net [rum] [panic] rum driver causes kernel panic with WPA. o kern/123892 net [tap] [patch] No buffer space available o kern/123890 net [ppp] [panic] crash & reboot on work with PPP low-spee o kern/123858 net [stf] [patch] stf not usable behind a NAT o kern/123796 net [ipfilter] FreeBSD 6.1+VPN+ipnat+ipf: port mapping doe o kern/123758 net [panic] panic while restarting net/freenet6 o bin/123633 net ifconfig(8) doesn't set inet and ether address in one o kern/123559 net [iwi] iwi periodically disassociates/associates [regre o bin/123465 net [ip6] route(8): route add -inet6 -interfac o kern/123463 net [ipsec] [panic] repeatable crash related to ipsec-tool o conf/123330 net [nsswitch.conf] Enabling samba wins in nsswitch.conf c o kern/123160 net [ip] Panic and reboot at sysctl kern.polling.enable=0 o kern/122989 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/122954 net [lagg] IPv6 EUI64 incorrectly chosen for lagg devices f kern/122780 net [lagg] tcpdump on lagg interface during high pps wedge o kern/122685 net It is not visible passing packets in tcpdump(1) o kern/122319 net [wi] imposible to enable ad-hoc demo mode with Orinoco o kern/122290 net [netgraph] [panic] Netgraph related "kmem_map too smal o kern/122252 net [ipmi] [bge] IPMI problem with BCM5704 (does not work o kern/122033 net [ral] [lor] Lock order reversal in ral0 at bootup ieee o bin/121895 net [patch] rtsol(8)/rtsold(8) doesn't handle managed netw s kern/121774 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/121555 net [panic] Fatal trap 12: current process = 12 (swi1: net o kern/121443 net [gif] [lor] icmp6_input/nd6_lookup o kern/121437 net [vlan] Routing to layer-2 address does not work on VLA o bin/121359 net [patch] [security] ppp(8): fix local stack overflow in o kern/121257 net [tcp] TSO + natd -> slow outgoing tcp traffic o kern/121181 net [panic] Fatal trap 3: breakpoint instruction fault whi o kern/120966 net [rum] kernel panic with if_rum and WPA encryption o kern/120566 net [request]: ifconfig(8) make order of arguments more fr o kern/120304 net [netgraph] [patch] netgraph source assumes 32-bit time o kern/120266 net [udp] [panic] gnugk causes kernel panic when closing U o bin/120060 net routed(8) deletes link-level routes in the presence of o kern/119945 net [rum] [panic] rum device in hostap mode, cause kernel o kern/119791 net [nfs] UDP NFS mount of aliased IP addresses from a Sol o kern/119617 net [nfs] nfs error on wpa network when reseting/shutdown f kern/119516 net [ip6] [panic] _mtx_lock_sleep: recursed on non-recursi o kern/119432 net [arp] route add -host -iface causes arp e o kern/119225 net [wi] 7.0-RC1 no carrier with Prism 2.5 wifi card [regr o kern/118727 net [netgraph] [patch] [request] add new ng_pf module o kern/117423 net [vlan] Duplicate IP on different interfaces o bin/117339 net [patch] route(8): loading routing management commands o bin/116643 net [patch] [request] fstat(1): add INET/INET6 socket deta o kern/116185 net [iwi] if_iwi driver leads system to reboot o kern/115239 net [ipnat] panic with 'kmem_map too small' using ipnat o kern/115019 net [netgraph] ng_ether upper hook packet flow stops on ad o kern/115002 net [wi] if_wi timeout. failed allocation (busy bit). ifco o kern/114915 net [patch] [pcn] pcn (sys/pci/if_pcn.c) ethernet driver f o kern/113432 net [ucom] WARNING: attempt to net_add_domain(netgraph) af o kern/112722 net [ipsec] [udp] IP v4 udp fragmented packet reject o kern/112686 net [patm] patm driver freezes System (FreeBSD 6.2-p4) i38 o bin/112557 net [patch] ppp(8) lock file should not use symlink name o kern/112528 net [nfs] NFS over TCP under load hangs with "impossible p o kern/111537 net [inet6] [patch] ip6_input() treats mbuf cluster wrong o kern/111457 net [ral] ral(4) freeze o kern/110284 net [if_ethersubr] Invalid Assumption in SIOCSIFADDR in et o kern/110249 net [kernel] [regression] [patch] setsockopt() error regre o kern/109470 net [wi] Orinoco Classic Gold PC Card Can't Channel Hop o bin/108895 net pppd(8): PPPoE dead connections on 6.2 [regression] o kern/107944 net [wi] [patch] Forget to unlock mutex-locks o conf/107035 net [patch] bridge(8): bridge interface given in rc.conf n o kern/106444 net [netgraph] [panic] Kernel Panic on Binding to an ip to o kern/106316 net [dummynet] dummynet with multipass ipfw drops packets o kern/105945 net Address can disappear from network interface s kern/105943 net Network stack may modify read-only mbuf chain copies o bin/105925 net problems with ifconfig(8) and vlan(4) [regression] o kern/104851 net [inet6] [patch] On link routes not configured when usi o kern/104751 net [netgraph] kernel panic, when getting info about my tr o kern/103191 net Unpredictable reboot o kern/103135 net [ipsec] ipsec with ipfw divert (not NAT) encodes a pac o kern/102540 net [netgraph] [patch] supporting vlan(4) by ng_fec(4) o conf/102502 net [netgraph] [patch] ifconfig name does't rename netgrap o kern/102035 net [plip] plip networking disables parallel port printing o kern/101948 net [ipfilter] [panic] Kernel Panic Trap No 12 Page Fault o kern/100709 net [libc] getaddrinfo(3) should return TTL info o kern/100519 net [netisr] suggestion to fix suboptimal network polling o kern/98978 net [ipfilter] [patch] ipfilter drops OOW packets under 6. o kern/98597 net [inet6] Bug in FreeBSD 6.1 IPv6 link-local DAD procedu o bin/98218 net wpa_supplicant(8) blacklist not working o kern/97306 net [netgraph] NG_L2TP locks after connection with failed o conf/97014 net [gif] gifconfig_gif? in rc.conf does not recognize IPv f kern/96268 net [socket] TCP socket performance drops by 3000% if pack o kern/95519 net [ral] ral0 could not map mbuf o kern/95288 net [pppd] [tty] [panic] if_ppp panic in sys/kern/tty_subr o kern/95277 net [netinet] [patch] IP Encapsulation mask_match() return o kern/95267 net packet drops periodically appear f kern/93378 net [tcp] Slow data transfer in Postfix and Cyrus IMAP (wo o kern/93019 net [ppp] ppp and tunX problems: no traffic after restarti o kern/92880 net [libc] [patch] almost rewritten inet_network(3) functi s kern/92279 net [dc] Core faults everytime I reboot, possible NIC issu o kern/91859 net [ndis] if_ndis does not work with Asus WL-138 s kern/91777 net [ipfilter] [patch] wrong behaviour with skip rule insi o kern/91364 net [ral] [wep] WF-511 RT2500 Card PCI and WEP o kern/91311 net [aue] aue interface hanging o kern/87521 net [ipfilter] [panic] using ipfilter "auth" keyword leads o kern/87421 net [netgraph] [panic]: ng_ether + ng_eiface + if_bridge o kern/86871 net [tcp] [patch] allocation logic for PCBs in TIME_WAIT s o kern/86427 net [lor] Deadlock with FASTIPSEC and nat o kern/86103 net [ipfilter] Illegal NAT Traversal in IPFilter o kern/85780 net 'panic: bogus refcnt 0' in routing/ipv6 o bin/85445 net ifconfig(8): deprecated keyword to ifconfig inoperativ o bin/82975 net route change does not parse classfull network as given o kern/82881 net [netgraph] [panic] ng_fec(4) causes kernel panic after o kern/82468 net Using 64MB tcp send/recv buffers, trafficflow stops, i o bin/82185 net [patch] ndp(8) can delete the incorrect entry o kern/81095 net IPsec connection stops working if associated network i o kern/78968 net FreeBSD freezes on mbufs exhaustion (network interface o kern/78090 net [ipf] ipf filtering on bridged packets doesn't work if o kern/77341 net [ip6] problems with IPV6 implementation s kern/77195 net [ipfilter] [patch] ipfilter ioctl SIOCGNATL does not m o kern/75873 net Usability problem with non-RFC-compliant IP spoof prot s kern/75407 net [an] an(4): no carrier after short time a kern/71474 net [route] route lookup does not skip interfaces marked d o kern/71469 net default route to internet magically disappears with mu o kern/70904 net [ipfilter] ipfilter ipnat problem with h323 proxy supp o kern/68889 net [panic] m_copym, length > size of mbuf chain o kern/66225 net [netgraph] [patch] extend ng_eiface(4) control message o kern/65616 net IPSEC can't detunnel GRE packets after real ESP encryp s kern/60293 net [patch] FreeBSD arp poison patch a kern/56233 net IPsec tunnel (ESP) over IPv6: MTU computation is wrong s bin/41647 net ifconfig(8) doesn't accept lladdr along with inet addr o kern/39937 net ipstealth issue a kern/38554 net [patch] changing interface ipaddress doesn't seem to w o kern/34665 net [ipfilter] [hang] ipfilter rcmd proxy "hangs". o kern/31940 net ip queue length too short for >500kpps o kern/31647 net [libc] socket calls can return undocumented EINVAL o kern/30186 net [libc] getaddrinfo(3) does not handle incorrect servna o kern/27474 net [ipfilter] [ppp] Interactive use of user PPP and ipfil f kern/24959 net [patch] proper TCP_NOPUSH/TCP_CORK compatibility o conf/23063 net [arp] [patch] for static ARP tables in rc.network o kern/21998 net [socket] [patch] ident only for outgoing connections o kern/5877 net [socket] sb_cc counts control data as well as data dat 465 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Jun 17 14:12:32 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C68DC93C for ; Mon, 17 Jun 2013 14:12:32 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: from acm.poly.edu (acm.poly.edu [64.147.113.26]) by mx1.freebsd.org (Postfix) with ESMTP id A2DF61937 for ; Mon, 17 Jun 2013 14:12:32 +0000 (UTC) Received: from acm.poly.edu (localhost [127.0.0.1]) by acm.poly.edu (Postfix) with ESMTP id F006B1F1530 for ; Mon, 17 Jun 2013 10:12:31 -0400 (EDT) Received: (qmail 63855 invoked from network); 17 Jun 2013 14:12:31 -0000 Received: from unknown (HELO ?10.50.50.200?) (spawk@64.147.100.2) by acm.poly.edu with CAMELLIA256-SHA encrypted SMTP; 17 Jun 2013 14:12:31 -0000 Message-ID: <51BF1948.7040105@acm.poly.edu> Date: Mon, 17 Jun 2013 10:12:24 -0400 From: Boris Kochergin User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/20130401 Thunderbird/17.0.4 MIME-Version: 1.0 To: Jack Vogel Subject: Re: Unsupported AFBR-700SDZ SFP+ module with 82598EB 10-Gigabit AF Dual Port Network Connection References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: "freebsd-net@freebsd.org" , =?ISO-8859-1?Q?=22Wei=DF=2C_J=FCrgen=22?= X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jun 2013 14:12:32 -0000 Cool. Any idea of when soon might be? And about that list of supported SFP+ modules? Is any Intel 10-GBASE-SR SFP+ module guaranteed to work with this card and driver? -Boris On 06/09/13 22:09, Jack Vogel wrote: > There will be a driver update soon with the way it should be done, it will > be in the core driver > code and not as here in the shared code. > > Regards, > > Jack > > PS Oh, and the email address should be 'freebsd@intel.com' now rather than > freebsdnic, it > still ultimately just gets to me however. > > > > On Sun, Jun 9, 2013 at 10:42 AM, Weiß, Jürgen wrote: > >> With the following patch the ixgbe (ix) driver >> accepts any SFP. >> >> >> --- ixgbe_phy.c.orig 2012-10-01 18:38:31.000000000 +0200 >> +++ ixgbe_phy.c 2012-11-13 16:23:18.650609931 +0100 >> @@ -1186,6 +1186,7 @@ >> } >> >> ixgbe_get_device_caps(hw, &enforce_sfp); >> + enforce_sfp |= IXGBE_DEVICE_CAPS_ALLOW_ANY_SFP; >> if (!(enforce_sfp & IXGBE_DEVICE_CAPS_ALLOW_ANY_SFP) && >> !((hw->phy.sfp_type == ixgbe_sfp_type_1g_cu_core0) || >> (hw->phy.sfp_type == ixgbe_sfp_type_1g_cu_core1) || >> >> >> Regards >> >> Juergen >> >> Juergen Weiss |Universitaet Mainz, Zentrum fuer Datenverarbeitung, >> weiss@uni-mainz.de |55099 Mainz, Tel: +49(6131)39-26361, FAX: >> +49(6131)39-26407 >> >> _______________________________________________ >> 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" >> > _______________________________________________ > 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 Jun 17 14:16:19 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4C991A28 for ; Mon, 17 Jun 2013 14:16:19 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: from acm.poly.edu (acm.poly.edu [64.147.113.26]) by mx1.freebsd.org (Postfix) with ESMTP id 2992D196F for ; Mon, 17 Jun 2013 14:16:19 +0000 (UTC) Received: from acm.poly.edu (localhost [127.0.0.1]) by acm.poly.edu (Postfix) with ESMTP id C67581F1349 for ; Mon, 17 Jun 2013 10:08:11 -0400 (EDT) Received: (qmail 63808 invoked from network); 17 Jun 2013 14:08:11 -0000 Received: from unknown (HELO ?10.50.50.200?) (spawk@64.147.100.2) by acm.poly.edu with CAMELLIA256-SHA encrypted SMTP; 17 Jun 2013 14:08:11 -0000 Message-ID: <51BF1843.30605@acm.poly.edu> Date: Mon, 17 Jun 2013 10:08:03 -0400 From: Boris Kochergin User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/20130401 Thunderbird/17.0.4 MIME-Version: 1.0 To: =?ISO-8859-1?Q?=22Wei=DF=2C_J=FCrgen=22?= Subject: Re: Unsupported AFBR-700SDZ SFP+ module with 82598EB 10-Gigabit AF Dual Port Network Connection References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: "'freebsd-net@freebsd.org'" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jun 2013 14:16:19 -0000 Thanks, but this does not work. ix0: port 0xece0-0xecff mem 0xdf360000-0xdf37ffff,0xdf3c0000-0xdf3fffff,0xdf33c000-0xdf33ffff irq 45 at device 0.1 on pci6 ix0: Using MSIX interrupts with 9 vectors ix0: Unsupported SFP+ Module ix0: Hardware Initialization Failure device_attach: ix0 attach returned 5 -Boris On 06/09/13 13:42, Weiß, Jürgen wrote: > With the following patch the ixgbe (ix) driver > accepts any SFP. > > > --- ixgbe_phy.c.orig 2012-10-01 18:38:31.000000000 +0200 > +++ ixgbe_phy.c 2012-11-13 16:23:18.650609931 +0100 > @@ -1186,6 +1186,7 @@ > } > > ixgbe_get_device_caps(hw, &enforce_sfp); > + enforce_sfp |= IXGBE_DEVICE_CAPS_ALLOW_ANY_SFP; > if (!(enforce_sfp & IXGBE_DEVICE_CAPS_ALLOW_ANY_SFP) && > !((hw->phy.sfp_type == ixgbe_sfp_type_1g_cu_core0) || > (hw->phy.sfp_type == ixgbe_sfp_type_1g_cu_core1) || > > > Regards > > Juergen > > Juergen Weiss |Universitaet Mainz, Zentrum fuer Datenverarbeitung, > weiss@uni-mainz.de |55099 Mainz, Tel: +49(6131)39-26361, FAX: +49(6131)39-26407 > From owner-freebsd-net@FreeBSD.ORG Mon Jun 17 18:50:17 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8B92B6F for ; Mon, 17 Jun 2013 18:50:17 +0000 (UTC) (envelope-from freebsd@mackn.org) Received: from mail-hosting.netagogo.com (mail-hosting.netagogo.com [64.62.244.187]) by mx1.freebsd.org (Postfix) with ESMTP id 76E5B1902 for ; Mon, 17 Jun 2013 18:50:17 +0000 (UTC) Received: by mail-hosting.netagogo.com (Postfix, from userid 65534) id 21EF74E73; Mon, 17 Jun 2013 11:44:48 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail-hosting.netagogo.com X-Spam-Level: X-Spam-Status: No, score=-1.5 required=6.0 tests=ALL_TRUSTED,BAYES_05 autolearn=ham version=3.3.2 Received: from mail-hosting.netagogo.com (unknown [10.10.10.187]) by mail-hosting.netagogo.com (Postfix) with ESMTP id 8EC474E7D for ; Mon, 17 Jun 2013 11:44:46 -0700 (PDT) Received: from [10.111.0.21] (67-215-87-12.ip.opendns.com [67.215.87.12]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail-hosting.netagogo.com (Postfix) with ESMTPSA id 6D51D4E75 for ; Mon, 17 Jun 2013 11:44:46 -0700 (PDT) Message-ID: <51BF591D.1050301@mackn.org> Date: Mon, 17 Jun 2013 11:44:45 -0700 From: Mack Nagashima User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Some routes no longer getting flagged with 'GATEWAY' in fbsd >=8 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jun 2013 18:50:17 -0000 we're in the process of upgrading from fbsd 7 to 9 and noticed a change in behavior that might be problematic for us. We use quagga to establish bgp sessions with a router. We have it set to redistribute kernel routes. Zebra seems to drop anything that doesn't have the 'GATEWAY' flag set on a route. Prior to fbsd8 this wasn't a problem. Doing something like the following worked fine in fbsd7: ifconfig em0 inet 192.168.100.1/24 ifconfig lo0 inet 192.168.100.100/24 alias route add -nostatic 192.168.100.100/32 192.168.100.1 in fbsd7 this would yield a route with the flags according to RTM_GET. in fbsd8+ the same would yield a route with without the GATEWAY flag. However the RTM_ADD for the 'route add' comes in with on fbsd8+ so quagga does add if it's up before the route gets added but starting quagga after the route is added ignores it since it's missing the GATEWAY flag once in the routing table. (route delete also fails to propagate to quagga since the GATEWAY flag is missing) I assume this is all due to the networking overhaul in fbsd8 and perhaps it no longer flags any route who's gateway is bound to ANY interface on the box as a gateway. So the ultimate question is.. is there a way to get the legacy behavior and get them flagged with GATEWAY so zebra will see them or a better solution with the way networking now works... (i noticed that issuing a 'route change' of an existing route with the GATEWAY flag set seems to work as it doesn't drop the flag when the gateway changes under it...) Thanks in advance! -mackn From owner-freebsd-net@FreeBSD.ORG Mon Jun 17 19:26:21 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8C64DA3D; Mon, 17 Jun 2013 19:26:21 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from plsvl-mailgw-02.bluecoat.com (plsvl-mailgw-02.bluecoat.com [199.91.133.12]) by mx1.freebsd.org (Postfix) with ESMTP id 6A0D91A75; Mon, 17 Jun 2013 19:26:21 +0000 (UTC) Received: from pwsvl-exchts-03.internal.cacheflow.com (pwsvl-exchts-03.bluecoat.com [10.2.2.160]) by plsvl-mailgw-02.bluecoat.com (Postfix) with ESMTP id A657420591; Mon, 17 Jun 2013 12:18:26 -0700 (PDT) Received: from PWSVL-EXCHTS-06.internal.cacheflow.com (10.2.2.166) by pwsvl-exchts-03.internal.cacheflow.com (10.2.2.160) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 17 Jun 2013 12:18:26 -0700 Received: from PWSVL-EXCMBX-02.internal.cacheflow.com ([fe80::81ba:dd3c:2f44:2eff]) by pwsvl-exchts-06.internal.cacheflow.com ([fe80::8554:761:8def:a2e1%12]) with mapi id 14.03.0123.003; Mon, 17 Jun 2013 12:18:26 -0700 From: "Li, Qing" To: Mack Nagashima , "freebsd-net@freebsd.org" Subject: RE: Some routes no longer getting flagged with 'GATEWAY' in fbsd >=8 Thread-Topic: Some routes no longer getting flagged with 'GATEWAY' in fbsd >=8 Thread-Index: AQHOa4uIH4lG6JKH1U+cypzkUhXiMJk6RqPB Date: Mon, 17 Jun 2013 19:18:25 +0000 Message-ID: References: <51BF591D.1050301@mackn.org> In-Reply-To: <51BF591D.1050301@mackn.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [199.91.133.85] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "qingli@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jun 2013 19:26:21 -0000 Hi,=0A= =0A= I tried to keep the route messages to be legacy compatible due to reported = =0A= breakage at the time. Let me revisit the code and get back to you.=0A= =0A= I haven't run the quagga code for years, so please don't mind me request=0A= some information from you offline.=0A= =0A= --Qing=0A= =0A= =0A= ________________________________________=0A= From: owner-freebsd-net@freebsd.org [owner-freebsd-net@freebsd.org] on beha= lf of Mack Nagashima [freebsd@mackn.org]=0A= Sent: Monday, June 17, 2013 11:44 AM=0A= To: freebsd-net@freebsd.org=0A= Subject: Some routes no longer getting flagged with 'GATEWAY' in fbsd >=3D8= =0A= =0A= we're in the process of upgrading from fbsd 7 to 9 and noticed a change=0A= in behavior that might be problematic for us.=0A= =0A= We use quagga to establish bgp sessions with a router. We have it set=0A= to redistribute kernel routes.=0A= Zebra seems to drop anything that doesn't have the 'GATEWAY' flag set on=0A= a route.=0A= =0A= Prior to fbsd8 this wasn't a problem. Doing something like the=0A= following worked fine in fbsd7:=0A= =0A= ifconfig em0 inet 192.168.100.1/24=0A= ifconfig lo0 inet 192.168.100.100/24 alias=0A= route add -nostatic 192.168.100.100/32 192.168.100.1=0A= =0A= in fbsd7 this would yield a route with the flags according=0A= to RTM_GET.=0A= in fbsd8+ the same would yield a route with without the GATEWAY flag.= =0A= =0A= However the RTM_ADD for the 'route add' comes in with =0A= on fbsd8+ so quagga does add if it's up before the route gets added but=0A= starting quagga after the route is added ignores it since it's missing=0A= the GATEWAY flag once in the routing table. (route delete also fails to=0A= propagate to quagga since the GATEWAY flag is missing)=0A= =0A= I assume this is all due to the networking overhaul in fbsd8 and perhaps=0A= it no longer flags any route who's gateway is bound to ANY interface on=0A= the box as a gateway.=0A= =0A= So the ultimate question is.. is there a way to get the legacy behavior=0A= and get them flagged with GATEWAY so zebra will see them or a better=0A= solution with the way networking now works... (i noticed that issuing a=0A= 'route change' of an existing route with the GATEWAY flag set seems to=0A= work as it doesn't drop the flag when the gateway changes under it...)=0A= =0A= Thanks in advance!=0A= =0A= -mackn=0A= =0A= _______________________________________________=0A= freebsd-net@freebsd.org mailing list=0A= http://lists.freebsd.org/mailman/listinfo/freebsd-net=0A= To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"=0A= From owner-freebsd-net@FreeBSD.ORG Mon Jun 17 20:37:48 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3E3185DB; Mon, 17 Jun 2013 20:37:48 +0000 (UTC) (envelope-from brian@freebsd.org) Received: from smtp-out-02.shaw.ca (smtp-out-02.shaw.ca [64.59.136.138]) by mx1.freebsd.org (Postfix) with ESMTP id F2F2D1E32; Mon, 17 Jun 2013 20:37:47 +0000 (UTC) X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.1 cv=YS95TUGYX+MRkNY/meip+CxRTyy2F4x7QGJ4HWfgHsg= c=1 sm=1 a=0Evk4HcnhGUA:10 a=dBRESv0yCI8A:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=Jvqgub9IZPV2TmRqH1mFPg==:17 a=P4JvR0-YAAAA:8 a=g0wtaXY6AAAA:8 a=6I5d2MoRAAAA:8 a=uYfCM8JhAAAA:8 a=MMwg4So0AAAA:8 a=VkI5GP1dgp3jts2Rwu8A:9 a=CjuIK1q_8ugA:10 a=DWS6ea1utk0A:10 a=SV7veod9ZcQA:10 a=2joWEaGdj38A:10 a=WJ3hkfHDukgA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 Received: from unknown (HELO gw.Awfulhak.org) ([174.7.169.46]) by smtp-out-02.shaw.ca with ESMTP; 17 Jun 2013 14:37:41 -0600 Received: from [10.10.11.20] ([96.53.48.10]) (authenticated bits=0) by gw.Awfulhak.org (8.14.7/8.14.7) with ESMTP id r5HKba0x061700 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 17 Jun 2013 13:37:37 -0700 (PDT) (envelope-from brian@FreeBSD.org) Subject: Re: Some routes no longer getting flagged with 'GATEWAY' in fbsd >=8 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Content-Type: text/plain; charset=us-ascii From: Brian Somers In-Reply-To: Date: Mon, 17 Jun 2013 13:37:36 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <5CD9527C-6B2E-42D9-A3F6-788522F6E14A@FreeBSD.org> References: <51BF591D.1050301@mackn.org> To: "Li, Qing" X-Mailer: Apple Mail (2.1508) X-Spam-Status: No, score=2.2 required=5.0 tests=RDNS_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on gw.lan.Awfulhak.org Cc: "freebsd-net@freebsd.org" , Mack Nagashima , "qingli@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jun 2013 20:37:48 -0000 Also relevant is this patch.... http://patchwork.diac24.net/patch/494/mbox/ I guess it seems like more of a workaround than a fix though. On Jun 17, 2013, at 12:18 PM, "Li, Qing" wrote: > Hi, >=20 > I tried to keep the route messages to be legacy compatible due to = reported=20 > breakage at the time. Let me revisit the code and get back to you. >=20 > I haven't run the quagga code for years, so please don't mind me = request > some information from you offline. >=20 > --Qing >=20 >=20 > ________________________________________ > From: owner-freebsd-net@freebsd.org [owner-freebsd-net@freebsd.org] on = behalf of Mack Nagashima [freebsd@mackn.org] > Sent: Monday, June 17, 2013 11:44 AM > To: freebsd-net@freebsd.org > Subject: Some routes no longer getting flagged with 'GATEWAY' in fbsd = >=3D8 >=20 > we're in the process of upgrading from fbsd 7 to 9 and noticed a = change > in behavior that might be problematic for us. >=20 > We use quagga to establish bgp sessions with a router. We have it set > to redistribute kernel routes. > Zebra seems to drop anything that doesn't have the 'GATEWAY' flag set = on > a route. >=20 > Prior to fbsd8 this wasn't a problem. Doing something like the > following worked fine in fbsd7: >=20 > ifconfig em0 inet 192.168.100.1/24 > ifconfig lo0 inet 192.168.100.100/24 alias > route add -nostatic 192.168.100.100/32 192.168.100.1 >=20 > in fbsd7 this would yield a route with the flags = according > to RTM_GET. > in fbsd8+ the same would yield a route with without the GATEWAY = flag. >=20 > However the RTM_ADD for the 'route add' comes in with = > on fbsd8+ so quagga does add if it's up before the route gets added = but > starting quagga after the route is added ignores it since it's missing > the GATEWAY flag once in the routing table. (route delete also fails = to > propagate to quagga since the GATEWAY flag is missing) >=20 > I assume this is all due to the networking overhaul in fbsd8 and = perhaps > it no longer flags any route who's gateway is bound to ANY interface = on > the box as a gateway. >=20 > So the ultimate question is.. is there a way to get the legacy = behavior > and get them flagged with GATEWAY so zebra will see them or a better > solution with the way networking now works... (i noticed that issuing = a > 'route change' of an existing route with the GATEWAY flag set seems to > work as it doesn't drop the flag when the gateway changes under it...) >=20 > Thanks in advance! >=20 > -mackn >=20 -- Brian Somers = Don't _EVER_ lose your sense of humour ! = From owner-freebsd-net@FreeBSD.ORG Mon Jun 17 23:57:10 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 354D5D81; Mon, 17 Jun 2013 23:57:10 +0000 (UTC) (envelope-from lists@rewt.org.uk) Received: from hosted.mx.as41113.net (hosted.mx.as41113.net [91.208.177.22]) by mx1.freebsd.org (Postfix) with ESMTP id F2CB81895; Mon, 17 Jun 2013 23:57:09 +0000 (UTC) Received: from [172.16.9.23] (bella.stf.rewt.org.uk [91.208.177.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: lists@rewt.org.uk) by hosted.mx.as41113.net (Postfix) with ESMTPSA id 3bZ8V62RTLz6d; Tue, 18 Jun 2013 00:57:01 +0100 (BST) Message-ID: <51BFA24D.70705@rewt.org.uk> Date: Tue, 18 Jun 2013 00:57:01 +0100 From: Joe Holden User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Jason Hellenthal Subject: Re: How not allow setting ip changes interface down status? References: <69CF1AAF-230D-4B2B-9C95-20DDD772997E@dataix.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: h bagade , "freebsd-net@freebsd.org" , Adrian Chadd , Jack Vogel X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jun 2013 23:57:10 -0000 Jason Hellenthal wrote: > Off the top of my head I don't know of another OS that does this. > > But yes agreed changing that behavior would probably effect a lot of people in a negative way at this point. > > Not to mention script breakage. > > But a tunable in the stack somewhere would be awesome to change this behavior. Either interface specific or global or both. > > Sometimes installing a new faucet you don't want the water to run until all the nuts, bolts and washers are installed. > The entire notion is ridiculous, it is quite simple - if the interface is down, it isn't in the FIB, you can't arbitarily return an error for setting an IP on an interface that isn't up. The last thing we need is yet more nonsense stack changes, allowing 0/8 to be used was bad enough. From owner-freebsd-net@FreeBSD.ORG Tue Jun 18 08:17:00 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 935AF7C3; Tue, 18 Jun 2013 08:17:00 +0000 (UTC) (envelope-from carlopmart@gmail.com) Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by mx1.freebsd.org (Postfix) with ESMTP id 04B7B1484; Tue, 18 Jun 2013 08:16:59 +0000 (UTC) Received: by mail-we0-f180.google.com with SMTP id w56so3158940wes.11 for ; Tue, 18 Jun 2013 01:16:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ld1hquJ7QDMPajlJft4e8HYwEY8FrrCopiZ4uzeLD2g=; b=sLscnv3/5HcjWguTUfrpzfen2UQC8TyX1LsyjnGerk/sz4p1MCyyC2xWg9uBuJNM6Z 5TuRlqiwdKqxKLgf4hAMTAFIF8Inb30zYa+pKA9kHG3wP652IsI/4xjQNxNZqANaVs3w u+5wMY3mJiHuRR1GzbXzW2APf7dZT6xK9wf6NqQ4TpItaqiYq006x9M+EUQIIymzKi01 6GQjb0iVsAhevRvhl2KcFdnLNP0EdrR7e5pFRH7LP+2ADnpMNvSyMuV6bFhUOQRXic0w SbZyqH7ZBacfQNZ3dAq9yBKgfdyYObzVfgHVumYNvhZ4fRLu8CDL8JDtYn5pzp8gPA0M P5xQ== MIME-Version: 1.0 X-Received: by 10.180.74.162 with SMTP id u2mr1215919wiv.36.1371543418981; Tue, 18 Jun 2013 01:16:58 -0700 (PDT) Received: by 10.194.76.178 with HTTP; Tue, 18 Jun 2013 01:16:58 -0700 (PDT) In-Reply-To: References: Date: Tue, 18 Jun 2013 08:16:58 +0000 Message-ID: Subject: Fwd: Avoid sharing interrupts in FreeBSD under ESXi From: "C. L. Martinez" To: freebsd-net@freebsd.org, freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jun 2013 08:17:00 -0000 Hi all, First, sorry for the cross-posting. I have installed a FreeBSD 8.4 vm under an ESXi 5.1 U1 server. All works ok, except for interrupt usage between mpt and nic interfaces: root@fbsdtst:~ # vmstat -i interrupt total rate irq1: atkbd0 6 0 irq6: fdc0 9 0 irq16: em2 mpt2 945924 1 irq17: em3 em6 2124484 4 irq18: em0 em4 em7+ 5950584 11 irq19: em1 em5 em8+ 2317830055 4499 cpu0: timer 206119496 400 Total 2532970558 4916 I have enabled the following options in loader.conf: hw.pci.enable_msi="0" hw.pci.enable_msix="0" without a result. Is it possible to avoid to share interrupts in FreeBSD when it is running as a vm? Exists some kernel option to resolve this (via sysctl or compiling a new kernel)? Thanks. From owner-freebsd-net@FreeBSD.ORG Tue Jun 18 09:06:44 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1DBCF97C; Tue, 18 Jun 2013 09:06:44 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x22f.google.com (mail-qa0-x22f.google.com [IPv6:2607:f8b0:400d:c00::22f]) by mx1.freebsd.org (Postfix) with ESMTP id C2BA518DC; Tue, 18 Jun 2013 09:06:43 +0000 (UTC) Received: by mail-qa0-f47.google.com with SMTP id i13so2026910qae.20 for ; Tue, 18 Jun 2013 02:06:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=GTdZLZEzqwc7fsPifKGadSbEkr/gkI1EfxHpyWbN+pI=; b=rUck29GubBrzrFoSTTSTu0evkvCs3C1WCP3GERpicWz2MLYA4fI9+hastvjb9sdhzV 7MIZ+jo8c2JAESZIb5DEMvZOGDuHxswHo/EPEE75eEqSi2rNPEGKHAs8GuXX+9Va1rF+ 7FR2lJ+umHceUeR+2FJMSfrLP1XjqZZmTR72NoiX8hEFjjUCUQrmMf5U2SEDW1M6k17s x3soDD1P6CDh/CTbv25wcFDJyOIXT/drq2dUX7TnrMPUHSi6sUmhOi/4Tu+S7S6qMPfx oa8/dU+IUsb7oSMY4bcPmsDd2ndz7NzwouiPcfRGLYfJjC+IOQ1PV0AkPyPbIsD+r7+w +zaw== MIME-Version: 1.0 X-Received: by 10.224.11.6 with SMTP id r6mr1726794qar.65.1371546403280; Tue, 18 Jun 2013 02:06:43 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.5.65 with HTTP; Tue, 18 Jun 2013 02:06:43 -0700 (PDT) In-Reply-To: References: Date: Tue, 18 Jun 2013 02:06:43 -0700 X-Google-Sender-Auth: tLcwrgLzkx_NScEasQHEBV2cIIs Message-ID: Subject: Re: Avoid sharing interrupts in FreeBSD under ESXi From: Adrian Chadd To: "C. L. Martinez" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org, freebsd-virtualization@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jun 2013 09:06:44 -0000 ... you mean if mpt and em share an interrupt, things get wedged? adrian On 18 June 2013 01:16, C. L. Martinez wrote: > Hi all, > > First, sorry for the cross-posting. > > I have installed a FreeBSD 8.4 vm under an ESXi 5.1 U1 server. All > works ok, except for interrupt usage between mpt and nic interfaces: > > root@fbsdtst:~ # vmstat -i > interrupt total rate > irq1: atkbd0 6 0 > irq6: fdc0 9 0 > irq16: em2 mpt2 945924 1 > irq17: em3 em6 2124484 4 > irq18: em0 em4 em7+ 5950584 11 > irq19: em1 em5 em8+ 2317830055 4499 > cpu0: timer 206119496 400 > Total 2532970558 4916 > > I have enabled the following options in loader.conf: > > hw.pci.enable_msi="0" > hw.pci.enable_msix="0" > > without a result. Is it possible to avoid to share interrupts in > FreeBSD when it is running as a vm? Exists some kernel option to > resolve this (via sysctl or compiling a new kernel)? > > Thanks. > _______________________________________________ > 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 Jun 18 09:09:23 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 217B9A78; Tue, 18 Jun 2013 09:09:23 +0000 (UTC) (envelope-from carlopmart@gmail.com) Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) by mx1.freebsd.org (Postfix) with ESMTP id 5BE181907; Tue, 18 Jun 2013 09:09:22 +0000 (UTC) Received: by mail-wg0-f52.google.com with SMTP id b12so3245767wgh.7 for ; Tue, 18 Jun 2013 02:09:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hV9RBcBMeIgnxMog6pdMpQtzCMdoSemu+1AE1Or+FdI=; b=FRkiPWqm8XWlfR+wh9Bg3VmyuR0anK/2UjX9xtiNqzwvkTxd1XBWrMzXLu2jptTv7D N3Wh7DNxp0OgnPjEFES38rpPFzLHECwXqFKps5LpaEyGdN6+G3YJBqdej9LMpeh9vTvD dr8P4QgIZCelx6VWxGZ2pXVzuRSXW2/hretZFpi+mcOZoD6x4NoV8sRIm1E8Af4KLz1K oikua7LeREvjssnWwZqEm0eiiNrVCtUfTeXyGAaGT/jAPYpDVYretcWU25C3gaROVigE 9T8Mn6pq1c2FXMdEEaIhfaHYxNBO4LbRkcIYdpImQtZRjA2lj6JNvLJd2G8a8WgrwMy4 ukJQ== MIME-Version: 1.0 X-Received: by 10.180.100.35 with SMTP id ev3mr7070627wib.12.1371546561389; Tue, 18 Jun 2013 02:09:21 -0700 (PDT) Received: by 10.194.76.178 with HTTP; Tue, 18 Jun 2013 02:09:21 -0700 (PDT) In-Reply-To: References: Date: Tue, 18 Jun 2013 09:09:21 +0000 Message-ID: Subject: Re: Avoid sharing interrupts in FreeBSD under ESXi From: "C. L. Martinez" To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Cc: freebsd-net@freebsd.org, freebsd-virtualization@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jun 2013 09:09:23 -0000 On Tue, Jun 18, 2013 at 9:06 AM, Adrian Chadd wrote: > ... you mean if mpt and em share an interrupt, things get wedged? > > > > adrian > Yes. From owner-freebsd-net@FreeBSD.ORG Tue Jun 18 09:15:41 2013 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C8707CF0; Tue, 18 Jun 2013 09:15:41 +0000 (UTC) (envelope-from egrosbein@rdtc.ru) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [IPv6:2a03:3100:c:13::5]) by mx1.freebsd.org (Postfix) with ESMTP id 17BF71972; Tue, 18 Jun 2013 09:15:40 +0000 (UTC) Received: from eg.sd.rdtc.ru (localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.14.7/8.14.7) with ESMTP id r5I9FaYx009430; Tue, 18 Jun 2013 16:15:36 +0700 (NOVT) (envelope-from egrosbein@rdtc.ru) Message-ID: <51C02533.1070206@rdtc.ru> Date: Tue, 18 Jun 2013 16:15:31 +0700 From: Eugene Grosbein User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130415 Thunderbird/17.0.5 MIME-Version: 1.0 To: "net@freebsd.org" , Jack Vogel , luigi@freebsd.org Subject: em(4) & DEFAULT_ITR Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jun 2013 09:15:41 -0000 Hi! em(4) driver got new sysctl for 'itr' moderation register recently in head and stable/9. Previously, it used the macro DEFAULT_ITR for it. It seems for me, however, revision 250414 that brought this new feature was quite incomplete: driver still uses DEFAULT_ITR macro instead of sysctl value in the em_initialize_receive_unit() function. Isn't it a bug? And there is no loader tunable like in igb(4) to make a default to eliminate a need of extra reset of each adapter at sysctl time. And it is more convenient to set it in terms of "maximum interrupt per second" than as 'usec/4' unit timeouts, please :-) Eugene Grosbein From owner-freebsd-net@FreeBSD.ORG Tue Jun 18 11:40:01 2013 Return-Path: Delivered-To: freebsd-net@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8DCD2F11 for ; Tue, 18 Jun 2013 11:40:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 7FF5711AA for ; Tue, 18 Jun 2013 11:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r5IBe1Gd051742 for ; Tue, 18 Jun 2013 11:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5IBe1Od051741; Tue, 18 Jun 2013 11:40:01 GMT (envelope-from gnats) Date: Tue, 18 Jun 2013 11:40:01 GMT Message-Id: <201306181140.r5IBe1Od051741@freefall.freebsd.org> To: freebsd-net@FreeBSD.org Cc: From: Sergey Maltsev Subject: Re: kern/178612: [run] kernel panic due the problems with run driver X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Sergey Maltsev List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jun 2013 11:40:01 -0000 The following reply was made to PR kern/178612; it has been noted by GNATS. From: Sergey Maltsev To: bug-followup@FreeBSD.org, core.dumped.sm@gmail.com Cc: Subject: Re: kern/178612: [run] kernel panic due the problems with run driver Date: Tue, 18 Jun 2013 17:39:47 +0600 --089e016814549dc64f04df6c2b69 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Major upgrade for a system with a set number of ports around 2k is not acceptable for me. I updated system to the last release - 8.4, =C1nd replaced system files on similar of the link: http://svnweb.freebsd.org/base?view=3Drevision&revision=3D218676 Unfortunately compilation of a kernel ends with error: =3D=3D=3D> usb/run (all) cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/SERGIO/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=3D8000 --param inline-unit-growth=3D100 --param large-function-growth=3D1000 -fno-common -g -I/usr/obj/usr/src/sys/SERGIO -mno-align-long-strings -mpreferred-stack-boundary=3D2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -std=3Diso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /usr/src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c /usr/src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:77:1: error: "nitems" redefined In file included from /usr/src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:27: @/sys/param.h:274:1: error: this is the location of the previous definition *** Error code 1 Stop in /usr/src/sys/modules/usb/run. *** Error code 1 Stop in /usr/src/sys/modules/usb. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/SERGIO. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --089e016814549dc64f04df6c2b69 Content-Type: text/html; charset=KOI8-R Content-Transfer-Encoding: quoted-printable
Major upgrade for a system with a set number of ports arou= nd 2k is not acceptable for me.
I updated system to the last release - 8= .4, =C1nd replaced system files on similar of the link:
http://svnweb.freebsd.org/base?view=3Drevision&revision=3D21867= 6
Unfortunately compilation of a kernel ends with error:

=3D=3D=3D>= usb/run (all)
cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD= _MODULE -nostdinc=9A=9A -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/= src/sys/SERGIO/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=3D8000 = --param inline-unit-growth=3D100 --param large-function-growth=3D1000 -fno-= common -g -I/usr/obj/usr/src/sys/SERGIO -mno-align-long-strings -mpreferred= -stack-boundary=3D2=9A -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ff= reestanding -fstack-protector -std=3Diso9899:1999 -fstack-protector -Wall -= Wredundant-decls -Wnested-externs -Wstrict-prototypes=9A -Wmissing-prototyp= es -Wpointer-arith -Winline -Wcast-qual=9A -Wundef -Wno-pointer-sign -fform= at-extensions -c /usr/src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.= c
/usr/src/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:77:1: error: &q= uot;nitems" redefined
In file included from /usr/src/sys/modules/us= b/run/../../../dev/usb/wlan/if_run.c:27:
@/sys/param.h:274:1: error: thi= s is the location of the previous definition
*** Error code 1

Stop in /usr/src/sys/modules/usb/run.
*** Error = code 1

Stop in /usr/src/sys/modules/usb.
*** Error code 1

= Stop in /usr/src/sys/modules.
*** Error code 1

Stop in /usr/obj/u= sr/src/sys/SERGIO.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop i= n /usr/src.


--089e016814549dc64f04df6c2b69-- From owner-freebsd-net@FreeBSD.ORG Tue Jun 18 11:44:26 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B0F661A7 for ; Tue, 18 Jun 2013 11:44:26 +0000 (UTC) (envelope-from ferlin@simula.no) Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) by mx1.freebsd.org (Postfix) with ESMTP id 8984A11FC for ; Tue, 18 Jun 2013 11:44:26 +0000 (UTC) Received: by mail-ie0-f171.google.com with SMTP id qd12so9802675ieb.16 for ; Tue, 18 Jun 2013 04:44:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=yr5xG0lru+j0eW93GzQ6sSMJ7Q8Sc77bGpQEZBDMAbk=; b=W0wsyJnnu/w6pz9lHlM/TcBFMC37i6FVm951ZMSyGJiQNyJNnSdFH/JW9MtLvge86+ C+sM/LhDBmuvq57JFXQlxTHpMOsetQ/iaDMXjtbRoOUzBjADs7jj+/Q46eS31CSDsw1E l9oTF+mNsrkddZE4T17YOTY1TQADsIU//rViclh5XTOR0yFr9NzuHBp1wLAYbgD0GpP9 bHozSb+VurERWduNJJImddUjtjbCgrmMTywMOvhnIc8+SiesNX9MdFYG07823t62OX9L EtUtXBfQn0qbgJf+F6xkKSKzc+1lartTVjqlzTKCi1GUnMdrMe8D/bF+FgFacZKyCzGW C30g== MIME-Version: 1.0 X-Received: by 10.50.114.161 with SMTP id jh1mr7527598igb.112.1371555866216; Tue, 18 Jun 2013 04:44:26 -0700 (PDT) Received: by 10.50.73.231 with HTTP; Tue, 18 Jun 2013 04:44:26 -0700 (PDT) Date: Tue, 18 Jun 2013 13:44:26 +0200 Message-ID: Subject: FreeBSD 9.1 on arm From: Simone Ferlin-Oliveira To: freebsd-net@freebsd.org X-Gm-Message-State: ALoCoQkdpqFiHv/YfynN/0qXcSK67zwvxyxHb67CNVPK/u7x80Xbt7das87ZC3eJZy3nJ+lybLFN Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jun 2013 11:44:26 -0000 Hi, I will start with the process of bringing FreeBSD 9.1 (mainly because of CMT-SCTP) for a single-board customized board (S5PV210), and I would like to ask whether somebody has some experience doing it to share. I will work on these board using usb modems, so could it be something (driver) missing? Could it work at all? Thanks for any input, Simone From owner-freebsd-net@FreeBSD.ORG Tue Jun 18 15:49:55 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 02A2F272 for ; Tue, 18 Jun 2013 15:49:55 +0000 (UTC) (envelope-from Michael.Tuexen@lurchi.franken.de) Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by mx1.freebsd.org (Postfix) with ESMTP id 917B012AE for ; Tue, 18 Jun 2013 15:49:54 +0000 (UTC) Received: from [10.225.6.32] (unknown [194.95.73.101]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 9F9BA1C0C069C; Tue, 18 Jun 2013 17:49:50 +0200 (CEST) Subject: Re: FreeBSD 9.1 on arm Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Michael Tuexen In-Reply-To: Date: Tue, 18 Jun 2013 17:49:50 +0200 Content-Transfer-Encoding: 7bit Message-Id: References: To: Simone Ferlin-Oliveira X-Mailer: Apple Mail (2.1283) Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jun 2013 15:49:55 -0000 On Jun 18, 2013, at 1:44 PM, Simone Ferlin-Oliveira wrote: > Hi, > > I will start with the process of bringing FreeBSD 9.1 (mainly because of > CMT-SCTP) for a single-board customized board (S5PV210), and I would like > to ask whether somebody has some experience doing it to share. > I will work on these board using usb modems, so could it be something > (driver) missing? Could it work at all? Is your board supported by FreeBSD 9.1? I'm running FreeBSD head with SCTP on a Raspberry Pi without problems. So SCTP should work on arm. Best regards Michael > > Thanks for any input, > Simone > _______________________________________________ > 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 Jun 18 21:00:01 2013 Return-Path: Delivered-To: freebsd-net@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AAC02F99 for ; Tue, 18 Jun 2013 21:00:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 832B912C4 for ; Tue, 18 Jun 2013 21:00:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r5IL01r8082321 for ; Tue, 18 Jun 2013 21:00:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5IL01xS082320; Tue, 18 Jun 2013 21:00:01 GMT (envelope-from gnats) Date: Tue, 18 Jun 2013 21:00:01 GMT Message-Id: <201306182100.r5IL01xS082320@freefall.freebsd.org> To: freebsd-net@FreeBSD.org Cc: From: PseudoCylon Subject: Re: kern/178612: [run] kernel panic due the problems with run driver X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: PseudoCylon List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jun 2013 21:00:01 -0000 The following reply was made to PR kern/178612; it has been noted by GNATS. From: PseudoCylon To: bug-followup@FreeBSD.org, core.dumped.sm@gmail.com Cc: Subject: Re: kern/178612: [run] kernel panic due the problems with run driver Date: Tue, 18 Jun 2013 14:53:02 -0600 Try removing the line 77 in if_run.c Since r236486, nitimes() is defined in sys/param.h AK From owner-freebsd-net@FreeBSD.ORG Wed Jun 19 00:17:05 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F178F842 for ; Wed, 19 Jun 2013 00:17:05 +0000 (UTC) (envelope-from havenster@gmail.com) Received: from mail-pb0-x234.google.com (mail-pb0-x234.google.com [IPv6:2607:f8b0:400e:c01::234]) by mx1.freebsd.org (Postfix) with ESMTP id CF89C1D3B for ; Wed, 19 Jun 2013 00:17:05 +0000 (UTC) Received: by mail-pb0-f52.google.com with SMTP id xa12so4403847pbc.25 for ; Tue, 18 Jun 2013 17:17:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=NO9jUIHbuoWzZEKexTODXieh63+pNULouL+16J2P3og=; b=YbjgU1kTgYr8gKZOIYY8en6JRz4x2FdWwsBHGvZqJQPGV9V4xee/+Yk7xqmxTW6kAy iK/X0HZjunahtvVHPzxE92r16bCcvpHBKFSx/SISPd+vbKEbCnRCHEOyMhmTifb9zrwN EdT+W3kgjq39Y+zu1qtQw4z1S144HyX3D0ilREEeWCpCtheU9yj7vLe4lcoNLzMfZwwZ vYalZzmjqFC9jqePZ80wHfp838fxGV5srl50VaTzt9W2Na8U8W8aMdaUFmhOWWNi5wPM AQ3EAAGPE1r+HMtqQi8BDiEzF06/n4rRzo/oFNKhR5TX+B5btGwrEfJoxOpIsZVvLEJ5 o/Qw== MIME-Version: 1.0 X-Received: by 10.66.26.231 with SMTP id o7mr4090263pag.207.1371600724782; Tue, 18 Jun 2013 17:12:04 -0700 (PDT) Received: by 10.70.46.106 with HTTP; Tue, 18 Jun 2013 17:12:04 -0700 (PDT) In-Reply-To: <51BF1843.30605@acm.poly.edu> References: <51BF1843.30605@acm.poly.edu> Date: Tue, 18 Jun 2013 17:12:04 -0700 Message-ID: Subject: Re: Unsupported AFBR-700SDZ SFP+ module with 82598EB 10-Gigabit AF Dual Port Network Connection From: Haven Hash To: Boris Kochergin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-net@freebsd.org" , =?ISO-8859-1?B?V2Vp3ywgSvxyZ2Vu?= X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 19 Jun 2013 00:17:06 -0000 I believe there are two checks, one for Intel specific SFP modules (as some cards have their EEPROM's configured to only accept Intel branded optics), which this patch deals with, and another separate check for supported SFP's which is not addressed by this. Support SFP's include adapters from Finisar and a few other vendors, there's probably a list somewhere, but it does not include various types of Twinax cable (which will work if you load the driver then insert the cable, but the driver will refuse to create the interfaces if the cable is plugged in at the time it loads). I believe Jack is going to try and make these checks optional sometime in the future so you can try and use any SFP like with the Chelsio cards. On Mon, Jun 17, 2013 at 7:08 AM, Boris Kochergin wrote= : > Thanks, but this does not work. > > ix0: > port 0xece0-0xecff mem > 0xdf360000-0xdf37ffff,0xdf3c0000-0xdf3fffff,0xdf33c000-0xdf33ffff irq 45 > at device 0.1 on pci6 > ix0: Using MSIX interrupts with 9 vectors > ix0: Unsupported SFP+ Module > ix0: Hardware Initialization Failure > device_attach: ix0 attach returned 5 > > -Boris > > On 06/09/13 13:42, Wei=DF, J=FCrgen wrote: > > With the following patch the ixgbe (ix) driver > > accepts any SFP. > > > > > > --- ixgbe_phy.c.orig 2012-10-01 18:38:31.000000000 +0200 > > +++ ixgbe_phy.c 2012-11-13 16:23:18.650609931 +0100 > > @@ -1186,6 +1186,7 @@ > > } > > > > ixgbe_get_device_caps(hw, &enforce_sfp); > > + enforce_sfp |=3D IXGBE_DEVICE_CAPS_ALLOW_ANY_SFP; > > if (!(enforce_sfp & IXGBE_DEVICE_CAPS_ALLOW_ANY_SFP) && > > !((hw->phy.sfp_type =3D=3D ixgbe_sfp_type_1g_cu_cor= e0) || > > (hw->phy.sfp_type =3D=3D ixgbe_sfp_type_1g_cu_cor= e1) || > > > > > > Regards > > > > Juergen > > > > Juergen Weiss |Universitaet Mainz, Zentrum fuer Datenverarbeitung, > > weiss@uni-mainz.de |55099 Mainz, Tel: +49(6131)39-26361, FAX: > +49(6131)39-26407 > > > _______________________________________________ > 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 Jun 19 05:55:44 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 85698DCC for ; Wed, 19 Jun 2013 05:55:44 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-ve0-x230.google.com (mail-ve0-x230.google.com [IPv6:2607:f8b0:400c:c01::230]) by mx1.freebsd.org (Postfix) with ESMTP id 436A01B18 for ; Wed, 19 Jun 2013 05:55:44 +0000 (UTC) Received: by mail-ve0-f176.google.com with SMTP id c13so3757888vea.35 for ; Tue, 18 Jun 2013 22:55:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JeHqhEBIbDYRorHnvhNMWJD+k0dohMMZaLHOCflfbCw=; b=BO1Lr+7BgD8aB+6KOaEPqvGhkEu7F9UfPAo+1iKqRHVkhytLB/Cw1C9hnmSEG7sGJQ 1bdpZmBEzkSTtOpe0AwWxL2VYkvE4RtcxBAl71I/PPsWCzjIlPxRCleFmUr9Lzx6UKAa ifRk0Ir85BmrRTjPeSXcoF13lfCorNIqYQdbuPpUVSL3XUUH8pNlxf/7xw0KU7R3KY/o VsgLLzvisaCeTzmcjDfSqtrC+PEuxDTKE3sHufSXvcy1mekKYZ1+fZBj+XOKFzAIPn9I i/CawDw3/eIWcqfk9T2FAHjzQnCLr+KU290VmaDA1NTffQhvOkY9IFpuCGlZQJzLI0b3 Gp0w== MIME-Version: 1.0 X-Received: by 10.220.159.208 with SMTP id k16mr155494vcx.92.1371621343662; Tue, 18 Jun 2013 22:55:43 -0700 (PDT) Received: by 10.220.52.200 with HTTP; Tue, 18 Jun 2013 22:55:43 -0700 (PDT) In-Reply-To: References: <51BF1843.30605@acm.poly.edu> Date: Tue, 18 Jun 2013 22:55:43 -0700 Message-ID: Subject: Re: Unsupported AFBR-700SDZ SFP+ module with 82598EB 10-Gigabit AF Dual Port Network Connection From: Jack Vogel To: Haven Hash Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-net@freebsd.org" , =?ISO-8859-1?B?V2Vp3ywgSvxyZ2Vu?= , Boris Kochergin X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 19 Jun 2013 05:55:44 -0000 A new version of ixgbe was committed this afternoon, 2.5.13, it now has a compile-time option of using unsupported optics. Keep in mind that if you have issues I'm going to ask if it can be reproduced with supported optics as a first step :) Cheers, Jack On Tue, Jun 18, 2013 at 5:12 PM, Haven Hash wrote: > I believe there are two checks, one for Intel specific SFP modules (as so= me > cards have their EEPROM's configured to only accept Intel branded optics)= , > which this patch deals with, and another separate check for supported SFP= 's > which is not addressed by this. Support SFP's include adapters from Finis= ar > and a few other vendors, there's probably a list somewhere, but it does n= ot > include various types of Twinax cable (which will work if you load the > driver then insert the cable, but the driver will refuse to create the > interfaces if the cable is plugged in at the time it loads). > > I believe Jack is going to try and make these checks optional sometime in > the future so you can try and use any SFP like with the Chelsio cards. > > > On Mon, Jun 17, 2013 at 7:08 AM, Boris Kochergin > wrote: > > > Thanks, but this does not work. > > > > ix0: > > port 0xece0-0xecff mem > > 0xdf360000-0xdf37ffff,0xdf3c0000-0xdf3fffff,0xdf33c000-0xdf33ffff irq 4= 5 > > at device 0.1 on pci6 > > ix0: Using MSIX interrupts with 9 vectors > > ix0: Unsupported SFP+ Module > > ix0: Hardware Initialization Failure > > device_attach: ix0 attach returned 5 > > > > -Boris > > > > On 06/09/13 13:42, Wei=DF, J=FCrgen wrote: > > > With the following patch the ixgbe (ix) driver > > > accepts any SFP. > > > > > > > > > --- ixgbe_phy.c.orig 2012-10-01 18:38:31.000000000 +0200 > > > +++ ixgbe_phy.c 2012-11-13 16:23:18.650609931 +0100 > > > @@ -1186,6 +1186,7 @@ > > > } > > > > > > ixgbe_get_device_caps(hw, &enforce_sfp); > > > + enforce_sfp |=3D IXGBE_DEVICE_CAPS_ALLOW_ANY_SFP; > > > if (!(enforce_sfp & IXGBE_DEVICE_CAPS_ALLOW_ANY_SFP) = && > > > !((hw->phy.sfp_type =3D=3D ixgbe_sfp_type_1g_cu_c= ore0) > || > > > (hw->phy.sfp_type =3D=3D ixgbe_sfp_type_1g_cu_c= ore1) > || > > > > > > > > > Regards > > > > > > Juergen > > > > > > Juergen Weiss |Universitaet Mainz, Zentrum fuer Datenverarbeitun= g, > > > weiss@uni-mainz.de |55099 Mainz, Tel: +49(6131)39-26361, FAX: > > +49(6131)39-26407 > > > > > _______________________________________________ > > 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" > > > _______________________________________________ > 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 Jun 19 10:50:01 2013 Return-Path: Delivered-To: freebsd-net@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 58B43DD3 for ; Wed, 19 Jun 2013 10:50:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 4A82F1877 for ; Wed, 19 Jun 2013 10:50:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r5JAo0wG086861 for ; Wed, 19 Jun 2013 10:50:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5JAo0ap086846; Wed, 19 Jun 2013 10:50:00 GMT (envelope-from gnats) Date: Wed, 19 Jun 2013 10:50:00 GMT Message-Id: <201306191050.r5JAo0ap086846@freefall.freebsd.org> To: freebsd-net@FreeBSD.org Cc: From: Sergey Maltsev Subject: Re: kern/178612: [run] kernel panic due the problems with run driver X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Sergey Maltsev List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jun 2013 10:50:01 -0000 The following reply was made to PR kern/178612; it has been noted by GNATS. From: Sergey Maltsev To: PseudoCylon Cc: bug-followup@freebsd.org Subject: Re: kern/178612: [run] kernel panic due the problems with run driver Date: Wed, 19 Jun 2013 16:49:38 +0600 --001a1133d77e0e250c04df7f965c Content-Type: text/plain; charset=ISO-8859-1 The build kernel was completed. Thanks! Will wait for a panic. 2013/6/19 PseudoCylon > Try removing the line 77 in if_run.c > > Since r236486, nitimes() is defined in sys/param.h > > > AK > --001a1133d77e0e250c04df7f965c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
The build kernel was completed. Thanks!
Will wait for a= panic.


2013/6/19 PseudoCylon <moonlightakkiy@yahoo.ca>
Try removing the line 77 in if_run.c

Since r236486, nitimes() is defined in sys/param.h


AK

--001a1133d77e0e250c04df7f965c-- From owner-freebsd-net@FreeBSD.ORG Wed Jun 19 21:01:23 2013 Return-Path: Delivered-To: freebsd-net@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D66F5E21; Wed, 19 Jun 2013 21:01:23 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id B12461E9D; Wed, 19 Jun 2013 21:01:23 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r5JL1N3L009483; Wed, 19 Jun 2013 21:01:23 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5JL1NIm009482; Wed, 19 Jun 2013 21:01:23 GMT (envelope-from linimon) Date: Wed, 19 Jun 2013 21:01:23 GMT Message-Id: <201306192101.r5JL1NIm009482@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/179733: [lagg] [patch] interface loses capabilities when protocol changes X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 19 Jun 2013 21:01:23 -0000 Old Synopsis: [lagg] interface loses capabilities when protocol changes New Synopsis: [lagg] [patch] interface loses capabilities when protocol changes Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Wed Jun 19 21:00:53 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=179733 From owner-freebsd-net@FreeBSD.ORG Thu Jun 20 10:34:54 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 7BC596D for ; Thu, 20 Jun 2013 10:34:54 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by mx1.freebsd.org (Postfix) with ESMTP id 68C2A1B3B for ; Thu, 20 Jun 2013 10:34:54 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.87,904,1363158000"; d="scan'208";a="66762209" Received: from vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) by mx12-out.netapp.com with ESMTP; 20 Jun 2013 03:34:47 -0700 Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.35]) by vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) with mapi id 14.03.0123.003; Thu, 20 Jun 2013 03:34:47 -0700 From: "Eggert, Lars" To: "freebsd-net@freebsd.org" Subject: hw.igb.num_queues default Thread-Topic: hw.igb.num_queues default Thread-Index: AQHObaHIf6463S6M5065zbiLDwqGaw== Date: Thu, 20 Jun 2013 10:34:46 +0000 Message-ID: <843F7891-FD87-4F16-A279-B45D4A674F4E@netapp.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] Content-Type: text/plain; charset="us-ascii" Content-ID: <23E91D958892F145A440FDBC87021AA5@hq.netapp.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Jack Vogel X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 20 Jun 2013 10:34:54 -0000 Hi, I just popped a new four-port igb card into a -STABLE system and encountere= d severe issues even when unloaded right after boot, to the point where I c= ouldn't even ssh into the system anymore. The box has 2x4 cores: CPU: Intel(R) Xeon(R) CPU X5450 @ 3.00GHz (2992.60-MHz K8-class = CPU) Origin =3D "GenuineIntel" Id =3D 0x10676 Family =3D 0x6 Model =3D 0x17= Stepping =3D 6 Features=3D0xbfebfbff Features2=3D0xce3bd AMD Features=3D0x20100800 AMD Features2=3D0x1 TSC: P-state invariant, performance statistics real memory =3D 8589934592 (8192 MB) avail memory =3D 8239513600 (7857 MB) MPTable: Event timer "LAPIC" quality 400 FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 2 package(s) x 4 core(s) By default, the igb driver seems to set up one queue per detected CPU. Goog= ling around, people seemed to suggest that limiting the number of queues ma= kes things work better. I can confirm that setting hw.igb.num_queues=3D2 se= ems to have fixed the issue. (Two was the first value I tried, maybe other = values other than 0 would work, too.) In order to uphold POLA, should the igb driver maybe default to a conservat= ive value for hw.igb.num_queues that may not deliver optimal performance, b= ut at least works out of the box? Lars= From owner-freebsd-net@FreeBSD.ORG Thu Jun 20 13:38:06 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 448A69BC for ; Thu, 20 Jun 2013 13:38:06 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [IPv6:2a03:3100:c:13::5]) by mx1.freebsd.org (Postfix) with ESMTP id DD9AF19B9 for ; Thu, 20 Jun 2013 13:38:05 +0000 (UTC) Received: from eg.sd.rdtc.ru (localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.14.7/8.14.7) with ESMTP id r5KDc0rI036537; Thu, 20 Jun 2013 20:38:00 +0700 (NOVT) (envelope-from eugen@grosbein.net) Message-ID: <51C305B3.7050703@grosbein.net> Date: Thu, 20 Jun 2013 20:37:55 +0700 From: Eugene Grosbein User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130415 Thunderbird/17.0.5 MIME-Version: 1.0 To: "Eggert, Lars" Subject: Re: hw.igb.num_queues default References: <843F7891-FD87-4F16-A279-B45D4A674F4E@netapp.com> In-Reply-To: <843F7891-FD87-4F16-A279-B45D4A674F4E@netapp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: "freebsd-net@freebsd.org" , Jack Vogel X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 20 Jun 2013 13:38:06 -0000 On 20.06.2013 17:34, Eggert, Lars wrote: > real memory = 8589934592 (8192 MB) > avail memory = 8239513600 (7857 MB) > By default, the igb driver seems to set up one queue per detected CPU. Googling around, people seemed to suggest that limiting the number of queues makes things work better. I can confirm that setting hw.igb.num_queues=2 seems to have fixed the issue. (Two was the first value I tried, maybe other values other than 0 would work, too.) > > In order to uphold POLA, should the igb driver maybe default to a conservative value for hw.igb.num_queues that may not deliver optimal performance, but at least works out of the box? Or, better, make nmbclusters auto-tuning smarter, if any. I mean, use more nmbclusters for machines with large amounts of memory. Eugene Grosbein From owner-freebsd-net@FreeBSD.ORG Thu Jun 20 14:30:05 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7E492E3F for ; Thu, 20 Jun 2013 14:30:05 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id E91E51CDE for ; Thu, 20 Jun 2013 14:30:04 +0000 (UTC) Received: (qmail 65271 invoked from network); 20 Jun 2013 15:24:21 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 20 Jun 2013 15:24:21 -0000 Message-ID: <51C311D6.5090801@freebsd.org> Date: Thu, 20 Jun 2013 16:29:42 +0200 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Eugene Grosbein Subject: Re: hw.igb.num_queues default References: <843F7891-FD87-4F16-A279-B45D4A674F4E@netapp.com> <51C305B3.7050703@grosbein.net> In-Reply-To: <51C305B3.7050703@grosbein.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-net@freebsd.org" , "Eggert, Lars" , Jack Vogel X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 20 Jun 2013 14:30:05 -0000 On 20.06.2013 15:37, Eugene Grosbein wrote: > On 20.06.2013 17:34, Eggert, Lars wrote: > >> real memory = 8589934592 (8192 MB) >> avail memory = 8239513600 (7857 MB) > >> By default, the igb driver seems to set up one queue per detected CPU. Googling around, people seemed to suggest that limiting the number of queues makes things work better. I can confirm that setting hw.igb.num_queues=2 seems to have fixed the issue. (Two was the first value I tried, maybe other values other than 0 would work, too.) >> >> In order to uphold POLA, should the igb driver maybe default to a conservative value for hw.igb.num_queues that may not deliver optimal performance, but at least works out of the box? > > Or, better, make nmbclusters auto-tuning smarter, if any. > I mean, use more nmbclusters for machines with large amounts of memory. That has already been done in HEAD. The other problem is the pre-filling of the large rings for all queues stranding large amounts of mbuf clusters. OpenBSD starts with a small number of filled mbufs in the RX ring and then dynamically adjusts the number upwards if there is enough traffic to maintain deep buffers. I don't know if it always quickly scales in practice though. -- Andre From owner-freebsd-net@FreeBSD.ORG Thu Jun 20 14:53:44 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6C200C9C for ; Thu, 20 Jun 2013 14:53:44 +0000 (UTC) (envelope-from dkandula@gmail.com) Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) by mx1.freebsd.org (Postfix) with ESMTP id 0992D1E67 for ; Thu, 20 Jun 2013 14:53:43 +0000 (UTC) Received: by mail-wi0-f176.google.com with SMTP id ey16so1912515wid.3 for ; Thu, 20 Jun 2013 07:53:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=oD4UsRza7EfitMoOcT78QTKHuOia1MOTsigQueep7ko=; b=nYKfMgyAeVWsR0Tf/GVThmtnn9sGOEwJy9Ld5REelULTJ2cQvBZ1kSkuSxHQB02/Oc W819yj0S08rtww97igxJuNMDjrmI775uU15rJ36jnz997lfe6HHVThYY2goRRzrrP33k DAJguHSi252pLDSs9ro01/CiUlMkcBkcfCZPsQz7y9eAY4a31qfXEoV3IXBKKxxeoq/r /sXqTGiaUToitqrhTouPoCeOiXLgMco1JlZ8I63doRunMZqbaW5RP9BinvSDHmB6by5M i7dR6bKuzp/5mkHENxmHl9y0de2+3AT+4u7FLm+iW0ofSnDL9htNnPhLDFgkt5TdlSLq uBRQ== MIME-Version: 1.0 X-Received: by 10.180.20.228 with SMTP id q4mr5818186wie.1.1371740023235; Thu, 20 Jun 2013 07:53:43 -0700 (PDT) Received: by 10.194.6.137 with HTTP; Thu, 20 Jun 2013 07:53:43 -0700 (PDT) Date: Thu, 20 Jun 2013 10:53:43 -0400 Message-ID: Subject: Route deletion when processing a packet by ip_output From: Dheeraj Kandula To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 20 Jun 2013 14:53:44 -0000 Hey All, I have been going through the routing and packet processing code in FreeBSD and am not sure how this scenario is handled though this looks basic. Am I missing something here? When ip_output function is processing a packet and uses a route to send it on it's way to the destination, ip_output doesn't hold the read lock of the routing tree while processing the packet. This can be observed from the fact that the ignore flag is set to 0 when invoking in_rtalloc_ign(). Hence even though we increment the reference count for the route when we perform a lookup, the route deletion code can proceed with the deletion as the read lock is not acquired by anyone. i.e. there are no readers. Hence acquiring the write lock succeeds for deletion. The rn_delete disconnects the two nodes from the routing tree i.e. leaf and internal nodes for the route. But in rtrequest1_fib(), the memory for route i,e., rtentry is not unallocated as the reference count is not 1. it will be 2. But when we return from rtrequest1_fib() we don't have a handle on the route entry. Hence how do we get back to this route. I guess because we have a handle to it via the route lookup we can delete it once we call RT_REMREF macro. But once the route is disconnected from the routing tree, it doesn't make sense to use it. Isn't it? i.e. ip_output() may still use it to process the packet. Can anyone clarify this? Am I missing something here or didn't consider something along the way. Dheeraj From owner-freebsd-net@FreeBSD.ORG Thu Jun 20 15:33:50 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 27956B8C for ; Thu, 20 Jun 2013 15:33:50 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: from nm19-vm1.bullet.mail.ne1.yahoo.com (nm19-vm1.bullet.mail.ne1.yahoo.com [98.138.91.56]) by mx1.freebsd.org (Postfix) with ESMTP id CF5961124 for ; Thu, 20 Jun 2013 15:33:49 +0000 (UTC) Received: from [98.138.90.48] by nm19.bullet.mail.ne1.yahoo.com with NNFMP; 20 Jun 2013 15:33:43 -0000 Received: from [98.138.226.160] by tm1.bullet.mail.ne1.yahoo.com with NNFMP; 20 Jun 2013 15:33:43 -0000 Received: from [127.0.0.1] by omp1061.mail.ne1.yahoo.com with NNFMP; 20 Jun 2013 15:33:43 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 197182.83548.bm@omp1061.mail.ne1.yahoo.com Received: (qmail 52702 invoked by uid 60001); 20 Jun 2013 15:33:42 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1371742422; bh=yEuGygb6PbwhCAjYcSPTPeWgxct9uGBrmRJxvGPIeic=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=1NdyDmAIlaactKeDQaKep7Ektwtvk5nKC5EXUYmEm87r6QLYSUvYTj/fydUxSz0Y3M9tolmhcRofkEUSRhOyr+ukbmSC7BRYosO/+1KHz3391SCHn4+7dKT7X3j6YEkgkJS0YZ/3S7mgjk1nuXygD5TT/+Kos1NiZ911obv8XyU= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=jQh3VoIZV6/38pGqpzhQ+I8j+Q9OWHeWAClTm39FefOy592z8yFzydnoJ0YUt3Qo8iH/uZG/WX/HDb07UIy1eHbeYad1iy28LZdajFny8P43/OPWu/uELk5XYzjs7B3yxBSer02KRj74yA1/iwZhwqCBWERILGZYIfdSoQWbpp4=; X-YMail-OSG: G._LySsVM1lTaZyt9oLBq3BegEXRF0nwMu0L0L5xdyFZ1Wh AF0h49AckPgVa.geUNXUTxwGB_7BzOuP0YVW4caE4AOJpxJ1nkHUfCcM8n2f M0Gwb6tJlbsbCJv87TVlu3hSGQdxbGN6Oby2LVJihpQtPmFcPtpzpfM.htGL rM3ihsW5UtcCo1OjydTE9S.2nfFySq5GlpDy3tz5NaSt85q._8QDOkqYTIuT 3gI3HEVjaclbVCgMkcyD5iCZGcJAG2MSKHqwopr0maNqY.6Ctqc7gnWn7gmI KfUqodOzmXE8BKTHR4r6Ne1TG3DxKISfyAbQnb4VbDNSTd0H8hZIOjKrIobn laPX3YJwsGnZ0PN55mgn6nQfG3Yac8PaFUWZkG1TpDSHaGO6e9XR8dYKGiVJ MRPyACr5tJ081Z7lFekXStSmw17mNreLhr60xBOI15r8WZZco2I6SqO0IaHX 0QyZ6HHX_M5dJNc5Mh0oGtqEn.oJev.b6.R2ibj0NvYXn8CAX0Po4zAtMS.B u7ge_j88GdM_WU.8ikx6pmasblfmI3BezZ0VHKWUEZ9VW6oGu3fMVweTm62f uc4AfcgR2Xndy Received: from [98.203.118.124] by web121606.mail.ne1.yahoo.com via HTTP; Thu, 20 Jun 2013 08:33:42 PDT X-Rocket-MIMEInfo: 002.001, LS0tIE9uIFRodSwgNi8yMC8xMywgQW5kcmUgT3BwZXJtYW5uICB3cm90ZToNCg0KJmd0OyBGcm9tOiBBbmRyZSBPcHBlcm1hbm4gDQomZ3Q7IFN1YmplY3Q6IFJlOiBody5pZ2IubnVtX3F1ZXVlcyBkZWZhdWx0DQomZ3Q7IFRvOiAmcXVvdDtFdWdlbmUgR3Jvc2JlaW4mcXVvdDsgDQomZ3Q7IENjOiAmcXVvdDtmcmVlYnNkLW5ldEBmcmVlYnNkLm9yZyZxdW90OyAsICZxdW90O0VnZ2VydCwgTGFycyZxdW90OyAsICZxdW90O0phY2sgVm9nZWwmcXVvdDsgDQomZ3Q7IERhdGU6IFRodXJzZGF5LCBKdW5lIDIwLCABMAEBAQE- X-Mailer: YahooMailClassic/184 YahooMailWebService/0.8.148.554 Message-ID: <1371742422.50315.YahooMailBasic@web121606.mail.ne1.yahoo.com> Date: Thu, 20 Jun 2013 08:33:42 -0700 (PDT) From: Barney Cordoba Subject: Re: hw.igb.num_queues default To: Eugene Grosbein , Andre Oppermann In-Reply-To: <51C311D6.5090801@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-net@freebsd.org" , LarsEggert , Jack Vogel X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 20 Jun 2013 15:33:50 -0000 --- On Thu, 6/20/13, Andre Oppermann wrote: > From: Andre Oppermann=20 > Subject: Re: hw.igb.num_queues default > To: "Eugene Grosbein"=20 > Cc: "freebsd-net@freebsd.org" , "Eggert, Lars" , &= quot;Jack Vogel"=20 > Date: Thursday, June 20, 2013, 10:29 AM > On 20.06.2013 15:37, Eugene Grosbein > wrote: > > On 20.06.2013 17:34, Eggert, Lars wrote: > > > >> real memory=A0 =3D 8589934592 (8192 MB) > >> avail memory =3D 8239513600 (7857 MB) > > > >> By default, the igb driver seems to set up one > queue per detected CPU. Googling around, people seemed to > suggest that limiting the number of queues makes things work > better. I can confirm that setting hw.igb.num_queues=3D2 seems > to have fixed the issue. (Two was the first value I tried, > maybe other values other than 0 would work, too.) > >> > >> In order to uphold POLA, should the igb driver > maybe default to a conservative value for hw.igb.num_queues > that may not deliver optimal performance, but at least works > out of the box? > > > > Or, better, make nmbclusters auto-tuning smarter, if > any. > > I mean, use more nmbclusters for machines with large > amounts of memory. >=20 > That has already been done in HEAD. >=20 > The other problem is the pre-filling of the large rings for > all queues > stranding large amounts of mbuf clusters.=A0 OpenBSD > starts with a small > number of filled mbufs in the RX ring and then dynamically > adjusts the > number upwards if there is enough traffic to maintain deep > buffers.=A0 I > don't know if it always quickly scales in practice though. You're probably not running with 512MB these days, so pre-filling isn&#= 39;t much of an issue. 4 queues is only 8MB of ram with 1024 descriptors per queue, and 4MB with 5= 12. Think about the # of queues issue. In order to have acceptable latency, you= need to do 6k-10k=20 interrupts per second per queue. So with 4 queues you have to process 40K i= nts/second and with 2 you only process 20k. For a gig link 2 queues is much more effi= cient. "Spreading" for the sake of spreading is more about Intel marketi= ng than it is about practical computing. BC BC From owner-freebsd-net@FreeBSD.ORG Thu Jun 20 15:51:12 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CC1D8FDD; Thu, 20 Jun 2013 15:51:12 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by mx1.freebsd.org (Postfix) with ESMTP id B3F0111EC; Thu, 20 Jun 2013 15:51:12 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.87,906,1363158000"; d="scan'208";a="27481348" Received: from vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) by mx11-out.netapp.com with ESMTP; 20 Jun 2013 08:51:06 -0700 Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.35]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.03.0123.003; Thu, 20 Jun 2013 08:51:06 -0700 From: "Eggert, Lars" To: Andre Oppermann Subject: Re: hw.igb.num_queues default Thread-Topic: hw.igb.num_queues default Thread-Index: AQHObaHIf6463S6M5065zbiLDwqGa5k/ENGAgAAOeACAABa8AA== Date: Thu, 20 Jun 2013 15:51:04 +0000 Message-ID: <0C63DA17-BB98-4D93-B9D7-F3FAC5972586@netapp.com> References: <843F7891-FD87-4F16-A279-B45D4A674F4E@netapp.com> <51C305B3.7050703@grosbein.net> <51C311D6.5090801@freebsd.org> In-Reply-To: <51C311D6.5090801@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.104.60.116] Content-Type: text/plain; charset="iso-8859-1" Content-ID: <25830E86C07F9E41AE4FD96E90AAA2EA@hq.netapp.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-net@freebsd.org" , Jack Vogel , Eugene Grosbein X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 20 Jun 2013 15:51:12 -0000 Hi, On Jun 20, 2013, at 16:29, Andre Oppermann wrote: > On 20.06.2013 15:37, Eugene Grosbein wrote: >> Or, better, make nmbclusters auto-tuning smarter, if any. >> I mean, use more nmbclusters for machines with large amounts of memory. >=20 > That has already been done in HEAD. the box in question is running -CURRENT, so that may also still help. Frankly, I don't really care what the correct fix is. I just want to be abl= e to plop this NIC in and be able to connect to it without the need to didd= le any loader knobs. Lars= From owner-freebsd-net@FreeBSD.ORG Thu Jun 20 16:06:25 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B5E7362E; Thu, 20 Jun 2013 16:06:25 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx1.netapp.com (mx1.netapp.com [216.240.18.38]) by mx1.freebsd.org (Postfix) with ESMTP id 9C63B12D8; Thu, 20 Jun 2013 16:06:25 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.87,906,1363158000"; d="scan'208";a="264694250" Received: from vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) by mx1-out.netapp.com with ESMTP; 20 Jun 2013 09:06:19 -0700 Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.35]) by vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) with mapi id 14.03.0123.003; Thu, 20 Jun 2013 09:06:18 -0700 From: "Eggert, Lars" To: Andre Oppermann Subject: Re: hw.igb.num_queues default Thread-Topic: hw.igb.num_queues default Thread-Index: AQHObaHIf6463S6M5065zbiLDwqGa5k/ENGAgAAOeACAABa8AIAABEIA Date: Thu, 20 Jun 2013 16:06:18 +0000 Message-ID: References: <843F7891-FD87-4F16-A279-B45D4A674F4E@netapp.com> <51C305B3.7050703@grosbein.net> <51C311D6.5090801@freebsd.org> <0C63DA17-BB98-4D93-B9D7-F3FAC5972586@netapp.com> In-Reply-To: <0C63DA17-BB98-4D93-B9D7-F3FAC5972586@netapp.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.104.60.116] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-net@freebsd.org" , Jack Vogel , Eugene Grosbein X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 20 Jun 2013 16:06:25 -0000 On Jun 20, 2013, at 17:51, "Eggert, Lars" wrote: > the box in question is running -CURRENT, so that may also still help. s/CURRENT/STABLE/ >=20 > Frankly, I don't really care what the correct fix is. I just want to be a= ble to plop this NIC in and be able to connect to it without the need to di= ddle any loader knobs. >=20 > Lars > _______________________________________________ > 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 Sat Jun 22 01:11:36 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 153EEDD3 for ; Sat, 22 Jun 2013 01:11:36 +0000 (UTC) (envelope-from voxadam@gmail.com) Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) by mx1.freebsd.org (Postfix) with ESMTP id 967A91318 for ; Sat, 22 Jun 2013 01:11:35 +0000 (UTC) Received: by mail-la0-f43.google.com with SMTP id gw10so8133016lab.16 for ; Fri, 21 Jun 2013 18:11:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=no+aHrcUh9T1UGg+KF0D98KXchK+gWR1a9nzf9d7SeM=; b=0jZYZC3NNI8Ngc9VgBz0rP+8WgIdk+7PECZPRpv8P12CJf/QUGJAyX5pcdWTJ4Guge dAhFd70OXmDC+hhTMaGSHrPkpC/8PePzz1IPvf4sTzPX3Gnxx3kaytChfq5MqZ1J+xug ulksc9auA8/fqwiTwZc7V62WaYVLocH6KekGTg4GdjxGg0KvWHQA3rPtoVeU/RzYxBn4 NzhM8/ZnKiHf0WmE8i1/QuyTiTpb+o0Gf4Ny2P4KZFmp4KtOpZQjbp40wk3OhFbRs4Yo cSzabFCMBfueOpAX8T/QgrUL58mU+SXXNlhu5lXf5++Jf3dm/W3z6vLlGk+z1hC58eMq SMgA== X-Received: by 10.112.180.164 with SMTP id dp4mr2348686lbc.68.1371863494422; Fri, 21 Jun 2013 18:11:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.4.200 with HTTP; Fri, 21 Jun 2013 18:11:14 -0700 (PDT) From: Adam Hunt Date: Fri, 21 Jun 2013 18:11:14 -0700 Message-ID: Subject: Flapping WAN with axe interface To: freebsd-net@freebsd.org, wpaul@windriver.com Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 22 Jun 2013 01:11:36 -0000 I just replaced my old WRT54GS running DD-WRT at home with a proper pfSense firewall. The only real problem I've had is my WAN link to Comcast goes down at least every twelve hours. I used to think it was almost exactly every twelve hours (leading me to think Comcast's DHCP server hated me) but I have since noticed that the WAN flaps at less predictable intervals. I can't figure out if it's related to DHCP or not. I can say that nothing out of the ordinary was going on on my network when this happens. It happens whether or not anyone is actively using any of the systems on the network. It can happen when I'm working, browsing, and streaming Netflix or it can happen everyone in the house is asleep and most everything is down or idle. One thing that I have learned since I starting this adventure is that it's in some way related to my D-Link DUB-E100 rev B1 USB NIC. I know that USB isn't the preferred interface for networking but it's what I had. I'm currently using a 3.4 GHz P4 Prescott Dell OptiPlex GX620 "ultra small form factor" desktop for my firewall and it doesn't have any PCI/PCIe expansion so I'm left with USB. For some reason I had a D-Link DUB-E100 ver. B (AX88772) adapter laying in a box, since it was on the 8.3 HCL I decided to give it a try. Below you'll find the my system, dhcp, and gateway logs for the time that the link goes down. If you need any other logs or other information I'll be more than happy to provide it. system.log: http://pastebin.com/mxuXd55w dhcp.log: http://pastebin.com/tvAihELQ gateways.log: http://pastebin.com/2cZqjJBa So, after watching the logs, thinking, talking on IRC, checking with the pfSense forums I decided to perform a simple experiment. I swapped the interfaces, I connected my DOCSIS bridge to the bge0 onboard interface, and hung my LAN off the USB NIC. Ever since swapping the interfaces everything has been quiet. I haven't seen a single error in any of my logs. What are your thoughts? Is is a Comcast issue, an issue with the DOCSIS bridge, an axe bug, a USB bug, some combination of issues, or something different entirely? I realize I could just leave everything as is but I'd like to help solve this little mystery. Also, years ago I was taught it's bad form not to report potential bugs. Thanks for your help. --adam From owner-freebsd-net@FreeBSD.ORG Sat Jun 22 07:56:03 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E5F8DF98 for ; Sat, 22 Jun 2013 07:56:03 +0000 (UTC) (envelope-from s.khanchi@gmail.com) Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by mx1.freebsd.org (Postfix) with ESMTP id 82A4610E1 for ; Sat, 22 Jun 2013 07:56:03 +0000 (UTC) Received: by mail-we0-f180.google.com with SMTP id w56so6973889wes.39 for ; Sat, 22 Jun 2013 00:56:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; bh=ZbcYNdr8hLwWVka0fiu9Fe6I/40Q3n6ZJ3NTX/jSAfc=; b=IlskXe6PLypcn9R6OppsIZdYEM4fq/1s9bmCj3q307YNky/B2LWnMqJ9/kiG0coNcT CCXUkAziY1uRjFWrijPGIL9IKujiuQvmgjc1o7x6D54bTOkuTcWf6/jIP/1ZQ8/U20Es mw+Ur6CoL1Xwafm8pyAh7wB7a1EOReC2BiQNRA6vyy0HYF8XxLghUfvelr+CL3g0KPku UGvfhGAUkBm/0U6BWyRDZJA01AUNixzcOZZWQIxrEadT9Qa+tvofqDAIw9UXgvipQA22 Zw2sS1ENd0WX2zS+HQdBBTrpky22oz+mPg11lVwRwG1r4GWkgAdwPXMwzCXG03fsbJaj 9HyA== X-Received: by 10.194.8.163 with SMTP id s3mr11616145wja.41.1371887762645; Sat, 22 Jun 2013 00:56:02 -0700 (PDT) MIME-Version: 1.0 Sender: s.khanchi@gmail.com Received: by 10.194.22.195 with HTTP; Sat, 22 Jun 2013 00:55:42 -0700 (PDT) From: h bagade Date: Sat, 22 Jun 2013 12:25:42 +0430 X-Google-Sender-Auth: E4HokktqKF_YbPKZw3EwzUeImgs Message-ID: Subject: probable side effects of deleting interfaces ip addresses(loopback ones) from routing table ! To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 22 Jun 2013 07:56:04 -0000 Hi all, I've deleted the interface ip address from routing table and only keep the network address. Nothing is behaving unusual afterwards. I think this loopback ip address is added for better performance. My question is would I get in to trouble by deleting these ip addresses from routing table or it's, as I think, just a matter of performance? Thanks in advance From owner-freebsd-net@FreeBSD.ORG Sat Jun 22 08:04:16 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C6C3117E; Sat, 22 Jun 2013 08:04:16 +0000 (UTC) (envelope-from s.khanchi@gmail.com) Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) by mx1.freebsd.org (Postfix) with ESMTP id 37CA61127; Sat, 22 Jun 2013 08:04:16 +0000 (UTC) Received: by mail-wi0-f177.google.com with SMTP id ey16so1208187wid.4 for ; Sat, 22 Jun 2013 01:04:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=CfiShldyz11dSy0rqDtGs4rTOM/Y5sV0VVXX4xOjYXo=; b=0svxktwuCwfVkXwq0w+p9Oe49k0NomnrweWdAb49XjgOaoQ91omuFYnFcUoPFjCRCX 7STItLgy1FqlErB/RLOPNTsWS1IRFmdyYDKmKq2phFupEjF4TWYhhVL47JTxdRfzCbCl jp7NFhzhPcFKQMgJkkIqicS096To+BqhbL2KPYmwLHPpNbcCGkDjtNoKH6kf5nalLwao cfMRuc5z+eAKEcYxL8q5Y9Y5ml7t/Vvd3JT8OsNB6GZ1XFp/iYKpU3dDv+f7zzZBypdw cRmFGZnM6KhJFKpqfZQumdwyepsNVEBQGU6KfgC3NCVRQonwUH6B+NMZl21YL2YngF/W V0lg== X-Received: by 10.194.8.163 with SMTP id s3mr11631437wja.41.1371888255338; Sat, 22 Jun 2013 01:04:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.22.195 with HTTP; Sat, 22 Jun 2013 01:03:55 -0700 (PDT) In-Reply-To: <51BFA24D.70705@rewt.org.uk> References: <69CF1AAF-230D-4B2B-9C95-20DDD772997E@dataix.net> <51BFA24D.70705@rewt.org.uk> From: Sara Khanchi Date: Sat, 22 Jun 2013 12:33:55 +0430 Message-ID: Subject: Re: How not allow setting ip changes interface down status? To: Joe Holden Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Adrian Chadd , Jack Vogel , "freebsd-net@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 22 Jun 2013 08:04:16 -0000 On Tue, Jun 18, 2013 at 4:27 AM, Joe Holden wrote: > Jason Hellenthal wrote: > >> Off the top of my head I don't know of another OS that does this. >> >> But yes agreed changing that behavior would probably effect a lot of >> people in a negative way at this point. >> >> Not to mention script breakage. >> >> But a tunable in the stack somewhere would be awesome to change this >> behavior. Either interface specific or global or both. >> >> Sometimes installing a new faucet you don't want the water to run until >> all the nuts, bolts and washers are installed. >> >> The entire notion is ridiculous, it is quite simple - if the interface > is down, it isn't in the FIB, you can't arbitarily return an error for > setting an IP on an interface that isn't up. > > The last thing we need is yet more nonsense stack changes, allowing 0/8 to > be used was bad enough. > What I've intended to do, as jason is mentioned too, is assigning IP address to the interface but not let it works until a proper time. As I understand there is not any way just set the interface down besides adding IP! Still, any other solution? From owner-freebsd-net@FreeBSD.ORG Sat Jun 22 08:28:38 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A0547605 for ; Sat, 22 Jun 2013 08:28:38 +0000 (UTC) (envelope-from cochard@gmail.com) Received: from mail-ve0-x236.google.com (mail-ve0-x236.google.com [IPv6:2607:f8b0:400c:c01::236]) by mx1.freebsd.org (Postfix) with ESMTP id 6859411C2 for ; Sat, 22 Jun 2013 08:28:38 +0000 (UTC) Received: by mail-ve0-f182.google.com with SMTP id ox1so7114061veb.41 for ; Sat, 22 Jun 2013 01:28:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; bh=6ni1zeTOSPepJAPQCpSgyysUr2G8b7R5iQnorORpNCY=; b=Mkb2l6jg1SRgoIiZTpX7kFmxyPcWim4xxxhGEtTP8TdrUnDuLiD+2nEKDoneHvyDvv Cg+i+pNuODQXZzf9YPKaQ7PaoRLsOXQnvZ+oiq4reKGONS3euUX0cgDGH2WXI8XU8sne QFac3UeNZf4CGvCfNuk5STmYwt+u7gUCvga6Bt3pUwZ1FKk32d6aOkm0Q3Z7U0fWTd4D twDHx0Jdxjy1Z0mB2dz3KGZBzGfvpDnZVQZEXtmedasLV6XFNYRx826/ZjkcZwiHfOL3 D7Ca0ESiGMWfQxdAOk47FMI8GOKjonyGnWledBrrZnowa2RfJOexg36Ci4PyHplyrAXl ZwjA== X-Received: by 10.52.74.67 with SMTP id r3mr6243001vdv.112.1371889717944; Sat, 22 Jun 2013 01:28:37 -0700 (PDT) MIME-Version: 1.0 Sender: cochard@gmail.com Received: by 10.58.189.132 with HTTP; Sat, 22 Jun 2013 01:28:17 -0700 (PDT) From: =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?= Date: Sat, 22 Jun 2013 10:28:17 +0200 X-Google-Sender-Auth: sJuvtuPkooA-XH4H8M1Ye6VwGh0 Message-ID: Subject: netstat -i not accurate on -stable ? To: "freebsd-net@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 22 Jun 2013 08:28:38 -0000 Hi all, I was testing my pthread-netblbast (PR bin/179085) when I found a problem with netstat counters (tested on 9-stable r252056). netreceive (src/toots/tools/netrate) display this output: 542025 pps 43.362 Mbps - 271554 pkts in 0.500998393 ns 541562 pps 43.325 Mbps - 271323 pkts in 0.501000754 ns 541517 pps 43.321 Mbps - 271300 pkts in 0.500999700 ns 540487 pps 43.239 Mbps - 270784 pkts in 0.500999904 ns 541541 pps 43.323 Mbps - 271312 pkts in 0.500999621 ns 540624 pps 43.250 Mbps - 270853 pkts in 0.501000361 ns 541403 pps 43.312 Mbps - 271243 pkts in 0.500999669 ns 541079 pps 43.286 Mbps - 271081 pkts in 0.501000212 ns 540887 pps 43.271 Mbps - 270985 pkts in 0.501000258 ns 541796 pps 43.344 Mbps - 271440 pkts in 0.500999971 ns 541056 pps 43.284 Mbps - 271069 pkts in 0.500999719 ns 541224 pps 43.298 Mbps - 271155 pkts in 0.501002856 ns 541120 pps 43.290 Mbps - 271100 pkts in 0.500997659 ns But in the same time a "netstat -ihw 1" display this output: input (Total) output packets errs idrops bytes packets errs bytes colls 521k 508k 0 30M 3 0 562 0 521k 511k 0 30M 3 0 514 0 521k 526k 0 30M 3 0 514 0 521k 538k 0 30M 4 0 616 0 521k 495k 0 30M 3 0 514 0 521k 502k 0 30M 3 0 514 0 521k 531k 0 30M 3 0 514 0 521k 502k 0 30M 3 0 514 0 521k 504k 0 30M 3 0 514 0 521k 495k 0 30M 3 0 514 0 521k 498k 0 30M 3 0 514 0 521k 516k 0 30M 3 0 514 0 There are about 20Kpps difference between them. Regards, Olivier From owner-freebsd-net@FreeBSD.ORG Sat Jun 22 08:51:53 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 138BABEF for ; Sat, 22 Jun 2013 08:51:53 +0000 (UTC) (envelope-from sthaug@nethelp.no) Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by mx1.freebsd.org (Postfix) with SMTP id 5E350125B for ; Sat, 22 Jun 2013 08:51:51 +0000 (UTC) Received: (qmail 21547 invoked from network); 22 Jun 2013 08:45:09 -0000 Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 22 Jun 2013 08:45:09 -0000 Date: Sat, 22 Jun 2013 10:45:09 +0200 (CEST) Message-Id: <20130622.104509.74740460.sthaug@nethelp.no> To: s.khanchi@gmail.com Subject: Re: How not allow setting ip changes interface down status? From: sthaug@nethelp.no In-Reply-To: References: <51BFA24D.70705@rewt.org.uk> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 22 Jun 2013 08:51:53 -0000 > What I've intended to do, as jason is mentioned too, is assigning IP > address to the interface but not let it works until a proper time. As I > understand there is not any way just set the interface down besides adding > IP! Still, any other solution? Tested on 8.4-STABLE: ifconfig em0 10.2.3.4/24 ifconfig em0 down or, in rc.conf ifconfig_em1="inet 10.2.3.4/24" ifconfig_em1_alias0="down" I find this use of alias clumsy, and it *should not* be necessary. In both cases there is probably a small window where the interface is up and answering for the specified IP address. (I also tried ifconfig em0 10.2.3.4/24 down which didn't work - the interface is left in the UP state.) Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-net@FreeBSD.ORG Sat Jun 22 10:26:33 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 72596D20 for ; Sat, 22 Jun 2013 10:26:33 +0000 (UTC) (envelope-from carsten@innolan.dk) Received: from mail.innomanslan.tf (0126800067.1.fullrate.dk [95.166.204.165]) by mx1.freebsd.org (Postfix) with ESMTP id EE46C16F5 for ; Sat, 22 Jun 2013 10:26:32 +0000 (UTC) Received: from [192.168.44.228] (unknown [192.168.44.228]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: carsten@thehawk.dk) by mail.innomanslan.tf (Postfix) with ESMTPSA id 3B7CC12C2CA3; Sat, 22 Jun 2013 12:18:25 +0200 (CEST) Message-ID: <51C579F0.3020701@innolan.dk> Date: Sat, 22 Jun 2013 12:18:24 +0200 From: Carsten Sonne Larsen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130611 Thunderbird/17.0.6 MIME-Version: 1.0 To: Adam Hunt Subject: Re: Flapping WAN with axe interface References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, wpaul@windriver.com X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 22 Jun 2013 10:26:33 -0000 I used to run a setup with a D-Link DUB-E100 ver. B adapter on pfSense also using it for a DCHP WAN connection. I had a similar issues. Every time I unplugged the DUB-E100 things would work smoothly again. Now Im using the D-Link adapter on a 8.3-RELEASE and am still having issues once in a while. Im not a hardware guy but I think the D-Link simply just have a buggy hardware or somehow have some hardware restriction preventing it to be used as nothing else but an extra NIC in a laptop - I remember one of the issues was the NIC not being able to allocate buffer space. /carsten On 06/22/2013 03:11, Adam Hunt wrote: > I just replaced my old WRT54GS running DD-WRT at home with a proper pfSense > firewall. The only real problem I've had is my WAN link to Comcast goes > down at least every twelve hours. I used to think it was almost exactly > every twelve hours (leading me to think Comcast's DHCP server hated me) but > I have since noticed that the WAN flaps at less predictable intervals. I > can't figure out if it's related to DHCP or not. I can say that nothing out > of the ordinary was going on on my network when this happens. It happens > whether or not anyone is actively using any of the systems on the network. > It can happen when I'm working, browsing, and streaming Netflix or it can > happen everyone in the house is asleep and most everything is down or idle. > > One thing that I have learned since I starting this adventure is that it's > in some way related to my D-Link DUB-E100 rev B1 USB NIC. I know that USB > isn't the preferred interface for networking but it's what I had. I'm > currently using a 3.4 GHz P4 Prescott Dell OptiPlex GX620 "ultra small form > factor" desktop for my firewall and it doesn't have any PCI/PCIe expansion > so I'm left with USB. For some reason I had a D-Link DUB-E100 ver. B > (AX88772) adapter laying in a box, since it was on the 8.3 HCL I decided to > give it a try. > > Below you'll find the my system, dhcp, and gateway logs for the time that > the link goes down. If you need any other logs or other information I'll be > more than happy to provide it. > > system.log:http://pastebin.com/mxuXd55w > dhcp.log:http://pastebin.com/tvAihELQ > gateways.log:http://pastebin.com/2cZqjJBa > > > So, after watching the logs, thinking, talking on IRC, checking with the > pfSense forums I decided to perform a simple experiment. I swapped the > interfaces, I connected my DOCSIS bridge to the bge0 onboard interface, and > hung my LAN off the USB NIC. Ever since swapping the interfaces everything > has been quiet. I haven't seen a single error in any of my logs. > > What are your thoughts? Is is a Comcast issue, an issue with the DOCSIS > bridge, an axe bug, a USB bug, some combination of issues, or something > different entirely? I realize I could just leave everything as is but I'd > like to help solve this little mystery. Also, years ago I was taught it's > bad form not to report potential bugs. > > Thanks for your help. > > --adam > _______________________________________________ > 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"