From owner-freebsd-net@FreeBSD.ORG Sun Aug 28 00:20:12 2011 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E91F5106566C for ; Sun, 28 Aug 2011 00:20:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D965D8FC08 for ; Sun, 28 Aug 2011 00:20:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p7S0KCks031668 for ; Sun, 28 Aug 2011 00:20:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p7S0KCu0031666; Sun, 28 Aug 2011 00:20:12 GMT (envelope-from gnats) Date: Sun, 28 Aug 2011 00:20:12 GMT Message-Id: <201108280020.p7S0KCu0031666@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/159603: commit references a PR X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 00:20:13 -0000 The following reply was made to PR kern/159603; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/159603: commit references a PR Date: Sun, 28 Aug 2011 00:14:53 +0000 (UTC) Author: qingli Date: Sun Aug 28 00:14:40 2011 New Revision: 225223 URL: http://svn.freebsd.org/changeset/base/225223 Log: When an interface address route is removed from the system, another route with the same prefix is searched for as a replacement. The current code did not bypass routes that have non-operational interfaces. This patch fixes that bug and will find a replacement route with an active interface. PR: kern/159603 Submitted by: pluknet, ambrisko at ambrisko dot com Reviewed by: discussed on net@ Approved by: re (bz) MFC after: 3 days Modified: head/sys/netinet/in.c Modified: head/sys/netinet/in.c ============================================================================== --- head/sys/netinet/in.c Sat Aug 27 22:10:53 2011 (r225222) +++ head/sys/netinet/in.c Sun Aug 28 00:14:40 2011 (r225223) @@ -1163,7 +1163,8 @@ in_scrubprefix(struct in_ifaddr *target, p.s_addr &= ia->ia_sockmask.sin_addr.s_addr; } - if (prefix.s_addr != p.s_addr) + if ((prefix.s_addr != p.s_addr) || + !(ia->ia_ifp->if_flags & IFF_UP)) continue; /* _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Sun Aug 28 20:48:10 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5FA62106564A for ; Sun, 28 Aug 2011 20:48:10 +0000 (UTC) (envelope-from fredan-freebsd@fredan.se) Received: from mail.fredan.se (mail.fredan.se [77.105.235.102]) by mx1.freebsd.org (Postfix) with ESMTP id 28F748FC0C for ; Sun, 28 Aug 2011 20:48:09 +0000 (UTC) Received: from [2a03:b000:c04e:10:a075:3eff:fe10:2e3e] (port=42959 helo=fredan-pc.localnet) by mail.fredan.se with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.71) (envelope-from ) id 1Qxlmi-0005eW-5T for freebsd-net@freebsd.org; Sun, 28 Aug 2011 22:16:48 +0200 From: fredrik danerklint Organization: fredan To: freebsd-net@freebsd.org Date: Sun, 28 Aug 2011 22:16:47 +0200 User-Agent: KMail/1.13.6 (Linux/2.6.38-11-generic; KDE/4.6.2; x86_64; ; ) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201108282216.47501.fredan-freebsd@fredan.se> Subject: Dummynet, pipe and ip6 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Aug 2011 20:48:10 -0000 Hi! firewall_enable="YES" firewall_type="/etc/rc.firewall.local" pipe 1 config bw 1Mbit/s add 50091 pipe 1 ip from any to any via igb4 add 65000 allow ip from any to any When pinging the interface igb4 on the ip4 address it does work. When pinging the interface igb4 on the ip6 address it doesn't work. To get the ip6 address to respond at all I had to add: sysctl net.inet.ip.fw.one_pass=0 Why? Does the pipe really work with ip6 traffic in this configuration? -- //fredan From owner-freebsd-net@FreeBSD.ORG Sun Aug 28 21:07:09 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 237531065672 for ; Sun, 28 Aug 2011 21:07:09 +0000 (UTC) (envelope-from fredan-freebsd@fredan.se) Received: from mail.fredan.se (mail.fredan.se [77.105.235.102]) by mx1.freebsd.org (Postfix) with ESMTP id DEAB58FC0A for ; Sun, 28 Aug 2011 21:07:08 +0000 (UTC) Received: from [2a03:b000:c04e:10:a075:3eff:fe10:2e3e] (port=56620 helo=fredan-pc.localnet) by mail.fredan.se with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.71) (envelope-from ) id 1QxmWM-0007At-P0 for freebsd-net@freebsd.org; Sun, 28 Aug 2011 23:03:58 +0200 From: fredrik danerklint Organization: fredan To: freebsd-net@freebsd.org Date: Sun, 28 Aug 2011 23:03:57 +0200 User-Agent: KMail/1.13.6 (Linux/2.6.38-11-generic; KDE/4.6.2; x86_64; ; ) References: <201108282216.47501.fredan-freebsd@fredan.se> In-Reply-To: <201108282216.47501.fredan-freebsd@fredan.se> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201108282303.58169.fredan-freebsd@fredan.se> Subject: Re: Dummynet, pipe and ip6 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Aug 2011 21:07:09 -0000 > Hi! > > firewall_enable="YES" > firewall_type="/etc/rc.firewall.local" > > pipe 1 config bw 1Mbit/s > add 50091 pipe 1 ip from any to any via igb4 > add 65000 allow ip from any to any > > When pinging the interface igb4 on the ip4 address it does work. > When pinging the interface igb4 on the ip6 address it doesn't work. > > To get the ip6 address to respond at all I had to add: > > sysctl net.inet.ip.fw.one_pass=0 > > Why? > > Does the pipe really work with ip6 traffic in this configuration? Have to add that pinging the other side of the interface does not work even with the sysctl setting.... -- //fredan From owner-freebsd-net@FreeBSD.ORG Mon Aug 29 00:08:54 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0443106566C; Mon, 29 Aug 2011 00:08:54 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id B12CF8FC13; Mon, 29 Aug 2011 00:08:54 +0000 (UTC) Received: from lstewart-laptop.caia.swin.edu.au (ppp59-167-184-191.static.internode.on.net [59.167.184.191]) by lauren.room52.net (Postfix) with ESMTPSA id 76D4A7E824; Mon, 29 Aug 2011 10:08:52 +1000 (EST) Message-ID: <4E5AD893.7010708@freebsd.org> Date: Mon, 29 Aug 2011 10:08:51 +1000 From: Lawrence Stewart User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110727 Thunderbird/5.0 MIME-Version: 1.0 To: Steven Hartland References: <1F95A4C2D54E4F369830143CBDB5FF86@multiplay.co.uk><4E37C0F2.4080004@freebsd.org><2B063B6D95AA4C27B004C50D96393F91@multiplay.co.uk><4E3AA66A.6060605@freebsd.org><20229216858044E4881642284F245750@multiplay.co.uk> <4E432CB2.3030700@freebsd.org> <177917182AAD46A3962139F22B835B37@multiplay.co.uk> In-Reply-To: <177917182AAD46A3962139F22B835B37@multiplay.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY autolearn=unavailable version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on lauren.room52.net Cc: freebsd-net@freebsd.org, Andre Oppermann , slw@zxy.spb.ru Subject: Re: tcp failing to recover from a packet loss under 8.2-RELEASE? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 00:08:55 -0000 On 08/14/11 23:53, Steven Hartland wrote: > ----- Original Message ----- From: "Lawrence Stewart" > >> >> Here's my tweaked version of Andre's patch: >> http://people.freebsd.org/~lstewart/patches/misctcp/tcp_reass.c-logdebug%2bmissingsegment-20110811-lstewart.diff >> > > Still testing this and just noticed that the patch fails to > compile when INVARIANTS is enabled. The KASSERT calls need > ()'s around the split strings. oops, sorry. Compile tested on 8-STABLE without INVARIANTS enabled :/ Any further feedback with respect to the patch? Plan to submit it to re@ later this week for inclusion in 9.0. Cheers, Lawrence From owner-freebsd-net@FreeBSD.ORG Mon Aug 29 06:05:43 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72FC0106564A; Mon, 29 Aug 2011 06:05:43 +0000 (UTC) (envelope-from zeus@relay.ibs.dn.ua) Received: from relay.ibs.dn.ua (relay.ibs.dn.ua [91.216.196.25]) by mx1.freebsd.org (Postfix) with ESMTP id D82B18FC08; Mon, 29 Aug 2011 06:05:42 +0000 (UTC) Received: from relay.ibs.dn.ua (localhost [127.0.0.1]) by relay.ibs.dn.ua with ESMTP id p7T65exM026653; Mon, 29 Aug 2011 09:05:40 +0300 (EEST) Received: (from zeus@localhost) by relay.ibs.dn.ua (8.14.4/8.14.4/Submit) id p7T65dmw026649; Mon, 29 Aug 2011 09:05:39 +0300 (EEST) Date: Mon, 29 Aug 2011 09:05:39 +0300 From: Zeus V Panchenko To: freebsd-net@freebsd.org, freebsd-rc@freebsd.org Message-ID: <20110829060539.GG99571@relay.ibs.dn.ua> Mail-Followup-To: freebsd-net@freebsd.org, freebsd-rc@freebsd.org, =?utf-8?B?0JLQu9Cw0LTQuNGB0LvQsNCyINCf0YDQvtC00LDQvQ==?= References: <20101112070759.GA36248@relay.ibs.dn.ua> <20101112230000.GD22460@michelle.cdnetworks.com> <20110121125917.GA48950@relay.ibs.dn.ua> <20110826120601.GA18070@relay.ibs.dn.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20110826120601.GA18070@relay.ibs.dn.ua> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 8.1-RELEASE X-Editor: GNU Emacs 23.2.1 X-Face: iVBORw0KGgoAAAANSUhEUgAAACoAAAAqBAMAAAA37dRoAAAAFVBMVEWjjoiZhHDWzcZuW1U wOT+RcGxziJxEN0lIAAABrklEQVQokV2STXLbMAyFQaraE3a5dzSTfR1IF7CQrM3QuECn9z9DH0 gxzgSyFvr88PBD0uJxoR6BE+e8LtRgohE5ZB50sODP/REbfUnte/z12+llCekLUSKenFIMke6Be WinE8H0RJHSN71rUQp64gFDmtDDhRk0zam3FzpNVFprhwPGaFo6oY9wDBJQ9Qz6EuKyROJjDGa+ uza4VOTa8iHlN58Yv5BF9+4BGl0LA5pUD5xKXg4aQlVZm0co3NKxCGxQpu3aC352Gv3DZONmwQd tkrlaylV3YSew7bWtwAZF/zi9jblmprPoL7ktzeFSxmarVNmWRi+Bmxg7Y7tbGtR8XZUxLTo86G thANsssetjp3POuBvMBRlw6jRa5pKN7yVlP+F2lyiZGSMf5hnSU6eAVupmtfjRcxy0momwpxDnz 06hwnOWvBnUdR8U2/KX7cq26u1Jy5xFZMPOVONRbRUrwey8Qar6cWgf12xSymQuVX0DfYd4R8kN Hg0qCtLeaYZcj8B90M2N0cEX1P0vKSxw7NLy/3X8Qeriusu66jNA37P4Mn5QRTG2hz4d9D/6E3a EX852nwAAAABJRU5ErkJggg== Cc: =?utf-8?B?0JLQu9Cw0LTQuNGB0LvQsNCyINCf0YDQvtC00LDQvQ==?= Subject: Re: lagg(4) and alises X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: zeus@ibs.dn.ua List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 06:05:43 -0000 Hi, replying self question ... ipv4_addrs_lagg0="x.x.x.x/29 y.y.y.y/30 z.z.z.z/26" did help everything works after reboot all addressess are assigned and interface is up seems it is the only way to do that ... -- Zeus V. Panchenko JID:zeus@gnu.org.ua GMT+2 (EET) From owner-freebsd-net@FreeBSD.ORG Mon Aug 29 11:07:13 2011 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9FAF7106566B for ; Mon, 29 Aug 2011 11:07:13 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8DDCC8FC0A for ; Mon, 29 Aug 2011 11:07:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p7TB7DDs089343 for ; Mon, 29 Aug 2011 11:07:13 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p7TB7CbO089341 for freebsd-net@FreeBSD.org; Mon, 29 Aug 2011 11:07:12 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 29 Aug 2011 11:07:12 GMT Message-Id: <201108291107.p7TB7CbO089341@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-net@FreeBSD.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 11:07:13 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/160206 net [gif] gifX stops working after a while (IPv6 tunnel) o kern/159817 net [udp] write UDPv4: No buffer space available (code=55) o kern/159795 net [tcp] excessive duplicate ACKs and TCP session freezes o kern/159629 net [ipsec] [panic] kernel panic with IPsec in transport m o kern/159621 net [tcp] [panic] panic: soabort: so_count o kern/159603 net [netinet] [patch] in_ifscrubprefix() - network route c o kern/159602 net [netinet] [patch] arp_ifscrub() is called even if IFF_ o kern/159601 net [netinet] [patch] in_scrubprefix() - loopback route re o kern/159353 net [netinet] [patch] conditional call of ifa_del_loopback o kern/159294 net [em] em watchdog timeouts o kern/159203 net [wpi] Intel 3945ABG Wireless LAN not support IBSS o kern/158930 net [bpf] BPF element leak in ifp->bpf_if->bif_dlist o kern/158726 net [ip6] [patch] ICMPv6 Router Announcement flooding limi o kern/158694 net [ix] [lagg] ix0 is not working within lagg(4) o kern/158665 net [ip6] [panic] kernel pagefault in in6_setscope() o kern/158635 net [em] TSO breaks BPF packet captures with em driver f kern/157802 net [dummynet] [panic] kernel panic in dummynet o kern/157785 net amd64 + jail + ipfw + natd = very slow outbound traffi o kern/157429 net [re] Realtek RTL8169 doesn't work with re(4) o kern/157418 net [em] em driver lockup during boot on Supermicro X9SCM- o kern/157410 net [ip6] IPv6 Router Advertisements Cause Excessive CPU U o kern/157287 net [re] [panic] INVARIANTS panic (Memory modified after f o kern/157209 net [ip6] [patch] locking error in rip6_input() (sys/netin o kern/157200 net [network.subr] [patch] stf(4) can not communicate betw o kern/157182 net [lagg] lagg interface not working together with epair o kern/156877 net [dummynet] [panic] dummynet move_pkt() null ptr derefe o kern/156667 net [em] em0 fails to init on CURRENT after March 17 o kern/156408 net [vlan] Routing failure when using VLANs vs. Physical e o kern/156328 net [icmp]: host can ping other subnet but no have IP from o kern/156317 net [ip6] Wrong order of IPv6 NS DAD/MLD Report o kern/156283 net [ip6] [patch] nd6_ns_input - rtalloc_mpath does not re o kern/156279 net [if_bridge][divert][ipfw] unable to correctly re-injec o kern/156226 net [lagg]: failover does not announce the failover to swi o kern/156030 net [ip6] [panic] Crash in nd6_dad_start() due to null ptr o kern/155772 net ifconfig(8): ioctl (SIOCAIFADDR): File exists on direc o kern/155680 net [multicast] problems with multicast s kern/155642 net [request] Add driver for Realtek RTL8191SE/RTL8192SE W o kern/155604 net [flowtable] Flowtable excessively caches dest MAC addr o kern/155597 net [panic] Kernel panics with "sbdrop" message o kern/155585 net [tcp] [panic] tcp_output tcp_mtudisc loop until kernel o kern/155420 net [vlan] adding vlan break existent vlan o bin/155365 net [patch] routed(8): if.c in routed fails to compile if o kern/155177 net [route] [panic] Panic when inject routes in kernel o kern/155030 net [igb] igb(4) DEVICE_POLLING does not work with carp(4) o kern/155010 net [msk] ntfs-3g via iscsi using msk driver cause kernel o kern/155004 net [bce] [panic] kernel panic in bce0 driver o kern/154943 net [gif] ifconfig gifX create on existing gifX clears IP s kern/154851 net [request]: Port brcm80211 driver from Linux to FreeBSD o kern/154850 net [netgraph] [patch] ng_ether fails to name nodes when t o kern/154679 net [em] Fatal trap 12: "em1 taskq" only at startup (8.1-R o kern/154600 net [tcp] [panic] Random kernel panics on tcp_output o kern/154557 net [tcp] Freeze tcp-session of the clients, if in the gat o kern/154443 net [if_bridge] Kernel module bridgestp.ko missing after u o kern/154286 net [netgraph] [panic] 8.2-PRERELEASE panic in netgraph o kern/154255 net [nfs] NFS not responding o kern/154214 net [stf] [panic] Panic when creating stf interface o kern/154185 net race condition in mb_dupcl o kern/154169 net [multicast] [ip6] Node Information Query multicast add o kern/154134 net [ip6] stuck kernel state in LISTEN on ipv6 daemon whic o kern/154091 net [netgraph] [panic] netgraph, unaligned mbuf? o conf/154062 net [vlan] [patch] change to way of auto-generatation of v o kern/153937 net [ral] ralink panics the system (amd64 freeBSDD 8.X) wh o kern/153936 net [ixgbe] [patch] MPRC workaround incorrectly applied to o kern/153816 net [ixgbe] ixgbe doesn't work properly with the Intel 10g o kern/153772 net [ixgbe] [patch] sysctls reference wrong XON/XOFF varia o kern/153497 net [netgraph] netgraph panic due to race conditions o kern/153454 net [patch] [wlan] [urtw] Support ad-hoc and hostap modes o kern/153308 net [em] em interface use 100% cpu o kern/153244 net [em] em(4) fails to send UDP to port 0xffff o kern/152893 net [netgraph] [panic] 8.2-PRERELEASE panic in netgraph o kern/152853 net [em] tftpd (and likely other udp traffic) fails over e o kern/152828 net [em] poor performance on 8.1, 8.2-PRE o kern/152569 net [net]: Multiple ppp connections and routing table prob o kern/152235 net [arp] Permanent local ARP entries are not properly upd o kern/152141 net [vlan] [patch] encapsulate vlan in ng_ether before out o kern/152036 net [libc] getifaddrs(3) returns truncated sockaddrs for n o kern/151690 net [ep] network connectivity won't work until dhclient is o kern/151681 net [nfs] NFS mount via IPv6 leads to hang on client with o kern/151593 net [igb] [panic] Kernel panic when bringing up igb networ o kern/150920 net [ixgbe][igb] Panic when packets are dropped with heade o kern/150557 net [igb] igb0: Watchdog timeout -- resetting o kern/150251 net [patch] [ixgbe] Late cable insertion broken o kern/150249 net [ixgbe] Media type detection broken o bin/150224 net ppp(8) does not reassign static IP after kill -KILL co f kern/149969 net [wlan] [ral] ralink rt2661 fails to maintain connectio o kern/149937 net [ipfilter] [patch] kernel panic in ipfilter IP fragmen o kern/149643 net [rum] device not sending proper beacon frames in ap mo o kern/149609 net [panic] reboot after adding second default route o kern/149117 net [inet] [patch] in_pcbbind: redundant test o kern/149086 net [multicast] Generic multicast join failure in 8.1 o kern/148018 net [flowtable] flowtable crashes on ia64 o kern/147912 net [boot] FreeBSD 8 Beta won't boot on Thinkpad i1300 11 o kern/147894 net [ipsec] IPv6-in-IPv4 does not work inside an ESP-only o kern/147155 net [ip6] setfb not work with ipv6 o kern/146845 net [libc] close(2) returns error 54 (connection reset by f kern/146792 net [flowtable] flowcleaner 100% cpu's core load o kern/146719 net [pf] [panic] PF or dumynet kernel panic o kern/146534 net [icmp6] wrong source address in echo reply o kern/146427 net [mwl] Additional virtual access points don't work on m o kern/146426 net [mwl] 802.11n rates not possible on mwl o kern/146425 net [mwl] mwl dropping all packets during and after high u f kern/146394 net [vlan] IP source address for outgoing connections o bin/146377 net [ppp] [tun] Interface doesn't clear addresses when PPP o kern/146358 net [vlan] wrong destination MAC address o kern/146165 net [wlan] [panic] Setting bssid in adhoc mode causes pani o kern/146082 net [ng_l2tp] a false invaliant check was performed in ng_ o kern/146037 net [panic] mpd + CoA = kernel panic o bin/145934 net [patch] add count option to netstat(1) o kern/145825 net [panic] panic: soabort: so_count o kern/145728 net [lagg] Stops working lagg between two servers. f kern/144917 net [flowtable] [panic] flowtable crashes system [regressi o kern/144882 net MacBookPro =>4.1 does not connect to BSD in hostap wit o kern/144874 net [if_bridge] [patch] if_bridge frees mbuf after pfil ho o conf/144700 net [rc.d] async dhclient breaks stuff for too many people o kern/144616 net [nat] [panic] ip_nat panic FreeBSD 7.2 o kern/144572 net [carp] CARP preemption mode traffic partially goes to f kern/144315 net [ipfw] [panic] freebsd 8-stable reboot after add ipfw o kern/144231 net bind/connect/sendto too strict about sockaddr length o kern/143846 net [gif] bringing gif3 tunnel down causes gif0 tunnel to s kern/143673 net [stf] [request] there should be a way to support multi s kern/143666 net [ip6] [request] PMTU black hole detection not implemen o kern/143622 net [pfil] [patch] unlock pfil lock while calling firewall o kern/143593 net [ipsec] When using IPSec, tcpdump doesn't show outgoin o kern/143591 net [ral] RT2561C-based DLink card (DWL-510) fails to work o kern/143208 net [ipsec] [gif] IPSec over gif interface not working o kern/143034 net [panic] system reboots itself in tcp code [regression] o kern/142877 net [hang] network-related repeatable 8.0-STABLE hard hang o kern/142774 net Problem with outgoing connections on interface with mu o kern/142772 net [libc] lla_lookup: new lle malloc failed o kern/142018 net [iwi] [patch] Possibly wrong interpretation of beacon- o kern/141861 net [wi] data garbled with WEP and wi(4) with Prism 2.5 f kern/141741 net Etherlink III NIC won't work after upgrade to FBSD 8, o kern/141023 net [carp] CARP arp replays with wrong src mac o kern/140742 net rum(4) Two asus-WL167G adapters cannot talk to each ot o kern/140682 net [netgraph] [panic] random panic in netgraph o kern/140634 net [vlan] destroying if_lagg interface with if_vlan membe o kern/140619 net [ifnet] [patch] refine obsolete if_var.h comments desc o kern/140346 net [wlan] High bandwidth use causes loss of wlan connecti o kern/140142 net [ip6] [panic] FreeBSD 7.2-amd64 panic w/IPv6 o kern/140066 net [bwi] install report for 8.0 RC 2 (multiple problems) o kern/139565 net [ipfilter] ipfilter ioctl SIOCDELST broken o kern/139387 net [ipsec] Wrong lenth of PF_KEY messages in promiscuous o bin/139346 net [patch] arp(8) add option to remove static entries lis o kern/139268 net [if_bridge] [patch] allow if_bridge to forward just VL p kern/139204 net [arp] DHCP server replies rejected, ARP entry lost bef o kern/139117 net [lagg] + wlan boot timing (EBUSY) o kern/139058 net [ipfilter] mbuf cluster leak on FreeBSD 7.2 o kern/138850 net [dummynet] dummynet doesn't work correctly on a bridge o kern/138782 net [panic] sbflush_internal: cc 0 || mb 0xffffff004127b00 o kern/138688 net [rum] possibly broken on 8 Beta 4 amd64: able to wpa a o kern/138678 net [lo] FreeBSD does not assign linklocal address to loop o kern/138620 net [lagg] [patch] lagg port bpf-writes blocked o kern/138407 net [gre] gre(4) interface does not come up after reboot o kern/138332 net [tun] [lor] ifconfig tun0 destroy causes LOR if_adata/ o kern/138266 net [panic] kernel panic when udp benchmark test used as r o kern/138177 net [ipfilter] FreeBSD crashing repeatedly in ip_nat.c:257 f kern/138029 net [bpf] [panic] periodically kernel panic and reboot o kern/137881 net [netgraph] [panic] ng_pppoe fatal trap 12 p bin/137841 net [patch] wpa_supplicant(8) cannot verify SHA256 signed p kern/137776 net [rum] panic in rum(4) driver on 8.0-BETA2 o bin/137641 net ifconfig(8): various problems with "vlan_device.vlan_i o kern/137392 net [ip] [panic] crash in ip_nat.c line 2577 o kern/137372 net [ral] FreeBSD doesn't support wireless interface from o kern/137089 net [lagg] lagg falsely triggers IPv6 duplicate address de o bin/136994 net [patch] ifconfig(8) print carp mac address o kern/136911 net [netgraph] [panic] system panic on kldload ng_bpf.ko t o bin/136661 net [patch] ndp(8) ignores -f option o kern/136618 net [pf][stf] panic on cloning interface without unit numb o kern/136426 net [panic] spawning several dhclients in parallel panics o kern/135502 net [periodic] Warning message raised by rtfree function i o kern/134583 net [hang] Machine with jail freezes after random amount o o kern/134531 net [route] [panic] kernel crash related to routes/zebra o kern/134157 net [dummynet] dummynet loads cpu for 100% and make a syst o kern/133969 net [dummynet] [panic] Fatal trap 12: page fault while in o kern/133968 net [dummynet] [panic] dummynet kernel panic o kern/133736 net [udp] ip_id not protected ... o kern/133595 net [panic] Kernel Panic at pcpu.h:195 o kern/133572 net [ppp] [hang] incoming PPTP connection hangs the system o kern/133490 net [bpf] [panic] 'kmem_map too small' panic on Dell r900 o kern/133235 net [netinet] [patch] Process SIOCDLIFADDR command incorre o kern/133218 net [carp] [hang] use of carp(4) causes system to freeze f kern/133213 net arp and sshd errors on 7.1-PRERELEASE o kern/133060 net [ipsec] [pfsync] [panic] Kernel panic with ipsec + pfs o kern/132889 net [ndis] [panic] NDIS kernel crash on load BCM4321 AGN d o conf/132851 net [patch] rc.conf(5): allow to setfib(1) for service run o kern/132734 net [ifmib] [panic] panic in net/if_mib.c o kern/132705 net [libwrap] [patch] libwrap - infinite loop if hosts.all o kern/132672 net [ndis] [panic] ndis with rt2860.sys causes kernel pani o kern/132554 net [ipl] There is no ippool start script/ipfilter magic t o kern/132354 net [nat] Getting some packages to ipnat(8) causes crash o kern/132285 net [carp] alias gives incorrect hash in dmesg o kern/132277 net [crypto] [ipsec] poor performance using cryptodevice f o kern/132107 net [carp] carp(4) advskew setting ignored when carp IP us o kern/131781 net [ndis] ndis keeps dropping the link o kern/131776 net [wi] driver fails to init o kern/131753 net [altq] [panic] kernel panic in hfsc_dequeue o kern/131601 net [ipfilter] [panic] 7-STABLE panic in nat_finalise (tcp o bin/131567 net [socket] [patch] Update for regression/sockets/unix_cm o bin/131365 net route(8): route add changes interpretation of network f kern/130820 net [ndis] wpa_supplicant(8) returns 'no space on device' o kern/130628 net [nfs] NFS / rpc.lockd deadlock on 7.1-R o conf/130555 net [rc.d] [patch] No good way to set ipfilter variables a o kern/130525 net [ndis] [panic] 64 bit ar5008 ndisgen-erated driver cau o kern/130311 net [wlan_xauth] [panic] hostapd restart causing kernel pa o kern/130109 net [ipfw] Can not set fib for packets originated from loc f kern/130059 net [panic] Leaking 50k mbufs/hour f kern/129719 net [nfs] [panic] Panic during shutdown, tcp_ctloutput: in o kern/129517 net [ipsec] [panic] double fault / stack overflow o kern/129508 net [carp] [panic] Kernel panic with EtherIP (may be relat o kern/129219 net [ppp] Kernel panic when using kernel mode ppp o kern/129197 net [panic] 7.0 IP stack related panic o bin/128954 net ifconfig(8) deletes valid routes o bin/128602 net [an] wpa_supplicant(8) crashes with an(4) o kern/128448 net [nfs] 6.4-RC1 Boot Fails if NFS Hostname cannot be res o bin/128295 net [patch] ifconfig(8) does not print TOE4 or TOE6 capabi o bin/128001 net wpa_supplicant(8), wlan(4), and wi(4) issues o kern/127826 net [iwi] iwi0 driver has reduced performance and connecti o kern/127815 net [gif] [patch] if_gif does not set vlan attributes from o kern/127724 net [rtalloc] rtfree: 0xc5a8f870 has 1 refs f bin/127719 net [arp] arp: Segmentation fault (core dumped) f kern/127528 net [icmp]: icmp socket receives icmp replies not owned by p kern/127360 net [socket] TOE socket options missing from sosetopt() o bin/127192 net routed(8) removes the secondary alias IP of interface f kern/127145 net [wi]: prism (wi) driver crash at bigger traffic o kern/127050 net [carp] ipv6 does not work on carp interfaces [regressi o kern/126945 net [carp] CARP interface destruction with ifconfig destro o kern/126895 net [patch] [ral] Add antenna selection (marked as TBD) o kern/126874 net [vlan]: Zebra problem if ifconfig vlanX destroy o kern/126714 net [carp] CARP interface renaming makes system no longer o kern/126695 net rtfree messages and network disruption upon use of if_ o kern/126339 net [ipw] ipw driver drops the connection o kern/126075 net [inet] [patch] internet control accesses beyond end of o bin/125922 net [patch] Deadlock in arp(8) o kern/125920 net [arp] Kernel Routing Table loses Ethernet Link status o kern/125845 net [netinet] [patch] tcp_lro_rx() should make use of hard o kern/125816 net [carp] [if_bridge] carp stuck in init when using bridg f kern/125442 net [carp] [lagg] CARP combined with LAGG causes system pa o kern/125258 net [socket] socket's SO_REUSEADDR option does not work o kern/125239 net [gre] kernel crash when using gre o kern/124341 net [ral] promiscuous mode for wireless device ral0 looses o kern/124225 net [ndis] [patch] ndis network driver sometimes loses net o kern/124160 net [libc] connect(2) function loops indefinitely o kern/124021 net [ip6] [panic] page fault in nd6_output() o kern/123968 net [rum] [panic] rum driver causes kernel panic with WPA. o kern/123892 net [tap] [patch] No buffer space available o kern/123890 net [ppp] [panic] crash & reboot on work with PPP low-spee o kern/123858 net [stf] [patch] stf not usable behind a NAT o kern/123796 net [ipf] FreeBSD 6.1+VPN+ipnat+ipf: port mapping does not o kern/123758 net [panic] panic while restarting net/freenet6 o bin/123633 net ifconfig(8) doesn't set inet and ether address in one o kern/123559 net [iwi] iwi periodically disassociates/associates [regre o bin/123465 net [ip6] route(8): route add -inet6 -interfac o kern/123463 net [ipsec] [panic] repeatable crash related to ipsec-tool o conf/123330 net [nsswitch.conf] Enabling samba wins in nsswitch.conf c o kern/123160 net [ip] Panic and reboot at sysctl kern.polling.enable=0 f kern/123045 net [ng_mppc] ng_mppc_decompress - disabling node o kern/122989 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/122954 net [lagg] IPv6 EUI64 incorrectly chosen for lagg devices f kern/122780 net [lagg] tcpdump on lagg interface during high pps wedge o kern/122685 net It is not visible passing packets in tcpdump(1) o kern/122319 net [wi] imposible to enable ad-hoc demo mode with Orinoco o kern/122290 net [netgraph] [panic] Netgraph related "kmem_map too smal o kern/122033 net [ral] [lor] Lock order reversal in ral0 at bootup ieee o bin/121895 net [patch] rtsol(8)/rtsold(8) doesn't handle managed netw s kern/121774 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/121555 net [panic] Fatal trap 12: current process = 12 (swi1: net o kern/121443 net [gif] [lor] icmp6_input/nd6_lookup o kern/121437 net [vlan] Routing to layer-2 address does not work on VLA o bin/121359 net [patch] [security] ppp(8): fix local stack overflow in o kern/121257 net [tcp] TSO + natd -> slow outgoing tcp traffic o kern/121181 net [panic] Fatal trap 3: breakpoint instruction fault whi o kern/120966 net [rum] kernel panic with if_rum and WPA encryption o kern/120566 net [request]: ifconfig(8) make order of arguments more fr o kern/120304 net [netgraph] [patch] netgraph source assumes 32-bit time o kern/120266 net [udp] [panic] gnugk causes kernel panic when closing U o kern/120130 net [carp] [panic] carp causes kernel panics in any conste o bin/120060 net routed(8) deletes link-level routes in the presence of o kern/119945 net [rum] [panic] rum device in hostap mode, cause kernel o kern/119791 net [nfs] UDP NFS mount of aliased IP addresses from a Sol o kern/119617 net [nfs] nfs error on wpa network when reseting/shutdown f kern/119516 net [ip6] [panic] _mtx_lock_sleep: recursed on non-recursi o kern/119432 net [arp] route add -host -iface causes arp e o kern/119225 net [wi] 7.0-RC1 no carrier with Prism 2.5 wifi card [regr o kern/118727 net [netgraph] [patch] [request] add new ng_pf module o kern/117448 net [carp] 6.2 kernel crash [regression] o kern/117423 net [vlan] Duplicate IP on different interfaces o bin/117339 net [patch] route(8): loading routing management commands o kern/117271 net [tap] OpenVPN TAP uses 99% CPU on releng_6 when if_tap o bin/116643 net [patch] [request] fstat(1): add INET/INET6 socket deta o kern/116185 net [iwi] if_iwi driver leads system to reboot o kern/115239 net [ipnat] panic with 'kmem_map too small' using ipnat o kern/115019 net [netgraph] ng_ether upper hook packet flow stops on ad o kern/115002 net [wi] if_wi timeout. failed allocation (busy bit). ifco o kern/114915 net [patch] [pcn] pcn (sys/pci/if_pcn.c) ethernet driver f o kern/113432 net [ucom] WARNING: attempt to net_add_domain(netgraph) af o kern/112722 net [ipsec] [udp] IP v4 udp fragmented packet reject o kern/112686 net [patm] patm driver freezes System (FreeBSD 6.2-p4) i38 o bin/112557 net [patch] ppp(8) lock file should not use symlink name o kern/112528 net [nfs] NFS over TCP under load hangs with "impossible p o kern/111537 net [inet6] [patch] ip6_input() treats mbuf cluster wrong o kern/111457 net [ral] ral(4) freeze o kern/110284 net [if_ethersubr] Invalid Assumption in SIOCSIFADDR in et o kern/110249 net [kernel] [regression] [patch] setsockopt() error regre o kern/109470 net [wi] Orinoco Classic Gold PC Card Can't Channel Hop o bin/108895 net pppd(8): PPPoE dead connections on 6.2 [regression] o kern/107944 net [wi] [patch] Forget to unlock mutex-locks o conf/107035 net [patch] bridge(8): bridge interface given in rc.conf n o kern/106444 net [netgraph] [panic] Kernel Panic on Binding to an ip to o kern/106438 net [ipf] ipfilter: keep state does not seem to allow repl o kern/106316 net [dummynet] dummynet with multipass ipfw drops packets o kern/105945 net Address can disappear from network interface s kern/105943 net Network stack may modify read-only mbuf chain copies o bin/105925 net problems with ifconfig(8) and vlan(4) [regression] o kern/104851 net [inet6] [patch] On link routes not configured when usi o kern/104751 net [netgraph] kernel panic, when getting info about my tr o kern/103191 net Unpredictable reboot o kern/103135 net [ipsec] ipsec with ipfw divert (not NAT) encodes a pac o kern/102540 net [netgraph] [patch] supporting vlan(4) by ng_fec(4) o conf/102502 net [netgraph] [patch] ifconfig name does't rename netgrap o kern/102035 net [plip] plip networking disables parallel port printing o kern/101948 net [ipf] [panic] Kernel Panic Trap No 12 Page Fault - cau o kern/100709 net [libc] getaddrinfo(3) should return TTL info o kern/100519 net [netisr] suggestion to fix suboptimal network polling o kern/98978 net [ipf] [patch] ipfilter drops OOW packets under 6.1-Rel o kern/98597 net [inet6] Bug in FreeBSD 6.1 IPv6 link-local DAD procedu o bin/98218 net wpa_supplicant(8) blacklist not working o kern/97306 net [netgraph] NG_L2TP locks after connection with failed o conf/97014 net [gif] gifconfig_gif? in rc.conf does not recognize IPv f kern/96268 net [socket] TCP socket performance drops by 3000% if pack o kern/95519 net [ral] ral0 could not map mbuf o kern/95288 net [pppd] [tty] [panic] if_ppp panic in sys/kern/tty_subr o kern/95277 net [netinet] [patch] IP Encapsulation mask_match() return o kern/95267 net packet drops periodically appear f kern/93378 net [tcp] Slow data transfer in Postfix and Cyrus IMAP (wo o kern/93019 net [ppp] ppp and tunX problems: no traffic after restarti o kern/92880 net [libc] [patch] almost rewritten inet_network(3) functi s kern/92279 net [dc] Core faults everytime I reboot, possible NIC issu o kern/91859 net [ndis] if_ndis does not work with Asus WL-138 s kern/91777 net [ipf] [patch] wrong behaviour with skip rule inside an o kern/91364 net [ral] [wep] WF-511 RT2500 Card PCI and WEP o kern/91311 net [aue] aue interface hanging s kern/90086 net [hang] 5.4p8 on supermicro P8SCT hangs during boot if o kern/87521 net [ipf] [panic] using ipfilter "auth" keyword leads to k o kern/87421 net [netgraph] [panic]: ng_ether + ng_eiface + if_bridge s kern/86920 net [ndis] ifconfig: SIOCS80211: Invalid argument [regress o kern/86871 net [tcp] [patch] allocation logic for PCBs in TIME_WAIT s o kern/86427 net [lor] Deadlock with FASTIPSEC and nat o kern/86103 net [ipf] Illegal NAT Traversal in IPFilter o kern/85780 net 'panic: bogus refcnt 0' in routing/ipv6 o bin/85445 net ifconfig(8): deprecated keyword to ifconfig inoperativ p kern/85320 net [gre] [patch] possible depletion of kernel stack in ip o bin/82975 net route change does not parse classfull network as given o kern/82881 net [netgraph] [panic] ng_fec(4) causes kernel panic after o kern/82468 net Using 64MB tcp send/recv buffers, trafficflow stops, i o bin/82185 net [patch] ndp(8) can delete the incorrect entry o kern/81095 net IPsec connection stops working if associated network i o kern/79895 net [ipf] 5.4-RC2 breaks ipfilter NAT when using netgraph o kern/78968 net FreeBSD freezes on mbufs exhaustion (network interface o kern/78090 net [ipf] ipf filtering on bridged packets doesn't work if o kern/77341 net [ip6] problems with IPV6 implementation o kern/77273 net [ipf] ipfilter breaks ipv6 statefull filtering on 5.3 s kern/77195 net [ipf] [patch] ipfilter ioctl SIOCGNATL does not match o kern/75873 net Usability problem with non-RFC-compliant IP spoof prot s kern/75407 net [an] an(4): no carrier after short time a kern/71474 net [route] route lookup does not skip interfaces marked d o kern/71469 net default route to internet magically disappears with mu o kern/70904 net [ipf] ipfilter ipnat problem with h323 proxy support o kern/68889 net [panic] m_copym, length > size of mbuf chain o kern/66225 net [netgraph] [patch] extend ng_eiface(4) control message o kern/65616 net IPSEC can't detunnel GRE packets after real ESP encryp s kern/60293 net [patch] FreeBSD arp poison patch a kern/56233 net IPsec tunnel (ESP) over IPv6: MTU computation is wrong s bin/41647 net ifconfig(8) doesn't accept lladdr along with inet addr s kern/39937 net ipstealth issue a kern/38554 net [patch] changing interface ipaddress doesn't seem to w o kern/34665 net [ipf] [hang] ipfilter rcmd proxy "hangs". o kern/31940 net ip queue length too short for >500kpps o kern/31647 net [libc] socket calls can return undocumented EINVAL o kern/30186 net [libc] getaddrinfo(3) does not handle incorrect servna o kern/27474 net [ipf] [ppp] Interactive use of user PPP and ipfilter c f kern/24959 net [patch] proper TCP_NOPUSH/TCP_CORK compatibility o conf/23063 net [arp] [patch] for static ARP tables in rc.network o kern/21998 net [socket] [patch] ident only for outgoing connections o kern/5877 net [socket] sb_cc counts control data as well as data dat 384 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Aug 29 11:30:27 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFCA71065670 for ; Mon, 29 Aug 2011 11:30:27 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 5F51A8FC1A for ; Mon, 29 Aug 2011 11:30:27 +0000 (UTC) Received: (qmail 96410 invoked from network); 29 Aug 2011 10:19:58 -0000 Received: from localhost (HELO [127.0.0.1]) ([127.0.0.1]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 29 Aug 2011 10:19:58 -0000 Message-ID: <4E5B785D.6000009@freebsd.org> Date: Mon, 29 Aug 2011 13:30:37 +0200 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: Lawrence Stewart References: <1F95A4C2D54E4F369830143CBDB5FF86@multiplay.co.uk><4E37C0F2.4080004@freebsd.org><2B063B6D95AA4C27B004C50D96393F91@multiplay.co.uk><4E3AA66A.6060605@freebsd.org><20229216858044E4881642284F245750@multiplay.co.uk> <4E432CB2.3030700@freebsd.org> <177917182AAD46A3962139F22B835B37@multiplay.co.uk> <4E5AD893.7010708@freebsd.org> In-Reply-To: <4E5AD893.7010708@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: tcp failing to recover from a packet loss under 8.2-RELEASE? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 11:30:28 -0000 On 29.08.2011 02:08, Lawrence Stewart wrote: > On 08/14/11 23:53, Steven Hartland wrote: >> ----- Original Message ----- From: "Lawrence Stewart" >> >>> >>> Here's my tweaked version of Andre's patch: >>> http://people.freebsd.org/~lstewart/patches/misctcp/tcp_reass.c-logdebug%2bmissingsegment-20110811-lstewart.diff >>> >>> >> >> Still testing this and just noticed that the patch fails to >> compile when INVARIANTS is enabled. The KASSERT calls need >> ()'s around the split strings. > > oops, sorry. Compile tested on 8-STABLE without INVARIANTS enabled :/ > > Any further feedback with respect to the patch? Plan to submit it to re@ later this week for > inclusion in 9.0. I'm not sure these excessive KASSERT's are really necessary. Probably one covering those cases at the start of the function is sufficient. I was about to send the original patch to re@ for approval as well now that I'm back from vacation and fully available again. Don't mind if you do it if you've got the time. -- Andre From owner-freebsd-net@FreeBSD.ORG Mon Aug 29 13:47:14 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F628106566B for ; Mon, 29 Aug 2011 13:47:14 +0000 (UTC) (envelope-from ivo.vachkov@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3315C8FC18 for ; Mon, 29 Aug 2011 13:47:13 +0000 (UTC) Received: by vxh11 with SMTP id 11so5470377vxh.13 for ; Mon, 29 Aug 2011 06:47:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; bh=PvdvdrHRhG763rsOsmEfT2LOj2jwHALDDfWn68RvhKc=; b=q1dMVjmLTITkr6WeJtBzH59LQfp7r4jhmXE4KxCQmBTZdOy8VN5dmu9jW4qWckBtKX KbkI+D2OypidvGZACRso5o2DUeNORUwkvhxec/1MMO05yHdJ67gWOrKkZoWX2fa8napJ s+0V/rnKPcBQUF+Z8VojByycjK/jNNnH5OaxY= Received: by 10.52.95.227 with SMTP id dn3mr2748356vdb.528.1314623810183; Mon, 29 Aug 2011 06:16:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.176.11 with HTTP; Mon, 29 Aug 2011 06:16:30 -0700 (PDT) From: Ivo Vachkov Date: Mon, 29 Aug 2011 16:16:30 +0300 Message-ID: To: FreeBSD Net Content-Type: text/plain; charset=UTF-8 Subject: Request for information/comment on default-free zone router properties X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 13:47:14 -0000 Hello all, First of all, I'd like to apologize if my question is considered highly off-topic. I ask it only with regard to the current FreeBSD routing table implementation. Is there any (no need to be official) information what is the number of different routes (for IPv4 and IPv6) on a default-free zone (DFZ) router in the Internet? I vaguely remember the number 450 000+ distinct routes for IPv4? But what about IPv6? On a related note, what is the number of the network interfaces on a DFZ router? No need for exact number, educated guess/estimation would be greatly appreciated too. Thank you very much in advance. -- Ivo Vachkov From owner-freebsd-net@FreeBSD.ORG Mon Aug 29 14:18:13 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B88CD1065675 for ; Mon, 29 Aug 2011 14:18:13 +0000 (UTC) (envelope-from sthaug@nethelp.no) Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by mx1.freebsd.org (Postfix) with SMTP id 0796C8FC1D for ; Mon, 29 Aug 2011 14:18:12 +0000 (UTC) Received: (qmail 38984 invoked from network); 29 Aug 2011 13:59:04 -0000 Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 29 Aug 2011 13:59:04 -0000 Date: Mon, 29 Aug 2011 15:59:04 +0200 (CEST) Message-Id: <20110829.155904.08325665.sthaug@nethelp.no> To: ivo.vachkov@gmail.com From: sthaug@nethelp.no In-Reply-To: References: X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Request for information/comment on default-free zone router properties X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 14:18:13 -0000 > Is there any (no need to be official) information what is the number > of different routes (for IPv4 and IPv6) on a default-free zone (DFZ) > router in the Internet? I vaguely remember the number 450 000+ > distinct routes for IPv4? But what about IPv6? See http://www.cidr-report.org - it has all the information you need. Extract from the weekly post to Nanog: Recent Table History Date Prefixes CIDR Agg 19-08-11 371450 219002 20-08-11 371427 219147 21-08-11 371547 219346 22-08-11 371326 218957 23-08-11 371090 219346 24-08-11 371769 219465 25-08-11 372189 219508 26-08-11 372363 219490 > On a related note, what is the number of the network interfaces on a > DFZ router? No need for exact number, educated guess/estimation would > be greatly appreciated too. How long is a piece of string? "It depends." And the same is the case for number of interfaces. You obviously need a minimum of three for a router to do anything "interesting" with the packets. Also, it depends on whether you're talking about physical interfaces or logical (sub) interfaces. I'd say anything from 3 to 20 is fairly typical. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-net@FreeBSD.ORG Mon Aug 29 16:41:41 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EA131065672 for ; Mon, 29 Aug 2011 16:41:41 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.freebsd.org (Postfix) with ESMTP id 478908FC0A for ; Mon, 29 Aug 2011 16:41:41 +0000 (UTC) Received: from PWSVL-EXCHTS-01.internal.cacheflow.com ([10.2.2.122]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id p7TGfe8f008627 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 29 Aug 2011 09:41:40 -0700 (PDT) Received: from PWSVL-EXCMBX-01.internal.cacheflow.com ([fe80::15bc:12e2:4676:340f]) by PWSVL-EXCHTS-01.internal.cacheflow.com ([fe80::5c50:e2ba:8115:4223%20]) with mapi id 14.01.0289.001; Mon, 29 Aug 2011 09:41:38 -0700 From: "Li, Qing" To: John , FreeBSD Net Thread-Topic: ifconfig -alias with duplicate netmasks work? Thread-Index: AQHMYSYtcw8/6hjRC0uAz545GzKzQJU0Dv9w Date: Mon, 29 Aug 2011 16:41:37 +0000 Message-ID: References: <20110822234921.GA34843@FreeBSD.org> In-Reply-To: <20110822234921.GA34843@FreeBSD.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.2.2.106] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Subject: RE: ifconfig -alias with duplicate netmasks work? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 16:41:41 -0000 Hi, Yes, the address alias and its associated prefix installation code changed.= =20 Operationally it makes sense because all addresses of that same prefix go through one route utilizing that given interface. The side effect is you can have two separate interfaces on the same prefix, but only a single route is installed, which is associated with the address installed first. The other interfaces won't be utilized for outgoing traffic unless you enab= le RADIX_MPATH option in the kernel configuration. I think the manpage needing updates, and I am partly guilty for not having = time to update the content, which does take considerable amount of time for actu= al=20 behavior verification on different released versions. I am now resuming work on FBSD after a long hiatus, updating the route manp= age=20 is on my to-do list. --Qing > -----Original Message----- > From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd- > net@freebsd.org] On Behalf Of John > Sent: Monday, August 22, 2011 4:49 PM > To: FreeBSD Net > Subject: ifconfig -alias with duplicate netmasks work? >=20 > Fellow Net'ers >=20 > Debugging an nfs locking problem to a linux host, I accidently > issued some ifconfig commands on the bsd server (9-current) and > found that duplicate netmasks seem to work fine. For instance: >=20 > bce0: flags=3D8843 metric 0 mtu > 1500 > options=3Dc01bb N_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE> > ether d4:85:64:66:2a:14 > inet6 fe80::d685:64ff:fe66:2a14%bce0 prefixlen 64 scopeid 0x1 > inet 10.24.99.127 netmask 0xffff0000 broadcast 10.24.255.255 > inet 10.24.99.128 netmask 0xffff0000 broadcast 10.24.255.255 > inet 10.24.99.126 netmask 0xffff0000 broadcast 10.24.255.255 > nd6 options=3D29 > media: Ethernet autoselect (1000baseT ) > status: active >=20 > via the commands: >=20 > ifconfig bce0 inet 10.24.99.127 netmask 0xffff0000 broadcast > 10.24.255.255 > ifconfig bce0 inet 10.24.99.128 netmask 0xffff0000 broadcast > 10.24.255.255 alias > ifconfig bce0 inet 10.24.99.126 netmask 0xffff0000 broadcast > 10.24.255.255 alias >=20 > The man page for ifconfig says one 'must' use a different netmask, > typically 0xffffffff. However, everything still seems to work ok. >=20 > Has something changed, is the manpage wrong, am I totally missing > something? >=20 > Thanks, > John >=20 > man ifconfig >=20 > If the address > is on the same subnet as the first network address for this > interface, a non-conflicting netmask must be given. Usually > 0xffffffff is most appropriate. > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Tue Aug 30 01:47:40 2011 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B263F106564A; Tue, 30 Aug 2011 01:47:40 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8A0B18FC08; Tue, 30 Aug 2011 01:47:40 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p7U1levT007196; Tue, 30 Aug 2011 01:47:40 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p7U1leoF007192; Tue, 30 Aug 2011 01:47:40 GMT (envelope-from linimon) Date: Tue, 30 Aug 2011 01:47:40 GMT Message-Id: <201108300147.p7U1leoF007192@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/160300: [if_bridge] [patch] bridge(4) should attempt to use a static MAC address. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Aug 2011 01:47:40 -0000 Old Synopsis: bridge(4) should attempt to use a static MAC address. New Synopsis: [if_bridge] [patch] bridge(4) should attempt to use a static MAC address. Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Tue Aug 30 01:46:51 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=160300 From owner-freebsd-net@FreeBSD.ORG Tue Aug 30 01:50:22 2011 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A6711065676; Tue, 30 Aug 2011 01:50:22 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 12BC28FC17; Tue, 30 Aug 2011 01:50:22 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p7U1oLlZ008234; Tue, 30 Aug 2011 01:50:21 GMT (envelope-from thompsa@freefall.freebsd.org) Received: (from thompsa@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p7U1oL9k008225; Tue, 30 Aug 2011 01:50:21 GMT (envelope-from thompsa) Date: Tue, 30 Aug 2011 01:50:21 GMT Message-Id: <201108300150.p7U1oL9k008225@freefall.freebsd.org> To: thompsa@FreeBSD.org, freebsd-net@FreeBSD.org, thompsa@FreeBSD.org From: thompsa@FreeBSD.org Cc: Subject: Re: kern/160300: [if_bridge] [patch] bridge(4) should attempt to use a static MAC address. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Aug 2011 01:50:22 -0000 Synopsis: [if_bridge] [patch] bridge(4) should attempt to use a static MAC address. Responsible-Changed-From-To: freebsd-net->thompsa Responsible-Changed-By: thompsa Responsible-Changed-When: Tue Aug 30 01:49:53 UTC 2011 Responsible-Changed-Why: Grab. http://www.freebsd.org/cgi/query-pr.cgi?pr=160300 From owner-freebsd-net@FreeBSD.ORG Tue Aug 30 02:16:35 2011 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C70C8106566B; Tue, 30 Aug 2011 02:16:35 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9F2FA8FC17; Tue, 30 Aug 2011 02:16:35 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p7U2GZ1u034816; Tue, 30 Aug 2011 02:16:35 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p7U2GZIu034812; Tue, 30 Aug 2011 02:16:35 GMT (envelope-from linimon) Date: Tue, 30 Aug 2011 02:16:35 GMT Message-Id: <201108300216.p7U2GZIu034812@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/160293: [ieee80211] ppanic] kernel panic during network setup at boot X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Aug 2011 02:16:35 -0000 Old Synopsis: kernel panic during network setup at boot New Synopsis: [ieee80211] ppanic] kernel panic during network setup at boot Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Tue Aug 30 02:15:06 UTC 2011 Responsible-Changed-Why: Attempt to reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=160293 From owner-freebsd-net@FreeBSD.ORG Tue Aug 30 02:31:16 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 25CCD106566B for ; Tue, 30 Aug 2011 02:31:16 +0000 (UTC) (envelope-from chrismiller.bsd@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id AA8FF8FC15 for ; Tue, 30 Aug 2011 02:31:15 +0000 (UTC) Received: by wwi36 with SMTP id 36so6393246wwi.31 for ; Mon, 29 Aug 2011 19:31:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=dUiBwYQlZUsD7NcvgGEi98oFrrwyDf9IIHMBM6TvhUs=; b=h9D5hYix7abAxPGdWCTvhmRZJbZkYanfbRUtucS1+u4vT+ypagxupMKQysVeq9Mm7K mLQEwq8p/mVnTDpj/kepMvH2qfyxvUiD6WkHqXNED+nauaCHYgH6+rS8Mtmgn+UyCUsh QlTPRpN6oGcyY77+zFmuUQmhhoW96F+6IWwj4= MIME-Version: 1.0 Received: by 10.227.38.164 with SMTP id b36mr4637052wbe.54.1314671473593; Mon, 29 Aug 2011 19:31:13 -0700 (PDT) Received: by 10.227.148.19 with HTTP; Mon, 29 Aug 2011 19:31:13 -0700 (PDT) In-Reply-To: References: Date: Mon, 29 Aug 2011 22:31:13 -0400 Message-ID: From: Chris Miller To: "Li, Qing" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-net@freebsd.org" Subject: Re: arpresolve: can't allocate llinfo X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Aug 2011 02:31:16 -0000 Qing- This patch seems to be working. I was not seeing the issue every time so I can't say with 100% certainty, but I'd say I'm 95% certain at this point. If you don't hear otherwise in the next few days, assume that it is fixed. Thanks for your help. -Chris On Sat, Aug 27, 2011 at 2:13 PM, Li, Qing wrote: > Hi, > > Could you please try the patch sitting at > > http://people.freebsd.org/~qingli/in.c.diff > > and let me know if it works for you? > > Thanks, > > -- Qing > > > > -----Original Message----- > > From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd- > > net@freebsd.org] On Behalf Of Chris Miller > > Sent: Tuesday, August 16, 2011 3:05 PM > > To: freebsd-net@freebsd.org > > Subject: arpresolve: can't allocate llinfo > > > > I'm using FreeBSD 8.1 and I'm seeing the following messages spit out > > frequently. > > > > IPv4 address: "169.254.231.172" is not on the network > > arpresolve: can't allocate llinfo for 169.254.231.172 > > > > Background: > > I have two interfaces attached to the same LAN, both configured using > > 169.254/16 link local automatic addressing. > > ARP entries exist for each interface. > > There are two routing entries for 169.254.0.0/16, one going out each > > interface. > > > > I've done some debugging and it appears that this happens when a packet > > is > > received on one of the interfaces and while sending the reply the > > routing > > lookup code says that we should send it out the other interface. This > > causes > > the "not on the network" message. > > > > I'm looking for suggestions or patches to allow this configuration to > > work > > as I need to have both interfaces on this network for redundancy. > > > > Thanks for any help. > > > > -Chris Miller > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Tue Aug 30 03:32:41 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1953106564A for ; Tue, 30 Aug 2011 03:32:41 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.freebsd.org (Postfix) with ESMTP id A01CA8FC17 for ; Tue, 30 Aug 2011 03:32:41 +0000 (UTC) Received: from PWSVL-EXCHTS-02.internal.cacheflow.com (sai-rp.bluecoat.com [10.2.2.126] (may be forged)) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id p7U3Weuh002528 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 29 Aug 2011 20:32:41 -0700 (PDT) Received: from PWSVL-EXCMBX-01.internal.cacheflow.com ([fe80::15bc:12e2:4676:340f]) by PWSVL-EXCHTS-02.internal.cacheflow.com ([fe80::4910:317f:407:6ecc%14]) with mapi id 14.01.0289.001; Mon, 29 Aug 2011 20:32:38 -0700 From: "Li, Qing" To: Chris Miller Thread-Topic: arpresolve: can't allocate llinfo Thread-Index: AQHMZrzlw2+J95BHU0mMmYuftN0QGZU0vTfw Date: Tue, 30 Aug 2011 03:32:38 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.2.2.106] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-net@freebsd.org" Subject: RE: arpresolve: can't allocate llinfo X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Aug 2011 03:32:41 -0000 Thank you Chris for the verification. I will wait a few days before committ= ing the patch. --Qing From: Chris Miller [mailto:chrismiller.bsd@gmail.com] Sent: Monday, August 29, 2011 7:31 PM To: Li, Qing Cc: freebsd-net@freebsd.org Subject: Re: arpresolve: can't allocate llinfo Qing- This patch seems to be working. I was not seeing the issue every time so I = can't say with 100% certainty, but I'd say I'm 95% certain at this point. I= f you don't hear otherwise in the next few days, assume that it is fixed. Thanks for your help. -Chris On Sat, Aug 27, 2011 at 2:13 PM, Li, Qing > wrote: Hi, Could you please try the patch sitting at http://people.freebsd.org/~qingli/in.c.diff and let me know if it works for you? Thanks, -- Qing > -----Original Message----- > From: owner-freebsd-net@freebsd.org= [mailto:owner-freebsd- > net@freebsd.org] On Behalf Of Chris Miller > Sent: Tuesday, August 16, 2011 3:05 PM > To: freebsd-net@freebsd.org > Subject: arpresolve: can't allocate llinfo > > I'm using FreeBSD 8.1 and I'm seeing the following messages spit out > frequently. > > IPv4 address: "169.254.231.172" is not on the network > arpresolve: can't allocate llinfo for 169.254.231.172 > > Background: > I have two interfaces attached to the same LAN, both configured using > 169.254/16 link local automatic addressing. > ARP entries exist for each interface. > There are two routing entries for 169.254.0.0/16, = one going out each > interface. > > I've done some debugging and it appears that this happens when a packet > is > received on one of the interfaces and while sending the reply the > routing > lookup code says that we should send it out the other interface. This > causes > the "not on the network" message. > > I'm looking for suggestions or patches to allow this configuration to > work > as I need to have both interfaces on this network for redundancy. > > Thanks for any help. > > -Chris Miller > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Tue Aug 30 07:05:00 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42144106566B for ; Tue, 30 Aug 2011 07:05:00 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 9B8F28FC14 for ; Tue, 30 Aug 2011 07:04:59 +0000 (UTC) Received: (qmail 323 invoked from network); 30 Aug 2011 05:54:23 -0000 Received: from localhost (HELO [127.0.0.1]) ([127.0.0.1]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 30 Aug 2011 05:54:23 -0000 Message-ID: <4E5C8BA7.3080501@freebsd.org> Date: Tue, 30 Aug 2011 09:05:11 +0200 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: ivo.vachkov@gmail.com References: <20110829.155904.08325665.sthaug@nethelp.no> In-Reply-To: <20110829.155904.08325665.sthaug@nethelp.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, sthaug@nethelp.no Subject: Re: Request for information/comment on default-free zone router properties X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Aug 2011 07:05:00 -0000 On 29.08.2011 15:59, sthaug@nethelp.no wrote: >> Is there any (no need to be official) information what is the number >> of different routes (for IPv4 and IPv6) on a default-free zone (DFZ) >> router in the Internet? I vaguely remember the number 450 000+ >> distinct routes for IPv4? But what about IPv6? > > See http://www.cidr-report.org - it has all the information you need. > > Extract from the weekly post to Nanog: > > Recent Table History > Date Prefixes CIDR Agg > 19-08-11 371450 219002 > 20-08-11 371427 219147 > 21-08-11 371547 219346 > 22-08-11 371326 218957 > 23-08-11 371090 219346 > 24-08-11 371769 219465 > 25-08-11 372189 219508 > 26-08-11 372363 219490 For IPv6 the current number of prefixes is about 12451. Both IPv4 and IPv6 numbers are expected to rise significantly in the future as more people migrate to IPv6, and the exhausted IPv4 pool gets fragmented more and more. >> On a related note, what is the number of the network interfaces on a >> DFZ router? No need for exact number, educated guess/estimation would >> be greatly appreciated too. > > How long is a piece of string? "It depends." And the same is the case > for number of interfaces. You obviously need a minimum of three for a > router to do anything "interesting" with the packets. Also, it depends > on whether you're talking about physical interfaces or logical (sub) > interfaces. I'd say anything from 3 to 20 is fairly typical. I'd say that range is about right for pure core/backbone routers. What happens more and more is that access concentrators (xDSL) run BGP as well. In that case the number of interfaces is 10k and more. Only a few of them 'run' BGP though. -- Andre From owner-freebsd-net@FreeBSD.ORG Tue Aug 30 08:52:43 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CEEE61065670 for ; Tue, 30 Aug 2011 08:52:43 +0000 (UTC) (envelope-from ivo.vachkov@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8AC4E8FC15 for ; Tue, 30 Aug 2011 08:52:40 +0000 (UTC) Received: by vxh11 with SMTP id 11so6378367vxh.13 for ; Tue, 30 Aug 2011 01:52:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=kowRXobApZKZpFTD4zM3aq+vMqBxVEIXVAhVuG2r6r0=; b=FvkFZKc2x3WVyAn9dZhKxW2SFrWRvwvAqX705xaSUm0N12ZE6sPGTw0DmMQ0yRJpJo 9bUK5wJS2N67n+UMWpjUyH50RGft4JgM9wXN2qWt1jclOPEUQtZ6arAi1efSRctt6jLW Dm01b3Jgb7CvUhhUKSPkvF8mgsoZMepIMWzWY= Received: by 10.220.106.143 with SMTP id x15mr2198616vco.30.1314694360171; Tue, 30 Aug 2011 01:52:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.176.11 with HTTP; Tue, 30 Aug 2011 01:52:20 -0700 (PDT) In-Reply-To: <4E5C8BA7.3080501@freebsd.org> References: <20110829.155904.08325665.sthaug@nethelp.no> <4E5C8BA7.3080501@freebsd.org> From: Ivo Vachkov Date: Tue, 30 Aug 2011 11:52:20 +0300 Message-ID: To: Andre Oppermann Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, sthaug@nethelp.no Subject: Re: Request for information/comment on default-free zone router properties X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Aug 2011 08:52:43 -0000 On Tue, Aug 30, 2011 at 10:05 AM, Andre Oppermann wrote: > On 29.08.2011 15:59, sthaug@nethelp.no wrote: > >> Is there any (no need to be official) information what is the number >>> of different routes (for IPv4 and IPv6) on a default-free zone (DFZ) >>> router in the Internet? I vaguely remember the number 450 000+ >>> distinct routes for IPv4? But what about IPv6? >>> >> >> See http://www.cidr-report.org - it has all the information you need. >> >> Extract from the weekly post to Nanog: >> >> Recent Table History >> Date Prefixes CIDR Agg >> 19-08-11 371450 219002 >> 20-08-11 371427 219147 >> 21-08-11 371547 219346 >> 22-08-11 371326 218957 >> 23-08-11 371090 219346 >> 24-08-11 371769 219465 >> 25-08-11 372189 219508 >> 26-08-11 372363 219490 >> > > For IPv6 the current number of prefixes is about 12451. Both IPv4 > and IPv6 numbers are expected to rise significantly in the future > as more people migrate to IPv6, and the exhausted IPv4 pool gets > fragmented more and more. Yes, I believe the real challenge for effective routing will be the wide adoption of IPv6. Even with prefixlen /32 the possible number of IPv6 routeable prefixes is greater than the number of routable IPv4 addresses now. > > On a related note, what is the number of the network interfaces on a >>> DFZ router? No need for exact number, educated guess/estimation would >>> be greatly appreciated too. >>> >> >> How long is a piece of string? "It depends." And the same is the case >> for number of interfaces. You obviously need a minimum of three for a >> router to do anything "interesting" with the packets. Also, it depends >> on whether you're talking about physical interfaces or logical (sub) >> interfaces. I'd say anything from 3 to 20 is fairly typical. >> > > I'd say that range is about right for pure core/backbone routers. > What happens more and more is that access concentrators (xDSL) run > BGP as well. In that case the number of interfaces is 10k and more. > Only a few of them 'run' BGP though. My interest is purely academic. I would like to experiment with different data structures to see if there is a way to increase routing performance with large number of routes and interfaces. > -- > Andre > -- Ivo Vachkov From owner-freebsd-net@FreeBSD.ORG Tue Aug 30 09:01:29 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2046E106564A for ; Tue, 30 Aug 2011 09:01:29 +0000 (UTC) (envelope-from sthaug@nethelp.no) Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by mx1.freebsd.org (Postfix) with SMTP id 5ED248FC0C for ; Tue, 30 Aug 2011 09:01:27 +0000 (UTC) Received: (qmail 2264 invoked from network); 30 Aug 2011 09:01:26 -0000 Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 30 Aug 2011 09:01:26 -0000 Date: Tue, 30 Aug 2011 11:01:26 +0200 (CEST) Message-Id: <20110830.110126.112533011.sthaug@nethelp.no> To: ivo.vachkov@gmail.com From: sthaug@nethelp.no In-Reply-To: References: <20110829.155904.08325665.sthaug@nethelp.no> <4E5C8BA7.3080501@freebsd.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, andre@freebsd.org Subject: Re: Request for information/comment on default-free zone router properties X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Aug 2011 09:01:29 -0000 > My interest is purely academic. I would like to experiment with different > data structures to see if there is a way to increase routing performance > with large number of routes and interfaces. You're more likely to find routers with a large number of routes *or* with a large number of interfaces. You're less likely to find routers with both of these at the same time. Something to keep in mind... Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-net@FreeBSD.ORG Tue Aug 30 09:04:24 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 49375106566B; Tue, 30 Aug 2011 09:04:24 +0000 (UTC) (envelope-from ivo.vachkov@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id E72928FC19; Tue, 30 Aug 2011 09:04:23 +0000 (UTC) Received: by vxh11 with SMTP id 11so6387025vxh.13 for ; Tue, 30 Aug 2011 02:04:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ce+pazWWWtDibRM5D6f7amsFqRU+UXMlJMxQ4jdG8pA=; b=sJHpLCY1ZuiJI8DQb15lj+98ZQunwC82FuSQPk0nKcUrSWp8LlgxROkzpUMQu2rzjk Drv7b9jVmM8PQSlopUQosCoGZ+GFkKI4367pvkPKq/bzVdMfKrlpGe862lL1EH02HwTd hKH7gyv2yTBZQUBKPGNpnKr+zlPDHeEyqjtZs= Received: by 10.52.26.168 with SMTP id m8mr1113733vdg.327.1314695063173; Tue, 30 Aug 2011 02:04:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.176.11 with HTTP; Tue, 30 Aug 2011 02:04:03 -0700 (PDT) In-Reply-To: <20110830.110126.112533011.sthaug@nethelp.no> References: <20110829.155904.08325665.sthaug@nethelp.no> <4E5C8BA7.3080501@freebsd.org> <20110830.110126.112533011.sthaug@nethelp.no> From: Ivo Vachkov Date: Tue, 30 Aug 2011 12:04:03 +0300 Message-ID: To: sthaug@nethelp.no Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, andre@freebsd.org Subject: Re: Request for information/comment on default-free zone router properties X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Aug 2011 09:04:24 -0000 On Tue, Aug 30, 2011 at 12:01 PM, wrote: > > My interest is purely academic. I would like to experiment with different > > data structures to see if there is a way to increase routing performance > > with large number of routes and interfaces. > > You're more likely to find routers with a large number of routes *or* > with a large number of interfaces. You're less likely to find routers > with both of these at the same time. Something to keep in mind... Yes. I agree, thus my initial question to gather information on the somewhat average case ... > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > -- Ivo Vachkov From owner-freebsd-net@FreeBSD.ORG Tue Aug 30 13:01:14 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66D39106564A for ; Tue, 30 Aug 2011 13:01:14 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id 2EBD38FC0A for ; Tue, 30 Aug 2011 13:01:14 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1QyNwM-000KlM-S5 for freebsd-net@freebsd.org; Tue, 30 Aug 2011 15:01:18 +0200 Date: Tue, 30 Aug 2011 15:01:18 +0200 From: Kurt Jaeger To: freebsd-net@freebsd.org Message-ID: <20110830130118.GH28186@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: ethernet Q-in-Q ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Aug 2011 13:01:14 -0000 Hi! What about 802.1q VLANs encapsulated in another 802.1q VLAN ? On FreeBSD 8.1 or 9.0-BETA1: ifconfig vlan123 create ifconfig vlan123 vlandev em0 vlan 123 ifconfig vlan400 create ifconfig vlan400 vlandev vlan123 vlan 400 ------ ifconfig: SIOCSETVLAN: Protocol not supported ------ Any ideas ? -- pi@opsec.eu +49 171 3101372 9 years to go ! From owner-freebsd-net@FreeBSD.ORG Tue Aug 30 13:33:24 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A70D1065672 for ; Tue, 30 Aug 2011 13:33:24 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id E30BE8FC14 for ; Tue, 30 Aug 2011 13:33:23 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1QyORU-000LHO-Kt for freebsd-net@freebsd.org; Tue, 30 Aug 2011 15:33:28 +0200 Date: Tue, 30 Aug 2011 15:33:28 +0200 From: Kurt Jaeger To: freebsd-net@freebsd.org Message-ID: <20110830133328.GA81727@home.opsec.eu> References: <20110830130118.GH28186@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110830130118.GH28186@home.opsec.eu> Subject: Re: ethernet Q-in-Q ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Aug 2011 13:33:24 -0000 Hi! > What about 802.1q VLANs encapsulated in another 802.1q VLAN ? I found ng_vlan(4), mentioned in http://lists.freebsd.org/pipermail/freebsd-current/2005-December/058882.html Now I have to find out how to use it 8-) -- pi@opsec.eu +49 171 3101372 9 years to go ! From owner-freebsd-net@FreeBSD.ORG Tue Aug 30 21:31:18 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65B24106566C for ; Tue, 30 Aug 2011 21:31:18 +0000 (UTC) (envelope-from mailinglistmember@mgwigglesworth.net) Received: from mail.mgwigglesworth.net (mail.mgwigglesworth.com [75.146.26.81]) by mx1.freebsd.org (Postfix) with ESMTP id EDF418FC14 for ; Tue, 30 Aug 2011 21:31:17 +0000 (UTC) To: freebsd-net@freebsd.org Date: Tue, 30 Aug 2011 17:20:34 -0400 Envelope-To: freebsd-net@freebsd.org Message-ID: <4E5D5422.9040609@mgwigglesworth.net> From: "Martes G Wigglesworth" Received: from devsecure.mgwigglesworth.net (192.168.5.12 [192.168.5.12]) by mail.mgwigglesworth.net; Tue, 30 Aug 2011 17:21:17 -0400 Organization: M. G. Wigglesworth Holdings, LLC User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.20) Gecko/20110817 Fedora/3.1.12-1.fc14 Lightning/1.0b2 Thunderbird/3.1.12 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Commands for AR5212 cause system to hang using 8.2-STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mailinglistmember@mgwigglesworth.net List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 21:31:18 -0000 Greetings all. I am attempting to get a newer 8.2-based router up and running, and during my development process, I discovered that the wireless AR5212 card was not blinking, as it did when installed on the current router box. Upon further reading, into the differences between FBSD7 and FBSD8 wireless setup, I attempted to get it runing with no luck. On the command line, the following causes the running terminal to hault, or at least to appear to hault, and become non-reactive to keyboard input: ifconfig wlan0 create wlandev ath0 Here is the output from ifconfig ath0 ath0: flags=8802 metric 0 mtu 2290 ether 00:1b:2f:37:02:46 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier Here is the output from rc.conf setting which are relivant: wlans_ath0="wlan0" create_args_wlan0="wlanmode hostap" ifconfig_wlan0="inet 192.168.200.1 netmask 255.255.255.0 ssid "wrouter0" mode 54g channel 1" Here is my loader.conf file output: wlan_wep_load="YES" wlan_tkip_load="YES" wlan_ccmp_load="YES" lan_xauth_load="YES" wlan_acl_load="YES" if_lagg_load="YES" if_ath_load="YES" accf_http_load="YES" When I put the rc.conf variables in place, it hung the boot process, just after initialization of the gateway port. (fxp0) What should I look for, in attempting to figure this out? I have also noticed that while the FBSD-8 Handbook provides references to utilizing /etc/netif start this file does not exist on this 8-Stable install. I installed and upgraded from source, from 8.1-PRERELEASE, last spring or fall, and have just now started to really get this setup going, hence the older version. The system is an old PIII-866Mhz server board, with three quad-port interfaces and a fourth, which is wireless. (while I wait for the Atom D525 system to get here.) There is no "output" to list, given that the system hangs each time, without any debug, or kernel panic indicators. In fact the system only hangs on the incident user space, because you can still login and utilize ssh sessions, as well as anything else that is running. I use the terms "system hang" because acpi requests from the power switch are ignored, due to the system not being "ready" so I just have to hard reset. Any input would be most appreciated. -- -- Respectfully, Martes G Wigglesworth M. G. Wigglesworth Holdings, LLC www.mgwigglesworth.net From owner-freebsd-net@FreeBSD.ORG Wed Aug 31 01:47:33 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9FB01106566B; Wed, 31 Aug 2011 01:47:33 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4B70B8FC0C; Wed, 31 Aug 2011 01:47:33 +0000 (UTC) Received: by gyd10 with SMTP id 10so221375gyd.13 for ; Tue, 30 Aug 2011 18:47:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=6OcwrvFjhCQCorHMRjLIMTvvx3w8JnU+cZgmSov29B8=; b=RnxfVcHQ6Wwg6HNZcU3Uf9b8gWEnJ78yj8mY35jY14MTLiSgx1w2HUw85g18OoUYR+ F32hHfw9VGSUInZteTXnnXw/smxtj4bkf5KIYM9LSbJi9bgQmGwqB5jYouNbaK2SVlKj 4QXeR7vK30bWp+yATmj00G21+AIQ0xDeH8qaQ= MIME-Version: 1.0 Received: by 10.151.42.18 with SMTP id u18mr6819877ybj.429.1314755252266; Tue, 30 Aug 2011 18:47:32 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.145.21 with HTTP; Tue, 30 Aug 2011 18:47:32 -0700 (PDT) In-Reply-To: <4E5D5422.9040609@mgwigglesworth.net> References: <4E5D5422.9040609@mgwigglesworth.net> Date: Wed, 31 Aug 2011 09:47:32 +0800 X-Google-Sender-Auth: ambQzBnizIqDKN_TI0l0StMdz_4 Message-ID: From: Adrian Chadd To: mailinglistmember@mgwigglesworth.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org, freebsd-wireless@freebsd.org Subject: Re: Commands for AR5212 cause system to hang using 8.2-STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Aug 2011 01:47:33 -0000 Hi, You're not the first person to reply with this problem. I unfortunately have no way (yet) to reproduce these kinds of issues at home as all my atheros hardware works fine on freebsd-8 and freebsd-9 on all the laptop/PC/MIPS hardware I have. Can you please try 8.0-RELEASE and see if it works for you? I'd like to see where things broke along the FreeBSD-7 -> FreeBSD-8.2 path. Adrian On 31 August 2011 05:20, Martes G Wigglesworth wrote: > > Greetings all. > > I am attempting to get a newer 8.2-based router up and running, and durin= g > my development process, I discovered that the wireless AR5212 card was no= t > blinking, as it did when installed on the current router box. =A0Upon fur= ther > reading, into the differences between FBSD7 and FBSD8 wireless setup, I > attempted to get it runing with no luck. > > On the command line, the following causes the running terminal to hault, = or > at least to appear to hault, and become non-reactive to keyboard input: > > ifconfig wlan0 create wlandev ath0 > > > Here is the output from ifconfig ath0 > > > ath0: flags=3D8802 metric 0 mtu 2290 > =A0 =A0 =A0 =A0ether 00:1b:2f:37:02:46 > =A0 =A0 =A0 =A0media: IEEE 802.11 Wireless Ethernet autoselect (autoselec= t) > =A0 =A0 =A0 =A0status: no carrier > > > Here is the output from rc.conf setting which are relivant: > > wlans_ath0=3D"wlan0" > create_args_wlan0=3D"wlanmode hostap" > ifconfig_wlan0=3D"inet 192.168.200.1 netmask 255.255.255.0 ssid "wrouter0= " > mode 54g channel 1" > > > Here is my loader.conf file output: > > wlan_wep_load=3D"YES" > wlan_tkip_load=3D"YES" > wlan_ccmp_load=3D"YES" > lan_xauth_load=3D"YES" > wlan_acl_load=3D"YES" > if_lagg_load=3D"YES" > if_ath_load=3D"YES" > accf_http_load=3D"YES" > > > When I put the rc.conf variables in place, it hung the boot process, just > after initialization of the gateway port. (fxp0) > > What should I look for, in attempting to figure this out? > > I have also noticed that while the FBSD-8 Handbook provides references to > utilizing /etc/netif start this file does not exist on thi= s > 8-Stable install. > > I installed and upgraded from source, from 8.1-PRERELEASE, last spring or > fall, and have just now started to really get this setup going, hence the > older version. > > The system is an old PIII-866Mhz server board, with three quad-port > interfaces and a fourth, which is wireless. (while I wait for the Atom D5= 25 > system to get here.) > > There is no "output" to list, given that the system hangs each time, with= out > any debug, or kernel panic indicators. =A0In fact the system only hangs o= n the > incident user space, because you can still login and utilize ssh sessions= , > as well as anything else that is running. > > I use the terms "system hang" because acpi requests from the power switch > are ignored, due to the system not being "ready" so I just have to hard > reset. > > Any input would be most appreciated. > > -- > > -- > Respectfully, > > > Martes G Wigglesworth > M. G. Wigglesworth Holdings, LLC > www.mgwigglesworth.net > > _______________________________________________ > 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 Aug 31 03:53:19 2011 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 350E2106564A for ; Wed, 31 Aug 2011 03:53:19 +0000 (UTC) (envelope-from ask@develooper.com) Received: from mbox1.develooper.com (mbox1.develooper.com [207.171.7.178]) by mx1.freebsd.org (Postfix) with ESMTP id 17A798FC17 for ; Wed, 31 Aug 2011 03:53:18 +0000 (UTC) Received: (qmail 15690 invoked from network); 31 Aug 2011 03:53:18 -0000 Received: from gw.develooper.com (HELO embla.bn.dev) (ask@mail.dev@64.81.84.140) by smtp.develooper.com with ESMTPA; 31 Aug 2011 03:53:18 -0000 Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=iso-8859-1 From: =?iso-8859-1?Q?Ask_Bj=F8rn_Hansen?= In-Reply-To: <4E4B3267.8050707@freebsd.org> Date: Tue, 30 Aug 2011 20:53:17 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <8D7CB918-F7E0-4BC6-B9FC-624B1E438692@develooper.com> References: <4E4AB3BE.4090603@sentex.net> <9255C71C-BB78-417E-A900-85140FC2050C@develooper.com> <4E4B3267.8050707@freebsd.org> To: Julian Elischer X-Mailer: Apple Mail (2.1244.3) Cc: Mike Tancsa , net@freebsd.org Subject: system locks up when pf is enabled? (was: system locks up with vr driver on alix board) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Aug 2011 03:53:19 -0000 On Aug 16, 2011, at 20:15, Julian Elischer wrote: > from your description it doesn't sound like a vr problem. > I suggest you hook up teh serial console (I am guessing you already = have) > and set the config options to allow break-to-debugger or = alt-break-to-debugger on it > when it happens next, drop into the debugger.. >=20 > in fact, drop in, and do a ps to see what processes are runnable, > 'tr [pid] (or thread id)' to get a stack trace of anything that looks > interesting, and then cont and do it again a few times to get a feel > for where the processor is hanging out (a straight 'tr' will give you > the interrupt of the com port which is not intresting..) Alright, I thought I had locked this down to ZERO_COPY_SOCKETS being = enabled in the kernel (as unlikely as it seems that it'd break things = without being explicitly used -- I wanted to believe!). A couple days ago I figured out how to consistently make it happen (or = not). For about a week we'd been running with no trouble; until I = realized that a hostname added to our pf rules made them not load on = startup. When running without our pf rules loaded, everything is fine. = WIth the pf rules loaded the system will hang within 2-4 hours. Our ruleset was about 240 rules. We cut it down to ~140 rules today to = see if that made a difference; it didn't. We also turned off as much = IPv6 traffic as we could in case that was what was disturbing things = (adding IPv6 traffic is relatively new). Flipping the backup system to be the master for the active IP addresses = doesn't (as far as I can tell) make the old master recover. I tried looking for interesting information with the kernel debugger; = but honestly nothing springs out as interesting -- though that may be = due to my lack of skills more than anything else. I am including a = snapshot below. I ran ps and tr on 100024, 100025 (vr0 and vr1 = interrupt threads) and 100022 (thread taskq) a few more times but it = seemed to me to give basically the same thread trace information. For what it's worth, if I let 'cont' run for long enough for the system = to send out carp packets and get it's IPs back, 'ps' seemed more likely = to have 100024 or 100025 (vr0/vr1) in 'Run' state. If I interrupted the = system again relatively quickly after continuing, it was more likely to = have 'thread tasks' be the busy process. Any tips for what I can do to extract something more useful would be = greatly appreciated. As a last note -- earlier today I noticed that "Searches" in 'pfctl -si' = seemed to go up significantly just before the console locks up (which is = 15-30 minutes before the box stops routing packets). My theory was = that we were getting some sort of tiny DoS attack (doesn't take much to = take out a computer the size of a CD case); but that doesn't really make = sense as the system 1) never recovers and 2) the backup is fine as soon = as the master has been turned off / changed priorities. - ask db> ps pid ppid pgrp uid state wmesg wchan cmd 3300 2371 2371 0 R sshd 3299 3298 3298 0 S+ sbwait 0xc2ddb58c ssh 3298 3100 3298 0 S+ piperd 0xc2624620 scp 3100 3098 3100 0 Ss+ pause 0xc2e95850 csh 3098 2371 3098 0 Rs sshd 2904 2371 2904 0 Ss select 0xc379a924 sshd 2476 2474 2476 0 Ss+ ttyin 0xc2e44070 csh 2474 2371 2474 0 Rs sshd 2440 1 2440 0 Rs+ getty 2433 1 2433 0 Rs cron 2426 1 2426 62 Rs ftp-proxy 2397 1 2397 0 Ss select 0xc2d71964 inetd 2371 1 2371 0 Rs sshd 2349 1 2349 0 Rs bird 2302 1 2302 0 Rs radvd 2298 2292 2285 65534 S piperd 0xc2624188 multilog 2297 2291 2285 0 R openvpn 2292 2287 2285 0 S select 0xc2d713a4 supervise 2291 2287 2285 0 S select 0xc2d71a64 supervise 2288 1 2285 0 S piperd 0xc2624c40 readproctitle 2287 1 2285 0 R svscan 2244 1 2244 0 Rs ntpd 2129 1 2129 0 Rs syslogd 50 0 0 0 SL mdwait 0xc2717000 [md1] 40 0 0 0 SL mdwait 0xc24ef000 [md0] 22 0 0 0 RL [flowcleaner] 21 0 0 0 SL sdflush 0xc0b24d80 [softdepflush] 20 0 0 0 SL vlruwt 0xc25f52a8 [vnlru] 19 0 0 0 SL syncer 0xc0b14774 [syncer] 18 0 0 0 RL [bufdaemon] 17 0 0 0 RL [pagezero] 16 0 0 0 SL psleep 0xc0b2567c [vmdaemon] 15 0 0 0 SL psleep 0xc0b25644 [pagedaemon] 9 0 0 0 SL ccb_scan 0xc0b006d4 [xpt_thrd] 8 0 0 0 RL [pfpurge] 7 0 0 0 SL waiting_ 0xc0b181d8 [sctp_iterator] 14 0 0 0 SL (threaded) usb 100036 D - 0xc250ed34 [usbus1] 100035 D - 0xc250ed04 [usbus1] 100034 D - 0xc250ecd4 [usbus1] 100033 D - 0xc250eca4 [usbus1] 100032 D - 0xc2504b5c [usbus0] 100031 D - 0xc2504b2c [usbus0] 100030 D - 0xc2504afc [usbus0] 100029 D - 0xc2504acc [usbus0] 13 0 0 0 SL - 0xc0b0df64 [yarrow] 6 0 0 0 SL crypto_r 0xc0b2432c [crypto returns] 5 0 0 0 SL crypto_w 0xc0b24308 [crypto] 4 0 0 0 SL - 0xc0b0bc44 [g_down] 3 0 0 0 SL - 0xc0b0bc40 [g_up] 2 0 0 0 SL - 0xc0b0bc38 [g_event] 12 0 0 0 RL (threaded) intr 100037 I [swi0: uart uart] 100028 I [irq12: ohci0 = ehci0] 100027 I [irq14: ata0] 100026 I [irq15: vr2 ata1] 100025 Run CPU 0 [irq11: vr1] 100024 RunQ [irq10: vr0] 100021 I [swi5: +] 100016 I [swi2: cambio] 100015 I [swi6: task queue] 100014 I [swi6: Giant taskq] 100006 I [swi1: netisr 0] 100005 I [swi4: clock] 100004 I [swi3: vm] 11 0 0 0 RL [idle] 1 0 1 0 SLs wait 0xc2433d48 [init] 10 0 0 0 SL audit_wo 0xc0b246a0 [audit] 0 0 0 0 RLs (threaded) kernel 100040 D - 0xc2527880 [dummynet] 100023 D - 0xc24d6580 [glxsb0 taskq] 100022 RunQ [thread taskq] 100020 D - 0xc24afd40 [acpi_task_2] 100019 D - 0xc24afd40 [acpi_task_1] 100018 D - 0xc24afd40 [acpi_task_0] 100017 D - 0xc24afd80 [kqueue taskq] 100010 D - 0xc24512c0 [firmware taskq] 100000 D sched 0xc0b0bd20 [swapper] db> tr 100025 Tracing pid 12 tid 100025 td 0xc24d42d0 kdb_enter(c0a48fbe,c0a5d00a,1,c2522280,0,...) at 0xc0733b3a =3D = kdb_enter+0x3a uart_intr(c2522200,c24d42d0,c0afdc90,c2430980,4,...) at 0xc0632206 =3D = uart_intr+0x126 intr_event_handle(c2430980,cc918ac4,cc918aa4,cc918b40,4,...) at = 0xc06dff2c =3D intr_event_handle+0x5c intr_execute_handlers(c0afdc90,cc918ac4,cc918b40,c2ef8a00,cc918b68,...) = at 0xc09d4929 =3D intr_execute_handlers+0x49 atpic_handle_intr(4,cc918ac4) at 0xc09ee047 =3D atpic_handle_intr+0x67 Xatpic_intr4() at 0xc09cfa52 =3D Xatpic_intr4+0x22 --- interrupt, eip =3D 0xc09e0f58, esp =3D 0xcc918b04, ebp =3D = 0xcc918b68 --- bzero(c2ef8a00,0,12,0,0,...) at 0xc09e0f58 =3D bzero ip_input(c2ef8a00,246,c24a77c0,cc918bd0,c0622c21,...) at 0xc083ff8d =3D = ip_input+0x6cd netisr_dispatch_src(1,0,c2ef8a00,cc918c08,c07bb331,...) at 0xc07c9109 =3D = netisr_dispatch_src+0x89 netisr_dispatch(1,c2ef8a00,c24d8c00,c24d8c00,c2f16008,...) at 0xc07c93a0 = =3D netisr_dispatch+0x20 ether_demux(c24d8c00,c2ef8a00,3,0,3,...) at 0xc07bb331 =3D = ether_demux+0x161 ether_input(c24d8c00,c2ef8a00,c09d6ad0,c0b11780,c24d42d0,...) at = 0xc07bb8af =3D ether_input+0x33f vr_intr(c2499000,c24d42d0,0,109,dc13a3e2,...) at 0xc0690034 =3D = vr_intr+0x4d4 intr_event_execute_handlers(c24337f8,c2430600,c0a6b180,52d,c2430670,...) = at 0xc06def8b =3D intr_event_execute_handlers+0x13b ithread_loop(c24de360,cc918d28,0,0,0,...) at 0xc06e05ea =3D = ithread_loop+0x6a fork_exit(c06e0580,c24de360,cc918d28) at 0xc06dc830 =3D fork_exit+0x90 fork_trampoline() at 0xc09cf964 =3D fork_trampoline+0x8 --- trap 0, eip =3D 0, esp =3D 0xcc918d60, ebp =3D 0 --- db> tr 100024 Tracing pid 12 tid 100024 td 0xc24d45a0 sched_switch(c24d45a0,0,109,dc1435c0,660,...) at 0xc07270bf =3D = sched_switch+0x1df mi_switch(109,0,c0a6b180,52d,c24306f0,...) at 0xc071086a =3D = mi_switch+0x11a ithread_loop(c24de8c0,cc894d28,0,0,0,...) at 0xc06e06df =3D = ithread_loop+0x15f fork_exit(c06e0580,c24de8c0,cc894d28) at 0xc06dc830 =3D fork_exit+0x90 fork_trampoline() at 0xc09cf964 =3D fork_trampoline+0x8 --- trap 0, eip =3D 0, esp =3D 0xcc894d60, ebp =3D 0 --- db> cont KDB: enter: Line break on console [thread pid 0 tid 100022 ] Stopped at 0xc0733b3a =3D kdb_enter+0x3a: movl $0,0xc0b124b4 = =3D kdb_why db> ps=20 pid ppid pgrp uid state wmesg wchan cmd 3300 2371 2371 0 R sshd 3299 3298 3298 0 S+ sbwait 0xc2ddb58c ssh 3298 3100 3298 0 S+ piperd 0xc2624620 scp 3100 3098 3100 0 Ss+ pause 0xc2e95850 csh 3098 2371 3098 0 Rs sshd 2904 2371 2904 0 Ss select 0xc379a924 sshd 2476 2474 2476 0 Ss+ ttyin 0xc2e44070 csh 2474 2371 2474 0 Rs sshd 2440 1 2440 0 Rs+ getty 2433 1 2433 0 Rs cron 2426 1 2426 62 Rs ftp-proxy 2397 1 2397 0 Ss select 0xc2d71964 inetd 2371 1 2371 0 Rs sshd 2349 1 2349 0 Rs bird 2302 1 2302 0 Rs radvd 2298 2292 2285 65534 S piperd 0xc2624188 multilog 2297 2291 2285 0 R openvpn 2292 2287 2285 0 S select 0xc2d713a4 supervise 2291 2287 2285 0 S select 0xc2d71a64 supervise 2288 1 2285 0 S piperd 0xc2624c40 readproctitle 2287 1 2285 0 R svscan 2244 1 2244 0 Rs ntpd 2129 1 2129 0 Rs syslogd 50 0 0 0 SL mdwait 0xc2717000 [md1] 40 0 0 0 SL mdwait 0xc24ef000 [md0] 22 0 0 0 RL [flowcleaner] 21 0 0 0 SL sdflush 0xc0b24d80 [softdepflush] 20 0 0 0 SL vlruwt 0xc25f52a8 [vnlru] 19 0 0 0 SL syncer 0xc0b14774 [syncer] 18 0 0 0 RL [bufdaemon] 17 0 0 0 RL [pagezero] 16 0 0 0 SL psleep 0xc0b2567c [vmdaemon] 15 0 0 0 SL psleep 0xc0b25644 [pagedaemon] 9 0 0 0 SL ccb_scan 0xc0b006d4 [xpt_thrd] 8 0 0 0 RL [pfpurge] 7 0 0 0 SL waiting_ 0xc0b181d8 [sctp_iterator] 14 0 0 0 SL (threaded) usb 100036 D - 0xc250ed34 [usbus1] 100035 D - 0xc250ed04 [usbus1] 100034 D - 0xc250ecd4 [usbus1] 100033 D - 0xc250eca4 [usbus1] 100032 D - 0xc2504b5c [usbus0] 100031 D - 0xc2504b2c [usbus0] 100030 D - 0xc2504afc [usbus0] 100029 D - 0xc2504acc [usbus0] 13 0 0 0 SL - 0xc0b0df64 [yarrow] 6 0 0 0 SL crypto_r 0xc0b2432c [crypto returns] 5 0 0 0 SL crypto_w 0xc0b24308 [crypto] 4 0 0 0 SL - 0xc0b0bc44 [g_down] 3 0 0 0 SL - 0xc0b0bc40 [g_up] 2 0 0 0 SL - 0xc0b0bc38 [g_event] 12 0 0 0 WL (threaded) intr 100037 I [swi0: uart uart] 100028 I [irq12: ohci0 = ehci0] 100027 I [irq14: ata0] 100026 I [irq15: vr2 ata1] 100025 I [irq11: vr1] 100024 I [irq10: vr0] 100021 I [swi5: +] 100016 I [swi2: cambio] 100015 I [swi6: task queue] 100014 I [swi6: Giant taskq] 100006 I [swi1: netisr 0] 100005 I [swi4: clock] 100004 I [swi3: vm] 11 0 0 0 RL [idle] 1 0 1 0 SLs wait 0xc2433d48 [init] 10 0 0 0 SL audit_wo 0xc0b246a0 [audit] 0 0 0 0 RLs (threaded) kernel 100040 D - 0xc2527880 [dummynet] 100023 D - 0xc24d6580 [glxsb0 taskq] 100022 Run CPU 0 [thread taskq] 100020 D - 0xc24afd40 [acpi_task_2] 100019 D - 0xc24afd40 [acpi_task_1] 100018 D - 0xc24afd40 [acpi_task_0] 100017 D - 0xc24afd80 [kqueue taskq] 100010 D - 0xc24512c0 [firmware taskq] 100000 D sched 0xc0b0bd20 [swapper] db> tr 100024 Tracing pid 12 tid 100024 td 0xc24d45a0 sched_switch(c24d45a0,0,109,b67db121,673,...) at 0xc07270bf =3D = sched_switch+0x1df mi_switch(109,0,c0a6b180,52d,c24306f0,...) at 0xc071086a =3D = mi_switch+0x11a ithread_loop(c24de8c0,cc894d28,0,0,0,...) at 0xc06e06df =3D = ithread_loop+0x15f fork_exit(c06e0580,c24de8c0,cc894d28) at 0xc06dc830 =3D fork_exit+0x90 fork_trampoline() at 0xc09cf964 =3D fork_trampoline+0x8 --- trap 0, eip =3D 0, esp =3D 0xcc894d60, ebp =3D 0 --- db> tr 100022 Tracing pid 0 tid 100022 td 0xc24d4b40 kdb_enter(c0a48fbe,c0a5d00a,0,c2522280,0,...) at 0xc0733b3a =3D = kdb_enter+0x3a uart_intr(c2522200,c24d4b40,c0afdc90,c2430980,4,...) at 0xc0632206 =3D = uart_intr+0x126 intr_event_handle(c2430980,c23f5c20,0,c25db2bc,4,...) at 0xc06dff2c =3D = intr_event_handle+0x5c intr_execute_handlers(c0afdc90,c23f5c20,c25db2bc,0,c23f5c60,...) at = 0xc09d4929 =3D intr_execute_handlers+0x49 atpic_handle_intr(4,c23f5c20) at 0xc09ee047 =3D atpic_handle_intr+0x67 Xatpic_intr4() at 0xc09cfa52 =3D Xatpic_intr4+0x22 --- interrupt, eip =3D 0xc073cf01, esp =3D 0xc23f5c60, ebp =3D = 0xc23f5c60 --- sleepq_release(c25db2bc,0,0,0,c24afc80,...) at 0xc073cf01 =3D = sleepq_release+0x31 wakeup(c25db2bc,0,0,0,0,...) at 0xc07109f1 =3D wakeup+0x41 taskqueue_run_locked(c24afc80,c24afc9c,0,c0a66f59,0,...) at 0xc073e8e2 =3D= taskqueue_run_locked+0x142 taskqueue_thread_loop(c0b134ec,c23f5d28,0,0,0,...) at 0xc073ef27 =3D = taskqueue_thread_loop+0x87 fork_exit(c073eea0,c0b134ec,c23f5d28) at 0xc06dc830 =3D fork_exit+0x90 fork_trampoline() at 0xc09cf964 =3D fork_trampoline+0x8 --- trap 0, eip =3D 0, esp =3D 0xc23f5d60, ebp =3D 0 --- ... cont dance again ... db> tr 100022 Tracing pid 0 tid 100022 td 0xc24d4b40 kdb_enter(c0a48fbe,c0a5d00a,0,c2522280,0,...) at 0xc0733b3a =3D = kdb_enter+0x3a uart_intr(c2522200,c24d4b40,c0afdc90,c2430980,4,...) at 0xc0632206 =3D = uart_intr+0x126 intr_event_handle(c2430980,c23f5c48,c23f5c14,c24afc80,4,...) at = 0xc06dff2c =3D intr_event_handle+0x5c intr_execute_handlers(c0afdc90,c23f5c48,c24afc80,c25db2bc,c23f5cbc,...) = at 0xc09d4929 =3D intr_execute_handlers+0x49 atpic_handle_intr(4,c23f5c48) at 0xc09ee047 =3D atpic_handle_intr+0x67 Xatpic_intr4() at 0xc09cfa52 =3D Xatpic_intr4+0x22 --- interrupt, eip =3D 0xc073e7e3, esp =3D 0xc23f5c88, ebp =3D = 0xc23f5cbc --- taskqueue_run_locked(c24afc80,c24afc9c,0,c0a66f59,0,...) at 0xc073e7e3 =3D= taskqueue_run_locked+0x43 taskqueue_thread_loop(c0b134ec,c23f5d28,0,0,0,...) at 0xc073ef27 =3D = taskqueue_thread_loop+0x87 fork_exit(c073eea0,c0b134ec,c23f5d28) at 0xc06dc830 =3D fork_exit+0x90 fork_trampoline() at 0xc09cf964 =3D fork_trampoline+0x8 --- trap 0, eip =3D 0, esp =3D 0xc23f5d60, ebp =3D 0 --- db> tr 100024 Tracing pid 12 tid 100024 td 0xc24d45a0 sched_switch(c24d45a0,0,109,4b19c082,684,...) at 0xc07270bf =3D = sched_switch+0x1df mi_switch(109,0,c0a6b180,52d,c24306f0,...) at 0xc071086a =3D = mi_switch+0x11a ithread_loop(c24de8c0,cc894d28,0,0,0,...) at 0xc06e06df =3D = ithread_loop+0x15f fork_exit(c06e0580,c24de8c0,cc894d28) at 0xc06dc830 =3D fork_exit+0x90 fork_trampoline() at 0xc09cf964 =3D fork_trampoline+0x8 --- trap 0, eip =3D 0, esp =3D 0xcc894d60, ebp =3D 0 --- db> tr 100025 Tracing pid 12 tid 100025 td 0xc24d42d0 kdb_enter(c0a48fbe,c0a5d00a,58,c2522280,0,...) at 0xc0733b3a =3D = kdb_enter+0x3a uart_intr(c2522200,c24d42d0,c0afdc90,c2430980,4,...) at 0xc0632206 =3D = uart_intr+0x126 intr_event_handle(c2430980,cc918ac8,0,0,4,...) at 0xc06dff2c =3D = intr_event_handle+0x5c intr_execute_handlers(c0afdc90,cc918ac8,0,c2efa300,cc918b68,...) at = 0xc09d4929 =3D intr_execute_handlers+0x49 atpic_handle_intr(4,cc918ac8) at 0xc09ee047 =3D atpic_handle_intr+0x67 Xatpic_intr4() at 0xc09cfa52 =3D Xatpic_intr4+0x22 --- interrupt, eip =3D 0xc083e822, esp =3D 0xcc918b08, ebp =3D = 0xcc918b68 --- ip_forward(c2efa300,0,12,0,0,...) at 0xc083e822 =3D ip_forward+0x3b2 ip_input(c2efa300,246,c24a1580,cc918bd0,c0622c21,...) at 0xc083ff8d =3D = ip_input+0x6cd netisr_dispatch_src(1,0,c2efa300,cc918c08,c07bb331,...) at 0xc07c9109 =3D = netisr_dispatch_src+0x89 netisr_dispatch(1,c2efa300,c24d8c00,c24d8c00,c2f1a808,...) at 0xc07c93a0 = =3D netisr_dispatch+0x20 ether_demux(c24d8c00,c2efa300,3,0,3,...) at 0xc07bb331 =3D = ether_demux+0x161 ether_input(c24d8c00,c2efa300,c09d6ad0,c0b11780,c24d42d0,...) at = 0xc07bb8af =3D ether_input+0x33f vr_intr(c2499000,c24d42d0,0,109,48d02b08,...) at 0xc0690034 =3D = vr_intr+0x4d4 intr_event_execute_handlers(c24337f8,c2430600,c0a6b180,52d,c2430670,...) = at 0xc06def8b =3D intr_event_execute_handlers+0x13b ithread_loop(c24de360,cc918d28,0,0,0,...) at 0xc06e05ea =3D = ithread_loop+0x6a fork_exit(c06e0580,c24de360,cc918d28) at 0xc06dc830 =3D fork_exit+0x90 fork_trampoline() at 0xc09cf964 =3D fork_trampoline+0x8 --- trap 0, eip =3D 0, esp =3D 0xcc918d60, ebp =3D 0 --- From owner-freebsd-net@FreeBSD.ORG Thu Sep 1 02:04:03 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9CAB6106564A for ; Thu, 1 Sep 2011 02:04:03 +0000 (UTC) (envelope-from mailinglistmember@mgwigglesworth.net) Received: from mail.mgwigglesworth.net (mail.mgwigglesworth.com [75.146.26.81]) by mx1.freebsd.org (Postfix) with ESMTP id 3FF738FC0A for ; Thu, 1 Sep 2011 02:04:02 +0000 (UTC) To: freebsd-net@freebsd.org Date: Wed, 31 Aug 2011 22:03:49 -0400 Envelope-To: freebsd-net@freebsd.org,freebsd-wireless@freebsd.org References: <4E5D5422.9040609@mgwigglesworth.net> Message-ID: <4E5EE805.5010905@mgwigglesworth.net> From: "Martes G Wigglesworth" Received: from devsecure.mgwigglesworth.net (192.168.5.21 [192.168.5.21]) by mail.mgwigglesworth.net; Wed, 31 Aug 2011 22:04:30 -0400 Organization: M. G. Wigglesworth Holdings, LLC User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.20) Gecko/20110817 Fedora/3.1.12-1.fc14 Lightning/1.0b2 Thunderbird/3.1.12 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: [Solved] Re:Commands for AR5212 cause system to hang using 8.2-STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mailinglistmember@mgwigglesworth.net List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 02:04:03 -0000 On 08/30/2011 09:47 PM, Adrian Chadd wrote: > Can you please try 8.0-RELEASE and see if it works for you? I'd like > to see where things broke along the FreeBSD-7 -> FreeBSD-8.2 path. I finished another upgrade from source, and after the restart the ifconfig commands worked immediately. I guess whatever I did last Spring, was only a partial install. Results were as follows: |router0>ifconfig ath0: flags=8843 metric 0 mtu 2290 ether 00:1b:2f:37:02:46 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running lagg0: flags=8802 metric 0 mtu 1500 ether 00:00:00:00:00:00 media: Ethernet autoselect status: no carrier laggproto failover wlan0: flags=8843 metric 0 mtu 1500 ether 00:1b:2f:37:02:46 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running ssid wrouter0 channel 1 (2412 MHz 11g) bssid 00:1b:2f:37:02:46 country US ecm authmode OPEN privacy OFF txpower 23 scanvalid 60 protmode CTS wme burst dtimperiod 1 -dfs | I am able to get the wlan0 device to associate, and to scan, as listed below: router0> ifconfig wlan0 scan SSID/MESH ID BSSID CHAN RATE S:N INT CAPS CZXQ2 00:26:b8:46:70:8d 1 54M -85:-96 100 EPS WME HTCAP ATH 4EK81 00:26:b8:1f:ba:41 1 54M -92:-96 100 EPS WME HTCAP ATH virgicom-wi... 00:18:e7:0d:16:1a 2 54M 0:0 100 EPS WPA Belkin.306C 94:44:52:a3:f0:6c 1 54M -86:-96 100 EP MESHCONF MESHCONF WPS HTCAP WPA RSN WME 88VC7 00:1f:90:ed:8d:b9 1 54M -88:-96 100 EPS WME ATH ALLEN 00:24:b2:d6:57:2c 2 54M 0:0 100 EPS WME HTCAP ATH WPS However, the current issue may be something that is a simple "staleness" issue with a faulty kernel install, and hostapd. When attempting to get hostapd running, I get the following: router0>/etc/rc.d/hostapd start kldload: can't load wlan_xauth: No such file or directory /etc/rc.d/hostapd: WARNING: Unable to load kernel module wlan_xauth /etc/rc.d/hostapd: WARNING: failed precmd routine for hostapd Here is the currently installed version, which is asking for the seemingly depricated kernel module wlan_xauth. router0> hostapd -v hostapd v0.7.3 User space daemon for IEEE 802.11 AP management, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator Copyright (c) 2002-2010, Jouni Malinen and contributors I have found that I am actually missing the required wlan_xauth.ko wlan_xauth.symbols entries in /boot/kernel so I must have a messy install of the 8.2-STABLE kernel. I am considering this issue resolved, since I can fully utilize the wlan0 mechanism now. Thanks again. -- Respectfully, Martes G Wigglesworth M. G. Wigglesworth Holdings, LLC www.mgwigglesworth.net From owner-freebsd-net@FreeBSD.ORG Thu Sep 1 02:08:24 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D97041065670; Thu, 1 Sep 2011 02:08:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7E1B48FC08; Thu, 1 Sep 2011 02:08:24 +0000 (UTC) Received: by vxh11 with SMTP id 11so1266037vxh.13 for ; Wed, 31 Aug 2011 19:08:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=dW7miiAxsWcWv9y6mLA1hn3ROoaIuPNgpROyeaOcQho=; b=er/xR9cboNuH5S9co2FkJfw7iEkID6SvxwYonvMq7MooVigk0F63ZeG8lXLAVijjFH t0tECmnY6xLKTlufoQB5sd+UU2PP1Up0ApLdgRWPHSCIdDieO2O2z/N7pMGtLmtLpV1s OyQNA3gDinPR+HhM5OqQmPkdgm4jG2oxcZi5w= MIME-Version: 1.0 Received: by 10.52.20.106 with SMTP id m10mr1033132vde.328.1314842903604; Wed, 31 Aug 2011 19:08:23 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.52.33.49 with HTTP; Wed, 31 Aug 2011 19:08:23 -0700 (PDT) In-Reply-To: <4E5EE805.5010905@mgwigglesworth.net> References: <4E5D5422.9040609@mgwigglesworth.net> <4E5EE805.5010905@mgwigglesworth.net> Date: Thu, 1 Sep 2011 10:08:23 +0800 X-Google-Sender-Auth: TuZAs7kRwpSwEyTOaKYkOX0V0-g Message-ID: From: Adrian Chadd To: mailinglistmember@mgwigglesworth.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org, freebsd-wireless@freebsd.org Subject: Re: [Solved] Re:Commands for AR5212 cause system to hang using 8.2-STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Sep 2011 02:08:24 -0000 I didn't think wlan_xauth was deprecated; it should be installed in /boot/kernel/ . Adrian On 1 September 2011 10:03, Martes G Wigglesworth wrote: > On 08/30/2011 09:47 PM, Adrian Chadd wrote: >> >> Can you please try 8.0-RELEASE and see if it works for you? I'd like >> to see where things broke along the FreeBSD-7 -> =A0FreeBSD-8.2 path. > > I finished another upgrade from source, and after the restart the ifconfi= g > commands worked immediately. > I guess whatever I did last Spring, was only a partial install. > Results were as follows: > > |router0>ifconfig > ath0: flags=3D8843 metric 0 mtu 2= 290 > =A0 =A0 =A0 =A0ether 00:1b:2f:37:02:46 > =A0 =A0 =A0 =A0media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <= hostap> > =A0 =A0 =A0 =A0status: running > lagg0: flags=3D8802 metric 0 mtu 1500 > =A0 =A0 =A0 =A0ether 00:00:00:00:00:00 > =A0 =A0 =A0 =A0media: Ethernet autoselect > =A0 =A0 =A0 =A0status: no carrier > =A0 =A0 =A0 =A0laggproto failover > wlan0: flags=3D8843 metric 0 mtu = 1500 > =A0 =A0 =A0 =A0ether 00:1b:2f:37:02:46 > =A0 =A0 =A0 =A0media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <= hostap> > =A0 =A0 =A0 =A0status: running > =A0 =A0 =A0 =A0ssid wrouter0 channel 1 (2412 MHz 11g) bssid 00:1b:2f:37:0= 2:46 > =A0 =A0 =A0 =A0country US ecm authmode OPEN privacy OFF txpower 23 scanva= lid 60 > =A0 =A0 =A0 =A0protmode CTS wme burst dtimperiod 1 -dfs | > > > I am able to get the wlan0 device to associate, and to scan, as listed > below: > > router0> ifconfig wlan0 scan > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0SSID/MESH ID =A0 =A0BSSID =A0 =A0 =A0 =A0 = =A0 =A0 =A0CHAN RATE =A0 S:N =A0 =A0 INT > CAPS > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0CZXQ2 =A0 =A0 =A0 =A0 =A0 00:26:b8:46:70:8= d =A0 =A01 =A0 54M -85:-96 =A0100 EPS > =A0WME HTCAP ATH > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A04EK81 =A0 =A0 =A0 =A0 =A0 00:26:b8:1f:ba:4= 1 =A0 =A01 =A0 54M -92:-96 =A0100 EPS > =A0WME HTCAP ATH > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0virgicom-wi... =A000:18:e7:0d:16:1a =A0 = =A02 =A0 54M =A0 0:0 =A0 =A0100 EPS > =A0WPA > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Belkin.306C =A0 =A0 94:44:52:a3:f0:6c =A0 = =A01 =A0 54M -86:-96 =A0100 EP > =A0 MESHCONF MESHCONF WPS HTCAP WPA RSN WME > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A088VC7 =A0 =A0 =A0 =A0 =A0 00:1f:90:ed:8d:b= 9 =A0 =A01 =A0 54M -88:-96 =A0100 EPS > =A0WME ATH > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0ALLEN =A0 =A0 =A0 =A0 =A0 00:24:b2:d6:57:2= c =A0 =A02 =A0 54M =A0 0:0 =A0 =A0100 EPS > =A0WME HTCAP ATH WPS > > > However, the current issue may be something that is a simple "staleness" > issue with a faulty kernel install, and hostapd. > When attempting to get hostapd running, I get the following: > > > router0>/etc/rc.d/hostapd start > kldload: can't load wlan_xauth: No such file or directory > =A0 =A0 =A0 =A0 =A0 =A0 =A0/etc/rc.d/hostapd: WARNING: Unable to load ker= nel module > wlan_xauth > =A0 =A0 =A0 =A0 =A0 =A0 =A0/etc/rc.d/hostapd: WARNING: failed precmd rout= ine for hostapd > > > Here is the currently installed version, which is asking for the seemingl= y > depricated kernel module wlan_xauth. > > router0> hostapd -v > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0hostapd v0.7.3 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0User space daemon for IEEE 802.11 AP manag= ement, > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authentica= tor > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Copyright (c) 2002-2010, Jouni Malinen and > contributors > > > I have found that I am actually missing the required wlan_xauth.ko > wlan_xauth.symbols entries in /boot/kernel so I must have a messy install= of > the 8.2-STABLE kernel. > > I am considering this issue resolved, since I can fully utilize the wlan0 > mechanism now. > > Thanks again. > > -- > Respectfully, > > > Martes G Wigglesworth > M. G. Wigglesworth Holdings, LLC > www.mgwigglesworth.net > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Thu Sep 1 03:46:05 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D83071065670 for ; Thu, 1 Sep 2011 03:46:05 +0000 (UTC) (envelope-from ivsan@ngs.ru) Received: from smtpout17.ngs.ru (smtpout17.ngs.ru [195.93.186.223]) by mx1.freebsd.org (Postfix) with ESMTP id 32A4E8FC17 for ; Thu, 1 Sep 2011 03:46:04 +0000 (UTC) Received: from smtpout.ngs.ru (imx2.in.ngs.ru [172.16.0.5]) by smtpout17.ngs.ru (smtpout17.ngs.ru) with ESMTP id AE59A71D87D9 for ; Thu, 1 Sep 2011 10:35:24 +0700 (NOVST) Received: from mx14.intranet.ru (unknown [172.16.7.2]) by mail.ngs.ru (smtp) with ESMTP id DB240C2EAE184; Thu, 1 Sep 2011 10:35:20 +0700 (NOVST) Received: from mx16.intranet.ru (unknown [172.16.7.4]) by mx14.intranet.ru (mx14.intranet.ru) with ESMTP id D9281FB61; Thu, 1 Sep 2011 10:35:20 +0700 (NOVST) Received: from [80.242.66.33] (account ivsan@ngs.ru) by mx16.intranet.ru (CommuniGate Pro WebUser 4.3.11) with HTTP id 9695190; Thu, 01 Sep 2011 07:35:20 +0400 From: "Ivan Alexandrovich" To: freebsd-net@freebsd.org Date: Thu, 01 Sep 2011 10:35:20 +0700 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_===9695190====mx16.intranet.ru===_" Cc: Kurt Jaeger Subject: Re: Subject: ethernet Q-in-Q ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Sep 2011 03:46:05 -0000 This is a multi-part MIME message --_===9695190====mx16.intranet.ru===_ Content-Type: text/plain; charset="KOI8-R"; format="flowed" Content-Transfer-Encoding: 8bit Hi Here's ugly patch against in 8.2-RELEASE (see attachment) that makes vlan nesting possible. # ifconfig em0.15 create # ifconfig em0.15.18 create Don't know about possible side effects though. I suppose it doesn't play well wth bridges etc. With ng_vlan nesting is also possible, but since 8.0 I had to comment out this node name check in ng_ether.c: if ((node = ng_name2noderef(NULL, ifp->if_xname)) != NULL) { NG_NODE_UNREF(node); return; Best regards, Ivan Tue, 30 Aug 2011 15:01:18 +0200 Kurt Jaeger wrote: > Hi! > > What about 802.1q VLANs encapsulated in another 802.1q VLAN ? > > On FreeBSD 8.1 or 9.0-BETA1: > > ifconfig vlan123 create > ifconfig vlan123 vlandev em0 vlan 123 > ifconfig vlan400 create > ifconfig vlan400 vlandev vlan123 vlan 400 > ------ > ifconfig: SIOCSETVLAN: Protocol not supported > ------ > > Any ideas ? > > -- > pi@opsec.eu +49 171 3101372 9 years to go ! --_===9695190====mx16.intranet.ru===_ Content-Type: text/x-diff Content-Disposition: attachment; filename="if_vlan.patch" Content-Transfer-Encoding: base64 I3NyYy9zeXMvbmV0L2lmX3ZsYW4uYwotLS0gaWZfdmxhbi5jLm9yaWcgICAgICAyMDEwLTEy LTIxIDIzOjA5OjI1LjAwMDAwMDAwMCArMDYwMAorKysgaWZfdmxhbi5jICAgMjAxMS0wNS0z MSAyMzoxNDo1NS4wMDAwMDAwMDAgKzA3MDAKQEAgLTY2NSw3ICs2NjUsNyBAQAogICAgICAg IC8qIENoZWNrIGZvciA8ZXRoZXJpZj4uPHZsYW4+IHN0eWxlIGludGVyZmFjZSBuYW1lcy4g Ki8KICAgICAgICBJRk5FVF9STE9DS19OT1NMRUVQKCk7CiAgICAgICAgVEFJTFFfRk9SRUFD SChpZnAsICZWX2lmbmV0LCBpZl9saW5rKSB7Ci0gICAgICAgICAgICAgICBpZiAoaWZwLT5p Zl90eXBlICE9IElGVF9FVEhFUikKKyAgICAgICAgICAgICAgIGlmIChpZnAtPmlmX3R5cGUg IT0gSUZUX0VUSEVSICYmIGlmcC0+aWZfdHlwZSAhPSBJRlRfTDJWTEFOKQogICAgICAgICAg ICAgICAgICAgICAgICBjb250aW51ZTsKICAgICAgICAgICAgICAgIGlmIChzdHJuY21wKGlm cC0+aWZfeG5hbWUsIG5hbWUsIHN0cmxlbihpZnAtPmlmX3huYW1lKSkgIT0gMCkKICAgICAg ICAgICAgICAgICAgICAgICAgY29udGludWU7CkBAIC0xMDQ1LDcgKzEwNDUsNyBAQAogICAg ICAgIC8qIFZJRCBudW1iZXJzIDB4MCBhbmQgMHhGRkYgYXJlIHJlc2VydmVkICovCiAgICAg ICAgaWYgKHRhZyA9PSAwIHx8IHRhZyA9PSAweEZGRikKICAgICAgICAgICAgICAgIHJldHVy biAoRUlOVkFMKTsKLSAgICAgICBpZiAocC0+aWZfdHlwZSAhPSBJRlRfRVRIRVIpCisgICAg ICAgaWYgKHAtPmlmX3R5cGUgIT0gSUZUX0VUSEVSICYmIHAtPmlmX3R5cGUgIT0gSUZUX0wy VkxBTikKICAgICAgICAgICAgICAgIHJldHVybiAoRVBST1RPTk9TVVBQT1JUKTsKICAgICAg ICBpZiAoKHAtPmlmX2ZsYWdzICYgVkxBTl9JRkZMQUdTKSAhPSBWTEFOX0lGRkxBR1MpCiAg ICAgICAgICAgICAgICByZXR1cm4gKEVQUk9UT05PU1VQUE9SVCk7Cgo= --_===9695190====mx16.intranet.ru===_-- From owner-freebsd-net@FreeBSD.ORG Thu Sep 1 07:37:26 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D59F1065670 for ; Thu, 1 Sep 2011 07:37:26 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id 40A308FC0A for ; Thu, 1 Sep 2011 07:37:26 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1Qz1pz-000COl-Vp; Thu, 01 Sep 2011 09:37:23 +0200 Date: Thu, 1 Sep 2011 09:37:23 +0200 From: Kurt Jaeger To: freebsd-net@freebsd.org Message-ID: <20110901073723.GM28186@home.opsec.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: Ivan Alexandrovich Subject: Re: Subject: ethernet Q-in-Q ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Sep 2011 07:37:26 -0000 Hi! > Here's ugly patch against in 8.2-RELEASE (see attachment) that > makes vlan nesting possible. > Don't know about possible side effects though. > I suppose it doesn't play well wth bridges etc. Is there an PR for that ? Should I create one 8-) ? Any comments on the side effects from other readers of this list ? Any chance to get the patch in the standard kernel ? I'm far from being an expert in those things, so what might be reasons for not including this patch ? -- pi@opsec.eu +49 171 3101372 9 years to go ! From owner-freebsd-net@FreeBSD.ORG Thu Sep 1 08:15:55 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0133106566B for ; Thu, 1 Sep 2011 08:15:55 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id 625678FC0C for ; Thu, 1 Sep 2011 08:15:55 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1Qz2RH-000D0n-IK; Thu, 01 Sep 2011 10:15:55 +0200 Date: Thu, 1 Sep 2011 10:15:55 +0200 From: Kurt Jaeger To: freebsd-net@freebsd.org Message-ID: <20110901081555.GN28186@home.opsec.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: Ivan Alexandrovich Subject: ng_vlan since 8.x, was: Re: ethernet Q-in-Q ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Sep 2011 08:15:55 -0000 Hi! Ivan wrote: > With ng_vlan nesting is also possible, but since 8.0 > I had to comment out this node name check in ng_ether.c: > > if ((node = ng_name2noderef(NULL, ifp->if_xname)) != NULL) { > NG_NODE_UNREF(node); > return; About the ng_vlan approach -- 4 years ago you described the setup with ng_vlan (thank you, I'll test it soon): http://lists.freebsd.org/pipermail/freebsd-net/2007-August/015163.html This patch of yours -- is there an PR for it ? Why was is not included ? -- pi@opsec.eu +49 171 3101372 9 years to go ! From owner-freebsd-net@FreeBSD.ORG Thu Sep 1 19:04:53 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C60E1065670 for ; Thu, 1 Sep 2011 19:04:53 +0000 (UTC) (envelope-from lacombar@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3DAAE8FC0A for ; Thu, 1 Sep 2011 19:04:52 +0000 (UTC) Received: by ywo32 with SMTP id 32so2083156ywo.13 for ; Thu, 01 Sep 2011 12:04:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:cc:subject:date:message-id:x-mailer; bh=lFAJDfo5neVuqEzh+jtDVutLqkAGJA+k36JRcpLrx84=; b=YOB52Uqmu1ccRUwMqYIy8LTbV2Vb4cv7ydj3QHv9n5cE7vQ6M/Z4tjcHTv/JnntbOZ PWJfDupuXHu9ewDZC0nggYqlEgKgmX+QWp5R5nyOPMIPRlBQ4Pv5wQ2frdHvsczCl+vS Emzz3RYbcGYJ5Ky5zd8/JW765yXDgB6TBo78s= Received: by 10.151.5.2 with SMTP id h2mr387569ybi.127.1314903892460; Thu, 01 Sep 2011 12:04:52 -0700 (PDT) Received: from localhost.localdomain (69-165-142-232.dsl.teksavvy.com [69.165.142.232]) by mx.google.com with ESMTPS id u31sm190225ybu.9.2011.09.01.12.04.50 (version=SSLv3 cipher=OTHER); Thu, 01 Sep 2011 12:04:51 -0700 (PDT) From: Arnaud Lacombe To: freebsd-net@freebsd.org Date: Thu, 1 Sep 2011 15:04:34 -0400 Message-Id: <1314903874-27581-1-git-send-email-lacombar@gmail.com> X-Mailer: git-send-email 1.7.6.153.g78432 Cc: Jack Vogel , Arnaud Lacombe Subject: [PATCH] Fix igb(4) build on 7-STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Sep 2011 19:04:53 -0000 Driver from HEAD missed to isolate a variable. Cc: Jack Vogel Signed-off-by: Arnaud Lacombe --- sys/dev/e1000/if_igb.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/sys/dev/e1000/if_igb.c b/sys/dev/e1000/if_igb.c index cbf4d23..7fb2da0 100644 --- a/sys/dev/e1000/if_igb.c +++ b/sys/dev/e1000/if_igb.c @@ -2235,7 +2235,9 @@ igb_allocate_legacy(struct adapter *adapter) { device_t dev = adapter->dev; struct igb_queue *que = adapter->queues; +#if __FreeBSD_version >= 800000 struct tx_ring *txr = adapter->tx_rings; +#endif int error, rid = 0; /* Turn off all interrupts */ -- 1.7.6.153.g78432 From owner-freebsd-net@FreeBSD.ORG Thu Sep 1 23:20:24 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 707B9106566B for ; Thu, 1 Sep 2011 23:20:24 +0000 (UTC) (envelope-from arusan@gmx.com) Received: from mailout-eu.gmx.com (mailout-eu.gmx.com [213.165.64.43]) by mx1.freebsd.org (Postfix) with SMTP id EABFF8FC14 for ; Thu, 1 Sep 2011 23:20:23 +0000 (UTC) Received: (qmail 7935 invoked by uid 0); 1 Sep 2011 23:20:22 -0000 Received: from 200.28.73.30 by rms-eu006.v300.gmx.net with HTTP Date: Fri, 02 Sep 2011 01:20:20 +0200 From: "ANdrei" Message-ID: <20110901232021.261360@gmx.com> MIME-Version: 1.0 To: freebsd-net@freebsd.org X-Authenticated: #70645713 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 X-GMX-UID: UGIJIWpeMydhEYaiX25ldWVjaGRhZlox Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: RTL8168/8111 re PHY write failed X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Sep 2011 23:20:24 -0000 hi, I ran with no problems 8.0 on this machine, then upgraded to 8.2-RELEASE which worked ok for ~2weeks. Since yesterday I keep getting re1: reset never completed! re1: PHY write failed re1: PHY write failed re1: PHY write failed for one of the network interfaces. I have 3, all same chipset I think: one integrated (re2) and two on PCI-E (re0 and re1). only re1 has problems, the rest are fine (with one detail to mention: sometimes at boot re2 is not seen, it does not exist. rebooting makes it visible again - happens seldom). after this the status line normally shown by ifconfig disappears (it is still there for the 2 other interfaces that are ok) and for media it says: media: Ethernet autoselect (none) I tried disabling RX/TX checksums, UP/DOWN the interface, it does never recover. Reboot might fix it, but it seems to go again to this "dead" state in a few minutes - sometimes it boots like this. It's not a cable, I switched them (this is a bridge, so which cable goes where does not matter in my case) - still the same problem. Any ideas? It worked exactly like this for 2 full weeks with absolutely no problem, now I keep getting this almost immediately after reboot. Please CC me if replying, I am not subscribed to the list. BR. Andrei R. From owner-freebsd-net@FreeBSD.ORG Fri Sep 2 03:45:01 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40FB41065675 for ; Fri, 2 Sep 2011 03:45:01 +0000 (UTC) (envelope-from mailinglistmember@mgwigglesworth.net) Received: from mail.mgwigglesworth.net (mail.mgwigglesworth.com [75.146.26.81]) by mx1.freebsd.org (Postfix) with ESMTP id BC2A68FC14 for ; Fri, 2 Sep 2011 03:45:00 +0000 (UTC) To: freebsd-net@freebsd.org, freebsd-wireless@freebsd.org Date: Thu, 01 Sep 2011 23:43:44 -0400 Envelope-To: freebsd-net@freebsd.org,freebsd-wireless@freebsd.org References: <4E5D5422.9040609@mgwigglesworth.net> <4E5EE805.5010905@mgwigglesworth.net> Message-ID: <4E6050F0.2040203@mgwigglesworth.net> From: "Martes G Wigglesworth" Received: from devsecure.mgwigglesworth.net (192.168.5.21 [192.168.5.21]) by mail.mgwigglesworth.net; Thu, 01 Sep 2011 23:44:59 -0400 Organization: M. G. Wigglesworth Holdings, LLC User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.20) Gecko/20110817 Fedora/3.1.12-1.fc14 Lightning/1.0b2 Thunderbird/3.1.12 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: [Solved] Re:Commands for AR5212 cause system to hang using 8.2-STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mailinglistmember@mgwigglesworth.net List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 03:45:01 -0000 On 08/31/2011 10:08 PM, Adrian Chadd wrote: > I didn't think wlan_xauth was deprecated; it should be installed in > /boot/kernel/ . > > > Adrian From the freenode #freebsd channel, I discovered just what you have indicated, and was in the process of correcting a bad kernel install. After installing the kernel again, all required dependencies for hostapd have been restored, and it will start, and run. However, the new issue is that my wlan0 device will be setup with all the device settings of hostap AP mode, except for the ip address. The device becomes active, and registers as an access point having the desired ssid, however, no IP address is ever issues during the rc.conf setup process. Example: (with hostapd activated on boot) wlan0: flags=8843 metric 0 mtu 1500 ether 00:1b:2f:37:02:46 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running ssid wireless2 channel 1 (2412 MHz 11g) bssid 00:1b:2f:37:02:46 country US ecm authmode WPA privacy MIXED deftxkey 2 AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 23 scanvalid 60 protmode CTS wme burst dtimperiod 1 -dfs (without hostapd activated on boot) wlan0: flags=8843 metric 0 mtu 1500 ether 00:1b:2f:37:02:46 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running ssid wrouter0 channel 1 (2412 MHz 11g) bssid 00:1b:2f:37:02:46 country US ecm authmode OPEN privacy OFF txpower 23 scanvalid 60 protmode CTS wme burst dtimperiod 1 -dfs rc.conf section for this device is as follows: wlans_ath0="wlan0" create_args_wlan0="wlanmode hostap" ifconfig_wlan0="inet 192.168.200.1 netmask 255.255.0.0 ssid "wrouter0" mode 54g channel 1" However, all works perfectly, if I simply assign the intended ip address to the wlan0 device. Any input on this? -- Respectfully, Martes G Wigglesworth M. G. Wigglesworth Holdings, LLC www.mgwigglesworth.net From owner-freebsd-net@FreeBSD.ORG Fri Sep 2 09:46:18 2011 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55642106564A; Fri, 2 Sep 2011 09:46:18 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 6B0908FC12; Fri, 2 Sep 2011 09:46:17 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA16779; Fri, 02 Sep 2011 12:28:25 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QzQ2z-000EZt-6m; Fri, 02 Sep 2011 12:28:25 +0300 Message-ID: <4E60A1B8.7080607@FreeBSD.org> Date: Fri, 02 Sep 2011 12:28:24 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110830 Thunderbird/6.0 MIME-Version: 1.0 To: freebsd-net@FreeBSD.org, freebsd-standards@FreeBSD.org X-Enigmail-Version: undefined Content-Type: text/plain; charset=X-VIET-VPS Content-Transfer-Encoding: 7bit Cc: Subject: POLLHUP on never connected socket X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Sep 2011 09:46:18 -0000 I see a problem where FreeBSD kernel (recent head) returns POLLHUP _alone_ (0x10) for a socket that has never been connected - a client socket for which connect(2) failed. There is also a piece of software that doesn't expect that flag and exhibits illogical behavior because of it. This is how POSIX describes POLLHUP: POLLHUP The device has been disconnected. This event and POLLOUT are mutually-exclusive; a stream can never be writable if a hangup has occurred. However, this event and POLLIN, POLLRDNORM, POLLRDBAND, or POLLPRI are not mutually-exclusive. This flag is only valid in the revents bitmask; it shall be ignored in the events member. For me "disconnected" _implies_ that the device should have been connected first. But this is not explicitly said anywhere. Also, I think it's possible that a socket gets connected and immediately disconnected (before poll(2) is called), then the POLLHUP would be appropriate in any interpretation. So, I am inclined to think that the software should check for POLLHUP. But I would like to ask your opinion since the problem appears to be FreeBSD-specific. -- Andriy Gapon From owner-freebsd-net@FreeBSD.ORG Fri Sep 2 10:40:20 2011 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 255E3106566C; Fri, 2 Sep 2011 10:40:20 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (relay02.stack.nl [IPv6:2001:610:1108:5010::104]) by mx1.freebsd.org (Postfix) with ESMTP id B63FB8FC1C; Fri, 2 Sep 2011 10:40:19 +0000 (UTC) Received: from turtle.stack.nl (turtle.stack.nl [IPv6:2001:610:1108:5010::132]) by mx1.stack.nl (Postfix) with ESMTP id 193EF3593D6; Fri, 2 Sep 2011 12:40:19 +0200 (CEST) Received: by turtle.stack.nl (Postfix, from userid 1677) id 0CDD7173A8; Fri, 2 Sep 2011 12:40:19 +0200 (CEST) Date: Fri, 2 Sep 2011 12:40:19 +0200 From: Jilles Tjoelker To: Andriy Gapon Message-ID: <20110902104018.GA12845@stack.nl> References: <4E60A1B8.7080607@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E60A1B8.7080607@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-net@FreeBSD.org, freebsd-standards@FreeBSD.org Subject: Re: POLLHUP on never connected socket X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Sep 2011 10:40:20 -0000 On Fri, Sep 02, 2011 at 12:28:24PM +0300, Andriy Gapon wrote: > I see a problem where FreeBSD kernel (recent head) returns POLLHUP > _alone_ (0x10) for a socket that has never been connected - a client > socket for which connect(2) failed. There is also a piece of software > that doesn't expect that flag and exhibits illogical behavior because > of it. That would be a bug in that software. Returning POLLHUP alone is clearly valid. > This is how POSIX describes POLLHUP: > POLLHUP > The device has been disconnected. This event and POLLOUT are > mutually-exclusive; a stream can never be writable if a hangup has > occurred. However, this event and POLLIN, POLLRDNORM, POLLRDBAND, or > POLLPRI are not mutually-exclusive. This flag is only valid in the > revents bitmask; it shall be ignored in the events member. Together with the description of POLLIN which says that data may be read without blocking, this seems to mean that if POLLHUP is set alone, there is no point in calling read() since it will return 0 or -1 immediately. If POLLHUP and POLLIN are both set, there is still data in the buffer (in FreeBSD, POLLHUP | POLLIN is often returned even if there is no data, to keep buggy applications from breaking). A complicating factor is that there are situations where read() returns 0, but yet it is not a hangup. For example, if a user types the EOF character (such as ^D) in a terminal, this causes read() to return 0 but the terminal remains writable (and writing to it may even block). This is the "zero length message" which is under the obsolescent STREAMS marking, even though it applies to terminals in all implementations. Similarly, if the other side has done the equivalent of shutdown(SHUT_WR), read() will return 0 but POLLHUP must not be returned as it would prevent the application from waiting for space in the outgoing socket buffer; therefore POLLIN must be returned. Similar considerations apply to other shutdown() calls (but note that shutdown(SHUT_RD) is not sent to the other side). The other way around, read() may fail after poll() did not return POLLHUP if the connection had closed in the meantime. > For me "disconnected" _implies_ that the device should have been > connected first. But this is not explicitly said anywhere. Also, I > think it's possible that a socket gets connected and immediately > disconnected (before poll(2) is called), then the POLLHUP would be > appropriate in any interpretation. So, I am inclined to think that > the software should check for POLLHUP. But I would like to ask your > opinion since the problem appears to be FreeBSD-specific. There was a connection attempt in progress that failed at some point, which seems close enough to "disconnected". Alternatively, POLLERR could be set but could activate more bugs in applications. Comparisons with things like "connected and immediately disconnected" and "connection closed after poll() returned something" are useful in reasoning about this. Ports people have complained about poll() behaviour before, are there configure scripts that attempt to check if we ever return POLLHUP alone and only check for POLLIN if not? -- Jilles Tjoelker From owner-freebsd-net@FreeBSD.ORG Fri Sep 2 11:04:41 2011 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD9CD106566B; Fri, 2 Sep 2011 11:04:41 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id E7CA28FC12; Fri, 2 Sep 2011 11:04:39 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA18037; Fri, 02 Sep 2011 14:04:37 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QzRY5-000Ee8-4F; Fri, 02 Sep 2011 14:04:37 +0300 Message-ID: <4E60B842.8050506@FreeBSD.org> Date: Fri, 02 Sep 2011 14:04:34 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110830 Thunderbird/6.0 MIME-Version: 1.0 To: Jilles Tjoelker References: <4E60A1B8.7080607@FreeBSD.org> <20110902104018.GA12845@stack.nl> In-Reply-To: <20110902104018.GA12845@stack.nl> X-Enigmail-Version: undefined Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@FreeBSD.org, freebsd-standards@FreeBSD.org Subject: Re: POLLHUP on never connected socket X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Sep 2011 11:04:41 -0000 on 02/09/2011 13:40 Jilles Tjoelker said the following: > Ports people have complained about poll() behaviour before, are there > configure scripts that attempt to check if we ever return POLLHUP alone > and only check for POLLIN if not? Not sure about that other software and how POLLIN is related here. The software in question (mozilla nspr) checks for POLLNVAL, POLLERR, POLLPRI and POLLOUT to determine if anything interesting has happened to a connection supposed to be in progress. They aren't checking for POLLHUP at all and thus they keep thinking that the connection is still in progress when they get it. -- Andriy Gapon From owner-freebsd-net@FreeBSD.ORG Fri Sep 2 11:36:43 2011 Return-Path: Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD0B1106566B for ; Fri, 2 Sep 2011 11:36:43 +0000 (UTC) (envelope-from ache@vniz.net) Received: from vniz.net (vniz.net [194.87.13.69]) by mx1.freebsd.org (Postfix) with ESMTP id 4882E8FC13 for ; Fri, 2 Sep 2011 11:36:42 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by vniz.net (8.14.5/8.14.5) with ESMTP id p82BLG6D024064; Fri, 2 Sep 2011 15:21:16 +0400 (MSK) (envelope-from ache@vniz.net) Received: (from ache@localhost) by localhost (8.14.5/8.14.5/Submit) id p82BLG1k024063; Fri, 2 Sep 2011 15:21:16 +0400 (MSK) (envelope-from ache) Date: Fri, 2 Sep 2011 15:21:16 +0400 From: Andrey Chernov To: Andriy Gapon Message-ID: <20110902112116.GA23835@vniz.net> Mail-Followup-To: Andrey Chernov , Andriy Gapon , Jilles Tjoelker , freebsd-net@FreeBSD.ORG, freebsd-standards@FreeBSD.ORG References: <4E60A1B8.7080607@FreeBSD.org> <20110902104018.GA12845@stack.nl> <4E60B842.8050506@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E60B842.8050506@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-net@FreeBSD.ORG, freebsd-standards@FreeBSD.ORG, Jilles Tjoelker Subject: Re: POLLHUP on never connected socket X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Sep 2011 11:36:43 -0000 On Fri, Sep 02, 2011 at 02:04:34PM +0300, Andriy Gapon wrote: > on 02/09/2011 13:40 Jilles Tjoelker said the following: > > Ports people have complained about poll() behaviour before, are there > > configure scripts that attempt to check if we ever return POLLHUP alone > > and only check for POLLIN if not? > > Not sure about that other software and how POLLIN is related here. > The software in question (mozilla nspr) checks for POLLNVAL, POLLERR, POLLPRI > and POLLOUT to determine if anything interesting has happened to a connection > supposed to be in progress. They aren't checking for POLLHUP at all and thus > they keep thinking that the connection is still in progress when they get it. It seems for such case it should return POLLERR too. -- http://ache.vniz.net/ From owner-freebsd-net@FreeBSD.ORG Fri Sep 2 12:59:58 2011 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD779106564A; Fri, 2 Sep 2011 12:59:58 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 9DA208FC19; Fri, 2 Sep 2011 12:59:57 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA19362; Fri, 02 Sep 2011 15:59:55 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4E60D34B.6050506@FreeBSD.org> Date: Fri, 02 Sep 2011 15:59:55 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110705 Thunderbird/5.0 MIME-Version: 1.0 To: Andrey Chernov , Jilles Tjoelker , freebsd-net@FreeBSD.org, freebsd-standards@FreeBSD.org References: <4E60A1B8.7080607@FreeBSD.org> <20110902104018.GA12845@stack.nl> <4E60B842.8050506@FreeBSD.org> <20110902112116.GA23835@vniz.net> In-Reply-To: <20110902112116.GA23835@vniz.net> X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: Re: POLLHUP on never connected socket X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Sep 2011 12:59:58 -0000 on 02/09/2011 14:21 Andrey Chernov said the following: > On Fri, Sep 02, 2011 at 02:04:34PM +0300, Andriy Gapon wrote: >> on 02/09/2011 13:40 Jilles Tjoelker said the following: >>> Ports people have complained about poll() behaviour before, are there >>> configure scripts that attempt to check if we ever return POLLHUP alone >>> and only check for POLLIN if not? >> >> Not sure about that other software and how POLLIN is related here. >> The software in question (mozilla nspr) checks for POLLNVAL, POLLERR, POLLPRI >> and POLLOUT to determine if anything interesting has happened to a connection >> supposed to be in progress. They aren't checking for POLLHUP at all and thus >> they keep thinking that the connection is still in progress when they get it. > > It seems for such case it should return POLLERR too. > I think that I would agree as this is not a graceful disconnect / hang-up but an error in trying to connect. Anyway I am not an expert in this matters and I'd think that POLLHUP should be checked anyway - better safe than sorry. -- Andriy Gapon From owner-freebsd-net@FreeBSD.ORG Fri Sep 2 18:44:18 2011 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA893106564A; Fri, 2 Sep 2011 18:44:18 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id A08888FC12; Fri, 2 Sep 2011 18:44:17 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id VAA22449; Fri, 02 Sep 2011 21:44:07 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QzYil-000Etz-1x; Fri, 02 Sep 2011 21:44:07 +0300 Message-ID: <4E6123F4.4010209@FreeBSD.org> Date: Fri, 02 Sep 2011 21:44:04 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0.1) Gecko/20110901 Thunderbird/6.0.1 MIME-Version: 1.0 To: Bruce Evans References: <4E60A1B8.7080607@FreeBSD.org> <20110902104018.GA12845@stack.nl> <20110903015445.J957@besplex.bde.org> In-Reply-To: <20110903015445.J957@besplex.bde.org> X-Enigmail-Version: undefined Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@FreeBSD.org, freebsd-standards@FreeBSD.org, Jilles Tjoelker Subject: Re: POLLHUP on never connected socket X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Sep 2011 18:44:18 -0000 on 02/09/2011 20:36 Bruce Evans said the following: > It seems likely that there was a transient connection to cause this > problem. Do we know for sure? Not sure if this what you are asking but when I reproduced the problem it was by connecting to a local port where no one listened for sure. -- Andriy Gapon From owner-freebsd-net@FreeBSD.ORG Fri Sep 2 19:54:44 2011 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BAEC41065672; Fri, 2 Sep 2011 19:54:44 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 92F488FC18; Fri, 2 Sep 2011 19:54:44 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p82Jsism056595; Fri, 2 Sep 2011 19:54:44 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p82Jsiap056591; Fri, 2 Sep 2011 19:54:44 GMT (envelope-from linimon) Date: Fri, 2 Sep 2011 19:54:44 GMT Message-Id: <201109021954.p82Jsiap056591@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/160391: [ieee80211] [patch] Panic in mesh mode X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Sep 2011 19:54:44 -0000 Old Synopsis: Panic in mesh mode New Synopsis: [ieee80211] [patch] Panic in mesh mode Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Fri Sep 2 19:54:11 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=160391 From owner-freebsd-net@FreeBSD.ORG Fri Sep 2 20:08:12 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BEA95106564A; Fri, 2 Sep 2011 20:08:12 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from fallbackmx08.syd.optusnet.com.au (fallbackmx08.syd.optusnet.com.au [211.29.132.10]) by mx1.freebsd.org (Postfix) with ESMTP id 4243C8FC15; Fri, 2 Sep 2011 20:08:11 +0000 (UTC) Received: from mail02.syd.optusnet.com.au (mail02.syd.optusnet.com.au [211.29.132.183]) by fallbackmx08.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p82HaMib008579; Sat, 3 Sep 2011 03:36:22 +1000 Received: from c122-106-165-191.carlnfd1.nsw.optusnet.com.au (c122-106-165-191.carlnfd1.nsw.optusnet.com.au [122.106.165.191]) by mail02.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p82HaHtX015971 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 3 Sep 2011 03:36:18 +1000 Date: Sat, 3 Sep 2011 03:36:17 +1000 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Jilles Tjoelker In-Reply-To: <20110902104018.GA12845@stack.nl> Message-ID: <20110903015445.J957@besplex.bde.org> References: <4E60A1B8.7080607@FreeBSD.org> <20110902104018.GA12845@stack.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, freebsd-standards@freebsd.org, Andriy Gapon Subject: Re: POLLHUP on never connected socket X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Sep 2011 20:08:12 -0000 On Fri, 2 Sep 2011, Jilles Tjoelker wrote: > On Fri, Sep 02, 2011 at 12:28:24PM +0300, Andriy Gapon wrote: >> I see a problem where FreeBSD kernel (recent head) returns POLLHUP >> _alone_ (0x10) for a socket that has never been connected - a client >> socket for which connect(2) failed. There is also a piece of software >> that doesn't expect that flag and exhibits illogical behavior because >> of it. > > That would be a bug in that software. Returning POLLHUP alone is clearly > valid. I might be the author of this (kib committed my fixes). POLLHUP alone is certainly valid, but it is only supposed to happen after a disconnection. My tests (in /usr/src/tools/ regression/poll/pipepoll.c) check for this, but only for fifos. My fixes were mostly to make POLLHUP work at all (actually set it on hangup, so that old readers see it), and to make all the flags properly sticky for incomplete new connections (this includes POLLHUP). From pipepoll.c, about the old reader and a bug in the opposite direction (excessive dependency on POLLHUP in gdb). % /* % * Now we have no writer, but should still have data from the old % * writer. Check that we have both a data-readable condition and a % * hangup condition, and that the data can be read in the usual way. % * Since Linux does this, programs must not quit reading when they % * see POLLHUP; they must see POLLHUP without POLLIN (or another % * input condition) before they decide that there is EOF. gdb-6.1.1 % * is an example of a broken program that quits on POLLHUP only -- % * see its event-loop.c. % */ % ... Then for a new reader, with and without an old reader (this is only tested for fifos since the other supported cases don't have open() and always create a pair of fd's): % if (filetype == FT_FIFO) { % /* % * Check that POLLHUP is sticky for a new reader and for % * the old reader. % */ % fd2 = open(FIFONAME, O_RDONLY | O_NONBLOCK); % if (fd2 < 0) % err(1, "open for read"); % pfd.fd = fd2; % if (poll(&pfd, 1, 0) < 0) % err(1, "poll"); % report(num++, "6b", POLLHUP, pfd.revents); This checks that a new reader on a new fd (while the old reader is still active on the old fd) only sees only POLLHUP. It shouldn't see POLLIN since the test has arranged for there to be no data (otherwise it should see data from the old connection). It shouldn't see POLLOUT sice it is read-only (but see below). And it should see POLLHUP since there _was_ a connection and there isn't a new one yet, especially since the old reader still has it partially open. % pfd.fd = fd; % if (poll(&pfd, 1, 0) < 0) % err(1, "poll"); % report(num++, "6c", POLLHUP, pfd.revents); Check the same for the old reader. % close(fd2); % if (poll(&pfd, 1, 0) < 0) % err(1, "poll"); % report(num++, "6d", POLLHUP, pfd.revents); % } Check that POLLHUP persists even after the old reader goes away. IIRC, this might be different if the old reader goes away before the new reader arrives. It would be reasonable to clear POLLHUP when all readers, all writers and all data go away. But when there is data left, POLLIN must be kept to tell new readers that there is data, and POLLHUP must be kept to tell them that this data is old. The tests are very incomplete for sockets, and cover mainly fifos and normal pipes, with just socketpair() for sockets. The only change that I made to pipepoll.c after it was committed was to check POLLOUT. POLLOUT is normally set (it is set even for a r/o open()!?). But when POLLHUP is set, POLLOUT must be clear (IIRC this is about the one thing that is specified non-fuzzily by POSIX). Thus POLLOUT is expected to be clear when POLLHUP is expected to be set in the above checks, and applications don't need to check for POLLHUP if they only want to do output, and POLLHUP is almost unnecessary (since it almost tracks POLLHUP); POLLHUP is most useful in connection with POLLIN, especially if the fd is r/o and POLLOUT isn't bogusly set for r/o descriptors. There are the following states for POLLHUP | POLLIN: - clear: have a connection but no data - POLLIN: have a connection and data - POLLHUP: had a connection; have no data - POLLHUP | POLLIN: had a connection; have data left by it (or a previous one) Most differences with Linux and bugs are in this area. IIRC, Linux gets this right for some file types but not others. See the test output. >> This is how POSIX describes POLLHUP: >> POLLHUP >> The device has been disconnected. This event and POLLOUT are >> mutually-exclusive; a stream can never be writable if a hangup has >> occurred. However, this event and POLLIN, POLLRDNORM, POLLRDBAND, or >> POLLPRI are not mutually-exclusive. This flag is only valid in the >> revents bitmask; it shall be ignored in the events member. FreeBSD attempts to implement exactly this, with "has been" interpreted as strictly in the past, and the largest possible orthogonality in the setting oF POLLHUP vs the input flags. > Together with the description of POLLIN which says that data may be read > without blocking, this seems to mean that if POLLHUP is set alone, there > is no point in calling read() since it will return 0 or -1 immediately. > If POLLHUP and POLLIN are both set, there is still data in the buffer Indeed. I just remembered that the importance of these flags is more for how they affect the !O_NONBLOCK case that for polling in the O_NONBLOCK case (there is lots of redundancy for the latter). Only POLLIN is critical. If there is data, then a new !O_NONBLOCK open won't block, and read() won't block, so POLLIN must be set and poll() must not block to be consistent. When there is no data but there has been a disconnection, new readers normally block, but if they insist on using O_NONBLOCK for open(), then they will get a hint about the state from POLLHUP. IIRC, POLLHUP causes read() to not block, and the only hint that a reader gets that it should not spin trying the read is that POLLHUP but not POLLIN is set. This spin must be avoided by old readers, and keeping the same state for new readers is very delicate since some choices stop non-blocking opens from being usable to wait for a new writer. The choices made are supposed to be the least worse and the most compatible possible with Linux (see old PRs). Also, select() is more problematic than poll() since it can't return POLLHUP. It esentially has to OR POLLHUP into its input-ready condition, since it must not block() on input if there is a hangup but no data. ISTR that these semantics had to be modified a little so that it doesn't block for an old hangup, though the old hangup can still be seen using poll(). See the select() tests. > (in FreeBSD, POLLHUP | POLLIN is often returned even if there is no > data, to keep buggy applications from breaking). Is it? I think I fixed this in my version. kib didn't want to commit something; maybe it was this. This breaks non-buggy applications that depend on POLLIN being cleared to detect EOF. POLLHUP cannot be used to detect EOF (see the above comment about gdb (gdb loses the final input even on pipes for operations like "echo $command | gdb" when the writer happens to close the pipe first)). Neither poll() nor read() will block if either POLLHUP or POLLIN is set, so POLLIN must be clear to avoid an endless spin trying to read EOF if poll() is trusted. select() can't tell the difference between hangup and no data, so appliations using it must use another method to avoid the spin. Old versions of gdb used select() and then read() returning 0 as giving EOF. This works in most cases, but has races if there are multple readers. > A complicating factor is that there are situations where read() returns > 0, but yet it is not a hangup. For example, if a user types the EOF > character (such as ^D) in a terminal, this causes read() to return 0 but > the terminal remains writable (and writing to it may even block). This > is the "zero length message" which is under the obsolescent STREAMS > marking, even though it applies to terminals in all implementations. Old gdb works on terminals. This is because select() knows the difference between no data on a terminal and the EOF caused by a disconnection, so it blocks if there is no data and no disconnection. When it succeeds, it means that there is data or a disconnection and then read() returning 0 means that it is a disconnection, provided there is only 1 reader and no kernel conditions that clear the data. The "zero length message" stuff is part of the fuzziness in POSIX. The specification is less incomplete for STREAMS, but for other file types it is unclear whether zero length data is data. I think it has to count as data for select() but not for poll(), since select() doesn't have POLLHUP so it has no cause other than null data available to make it return on disconnection, while for poll() counting null data as data makes it impossible for poll() to block waiting for data after a disconnection and thus "fix" the problem with select() not being able to block. EIther choice causes problems and I forget exactly what is done now. > Similarly, if the other side has done the equivalent of > shutdown(SHUT_WR), read() will return 0 but POLLHUP must not be returned > as it would prevent the application from waiting for space in the > outgoing socket buffer; therefore POLLIN must be returned. Similar > considerations apply to other shutdown() calls (but note that > shutdown(SHUT_RD) is not sent to the other side). I'm not very familiar with user-mode socket programming. In the kernel, POLLHUP mostly follows SBS_CANTRCVMORE and SBS_CANTSENDMORE, and these flags work very orthogonally, more so than is possible with POLLHUP. Hmm, don't user-mode sockets (except bound ones?) go away when all the readers and writers go away, unlike for fifos? So the case of new readers with no old readers on an old connection can't happen. > The other way around, read() may fail after poll() did not return > POLLHUP if the connection had closed in the meantime. > >> For me "disconnected" _implies_ that the device should have been >> connected first. But this is not explicitly said anywhere. Also, I >> think it's possible that a socket gets connected and immediately >> disconnected (before poll(2) is called), then the POLLHUP would be >> appropriate in any interpretation. So, I am inclined to think that >> the software should check for POLLHUP. But I would like to ask your >> opinion since the problem appears to be FreeBSD-specific. > > There was a connection attempt in progress that failed at some point, > which seems close enough to "disconnected". Alternatively, POLLERR could > be set but could activate more bugs in applications. It seems likely that there was a transient connection to cause this problem. Do we know for sure? I don't like using POLLERR since it provides almost no information. A transient connection isn't an error. > Comparisons with things like "connected and immediately disconnected" > and "connection closed after poll() returned something" are useful in > reasoning about this. The former isn't really an error. Only failure establishing a connection might be an error. But can that even give a connection? Bruce From owner-freebsd-net@FreeBSD.ORG Fri Sep 2 20:26:22 2011 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A3141065672; Fri, 2 Sep 2011 20:26:22 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail07.syd.optusnet.com.au (mail07.syd.optusnet.com.au [211.29.132.188]) by mx1.freebsd.org (Postfix) with ESMTP id 32DA28FC08; Fri, 2 Sep 2011 20:26:21 +0000 (UTC) Received: from c122-106-165-191.carlnfd1.nsw.optusnet.com.au (c122-106-165-191.carlnfd1.nsw.optusnet.com.au [122.106.165.191]) by mail07.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p82KQJi0032442 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 3 Sep 2011 06:26:20 +1000 Date: Sat, 3 Sep 2011 06:26:19 +1000 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Andriy Gapon In-Reply-To: <4E6123F4.4010209@FreeBSD.org> Message-ID: <20110903053813.V2093@besplex.bde.org> References: <4E60A1B8.7080607@FreeBSD.org> <20110902104018.GA12845@stack.nl> <20110903015445.J957@besplex.bde.org> <4E6123F4.4010209@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@FreeBSD.org, freebsd-standards@FreeBSD.org, Jilles Tjoelker Subject: Re: POLLHUP on never connected socket X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Sep 2011 20:26:22 -0000 On Fri, 2 Sep 2011, Andriy Gapon wrote: > on 02/09/2011 20:36 Bruce Evans said the following: >> It seems likely that there was a transient connection to cause this >> problem. Do we know for sure? > > Not sure if this what you are asking but when I reproduced the problem it was by > connecting to a local port where no one listened for sure. Yes, that's what I'm asking. It should be simpler to fix if it is just a bug and doesn't involve reader/writer races. The code for setting POLLHUP for sockets is simple: from uipc_socket.c: % if ((events & POLLINIGNEOF) == 0) { % if (so->so_rcv.sb_state & SBS_CANTRCVMORE) { % revents |= events & (POLLIN | POLLRDNORM); % if (so->so_snd.sb_state & SBS_CANTSENDMORE) % revents |= POLLHUP; % } % } So POLLHUP tracks SBS_CANTRCVMORE && SBS_CANTSENDMORE exactly, and POLLHUP is never set without POLLIN. But in my version: % if ((events & POLLINIGNEOF) == 0) { % if (so->so_rcv.sb_state & SBS_CANTRCVMORE) { % if (so->so_snd.sb_state & SBS_CANTSENDMORE) % revents |= POLLHUP; % else % revents |= events & (POLLIN | POLLRDNORM); % } % } POLLIN is not set by hangup, bit actually means that there is (non-null) input available. jilles referred to this bug in -current. POLLINIGNEOF is an old attempt to fix this. It gives the caller more control. It works poorly, especially since most callers don't know that it exists. Perhaps SBS_CANTRCVMORE && SBS_CANTSENDMORE condition is too raw/low-level even for sockets. Fifos need more to get the behaviour that they want (as similar as possible to Linux). I quote my hackish version since the version in -current doesn't have any comments and my version does even more: >From fifo_open(), for readers: % mtx_lock(&fifo_mtx); % if (ap->a_mode & FREAD) { % fip->fi_readers++; % if (fip->fi_readers == 1) { % SOCKBUF_LOCK(&fip->fi_writesock->so_snd); % fip->fi_writesock->so_snd.sb_state &= ~SBS_CANTSENDMORE; % SOCKBUF_UNLOCK(&fip->fi_writesock->so_snd); % if (fip->fi_writers > 0) { % wakeup(&fip->fi_writers); % sowwakeup(fip->fi_writesock); % } % } % fdp = td->td_proc->p_fd; % FILEDESC_LOCK(fdp); % fp = fget_locked(fdp, ap->a_fdidx); % /* Abuse f_msgcount as a generation count. */ % fp->f_msgcount = fip->fi_wgen - fip->fi_writers; -current has the above line, and fixes the hack using a new field f_seqcount. % /* % * XXX quick fix: keep any POLLHUP condition sticky if we % * now have more than 1 reader, by clobbering f_msgcount % * here so that POLLINIGNEOF will not be set in % * fifo_poll_f(). (The above subtraction of fi_writers % * works similarly but is probably unnecessary since if % * there is a writer then there won't be a POLLHUP % * condition.) % * % * XXX: the generation counts are probably unnecessary now % * that this is broken to POSIX spec. They are to help % * make any POLLHUP condition sticky only for old readers. % * % * XXX: does this hack work right for a new reader that will % * block? % */ % fp->f_msgcount -= fip->fi_readers - 1; -current doesn't have the above line or the big comment. I forget if this is for more compatibility with Linux, or more correctness. I think the committed regression tests assert the behaviour give by this version, so they will certainly fail for -current. I'm surer of this for the spurious POLLIN with POLLHUP. % FILEDESC_UNLOCK(fdp); % } % int % fifo_poll_f(struct file *fp, int events, struct ucred *cred, struct thread *td) % { % struct file filetmp; % struct fifoinfo *fip; % int levents, revents = 0; % % fip = fp->f_vnode->v_fifoinfo; % levents = events & (POLLIN | POLLPRI | POLLRDNORM | POLLRDBAND); % if (levents) { % filetmp.f_data = fip->fi_readsock; % filetmp.f_cred = fp->f_cred; % if (fp->f_msgcount == fip->fi_wgen) % levents |= POLLINIGNEOF; -current has this (with s/msgcount/seqcount/). This is the only place that seqcount is used. I thought I removed all uses of POLLINIGNEOF in the kernel. % revents |= soo_poll(&filetmp, levents, cred, td); % } % levents = events & (POLLOUT | POLLWRNORM | POLLWRBAND); % if (levents) { % filetmp.f_data = fip->fi_writesock; % filetmp.f_cred = fp->f_cred; % revents |= soo_poll(&filetmp, levents, cred, td); Note that fifo polling calls soo_poll() twice, and it only uses POLLINIGNEOF for the second call. Thus the combination always sets POLLHUP if there is a disconnection. But the second call doesn't ask for POLLIN, so in -current there is no spurious POLLIN to echo POLLHUP in the case where POLLINIGNEOF is used, but there is if it is not. -current is subtly different. Where the above masks out POLLINIGNEOF in the user `events' in the first assignment to levents, -current keeps it. But both versions mask it for the second assignment. Thus my version always ignores the user POLLINIGNEOF for polling of fifos, but -current keeps it partially. -current thus sees POLLHUP and fails to completely ignore EOF even if the user passes POLLINIGNEOF, iff the user events also has one of the output flags set. The user would have to call poll() twice, first with only input flags set and then with output flags set get unmixed behaviour, but this won't work since either of the calls may block and the output check will never ignore EOF. % } % return (revents); % } Bruce From owner-freebsd-net@FreeBSD.ORG Fri Sep 2 21:09:35 2011 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F9F2106564A; Fri, 2 Sep 2011 21:09:35 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 61C568FC0C; Fri, 2 Sep 2011 21:09:33 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id AAA23623; Sat, 03 Sep 2011 00:09:21 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QzazI-000Ezc-UR; Sat, 03 Sep 2011 00:09:20 +0300 Message-ID: <4E6145FF.3090803@FreeBSD.org> Date: Sat, 03 Sep 2011 00:09:19 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0.1) Gecko/20110901 Thunderbird/6.0.1 MIME-Version: 1.0 To: Bruce Evans References: <4E60A1B8.7080607@FreeBSD.org> <20110902104018.GA12845@stack.nl> <20110903015445.J957@besplex.bde.org> <4E6123F4.4010209@FreeBSD.org> <20110903053813.V2093@besplex.bde.org> In-Reply-To: <20110903053813.V2093@besplex.bde.org> X-Enigmail-Version: undefined Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@FreeBSD.org, freebsd-standards@FreeBSD.org, Jilles Tjoelker Subject: Re: POLLHUP on never connected socket X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Sep 2011 21:09:35 -0000 on 02/09/2011 23:26 Bruce Evans said the following: > Yes, that's what I'm asking. It should be simpler to fix if it is just > a bug and doesn't involve reader/writer races. The code for setting > POLLHUP for sockets is simple: from uipc_socket.c: > > % if ((events & POLLINIGNEOF) == 0) { > % if (so->so_rcv.sb_state & SBS_CANTRCVMORE) { > % revents |= events & (POLLIN | POLLRDNORM); > % if (so->so_snd.sb_state & SBS_CANTSENDMORE) > % revents |= POLLHUP; > % } > % } > > So POLLHUP tracks SBS_CANTRCVMORE && SBS_CANTSENDMORE exactly, and POLLHUP > is never set without POLLIN. Umm, it seems that when you say that then you are assuming that the events contain POLLIN. In what I observe events == POLLOUT | POLLPRI and thus only POLLHUP is set in the revents. Not that this means too much, just an observation. > But in my version: > > % if ((events & POLLINIGNEOF) == 0) { > % if (so->so_rcv.sb_state & SBS_CANTRCVMORE) { > % if (so->so_snd.sb_state & SBS_CANTSENDMORE) > % revents |= POLLHUP; > % else > % revents |= events & (POLLIN | POLLRDNORM); > % } > % } > > POLLIN is not set by hangup, bit actually means that there is (non-null) > input available. jilles referred to this bug in -current. -- Andriy Gapon From owner-freebsd-net@FreeBSD.ORG Sat Sep 3 19:26:55 2011 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5357106566B; Sat, 3 Sep 2011 19:26:55 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id ADF578FC13; Sat, 3 Sep 2011 19:26:55 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p83JQtqY093386; Sat, 3 Sep 2011 19:26:55 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p83JQtPP093382; Sat, 3 Sep 2011 19:26:55 GMT (envelope-from linimon) Date: Sat, 3 Sep 2011 19:26:55 GMT Message-Id: <201109031926.p83JQtPP093382@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-net@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/160391: [ieee80211] [patch] Panic in mesh mode X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Sep 2011 19:26:55 -0000 Synopsis: [ieee80211] [patch] Panic in mesh mode Responsible-Changed-From-To: freebsd-net->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Sat Sep 3 19:26:43 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=160391