From owner-freebsd-net@FreeBSD.ORG Mon Aug 11 02:19:17 2008 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 C4A39106567C for ; Mon, 11 Aug 2008 02:19:17 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.227]) by mx1.freebsd.org (Postfix) with ESMTP id 890678FC17 for ; Mon, 11 Aug 2008 02:19:17 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so3040192rvf.43 for ; Sun, 10 Aug 2008 19:19:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=R1aR0bpS0EX7JUeLKo7m+p5xpOJTYCMf9LvpuX8sEh0=; b=DY/rPoa5f+qjHVhr4MJgevL+GEvODNTOmWIQYWUbLl4tDNKJqh4mYSFSbn+gMPrBxH z1rE2vd16r4soNjxuDMSateUlGvpg0FTRhiwnBq6+SBKnJPz3/p3HYhIy1wf+FovhYgn q9s4e2pZn8ZFa+xUjGriJsDTQWHsHaZexGIaQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=Kd/B1z1C+Qfh5W03lbNoaM6i7jpiZwB+hn5SDOCvDudq3rG6quch6MyELjq5UW7LG7 YdeMcBNFHZ2r0kx0FxEGlcHNGrP7U6RLPBAjnDDMU3HJnT35cl3JsOF9DPMYr/5Uh51d Qz+GwtCvtVDPttijAkUkOAp9BnvlDrpjp3/AM= Received: by 10.141.45.16 with SMTP id x16mr3134547rvj.34.1218421157040; Sun, 10 Aug 2008 19:19:17 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id g31sm7719148rvb.2.2008.08.10.19.19.14 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 10 Aug 2008 19:19:16 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m7B2H5Uc050622 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Aug 2008 11:17:05 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m7B2H3N2050620; Mon, 11 Aug 2008 11:17:03 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 11 Aug 2008 11:17:03 +0900 From: Pyun YongHyeon To: Christian Weisgerber Message-ID: <20080811021703.GC50045@cdnetworks.co.kr> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org Subject: Re: Rx/tx hardware checksumming statistics? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Aug 2008 02:19:17 -0000 On Sat, Aug 09, 2008 at 08:12:42PM +0000, Christian Weisgerber wrote: > OpenBSD keeps count of the packets that have undergone IPv4 header/ > TCP/UDP checksumming in hardware. These statics are available with > netstat -s, e.g.: > > ip: > ... > 492152 input datagrams checksum-processed by hardware > 911338 output datagrams checksum-processed by hardware > ... > > This comes in quite handy to check whether checksum offloading > actually works and which protocols are successfully processed this > way. > I don't think it indicates whether checksum offloading actually works as OpenBSD blindly set a flag, which was derived from hardware, to indicate hardware performed the checksum computation. You can still have a chance that checksum offloading does not work even if the counter constantly increase over time. In addition, OpenBSD have a no way to disable checksum offloading feature of hardware on the fly so you have to rebuild the driver to disable checksum offloading in case of broken/buggy hardware. > On FreeBSD, netstat -s does not provide this information. Are these > statistics available in some other way? How would I check whether AFAIK there is no such counters in FreeBSD. > packets have actually been checksummed in hardware? > If checksum offloading didn't work you couldn't get a working connection at all. -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Mon Aug 11 10:02:11 2008 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 D14051065675 for ; Mon, 11 Aug 2008 10:02:11 +0000 (UTC) (envelope-from onuraslan@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.170]) by mx1.freebsd.org (Postfix) with ESMTP id A5EF58FC1A for ; Mon, 11 Aug 2008 10:02:11 +0000 (UTC) (envelope-from onuraslan@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so1633839wfg.7 for ; Mon, 11 Aug 2008 03:02:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=ZnDi5UKDBX4wmCnNcbmIWo8Gtx0jfESghyO/NFWhx7M=; b=ACOCKeYBkvswamPcja0sI2/l4OamvtnGkIC6OY3G6PUUCkIH96uFIpZEKZL8Labm/P 7tPocw5XfwtzreAXgumLfEdo+CoxmxVMjbRsxO8wjwL70m0HUhTBg6AXjplJjiyFY7Ln DwzzvNDtI+gxvDQAgehjOYRKP7w9Q7TqNxlTg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=TWHwj2P0C+ulvO/gDWh9tckTkNo+qoZBUip4LQtyuVzluU5cTpGEA+WlldhpudO+Dg AkI9r462IRfJYn1IO5KKh/Loml0lOSpCAMsYD5LlXicCPVN8w1MFx97lWjemQjEC24Sp fJjA60xaaj0G5f1bdWUZoDGkOpX411Tf4iUzw= Received: by 10.142.230.9 with SMTP id c9mr2030999wfh.343.1218447308997; Mon, 11 Aug 2008 02:35:08 -0700 (PDT) Received: by 10.142.134.1 with HTTP; Mon, 11 Aug 2008 02:35:08 -0700 (PDT) Message-ID: Date: Mon, 11 Aug 2008 12:35:08 +0300 From: "Onur Aslan" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Named Listen IP 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, 11 Aug 2008 10:02:11 -0000 Hi. I am using named for a ns server. Named listening all ips for my machine. But when i reboot machine, my ppp network connecting after started named. named doesn't listening my ppp network's ip. Do you have a solution? Thanks. From owner-freebsd-net@FreeBSD.ORG Mon Aug 11 10:15:09 2008 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 0028C106567A for ; Mon, 11 Aug 2008 10:15:08 +0000 (UTC) (envelope-from ronan@artful.net) Received: from rennes.fr.clara.net (mail.rennes.fr.clara.net [62.240.254.62]) by mx1.freebsd.org (Postfix) with ESMTP id A9F718FC20 for ; Mon, 11 Aug 2008 10:15:07 +0000 (UTC) (envelope-from ronan@artful.net) Received: from localhost (localhost [127.0.0.1]) by rennes.fr.clara.net (Postfix) with ESMTP id B4D983D0C for ; Mon, 11 Aug 2008 11:44:18 +0200 (CEST) X-Virus-Scanned: amavisd-new at X-Spam-Flag: NO X-Spam-Score: -3.099 X-Spam-Level: X-Spam-Status: No, score=-3.099 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1.8, AWL=-1.300, BAYES_50=0.001] Received: from rennes.fr.clara.net ([127.0.0.1]) by localhost (rennes.fr.clara.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 182sMF5kObSm for ; Mon, 11 Aug 2008 11:44:18 +0200 (CEST) Received: from [10.0.1.66] (unknown [10.0.1.66]) by rennes.fr.clara.net (Postfix) with ESMTP id 1ED531D10 for ; Mon, 11 Aug 2008 11:44:18 +0200 (CEST) Message-ID: <48A009F4.4030901@artful.net> Date: Mon, 11 Aug 2008 11:44:20 +0200 From: Ronan Kerambrun User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD 7.0: sockets stuck in CLOSED state... 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, 11 Aug 2008 10:15:09 -0000 Hi all, I have the same problem, but using Varnish. I dont think it is an application bug because Poul-Henning Kamp (the developer of the application) is also a freebsd kernel developper.. # uname -a FreeBSD cache2 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #0: Thu Jun 19 20:37:34 CEST 2008 root@cache2:/usr/obj/usr/src/sys/GENERIC-ULE amd64 # netstat -n |grep -c CLOSED 1518 # varnishd -V varnishd (varnish-1.1.2) Copyright (c) 2006-2007 Linpro AS / Verdens Gang AS Cheers, ronan From owner-freebsd-net@FreeBSD.ORG Mon Aug 11 10:25:58 2008 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 CFB88106566C for ; Mon, 11 Aug 2008 10:25:58 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id 1180B8FC1D for ; Mon, 11 Aug 2008 10:25:57 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id m7BAPsEE083269; Mon, 11 Aug 2008 18:25:54 +0800 (KRAST) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id m7BAPsha083268; Mon, 11 Aug 2008 18:25:54 +0800 (KRAST) (envelope-from eugen) Date: Mon, 11 Aug 2008 18:25:54 +0800 From: Eugene Grosbein To: Onur Aslan Message-ID: <20080811102554.GA82579@svzserv.kemerovo.su> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org Subject: Re: Named Listen IP 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, 11 Aug 2008 10:25:58 -0000 On Mon, Aug 11, 2008 at 12:35:08PM +0300, Onur Aslan wrote: > I am using named for a ns server. Named listening all ips for my > machine. But when i reboot machine, my ppp network connecting after > started named. named doesn't listening my ppp network's ip. Do you > have a solution? By default, named runs as nonprivileged user and to the moment ppp brings interface up named has no right to listen it. The only solution I know is to run named as root, so add to /etc/rc.conf: named_uid="root" Eugene Grosbein From owner-freebsd-net@FreeBSD.ORG Mon Aug 11 11:07:01 2008 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 A07C11065673 for ; Mon, 11 Aug 2008 11:07:01 +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 8273B8FC1D for ; Mon, 11 Aug 2008 11:07:01 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m7BB71ct047268 for ; Mon, 11 Aug 2008 11:07:01 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m7BB70eK047264 for freebsd-net@FreeBSD.org; Mon, 11 Aug 2008 11:07:00 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 11 Aug 2008 11:07:00 GMT Message-Id: <200808111107.m7BB70eK047264@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, 11 Aug 2008 11:07:01 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/27474 net [ipf] [ppp] Interactive use of user PPP and ipfilter c o kern/35442 net [sis] [patch] Problem transmitting runts in if_sis dri a kern/38554 net [patch] changing interface ipaddress doesn't seem to w s kern/39937 net ipstealth issue s kern/77195 net [ipf] [patch] ipfilter ioctl SIOCGNATL does not match o kern/79895 net [ipf] 5.4-RC2 breaks ipfilter NAT when using netgraph s kern/81147 net [net] [patch] em0 reinitialization while adding aliase o kern/86103 net [ipf] Illegal NAT Traversal in IPFilter s kern/86920 net [ndis] ifconfig: SIOCS80211: Invalid argument [regress o kern/87521 net [ipf] [panic] using ipfilter "auth" keyword leads to k o kern/92090 net [bge] bge0: watchdog timeout -- resetting f kern/92552 net A serious bug in most network drivers from 5.X to 6.X o kern/95288 net [pppd] [tty] [panic] if_ppp panic in sys/kern/tty_subr o kern/98978 net [ipf] [patch] ipfilter drops OOW packets under 6.1-Rel o kern/101948 net [ipf] [panic] Kernel Panic Trap No 12 Page Fault - cau f kern/102344 net [ipf] Some packets do not pass through network interfa o bin/105925 net problems with ifconfig(8) and vlan(4) [regression] s kern/105943 net Network stack may modify read-only mbuf chain copies o kern/106316 net [dummynet] dummynet with multipass ipfw drops packets o kern/106438 net [ipf] ipfilter: keep state does not seem to allow repl o kern/108542 net [bce]: Huge network latencies with 6.2-RELEASE / STABL o bin/108895 net pppd(8): PPPoE dead connections on 6.2 [regression] o kern/109308 net [pppd] [panic] Multiple panics kernel ppp suspected [r o kern/109733 net [bge] bge link state issues [regression] o kern/112528 net [nfs] NFS over TCP under load hangs with "impossible p o kern/112686 net [patm] patm driver freezes System (FreeBSD 6.2-p4) i38 o kern/112722 net [udp] IP v4 udp fragmented packet reject o kern/113842 net [ip6] PF_INET6 proto domain state can't be cleared wit o kern/114714 net [gre][patch] gre(4) is not MPSAFE and does not support o kern/114839 net [fxp] fxp looses ability to speak with traffic o kern/115239 net [ipnat] panic with 'kmem_map too small' using ipnat o kern/116077 net [ip] [patch] 6.2-STABLE panic during use of multi-cast o kern/116185 net [iwi] if_iwi driver leads system to reboot o kern/116328 net [bge]: Solid hang with bge interface o kern/116747 net [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile o kern/116837 net [tun] [panic] [patch] ifconfig tunX destroy: panic o kern/117043 net [em] Intel PWLA8492MT Dual-Port Network adapter EEPROM o kern/117271 net [tap] OpenVPN TAP uses 99% CPU on releng_6 when if_tap o kern/117423 net [vlan] Duplicate IP on different interfaces o kern/117448 net [carp] 6.2 kernel crash [regression] o kern/118880 net [ip6] IP_RECVDSTADDR & IP_SENDSRCADDR not implemented o kern/119225 net [wi] 7.0-RC1 no carrier with Prism 2.5 wifi card [regr o kern/119345 net [ath] Unsuported Atheros 5424/2424 and CPU speedstep n o kern/119361 net [bge] bge(4) transmit performance problem o kern/119945 net [rum] [panic] rum device in hostap mode, cause kernel o kern/120130 net [carp] [panic] carp causes kernel panics in any conste o kern/120266 net [panic] gnugk causes kernel panic when closing UDP soc o kern/120304 net [netgraph] [patch] netgraph source assumes 32-bit time o kern/120966 net [rum] kernel panic with if_rum and WPA encryption o kern/121080 net [bge] IPv6 NUD problem on multi address config on bge0 o kern/121181 net [panic] Fatal trap 3: breakpoint instruction fault whi o kern/121298 net [em] [panic] Fatal trap 12: page fault while in kernel o kern/121437 net [vlan] Routing to layer-2 address does not work on VLA o kern/121555 net [panic] Fatal trap 12: current process = 12 (swi1: net o kern/121624 net [em] [regression] Intel em WOL fails after upgrade to o kern/121872 net [wpi] driver fails to attach on a fujitsu-siemens s711 o kern/121983 net [fxp] fxp0 MBUF and PAE o kern/122033 net [ral] [lor] Lock order reversal in ral0 at bootup [reg o kern/122058 net [em] [panic] Panic on em1: taskq o kern/122082 net [in_pcb] NULL pointer dereference in in_pcbdrop o kern/122195 net [ed] Alignment problems in if_ed f kern/122252 net [ipmi] [bge] IPMI problem with BCM5704 (does not work o kern/122290 net [netgraph] [panic] Netgraph related "kmem_map too smal o kern/122427 net [apm] [panic] apm and mDNSResponder cause panic during o kern/122551 net [bge] Broadcom 5715S no carrier on HP BL460c blade usi o kern/122685 net It is not visible passing packets in tcpdump o kern/122743 net [panic] vm_page_unwire: invalid wire count: 0 o kern/122772 net [em] em0 taskq panic, tcp reassembly bug causes radix f kern/122794 net [lagg] Kernel panic after brings lagg(8) up if NICs ar f conf/122858 net [nsswitch.conf] nsswitch in 7.0 is f*cked up o kern/122954 net [lagg] IPv6 EUI64 incorrectly chosen for lagg devices o kern/122989 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/123066 net [ipsec] [panic] kernel trap with ipsec o kern/123160 net [ip] Panic and reboot at sysctl kern.polling.enable=0 f kern/123172 net [bce] Watchdog timeout problems with if_bce f kern/123200 net [netgraph] Server failure due to netgraph mpd and dhcp o conf/123330 net [nsswitch.conf] Enabling samba wins in nsswitch.conf c o kern/123347 net [bge] bge1: watchdog timeout -- linkstate changed to D o kern/123429 net [nfe] [hang] "ifconfig nfe up" causes a hard system lo o kern/123463 net [ipsec] [panic] repeatable crash related to ipsec-tool o bin/123465 net [ip6] route(8): route add -inet6 -interfac o kern/123559 net [iwi] iwi periodically disassociates/associates [regre o kern/123603 net [tcp] tcp_do_segment and Received duplicate SYN o kern/123617 net [tcp] breaking connection when client downloading file o bin/123633 net ifconfig(8) doesn't set inet and ether address in one o kern/123796 net [ipf] FreeBSD 6.1+VPN+ipnat+ipf: port mapping does not o kern/123881 net [tcp] Turning on TCP blackholing causes slow localhost o kern/123968 net [rum] [panic] rum driver causes kernel panic with WPA. o kern/124021 net [ip6] [panic] page fault in nd6_output() o kern/124127 net [msk] watchdog timeout (missed Tx interrupts) -- recov o kern/124753 net [ieee80211] net80211 discards power-save queue packets o kern/124904 net [fxp] EEPROM corruption with Compaq NC3163 NIC o kern/125079 net [ppp] host routes added by ppp with gateway flag (regr f kern/125195 net [fxp] fxp(4) driver failed to initialize device Intel o kern/125920 net [arp] Kernel Routing Table loses Ethernet Link status o bin/125922 net [patch] Deadlock in arp(8) o kern/126075 net [in] Network: internet control accesses beyond end of o kern/126214 net [ath] txpower problem with Atheros wifi card 98 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o conf/23063 net [PATCH] for static ARP tables in rc.network o kern/34665 net [ipf] [hang] ipfilter rcmd proxy "hangs". s bin/41647 net ifconfig(8) doesn't accept lladdr along with inet addr o kern/54383 net [nfs] [patch] NFS root configurations without dynamic s kern/60293 net FreeBSD arp poison patch o kern/64556 net [sis] if_sis short cable fix problems with NetGear FA3 o kern/70904 net [ipf] ipfilter ipnat problem with h323 proxy support o kern/77273 net [ipf] ipfilter breaks ipv6 statefull filtering on 5.3 o kern/77913 net [wi] [patch] Add the APDL-325 WLAN pccard to wi(4) o kern/78090 net [ipf] ipf filtering on bridged packets doesn't work if o bin/79228 net [patch] extend arp(8) to be able to create blackhole r o kern/91594 net [em] FreeBSD > 5.4 w/ACPI fails to detect Intel Pro/10 s kern/91777 net [ipf] [patch] wrong behaviour with skip rule inside an o kern/93378 net [tcp] Slow data transfer in Postfix and Cyrus IMAP (wo o kern/95267 net packet drops periodically appear o kern/95277 net [netinet] [patch] IP Encapsulation mask_match() return o kern/100519 net [netisr] suggestion to fix suboptimal network polling o kern/102035 net [plip] plip networking disables parallel port printing o conf/102502 net [patch] ifconfig name does't rename netgraph node in n o conf/107035 net [patch] bridge interface given in rc.conf not taking a o kern/109470 net [wi] Orinoco Classic Gold PC Card Can't Channel Hop o bin/112557 net [patch] ppp(8) lock file should not use symlink name o kern/114915 net [patch] [pcn] pcn (sys/pci/if_pcn.c) ethernet driver f o bin/116643 net [patch] [request] fstat(1): add INET/INET6 socket deta o bin/117339 net [patch] route(8): loading routing management commands o kern/118727 net [netgraph] [patch] [request] add new ng_pf module a kern/118879 net [bge] [patch] bge has checksum problems on the 5703 ch o bin/118987 net ifconfig(8): ifconfig -l (address_family) does not wor o kern/119432 net [arp] route add -host -iface causes arp e f kern/119516 net [ip6] [panic] _mtx_lock_sleep: recursed on non-recursi o kern/119617 net [nfs] nfs error on wpa network when reseting/shutdown o kern/119791 net [nfs] UDP NFS mount of aliased IP addresses from a Sol o kern/120232 net [nfe] [patch] Bring in nfe(4) to RELENG_6 o kern/120566 net [request]: ifconfig(8) make order of arguments more fr o kern/121257 net [tcp] TSO + natd -> slow outgoing tcp traffic o kern/121443 net [gif] LOR icmp6_input/nd6_lookup o kern/121706 net [netinet] [patch] "rtfree: 0xc4383870 has 1 refs" emit s kern/121774 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/122068 net [ppp] ppp can not set the correct interface with pptpd o kern/122295 net [bge] bge Ierr rate increase (since 6.0R) [regression] o kern/122319 net [wi] imposible to enable ad-hoc demo mode with Orinoco o kern/122697 net [ath] Atheros card is not well supported o kern/122780 net [lagg] tcpdump on lagg interface during high pps wedge f kern/122839 net [multicast] FreeBSD 7 multicast routing problem o kern/122928 net [em] interface watchdog timeouts and stops receiving p o kern/123256 net [wpi] panic: blockable sleep lock with wpi(4) o kern/123892 net [tap] [patch] No buffer space available p kern/123961 net [vr] [patch] Allow vr interface to handle vlans o bin/124004 net ifconfig(8): Cannot assign both an IP and a MAC addres o kern/124160 net [libc] connect(2) function loops indefinitely o kern/124341 net [ral] promiscuous mode for wireless device ral0 looses o kern/124609 net [ipsec] [panic] ipsec 'remainder too big' panic with p o kern/124767 net [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/125181 net [ndis] [patch] with wep enters kdb.enter.unknown, pani o kern/125239 net [gre] kernel crash when using gre o kern/125258 net [socket] socket's SO_REUSEADDR option does not work f kern/125502 net [ral] ifconfig ral0 scan produces no output unless in o kern/125816 net [carp] [bridge] carp stuck in init when using bridge i o kern/125845 net [netinet] [patch] tcp_lro_rx() should make use of hard o kern/126339 net [ipw] ipw driver drops the connection 60 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Aug 11 12:22:36 2008 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 D8E0A1065673 for ; Mon, 11 Aug 2008 12:22:36 +0000 (UTC) (envelope-from mailnull@mips.inka.de) Received: from mail-in-10.arcor-online.net (mail-in-10.arcor-online.net [151.189.21.50]) by mx1.freebsd.org (Postfix) with ESMTP id 6023D8FC08 for ; Mon, 11 Aug 2008 12:22:36 +0000 (UTC) (envelope-from mailnull@mips.inka.de) Received: from mail-in-07-z2.arcor-online.net (mail-in-07-z2.arcor-online.net [151.189.8.19]) by mail-in-10.arcor-online.net (Postfix) with ESMTP id E73C31F4FE9 for ; Mon, 11 Aug 2008 14:22:34 +0200 (CEST) Received: from mail-in-01.arcor-online.net (mail-in-01.arcor-online.net [151.189.21.41]) by mail-in-07-z2.arcor-online.net (Postfix) with ESMTP id D0C672C73EB for ; Mon, 11 Aug 2008 14:22:34 +0200 (CEST) Received: from lorvorc.mips.inka.de (dslb-088-067-125-228.pools.arcor-ip.net [88.67.125.228]) by mail-in-01.arcor-online.net (Postfix) with ESMTP id AAAEB10566E for ; Mon, 11 Aug 2008 14:22:34 +0200 (CEST) Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.14.2/8.14.2) with ESMTP id m7BCMXnq097162 for ; Mon, 11 Aug 2008 14:22:33 +0200 (CEST) (envelope-from mailnull@lorvorc.mips.inka.de) Received: (from mailnull@localhost) by lorvorc.mips.inka.de (8.14.2/8.14.2/Submit) id m7BCMXdH097161 for freebsd-net@freebsd.org; Mon, 11 Aug 2008 14:22:33 +0200 (CEST) (envelope-from mailnull) From: naddy@mips.inka.de (Christian Weisgerber) Date: Mon, 11 Aug 2008 12:22:33 +0000 (UTC) Message-ID: References: <20080811021703.GC50045@cdnetworks.co.kr> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-net@freebsd.org X-Virus-Scanned: ClamAV 0.93.3/8005/Mon Aug 11 13:39:24 2008 on mail-in-01.arcor-online.net X-Virus-Status: Clean Subject: Re: Rx/tx hardware checksumming statistics? 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, 11 Aug 2008 12:22:36 -0000 Pyun YongHyeon wrote: > I don't think it indicates whether checksum offloading actually > works as OpenBSD blindly set a flag, which was derived from > hardware, to indicate hardware performed the checksum computation. Yes. It counts the instances where the network stack assumes that the hardware successfully verified the checksum. That is an interesting number. OpenBSD's re(4) driver is ported from FreeBSD. Recently, Brad Smith has been merging the tx/rx checksum offload support for the newer chips (RTL8111C etc.) into the OpenBSD driver and I have done some testing for him. Looking at the counters, I have noticed: * IP header rx checksumming is only registered for IP/TCP and IP/UDP packets, but not for other protocols, such as IP/ICMP. * If VLAN tagging is enabled, no rx checksumming is registered at all. I don't have documentation for the Realtek chips, so I don't know if the hardware really cannot perform these operations or if the driver simply fails to take advantage of them. Presumably the same limitations also apply to the FreeBSD driver, but without the counters, how can you tell? -- Christian "naddy" Weisgerber naddy@mips.inka.de From owner-freebsd-net@FreeBSD.ORG Mon Aug 11 15:38:57 2008 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 26EB1106566B for ; Mon, 11 Aug 2008 15:38:57 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [220.233.188.227]) by mx1.freebsd.org (Postfix) with ESMTP id 41AE68FC21 for ; Mon, 11 Aug 2008 15:38:56 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (localhost.nimnet.asn.au [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id m7BF8lGc025300; Tue, 12 Aug 2008 01:08:52 +1000 (EST) (envelope-from smithi@sola.nimnet.asn.au) Received: from localhost (smithi@localhost) by sola.nimnet.asn.au (8.14.2/8.14.2/Submit) with ESMTP id m7BF8k6e025297; Tue, 12 Aug 2008 01:08:46 +1000 (EST) (envelope-from smithi@sola.nimnet.asn.au) Date: Tue, 12 Aug 2008 01:08:46 +1000 (EST) From: Ian Smith To: Onur Aslan In-Reply-To: Message-ID: <20080812001925.I24964@sola.nimnet.asn.au> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-net@freebsd.org Subject: Re: Named Listen IP 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, 11 Aug 2008 15:38:57 -0000 On Mon, 11 Aug 2008, Onur Aslan wrote: > I am using named for a ns server. Named listening all ips for my > machine. But when i reboot machine, my ppp network connecting after > started named. named doesn't listening my ppp network's ip. Do you > have a solution? Assuming you have a fixed IP address when ppp comes up, specify that address in named's listen-on list. When ppp has connected, assigned its addresses and set the default route, have ppp run an up-script that runs '/etc/rc.d/named restart'. named will then see the ppp interface and listen on that address as well as any others specified, like localhost. ppp runs its up/down scripts as root; you don't need (or want) to have named running as root. cheers, Ian From owner-freebsd-net@FreeBSD.ORG Mon Aug 11 17:40:27 2008 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 88D82106567E for ; Mon, 11 Aug 2008 17:40:27 +0000 (UTC) (envelope-from prvs=pschmehl_lists=102d11afb@tx.rr.com) Received: from ip-relay-002.utdallas.edu (ip-relay-002.utdallas.edu [129.110.20.112]) by mx1.freebsd.org (Postfix) with ESMTP id 5874D8FC1D for ; Mon, 11 Aug 2008 17:40:27 +0000 (UTC) (envelope-from prvs=pschmehl_lists=102d11afb@tx.rr.com) X-Group: RELAYLIST X-IronPort-AV: E=Sophos;i="4.31,321,1215406800"; d="scan'208";a="5117720" Received: from smtp3.utdallas.edu ([129.110.20.110]) by ip-relay-002.utdallas.edu with ESMTP; 11 Aug 2008 12:11:48 -0500 Received: from utd65257.utdallas.edu (utd65257.utdallas.edu [129.110.3.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.utdallas.edu (Postfix) with ESMTPSA id 5C40623DF2; Mon, 11 Aug 2008 12:11:48 -0500 (CDT) Date: Mon, 11 Aug 2008 12:11:48 -0500 From: Paul Schmehl To: Ian Smith , Onur Aslan Message-ID: In-Reply-To: <20080812001925.I24964@sola.nimnet.asn.au> References: <20080812001925.I24964@sola.nimnet.asn.au> X-Mailer: Mulberry/4.0.6 (Linux/x86) X-Munged-Reply-To: Figure it out MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: freebsd-net@freebsd.org Subject: Re: Named Listen IP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Aug 2008 17:40:27 -0000 --On Tuesday, August 12, 2008 01:08:46 +1000 Ian Smith wrote: > On Mon, 11 Aug 2008, Onur Aslan wrote: > > I am using named for a ns server. Named listening all ips for my > > machine. But when i reboot machine, my ppp network connecting after > > started named. named doesn't listening my ppp network's ip. Do you > > have a solution? > > Assuming you have a fixed IP address when ppp comes up, specify that > address in named's listen-on list. When ppp has connected, assigned its > addresses and set the default route, have ppp run an up-script that runs > '/etc/rc.d/named restart'. > > named will then see the ppp interface and listen on that address as well > as any others specified, like localhost. ppp runs its up/down scripts > as root; you don't need (or want) to have named running as root. > Just wondering - couldn't this be fixed by adding the keyword "network" to the REQUIRE portion of the /etc/rc.d/named script? (Right now it contains SERVERS and cleanvar. I'm suggesting adding network.) -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. ******************************************* Check the headers before clicking on Reply. From owner-freebsd-net@FreeBSD.ORG Mon Aug 11 20:07:12 2008 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 8A219106567B for ; Mon, 11 Aug 2008 20:07:12 +0000 (UTC) (envelope-from personal@daemoncore.org) Received: from mail.daemoncore.org (mail.daemoncore.org [64.71.161.107]) by mx1.freebsd.org (Postfix) with ESMTP id 6CB388FC14 for ; Mon, 11 Aug 2008 20:07:12 +0000 (UTC) (envelope-from personal@daemoncore.org) Received: from [80.177.203.173] (laptop2.daemoncore.org [80.177.203.173]) (Authenticated sender: personal@daemoncore.org) by mail.daemoncore.org (Postfix) with ESMTPA id 4F5402E038 for ; Mon, 11 Aug 2008 14:52:20 -0500 (CDT) From: Paul G Webster To: freebsd-net@freebsd.org Content-Type: text/plain Organization: DcDj Audio solutions Date: Mon, 11 Aug 2008 20:50:43 +0100 Message-Id: <1218484244.1750.6.camel@laptop2.daemoncore.org> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: RE: NetGear PCMCIA card (GA518) 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, 11 Aug 2008 20:07:12 -0000 Good day all, Im trying to get the PCMCIA 100/1000 nic in topic working, someone has managed it before: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2004-11/0857.html But that patch wont apply cleanly, dmesg reports on card entry (with no patch): re0: port 0xf000-0xf0ff mem 0xfc007000-0xfc0071ff irq 16 at device 0.0 on cardbus0 re0: PHY read failed re0: MII without any phy! device_attach: re0 attach returned 6 Anyone able tend a hand? -- Thank you for your time -- paul g webster From owner-freebsd-net@FreeBSD.ORG Mon Aug 11 22:06:14 2008 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 23A511065682 for ; Mon, 11 Aug 2008 22:06:14 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.freebsd.org (Postfix) with ESMTP id A69D38FC13 for ; Mon, 11 Aug 2008 22:06:13 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 32303 invoked by uid 399); 11 Aug 2008 22:06:13 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 11 Aug 2008 22:06:13 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <48A0B7D3.2090702@FreeBSD.org> Date: Mon, 11 Aug 2008 15:06:11 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.16 (X11/20080726) MIME-Version: 1.0 To: Onur Aslan References: In-Reply-To: X-Enigmail-Version: 0.95.6 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Named Listen IP 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, 11 Aug 2008 22:06:14 -0000 Onur Aslan wrote: > Hi. > > I am using named for a ns server. Named listening all ips for my > machine. But when i reboot machine, my ppp network connecting after > started named. Do you mean that the ppp startup script starts running before the named startup script starts running, but doesn't finish connecting until named starts? If so, then the solution that Ian gave you (to add '/etc/rc.d/named restart' to your ppp script) is the right one. Or do you mean that the named startup script runs first, then the ppp startup script runs after it? This shouldn't happen, but if it's happening to you we need to know why. Follow these steps: mkdir testrc cd testrc cp /etc/rc . fetch http://dougbarton.us/rc-debug.diff patch < rc-debug.diff /bin/sh rc If the two "early" runs are different it will show that, in which case there is an even bigger problem. What usually happens is that they are the same and the second one will be deleted. Paste the results of rc.early1 (and 2 if they are different) and rc.late into your response and we'll take it from there. hope this helps, Doug -- This .signature sanitized for your protection From owner-freebsd-net@FreeBSD.ORG Mon Aug 11 22:34:56 2008 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 C94AB1065670 for ; Mon, 11 Aug 2008 22:34:56 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (host-122-100-2-232.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id 89D158FC08 for ; Mon, 11 Aug 2008 22:34:55 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id 7C0BC173FF; Tue, 12 Aug 2008 08:35:09 +1000 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.1.50.60] (138.21.96.58.exetel.com.au [58.96.21.138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id 75AA51736B for ; Tue, 12 Aug 2008 08:35:05 +1000 (EST) Message-ID: <48A0BE14.6070102@modulus.org> Date: Tue, 12 Aug 2008 08:32:52 +1000 From: Andrew Snow User-Agent: Thunderbird 2.0.0.14 (X11/20080523) MIME-Version: 1.0 To: "freebsd-net >> FreeBSD Net" References: <20080811021703.GC50045@cdnetworks.co.kr> In-Reply-To: <20080811021703.GC50045@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Rx/tx hardware checksumming statistics? 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, 11 Aug 2008 22:34:56 -0000 Are there any NIC hardware counters that FreeBSD could be taking advantage of or displaying? From owner-freebsd-net@FreeBSD.ORG Tue Aug 12 02:01:26 2008 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 46C89106566C for ; Tue, 12 Aug 2008 02:01:26 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.238]) by mx1.freebsd.org (Postfix) with ESMTP id 0E3F58FC16 for ; Tue, 12 Aug 2008 02:01:26 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so3756790rvf.43 for ; Mon, 11 Aug 2008 19:01:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=7W6TL5tPTiWDEDAj0kYdkxYLfuUDag3E6mWeDBssb98=; b=Lu1yG09tKc+fkrzF6oc10BFeCdC0p3omezVxC9/eZKNMF6M7G99bm1Nl+tcRJos4yy E7C3ZrbvwNMM2WurMp/JoPDWW/VGub1KM7VfBvPAQuO61b9yspbyQLKzS+wpFGpzlSio l5lJjKDoupydMX+v83H5eIPYInuF3rK90JUmw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=EKfw4oRq3MWpy2dbBd0PC0PSR4NSfZmkiE7loaNu0N1cok3uoAVhWs6KnkC4UshWQH jx5TxZT29PspUHMuRhuZArRpvNsNb4Pn9l4fKFAOyrCQTwy/zw+2k5zKgtgnYsciiuNa PMG9NBKBmr5S+0BpWXY0Yk6n4me78rNvVPtsU= Received: by 10.141.29.18 with SMTP id g18mr3960944rvj.298.1218506485782; Mon, 11 Aug 2008 19:01:25 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id l31sm10019898rvb.6.2008.08.11.19.01.15 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 11 Aug 2008 19:01:17 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m7C1x6QP054843 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Aug 2008 10:59:06 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m7C1x5bQ054842; Tue, 12 Aug 2008 10:59:05 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 12 Aug 2008 10:59:05 +0900 From: Pyun YongHyeon To: Paul G Webster Message-ID: <20080812015905.GC54362@cdnetworks.co.kr> References: <1218484244.1750.6.camel@laptop2.daemoncore.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1218484244.1750.6.camel@laptop2.daemoncore.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org Subject: Re: NetGear PCMCIA card (GA518) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Aug 2008 02:01:26 -0000 On Mon, Aug 11, 2008 at 08:50:43PM +0100, Paul G Webster wrote: > Good day all, > > Im trying to get the PCMCIA 100/1000 nic in topic working, someone has > managed it before: > > http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2004-11/0857.html > > But that patch wont apply cleanly, dmesg reports on card entry (with no > patch): > > re0: port > 0xf000-0xf0ff mem 0xfc007000-0xfc0071ff irq 16 at device 0.0 on cardbus0 > re0: PHY read failed > re0: MII without any phy! > device_attach: re0 attach returned 6 > > Anyone able tend a hand? > It seems that the controller is recognized by re(4) but initialization was not successful. Since your controller is not second generation of RealTek 8168/8111 I think the issue could be related with cardbus driver. imp@ may have more idea what's happening here. > -- Thank you for your time > -- paul g webster -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Tue Aug 12 02:31:08 2008 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 6915F1065673 for ; Tue, 12 Aug 2008 02:31:08 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.234]) by mx1.freebsd.org (Postfix) with ESMTP id 2EAEF8FC18 for ; Tue, 12 Aug 2008 02:31:08 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so3774831rvf.43 for ; Mon, 11 Aug 2008 19:31:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=LdLiSDzGdZEYl+Gh1ZxtlS4teOTlDio+yH1hHRp96Pg=; b=Q5ywBDbFR8Pgl9lqjpm/zhG77vGeWsZdrcfW/RehSPq3aPsjd6M9BKfOYJnOPwjsku Q3b3mSlXMLVSwg41ZNPX165uvvTZ0LXRUso7e8W7AiWFskDw1ugSvGEYKx7l2HHeqMhw opUjmswfK6Wk5e9YsscIyQBJo/kXMr0TYyDmY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=kaqcaqLri9tiPFdrwv8lktrwrCEIDSSlYdRmJAZ53OA9gaqUUBgWJqjtYuCmn5K19m 4bGGieWcg/PdF4ssgU1aDRuxFvG+DzZcQb9ddaKE9KL52y1cxyizP5hxO8Wky+CjLkOj xO5LUUFCtotPFOUchwgI8/58p3XvAF96ZPAXI= Received: by 10.141.15.19 with SMTP id s19mr3990213rvi.205.1218508267917; Mon, 11 Aug 2008 19:31:07 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id b8sm10042997rvf.8.2008.08.11.19.31.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 11 Aug 2008 19:31:06 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m7C2StKN054925 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Aug 2008 11:28:55 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m7C2SroL054924; Tue, 12 Aug 2008 11:28:53 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 12 Aug 2008 11:28:53 +0900 From: Pyun YongHyeon To: Christian Weisgerber Message-ID: <20080812022853.GD54362@cdnetworks.co.kr> References: <20080811021703.GC50045@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org Subject: Re: Rx/tx hardware checksumming statistics? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Aug 2008 02:31:08 -0000 On Mon, Aug 11, 2008 at 12:22:33PM +0000, Christian Weisgerber wrote: > Pyun YongHyeon wrote: > > > I don't think it indicates whether checksum offloading actually > > works as OpenBSD blindly set a flag, which was derived from > > hardware, to indicate hardware performed the checksum computation. > > Yes. It counts the instances where the network stack assumes that > the hardware successfully verified the checksum. That is an > interesting number. > > OpenBSD's re(4) driver is ported from FreeBSD. Recently, Brad Smith > has been merging the tx/rx checksum offload support for the newer > chips (RTL8111C etc.) into the OpenBSD driver and I have done some > testing for him. Looking at the counters, I have noticed: > * IP header rx checksumming is only registered for IP/TCP and IP/UDP > packets, but not for other protocols, such as IP/ICMP. Note, the controller can only offload IP, TCP and UDP checksumming. ICMP should be handled by software. > * If VLAN tagging is enabled, no rx checksumming is registered at > all. > > I don't have documentation for the Realtek chips, so I don't know > if the hardware really cannot perform these operations or if the > driver simply fails to take advantage of them. Presumably the same AFAIK all RealTek gigabit controllers can do TSO, checksum offload, and VLAN tag insertion/stripping. Of course there are known hardware bugs for these hardware assistance but it's different question, I think. > limitations also apply to the FreeBSD driver, but without the No, FreeBSD have no such limitation, re(4) takes full advantage of hardware assistance if the controller in question is known to work with the feature. > counters, how can you tell? > I think you can check the output of ifconfig(4). Unlike OpenBSD, you can see 'options' part of output which indicates current active hardware features such as checksum offload, WOL, TSO etc. I have no strong opinions on adding these counters but I guess there are too many hardware assisted counters if we take the route, for example, re(4) can do the following with hardware assistance and each hardware assistance will require separate counters. - TSO(TCP segmentation offload) - VLAN tag insertion - VLAN tag stripping - Tx/Rx IP/TCP/UDP checksum offload > -- > Christian "naddy" Weisgerber naddy@mips.inka.de -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Tue Aug 12 02:41:43 2008 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 EB3711065679 for ; Tue, 12 Aug 2008 02:41:43 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.234]) by mx1.freebsd.org (Postfix) with ESMTP id B0ACF8FC13 for ; Tue, 12 Aug 2008 02:41:43 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so3780538rvf.43 for ; Mon, 11 Aug 2008 19:41:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=cLTDnikmhL6gnovjFvcrMRj82JBAgRZRgoG+CtOrlj8=; b=R8AiV2hDXyxAdMq1X3bak6Ojm1q8PxeX25WLmpcKPNx/t9gPiUoJ9LEECL8/uEEvyA uIMFHFQWroeMMBwrTl0nr0HRDvBKZg7pYp0DTKZmrnK3Vzh9p48qprh4gpQzhHUXhVep hYPv6WsqQ+JcspHMy7GqWzqlpXDvPbBJx3W0o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=tffN/cTIVYWt447/pzIsmlEO76VS9+ZEoTy3yfNknmmdj3mr8axxmHhxcLH9Qb7Ap2 LALAZC4urGbJzOIU4IJXMkMd9dnGE/NNbM5FyHR8dOXqki5C2x8eWnnhFewCSrRckm/y kr+U5/8jkjVYP4fBGk3p56E5ADgTbCNxttO+Y= Received: by 10.140.207.2 with SMTP id e2mr3994985rvg.187.1218508903496; Mon, 11 Aug 2008 19:41:43 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id b8sm6491134rvf.8.2008.08.11.19.41.41 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 11 Aug 2008 19:41:42 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m7C2dW8c054968 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Aug 2008 11:39:32 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m7C2dScK054967; Tue, 12 Aug 2008 11:39:28 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 12 Aug 2008 11:39:28 +0900 From: Pyun YongHyeon To: Andrew Snow Message-ID: <20080812023928.GE54362@cdnetworks.co.kr> References: <20080811021703.GC50045@cdnetworks.co.kr> <48A0BE14.6070102@modulus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48A0BE14.6070102@modulus.org> User-Agent: Mutt/1.4.2.1i Cc: "freebsd-net >> FreeBSD Net" Subject: Re: Rx/tx hardware checksumming statistics? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Aug 2008 02:41:44 -0000 On Tue, Aug 12, 2008 at 08:32:52AM +1000, Andrew Snow wrote: > > Are there any NIC hardware counters that FreeBSD could be taking > advantage of or displaying? > It depends on device driver. Some drivers access hardware counters maintained by MAC and can display these counters with sysctl(8). In addition these counters are used to update statistics counters in ifnet which can be checked with netstat(1). For example, em(4), age(4), sf(4), bge(4), bce(4) provide sysctl interface. -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Tue Aug 12 06:49:17 2008 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 540C0106564A; Tue, 12 Aug 2008 06:49:17 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 284898FC0A; Tue, 12 Aug 2008 06:49:17 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (remko@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m7C6nHLt064138; Tue, 12 Aug 2008 06:49:17 GMT (envelope-from remko@freefall.freebsd.org) Received: (from remko@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m7C6nHv9064134; Tue, 12 Aug 2008 06:49:17 GMT (envelope-from remko) Date: Tue, 12 Aug 2008 06:49:17 GMT Message-Id: <200808120649.m7C6nHv9064134@freefall.freebsd.org> To: remko@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: remko@FreeBSD.org Cc: Subject: Re: kern/126469: [fxp] [panic] fxp(4) related kernel panic 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, 12 Aug 2008 06:49:17 -0000 Synopsis: [fxp] [panic] fxp(4) related kernel panic Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: remko Responsible-Changed-When: Tue Aug 12 06:49:16 UTC 2008 Responsible-Changed-Why: Over to maintainer. http://www.freebsd.org/cgi/query-pr.cgi?pr=126469 From owner-freebsd-net@FreeBSD.ORG Tue Aug 12 09:55:31 2008 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 572401065676; Tue, 12 Aug 2008 09:55:31 +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 2EF708FC1A; Tue, 12 Aug 2008 09:55:31 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m7C9tVJM004888; Tue, 12 Aug 2008 09:55:31 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m7C9tVBN004884; Tue, 12 Aug 2008 09:55:31 GMT (envelope-from linimon) Date: Tue, 12 Aug 2008 09:55:31 GMT Message-Id: <200808120955.m7C9tVBN004884@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/126475: [ath] [panic] ath pcmcia card inevitably panics under FreeBSD-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: Tue, 12 Aug 2008 09:55:31 -0000 Synopsis: [ath] [panic] ath pcmcia card inevitably panics under FreeBSD-7 STABLE Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Tue Aug 12 09:55:18 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=126475 From owner-freebsd-net@FreeBSD.ORG Tue Aug 12 15:32:14 2008 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 4886D1065676 for ; Tue, 12 Aug 2008 15:32:14 +0000 (UTC) (envelope-from mutex@secure-it.ca) Received: from secure-it.ca (cl-12.chi-02.us.sixxs.net [IPv6:2001:4978:f:b::2]) by mx1.freebsd.org (Postfix) with ESMTP id 2286C8FC0C for ; Tue, 12 Aug 2008 15:32:14 +0000 (UTC) (envelope-from mutex@secure-it.ca) Received: from localhost (unknown [127.0.0.1]) by secure-it.ca (Postfix) with ESMTP id 8340E1A9832 for ; Tue, 12 Aug 2008 11:32:25 -0400 (EDT) X-Virus-Scanned: amavisd-new at secure-it.ca Received: from secure-it.ca ([127.0.0.1]) by localhost (secure-it.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7xhKSeEmq8re for ; Tue, 12 Aug 2008 11:31:45 -0400 (EDT) Received: from webmail.unixtech.info (localhost [IPv6:::1]) by secure-it.ca (Postfix) with ESMTP id CB5601A9830 for ; Tue, 12 Aug 2008 11:31:44 -0400 (EDT) Received: from 70.80.73.214 (SquirrelMail authenticated user mutex) by webmail.unixtech.info with HTTP; Tue, 12 Aug 2008 11:31:45 -0400 (EDT) Message-ID: <55144.70.80.73.214.1218555105.squirrel@webmail.unixtech.info> In-Reply-To: <48A0B7D3.2090702@FreeBSD.org> References: <48A0B7D3.2090702@FreeBSD.org> Date: Tue, 12 Aug 2008 11:31:45 -0400 (EDT) From: mutex@secure-it.ca To: freebsd-net@freebsd.org User-Agent: SquirrelMail/1.4.13 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: Named Listen IP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mutex@secure-it.ca List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Aug 2008 15:32:14 -0000 Hello, to me, I found that the easiest solution was to use ppp startup script instead of /etc/rc.conf. You should take a look at /etc/ppp/ppp.linkup and /etc/ppp/ip-up files depending on your setup. -- Public --> 4096R/1DA0F13F 2008-06-26 [expires: 2013-06-25] Key fingerprint -- > 2287 2F1F FE62 3975 F181 DDA6 B65F 3B1C 1DA0 F13F uid MuteX mutex@secure-it.ca (secure-it.ca) From owner-freebsd-net@FreeBSD.ORG Tue Aug 12 15:33:18 2008 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 9191E106567E for ; Tue, 12 Aug 2008 15:33:18 +0000 (UTC) (envelope-from mailnull@mips.inka.de) Received: from mail-in-09.arcor-online.net (mail-in-09.arcor-online.net [151.189.21.49]) by mx1.freebsd.org (Postfix) with ESMTP id 288C68FC23 for ; Tue, 12 Aug 2008 15:33:18 +0000 (UTC) (envelope-from mailnull@mips.inka.de) Received: from mail-in-20-z2.arcor-online.net (mail-in-20-z2.arcor-online.net [151.189.8.85]) by mail-in-09.arcor-online.net (Postfix) with ESMTP id 4773F302894 for ; Tue, 12 Aug 2008 17:33:16 +0200 (CEST) Received: from mail-in-08.arcor-online.net (mail-in-08.arcor-online.net [151.189.21.48]) by mail-in-20-z2.arcor-online.net (Postfix) with ESMTP id 399E41077FD for ; Tue, 12 Aug 2008 17:33:16 +0200 (CEST) Received: from lorvorc.mips.inka.de (dslb-088-067-127-145.pools.arcor-ip.net [88.67.127.145]) by mail-in-08.arcor-online.net (Postfix) with ESMTP id F069E2BB6EB for ; Tue, 12 Aug 2008 17:33:15 +0200 (CEST) Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.14.2/8.14.2) with ESMTP id m7CFXEHn073373 for ; Tue, 12 Aug 2008 17:33:14 +0200 (CEST) (envelope-from mailnull@lorvorc.mips.inka.de) Received: (from mailnull@localhost) by lorvorc.mips.inka.de (8.14.2/8.14.2/Submit) id m7CFXEaH073372 for freebsd-net@freebsd.org; Tue, 12 Aug 2008 17:33:14 +0200 (CEST) (envelope-from mailnull) From: naddy@mips.inka.de (Christian Weisgerber) Date: Tue, 12 Aug 2008 15:33:14 +0000 (UTC) Message-ID: References: <20080811021703.GC50045@cdnetworks.co.kr> <20080812022853.GD54362@cdnetworks.co.kr> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-net@freebsd.org X-Virus-Scanned: ClamAV 0.93.3/8018/Tue Aug 12 10:36:31 2008 on mail-in-08.arcor-online.net X-Virus-Status: Clean Subject: Re: Rx/tx hardware checksumming statistics? 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, 12 Aug 2008 15:33:18 -0000 Pyun YongHyeon wrote: > > OpenBSD's re(4) driver is ported from FreeBSD. Recently, Brad Smith > > has been merging the tx/rx checksum offload support for the newer > > chips (RTL8111C etc.) into the OpenBSD driver and I have done some > > testing for him. Looking at the counters, I have noticed: > > * IP header rx checksumming is only registered for IP/TCP and IP/UDP > > packets, but not for other protocols, such as IP/ICMP. > > Note, the controller can only offload IP, TCP and UDP checksumming. > ICMP should be handled by software. Yes, but the IP/ICMP packet should still be subject to IP checksumming. What I see with an 8111C (RL_FLAG_DESCV2): * incoming IP/TCP packet => IP checksum processed in hardware => TCP checksum processed in hardware * incoming IP/UDP packet => IP checksum processed in hardware => UDP checksum processed in hardware * incoming IP/ICMP packet => IP checksum _not_ processed in hardware With an old 8169S the latter case is different: * incoming IP/ICMP packet => IP checksum processed in hardware > > limitations also apply to the FreeBSD driver, but without the > > No, FreeBSD have no such limitation, re(4) takes full advantage of > hardware assistance if the controller in question is known to work > with the feature. I cannot find any difference between the respective drivers suggesting that the behavior above would be any different on FreeBSD. There are no relevant differences in the RX checksumming section in re_rxeof(). > > counters, how can you tell? > > I think you can check the output of ifconfig(4). This does not tell you if an individual received packet has been marked CSUM_IP_CHECKED|CSUM_IP_VALID. -- Christian "naddy" Weisgerber naddy@mips.inka.de From owner-freebsd-net@FreeBSD.ORG Tue Aug 12 22:18:40 2008 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 03579106566B for ; Tue, 12 Aug 2008 22:18:40 +0000 (UTC) (envelope-from mailnull@mips.inka.de) Received: from mail-in-01.arcor-online.net (mail-in-01.arcor-online.net [151.189.21.41]) by mx1.freebsd.org (Postfix) with ESMTP id B04FC8FC08 for ; Tue, 12 Aug 2008 22:18:39 +0000 (UTC) (envelope-from mailnull@mips.inka.de) Received: from mail-in-11-z2.arcor-online.net (mail-in-11-z2.arcor-online.net [151.189.8.28]) by mail-in-01.arcor-online.net (Postfix) with ESMTP id D011C104FB3 for ; Wed, 13 Aug 2008 00:18:37 +0200 (CEST) Received: from mail-in-09.arcor-online.net (mail-in-09.arcor-online.net [151.189.21.49]) by mail-in-11-z2.arcor-online.net (Postfix) with ESMTP id BA0CF3465A8 for ; Wed, 13 Aug 2008 00:18:37 +0200 (CEST) Received: from lorvorc.mips.inka.de (dslb-088-067-127-145.pools.arcor-ip.net [88.67.127.145]) by mail-in-09.arcor-online.net (Postfix) with ESMTP id 90C623BE22 for ; Wed, 13 Aug 2008 00:18:37 +0200 (CEST) Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.14.2/8.14.2) with ESMTP id m7CMIa5J094510 for ; Wed, 13 Aug 2008 00:18:36 +0200 (CEST) (envelope-from mailnull@lorvorc.mips.inka.de) Received: (from mailnull@localhost) by lorvorc.mips.inka.de (8.14.2/8.14.2/Submit) id m7CMIaW7094509 for freebsd-net@freebsd.org; Wed, 13 Aug 2008 00:18:36 +0200 (CEST) (envelope-from mailnull) From: naddy@mips.inka.de (Christian Weisgerber) Date: Tue, 12 Aug 2008 22:18:36 +0000 (UTC) Message-ID: References: <20080811021703.GC50045@cdnetworks.co.kr> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-net@freebsd.org X-Virus-Scanned: ClamAV 0.93.3/8021/Tue Aug 12 21:27:39 2008 on mail-in-09.arcor-online.net X-Virus-Status: Clean Subject: Re: Rx/tx hardware checksumming statistics? 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, 12 Aug 2008 22:18:40 -0000 Christian Weisgerber wrote: > OpenBSD's re(4) driver is ported from FreeBSD. [...] > * If VLAN tagging is enabled, no rx checksumming is registered at > all. For the record, this is in fact due to a difference in the OpenBSD driver, i.e., it does not apply to FreeBSD. OpenBSD does not enable VLAN tag stripping in hardware. Without this, the chip apparently does not perform any rx checksumming on tagged frames. -- Christian "naddy" Weisgerber naddy@mips.inka.de From owner-freebsd-net@FreeBSD.ORG Wed Aug 13 01:11:57 2008 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 336B51065680 for ; Wed, 13 Aug 2008 01:11:57 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.236]) by mx1.freebsd.org (Postfix) with ESMTP id 8A9108FC12 for ; Wed, 13 Aug 2008 01:11:56 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so4562352rvf.43 for ; Tue, 12 Aug 2008 18:11:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=83Q7Xq5x5QfIg8UMBdir9OqJ6URpEoyVrXOoCl1dgl0=; b=U3m1TYjUzfKNNpBAoLmfR1QKxQGllrLwwz0h+FkLncXMYlOtr4hpOfu0tKlxvOxzW0 ND2bVaPmRyjKjMyQqzK6X1M5Nn0VwjZ3UbebXtoeBh9xsac6s8UVYdw02IjfkvZvBn0T q+Vv4Con+zE4OZ8w1Y2A6Ej3ddeBqgIO3tl1c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=fi5BQO7CA6/59qk3vtoogl/cqzrgA+HQchCHicWnkDzHEWNO1CWtNi+BHbRHOAqxQk M+PaVmLXB3Id3d/gI8gCmzxlKE3u950mA+9ZtpBY4l50Yi0tUvm8IbU2EaDfT3RCPjja P5FShljmonH12a5k/0MGxiD2CYpntqPtMuJag= Received: by 10.141.172.7 with SMTP id z7mr4837391rvo.15.1218589916306; Tue, 12 Aug 2008 18:11:56 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id k2sm12333006rvb.4.2008.08.12.18.11.54 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 12 Aug 2008 18:11:55 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m7D19jhg058907 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 Aug 2008 10:09:45 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m7D19i8b058906; Wed, 13 Aug 2008 10:09:44 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 13 Aug 2008 10:09:44 +0900 From: Pyun YongHyeon To: Christian Weisgerber Message-ID: <20080813010944.GB58659@cdnetworks.co.kr> References: <20080811021703.GC50045@cdnetworks.co.kr> <20080812022853.GD54362@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org Subject: Re: Rx/tx hardware checksumming statistics? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Aug 2008 01:11:57 -0000 On Tue, Aug 12, 2008 at 03:33:14PM +0000, Christian Weisgerber wrote: > Pyun YongHyeon wrote: > > > > OpenBSD's re(4) driver is ported from FreeBSD. Recently, Brad Smith > > > has been merging the tx/rx checksum offload support for the newer > > > chips (RTL8111C etc.) into the OpenBSD driver and I have done some > > > testing for him. Looking at the counters, I have noticed: > > > * IP header rx checksumming is only registered for IP/TCP and IP/UDP > > > packets, but not for other protocols, such as IP/ICMP. > > > > Note, the controller can only offload IP, TCP and UDP checksumming. > > ICMP should be handled by software. > > Yes, but the IP/ICMP packet should still be subject to IP checksumming. > > What I see with an 8111C (RL_FLAG_DESCV2): > * incoming IP/TCP packet > => IP checksum processed in hardware > => TCP checksum processed in hardware > * incoming IP/UDP packet > => IP checksum processed in hardware > => UDP checksum processed in hardware > * incoming IP/ICMP packet > => IP checksum _not_ processed in hardware > > With an old 8169S the latter case is different: > * incoming IP/ICMP packet > => IP checksum processed in hardware > > > > limitations also apply to the FreeBSD driver, but without the > > > > No, FreeBSD have no such limitation, re(4) takes full advantage of > > hardware assistance if the controller in question is known to work > > with the feature. > > I cannot find any difference between the respective drivers suggesting > that the behavior above would be any different on FreeBSD. There > are no relevant differences in the RX checksumming section in > re_rxeof(). > Aha I see. The second generation of RTL8168/8111/810x controllers use new descriptor format. I don't know why RealTek dropped supporting IP/ICMP checksumming and I couldn't verify that as I have no such hardware. However it seems RealTek added IPv6 checksum offload support for these controllers so the checksum offload oddity for IP/ICMP could be a bug introduced in this newer descriptor format. > > > counters, how can you tell? > > > > I think you can check the output of ifconfig(4). > > This does not tell you if an individual received packet has been > marked CSUM_IP_CHECKED|CSUM_IP_VALID. > That's correct. -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Wed Aug 13 04:52:19 2008 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 27987106564A for ; Wed, 13 Aug 2008 04:52:19 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [220.233.188.227]) by mx1.freebsd.org (Postfix) with ESMTP id 421ED8FC17 for ; Wed, 13 Aug 2008 04:52:17 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (localhost.nimnet.asn.au [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id m7D4qA26073599; Wed, 13 Aug 2008 14:52:16 +1000 (EST) (envelope-from smithi@sola.nimnet.asn.au) Received: from localhost (smithi@localhost) by sola.nimnet.asn.au (8.14.2/8.14.2/Submit) with ESMTP id m7D4qArq073596; Wed, 13 Aug 2008 14:52:10 +1000 (EST) (envelope-from smithi@sola.nimnet.asn.au) Date: Wed, 13 Aug 2008 14:52:10 +1000 (EST) From: Ian Smith To: freebsd-net@freebsd.org In-Reply-To: Message-ID: <20080813031552.R37370@sola.nimnet.asn.au> References: <20080812001925.I24964@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Onur Aslan Subject: Re: Named Listen IP 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, 13 Aug 2008 04:52:19 -0000 On Mon, 11 Aug 2008, Paul Schmehl wrote: > --On Tuesday, August 12, 2008 01:08:46 +1000 Ian Smith > wrote: > > > On Mon, 11 Aug 2008, Onur Aslan wrote: > > > I am using named for a ns server. Named listening all ips for my > > > machine. But when i reboot machine, my ppp network connecting after > > > started named. named doesn't listening my ppp network's ip. Do you > > > have a solution? > > > > Assuming you have a fixed IP address when ppp comes up, specify that > > address in named's listen-on list. When ppp has connected, assigned its > > addresses and set the default route, have ppp run an up-script that runs > > '/etc/rc.d/named restart'. > > > > named will then see the ppp interface and listen on that address as well > > as any others specified, like localhost. ppp runs its up/down scripts > > as root; you don't need (or want) to have named running as root. > > > > Just wondering - couldn't this be fixed by adding the keyword "network" to > the REQUIRE portion of the /etc/rc.d/named script? (Right now it contains > SERVERS and cleanvar. I'm suggesting adding network.) rcorder (for 5.5 and 7.0 anyway) has ppp starting before named alright. However ppp is exec'd and begins connecting but is not waited for - as a rule fortunately, as even ADSL can take a while, and dialup takes a good long while - before proceeding with the boot, including named. I suppose /etc/rc.d/ppp maybe could be hacked to wait around, up to some timeout anyway, or /etc/rc.d/named could be taught to timed-wait on some indication for such specific cases, but some rcorder dependencies seem hardly resolvable in the 'general case' .. I had the same issue with mpd on ADSL recently after a rare reboot; still pondering a tidy solution. cheers, Ian (Paul, sorry but your reply-to clues in the headers only confused me) From owner-freebsd-net@FreeBSD.ORG Wed Aug 13 06:29:00 2008 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 49A321065670 for ; Wed, 13 Aug 2008 06:29:00 +0000 (UTC) (envelope-from brutal_hitman_@hotmail.com) Received: from blu0-omc2-s4.blu0.hotmail.com (blu0-omc2-s4.blu0.hotmail.com [65.55.111.79]) by mx1.freebsd.org (Postfix) with ESMTP id 04A538FC16 for ; Wed, 13 Aug 2008 06:28:59 +0000 (UTC) (envelope-from brutal_hitman_@hotmail.com) Received: from BLU131-W34 ([65.55.111.72]) by blu0-omc2-s4.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 12 Aug 2008 23:16:59 -0700 Message-ID: X-Originating-IP: [74.141.28.245] From: Ben Wittgen To: Date: Wed, 13 Aug 2008 06:16:58 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 13 Aug 2008 06:16:59.0411 (UTC) FILETIME=[31A0B630:01C8FD0C] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: (no subject) 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, 13 Aug 2008 06:29:00 -0000 Hey=2C I'm new here and an overall FreeBSD newbie. I use pfSense for routi= ng=2Cwww.pfsense.org=2C which uses FreeBSD. I got onto my computer this mo= rning to find my internet had been dropped=2C no wan or LAN or webGUI=2C ro= uter was still on=2C so i turned on the monitor that was plugged into the r= outer there were messages being spammed and i could no longer type anything= =2C it completely locked up. it was spamming this:em0: discard frame w/o p= acket headerem0: discard frame w/o packet headerem0: discard frame w/o pack= et headerem0: discard frame w/o packet headerre0: discard frame w/o packet = headerem0: discard frame w/o packet headerand it was randomly interchanging= re0 and em0.im using pfsense 1.2.1-RC1 built on Mon Aug 4 22:05:47 EDT 200= 8=2C and the OS version is FreeBSD 7.0. =20 I get this error after about 4-5 days and my wireless goes under heavy load= . let me know any more information i need to provide and how to obtain it = if it requires logs and i'll be glad to. thanks. _________________________________________________________________ Your PC=2C mobile phone=2C and online services work together like never bef= ore. http://clk.atdmt.com/MRT/go/108587394/direct/01/= From owner-freebsd-net@FreeBSD.ORG Wed Aug 13 06:34:43 2008 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 3C9241065671 for ; Wed, 13 Aug 2008 06:34:43 +0000 (UTC) (envelope-from viper@perm.raid.ru) Received: from smtp.ertelecom.ru (smtp.ertelecom.ru [212.33.232.210]) by mx1.freebsd.org (Postfix) with ESMTP id D7BD78FC1D for ; Wed, 13 Aug 2008 06:34:42 +0000 (UTC) (envelope-from viper@perm.raid.ru) Received: from mail.raid.ru ([212.33.232.8]:6426) by smtp.ertelecom.ru with esmtp (Exim) id 1KT9wO-000H3A-Vx for ; Wed, 13 Aug 2008 12:34:41 +0600 Received: from 212.33.232.121 (SquirrelMail authenticated user viper) by mail.raid.ru with HTTP; Wed, 13 Aug 2008 12:34:40 +0600 (YEKST) Message-ID: <48912.212.33.232.121.1218609280.squirrel@mail.raid.ru> In-Reply-To: <17499.212.33.232.121.1217925622.squirrel@mail.raid.ru> References: <17499.212.33.232.121.1217925622.squirrel@mail.raid.ru> Date: Wed, 13 Aug 2008 12:34:40 +0600 (YEKST) From: "Vladimir Korkodinov" To: freebsd-net@freebsd.org User-Agent: SquirrelMail/1.4.8 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: arp - strange things X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: viper@perm.raid.ru List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Aug 2008 06:34:43 -0000 >From today FreeBSD 7.0-STABLE #7: Wed Aug 13 11:30:49 YEKST 2008 How fix problem? Any suggestion? ? (10.100.8.118) at (incomplete) on bce1 [ethernet] ? (10.100.10.190) at 00:1a:4b:dd:84:a0 on bce1 [ethernet] ? (10.100.10.190) at (incomplete) on bce1 [ethernet] ? (10.100.10.190) at (incomplete) on bce1 [ethernet] ? (10.100.10.190) at (incomplete) on bce1 [ethernet] ? (10.100.10.190) at (incomplete) on bce1 [ethernet] ? (10.100.10.190) at (incomplete) on bce1 [ethernet] ? (10.100.10.190) at (incomplete) on bce1 [ethernet] arp -ad 10.100.8.118 (10.100.8.118) deleted delete: cannot locate 10.100.8.118 10.100.10.40 (10.100.10.40) deleted 10.100.10.190 (10.100.10.190) deleted delete: cannot locate 10.100.10.190 delete: cannot locate 10.100.10.190 delete: cannot locate 10.100.10.190 delete: cannot locate 10.100.10.190 delete: cannot locate 10.100.10.190 delete: cannot locate 10.100.10.190 delete: cannot locate 10.100.10.190 delete: cannot locate 10.100.10.190 delete: cannot locate 10.100.10.190 delete: cannot locate 10.100.10.190 delete: cannot locate 10.100.10.190 uptime 12:33PM up 45 mins arp -an | grep incom | wc -l 245 > I csup my server from Jul 14 to today sources and saw strange issue > with arp table. > Long description see below. > > Do you have the same "issue" on your own servers? > > Partial reverting > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/if_ether.c > Revision 1.162.2.2 seems fix problem. > > +#if 0 /* -current */ /* Only call this once */ > if (firstpass) { > sin.sin_addr.s_addr = isaddr.s_addr; > EVENTHANDLER_INVOKE(route_arp_update_event, rt, > ar_sha(ah), (struct sockaddr *)&sin); > } > +#endif > > Long description: > > Environment: > uname -a > FreeBSD monitor 7.0-STABLE FreeBSD 7.0-STABLE #5: Tue Aug 5 > 13:15:24 YEKST 2008 root@monitor:/usr/obj/usr/src/sys/kernel > amd64 > > Description: > arp -an > ? (10.100.8.118) at 00:1c:c4:3d:f0:b8 on bce1 [ethernet] > ? (10.100.8.118) at (incomplete) on bce1 [ethernet] > ............. > ? (10.100.10.190) at 00:1a:4b:dd:84:a0 on bce1 [ethernet] > ? (10.100.10.190) at (incomplete) on bce1 [ethernet] > ? (10.100.10.190) at (incomplete) on bce1 [ethernet] > ? (10.100.10.190) at (incomplete) on bce1 [ethernet] > ? (10.100.10.190) at (incomplete) on bce1 [ethernet] > ................ > ? (212.xxx.xxx.xxx) at 00:1e:0b:91:15:08 on bce0 permanent > [ethernet] > ? (212.xxx.xxx.xxx) at 00:1e:0b:91:15:08 on bce0 permanent > [ethernet] > ? (212.xxx.xxx.xxx) at 00:1e:0b:91:15:08 on bce0 permanent > [ethernet] > > > route monitor > > got message of size 296 on Tue Aug 5 14:08:23 2008 > RTM_ADD: Add Route: len 296, pid: 0, seq 0, errno 0, > flags: > locks: inits: > sockaddrs: > 10.100.10.190 bce1:0.1e.b.91.15.6 10.100.200.120 > > got message of size 296 on Tue Aug 5 14:09:11 2008 > RTM_ADD: Add Route: len 296, pid: 0, seq 0, errno 0, > flags: > locks: inits: > sockaddrs: > 10.100.10.190 bce1:0.1e.b.91.15.6 10.100.200.120 > > got message of size 296 on Tue Aug 5 14:09:12 2008 > RTM_ADD: Add Route: len 296, pid: 0, seq 0, errno 0, > flags: > locks: inits: > sockaddrs: > 10.100.10.190 bce1:0.1e.b.91.15.6 10.100.200.120 > > got message of size 296 on Tue Aug 5 14:09:12 2008 > RTM_ADD: Add Route: len 296, pid: 0, seq 0, errno 0, > flags: > locks: inits: > sockaddrs: > 10.100.10.190 bce1:0.1e.b.91.15.6 10.100.200.120 > > got message of size 296 on Tue Aug 5 14:09:17 2008 > RTM_ADD: Add Route: len 296, pid: 0, seq 0, errno 0, > flags: > locks: inits: > sockaddrs: > 10.100.10.190 bce1:0.1e.b.91.15.6 10.100.200.120 > > got message of size 296 on Tue Aug 5 14:09:17 2008 > RTM_ADD: Add Route: len 296, pid: 0, seq 0, errno 0, > flags: > locks: inits: > sockaddrs: > 10.100.10.190 bce1:0.1e.b.91.15.6 10.100.200.120 > > -- > Best regards > Vladimir Korkodinov > -- Best regards Vladimir Korkodinov From owner-freebsd-net@FreeBSD.ORG Wed Aug 13 15:20:36 2008 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 01C741065671 for ; Wed, 13 Aug 2008 15:20:36 +0000 (UTC) (envelope-from damien.deville@netasq.com) Received: from netasq.netasq.com (netasq.netasq.com [213.30.137.178]) by mx1.freebsd.org (Postfix) with ESMTP id C42298FC12 for ; Wed, 13 Aug 2008 15:20:35 +0000 (UTC) (envelope-from damien.deville@netasq.com) Received: from barbar.netasq.com (unknown [10.0.0.126]) by netasq.netasq.com (Postfix) with ESMTP id 0F673435E1 for ; Wed, 13 Aug 2008 17:20:34 +0200 (CEST) Message-ID: <48A2FBBD.1000503@netasq.com> Date: Wed, 13 Aug 2008 17:20:29 +0200 From: Damien Deville User-Agent: Thunderbird 2.0.0.16 (X11/20080730) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: RELENG_7 crash in if_vlan X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: damien.deville@netasq.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Aug 2008 15:20:36 -0000 Hi, On today's checkout of RELENG_7 it is possible to crash the system using the following commands: ifconfig vlan0 create ifconfig vlan0 -vlandev Crash is located in if_vlan.c in vlan_unconfig_locked() when dereferencing a NULL pointer (ifv->ifv_trunk) to access parent interface using PARENT macro. Damien -- Damien Deville R&D engineer damien.deville@netasq.com http://www.netasq.com NETASQ - We secure IT From owner-freebsd-net@FreeBSD.ORG Wed Aug 13 22:31:43 2008 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 449B51065670 for ; Wed, 13 Aug 2008 22:31:43 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.229]) by mx1.freebsd.org (Postfix) with ESMTP id 057E98FC21 for ; Wed, 13 Aug 2008 22:31:42 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wr-out-0506.google.com with SMTP id c8so95212wra.27 for ; Wed, 13 Aug 2008 15:31:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=UfbT4E1kXNaIWvtZ/3IR4pL4S7DGEbFx7umg9OuPxQE=; b=XNztHBR8EoL6WJ1FOHE9MmJ2N8XQQ9a66vzck2ao/vFuZJFr85bEG3FKT68nw9F7go 00p/gMHOLMDz5jrlmhnMD5ev0sceRPRXu30LDUTYOAb/9Mp4RGdXSi1htpFGQGFsQyXm y5oNp+H9vNqf7krVhYJxcWQIc0e113dowEaVc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=fH+CYDfri140wMYlsKFN9EaGUuPoXcFtcaIbqqOa3+bBY4E/GkQ/VrXOm4ZukmJMKt DrS8kbunmq42Whjn0b2X2vDbK2L1lBEE//YO6me88kLZFPth5IhrJToAn8v5QzNwXRnv I4jOUABBP01i11Po3WmqJcPzz2AxV8ZlzROBk= Received: by 10.90.94.12 with SMTP id r12mr521135agb.108.1218664943825; Wed, 13 Aug 2008 15:02:23 -0700 (PDT) Received: by 10.100.43.1 with HTTP; Wed, 13 Aug 2008 15:02:23 -0700 (PDT) Message-ID: <2a41acea0808131502y39879a22u39c472bd0b810fc2@mail.gmail.com> Date: Wed, 13 Aug 2008 15:02:23 -0700 From: "Jack Vogel" To: "FreeBSD Stable List" , "freebsd-net@freebsd.org" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: HEADS UP: E1000 networking changes in STABLE/7.1 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: Wed, 13 Aug 2008 22:31:43 -0000 There is a change that has been in the STABLE tree for a few months, but many might have missed it, its an important change to note and possibly for some prepare for with the 7.1 RELEASE. There is a new E1000 network driver, igb, which supports two family of adapters so far: the 82575 and the new 82576. In FreeBSD 7 the support for 82575 was in the em driver, however due to support issues across all the OS's we do drivers for, the decision was made to split the newer drivers off from those before. There are big differences in the register set, and in things like the descriptor format that made this expedient. I made the support for the 82575 available very early in FreeBSD, earlier even than Linux so that certain vendors could have a working driver early. At first I thought to avoid splitting the driver, but support issues are going to make that impractical. So there is a split, its been in HEAD since Febuary, and now 7.1 will release with this change. What this means is that if you have 82575 adapters in a system they are going to change from being 'emX' to being 'igbX', in the RELEASE the install kernel will have both drivers in it, but on an upgrade path, or using a set of scripts that get postinstalled you need to be ready to make this change. How can you tell if you have such a device: Simple, use pciconf, there are only 3 ID's that are effected: 0x10A7, 0x10A9, and 0x10D6. If you have questions feel free to email me. Cheers, Jack Vogel Intel Lan Access Division From owner-freebsd-net@FreeBSD.ORG Thu Aug 14 03:11:19 2008 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 6E516106566C for ; Thu, 14 Aug 2008 03:11:19 +0000 (UTC) (envelope-from paul@gtcomm.net) Received: from atlas.gtcomm.net (atlas.gtcomm.net [67.215.15.242]) by mx1.freebsd.org (Postfix) with ESMTP id 3598C8FC14 for ; Thu, 14 Aug 2008 03:11:19 +0000 (UTC) (envelope-from paul@gtcomm.net) Received: from c-76-108-197-4.hsd1.fl.comcast.net ([76.108.197.4] helo=[192.168.1.6]) by atlas.gtcomm.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1KTT8E-0006Gw-No; Wed, 13 Aug 2008 23:04:10 -0400 Message-ID: <48A3A2DA.8030404@gtcomm.net> Date: Wed, 13 Aug 2008 23:13:30 -0400 From: Paul User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: Jack Vogel References: <2a41acea0808131502y39879a22u39c472bd0b810fc2@mail.gmail.com> In-Reply-To: <2a41acea0808131502y39879a22u39c472bd0b810fc2@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-net@freebsd.org" Subject: Re: HEADS UP: E1000 networking changes in STABLE/7.1 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: Thu, 14 Aug 2008 03:11:19 -0000 Hi Jack. Will the em driver ever support the multiple hardware queues of the 82571 or are we just stuck with the standard em driver? Has there been any significant change in the em driver itself ? I have a feeling that the 82571 should be in the igb driver but for some reason it isn't. I am curious because we have a LOT of 4 port 82571 PCI-E cards and they are not cheap. :] Thanks Paul Jack Vogel wrote: > There is a change that has been in the STABLE tree for a few months, > but many might have missed it, > its an important change to note and possibly for some prepare for with > the 7.1 RELEASE. > > There is a new E1000 network driver, igb, which supports two family of > adapters so far: the > 82575 and the new 82576. In FreeBSD 7 the support for 82575 was in > the em driver, however > due to support issues across all the OS's we do drivers for, the > decision was made to split the > newer drivers off from those before. There are big differences in the > register set, and in things > like the descriptor format that made this expedient. > > I made the support for the 82575 available very early in FreeBSD, > earlier even than Linux so > that certain vendors could have a working driver early. At first I > thought to avoid splitting the > driver, but support issues are going to make that impractical. So > there is a split, its been in > HEAD since Febuary, and now 7.1 will release with this change. > > What this means is that if you have 82575 adapters in a system they > are going to change > from being 'emX' to being 'igbX', in the RELEASE the install kernel > will have both drivers > in it, but on an upgrade path, or using a set of scripts that get > postinstalled you need to > be ready to make this change. > > How can you tell if you have such a device: Simple, use pciconf, there > are only 3 ID's > that are effected: 0x10A7, 0x10A9, and 0x10D6. > > If you have questions feel free to email me. > > Cheers, > > Jack Vogel > Intel Lan Access Division > _______________________________________________ > 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 Aug 14 04:35:45 2008 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 445971065675 for ; Thu, 14 Aug 2008 04:35:45 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.231]) by mx1.freebsd.org (Postfix) with ESMTP id EDFE78FC0C for ; Thu, 14 Aug 2008 04:35:44 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wr-out-0506.google.com with SMTP id c8so140522wra.27 for ; Wed, 13 Aug 2008 21:35:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=10D+RdUaxPgTGfF/B8pCJkjUkk4L1pAcYrEwZgv/VHc=; b=d9gX0bwpMfPvETaQbfTfNkK2K2Ma6hPEaVfSIuMlUHwGz5xIaqDGo0s31h3ABhfcx8 BBMbA75DgFhuy+eUso4z5pcbpGKWFx69mwKOsbYaj4SvQKE2CHeiFsT6U8ZrXh4Xt8fy OtrsHJ2BJc2UXnaPCWiAyEfPTLlltl7gXCk6A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=PgEUVwT39P6qVVa2ISi/BSi9A76ouctfYsHI2siE48F/6nZzcrTOWqbJWT20te8HLT 9xtNVWFrB1gApYbgaIFabUPZ2VHdBvMFXrBDAJhEnkxuncWfkS3+A4jOkBBidImANljj 42ptGwmEF0/cZN6N8R2R3/3IYCfNbO1FWyg4k= Received: by 10.90.92.14 with SMTP id p14mr1076466agb.84.1218688544256; Wed, 13 Aug 2008 21:35:44 -0700 (PDT) Received: by 10.100.43.1 with HTTP; Wed, 13 Aug 2008 21:35:44 -0700 (PDT) Message-ID: <2a41acea0808132135oe9ebc6bk9423ac19f2e9f77a@mail.gmail.com> Date: Wed, 13 Aug 2008 21:35:44 -0700 From: "Jack Vogel" To: Paul In-Reply-To: <48A3A2DA.8030404@gtcomm.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0808131502y39879a22u39c472bd0b810fc2@mail.gmail.com> <48A3A2DA.8030404@gtcomm.net> Cc: "freebsd-net@freebsd.org" , FreeBSD Stable List Subject: Re: HEADS UP: E1000 networking changes in STABLE/7.1 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: Thu, 14 Aug 2008 04:35:45 -0000 On Wed, Aug 13, 2008 at 8:13 PM, Paul wrote: > Hi Jack. Will the em driver ever support the multiple hardware queues of > the 82571 or are we just stuck with the standard em driver? > Has there been any significant change in the em driver itself ? > I have a feeling that the 82571 should be in the igb driver but for some > reason it isn't. I am curious because we have a LOT of 4 port 82571 PCI-E > cards and they are not cheap. :] Hey Paul, You are right, quad port cards aren't cheap, Intel has sold them even back in a PCI-X based system. And the one you are talking about was released since I have been in this job, so pretty new :) However, they will never support multiple queues, the reason being that in order to do this you need multple MSI vectors, in other words, MSIX. Still, they are very handy, they do support MSI, but just one per interface. Oh, and I debated about where to make the cutoff line on the em/igb split and decided the best thing to do was to follow Linux. The biggest difference between the two drivers is that those in the igb use a different descriptor format, called 'advanced descriptors'. The split does NOT mean that em is now fixed. Quite the contrary, the em driver that was just MFC'd into STABLE has support for what I think is going to be the coolest new consumer adapter out there, called 82574, code name Hartwell, and also for ICH10. Both these two new interfaces have IEEE 1588 Precision Time Protocol support, something that is becoming important for networked multimedia applications. Oh, and Hartwell is the first adapter in the em driver that actually does multiqueue, although in a limited fashion, it does MSIX. This adapter is made at a lower cost point, but it has really nice features. I only wish the new motherboard that I bought had them rather than ICH9 but oh well :) I predict they are going to be selling like hotcakes before the end of year. I will continue to share fixes between the em and igb drivers as they are applicable. I still think a real legacy driver for the oldest adapters would be a good idea, just so they don't get broken by new development, with as many as we support regression testing is already not being done adequately. I just have not had time to think about this yet, it may be coming, it would probably be for everything that was not PCI Express. Hope the info was helpful, I'm always happy to answer questions, Jack From owner-freebsd-net@FreeBSD.ORG Thu Aug 14 05:00:15 2008 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 45D7F106568D for ; Thu, 14 Aug 2008 05:00:15 +0000 (UTC) (envelope-from paul@gtcomm.net) Received: from atlas.gtcomm.net (atlas.gtcomm.net [67.215.15.242]) by mx1.freebsd.org (Postfix) with ESMTP id 087808FC16 for ; Thu, 14 Aug 2008 05:00:14 +0000 (UTC) (envelope-from paul@gtcomm.net) Received: from c-76-108-197-4.hsd1.fl.comcast.net ([76.108.197.4] helo=[192.168.1.6]) by atlas.gtcomm.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1KTUpi-0006xV-Le; Thu, 14 Aug 2008 00:53:10 -0400 Message-ID: <48A3BC67.3050905@gtcomm.net> Date: Thu, 14 Aug 2008 01:02:31 -0400 From: Paul User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: Jack Vogel References: <2a41acea0808131502y39879a22u39c472bd0b810fc2@mail.gmail.com> <48A3A2DA.8030404@gtcomm.net> <2a41acea0808132135oe9ebc6bk9423ac19f2e9f77a@mail.gmail.com> In-Reply-To: <2a41acea0808132135oe9ebc6bk9423ac19f2e9f77a@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-net@freebsd.org" Subject: Re: HEADS UP: E1000 networking changes in STABLE/7.1 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: Thu, 14 Aug 2008 05:00:15 -0000 The hardware spec sheet says it does support multi queue but only MSI, so I would suspect it is disabled by default since that would (maybe) cause performance to be less. Would it take advantage of multiple cpus to turn on the multiple queues even without MSIX? (i.e. having more than 1 taskq in freebsd per interface for receives/sends) It should still do per-vector masking so it couldn't be THAT bad with the multi queues enabled but there's probably a good reason why they are disabled by default eh? Would be fun to test it out though :> :> I think even if the driver / bsd split it up into multiple taskq's so it would take advantage of SMP better that it would work, but that might require some modifications outside of the driver level (which I can think of a lot) but I guess i"m hoping for an easier solution so I don't have to go replacing all these 82571EB cards.. They work great, but the cpus are running out.. Having 3 or 4 idle cpus while the other ones are struggling due to network load and dropping packets is aggravating :) Will the 82575/6 cards alleviate that problem or will I still be faced with the same issue (due to os limitations)? I plan on buying the dual port ET controller[82576] (which was supoosed to be shipping last month) but I can't find one anywhere! argh.. Thanks Paul Jack Vogel wrote: > On Wed, Aug 13, 2008 at 8:13 PM, Paul wrote: > >> Hi Jack. Will the em driver ever support the multiple hardware queues of >> the 82571 or are we just stuck with the standard em driver? >> Has there been any significant change in the em driver itself ? >> I have a feeling that the 82571 should be in the igb driver but for some >> reason it isn't. I am curious because we have a LOT of 4 port 82571 PCI-E >> cards and they are not cheap. :] >> > > Hey Paul, > > You are right, quad port cards aren't cheap, Intel has sold them > even back in a > PCI-X based system. And the one you are talking about was released since I > have been in this job, so pretty new :) However, they will never > support multiple > queues, the reason being that in order to do this you need multple MSI vectors, > in other words, MSIX. Still, they are very handy, they do support MSI, but just > one per interface. Oh, and I debated about where to make the cutoff line on the > em/igb split and decided the best thing to do was to follow Linux. The biggest > difference between the two drivers is that those in the igb use a > different descriptor > format, called 'advanced descriptors'. > > The split does NOT mean that em is now fixed. Quite the contrary, > the em driver > that was just MFC'd into STABLE has support for what I think is going to be the > coolest new consumer adapter out there, called 82574, code name Hartwell, and > also for ICH10. Both these two new interfaces have IEEE 1588 Precision Time > Protocol support, something that is becoming important for networked multimedia > applications. Oh, and Hartwell is the first adapter in the em driver > that actually > does multiqueue, although in a limited fashion, it does MSIX. This > adapter is made > at a lower cost point, but it has really nice features. I only wish > the new motherboard > that I bought had them rather than ICH9 but oh well :) I predict they > are going to > be selling like hotcakes before the end of year. > > I will continue to share fixes between the em and igb drivers as they > are applicable. > I still think a real legacy driver for the oldest adapters would be a > good idea, just so > they don't get broken by new development, with as many as we support regression > testing is already not being done adequately. I just have not had time > to think about > this yet, it may be coming, it would probably be for everything that > was not PCI Express. > > Hope the info was helpful, I'm always happy to answer questions, > > Jack > _______________________________________________ > 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 Aug 14 05:25:05 2008 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 5CA0A106567F for ; Thu, 14 Aug 2008 05:25:05 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.224]) by mx1.freebsd.org (Postfix) with ESMTP id 11B2E8FC17 for ; Thu, 14 Aug 2008 05:25:04 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wr-out-0506.google.com with SMTP id c8so145769wra.27 for ; Wed, 13 Aug 2008 22:25:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=syQMyp3H+2lbvRIJIMcmGc7koQNbWUODq2pr41FU2vA=; b=WMvEL+he/IfR0JMRvUj3MCUDeuUFDPaFYOzyGv3rASGX2omzTBd/pz4iv2FSZQO+hQ mOaC5f/WYs9ais+ePoRI6FaSwgrHjspyJxr41zfcLNAtzBS5Q0SLmBmv66rmB8IIwveJ QhrZGLdk/n8IccahXBFELmEF9tTV91lzATNGU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=jig3k6qgbED7bqRWRkIcSssYwwBGDomuHT1fnK4YQb7rvmkSmFPjjuc3q5ykSRbVN8 t23RmVFneIyyA2DCi2tRIjooqbt1En88PzEljsR1+9SBUvanK9g6vDZ+MpuFNBjDUfaz fT/gjRjwhlIMp9Qbw9LYZH7Q1p9C0xUC+kUHo= Received: by 10.90.113.17 with SMTP id l17mr1143663agc.20.1218691503950; Wed, 13 Aug 2008 22:25:03 -0700 (PDT) Received: by 10.100.43.1 with HTTP; Wed, 13 Aug 2008 22:25:03 -0700 (PDT) Message-ID: <2a41acea0808132225s6e77175fnf6780b249ed07058@mail.gmail.com> Date: Wed, 13 Aug 2008 22:25:03 -0700 From: "Jack Vogel" To: Paul In-Reply-To: <48A3BC67.3050905@gtcomm.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0808131502y39879a22u39c472bd0b810fc2@mail.gmail.com> <48A3A2DA.8030404@gtcomm.net> <2a41acea0808132135oe9ebc6bk9423ac19f2e9f77a@mail.gmail.com> <48A3BC67.3050905@gtcomm.net> Cc: "freebsd-net@freebsd.org" Subject: Re: HEADS UP: E1000 networking changes in STABLE/7.1 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: Thu, 14 Aug 2008 05:25:05 -0000 On Wed, Aug 13, 2008 at 10:02 PM, Paul wrote: > The hardware spec sheet says it does support multi queue but only MSI, so I > would suspect it is disabled by default since that would (maybe) cause > performance to be less. > Would it take advantage of multiple cpus to turn on the multiple queues > even without MSIX? (i.e. having more than 1 taskq in freebsd per interface > for receives/sends) > It should still do per-vector masking so it couldn't be THAT bad with the > multi queues enabled but there's probably a good reason why they are > disabled by default eh? Would be > fun to test it out though :> :> > I think even if the driver / bsd split it up into multiple taskq's so it > would take advantage of SMP better that it would work, but that might > require some modifications outside of the ome of his work within a couple weeks. I have also been working on what performance tweaks I havedriver level (which I can think of > a lot) but I guess i"m hoping for an easier solution so > I don't have to go replacing all these 82571EB cards.. They work great, but > the cpus are running out.. Having 3 or 4 idle cpus while the other ones are > struggling due to network load and dropping packets is aggravating :) Will > the 82575/6 cards alleviate that problem or will I still be faced with the > same issue (due to os limitations)? > I plan on buying the dual port ET controller[82576] (which was supoosed to > be shipping last month) but I can't find one anywhere! argh.. The Linux team here implemented multiqueue based on 82571 3 or 4 years ago, they found that without MSIX it just caused more problems than it was worth and they turned it off again until recently. Linux is in a better position right now, Dave Miller has been hacking madly at their stack and they have pretty complete multiqueue support in the stack. One of my friends here at Intel was responsible for a lot of the work and code along the way. I know there's stack work going on, hopefully all drivers will benefit from that as it comes out. Also Kip Macy has been doing some work for a customer that is based on my igb code, he promised to have some patches back to me in a couple weeks, I'm sure it will be good stuff too. I do not know how hard 82576 is to get right now, it has a TON of potential that I have no where near tapped yet. Before the firedrill the last couple of days I had started on updating the ioatdma driver, which we need so that I can put DCA into the igb driver (Direct Cache Access), that should be a big performance enhancer when I can get it done. Jack From owner-freebsd-net@FreeBSD.ORG Thu Aug 14 05:43:40 2008 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 127C31065677 for ; Thu, 14 Aug 2008 05:43:40 +0000 (UTC) (envelope-from paul@gtcomm.net) Received: from atlas.gtcomm.net (atlas.gtcomm.net [67.215.15.242]) by mx1.freebsd.org (Postfix) with ESMTP id C82E38FC1F for ; Thu, 14 Aug 2008 05:43:39 +0000 (UTC) (envelope-from paul@gtcomm.net) Received: from c-76-108-197-4.hsd1.fl.comcast.net ([76.108.197.4] helo=[192.168.1.6]) by atlas.gtcomm.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1KTVVh-0001xZ-Hi; Thu, 14 Aug 2008 01:36:33 -0400 Message-ID: <48A3C692.3000909@gtcomm.net> Date: Thu, 14 Aug 2008 01:45:54 -0400 From: Paul User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: Jack Vogel References: <2a41acea0808131502y39879a22u39c472bd0b810fc2@mail.gmail.com> <48A3A2DA.8030404@gtcomm.net> <2a41acea0808132135oe9ebc6bk9423ac19f2e9f77a@mail.gmail.com> <48A3BC67.3050905@gtcomm.net> <2a41acea0808132225s6e77175fnf6780b249ed07058@mail.gmail.com> In-Reply-To: <2a41acea0808132225s6e77175fnf6780b249ed07058@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-net@freebsd.org" Subject: Re: HEADS UP: E1000 networking changes in STABLE/7.1 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: Thu, 14 Aug 2008 05:43:40 -0000 Nice.. Now if they would just optimize the IP stack for SMP and the rest of the drivers we may have a piece of equipment and OS that will compete with the hardware vendor routers :) Full BGP, a few million pps(I hope), and filters.. Nothing does that right now short of Juniper M7i or Cisco SUP720-3b/cxl or 72xx, etc.. Of course the first 2 do it way faster but are also very expensive. Linux is backwards on packet forwarding until they get rid of the route cache, it's almost useless in a service provider environment (millions of flows and hundreds of thousands of new flows per second for instance), although it's still the most flexible. Please keep us updated on any interesting changes to the em/igb/ixgb :> I have ordered an 82575 card and will be testing it along with some other CPUs to fire up my routing performance thread again :> :> Paul > The Linux team here implemented multiqueue based on 82571 3 or 4 years ago, > they found that without MSIX it just caused more problems than it was worth > and they turned it off again until recently. > > Linux is in a better position right now, Dave Miller has been hacking madly at > their stack and they have pretty complete multiqueue support in the stack. One > of my friends here at Intel was responsible for a lot of the work and code along > the way. > > I know there's stack work going on, hopefully all drivers will benefit from that > as it comes out. Also Kip Macy has been doing some work for a customer > that is based on my igb code, he promised to have some patches back to me > in a couple weeks, I'm sure it will be good stuff too. > > I do not know how hard 82576 is to get right now, it has a TON of potential > that I have no where near tapped yet. Before the firedrill the last couple of > days I had started on updating the ioatdma driver, which we need so that > I can put DCA into the igb driver (Direct Cache Access), that should be a > big performance enhancer when I can get it done. > > Jack > > From owner-freebsd-net@FreeBSD.ORG Thu Aug 14 17:51:59 2008 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 4F0F01065677 for ; Thu, 14 Aug 2008 17:51:59 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from proxy.meer.net (proxy.meer.net [64.13.141.13]) by mx1.freebsd.org (Postfix) with ESMTP id 3E52D8FC18 for ; Thu, 14 Aug 2008 17:51:59 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [64.13.141.3]) by proxy.meer.net (8.14.2/8.14.2) with ESMTP id m7EHpu2D098843; Thu, 14 Aug 2008 10:51:58 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from mail2.meer.net (mail2.meer.net [64.13.141.16]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id m7EHptKx026262; Thu, 14 Aug 2008 10:51:55 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (209.249.190.254.available.above.net [209.249.190.254] (may be forged)) (authenticated bits=0) by mail2.meer.net (8.14.1/8.14.1) with ESMTP id m7EHps5m008209; Thu, 14 Aug 2008 10:51:54 -0700 (PDT) (envelope-from gnn@neville-neil.com) Date: Thu, 14 Aug 2008 13:51:54 -0400 Message-ID: From: gnn@freebsd.org To: "Jack Vogel" In-Reply-To: <2a41acea0808131502y39879a22u39c472bd0b810fc2@mail.gmail.com> References: <2a41acea0808131502y39879a22u39c472bd0b810fc2@mail.gmail.com> User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.7 Emacs/22.2.50 (i386-apple-darwin9.4.0) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Canit-CHI2: 0.50 X-Bayes-Prob: 0.5 (Score 0, tokens from: ) X-Spam-Score: 0.10 () [Tag at 5.00] COMBINED_FROM X-CanItPRO-Stream: default X-Canit-Stats-ID: 1239928 - d63185b3a2b4 X-Scanned-By: CanIt (www . roaringpenguin . com) on 64.13.141.13 Cc: "freebsd-net@freebsd.org" , FreeBSD Stable List Subject: Re: HEADS UP: E1000 networking changes in STABLE/7.1 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: Thu, 14 Aug 2008 17:51:59 -0000 Hi Jack, Thanks for this and for the concise pciconf line. We use em (soon to be igb) interfaces extensively at work. Best, George From owner-freebsd-net@FreeBSD.ORG Sat Aug 16 01:56:28 2008 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 DEC381065677 for ; Sat, 16 Aug 2008 01:56:28 +0000 (UTC) (envelope-from rfrench@freebsd.org) Received: from oberon.wxnz.net (oberon.wxnz.net [58.28.6.13]) by mx1.freebsd.org (Postfix) with ESMTP id BEFF68FC1C for ; Sat, 16 Aug 2008 01:56:28 +0000 (UTC) (envelope-from rfrench@freebsd.org) Received: from mini-tank.local (ip-58-28-152-154.static-xdsl.xnet.co.nz [58.28.152.154]) by oberon.wxnz.net (Postfix) with ESMTP id B5CD6464105 for ; Sat, 16 Aug 2008 13:59:43 +1200 (NZST) From: Ryan French To: freebsd-net@freebsd.org Date: Sat, 16 Aug 2008 13:56:26 +1200 User-Agent: KMail/1.9.9 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200808161356.26891.rfrench@freebsd.org> Subject: .pru_attach and kernel warnings 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, 16 Aug 2008 01:56:28 -0000 Hi everyone, I'm having issues with trying to build my kernel at the moment with my MPLS development code included. I'm trying to build a pr_usrreqs struct and with my attach method I am getting the warning 'initialization from incompatible pointer type', but as far as I can see the way I have done it is the same as other protocols. static int mpls_attach(struct socket *so) { int error = 0; if (so->so_snd.sb_hiwat == 0 || so->so_rcv.sb_hiwat == 0) { error = soreserve(so, mpls_raw_sendspace, mpls_raw_recvspace); return error; } else return EOPNOTSUPP; } struct pr_usrreqs mpls_raw_usrreq = { .pru_accept = pru_accept_notsupp, .pru_attach = mpls_attach, .pru_bind = pru_bind_notsupp, .pru_connect = pru_connect_notsupp, .pru_connect2 = pru_connect2_notsupp, .pru_control = mpls_control, .pru_disconnect = pru_disconnect_notsupp, .pru_listen = pru_listen_notsupp, .pru_peeraddr = pru_peeraddr_notsupp, .pru_rcvd = pru_rcvd_notsupp, .pru_rcvoob = pru_rcvoob_notsupp, .pru_send = pru_send_notsupp, .pru_sense = pru_sense_null, .pru_shutdown = pru_shutdown_notsupp, .pru_sockaddr = pru_sockaddr_notsupp, .pru_sosend = pru_sosend_notsupp, .pru_soreceive = pru_soreceive_notsupp, .pru_sopoll = pru_sopoll_notsupp }; Should I ignore this warning or is there a problem with my code that I'm missing? Thanks for any help. From owner-freebsd-net@FreeBSD.ORG Sat Aug 16 03:07:51 2008 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 8DAFD1065690; Sat, 16 Aug 2008 03:07:51 +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 7CF4B8FC1E; Sat, 16 Aug 2008 03:07:51 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m7G37pGp057823; Sat, 16 Aug 2008 03:07:51 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m7G37pUK057819; Sat, 16 Aug 2008 03:07:51 GMT (envelope-from linimon) Date: Sat, 16 Aug 2008 03:07:51 GMT Message-Id: <200808160307.m7G37pUK057819@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/126561: [nlm] NLM (rpclockd) RPC UNLOCK failure (stalls Mac OS X Finder, iTunes, etc?) 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, 16 Aug 2008 03:07:51 -0000 Old Synopsis: NLM (rpclockd) RPC UNLOCK failure (stalls Mac OS X Finder, iTunes, etc?) New Synopsis: [nlm] NLM (rpclockd) RPC UNLOCK failure (stalls Mac OS X Finder, iTunes, etc?) Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sat Aug 16 03:06:30 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=126561 From owner-freebsd-net@FreeBSD.ORG Sat Aug 16 05:40:22 2008 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 26F081065671; Sat, 16 Aug 2008 05:40:22 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (hergotha.csail.mit.edu [66.92.79.170]) by mx1.freebsd.org (Postfix) with ESMTP id BC1FE8FC16; Sat, 16 Aug 2008 05:40:21 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (localhost [127.0.0.1]) by hergotha.csail.mit.edu (8.13.8/8.13.8) with ESMTP id m7G5BG1B083708; Sat, 16 Aug 2008 01:11:16 -0400 (EDT) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.13.8/8.13.8/Submit) id m7G5BEb1083707; Sat, 16 Aug 2008 01:11:14 -0400 (EDT) (envelope-from wollman) Date: Sat, 16 Aug 2008 01:11:14 -0400 (EDT) From: Garrett Wollman Message-Id: <200808160511.m7G5BEb1083707@hergotha.csail.mit.edu> To: rfrench@freebsd.org In-Reply-To: <200808161356.26891.rfrench@freebsd.org> Organization: None X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (hergotha.csail.mit.edu [127.0.0.1]); Sat, 16 Aug 2008 01:11:16 -0400 (EDT) X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on hergotha.csail.mit.edu Cc: net@freebsd.org Subject: Re: .pru_attach and kernel warnings 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, 16 Aug 2008 05:40:22 -0000 In article <200808161356.26891.rfrench@freebsd.org>, rfrench@freebsd.org writes: >static int >mpls_attach(struct socket *so) The prototype for a protocol attach functions is int (*pru_attach)(struct socket *so, int proto, struct thread *td); (see sys/protosw.h). You don't have to use these arguments, but you do have to declare them properly. -GAWollman From owner-freebsd-net@FreeBSD.ORG Sat Aug 16 12:37:16 2008 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 08498106566C; Sat, 16 Aug 2008 12:37:16 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CD6858FC1A; Sat, 16 Aug 2008 12:37:15 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (gavin@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m7GCbFsv061252; Sat, 16 Aug 2008 12:37:15 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m7GCbFY3061248; Sat, 16 Aug 2008 12:37:15 GMT (envelope-from gavin) Date: Sat, 16 Aug 2008 12:37:15 GMT Message-Id: <200808161237.m7GCbFY3061248@freefall.freebsd.org> To: intron@intron.ac, gavin@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-net@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: kern/126564: [ath] doesn't work with my PCI-E X1 wireless network adaptor 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, 16 Aug 2008 12:37:16 -0000 Synopsis: [ath] doesn't work with my PCI-E X1 wireless network adaptor State-Changed-From-To: open->feedback State-Changed-By: gavin State-Changed-When: Sat Aug 16 12:35:46 UTC 2008 State-Changed-Why: To submitter: can you try the updated HAL from http://people.freebsd.org/~sam/ath_hal-20080528.tgz (unpack into /usr/src/sys/contrib/ath) and see if that fixes theings for you? Responsible-Changed-From-To: freebsd-i386->freebsd-net Responsible-Changed-By: gavin Responsible-Changed-When: Sat Aug 16 12:35:46 UTC 2008 Responsible-Changed-Why: Over to maintainers http://www.freebsd.org/cgi/query-pr.cgi?pr=126564