From owner-freebsd-net@freebsd.org Sun May 1 21:00:16 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D484B29194 for ; Sun, 1 May 2016 21:00:16 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 03D701F05 for ; Sun, 1 May 2016 21:00:16 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u41L016c072451 for ; Sun, 1 May 2016 21:00:15 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201605012100.u41L016c072451@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-net@FreeBSD.org Subject: Problem reports for freebsd-net@FreeBSD.org that need special attention Date: Sun, 01 May 2016 21:00:15 +0000 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 01 May 2016 21:00:16 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- In Progress | 193452 | Dell PowerEdge 210 II -- Kernel panic bce (broadc In Progress | 203422 | mpd/ppoe not working with re(4) with revision 285 New | 204438 | setsockopt() handling of kern.ipc.maxsockbuf limi New | 205592 | TCP processing in IPSec causes kernel panic New | 206053 | kqueue support code of netmap causes panic Open | 148807 | [panic] 8.1-RELEASE/10.1-STABLE "panic: sbdrop" a Open | 194485 | Userland cannot add IPv6 prefix routes Open | 194515 | Fatal Trap 12 Kernel with vimage Open | 199136 | [if_tap] Added down_on_close sysctl variable to t Open | 201694 | 10.2-BETA2 crashing when killing VIMAGE/VNET jail Open | 206544 | sendmsg(2) (sendto(2) too?) can fail with EINVAL; 11 problems total for which you should take action. From owner-freebsd-net@freebsd.org Tue May 3 08:13:36 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DBC94B298DD for ; Tue, 3 May 2016 08:13:36 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from reviews.nyi.freebsd.org (reviews.nyi.freebsd.org [IPv6:2610:1c1:1:607c::16:b]) by mx1.freebsd.org (Postfix) with ESMTP id AC7BB10AF for ; Tue, 3 May 2016 08:13:36 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by reviews.nyi.freebsd.org (Postfix, from userid 1346) id 112A4152B1; Tue, 3 May 2016 08:13:36 +0000 (UTC) Date: Tue, 3 May 2016 08:13:36 +0000 To: freebsd-net@freebsd.org From: Phabricator Reply-to: D6137+325+f015369c65104c2f@reviews.freebsd.org Subject: [Differential] D6137: tcp/lro: Refactor the free/active list operation. Message-ID: X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , Thread-Topic: D6137: tcp/lro: Refactor the free/active list operation. X-Herald-Rules: <64> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: ZDQ3OTAzM2ZhZTk0ODRmZGQwZGYxNDFlY2ZjIFcoXbA= MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="b1_d8a6fb02e6aab60dba85788c4ecbc6ab" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 May 2016 08:13:37 -0000 --b1_d8a6fb02e6aab60dba85788c4ecbc6ab Content-Type: text/plain; charset = "utf-8" Content-Transfer-Encoding: 8bit This revision was automatically updated to reflect the committed changes. Closed by commit rS298974: tcp/lro: Refactor the active list operation. (authored by sephe). CHANGED PRIOR TO COMMIT https://reviews.freebsd.org/D6137?vs=15725&id=15841#toc REPOSITORY rS FreeBSD src repository CHANGES SINCE LAST UPDATE https://reviews.freebsd.org/D6137?vs=15725&id=15841 REVISION DETAIL https://reviews.freebsd.org/D6137 AFFECTED FILES head/sys/netinet/tcp_lro.c EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, network, adrian, delphij, glebius, hselasky, np, decui_microsoft.com, honzhan_microsoft.com, howard0su_gmail.com, transport, rrs, gallatin Cc: freebsd-net-list --b1_d8a6fb02e6aab60dba85788c4ecbc6ab Content-Type: text/x-patch; charset=utf-8; name="D6137.15841.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="D6137.15841.patch" ZGlmZiAtLWdpdCBhL2hlYWQvc3lzL25ldGluZXQvdGNwX2xyby5jIGIvaGVhZC9zeXMvbmV0aW5l dC90Y3BfbHJvLmMKLS0tIGEvaGVhZC9zeXMvbmV0aW5ldC90Y3BfbHJvLmMKKysrIGIvaGVhZC9z eXMvbmV0aW5ldC90Y3BfbHJvLmMKQEAgLTY5LDYgKzY5LDIwIEBACiAKIHN0YXRpYyB2b2lkCXRj cF9scm9fcnhfZG9uZShzdHJ1Y3QgbHJvX2N0cmwgKmxjKTsKIAorc3RhdGljIF9faW5saW5lIHZv aWQKK3RjcF9scm9fYWN0aXZlX2luc2VydChzdHJ1Y3QgbHJvX2N0cmwgKmxjLCBzdHJ1Y3QgbHJv X2VudHJ5ICpsZSkKK3sKKworCUxJU1RfSU5TRVJUX0hFQUQoJmxjLT5scm9fYWN0aXZlLCBsZSwg bmV4dCk7Cit9CisKK3N0YXRpYyBfX2lubGluZSB2b2lkCit0Y3BfbHJvX2FjdGl2ZV9yZW1vdmUo c3RydWN0IGxyb19lbnRyeSAqbGUpCit7CisKKwlMSVNUX1JFTU9WRShsZSwgbmV4dCk7Cit9CisK IGludAogdGNwX2xyb19pbml0KHN0cnVjdCBscm9fY3RybCAqbGMpCiB7CkBAIC0xMjksNyArMTQz LDcgQEAKIAogCS8qIGZyZWUgYWN0aXZlIG1idWZzLCBpZiBhbnkgKi8KIAl3aGlsZSAoKGxlID0g TElTVF9GSVJTVCgmbGMtPmxyb19hY3RpdmUpKSAhPSBOVUxMKSB7Ci0JCUxJU1RfUkVNT1ZFKGxl LCBuZXh0KTsKKwkJdGNwX2xyb19hY3RpdmVfcmVtb3ZlKGxlKTsKIAkJbV9mcmVlbShsZS0+bV9o ZWFkKTsKIAl9CiAKQEAgLTIzNCw3ICsyNDgsNyBAQAogCXN0cnVjdCBscm9fZW50cnkgKmxlOwog CiAJd2hpbGUgKChsZSA9IExJU1RfRklSU1QoJmxjLT5scm9fYWN0aXZlKSkgIT0gTlVMTCkgewot CQlMSVNUX1JFTU9WRShsZSwgbmV4dCk7CisJCXRjcF9scm9fYWN0aXZlX3JlbW92ZShsZSk7CiAJ CXRjcF9scm9fZmx1c2gobGMsIGxlKTsKIAl9CiB9CkBAIC0yNTIsNyArMjY2LDcgQEAKIAl0aW1l dmFsc3ViKCZ0diwgdGltZW91dCk7CiAJTElTVF9GT1JFQUNIX1NBRkUobGUsICZsYy0+bHJvX2Fj dGl2ZSwgbmV4dCwgbGVfdG1wKSB7CiAJCWlmICh0aW1ldmFsY21wKCZ0diwgJmxlLT5tdGltZSwg Pj0pKSB7Ci0JCQlMSVNUX1JFTU9WRShsZSwgbmV4dCk7CisJCQl0Y3BfbHJvX2FjdGl2ZV9yZW1v dmUobGUpOwogCQkJdGNwX2xyb19mbHVzaChsYywgbGUpOwogCQl9CiAJfQpAQCAtNjIwLDE2ICs2 MzQsMTYgQEAKIAogCQkvKiBGbHVzaCBub3cgaWYgYXBwZW5kaW5nIHdpbGwgcmVzdWx0IGluIG92 ZXJmbG93LiAqLwogCQlpZiAobGUtPnBfbGVuID4gKGxjLT5scm9fbGVuZ3RoX2xpbSAtIHRjcF9k YXRhX2xlbikpIHsKLQkJCUxJU1RfUkVNT1ZFKGxlLCBuZXh0KTsKKwkJCXRjcF9scm9fYWN0aXZl X3JlbW92ZShsZSk7CiAJCQl0Y3BfbHJvX2ZsdXNoKGxjLCBsZSk7CiAJCQlicmVhazsKIAkJfQog CiAJCS8qIFRyeSB0byBhcHBlbmQgdGhlIG5ldyBzZWdtZW50LiAqLwogCQlpZiAoX19wcmVkaWN0 X2ZhbHNlKHNlcSAhPSBsZS0+bmV4dF9zZXEgfHwKIAkJICAgICh0Y3BfZGF0YV9sZW4gPT0gMCAm JiBsZS0+YWNrX3NlcSA9PSB0aC0+dGhfYWNrKSkpIHsKIAkJCS8qIE91dCBvZiBvcmRlciBwYWNr ZXQgb3IgZHVwbGljYXRlIEFDSy4gKi8KLQkJCUxJU1RfUkVNT1ZFKGxlLCBuZXh0KTsKKwkJCXRj cF9scm9fYWN0aXZlX3JlbW92ZShsZSk7CiAJCQl0Y3BfbHJvX2ZsdXNoKGxjLCBsZSk7CiAJCQly ZXR1cm4gKFRDUF9MUk9fQ0FOTk9UKTsKIAkJfQpAQCAtNjYyLDcgKzY3Niw3IEBACiAJCQkgKiBi ZSBmdXJ0aGVyIGRlbGF5ZWQuCiAJCQkgKi8KIAkJCWlmIChsZS0+YXBwZW5kX2NudCA+PSBsYy0+ bHJvX2Fja2NudF9saW0pIHsKLQkJCQlMSVNUX1JFTU9WRShsZSwgbmV4dCk7CisJCQkJdGNwX2xy b19hY3RpdmVfcmVtb3ZlKGxlKTsKIAkJCQl0Y3BfbHJvX2ZsdXNoKGxjLCBsZSk7CiAJCQl9CiAJ CQlyZXR1cm4gKDApOwpAQCAtNjg2LDcgKzcwMCw3IEBACiAJCSAqIG92ZXJmbG93LCBwcm8tYWN0 aXZlbHkgZmx1c2ggbm93LgogCQkgKi8KIAkJaWYgKGxlLT5wX2xlbiA+IChsYy0+bHJvX2xlbmd0 aF9saW0gLSBsYy0+aWZwLT5pZl9tdHUpKSB7Ci0JCQlMSVNUX1JFTU9WRShsZSwgbmV4dCk7CisJ CQl0Y3BfbHJvX2FjdGl2ZV9yZW1vdmUobGUpOwogCQkJdGNwX2xyb19mbHVzaChsYywgbGUpOwog CQl9IGVsc2UKIAkJCWdldG1pY3JvdGltZSgmbGUtPm10aW1lKTsKQEAgLTcwMSw3ICs3MTUsNyBA QAogCS8qIFN0YXJ0IGEgbmV3IHNlZ21lbnQgY2hhaW4uICovCiAJbGUgPSBMSVNUX0ZJUlNUKCZs Yy0+bHJvX2ZyZWUpOwogCUxJU1RfUkVNT1ZFKGxlLCBuZXh0KTsKLQlMSVNUX0lOU0VSVF9IRUFE KCZsYy0+bHJvX2FjdGl2ZSwgbGUsIG5leHQpOworCXRjcF9scm9fYWN0aXZlX2luc2VydChsYywg bGUpOwogCWdldG1pY3JvdGltZSgmbGUtPm10aW1lKTsKIAogCS8qIFN0YXJ0IGZpbGxpbmcgaW4g ZGV0YWlscy4gKi8KCg== --b1_d8a6fb02e6aab60dba85788c4ecbc6ab-- From owner-freebsd-net@freebsd.org Tue May 3 19:41:15 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CC169B2CEBC for ; Tue, 3 May 2016 19:41:15 +0000 (UTC) (envelope-from victor.toni@gmail.com) Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 563A01BCD for ; Tue, 3 May 2016 19:41:15 +0000 (UTC) (envelope-from victor.toni@gmail.com) Received: by mail-lf0-x22f.google.com with SMTP id u64so34752827lff.3 for ; Tue, 03 May 2016 12:41:15 -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; bh=gc0kS4FWeyRgh8FzaGJrEEK3oQhvg2mltOYTUWODP9M=; b=XE0BQXhobNGhUFlgOSiL05XI9JFsqULSS7t/0Vtf/P+LCjKzFKZC8HrMdqCN8K+8sb RFKzTxutJENYagnZCbkiflBNVdani+Qi6CVYx305tf0azxrO29z9COoU0VLOdzqEctJZ aRv+/CHJq4giGJ1LbFcSFhUHhKn4wG6lERuqfmUFiiHv+E0zvxCen9r7f9p969psoLby HeMBiblSFQKtavWHFsuIheC5Tf/u4HbxkJrTz5DLSE+oo8vWsqx2C5pXbqsFj1ZRzHMC LwkRZ4cebmeLDiBQ+qXoPjiO+S6V3AbkJg/StYY/0CfnK8IoGS6ms+DIjt8ZaGvh+q3J qdJQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=gc0kS4FWeyRgh8FzaGJrEEK3oQhvg2mltOYTUWODP9M=; b=CcY0XESbSwDTUnxYjVRJw1Cybb28jEIWFcegSoRdpKwdzoHH/uBf85p1aD74ro/jPY bLQi3GetWKdh6kK4fBu2vVVczAjCV2zlJ3FTzSTmFmouVnxqINuiggJzvbD1XZn8Jtcv bxVY2e/H6z1bMJy7b28nI7qsM6ghu0vHqgYcT4snvPGnBI7sE962+mN5DPDtKo3umv0G gp2hfmdJ/41pAuTHVLQqkVlKZDmtnWK3qBUsVyPBNXH3UDtOOCXRRWC5uUUWo/rTzJho niFSewOrbzRh6pbraXUqV0N8JYSW+0hs6505Ua0DsVDZUgrwWdO03ZoHotZfFPA2Sc7u Ywzw== X-Gm-Message-State: AOPr4FUZp3AycQhy+FNRAz7b2D13ObRYxFIPCXI64jWFBXyVIn/9dFhiiCuR8iaiGi6fQdCGYL17EyBjBl5jXQ== X-Received: by 10.112.73.40 with SMTP id i8mr2082259lbv.101.1462304473697; Tue, 03 May 2016 12:41:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.20.194 with HTTP; Tue, 3 May 2016 12:40:43 -0700 (PDT) From: Victor Toni Date: Tue, 3 May 2016 21:40:43 +0200 Message-ID: Subject: undeclared identifier 'NBBY' To: freebsd-net@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 03 May 2016 19:41:15 -0000 I'm trying to port the linux-based mcproxy ( https://github.com/mcproxy/mcproxy) to FreeBSD. While trying to use instead of I encountered the following error: -------------------------------------------------------------------- /usr/include/netinet6/ip6_mroute.h:90:39: error: use of undeclared identifier 'NBBY' if_mask ifs_bits[howmany(IF_SETSIZE, NIFBITS)]; ^ /usr/include/netinet6/ip6_mroute.h:83:36: note: expanded from macro 'NIFBITS' #define NIFBITS (sizeof(if_mask) * NBBY) /* bits per mask */ ^ /usr/include/netinet6/ip6_mroute.h:86:33: note: expanded from macro 'howmany' #define howmany(x, y) (((x) + ((y) - 1)) / (y)) ^ /usr/include/netinet6/ip6_mroute.h:90:39: error: use of undeclared identifier 'NBBY' /usr/include/netinet6/ip6_mroute.h:83:36: note: expanded from macro 'NIFBITS' #define NIFBITS (sizeof(if_mask) * NBBY) /* bits per mask */ ^ /usr/include/netinet6/ip6_mroute.h:86:45: note: expanded from macro 'howmany' #define howmany(x, y) (((x) + ((y) - 1)) / (y)) ^ -------------------------------------------------------------------- The error results from the missing definition of NBBY or rather the missing include of where NBBY is defined. My expectation would be that header files should be self-sufficient and as such should include on its own. What is the prefered way to work with header files in FreeBSD? Or is it a bug in the header file? Best regards, Victor From owner-freebsd-net@freebsd.org Tue May 3 20:50:38 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A801B2C295 for ; Tue, 3 May 2016 20:50:38 +0000 (UTC) (envelope-from victor.toni@gmail.com) Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C559A13B4 for ; Tue, 3 May 2016 20:50:37 +0000 (UTC) (envelope-from victor.toni@gmail.com) Received: by mail-lf0-x22b.google.com with SMTP id m64so36767518lfd.1 for ; Tue, 03 May 2016 13:50:37 -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; bh=6cwnqH48pjEdyP3TQ2fVHXmicb5bbNNz2eLMhwapJBU=; b=lxuWYixKVkHBX90VMK0kdaIex2dnJtguu2SL3DV4AN6QQ7sinRCI18YUmdTKZipBH8 +SKfzPLSmZRmNwQTRyTm70GREjaMxBbxo9v1xxyvBPl+kd4wJFq0s2gYDwN8ovQLEUd7 GsmcIEBeT5dZhRUVdZ0i0zcm845NjCRaakTMdiVZYfzrgr70ZrzfwfgQp4YzQTB4/dGB IcaNAek/F+1o3qlOwYZoLj6MiLQ7nZrlE0S+vfU1gPWqIz97GwGGqGLUIt4vFRn/kTOp udp+OUkR8ggpBiz2LffEAdWMB4/bzVEKHIXPy87CgOeCVsxCvsPo/JEaf5HNhJ9UsYWT NBjQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=6cwnqH48pjEdyP3TQ2fVHXmicb5bbNNz2eLMhwapJBU=; b=c6EwaUEjhiKI3ds4sWM5KJMvncjq9qXvZ8Ibc8R/J477z+agAPc3K1jsVeW5rgwqUY 5TizzEI9GczeadKjpQOtIpzrRwDoaVPieQU/odnGzUHBf1yMXJRlDiQUKS+Bg9uTGdDZ v+sL0Iodg53UemvrdU3c96R/8BMeARYdLjHb+Sk/NuxLP0vFmWPoLzlKWKEf9+yO4Myw Jmc9zGZ34Mu7eDYonRMVN2JdkIfG9NBiDkRk8aI9naRUt+p9/+JaFeBhwyOf48VIY4/m VXEyt9QOPXarU+PFYBcFgFBuvVfKXC5lGoYiZJClNfoP7UytSXrgAILKKmY9jqRKaHnf fbBw== X-Gm-Message-State: AOPr4FXIOZRyrzfvYTgpXwaiYGlY1GIB0oPaH3t1SMSi9bv1FPwzxYl2eewSl33JZ16F5r/Gt+sT9iKB9NYVKw== X-Received: by 10.112.147.225 with SMTP id tn1mr2197856lbb.98.1462308636048; Tue, 03 May 2016 13:50:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.20.194 with HTTP; Tue, 3 May 2016 13:50:06 -0700 (PDT) From: Victor Toni Date: Tue, 3 May 2016 22:50:06 +0200 Message-ID: Subject: setsourcefilter/getsourcefilter missing const qualifier? To: freebsd-net@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 03 May 2016 20:50:38 -0000 When trying to compile some linux-originated code on FreeBSD I get the following errors: /usr/include/netinet/in.h:585:5: note: candidate function not viable: 3rd argument ('const sockaddr *') would lose const qualifier int setsourcefilter(int, uint32_t, struct sockaddr *, socklen_t, ^ /usr/include/netinet/in.h:587:5: note: candidate function not viable: 3rd argument ('const sockaddr *') would lose const qualifier int getsourcefilter(int, uint32_t, struct sockaddr *, socklen_t, ^ Looking at the linux version of these funtions: http://code.metager.de/source/xref/gnu/glibc/inet/netinet/in.h#616 616 /* Get source filter. */617 *extern* *int* getsourcefilter (*int* __s , uint32_t __interface_addr ,618 *const* *struct* sockaddr *__group ,619 socklen_t __grouplen , uint32_t *__fmode ,620 uint32_t *__numsrc ,621 *struct* sockaddr_storage *__slist ) __THROW ;622 623 /* Set source filter. */624 *extern* *int* setsourcefilter (*int* __s , uint32_t __interface_addr ,625 *const* *struct* sockaddr *__group ,626 socklen_t __grouplen , uint32_t __fmode ,627 uint32_t __numsrc ,628 *const* *struct* sockaddr_storage *__slist ) __THROW ; and the FreeBSD version http://code.metager.de/source/xref/freebsd/sys/netinet/in.h#593 593 *int* setsourcefilter (*int*, uint32_t , *struct* sockaddr *, socklen_t ,594 uint32_t , uint32_t , *struct* sockaddr_storage *);595 *int* getsourcefilter (*int*, uint32_t , *struct* sockaddr *, socklen_t ,596 uint32_t *, uint32_t *, *struct* sockaddr_storage *); the main difference is that the linux version makes guarantees about the parameters. (I know that the line numbers for don't match for the error given, it's for example only) Wouldn't it be safe for the FreeBSD version to make the same assumption? Best regards, Victor From owner-freebsd-net@freebsd.org Wed May 4 00:49:56 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 10AEBB2A1B4 for ; Wed, 4 May 2016 00:49:56 +0000 (UTC) (envelope-from skafte@trollkarl.net) Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D98291B3C for ; Wed, 4 May 2016 00:49:55 +0000 (UTC) (envelope-from skafte@trollkarl.net) Received: by mail-ig0-x232.google.com with SMTP id s8so35337043ign.0 for ; Tue, 03 May 2016 17:49:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=trollkarl.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=5tTEJaMeFFYZ4uISqrYUOfBPx+lBg8+cs3/3ROcybVw=; b=VFqLHGXYAZEtRLfGAfe98btmVLWLHan+io42x0jf8T8hIVczM1zCctkUvmyX9xYv9O BhshqBXLWmihHYGkmHX+61fXe2qviC8i1Kc3YPBNUBDkNoPZdyYWDj45BiwE4Lnjs+Xk ZboP3s6bjpyXsSPc2urYM3PCJV/D3yFFIQvk8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=5tTEJaMeFFYZ4uISqrYUOfBPx+lBg8+cs3/3ROcybVw=; b=S609VKtBXqqt+Gw5d1Pzf8L0eAkkgVJNBOB035JOZMHm5xxC2GnVE2qd58aBjumDYG RbCNb9xtLjKQeqjCOlo5Aakh7X9GztvhyFRNQsoaDRXcu5QedPpkhyB8bb/PMugkZ/en 3CQim0ObvkBqXc+OW5E0OxbTN1iUAixqezpD5A8GHmGPZiCVSx1mYccWkmfR0hLEx+3h OoNVeOMgclPoEc2wRxfwZyAJSSPMiSAAtQu3A8GZY1fCcW7pBzIxdsAAhRzBubS/invD tQ6Z41sxlfMJzdjW3g/AkO/GUU9RHNKImJ8mJZyS+LQ3vOZW1sJDk8WyY/5NjfjRnT0N rR6Q== X-Gm-Message-State: AOPr4FXAGdW0d3JX3crDenbFHjbIDLA/2bskf2qBmb0TjF4FholHGHZuKViesm7qE6+WarggDPPNzr3M00ZlTg== X-Received: by 10.50.132.36 with SMTP id or4mr6980423igb.23.1462322995157; Tue, 03 May 2016 17:49:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.50.200 with HTTP; Tue, 3 May 2016 17:49:35 -0700 (PDT) In-Reply-To: <20130721.210831.74736231.sthaug@nethelp.no> References: <1374423821.78377.YahooMailNeo@web121604.mail.ne1.yahoo.com> <541D7415-70A4-4374-8B8D-FD80A2F03208@netflix.com> <20130721.210831.74736231.sthaug@nethelp.no> From: Greg Skafte Date: Tue, 3 May 2016 18:49:35 -0600 Message-ID: Subject: Re: LACP LAGG device problems To: sthaug@nethelp.no Cc: scottl@netflix.com, barney_cordoba@yahoo.com, adrian@freebsd.org, freebsd-net@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 04 May 2016 00:49:56 -0000 in the world of VSS/IRF switches or VCP switches, we used 2x10G active-active across switches for redundancy + availability + capacity usually with mode IP-HASH -- Email: skafte@trollkarl.net Contact me for ICQ,MSN,AIM,Yahoo,GTalk,Skype -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse than complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) On 21 July 2013 at 13:08, wrote: > > Adrian, you're killing my spam filter! But yes, our use of FreeBSD at > Netflix is hardly a science project. Http://openconnect.netflix.com > > With my ISP hat on, I expect us to continue using LAGG with 10G member > links for many years - simply because 100G is so expensive. One can > hope that CFP2 and CFP4 will improve matters somewhat (though it won't > help much for the DWDM transport side). > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > _______________________________________________ > 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 May 4 02:55:44 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8609AB2C201 for ; Wed, 4 May 2016 02:55:44 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47678171F for ; Wed, 4 May 2016 02:55:44 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi0-x231.google.com with SMTP id x201so50205829oif.3 for ; Tue, 03 May 2016 19:55:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to; bh=8fJEklDW8N+wHuxmzhFTYbe/ztyQLkVDdfKI8WUBfss=; b=MDYSaCXZTcmO6WrnWnMW/X3BweXoCLByzE2fqkC+G/0UZJQ8JBJXQYMr4w9XCuQ1va jV0z33uJLfzb1zgiaXNosVcmIwC3M/PTetJ9CPQuMsSbAPN9T5S5YKg0EOSMIZkCyJ3w dilg/TNrj761nzpnwZq0ND2FR74rINfHt18xmOcs6T+tuNaJivqtqoeNV0NngLa+Lzxh earr61RTrvEyKOK6jWCTOwmeegWfoWgVPJqupVWHuAXIYfAeIDbRC+fFr1r/XfpbRLuO f4khog6vX1eTqVZU5sFIUrdepZjpZdKoDh1gYr2DbbHUad4vME2inkRRB9Fts1vzHsr6 s+6A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:date:message-id:subject:from :to; bh=8fJEklDW8N+wHuxmzhFTYbe/ztyQLkVDdfKI8WUBfss=; b=YycvESkZRJ2RN14rz/Ao9JDSUD0LKr/43cuUZmmMJu/nOkx7pTdVyqKTb/q3r9+sjc cib1f0K1uk8NQ6TT1GRSLUon2CxceFDctSDkOKZdygK1H4cHoxX5n5LA8qEbIUFuOBdS IDhQe659vlDcHOUqMsBwD8dFm+EmyQfEamsRAPdiOVxt8zRn5QRMnoGBMWKBYV9L51YV mWKjnVLBNi5YX51ZUyTxp95/8z9wCHuCTwZuROkO6q0+S3LmEZXPSJWWGP80vyqqcCZQ JixJOM6rYZUZuDd6Qvr/tAdN6pvOxj87rJ5EeHflFbI+8vfu6waGlCIE+vKw0OsU4yO6 RkIA== X-Gm-Message-State: AOPr4FUjep6unGNIjAtSKHcp6R3ZUX6JW6/2KCwle1zaRv4Ktk2HLwCIvGHupBYtZ2YVVG1dgIqWRx95NInEIg== MIME-Version: 1.0 X-Received: by 10.157.12.210 with SMTP id o18mr3054001otd.192.1462330543553; Tue, 03 May 2016 19:55:43 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.202.64.138 with HTTP; Tue, 3 May 2016 19:55:43 -0700 (PDT) Date: Tue, 3 May 2016 20:55:43 -0600 X-Google-Sender-Auth: yAD9Xxq6YAHicVmaI6GbnqBJpfE Message-ID: Subject: How to use pf with vimage jails? From: Alan Somers To: FreeBSD Net Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 04 May 2016 02:55:44 -0000 Is there any documentation on how to run pf on a host, using it to control access to vimage jails? I see that only ipfw can be run from _inside_ of the jail, but I'm interested in running pf _outside_ of the jail. One example application would be to use a jail as a honeypot. In that case, you wouldn't trust the jail to control its own firewall. Another would be to use jails as a poor man's DMZ. -Alan From owner-freebsd-net@freebsd.org Wed May 4 10:23:44 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B8CEB2B878 for ; Wed, 4 May 2016 10:23:44 +0000 (UTC) (envelope-from kristof@sigsegv.be) Received: from venus.codepro.be (venus.codepro.be [IPv6:2a01:4f8:162:1127::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.codepro.be", Issuer "Gandi Standard SSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0BE181AA0; Wed, 4 May 2016 10:23:43 +0000 (UTC) (envelope-from kristof@sigsegv.be) Received: from [IPv6:::1] (vega.codepro.be [IPv6:2a01:4f8:162:1127::3]) (Authenticated sender: kp) by venus.codepro.be (Postfix) with ESMTPSA id 3835B756D; Wed, 4 May 2016 12:23:40 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sigsegv.be; s=mail; t=1462357420; bh=71iW9ST0kRBIX4ZWUCZ2BGI3Z52jRCroxqG4giwTw30=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=cpdZUqRDV4OwMJYHElzpwCxTQB82qUJNvxLVDnGfctzEOmpZzMQuaqRHzbtI6gUgP rWz0OY4CoV9FLxCVVBLJQhUYzxo1A7kcVSx3YIjN2VF6nrZJGj34pSEr2vYx4eFKL2 kb4FEWAuQYeYQew5DC3oNiEWUILxk7PSGECjqQM4= Subject: Re: How to use pf with vimage jails? Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Content-Type: text/plain; charset=utf-8 From: Kristof Provost X-Checked-By-Nsa: Probably In-Reply-To: Date: Wed, 4 May 2016 12:23:40 +0200 Cc: FreeBSD Net Content-Transfer-Encoding: quoted-printable Message-Id: <67045371-07B8-4718-8A8B-98E3FBFF994E@sigsegv.be> References: To: Alan Somers X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 04 May 2016 10:23:44 -0000 > On 04 May 2016, at 04:55, Alan Somers wrote: >=20 > Is there any documentation on how to run pf on a host, using it to = control > access to vimage jails? I see that only ipfw can be run from _inside_ = of > the jail, but I'm interested in running pf _outside_ of the jail. =20 That=E2=80=99s supported, and really no different from configuring pf = otherwise. Just treat the vimage jails as if they were on different machines, = behind your firewall. Regards, Kristof From owner-freebsd-net@freebsd.org Wed May 4 14:48:55 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 87294B2D165 for ; Wed, 4 May 2016 14:48:55 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3F33A1B9E for ; Wed, 4 May 2016 14:48:55 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-ob0-x236.google.com with SMTP id x1so21689318obt.0 for ; Wed, 04 May 2016 07:48:55 -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:message-id:subject :from:to:cc; bh=sQF6EoGltYGKllfjpKp7TjopP0LJFYj3jsDP8J9xi6M=; b=BvlT6m7vjKB2ePEpLF35TvcMEhbVHaLn3/xGkpSd/hD7P/rskZaMNhtBdFwPWr6v9C R4PMdpPV/d+/StO8wO6ReiFZGIJNzUNTYDx3DkMgTl2HOEZbAxoVTcIEbVJSnK9RWEF/ +Z+UoZR1U1lvRkCpodEuxK4vyb9E6AY4KDcMSR3/rbfWvgjhEP6PL9VAq6MkLasI79/G JMfTJe5hboBCzYuOggYDdrleEJ1klwQP/BHDyjO0khrrfLMWVMoJI6Cl/A4jZ6ElHVwl w3Lec/n5F0z5Int4AYBH+MQBXVH0fouNobf3hJBRHPEG2yHLWLMvJgPkuwIgU/US/QN3 qnEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=sQF6EoGltYGKllfjpKp7TjopP0LJFYj3jsDP8J9xi6M=; b=Z5gvbwc3mJpcI/CCJpA9qkx/ZqJxnpxRZeNeP79Uue03kaqVeuHHQS2XcIHxFYSx7H a16UucBE7MPQ0p072b+1930rYOVjs9dZuoGhqgwOyq8UypzkonrmYAXuhp68bZ/ecI3N V7mbuTSbo3qN5KxauJ13KZl0guj6fCQxL6xXP9cVfJmbQVZmGHdLoamVbjZiQLXN9UIl gZe2eXkPE606773fBVBaA+rn8UoGbWAOxrBGAPM5viYf7avl8ZgSzczY3ODUHDrHAU3p GyXmHWsM2sl3C1JpNblL0NrmzhDhSiRjIxZ4P3mYfc3oLCKcnB2dzDdNe3aZ58wAeURB +9Uw== X-Gm-Message-State: AOPr4FXpGY0u3FoBhjxJUUEmB7NXWcqUjZtajtL9KdRsT+CD0iKr+Nb3apSe9iwiDL7ScerrVY5ApZsvw3UKZg== MIME-Version: 1.0 X-Received: by 10.182.232.168 with SMTP id tp8mr4226012obc.65.1462373334428; Wed, 04 May 2016 07:48:54 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.202.64.138 with HTTP; Wed, 4 May 2016 07:48:54 -0700 (PDT) In-Reply-To: <67045371-07B8-4718-8A8B-98E3FBFF994E@sigsegv.be> References: <67045371-07B8-4718-8A8B-98E3FBFF994E@sigsegv.be> Date: Wed, 4 May 2016 08:48:54 -0600 X-Google-Sender-Auth: sagLvvmS_iXhYgVWSRs8M2yXNNA Message-ID: Subject: Re: How to use pf with vimage jails? From: Alan Somers To: Kristof Provost Cc: FreeBSD Net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 04 May 2016 14:48:55 -0000 On Wed, May 4, 2016 at 4:23 AM, Kristof Provost wrote: > > > On 04 May 2016, at 04:55, Alan Somers wrote: > > > > Is there any documentation on how to run pf on a host, using it to > control > > access to vimage jails? I see that only ipfw can be run from _inside_ = of > > the jail, but I'm interested in running pf _outside_ of the jail. > > That=E2=80=99s supported, and really no different from configuring pf oth= erwise. > Just treat the vimage jails as if they were on different machines, behind > your firewall. > > Regards, > Kristof > > Then maybe it's the bridged aspect that's screwing me up. Is there a guide for using pf on bridged interfaces? All I can find is this guide for ipfw. https://www.freebsd.org/doc/en/articles/filtering-bridges/article.html -Alan From owner-freebsd-net@freebsd.org Wed May 4 14:54:04 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2048BB2D2B6 for ; Wed, 4 May 2016 14:54:04 +0000 (UTC) (envelope-from kristof@sigsegv.be) Received: from venus.codepro.be (venus.codepro.be [IPv6:2a01:4f8:162:1127::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.codepro.be", Issuer "Gandi Standard SSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B54DB1EE9; Wed, 4 May 2016 14:54:03 +0000 (UTC) (envelope-from kristof@sigsegv.be) Received: from [IPv6:::1] (vega.codepro.be [IPv6:2a01:4f8:162:1127::3]) (Authenticated sender: kp) by venus.codepro.be (Postfix) with ESMTPSA id 934DA324B8; Wed, 4 May 2016 16:54:00 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sigsegv.be; s=mail; t=1462373640; bh=u6s6H2B4UTJFMJxoGxabqgQ8/cmCq91FhIzCB7/Ov5s=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=tDxAvzbaF5F3LJVGGElH2e/0RrInVQ96VOnx+sBholQkSsCoWF8vOfBoArKwahaJN 0HMBwcxzZAhML6WiCT8bDP1cG18e1pANIWl8X+Qb+qSzOZ91k5jVwOAguPq/6ZdLXC 0iXHtKn3V1Bq2Cwly9QnUAtjBn6IsPoKEiAnyCj8= Subject: Re: How to use pf with vimage jails? Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Kristof Provost X-Checked-By-Nsa: Probably In-Reply-To: Date: Wed, 4 May 2016 16:53:59 +0200 Cc: FreeBSD Net Message-Id: <4EBFFB72-B185-4272-ACDF-B6B576ADE0D2@sigsegv.be> References: <67045371-07B8-4718-8A8B-98E3FBFF994E@sigsegv.be> To: Alan Somers X-Mailer: Apple Mail (2.3124) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 04 May 2016 14:54:04 -0000 > On 04 May 2016, at 16:48, Alan Somers wrote: >=20 > On Wed, May 4, 2016 at 4:23 AM, Kristof Provost > wrote: >=20 > > On 04 May 2016, at 04:55, Alan Somers > wrote: > > > > Is there any documentation on how to run pf on a host, using it to = control > > access to vimage jails? I see that only ipfw can be run from = _inside_ of > > the jail, but I'm interested in running pf _outside_ of the jail. >=20 > That=E2=80=99s supported, and really no different from configuring pf = otherwise. > Just treat the vimage jails as if they were on different machines, = behind your firewall. >=20 > Regards, > Kristof >=20 >=20 > Then maybe it's the bridged aspect that's screwing me up. Is there a = guide for using pf on bridged interfaces? All I can find is this guide = for ipfw. >=20 Treat a bridge as a simple interface, pretend that the bridge members = are just devices plugged into a switch connected to the bridge = interface. > https://www.freebsd.org/doc/en/articles/filtering-bridges/article.html = >=20 That=E2=80=99s a filtering bridge, which is a different use case. On a = filtering bridge the firewall device doesn=E2=80=99t need an IP, instead = interpreting the layer 2 packets. pf can do this (see the net.link.bridge.pfil_bridge sysctl), but there = are major problems with the implementation. I=E2=80=99d discourage you = from using this. Regards, Kristof From owner-freebsd-net@freebsd.org Wed May 4 15:59:25 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA40DB2B21B for ; Wed, 4 May 2016 15:59:25 +0000 (UTC) (envelope-from sd@beastie.io) Received: from beastie.io (beastie.io [104.236.166.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "beastie.io", Issuer "StartCom Class 1 DV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D92AD1763; Wed, 4 May 2016 15:59:25 +0000 (UTC) (envelope-from sd@beastie.io) Received: from beastie.io (localhost [127.0.0.1]) by beastie.io (OpenSMTPD) with ESMTPS id 062c4538 TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Wed, 4 May 2016 15:59:17 +0000 (UTC) Received: (from sd@localhost) by beastie.io (8.15.2/8.15.2/Submit) id u44FxGK1019198; Wed, 4 May 2016 15:59:16 GMT (envelope-from sd@beastie.io) Date: Wed, 4 May 2016 15:59:15 +0000 From: Shawn Debnath To: Alan Somers Cc: Kristof Provost , FreeBSD Net Subject: Re: How to use pf with vimage jails? Message-ID: <20160504155915.GD4796@beastie.io> References: <67045371-07B8-4718-8A8B-98E3FBFF994E@sigsegv.be> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0 (2016-04-01) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 04 May 2016 15:59:26 -0000 On 05/04, Alan Somers wrote: > Then maybe it's the bridged aspect that's screwing me up. Is there a guide > for using pf on bridged interfaces? All I can find is this guide for ipfw. I ran into a similar issue recently and decided to write up an article on my site that documents how to set up jails with VNET/VIMAGE using a bridge on the host. This might help you: http://shawndebnath.com/articles/2016/03/27/freebsd-jails-with-vlan-howto.html If you see any errors, do let me know and I will get those fixed up. Thanks, Shawn From owner-freebsd-net@freebsd.org Wed May 4 17:08:48 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B2AF3B2C522 for ; Wed, 4 May 2016 17:08:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 95174111A for ; Wed, 4 May 2016 17:08:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u44H8lSF026918 for ; Wed, 4 May 2016 17:08:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 176419] [kernel] [patch] socketpair support for LOCAL_PEERCRED Date: Wed, 04 May 2016 17:08:47 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eto.freebsd@ethome.sk X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 04 May 2016 17:08:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D176419 Martin eto Misuth changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eto.freebsd@ethome.sk --- Comment #2 from Martin eto Misuth --- I think I hit this recently as well. Man page contains wording: [ENOTCONN] The argument s does not refer to a socket on which connect(2) or listen(2) have been called. Which actually describes situation exactly, but it is bit non-obvious that = it also means implicit exclusion of socktepair(). More over, as mentioned by nicholas, other system I tried (Linux) supports getting this information about socketpair() created sockets. I have not yet tried OS X. I wanted to use this to verify socket owner credentials (usually parent process), before consuming data from it, in scripted environment. Unfortunately, this feature can be used only when I go through fs namespace= . I don't know how these "anonymous" sockets (created by socketpair()) are implemented internally but, I think creating socket files in my situation is kinda wasteful. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed May 4 19:33:57 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 862B3B2D625 for ; Wed, 4 May 2016 19:33:57 +0000 (UTC) (envelope-from testdog@hotmail.com) Received: from BLU004-OMC2S26.hotmail.com (blu004-omc2s26.hotmail.com [65.55.111.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 450721F89 for ; Wed, 4 May 2016 19:33:56 +0000 (UTC) (envelope-from testdog@hotmail.com) Received: from BLU172-W20 ([65.55.111.72]) by BLU004-OMC2S26.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Wed, 4 May 2016 12:33:50 -0700 X-TMN: [GJrQ88FqMFXBprwigf7+PkSq/AgtsY8C] X-Originating-Email: [testdog@hotmail.com] Message-ID: From: Wayne H To: "freebsd-net@freebsd.org" Subject: Not able to raise the MTU on FreeBSD 10.3 Date: Wed, 4 May 2016 19:33:50 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 04 May 2016 19:33:50.0808 (UTC) FILETIME=[E2C1AD80:01D1A63B] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 04 May 2016 19:33:57 -0000 I have two new servers connected together with 10 gig Intel and 1 gig Nic= cards. It doesn't matter if I have them connected via a switch or directly= connected to each other. I am unable to pass ping packets above 1472. If I= set the MTU to anything up to 9000 I till can't pass anything above 1472. = I have the 10 gig connected via an Intel SFP+ Cable between the servers. I = also tried connecting the 1 gig Nics between the servers. I would like to use jumbo frames to mount these servers to a NFS server. If= I set the MTU to 9000 in rc.conf on boot up I can mount the NFS but as soo= n as I try to write to it the NFS hangs. If I umount and reset the MTU to 1= 500 it works fine. Anyone know what I am doing wrong? root@backgate1:/usr/home/wayne # ping -D -s 1472 10.168.48.145 PING 10.168.48.145 (10.168.48.145): 1472 data bytes 1480 bytes from 10.168.48.145: icmp_seq=3D0 ttl=3D64 time=3D0.111 ms 1480 bytes from 10.168.48.145: icmp_seq=3D1 ttl=3D64 time=3D0.059 ms ^C --- 10.168.48.145 ping statistics --- 2 packets transmitted=2C 2 packets received=2C 0.0% packet loss round-trip min/avg/max/stddev =3D 0.059/0.085/0.111/0.026 ms root@backgate1:/usr/home/wayne # ping -D -s 1473 10.168.48.145 PING 10.168.48.145 (10.168.48.145): 1473 data bytes ping: sendto: Message too long ping: sendto: Message too long ^C --- 10.168.48.145 ping statistics --- 2 packets transmitted=2C 0 packets received=2C 100.0% packet loss FreeBSD 10.3-RELEASE #0 r297264: Fri Mar 25 02:10:02 UTC 2016 root@rele= ng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC Intel(R) Ethernet Connection XL710 Driver=2C Version - 1.4.3 ixl0@pci0:5:0:0: class=3D0x020000 card=3D0x00078086 chip=3D0x1572808= 6 rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Ethernet Controller X710 for 10GbE SFP+' class =3D network ntel(R) PRO/1000 Network Connection=2C Version - 2.5.3-k =20 igb0@pci0:11:0:0: class=3D0x020000 card=3D0x152115d9 chip=3D0x1521808= 6 rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'I350 Gigabit Network Connection' class =3D network ixl0: flags=3D8843 metric 0= mtu 9000 options=3D6407bb ether 3c:fd:fe:9d:5c:24 inet 10.168.48.144 netmask 0xffffff00 broadcast 10.168.48.255 nd6 options=3D29 media: Ethernet autoselect (10Gbase-Twinax ) status: active igb0: flags=3D8843 metric 0= mtu 9000 options=3D403bb ether 0c:c4:7a:32:f0:51 inet 172.16.48.244 netmask 0xffffff00 broadcast 172.16.48.255 nd6 options=3D29 media: Ethernet autoselect (1000baseT ) status: active Thanks = From owner-freebsd-net@freebsd.org Wed May 4 19:45:25 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A33AB2D8A4 for ; Wed, 4 May 2016 19:45:25 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0412A1515 for ; Wed, 4 May 2016 19:45:24 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.14.9/8.14.9) with ESMTP id u44JjELJ061140 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 4 May 2016 21:45:15 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: freebsd-net@freebsd.org Received: from [10.58.0.10] (dadvw [10.58.0.10]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id u44Jj58U087937 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 5 May 2016 02:45:06 +0700 (KRAT) (envelope-from eugen@grosbein.net) Subject: Re: Not able to raise the MTU on FreeBSD 10.3 To: Wayne H , "freebsd-net@freebsd.org" References: From: Eugene Grosbein Message-ID: <572A513D.5080904@grosbein.net> Date: Thu, 5 May 2016 02:45:01 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM autolearn=no version=3.3.2 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 04 May 2016 19:45:25 -0000 05.05.2016 2:33, Wayne H пишет: > I have two new servers connected together with 10 gig Intel and 1 gig Nic cards. It doesn't matter if I have them connected via a switch or directly connected to each other. I am unable to pass ping packets above 1472. If I set the MTU to anything up to 9000 I till can't pass anything above 1472. I have the 10 gig connected via an Intel SFP+ Cable between the servers. I also tried connecting the 1 gig Nics between the servers. > > I would like to use jumbo frames to mount these servers to a NFS server. If I set the MTU to 9000 in rc.conf on boot up I can mount the NFS but as soon as I try to write to it the NFS hangs. If I umount and reset the MTU to 1500 it works fine. > > Anyone know what I am doing wrong? First increase MTU, then assign IP address. Or delete it and reassign after increase of MTU to recreate "interface route" having its own MTU inherited by interface MTU. This MTU of the "interface route" limits you and it is not changed automatically with interface MTU in your version of FreeBSD. From owner-freebsd-net@freebsd.org Wed May 4 19:53:01 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4C81FB2DA9D for ; Wed, 4 May 2016 19:53:01 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1D1BF1A9E for ; Wed, 4 May 2016 19:53:01 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-io0-x232.google.com with SMTP id d62so65165274iof.2 for ; Wed, 04 May 2016 12:53:01 -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; bh=bIhlpQ2CprzI/9EWE4nEkYzNemhT62nOgUY0PZa+L0o=; b=Y6YHZOQZgNIKkhbLeAv880AEiByexy7vNUcZ03JqKliyV3iyKmU+BHovu4k91dH8Ld wB2oeidSW4PSNw1SpA79xBW3mNBnWW31vgCuCiBlwb26RQR6Dje6D0HVBvhxA6wdOAyH zY/ucZYq09ZXQ4JckLPsFKYu5jauIXialGISJJg7asnVFQEwkRqZPOW3r3xmT8+lpSo7 l9a3vtrIKhiPYyjuusFZCG3zlpE5Fw1Ky/lFK6L1FaoNzZFZxJ2Upqc0oeaR3fKlCvAB uHFZ4gxiemE22EO4HkPtIoMjStcZqasZI/QddBQcp/8B8kkqZmwvOR8B5i8FQ1wkPECR sfbA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=bIhlpQ2CprzI/9EWE4nEkYzNemhT62nOgUY0PZa+L0o=; b=hv6BkMasor2JObBMoTmhpWRymsK/xJluu9p6NG/KcfYJsd6p6p0gCmJXugdzwnMnCZ enJFmulehvygNtTVYu9Tyupp51H7K1ZC9VdDC0OnAHXMb5PT8j2EzJxCiRHVTJZqQf2B v51mVph74dUU5VzJ6m5FkFhVPNT4762pKvLgMntqpAj/k6q/pfv7nuIvXFPRh5vmjc1n Lnzbh8mF7f3i5kB7OdDJAGWHJniwxwwnIlqYH5JIyeShUfDRPvExpvkzQ5blFLJxE1+d 0tiMzPxdvPYWTOz0Z78y91Zbgod/LXCzXIWOgLvkrwEI9gVyEmFFWBnRhTYb2nQX8LST KCUQ== X-Gm-Message-State: AOPr4FUJcxhuOSTdD/yu9ILLGq+yPMdkStnmJs4ta7TkcUs79EMI2HQO1nrVneLUQgkPV3NOPtPOer0sD75zRA== MIME-Version: 1.0 X-Received: by 10.107.134.24 with SMTP id i24mr12778416iod.130.1462391580593; Wed, 04 May 2016 12:53:00 -0700 (PDT) Received: by 10.107.161.6 with HTTP; Wed, 4 May 2016 12:53:00 -0700 (PDT) In-Reply-To: <572A513D.5080904@grosbein.net> References: <572A513D.5080904@grosbein.net> Date: Wed, 4 May 2016 12:53:00 -0700 Message-ID: Subject: Re: Not able to raise the MTU on FreeBSD 10.3 From: Freddie Cash To: Eugene Grosbein Cc: Wayne H , "freebsd-net@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 04 May 2016 19:53:01 -0000 On Wed, May 4, 2016 at 12:45 PM, Eugene Grosbein wrote= : > 05.05.2016 2:33, Wayne H =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > >> I have two new servers connected together with 10 gig Intel and 1 gig >> Nic cards. It doesn't matter if I have them connected via a switch or >> directly connected to each other. I am unable to pass ping packets above >> 1472. If I set the MTU to anything up to 9000 I till can't pass anything >> above 1472. I have the 10 gig connected via an Intel SFP+ Cable between = the >> servers. I also tried connecting the 1 gig Nics between the servers. >> >> I would like to use jumbo frames to mount these servers to a NFS server. >> If I set the MTU to 9000 in rc.conf on boot up I can mount the NFS but a= s >> soon as I try to write to it the NFS hangs. If I umount and reset the MT= U >> to 1500 it works fine. >> >> Anyone know what I am doing wrong? >> > > First increase MTU, then assign IP address. > Or delete it and reassign after increase of MTU to recreate "interface > route" having its own MTU > inherited by interface MTU. This MTU of the "interface route" limits you > and it is not changed > automatically with interface MTU in your version of FreeBSD. > =E2=80=8BYou can also manually delete and re-add the route with the -mtu op= tion, if you don't want to drop/add the IP.=E2=80=8B --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-net@freebsd.org Wed May 4 21:22:17 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 54F6DB2DAD9 for ; Wed, 4 May 2016 21:22:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3EAE41D78 for ; Wed, 4 May 2016 21:22:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u44LMHJH022614 for ; Wed, 4 May 2016 21:22:17 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 209270] [igmp] logic error in igmp_v3_suppress_group_record Date: Wed, 04 May 2016 21:22:17 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ngie@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 04 May 2016 21:22:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209270 Ngie Cooper changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org CC| |bms@FreeBSD.org --- Comment #1 from Ngie Cooper --- This change has been in since 2009: 71233409e (bms 2009-03-09 17:53:05 +0000 1939) if (inm->inm_state = !=3D IGMP_G_QUERY_PENDING_MEMBER || 71233409e (bms 2009-03-09 17:53:05 +0000 1940) inm->inm_state = !=3D IGMP_SG_QUERY_PENDING_MEMBER) 71233409e (bms 2009-03-09 17:53:05 +0000 1941) return; I agree with this likely being a logic error. Forwarding over to net@ for inspection though. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu May 5 00:23:34 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5DAC7B2BCC8 for ; Thu, 5 May 2016 00:23:34 +0000 (UTC) (envelope-from vangyzen@FreeBSD.org) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [199.48.133.146]) by mx1.freebsd.org (Postfix) with ESMTP id 3ADE21B0D for ; Thu, 5 May 2016 00:23:33 +0000 (UTC) (envelope-from vangyzen@FreeBSD.org) Received: from blue.beer.town (unknown [76.164.15.242]) by smtp.vangyzen.net (Postfix) with ESMTPSA id 61043564B8; Wed, 4 May 2016 19:23:27 -0500 (CDT) Subject: Re: setsourcefilter/getsourcefilter missing const qualifier? To: Victor Toni , freebsd-net@freebsd.org References: From: Eric van Gyzen Message-ID: Date: Wed, 4 May 2016 19:23:26 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 05 May 2016 00:23:34 -0000 On 05/ 3/16 03:50 PM, Victor Toni wrote: > When trying to compile some linux-originated code on FreeBSD I get the > following errors: > > /usr/include/netinet/in.h:585:5: note: candidate function not viable: 3rd > argument ('const sockaddr *') would lose const qualifier > int setsourcefilter(int, uint32_t, struct sockaddr *, socklen_t, > ^ > /usr/include/netinet/in.h:587:5: note: candidate function not viable: 3rd > argument ('const sockaddr *') would lose const qualifier > int getsourcefilter(int, uint32_t, struct sockaddr *, socklen_t, > ^ > > the main difference is that the linux version makes guarantees about > the parameters. > > > Wouldn't it be safe for the FreeBSD version to make the same assumption? Yes, it would be safe in practice, since the implementation does not modify those parameters. However, RFC 3678 does not specify them as const, and neither do illumos (Solaris) and Mac OS X, so code that tries to pass const parameters is not portable. I would suggest changing the code to pass non-const parameters. Eric From owner-freebsd-net@freebsd.org Thu May 5 00:29:09 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DADC7B2BDF7 for ; Thu, 5 May 2016 00:29:09 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 972DE1C84; Thu, 5 May 2016 00:29:09 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: by mail-qk0-x233.google.com with SMTP id x7so35382708qkd.3; Wed, 04 May 2016 17:29:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:mime-version; bh=x1PS99j/4HUygoruUdcG2EP7lPjcUU2MQzk3zGBMPwY=; b=hWNlBgfI0g0LQQE93qGukYH8NmlGwnTerAcykjDuK4BYueFn8cyWhvT4tmJRJkaM5j wkaGn9H21epG9lS9QYi6YuHDiDsSe02xSZnjGlvT9GnO64OKh3t/3zkTVw8ZfAqew9TR 16QAaO5UcGj39IslVu7ATL0ADHJ5lBvNx5U03MCSb+H/LNnd3a66jF4u+/QGhW2Vdy0y zJ4r80vekEpnXn2zjLIPE4eZxarEHE1RW8/B1vbaLY0t6T2zusxOsxYgEMO3/+EiufDe rK4k3MH3Ryambx6XCbSgbER/htV52HtyXyXb4WpFRhCQpttXVc9XVPJpHaZirKBj+HGK xX3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version; bh=x1PS99j/4HUygoruUdcG2EP7lPjcUU2MQzk3zGBMPwY=; b=FN+f29XhSLKJFTRznUCPfanNgAI5EZWQfCNpwu48glFJhKF3zkNxVBzaSah6dIh6wl V4pu6bmjcWx4PES++NPXzTR2gg2irr8egRhlEd5tCpUutsC/vhAxlsuMZQCU7OtKerNh 0c5jZlt4OfmLJt75FDdkSfr0qo+cQLR/s3x+FCyLSpaCymXBeN/NlV1UNVLqgAON5xFj sV73T0Zd5FMu4K1xK/dt2L3hcQ8kNKc9NBJOmfzbTDG9gBhw8N3hTYDdwoa+P6hqoo2X pKgeoC5gM/+3hESvLsWdVyoUHOk8rn2v61OXMTJesWdET0fiCTz+E1+4Y3Ifa6IVo1Mo P6hQ== X-Gm-Message-State: AOPr4FVwtjAFGHoGBuNvVz0AARYEebG3Y58t8ymhuEWOMMHSYmwRNZvW6aOnIvgr6/eW5g== X-Received: by 10.55.159.136 with SMTP id i130mr11672137qke.29.1462408148798; Wed, 04 May 2016 17:29:08 -0700 (PDT) Received: from kan ([2601:18f:802:4680:226:18ff:fe00:232e]) by smtp.gmail.com with ESMTPSA id l62sm2399304qge.13.2016.05.04.17.29.07 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 04 May 2016 17:29:07 -0700 (PDT) Date: Wed, 4 May 2016 20:28:51 -0400 From: Alexander Kabaev To: freebsd-net@freebsd.org Cc: "George V. Neville-Neil" , Mike Karels Subject: r297225 breaks option FLOWTABLE Message-ID: <20160504202851.28866e4e@kan> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/ilJH8ooPK9zAKymijbcifso"; protocol="application/pgp-signature" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 05 May 2016 00:29:10 -0000 --Sig_/ilJH8ooPK9zAKymijbcifso Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi, due to reasons now unknown, I had 'options FLOWTABLE' in my kernel config and -current did panic on boot up after I updated it from the tree as of March 19 to r299065. I did not save the exact panic backtrace as the affected system is not on the serial console and has no swap space, but it goes as follows: panic() rtfree() (net/route.c, line 507) in_pcbree() (netinet/in_pcb.c, line 1302) udp_detach() sofree() soclose() ... I did not debug any further. If I disable flowtable, kernel works fine. If I revert the r297225 alone, kernel also works fine with or without flowtable enabled. --=20 Alexander Kabaev --Sig_/ilJH8ooPK9zAKymijbcifso Content-Type: application/pgp-signature Content-Description: Цифровая подпись OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJXKpPEXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDNUY3RDk5NTk5QjY0MUUxM0M1MTU2OTEw NzEzMjI5OTkyNzkyRTdFAAoJEAcTIpmSeS5+gvoQAJUYG8awRdkN+MTB5Dfpb3/D 9U2SFU2JV7kpUOTg46KrG5rzFOq4cnl8Ud27NO3TUhhXqcUar17pRb3y94IwMUdi lm4OQfydy0Ba1gfKnpFCi55wDhbSaKx15QA0cnMFhQVK/vA9Ptc0XI2nXT7FcXlG JYstyDMJHyqNaDWq+9cDs11gsQx0JnGGIFwqNDjCfPVpemTYYs6Pl/sGr24zVRnd /nkX6on5+AW9E8g58I+4gH0w+jiJUEV0mNqhSSfDxWsoTlmsAB4gfbDTKkPpuyfU FYEYXeL3T20QTyqHyjqLp76eq+OLjI1GutpqGg6A3gRESMu9RjQiVoELmPpEoYUg eRMjCxwYpCQ5y40vENUEdz5wU5e5SwRmp3GTgIQlKLLqkjS0JSF67mGWdYI1d2rw tdOdDuBv/LJfar3bs21TnLBpbfHVN6qrGdKOUfimlFMCdoLh2uo6InAF7Il6eO4B LsUY6lUmDMYT2YPJxqLTKm/yY7h4MiQmcMbAGX9mtYd4xgdsG/YdrFwYuZcJAGsV wIbmPXwFi07Hu90dEyAoHp4R9g1DdmzswZERdWdfcEcJpNOXT6bs/MBkc9GuzJJt Vmw9mYsmtb7pLZ+P5OexhjTuvyhVd/Wyd7trIGJZjQs3UwaIgqAWnKDLgZnes313 vgcS4VgPjIrZUpY4UJBE =cLhc -----END PGP SIGNATURE----- --Sig_/ilJH8ooPK9zAKymijbcifso-- From owner-freebsd-net@freebsd.org Thu May 5 05:50:20 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6F1BDB2E067 for ; Thu, 5 May 2016 05:50:20 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 328941042; Thu, 5 May 2016 05:50:19 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-225-151.lns20.per1.internode.on.net [121.45.225.151]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id u455o5a8098798 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 4 May 2016 22:50:08 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: How to use pf with vimage jails? To: Shawn Debnath , Alan Somers References: <67045371-07B8-4718-8A8B-98E3FBFF994E@sigsegv.be> <20160504155915.GD4796@beastie.io> Cc: Kristof Provost , FreeBSD Net From: Julian Elischer Message-ID: <3ed0ddc2-3439-19fb-3075-8b5079cc5731@freebsd.org> Date: Thu, 5 May 2016 13:49:59 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <20160504155915.GD4796@beastie.io> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 05 May 2016 05:50:20 -0000 On 4/05/2016 11:59 PM, Shawn Debnath wrote: > On 05/04, Alan Somers wrote: >> Then maybe it's the bridged aspect that's screwing me up. Is there a guide >> for using pf on bridged interfaces? All I can find is this guide for ipfw. > I ran into a similar issue recently and decided to write up an article on > my site that documents how to set up jails with VNET/VIMAGE using a bridge > on the host. This might help you: > > http://shawndebnath.com/articles/2016/03/27/freebsd-jails-with-vlan-howto.html > > If you see any errors, do let me know and I will get those fixed up. devin just committed some sample code to share/examples https://svnweb.freebsd.org/base/head/share/examples/jails/ there is also some code in https://svnweb.freebsd.org/base/head/share/examples/netgraph/ that may be relevant, but uses netgraph bridging. > > Thanks, > Shawn > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@freebsd.org Thu May 5 13:09:06 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4EC14B2C9FA for ; Thu, 5 May 2016 13:09:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3FAED170B for ; Thu, 5 May 2016 13:09:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u45D95MV007310 for ; Thu, 5 May 2016 13:09:06 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 203031] LACP problem with FreeBSD 10.2-RELEASE Date: Thu, 05 May 2016 13:09:05 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: vnv099@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 05 May 2016 13:09:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203031 Nick changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vnv099@gmail.com --- Comment #5 from Nick --- I have same problem at two servers running freebsd 10.2 and using LACP. At = some time in log apper messages like=20 kernel: igb0: Interface stopped DISTRIBUTING, possible flapping kernel: igb1: Interface stopped DISTRIBUTING, possible flapping and LA goes high to 30-40. Tried to updade to 10.3 but got same problem. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu May 5 19:43:34 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF51CB2F64B for ; Thu, 5 May 2016 19:43:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BFBC41A8A for ; Thu, 5 May 2016 19:43:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u45JhVfC091917 for ; Thu, 5 May 2016 19:43:34 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 193802] tso seems broken on RELENG10 for version 7.4.2 of em driver Date: Thu, 05 May 2016 19:43:31 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: sbruno@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 05 May 2016 19:43:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D193802 Sean Bruno changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|In Progress |Closed --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri May 6 04:16:19 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3F7BCB2F6F6 for ; Fri, 6 May 2016 04:16:19 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 16A901058; Fri, 6 May 2016 04:16:19 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi0-x22c.google.com with SMTP id x201so126524366oif.3; Thu, 05 May 2016 21:16:18 -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:message-id:subject :from:to:cc; bh=FpxdqDO6nfiQLywttwJGgG3RHnEpMt/ZngppOJGx5hY=; b=ROc7gHsjpSAJMY4CL47yo0685J0ffB7qpxg0xRQYuBAgjC4+DwJLQflwxTHRHygi+H f4QLTqfvTTMnLNz4ULwbgANr3eGwc0tvi0z/pmcP+AwO2RNc21hlyahGSHjqR5xjJVdS X/JbpX++yvUxNzV5pSKBfbH/7HsJ4YU1mTAWfPqmU1w/qeyEnv79cltdaO+Cj+nDkgSb RcK3Xj3kukDC0SyoA5ejCfnV4IVJ/1FXGG8gaQCZfdOg+vW5WkNt7gT/e6vaaE/dLQf+ YStwlUM7Av+sobiDaX+ehzDCafHD2LexcW0sNLDYikhoP/ZmziJlMy3KN/FtdnGFnMjS uPLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=FpxdqDO6nfiQLywttwJGgG3RHnEpMt/ZngppOJGx5hY=; b=AYf6V0eFjwTl15uO6P+IZCUCc5I9x2fsOYGBGYcTzSrH1n8fTREwxlaKs3lCzLLIFx K430KgNnYzNnw53+sPrBPkIuweHWIjdBuA8AfRyrDIxY7IODh/RWqpQ+/s/FV3OJoLWp 5n3EBkxvLcITBw4q0WsQ9f5ppXFpIdXi+VlZ7d4xDwFS/rT4kynTM9/56QIpomfb7LTE 7C+rq5gWSgtk+epdebld5suOsL/GkAdK7KNA2q6ts033iHIOds9ppxw6zitdhHVbMIhf ahRc2PIb3Ph3fc9G0QRPyIb1koykYBbeawvOBDKIXqYBw68Az1Zg7o5CPV+eu35TJtUR E8hA== X-Gm-Message-State: AOPr4FUrpNRDsOvVdRqiWaYZYBrjd4ewtGTfiRDFHKETpaQA+QTao29SHxhQ0/i8YFvCh6IA29h3fJwzZbqoow== MIME-Version: 1.0 X-Received: by 10.202.73.72 with SMTP id w69mr3251136oia.176.1462508178344; Thu, 05 May 2016 21:16:18 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.202.64.138 with HTTP; Thu, 5 May 2016 21:16:18 -0700 (PDT) In-Reply-To: <3ed0ddc2-3439-19fb-3075-8b5079cc5731@freebsd.org> References: <67045371-07B8-4718-8A8B-98E3FBFF994E@sigsegv.be> <20160504155915.GD4796@beastie.io> <3ed0ddc2-3439-19fb-3075-8b5079cc5731@freebsd.org> Date: Thu, 5 May 2016 22:16:18 -0600 X-Google-Sender-Auth: C-AauRGkq4k3d3UQp_h5cM7ZZpI Message-ID: Subject: Re: How to use pf with vimage jails? From: Alan Somers To: Julian Elischer Cc: Shawn Debnath , Kristof Provost , FreeBSD Net Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2016 04:16:19 -0000 On Wed, May 4, 2016 at 11:49 PM, Julian Elischer wrote: > On 4/05/2016 11:59 PM, Shawn Debnath wrote: > >> On 05/04, Alan Somers wrote: >> >>> Then maybe it's the bridged aspect that's screwing me up. Is there a >>> guide >>> for using pf on bridged interfaces? All I can find is this guide for >>> ipfw. >>> >> I ran into a similar issue recently and decided to write up an article on >> my site that documents how to set up jails with VNET/VIMAGE using a bridge >> on the host. This might help you: >> >> >> http://shawndebnath.com/articles/2016/03/27/freebsd-jails-with-vlan-howto.html >> >> If you see any errors, do let me know and I will get those fixed up. >> > > devin just committed some sample code to share/examples > > https://svnweb.freebsd.org/base/head/share/examples/jails/ > > there is also some code in > https://svnweb.freebsd.org/base/head/share/examples/netgraph/ > > that may be relevant, but uses netgraph bridging. > > > >> Thanks, >> Shawn >> >> I finally found a configuration that works, but there were two surprises. First, I had to set net.link.bridge.pfil_member=1. Second, I essentially had to double all rules; they must be written once for the physical interface and once for the virtual interface. Here is an example pf.conf file: communication to the jail host uses em0 only. em1 is reserved as the bridge for various jails' vnet interfaces. The www jail uses vnet0. The rules allow inbound traffic only on ports 80 and 443, but any outbound traffic. www_services = "{ http, https }" host_iface = "em0" dmz_iface = "em1" www_jail_iface = "vnet0:1" www_ip = "192.168.0.40" set state-policy if-bound scrub in block in all block out all pass in on $host_iface pass out on $host_iface set skip on lo0 pass in on $dmz_iface pass out on $www_jail_iface proto tcp to $www_ip port $www_services pass in on $www_jail_iface keep state pass out on $dmz_iface Thanks for all the suggestions. -Alan From owner-freebsd-net@freebsd.org Fri May 6 07:54:57 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 572E2B30F3E for ; Fri, 6 May 2016 07:54:57 +0000 (UTC) (envelope-from rigging@honyuan.com) Received: from m97106.qiye.163.com (m97106.qiye.163.com [220.181.97.106]) by mx1.freebsd.org (Postfix) with ESMTP id E5FA51027 for ; Fri, 6 May 2016 07:54:37 +0000 (UTC) (envelope-from rigging@honyuan.com) Received: from rigging$honyuan.com ( [144.0.16.87] ) by ajax-webmail-wmsvr3 (Coremail) ; Fri, 6 May 2016 15:34:25 +0800 (CST) X-Originating-IP: [144.0.16.87] Date: Fri, 6 May 2016 15:34:25 +0800 (CST) From: Laura To: freebsd-net@freebsd.org Subject: Do you sale Carabiner and Snap hook X-Priority: 3 X-Mailer: Coremail Webmail Server Version SP_ntes V3.5 build 20150911(74783.7961) Copyright (c) 2002-2016 www.mailtech.cn 163-hosting MIME-Version: 1.0 Message-ID: <791fcfcb.14d09.15484fd2e7d.Coremail.rigging@honyuan.com> X-CM-TRANSID: auCowECpdUEBSSxXoaQjAA--.10W X-CM-SenderInfo: 5uljwxtqj6x0pq1xt0oofrz/1tbiOxxhblXJnEwEVAABs1 X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU== Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2016 07:54:57 -0000 RGVhciBTaXIKCk5pY2UgZGF5LCBIb3BlIHRoaXMgRW1haWwgZmluZCB5b3Ugd2VsbC4KClRoaXMg aXMgTGF1cmEsIGdlbmVyYWwgbWFuYWdlciBvZiBDaGluYSBIb255dWFuIE1hY2hpbmVyeSBDby4s TGltaXRlZC4KCldlIGFyZSBiZWluZyBvbmUgb2YgdGhlIGxlYWRpbmcgZXhwb3J0ZXIgZm9yIFJp Z2dpbmcgSGFyZHdhcmUsIENhcmFiaW5lciBhbmQgc25hcCBob29rIGluIENoaW5hLiAKCldlIHNw ZWNpYWxpemUgaW4gdGhlIG1hbnVmYWN0dXJlIG9mIGFsbCBraW5kcyBvZiBob29rcyBtYW55IHll YXJzLgoKSSB0aG91Z2h0IHlvdSBtaWdodCBiZSBpbnRlcmVzdGVkIGluIG91ciBwcm9kdWN0cyAK CldvdWxkIHlvdSBsaWtlIHRvIGdldCBzb21lIGZyZWUgc2FtcGxlcyBmb3IgdGVzdGluZywgbXkg ZnJpZW5kPwoKSWYgeW91IG5lZWQsSSBjYW4gc2VuZCB5b3UgbW9yZSBpbmZvcm1hdGlvbiBmb3Ig eW91LCBkZWFyIGZyaWVuZC4KCknigJltIGhlcmUgd2FpdGluZyBmb3IgeW91ciByZXBseS4KClRo YW5rcyEKCgoKCgoKLS0KCkJFU1QgUkVHQVJEUywKTGF1cmEgU1VOCkdlbmVyYWwgTWFuYWdlcgoy MDE2LTA1LTA2CiAKQ0hJTkEgSE9OWVVBTiBNQUNISU5FUlkgQ08uLExJTUlURUQKT0ZGSUNFIEFE RFJFU1M6Ck5vLjM4LENoYW5namlhbmcgRWFzdCBSb2FkLCBRaW5nZGFvIEVjb25vbWljIGFuZCBE ZXZlbG9wbWVudCBab25lLENoaW5hClRlbDogMDA4NiA1MzIgODYxMDY1MzYKTW9iaWxlOjAwODYg MTU5NjMyMDM2NzUsMTMzMjUwMjE2MTIKRmF4OjAwODYgNTMyIDg2MTA3MjM2ClNreXBlIElEOiBo b24geXVhbgpFbWFpbDogcmlnZ2luZ0Bob255dWFuLmNvbeKAjQpIdHRwOi8vd3d3Lmhvbnl1YW4u Y29tCg== From owner-freebsd-net@freebsd.org Fri May 6 15:41:53 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 818E8B2E4A6 for ; Fri, 6 May 2016 15:41:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7266D1ADF for ; Fri, 6 May 2016 15:41:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u46FfrPG077418 for ; Fri, 6 May 2016 15:41:53 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 208409] [PATCH] igb and ALTQ Date: Fri, 06 May 2016 15:41:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-BETA2 X-Bugzilla-Keywords: IntelNetworking, patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2016 15:41:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208409 --- Comment #6 from commit-hook@freebsd.org --- A commit references this bug: Author: sbruno Date: Fri May 6 15:41:38 UTC 2016 New revision: 299182 URL: https://svnweb.freebsd.org/changeset/base/299182 Log: If ALTQ is defined in the kern conf, switch to Legacy Mode. PR: 208409 Submitted by: freebsd@mcwest.org MFC after: 2 weeks Changes: head/sys/dev/e1000/if_igb.h --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri May 6 16:29:13 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 990C7B2EFA7 for ; Fri, 6 May 2016 16:29:13 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 8416A10FB for ; Fri, 6 May 2016 16:29:13 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yuri.doctorlan.com (c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id u46GTCLd027390 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 6 May 2016 09:29:12 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190] claimed to be yuri.doctorlan.com To: freebsd-net@freebsd.org From: Yuri Subject: Marvell Yukon (msk) network card causes the "sticky mouse" problem: mouse stops for extended periods of time Message-ID: <572CC657.8040207@rawbw.com> Date: Fri, 6 May 2016 09:29:11 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2016 16:29:13 -0000 When Marvell Yukon card is active on the desktop system, mouse periodically stops, sometimes for seconds. I think this also makes the system impaired in some other ways. The offending device: mskc0: port 0xd800-0xd8ff mem 0xfbdfc000-0xfbdfffff irq 18 at device 0.0 on pci6 msk0: on mskc0 When I replaced it with Linksys sk0 the problem is completely gone: skc0: port 0xe800-0xe8ff mem 0xfbefc000-0xfbefffff irq 17 at device 1.0 on pci8 There were few other problem reports about Marvell Yukon cards in this ML in 2015-2016. Yuri From owner-freebsd-net@freebsd.org Fri May 6 18:29:24 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7AE7AB31C84 for ; Fri, 6 May 2016 18:29:24 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from reviews.nyi.freebsd.org (reviews.nyi.freebsd.org [IPv6:2610:1c1:1:607c::16:b]) by mx1.freebsd.org (Postfix) with ESMTP id 5467D19A3 for ; Fri, 6 May 2016 18:29:24 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by reviews.nyi.freebsd.org (Postfix, from userid 1346) id 836F415603; Fri, 6 May 2016 18:29:23 +0000 (UTC) Date: Fri, 6 May 2016 18:29:23 +0000 To: freebsd-net@freebsd.org From: "sbruno (Sean Bruno)" Reply-to: D6148+325+ea9e78ec8d498ebd@reviews.freebsd.org Subject: [Differential] D6148: tcp/syncache: Add comment for syncache_respond Message-ID: <2fd7e81323ca9c067294b4feddaf0297@localhost.localdomain> X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , Thread-Topic: D6148: tcp/syncache: Add comment for syncache_respond X-Herald-Rules: <64> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: Y2FkNGI5OTYzNDYzYzgyNmZmMTk0MGY3OGYwIFcs4oM= MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2016 18:29:24 -0000 sbruno accepted this revision. REVISION DETAIL https://reviews.freebsd.org/D6148 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: sepherosa_gmail.com, network, transport, adrian, rwatson, gnn, lstewart, glebius, delphij, mike-karels.net, jtl, hiren, hselasky, sbruno Cc: freebsd-net-list From owner-freebsd-net@freebsd.org Fri May 6 19:00:18 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C656B31262 for ; Fri, 6 May 2016 19:00:18 +0000 (UTC) (envelope-from sonsechang@gmail.com) Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 58CAA16DB for ; Fri, 6 May 2016 19:00:18 +0000 (UTC) (envelope-from sonsechang@gmail.com) Received: by mail-qg0-x22c.google.com with SMTP id f74so61204449qge.2 for ; Fri, 06 May 2016 12:00:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=user-agent:date:subject:from:to:message-id:thread-topic :mime-version; bh=+TuWOGe/bjUW8V/Ryfi0pWk5hKnBlaNP2EOLN8JMvAA=; b=TP9PRc9aQ2iSkJek7JJHo7DWwd7TOoBRkOzmtcagq20V0ETpG7AI4RFlVmD9KlD7xO aKkxLAgvRrkkhiZxdFTCc7jH/T6xqCdykaXOBntwOHR+fWdvlf+xQqzB4xVrulADdJn3 8p3vPw9bFu+M0z0tgg6+O91z43pI0NdGo/I+VvqFxBVMOwzTU4v2HKimmAXNaujr68GB GY6vkZXmT2ngujRN+HcMAv4XqMrPMGEqixWKRkNibXZ13nbIHMlVm9OtEOvk5xuydm5h TBZVzIAk/hpoD2HTJNj+9sPpPYrgoy17bDHJain9eVFD43hscXxgefYwGX7RfbPH0JnL t7jg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:mime-version; bh=+TuWOGe/bjUW8V/Ryfi0pWk5hKnBlaNP2EOLN8JMvAA=; b=NZV2uaiN7QMArIHgFLHxbnlhJeyACj+5yN9wKt+btJ7cF40qeFfrUTX00TO/ioG17W wM0SbomdW6Gi1XKP2BkJig+ftCirroSbqo18Uf0/3EdLqByX7C5kpFiGErBruOPb+0FF 2xnYvzXMHqDIikKRPgd819J06jx2Luv2aylssSCiSWCg5dEYlaoFuCfDeZdM/hFUsheB aRg1s2YahJ1ewHWL3+Euu1pWtaiHoc94I5UfROxANvXbV5nMNSDqUB/DTpda5RUrx4Wv V6RVBEjOWs4d6H31eXa4mjnPN+kMNfsgwEWef6bSPglUnRj7vzpFFJ5JGSe2P3ZpdMh6 HLxQ== X-Gm-Message-State: AOPr4FVyvB+OqRqsAlHKZyr8AIP7z+3qgEtNVm2xGEKijqwM6X8aJ8Ffeveg4oucay7zrg== X-Received: by 10.140.96.100 with SMTP id j91mr21625434qge.10.1462561217573; Fri, 06 May 2016 12:00:17 -0700 (PDT) Received: from [10.63.221.111] ([216.240.30.5]) by smtp.gmail.com with ESMTPSA id 50sm6275569qgy.36.2016.05.06.12.00.15 for (version=TLSv1/SSLv3 cipher=OTHER); Fri, 06 May 2016 12:00:16 -0700 (PDT) User-Agent: Microsoft-MacOutlook/14.6.3.160329 Date: Fri, 06 May 2016 15:00:12 -0400 Subject: multipath tcp From: Sonny Son To: freebsd-net Message-ID: Thread-Topic: multipath tcp Mime-version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2016 19:00:18 -0000 Dear, I would like to try multipath TCP. Can somebody tell me what is the most recommended one? v0.51 seems to be the latest one. Is it the one that I should try? Thank you! From owner-freebsd-net@freebsd.org Sat May 7 00:11:30 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 88ED1B31ADF for ; Sat, 7 May 2016 00:11:30 +0000 (UTC) (envelope-from zclaudio@bsd.com.br) Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5357B1FC5 for ; Sat, 7 May 2016 00:11:30 +0000 (UTC) (envelope-from zclaudio@bsd.com.br) Received: by mail-ig0-x22e.google.com with SMTP id u10so60237866igr.1 for ; Fri, 06 May 2016 17:11:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=Wn4jn0h3C9yo2AxYRniVwQHXErHuuAzkNzS7ftwrBqo=; b=Pod8ndN2WbmKJTY1IIymwQII3BnqWE8yJWfDv3seJ1eT38WhRsTqUmaiZpYMCAT1TQ fPrZM9y6mcPIuI0n1X3UGw6AFziCl7nD+tK6YsJF6p65j+FTe1l147S3puWNTeUp5jxS j2ulgsQoDMTLBBzRjEqFPAXpRvahU5gKhk7IQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=Wn4jn0h3C9yo2AxYRniVwQHXErHuuAzkNzS7ftwrBqo=; b=ONvLyktVzy823WaS0teotuiA1dWmiupr5SsHT75kgz/O3jLqWNA9RmDxK8g9bCpoXS xL7CmqaItn//w1h9Qv6p0+d5rRxyOyJCwG3kid+lGfb+xFnR9fzojctjkkYCgzJPuovx 4pGmKjhPTaMtrlQdT4afZlDEpBzh5NEF9g0iWu1/qqpgTcrBwcTymp72IekOnYY07kYM mtt2VDLzIGyMZ4zAijpS95geQdXYSSM9w777upCl1LeO0EH0kz4Df87mZayqgzRSIVFd AS0Zpe72XzSs3ZSU4AHPLK0EA+/0fgmUyIpVrz6EWDMFiWxejrALPjdKCmaSjZfJrlIu wojA== X-Gm-Message-State: AOPr4FViJMFXIEBlftv8izZNGCSPJV4JmwYey1VIbho+zeKU+DJ5ZiJEUB/YB3endisVTKt50iqvI/QTkBm7GQ== MIME-Version: 1.0 X-Received: by 10.50.123.161 with SMTP id mb1mr353767igb.20.1462579889671; Fri, 06 May 2016 17:11:29 -0700 (PDT) Received: by 10.107.29.16 with HTTP; Fri, 6 May 2016 17:11:29 -0700 (PDT) In-Reply-To: References: Date: Fri, 6 May 2016 21:11:29 -0300 Message-ID: Subject: Re: Regression? VLAN packet drop after upgrading from r281235 From: Ze Claudio Pastore To: Ryan Stone Cc: freebsd-net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 07 May 2016 00:11:30 -0000 OK I submitted a Bug Report, if someone else get's a similar problem. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209351 2016-04-27 18:10 GMT-03:00 Z=C3=A9 Claudio Pastore : > Hello Ryan, > > 2016-04-27 17:28 GMT-03:00 Ryan Stone : > >> From a quick look at the vlan code, I can identify a few cases that migh= t >> cause that counter to increment: >> >> 1) Error from the underlying ixgbe device. Does "netstat -dI ix0" show >> that the driver has been dropping packets? >> > > No, it does not increase drop counters on ix port, only on the vlan devic= e. > > >> >> 2) Link down events on the underlying NIC. I believe that link flaps >> will be logged to /var/log/messages and dmesg; do you see anything there >> that might correspond to the time of the packet drops? >> > > No, dmesg is clean, only a couple down/up link when I actually did > disconnect the port, and no other message on /var/log/messages that grabs > my attention. > > >> >> 3) If VLAN_HWTAGGING is disabled through ifconfig on the port, then in >> theory a low memory event could cause the packet to be dropped. Does >> "netstat -m" show that "requests for mbufs denied" increasing? >> > > Here is the ifconfig -v output for the vlan6 on the 10.1-STABLE system > > vlan6: flags=3D8843 metric 0 mtu = 1500 > options=3D303 > ether a0:36:9f:2a:6d:ae > inet6 fe80::a236:9fff:fe2a:6dae%vlan6 prefixlen 64 scopeid 0x19 > inet6 2804:1054:bad:b1fe::1 prefixlen 64 > nd6 options=3D21 > media: Ethernet autoselect (10Gbase-SR ) > status: active > vlan: 3005 parent interface: ix3 > groups: vlan > > And here it is on the 10.3-STABLE system, I dont know why the only > difference is no options were printed on the newer system, everything els= e > is the same. > > vlan6: flags=3D8843 metric 0 mtu = 1500 > ether a0:36:9f:2a:6d:ae > inet6 fe80::a236:9fff:fe2a:6dae%vlan6 prefixlen 64 scopeid 0x19 > inet6 2804:1054:bad:b1fe::1 prefixlen 64 > nd6 options=3D21 > media: Ethernet autoselect (10Gbase-SR ) > status: active > vlan: 3005 parent interface: ix3 > groups: vlan > > This is the netstat -m output when system has packet loss. Denied and > delayed counters are zeroed. > > % netstat -m > 12365/21040/33405 mbufs in use (current/cache/total) > 12310/14530/26840/505076 mbuf clusters in use (current/cache/total/max) > 12310/14508 mbuf+clusters out of packet secondary zone in use > (current/cache) > 0/225/225/252538 4k (page size) jumbo clusters in use > (current/cache/total/max) > 0/0/0/74826 9k jumbo clusters in use (current/cache/total/max) > 0/0/0/42089 16k jumbo clusters in use (current/cache/total/max) > 27711K/35220K/62931K bytes allocated to network (current/cache/total) > 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) > 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) > 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) > 0/0/0 requests for jumbo clusters denied (4k/9k/16k) > 0 requests for sfbufs denied > 0 requests for sfbufs delayed > 0 requests for I/O initiated by sendfile > > > >> >> On Wed, Apr 27, 2016 at 2:41 PM, Z=C3=A9 Claudio Pastore >> wrote: >> >>> Hello, >>> >>> On a BGP border router I help manage, we run FreeBSD 10.1-STABLE, >>> version r281235 and it works fine for several years now. >>> >>> We have around 4Gbit/s and 1.8Mpps routed on peak while per port >>> interface >>> we peak at 300Kpps. >>> >>> Our quality metrics are measured with: >>> >>> ping -s 1472 -i 0.1 >>> >>> As well as iperf bidirecional. >>> >>> This metric is similar to what Speedy Test and SIMET tests are done and >>> our >>> customers reference. >>> >>> Systems working w/o problem: >>> - 10.1-STABLE / r281235 >>> >>> Systems tested with drops: >>> - 10.2-STABLE / r292035M >>> - 10.3-STABLE / r298705 >>> - 11.0-CURRENT / r295683 (downloaded snapshot from ftp.freebsd.org) >>> - 11.0-CURRENT Melifaro Routing Branch / r297731M >>> >>> While testing, when errors happen I can see output errs on the vlan por= t >>> on >>> the output from "netstat -w1 -I vlan6" >>> >>> input vlan6 output >>> packets errs idrops bytes packets errs bytes colls >>> 1 0 0 66 30557 2 33310968 0 >>> 1 0 0 105 31458 3 33912219 0 >>> 2 0 0 2954 32001 8 34983986 0 >>> 1 0 0 1512 33150 6 35942558 0 >>> 1 0 0 1512 33654 4 37311862 0 >>> 1 0 0 1512 34825 3 38213793 0 >>> 3 0 0 1683 35376 4 39488912 0 >>> 5 0 0 7280 32423 3 35551869 0 >>> >>> Problems may happen under high load (~200Kpps) or low load (~30Kpps) on= a >>> vlan port. The observed frame loss never happens on untagged ports, onl= y >>> vlan related. The observed loss happens with packets sized 900 bytes an= d >>> above but noticeably loss rate is higher with packets close to 1400 (14= 72 >>> is my reference size). >>> >>> Loss rate on all listed systems different from r281235 is 9-19% with >>> ping(1) and iperf, while it's 0% on r281235. >>> >>> First I believed it to be a Intel driver error on systems newer than >>> 10.1. >>> My reference card are dual port 82599EB 10-Gigabit SFI/SFP+ Network >>> Connection (2x2 on x8 PCIe bus, total 4x10G). But yesterday I replaced >>> Intel by Chelsio T5 and the problem is still exactly the same, so it's >>> not >>> related to card vendor. >>> >>> I always test the very same hardware, I have two SSD drives in this >>> router, >>> one for the 10.1 which just runs fine and the other disk to test the >>> various versions of FreeBSD. >>> >>> Only minor loader and sysctl confs are tweaked: >>> >>> kern.hz=3D2000 >>> net.inet.ip.redirect=3D1 # do not send IP redirects >>> net.inet.ip.accept_sourceroute=3D0 # drop source routed packets si= nce >>> they ca >>> net.inet.ip.sourceroute=3D0 # if source routed packets are >>> accepted th >>> net.inet.tcp.drop_synfin=3D1 # SYN/FIN packets get dropped o= n >>> initial c >>> net.inet.udp.blackhole=3D1 # drop udp packets destined for >>> closed soc >>> net.inet.tcp.blackhole=3D2 # drop tcp packets destined for >>> closed por >>> security.bsd.see_other_uids=3D0 >>> >>> Can anyone suggest what might be a fix/tuning for this behavior? Was >>> there >>> any relevant change on vlan code from particular revisions close to the >>> one >>> I run on 10.1 and later which would lead to such a big difference? >>> _______________________________________________ >>> freebsd-net@freebsd.org mailing list >>> https://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 May 7 11:34:52 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 15733B2FFF9 for ; Sat, 7 May 2016 11:34:52 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from reviews.nyi.freebsd.org (reviews.nyi.freebsd.org [IPv6:2610:1c1:1:607c::16:b]) by mx1.freebsd.org (Postfix) with ESMTP id E525C1324 for ; Sat, 7 May 2016 11:34:51 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by reviews.nyi.freebsd.org (Postfix, from userid 1346) id 6C1A6155FE; Sat, 7 May 2016 11:34:51 +0000 (UTC) Date: Sat, 7 May 2016 11:34:51 +0000 To: freebsd-net@freebsd.org From: "nvass-gmx.com (Nikos Vassiliadis)" Reply-to: D1944+325+8925873bdc96dfc2@reviews.freebsd.org Subject: [Differential] D1944: PF and VIMAGE fixes Message-ID: <15195aae39f8bff68ba6fc4e20bf10bb@localhost.localdomain> X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: Thread-Topic: D1944: PF and VIMAGE fixes X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: NDc2NzM0MzY4OTdiYThiNTU1MjY2ZDZmMTJiIFct0ts= MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 May 2016 11:34:52 -0000 nvass-gmx.com added a comment. Thanks for taking a look Kristof, I believe all your points are valid. Thing is that all eventhandlers need a more thorough look. They don't work as they should; be it virtualized or not, be it a VIMAGE or GENERIC kernel. I am trying to take a look but I haven't thrown enough time to it. INLINE COMMENTS > @kristof wrote in sys/netpfil/pf/pf_if.c:130 > I don't understand why this is required. Surely if an ifnet lives in V_ifnet (so, lives in the current vnet) ifp->if_vnet is always going to be curvnet? You're correct. It is plain wrong REVISION DETAIL https://reviews.freebsd.org/D1944 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: nvass-gmx.com, bz, trociny, kristof, gnn, zec, rodrigc, glebius, eri Cc: ryan_timewasted.me, mmoll, javier_ovi_yahoo.com, farrokhi, julian, robak, freebsd-virtualization-list, freebsd-pf-list, freebsd-net-list From owner-freebsd-net@freebsd.org Sat May 7 12:48:58 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 56546B2B920 for ; Sat, 7 May 2016 12:48:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46C9F111B for ; Sat, 7 May 2016 12:48:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u47CmvTf094511 for ; Sat, 7 May 2016 12:48:58 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 208173] can't create GRE-tunnel over IPv6 Date: Sat, 07 May 2016 12:48:57 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: me@cschwarz.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 07 May 2016 12:48:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208173 Christian Schwarz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |me@cschwarz.com --- Comment #3 from Christian Schwarz --- Created attachment 170092 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D170092&action= =3Dedit Add notice about IPv6 encapsulation Would > [inet6] tunnel src_address dest_address be a better choice? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sat May 7 12:50:42 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ED13EB2B9AB for ; Sat, 7 May 2016 12:50:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DDD4511EC for ; Sat, 7 May 2016 12:50:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u47CogZg098317 for ; Sat, 7 May 2016 12:50:42 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 208173] can't create GRE-tunnel over IPv6 Date: Sat, 07 May 2016 12:50:43 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: me@cschwarz.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: cc flagtypes.name Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 07 May 2016 12:50:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208173 Christian Schwarz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd-net@FreeBSD.org Flags| |maintainer-feedback?(freebs | |d-net@FreeBSD.org) --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sat May 7 12:50:42 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DED22B2B9A9 for ; Sat, 7 May 2016 12:50:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B6FC911EB for ; Sat, 7 May 2016 12:50:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u47CogZe098317 for ; Sat, 7 May 2016 12:50:42 GMT (envelope-from bugzilla-noreply@freebsd.org) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: maintainer-feedback requested: [Bug 208173] can't create GRE-tunnel over IPv6 Date: Sat, 07 May 2016 12:50:43 +0000 X-Bugzilla-Type: request X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? Message-ID: In-Reply-To: References: X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 07 May 2016 12:50:43 -0000 Christian Schwarz has asked freebsd-net@FreeBSD.org for maintainer-feedback: Bug 208173: can't create GRE-tunnel over IPv6 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208173 From owner-freebsd-net@freebsd.org Sat May 7 15:34:32 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 424EBB319F8 for ; Sat, 7 May 2016 15:34:32 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D16A31EFE for ; Sat, 7 May 2016 15:34:30 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.14.9/8.14.9) with ESMTP id u47FYKN9074525 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 7 May 2016 17:34:21 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: yuri@rawbw.com Received: from [10.58.0.10] (dadvw [10.58.0.10]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id u47FYFip017585 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 7 May 2016 22:34:15 +0700 (KRAT) (envelope-from eugen@grosbein.net) Subject: Re: Marvell Yukon (msk) network card causes the "sticky mouse" problem: mouse stops for extended periods of time To: Yuri , freebsd-net@freebsd.org References: <572CC657.8040207@rawbw.com> From: Eugene Grosbein Message-ID: <572E0AF1.5060307@grosbein.net> Date: Sat, 7 May 2016 22:34:09 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <572CC657.8040207@rawbw.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM autolearn=no version=3.3.2 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 07 May 2016 15:34:32 -0000 06.05.2016 23:29, Yuri пишет: > When Marvell Yukon card is active on the desktop system, mouse periodically stops, sometimes for seconds. I think this also makes the system impaired in some other ways. > > The offending device: > mskc0: port 0xd800-0xd8ff mem 0xfbdfc000-0xfbdfffff irq 18 at device 0.0 on pci6 > msk0: on mskc0 > > When I replaced it with Linksys sk0 the problem is completely gone: > skc0: port 0xe800-0xe8ff mem 0xfbefc000-0xfbefffff irq 17 at device 1.0 on pci8 > > There were few other problem reports about Marvell Yukon cards in this ML in 2015-2016. Verify if your mouse (USB one?) is using IRQ 18 too. "vmstat -ai" command would be helpful. From owner-freebsd-net@freebsd.org Sat May 7 16:33:48 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F04ACB317AB for ; Sat, 7 May 2016 16:33:48 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id C058C16F0 for ; Sat, 7 May 2016 16:33:48 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yuri.doctorlan.com (c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id u47GXfPc056778 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sat, 7 May 2016 09:33:41 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190] claimed to be yuri.doctorlan.com Subject: Re: Marvell Yukon (msk) network card causes the "sticky mouse" problem: mouse stops for extended periods of time To: Eugene Grosbein , freebsd-net@freebsd.org References: <572CC657.8040207@rawbw.com> <572E0AF1.5060307@grosbein.net> From: Yuri Message-ID: <572E18E3.30300@rawbw.com> Date: Sat, 7 May 2016 09:33:39 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <572E0AF1.5060307@grosbein.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 07 May 2016 16:33:49 -0000 On 05/07/2016 08:34, Eugene Grosbein wrote: > > Verify if your mouse (USB one?) is using IRQ 18 too. > "vmstat -ai" command would be helpful. Yes, I have a USB mouse, and my USB uses IRQ 18: irq18: ehci0 uhci5 503154 9 stray irq18 0 0 Yuri From owner-freebsd-net@freebsd.org Sat May 7 17:47:55 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1A483B329B9 for ; Sat, 7 May 2016 17:47:55 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9AF2D1B2E for ; Sat, 7 May 2016 17:47:53 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.14.9/8.14.9) with ESMTP id u47HlnFt074845 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 7 May 2016 19:47:49 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: yuri@rawbw.com Received: from [10.58.0.10] (dadvw [10.58.0.10]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id u47HlbT6018179 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 8 May 2016 00:47:38 +0700 (KRAT) (envelope-from eugen@grosbein.net) Subject: Re: Marvell Yukon (msk) network card causes the "sticky mouse" problem: mouse stops for extended periods of time To: Yuri , freebsd-net@freebsd.org References: <572CC657.8040207@rawbw.com> <572E0AF1.5060307@grosbein.net> <572E18E3.30300@rawbw.com> From: Eugene Grosbein Message-ID: <572E2A34.1010506@grosbein.net> Date: Sun, 8 May 2016 00:47:32 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <572E18E3.30300@rawbw.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM autolearn=no version=3.3.2 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hz.grosbein.net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 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, 07 May 2016 17:47:55 -0000 07.05.2016 23:33, Yuri wrote: >> Verify if your mouse (USB one?) is using IRQ 18 too. >> "vmstat -ai" command would be helpful. > Yes, I have a USB mouse, and my USB uses IRQ 18: > > irq18: ehci0 uhci5 503154 9 > stray irq18 0 0 That must be the reason. Somehow interrupt sharing for USB and NIC does not work well in your system. Can't say for sure what it guilty, FreeBSD kernel, motherboard ACPI BIOS, NIC or USB driver.