From owner-freebsd-net@FreeBSD.ORG Sun Oct 25 09:24:10 2009 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 9C008106568F for ; Sun, 25 Oct 2009 09:24:10 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mx01.netsrc.de (mx01.netsrc.de [89.107.71.100]) by mx1.freebsd.org (Postfix) with ESMTP id 55D358FC0A for ; Sun, 25 Oct 2009 09:24:09 +0000 (UTC) Received: from maja.lab.techwires.net (dslb-088-067-210-182.pools.arcor-ip.net [88.67.210.182]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.netsrc.de (Postfix) with ESMTP id 7BE47192FD9; Sun, 25 Oct 2009 10:24:08 +0100 (CET) Received: from maja.lab.techwires.net (localhost [127.0.0.1]) by maja.lab.techwires.net (8.14.3/8.14.3) with ESMTP id n9P9O70K001877; Sun, 25 Oct 2009 10:24:07 +0100 (CET) (envelope-from bschmidt@techwires.net) Received: (from bschmidt@localhost) by maja.lab.techwires.net (8.14.3/8.14.3/Submit) id n9P9O6hR001876; Sun, 25 Oct 2009 10:24:06 +0100 (CET) (envelope-from bschmidt@techwires.net) X-Authentication-Warning: maja.lab.sad1.techwires.net: bschmidt set sender to bschmidt@techwires.net using -f From: Bernhard Schmidt To: freebsd-net@freebsd.org Date: Sun, 25 Oct 2009 10:24:06 +0100 User-Agent: KMail/1.12.1 (FreeBSD/9.0-CURRENT; KDE/4.3.1; amd64; ; ) References: <20091009170839.142800@gmx.net> <3F27A279-6347-456B-A9B6-7CE847DD1A49@gmail.com> <11167f520910241241o6a1ada3cmf076add6374a1add@mail.gmail.com> In-Reply-To: <11167f520910241241o6a1ada3cmf076add6374a1add@mail.gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200910251024.06856.bschmidt@techwires.net> Cc: "Sam Fourman Jr." , Rui Paulo Subject: Re: Intel WiFi 5100/5300 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Oct 2009 09:24:10 -0000 On Saturday 24 October 2009 21:41:39 Sam Fourman Jr. wrote: > Just wanted to make everyone aware that OpenBSD just 1 hour ago commited > a bunch of changes to their iwn driver. maybe some of it is useful for > FreeBSD as well? > > Log message: > huge diff introducing many of the recent changes made by intel to iwlwifi: > - ICT interrupts for >=5000 series (avoids reading IWN_INT which is slow) > - support v2 firmware header (including build number) > - switch to v2 firmware api (requires a firmware package upgrade) > - initial support for 1000 series and initial bits for upcoming 6000 > series (untested as hardware is not available to the general public) > - many bug fixes, including workarounds for hardware bugs > > make sure to update your iwn-firmware package to iwn-firmware-5.2. Definitely, I'll look into that. -- Bernhard From owner-freebsd-net@FreeBSD.ORG Sun Oct 25 20:00:12 2009 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 92E1710656A7 for ; Sun, 25 Oct 2009 20:00:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 344548FC17 for ; Sun, 25 Oct 2009 20:00:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9PK0BDL025547 for ; Sun, 25 Oct 2009 20:00:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9PK0BGp025546; Sun, 25 Oct 2009 20:00:11 GMT (envelope-from gnats) Date: Sun, 25 Oct 2009 20:00:11 GMT Message-Id: <200910252000.n9PK0BGp025546@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Mark Atkinson Cc: Subject: Re: kern/124127: [msk] watchdog timeout (missed Tx interrupts) -- recovering X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mark Atkinson List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Oct 2009 20:00:12 -0000 The following reply was made to PR kern/124127; it has been noted by GNATS. From: Mark Atkinson To: freebsd prs Cc: Subject: Re: kern/124127: [msk] watchdog timeout (missed Tx interrupts) -- recovering Date: Sun, 25 Oct 2009 12:55:38 -0700 (PDT) After a week on a Oct 19th 2009 built kernel, I got hit with the watchdog again, so I applied the patch. The msk interface was non functional (came up but was unable to pass traffic) after applying the patch, so I booted back to the unpatched kernel. Mark Atkinson atkin901@yahoo.com (!wired)?(coffee++):(wired); From owner-freebsd-net@FreeBSD.ORG Mon Oct 26 09:43:09 2009 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 00CA6106566C for ; Mon, 26 Oct 2009 09:43:09 +0000 (UTC) (envelope-from s-XU9OVxO37oYw2zIyoGNOn9HZNI39CXHtwoDIFYuAXzPRtor1G-z3_G@bounce.linkedin.com) Received: from mail16-a-ad.linkedin.com (mail16-a-ad.linkedin.com [208.111.169.140]) by mx1.freebsd.org (Postfix) with ESMTP id C3D038FC15 for ; Mon, 26 Oct 2009 09:43:08 +0000 (UTC) DomainKey-Signature: s=prod; d=linkedin.com; c=nofws; q=dns; h=Sender:Date:From:To:Message-ID:Subject:MIME-Version: Content-Type:X-LinkedIn-fbl; b=LBtVTExpkBo20T0ujsGJTsqoMgv2rhcFdldbD3GrrRB47cm3+5/AkKgK tCCuwSqyrHLoKZ8/cCk/vJfT/QLnCE1NdROI7BdSqIR6+2MUl1FnR9HLN P1HLS08w6d9Uin5; Sender: messages-noreply@bounce.linkedin.com Date: Mon, 26 Oct 2009 02:15:07 -0700 (PDT) From: saravana perumal To: Scott Ullrich Message-ID: <1091669987.2430605.1256548507494.JavaMail.app@ech3-cdn06.prod> MIME-Version: 1.0 X-LinkedIn-fbl: XU9OVxO37oYw2zIyoGNOn9HZNI39CXHtwoDIFYuAXzPRtor1G-z3_G Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Invitation to connect on LinkedIn 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, 26 Oct 2009 09:43:09 -0000 LinkedIn ------------ saravana perumal requested to add you as a connection on LinkedIn: ------------------------------------------ Scott, I'd like to add you to my professional network on LinkedIn. - saravana Accept invitation from saravana perumal http://www.linkedin.com/e/PLgN6ynStv_BKk9UWJP96hnStv_BKkDo9Z0f/blk/I1533505122_2/pmpxnSRJrSdvj4R5fnhv9ClRsDgZp6lQs6lzoQ5AomZIpn8_cBYOcz4Rc3kPcPkNiiZds7x7rnhJmyYUdz0PcPAVcjwLrCBxbOYWrSlI/EML_comm_afe/ View invitation from saravana perumal http://www.linkedin.com/e/PLgN6ynStv_BKk9UWJP96hnStv_BKkDo9Z0f/blk/I1533505122_2/39vcz8Ndj0RcPcRckALqnpPbOYWrSlI/svi/ ------------------------------------------ DID YOU KNOW that LinkedIn can find the answers to your most difficult questions? Post those vexing questions on LinkedIn Answers to tap into the knowledge of the world's foremost business experts: http://www.linkedin.com/e/ask/inv-23/ ------ (c) 2009, LinkedIn Corporation From owner-freebsd-net@FreeBSD.ORG Mon Oct 26 11:07:04 2009 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 7064A106568B for ; Mon, 26 Oct 2009 11:07:04 +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 5CFB28FC13 for ; Mon, 26 Oct 2009 11:07:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9QB74KS043835 for ; Mon, 26 Oct 2009 11:07:04 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9QB737U043833 for freebsd-net@FreeBSD.org; Mon, 26 Oct 2009 11:07:03 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 26 Oct 2009 11:07:03 GMT Message-Id: <200910261107.n9QB737U043833@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, 26 Oct 2009 11:07:04 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/139761 net [bce] bce driver on IBM HS22 [No PHY found on Child MI o kern/139565 net [ipfilter] ipfilter ioctl SIOCDELST broken o kern/139559 net [tun] several tun(4) interfaces can be created with sa o kern/139387 net [ipsec] Wrong lenth of PF_KEY messages in promiscuous o bin/139346 net [patch] arp(8) add option to remove static entries lis o kern/139268 net [if_bridge] [patch] allow if_bridge to forward just VL o kern/139204 net [arp] DHCP server replies rejected, ARP entry lost bef o kern/139162 net [fwip] [panic] 8.0-RC1 panics if using IP over firewir o kern/139145 net [ip6] IPv6 blackhole / reject routes broken o kern/139117 net [lagg] + wlan boot timing (EBUSY) o kern/139113 net [arp] removing IP alias doesn't delete permanent arp e o kern/139058 net [ipfilter] mbuf cluster leak on FreeBSD 7.2 o kern/138999 net [libc] lighttpd/php-cgi with freebsd sendfile(2) enabl o kern/138850 net [dummynet] dummynet doesn't work correctly on a bridge o kern/138782 net [panic] sbflush_internal: cc 0 || mb 0xffffff004127b00 o kern/138739 net [wpi] wpi(4) does not work very well under 8.0-BETA4 o kern/138694 net [bge] FreeBSD 6.3 release does not recognize Broadcom o amd64/138688 net [rum] possibly broken on 8 Beta 4 amd64: able to wpa a o kern/138678 net [lo] FreeBSD does not assign linklocal address to loop o kern/138676 net [route] after buildworld not work local routes [regres f kern/138666 net [multicast] [panic] not working multicast through igmp o kern/138660 net [igb] igb driver troubles in 8.0-BETA4 o kern/138652 net TCP window scaling value calculated incorrectly? o kern/138620 net [lagg] [patch] lagg port bpf-writes blocked o kern/138427 net [wpi] [panic] Kernel panic after trying set monitor wl o kern/138407 net [gre] gre(4) interface does not come up after reboot o kern/138378 net [altq] [patch] Memory leak in hfsc_class_modify() in f o kern/138332 net [tun] [lor] ifconfig tun0 destroy causes LOR on 8.0-BE o kern/138266 net [panic] kernel panic when udp benchmark test used as r o kern/138177 net [ipfilter] FreeBSD crashing repeatedly in ip_nat.c:257 o kern/138130 net [netinet] [patch] Resource leak in LibAliasRefreshModu o kern/138046 net [tcp] tcp sockets stay in SYN_SENT even after receivin o kern/137881 net [netgraph] [panic] ng_pppoe fatal trap 12 o bin/137841 net [patch] wpa_supplicant(8) cannot verify SHA256 signed p kern/137795 net [sctp] [panic] mtx_lock() of destroyed mutex o kern/137776 net [rum] panic in rum(4) driver on 8.0-BETA2 o kern/137775 net [netgraph] [patch] Add XMIT_FAILOVER to ng_one2many o bin/137641 net ifconfig(8): various problems with "vlan_device.vlan_i o kern/137592 net [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on ne o bin/137484 net [patch] Integer overflow in wpa_supplicant(8) base64 e o kern/137392 net [ip] [panic] crash in ip_nat.c line 2577 o kern/137372 net [ral] FreeBSD doesn't support wireless interface from o kern/137317 net [tcp] logs full of syncache problems o kern/137292 net [ste] DFE-580TX not working properly o kern/137279 net [bge] [panic] Page fault (fatal trap 12) NFS server w/ o kern/137089 net [lagg] lagg falsely triggers IPv6 duplicate address de o bin/136994 net [patch] ifconfig(8) print carp mac address o kern/136943 net [wpi] [lor] wpi0_com_lock / wpi0 o kern/136911 net [netgraph] [panic] system panic on kldload ng_bpf.ko t o kern/136876 net [bge] bge will not resume properly after suspend o kern/136836 net [ath] atheros card stops functioning after about 12 ho o kern/136618 net [pf][stf] panic on cloning interface without unit numb o kern/136482 net [age] Attansic L1 Gigabit Ethernet recieves multicasts o kern/136426 net [panic] spawning several dhclients in parallel panics o kern/136168 net [em] em driver initialization fails on Intel 5000PSL m o kern/135836 net [bce] bce BCM5709 Watchdog after warm boot - ok after o kern/135502 net [periodic] Warning message raised by rtfree function i o kern/135222 net [igb] low speed routing between two igb interfaces o kern/135067 net [patch] [fib] Incorrect KASSERTs in sys/net/route.c o kern/134956 net [em] FreeBSD 7.1 & 7.2, Intel PRO/1000 PT Quad Port Se o kern/134931 net [route] [fib] Route messages sent to all socket listen o kern/134658 net [bce] bce driver fails on PowerEdge m610 blade. o kern/134583 net [hang] Machine with jail freezes after random amount o o kern/134531 net [route] [panic] kernel crash related to routes/zebra o kern/134401 net [msk] [panic] Kernel Fatal trap 12: page fault while i o kern/134369 net [route] [ip6] IPV6 in Head broken for routing table up o kern/134168 net [ral] ral driver problem on RT2525 2.4GHz transceiver o kern/134157 net [dummynet] dummynet loads cpu for 100% and make a syst o kern/134079 net [em] "em0: Invalid MAC address" in FreeBSD-Current ( 8 o kern/133969 net [dummynet] [panic] Fatal trap 12: page fault while in o kern/133968 net [dummynet] [panic] dummynet kernel panic o kern/133902 net [tun] Killing tun0 iface ssh tunnel causes Panic Strin o kern/133786 net [netinet] [patch] ip_input might cause kernel panic o kern/133736 net [udp] ip_id not protected ... o kern/133613 net [wpi] [panic] kernel panic in wpi(4) o kern/133595 net [panic] Kernel Panic at pcpu.h:195 o kern/133572 net [ppp] [hang] incoming PPTP connection hangs the system o kern/133490 net [bpf] [panic] 'kmem_map too small' panic on Dell r900 o kern/133328 net [bge] [panic] Kernel panics with Windows7 client o kern/133235 net [netinet] [patch] Process SIOCDLIFADDR command incorre o kern/133218 net [carp] [hang] use of carp(4) causes system to freeze f kern/133213 net arp and sshd errors on 7.1-PRERELEASE o kern/133204 net [msk] msk driver timeouts o kern/133060 net [ipsec] [pfsync] [panic] Kernel panic with ipsec + pfs o kern/132991 net [bge] if_bge low performance problem f bin/132911 net ip6fw(8): argument type of fill_icmptypes is wrong and o kern/132889 net [ndis] [panic] NDIS kernel crash on load BCM4321 AGN d o kern/132885 net [wlan] 802.1x broken after SVN rev 189592 o conf/132851 net [fib] [patch] allow to setup fib for service running f o kern/132832 net [netinet] [patch] tcp_output() might generate invalid o bin/132798 net [patch] ggatec(8): ggated/ggatec connection slowdown p o kern/132734 net [ifmib] [panic] panic in net/if_mib.c o kern/132722 net [ath] Wifi ath0 associates fine with AP, but DHCP or I o kern/132705 net [libwrap] [patch] libwrap - infinite loop if hosts.all o kern/132672 net [ndis] [panic] ndis with rt2860.sys causes kernel pani o kern/132669 net [xl] 3c905-TX send DUP! in reply on ping (sometime) o kern/132554 net [ipl] There is no ippool start script/ipfilter magic t o kern/132354 net [nat] Getting some packages to ipnat(8) causes crash o kern/132285 net [carp] alias gives incorrect hash in dmesg o kern/132277 net [crypto] [ipsec] poor performance using cryptodevice f o kern/132107 net [carp] carp(4) advskew setting ignored when carp IP us o kern/131781 net [ndis] ndis keeps dropping the link o kern/131776 net [wi] driver fails to init o kern/131753 net [altq] [panic] kernel panic in hfsc_dequeue o bin/131567 net [socket] [patch] Update for regression/sockets/unix_cm o kern/131549 net ifconfig(8) can't clear 'monitor' mode on the wireless o kern/131536 net [netinet] [patch] kernel does allow manipulation of su o bin/131365 net route(8): route add changes interpretation of network o kern/131162 net [ath] Atheros driver bugginess and kernel crashes o kern/131153 net [iwi] iwi doesn't see a wireless network f kern/131087 net [ipw] [panic] ipw / iwi - no sent/received packets; iw f kern/130820 net [ndis] wpa_supplicant(8) returns 'no space on device' o kern/130628 net [nfs] NFS / rpc.lockd deadlock on 7.1-R o conf/130555 net [rc.d] [patch] No good way to set ipfilter variables a o kern/130525 net [ndis] [panic] 64 bit ar5008 ndisgen-erated driver cau o kern/130311 net [wlan_xauth] [panic] hostapd restart causing kernel pa o kern/130109 net [ipfw] Can not set fib for packets originated from loc f kern/130059 net [panic] Leaking 50k mbufs/hour o kern/129750 net [ath] Atheros AR5006 exits on "cannot map register spa f kern/129719 net [nfs] [panic] Panic during shutdown, tcp_ctloutput: in o kern/129580 net [ndis] Netgear WG311v3 (ndis) causes kenel trap at boo o kern/129517 net [ipsec] [panic] double fault / stack overflow o kern/129508 net [carp] [panic] Kernel panic with EtherIP (may be relat o kern/129352 net [xl] [patch] xl0 watchdog timeout o kern/129219 net [ppp] Kernel panic when using kernel mode ppp o kern/129197 net [panic] 7.0 IP stack related panic o kern/129135 net [vge] vge driver on a VIA mini-ITX not working o bin/128954 net ifconfig(8) deletes valid routes o kern/128917 net [wpi] [panic] if_wpi and wpa+tkip causing kernel panic o kern/128884 net [msk] if_msk page fault while in kernel mode o kern/128840 net [igb] page fault under load with igb/LRO o bin/128602 net [an] wpa_supplicant(8) crashes with an(4) o kern/128598 net [bluetooth] WARNING: attempt to net_add_domain(bluetoo o kern/128448 net [nfs] 6.4-RC1 Boot Fails if NFS Hostname cannot be res o conf/128334 net [request] use wpa_cli in the "WPA DHCP" situation o bin/128295 net [patch] ifconfig(8) does not print TOE4 or TOE6 capabi o bin/128001 net wpa_supplicant(8), wlan(4), and wi(4) issues o kern/127928 net [tcp] [patch] TCP bandwidth gets squeezed every time t o kern/127834 net [ixgbe] [patch] wrong error counting o kern/127826 net [iwi] iwi0 driver has reduced performance and connecti o kern/127815 net [gif] [patch] if_gif does not set vlan attributes from o kern/127724 net [rtalloc] rtfree: 0xc5a8f870 has 1 refs f bin/127719 net [arp] arp: Segmentation fault (core dumped) s kern/127587 net [bge] [request] if_bge(4) doesn't support BCM576X fami f kern/127528 net [icmp]: icmp socket receives icmp replies not owned by o bin/127192 net routed(8) removes the secondary alias IP of interface f kern/127145 net [wi]: prism (wi) driver crash at bigger traffic o kern/127102 net [wpi] Intel 3945ABG low throughput o kern/127057 net [udp] Unable to send UDP packet via IPv6 socket to IPv o kern/127050 net [carp] ipv6 does not work on carp interfaces [regressi o kern/126945 net [carp] CARP interface destruction with ifconfig destro o kern/126924 net [an] [patch] printf -> device_printf and simplify prob o kern/126895 net [patch] [ral] Add antenna selection (marked as TBD) o kern/126874 net [vlan]: Zebra problem if ifconfig vlanX destroy o bin/126822 net wpa_supplicant(8): WPA PSK does not work in adhoc mode o kern/126714 net [carp] CARP interface renaming makes system no longer o kern/126695 net rtfree messages and network disruption upon use of if_ o kern/126688 net [ixgbe] [patch] 1.4.7 ixgbe driver panic with 4GB and o kern/126475 net [ath] [panic] ath pcmcia card inevitably panics under o kern/126339 net [ipw] ipw driver drops the connection o kern/126214 net [ath] txpower problem with Atheros wifi card o kern/126075 net [inet] [patch] internet control accesses beyond end of o bin/125922 net [patch] Deadlock in arp(8) o kern/125920 net [arp] Kernel Routing Table loses Ethernet Link status o kern/125845 net [netinet] [patch] tcp_lro_rx() should make use of hard o kern/125816 net [carp] [if_bridge] carp stuck in init when using bridg f kern/125502 net [ral] ifconfig ral0 scan produces no output unless in o kern/125258 net [socket] socket's SO_REUSEADDR option does not work o kern/125239 net [gre] kernel crash when using gre o kern/124767 net [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 net [ieee80211] net80211 discards power-save queue packets o kern/124341 net [ral] promiscuous mode for wireless device ral0 looses o kern/124160 net [libc] connect(2) function loops indefinitely o kern/124127 net [msk] watchdog timeout (missed Tx interrupts) -- recov o kern/124021 net [ip6] [panic] page fault in nd6_output() o kern/123968 net [rum] [panic] rum driver causes kernel panic with WPA. p kern/123961 net [vr] [patch] Allow vr interface to handle vlans o kern/123892 net [tap] [patch] No buffer space available o kern/123890 net [ppp] [panic] crash & reboot on work with PPP low-spee o kern/123858 net [stf] [patch] stf not usable behind a NAT o kern/123796 net [ipf] FreeBSD 6.1+VPN+ipnat+ipf: port mapping does not o bin/123633 net ifconfig(8) doesn't set inet and ether address in one f kern/123617 net [tcp] breaking connection when client downloading file o kern/123603 net [tcp] tcp_do_segment and Received duplicate SYN o kern/123559 net [iwi] iwi periodically disassociates/associates [regre o bin/123465 net [ip6] route(8): route add -inet6 -interfac o kern/123463 net [ipsec] [panic] repeatable crash related to ipsec-tool o kern/123429 net [nfe] [hang] "ifconfig nfe up" causes a hard system lo o kern/123347 net [bge] bge1: watchdog timeout -- linkstate changed to D o conf/123330 net [nsswitch.conf] Enabling samba wins in nsswitch.conf c o kern/123256 net [wpi] panic: blockable sleep lock with wpi(4) f kern/123172 net [bce] Watchdog timeout problems with if_bce o kern/123160 net [ip] Panic and reboot at sysctl kern.polling.enable=0 o kern/122989 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/122954 net [lagg] IPv6 EUI64 incorrectly chosen for lagg devices o kern/122928 net [em] interface watchdog timeouts and stops receiving p f kern/122839 net [multicast] FreeBSD 7 multicast routing problem o kern/122780 net [lagg] tcpdump on lagg interface during high pps wedge o kern/122772 net [em] em0 taskq panic, tcp reassembly bug causes radix o kern/122743 net [mbuf] [panic] vm_page_unwire: invalid wire count: 0 o kern/122697 net [ath] Atheros card is not well supported o kern/122685 net It is not visible passing packets in tcpdump(1) o kern/122551 net [bge] Broadcom 5715S no carrier on HP BL460c blade usi o kern/122319 net [wi] imposible to enable ad-hoc demo mode with Orinoco o kern/122290 net [netgraph] [panic] Netgraph related "kmem_map too smal o kern/122195 net [ed] Alignment problems in if_ed o kern/122058 net [em] [panic] Panic on em1: taskq o kern/122033 net [ral] [lor] Lock order reversal in ral0 at bootup [reg o bin/121895 net [patch] rtsol(8)/rtsold(8) doesn't handle managed netw o kern/121872 net [wpi] driver fails to attach on a fujitsu-siemens s711 s kern/121774 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/121706 net [netinet] [patch] "rtfree: 0xc4383870 has 1 refs" emit o kern/121624 net [em] [regression] Intel em WOL fails after upgrade to o kern/121555 net [panic] Fatal trap 12: current process = 12 (swi1: net o kern/121443 net [gif] [lor] icmp6_input/nd6_lookup o kern/121437 net [vlan] Routing to layer-2 address does not work on VLA o bin/121359 net [patch] ppp(8): fix local stack overflow in ppp o kern/121298 net [em] [panic] Fatal trap 12: page fault while in kernel o kern/121257 net [tcp] TSO + natd -> slow outgoing tcp traffic o kern/121181 net [panic] Fatal trap 3: breakpoint instruction fault whi o kern/121080 net [bge] IPv6 NUD problem on multi address config on bge0 o kern/120966 net [rum] kernel panic with if_rum and WPA encryption p docs/120945 net [patch] ip6(4) man page lacks documentation for TCLASS o kern/120566 net [request]: ifconfig(8) make order of arguments more fr o kern/120304 net [netgraph] [patch] netgraph source assumes 32-bit time o kern/120266 net [udp] [panic] gnugk causes kernel panic when closing U o kern/120232 net [nfe] [patch] Bring in nfe(4) to RELENG_6 o kern/120130 net [carp] [panic] carp causes kernel panics in any conste o bin/120060 net routed(8) deletes link-level routes in the presence of o kern/119945 net [rum] [panic] rum device in hostap mode, cause kernel o kern/119791 net [nfs] UDP NFS mount of aliased IP addresses from a Sol o kern/119617 net [nfs] nfs error on wpa network when reseting/shutdown f kern/119516 net [ip6] [panic] _mtx_lock_sleep: recursed on non-recursi o kern/119432 net [arp] route add -host -iface causes arp e o kern/119225 net [wi] 7.0-RC1 no carrier with Prism 2.5 wifi card [regr a bin/118987 net ifconfig(8): ifconfig -l (address_family) does not wor o sparc/118932 net [panic] 7.0-BETA4/sparc-64 kernel panic in rip_output a kern/118879 net [bge] [patch] bge has checksum problems on the 5703 ch o kern/118727 net [netgraph] [patch] [request] add new ng_pf module a kern/118238 net [bce] [patch] bce driver shows "no carrier" on Intel S s kern/117717 net [panic] Kernel panic with Bittorrent client. o kern/117448 net [carp] 6.2 kernel crash [regression] o kern/117423 net [vlan] Duplicate IP on different interfaces o bin/117339 net [patch] route(8): loading routing management commands o kern/117271 net [tap] OpenVPN TAP uses 99% CPU on releng_6 when if_tap o kern/117043 net [em] Intel PWLA8492MT Dual-Port Network adapter EEPROM o kern/116837 net [tun] [panic] [patch] ifconfig tunX destroy: panic o kern/116747 net [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile o bin/116643 net [patch] [request] fstat(1): add INET/INET6 socket deta o kern/116185 net [iwi] if_iwi driver leads system to reboot o kern/115239 net [ipnat] panic with 'kmem_map too small' using ipnat o kern/115019 net [netgraph] ng_ether upper hook packet flow stops on ad o kern/115002 net [wi] if_wi timeout. failed allocation (busy bit). ifco o kern/114915 net [patch] [pcn] pcn (sys/pci/if_pcn.c) ethernet driver f o kern/113895 net [xl] xl0 fails on 6.2-RELEASE but worked fine on 5.5-R o kern/113432 net [ucom] WARNING: attempt to net_add_domain(netgraph) af o kern/112722 net [ipsec] [udp] IP v4 udp fragmented packet reject o kern/112686 net [patm] patm driver freezes System (FreeBSD 6.2-p4) i38 o kern/112570 net [bge] packet loss with bge driver on BCM5704 chipset o bin/112557 net [patch] ppp(8) lock file should not use symlink name o kern/112528 net [nfs] NFS over TCP under load hangs with "impossible p o kern/111457 net [ral] ral(4) freeze o kern/110140 net [ipw] ipw fails under load o kern/109733 net [bge] bge link state issues [regression] o kern/109470 net [wi] Orinoco Classic Gold PC Card Can't Channel Hop o kern/109308 net [pppd] [panic] Multiple panics kernel ppp suspected [r o kern/109251 net [re] [patch] if_re cardbus card won't attach o bin/108895 net pppd(8): PPPoE dead connections on 6.2 [regression] o kern/108542 net [bce] Huge network latencies with 6.2-RELEASE / STABLE o kern/107944 net [wi] [patch] Forget to unlock mutex-locks o kern/107850 net [bce] bce driver link negotiation is faulty o conf/107035 net [patch] bridge(8): bridge interface given in rc.conf n o kern/106438 net [ipf] ipfilter: keep state does not seem to allow repl o kern/106316 net [dummynet] dummynet with multipass ipfw drops packets o kern/106243 net [nve] double fault panic in if_nve.c on high loads o kern/105945 net Address can disappear from network interface s kern/105943 net Network stack may modify read-only mbuf chain copies o bin/105925 net problems with ifconfig(8) and vlan(4) [regression] o kern/105348 net [ath] ath device stopps TX o kern/104851 net [inet6] [patch] On link routes not configured when usi o kern/104751 net [netgraph] kernel panic, when getting info about my tr o kern/104485 net [bge] Broadcom BCM5704C: Intermittent on newer chip ve o kern/103191 net Unpredictable reboot o kern/103135 net [ipsec] ipsec with ipfw divert (not NAT) encodes a pac o conf/102502 net [netgraph] [patch] ifconfig name does't rename netgrap o kern/102035 net [plip] plip networking disables parallel port printing o kern/101948 net [ipf] [panic] Kernel Panic Trap No 12 Page Fault - cau o kern/100709 net [libc] getaddrinfo(3) should return TTL info o kern/100519 net [netisr] suggestion to fix suboptimal network polling o kern/98978 net [ipf] [patch] ipfilter drops OOW packets under 6.1-Rel o kern/98597 net [inet6] Bug in FreeBSD 6.1 IPv6 link-local DAD procedu o bin/98218 net wpa_supplicant(8) blacklist not working f bin/97392 net ppp(8) hangs instead terminating o kern/97306 net [netgraph] NG_L2TP locks after connection with failed f kern/96268 net [socket] TCP socket performance drops by 3000% if pack o kern/96030 net [bfe] [patch] Install hangs with Broadcomm 440x NIC in o kern/95519 net [ral] ral0 could not map mbuf o kern/95288 net [pppd] [tty] [panic] if_ppp panic in sys/kern/tty_subr o kern/95277 net [netinet] [patch] IP Encapsulation mask_match() return o kern/95267 net packet drops periodically appear s kern/94863 net [bge] [patch] hack to get bge(4) working on IBM e326m o kern/94162 net [bge] 6.x kenel stale with bge(4) o kern/93886 net [ath] Atheros/D-Link DWL-G650 long delay to associate f kern/93378 net [tcp] Slow data transfer in Postfix and Cyrus IMAP (wo o kern/93019 net [ppp] ppp and tunX problems: no traffic after restarti o kern/92880 net [libc] [patch] almost rewritten inet_network(3) functi f kern/92552 net A serious bug in most network drivers from 5.X to 6.X s kern/92279 net [dc] Core faults everytime I reboot, possible NIC issu o kern/92090 net [bge] bge0: watchdog timeout -- resetting o kern/91859 net [ndis] if_ndis does not work with Asus WL-138 s kern/91777 net [ipf] [patch] wrong behaviour with skip rule inside an o kern/91594 net [em] FreeBSD > 5.4 w/ACPI fails to detect Intel Pro/10 o kern/91364 net [ral] [wep] WF-511 RT2500 Card PCI and WEP o kern/91311 net [aue] aue interface hanging o kern/90890 net [vr] Problems with network: vr0: tx shutdown timeout s kern/90086 net [hang] 5.4p8 on supermicro P8SCT hangs during boot if f kern/88082 net [ath] [panic] cts protection for ath0 causes panic o kern/87521 net [ipf] [panic] using ipfilter "auth" keyword leads to k o kern/87506 net [vr] [patch] Fix alias support on vr interfaces s kern/86920 net [ndis] ifconfig: SIOCS80211: Invalid argument [regress o kern/86103 net [ipf] Illegal NAT Traversal in IPFilter o kern/85780 net 'panic: bogus refcnt 0' in routing/ipv6 o bin/85445 net ifconfig(8): deprecated keyword to ifconfig inoperativ o kern/85266 net [xe] [patch] xe(4) driver does not recognise Xircom XE o kern/84202 net [ed] [patch] Holtek HT80232 PCI NIC recognition on Fre o bin/82975 net route change does not parse classfull network as given o kern/82497 net [vge] vge(4) on AMD64 only works when loaded late, not f kern/81644 net [vge] vge(4) does not work properly when loaded as a K s kern/81147 net [net] [patch] em0 reinitialization while adding aliase o kern/80853 net [ed] [patch] add support for Compex RL2000/ISA in PnP o kern/79895 net [ipf] 5.4-RC2 breaks ipfilter NAT when using netgraph f kern/79262 net [dc] Adaptec ANA-6922 not fully supported o bin/79228 net [patch] extend arp(8) to be able to create blackhole r o kern/78090 net [ipf] ipf filtering on bridged packets doesn't work if p kern/77913 net [wi] [patch] Add the APDL-325 WLAN pccard to wi(4) o kern/77341 net [ip6] problems with IPV6 implementation o kern/77273 net [ipf] ipfilter breaks ipv6 statefull filtering on 5.3 s kern/77195 net [ipf] [patch] ipfilter ioctl SIOCGNATL does not match o kern/75873 net Usability problem with non-RFC-compliant IP spoof prot s kern/75407 net [an] an(4): no carrier after short time f kern/73538 net [bge] problem with the Broadcom BCM5788 Gigabit Ethern o kern/71469 net default route to internet magically disappears with mu o kern/70904 net [ipf] ipfilter ipnat problem with h323 proxy support o kern/64556 net [sis] [patch] if_sis short cable fix problems with Net s kern/60293 net [patch] FreeBSD arp poison patch o kern/54383 net [nfs] [patch] NFS root configurations without dynamic f i386/45773 net [bge] Softboot causes autoconf failure on Broadcom 570 s bin/41647 net ifconfig(8) doesn't accept lladdr along with inet addr s kern/39937 net ipstealth issue a kern/38554 net [patch] changing interface ipaddress doesn't seem to w o kern/35442 net [sis] [patch] Problem transmitting runts in if_sis dri o kern/34665 net [ipf] [hang] ipfilter rcmd proxy "hangs". o kern/31647 net [libc] socket calls can return undocumented EINVAL o kern/30186 net [libc] getaddrinfo(3) does not handle incorrect servna o kern/27474 net [ipf] [ppp] Interactive use of user PPP and ipfilter c o conf/23063 net [arp] [patch] for static ARP tables in rc.network 356 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Oct 26 15:53:04 2009 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 D6D7E10656BB; Mon, 26 Oct 2009 15:52:54 +0000 (UTC) (envelope-from freebsd@levsha.org.ua) Received: from expo.ukrweb.net (mail.univua.net [91.202.128.78]) by mx1.freebsd.org (Postfix) with ESMTP id 890C48FC27; Mon, 26 Oct 2009 15:52:54 +0000 (UTC) Received: from levsha by expo.ukrweb.net with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1N2RDh-000NqT-HJ; Mon, 26 Oct 2009 17:10:53 +0200 Date: Mon, 26 Oct 2009 17:10:53 +0200 From: Mykola Dzham To: Bernhard Schmidt Message-ID: <20091026151053.GZ93554@expo.ukrweb.net> References: <20091009170839.142800@gmx.net> <4ad871310910211751t31b17133kf994728b2cbf2b39@mail.gmail.com> <200910240014.58690.bschmidt@techwires.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200910240014.58690.bschmidt@techwires.net> X-Operating-System: FreeBSD/7.0-STABLE (i386) User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Brandon Gooch , freebsd-net@freebsd.org, Rui Paulo , David Horn , Glen Barber Subject: Re: Intel WiFi 5100/5300 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, 26 Oct 2009 15:53:04 -0000 Bernhard Schmidt wrote: > Hi, > > Update: > > * iwnfw has now been split into individual modules so autoloading of firmware > module(s) does work again. > * Changes have been made to RUN -> AUTH transition, this should fix the issue > reported by Glen and others. > * Brandon reported issues in iwn_cmd() with large commands, those have been > fixed to. > * DEAUTH is now handled correctly. > > http://techwires.net/~bschmidt/patches/freebsd/iwn/iwn-20091024.tar.gz > or > http://techwires.net/~bschmidt/patches/freebsd/iwn/sys/ My 9.0-CURRENT r198465M amd64 crashes immediately after loading if_iwn Backtrace from core: (kgdb) bt #0 doadump () at pcpu.h:223 #1 0xffffffff8016e35c in db_fncall (dummy1=Variable "dummy1" is not available. ) at /usr/local/arch/src/sys/ddb/db_command.c:548 #2 0xffffffff8016e691 in db_command (last_cmdp=0xffffffff805cff60, cmd_table=Variable "cmd_table" is not available. ) at /usr/local/arch/src/sys/ddb/db_command.c:445 #3 0xffffffff8016e8e0 in db_command_loop () at /usr/local/arch/src/sys/ddb/db_command.c:498 #4 0xffffffff801708b9 in db_trap (type=Variable "type" is not available. ) at /usr/local/arch/src/sys/ddb/db_main.c:229 #5 0xffffffff80232ab5 in kdb_trap (type=12, code=0, tf=0xffffff807923ea10) at /usr/local/arch/src/sys/kern/subr_kdb.c:535 #6 0xffffffff803dad8d in trap_fatal (frame=0xffffff807923ea10, eva=Variable "eva" is not available. ) at /usr/local/arch/src/sys/amd64/amd64/trap.c:855 #7 0xffffffff803dba35 in trap (frame=0xffffff807923ea10) at /usr/local/arch/src/sys/amd64/amd64/trap.c:348 #8 0xffffffff803c13a3 in calltrap () at /usr/local/arch/src/sys/amd64/amd64/exception.S:224 #9 0xffffffff803bba81 in _bus_dmamap_sync (dmat=0xffffff011008cd00, map=Variable "map" is not available. ) at /usr/local/arch/src/sys/amd64/amd64/busdma_machdep.c:933 #10 0xffffffff80ed86ae in iwn_notif_intr () from /boot/kernel/if_iwn.ko #11 0xffffffff80ed8bf5 in iwn_intr () from /boot/kernel/if_iwn.ko #12 0xffffff0110038780 in ?? () #13 0x0000000000000000 in ?? () #14 0xffffff00312a9c00 in ?? () #15 0xffffff00312a9c48 in ?? () #16 0xffffff00312a9ca8 in ?? () #17 0xffffff807923ebd0 in ?? () #18 0xffffffff801ddbb6 in intr_event_execute_handlers (p=Variable "p" is not available. ) at /usr/local/arch/src/sys/kern/kern_intr.c:1220 Previous frame inner to this frame (corrupt stack?) (kgdb) Full crashinfo is on http://levsha.me/crash/iwn/core.20091025.txt -- LEFT-(UANIC|RIPE) JID: levsha@jabber.net.ua PGP fingerprint: 1BCD 7C80 2E04 7282 C944 B0E0 7E67 619E 4E72 9280 From owner-freebsd-net@FreeBSD.ORG Mon Oct 26 16:11:32 2009 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 86573106566B for ; Mon, 26 Oct 2009 16:11:32 +0000 (UTC) (envelope-from kalin@el.net) Received: from mail.el.net (mail.el.net [74.1.12.120]) by mx1.freebsd.org (Postfix) with ESMTP id 11B298FC14 for ; Mon, 26 Oct 2009 16:11:31 +0000 (UTC) Received: (qmail 44150 invoked by uid 1008); 26 Oct 2009 17:25:29 -0000 Received: from unknown (HELO kalins-macbook-pro.local) (kalin@el.net@24.193.246.51) by mail.el.net with ESMTPA; 26 Oct 2009 17:25:29 -0000 Message-ID: <4AE5C99B.2000102@el.net> Date: Mon, 26 Oct 2009 12:08:59 -0400 From: kalin m User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: pyunyh@gmail.com References: <4AE2780F.4080600@el.net> <20091024214640.GE6050@michelle.cdnetworks.com> <20091024215219.GF6050@michelle.cdnetworks.com> In-Reply-To: <20091024215219.GF6050@michelle.cdnetworks.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re: Marvell 88E8057 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, 26 Oct 2009 16:11:32 -0000 Pyun YongHyeon wrote: > On Sat, Oct 24, 2009 at 02:46:40PM -0700, Pyun YongHyeon wrote: > >> On Fri, Oct 23, 2009 at 11:44:15PM -0400, kalin m wrote: >> >>> hi all.. >>> >>> does anybody here know if freebsd has a driver for Marvell 88E8057 nic chip? >>> >>> according to the kernel list of drivers (7.2) marvell chips are driven >>> by the msk driver. but it doesn't show up in pciconf, dmesg or >>> sysinstall.... >>> strangely enough 88E8057 is not in the list in man msk. although 88E8056 >>> and 88E8058 are. is this just bad luck?! >>> >>> >> I think 88E8057(Yukon Ultra 2) is the latest chipset from Marvell >> and no one ever expressed his/her willingness to try experiment >> patch. I guess msk(4) in HEAD has all required features to support >> 88E8057. Would you try attached patch? >> >> The patch was generated against HEAD. If you have to use 7.2-RELEASE >> copy the following files from HEAD and apply attached patch. >> >> /usr/src/sys/dev/msk/if_msk.c >> /usr/src/sys/dev/msk/if_mskreg.h >> /usr/src/sys/dev/mii/miidevs >> /usr/src/sys/dev/mii/e1000phy.c >> /usr/src/sys/dev/mii/e1000phyreg.c >> > ^^^^^^^^^^^^^^ > It should be read e1000phyreg.h > hi there Pyun YongHyeon... i stillhave not gotten you previous email with the attached patch. can you resend please? thanks..... From owner-freebsd-net@FreeBSD.ORG Mon Oct 26 17:45:52 2009 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 03D521065762 for ; Mon, 26 Oct 2009 17:45:52 +0000 (UTC) (envelope-from fbsdlists@gmail.com) Received: from mail-pz0-f202.google.com (mail-pz0-f202.google.com [209.85.222.202]) by mx1.freebsd.org (Postfix) with ESMTP id D183D8FC08 for ; Mon, 26 Oct 2009 17:45:51 +0000 (UTC) Received: by pzk40 with SMTP id 40so7695356pzk.7 for ; Mon, 26 Oct 2009 10:45:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=rGgc2HRcHoFLxFsF5WT0JdKufzySJz8GFL66W/1Nlqc=; b=FuvOSkHOLEAaQcs3aqv2cPUV4Kdz75w79K8Wux0Iy2b0cPvf6aGBjfeLjs3jBGd6nR VyGm+RNP6NDJHKXCNHiqpVWbkAf55EpbXXZ4PzylHgS2iy41pPfeXYuhK5YQ2IiT0AyP Zy7xofIlq5HGBFFMJ/UJ2Zjo3baWved1RxMO4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=FBQMaIIoK7ESWDEvB3bJMLLFbiiY1XZTLjHsUZDxSOHH6M91rwdEZIj8LqYTZHKiRC N4p86ZGMTpOma3SakLQ15pJ0kIaGJmHOO37cwsZW8NS2CszrglJAxGX83hg/wB9teVma pc2FVN/CI8oY6TpiOyV/4TUNWjJtk3xysiIJk= MIME-Version: 1.0 Received: by 10.142.67.39 with SMTP id p39mr1202390wfa.204.1256577332301; Mon, 26 Oct 2009 10:15:32 -0700 (PDT) In-Reply-To: <4AE2780F.4080600@el.net> References: <4AE2780F.4080600@el.net> Date: Mon, 26 Oct 2009 13:15:32 -0400 Message-ID: <54db43990910261015k239933e0l3528d463d8cf7f50@mail.gmail.com> From: Bob Johnson To: kalin m Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org Subject: Re: Marvell 88E8057 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, 26 Oct 2009 17:45:52 -0000 On 10/23/09, kalin m wrote: > > hi all.. > > does anybody here know if freebsd has a driver for Marvell 88E8057 nic chip? > Marvell provides FreeBSD drivers. If you don't have a philosophical objection to using a manufacturer's binary driver, you might find what you need at their website. http://www.marvell.com/drivers/search.do I think they provide one FreeBSD driver for all of their chipsets. Don't know if it supports the 88E8057. -- -- Bob Johnson fbsdlists@gmail.com From owner-freebsd-net@FreeBSD.ORG Mon Oct 26 17:51:24 2009 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 0E7411065679 for ; Mon, 26 Oct 2009 17:51:24 +0000 (UTC) (envelope-from kalin@el.net) Received: from mail.el.net (mail.el.net [74.1.12.120]) by mx1.freebsd.org (Postfix) with ESMTP id B0E2A8FC08 for ; Mon, 26 Oct 2009 17:51:23 +0000 (UTC) Received: (qmail 60195 invoked by uid 1008); 26 Oct 2009 19:05:22 -0000 Received: from unknown (HELO kalins-macbook-pro.local) (kalin@el.net@74.1.12.115) by mail.el.net with ESMTPA; 26 Oct 2009 19:05:22 -0000 Message-ID: <4AE5E104.2010302@el.net> Date: Mon, 26 Oct 2009 13:48:52 -0400 From: kalin m User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Bob Johnson References: <4AE2780F.4080600@el.net> <54db43990910261015k239933e0l3528d463d8cf7f50@mail.gmail.com> In-Reply-To: <54db43990910261015k239933e0l3528d463d8cf7f50@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re: Marvell 88E8057 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, 26 Oct 2009 17:51:24 -0000 Bob Johnson wrote: > On 10/23/09, kalin m wrote: > >> hi all.. >> >> does anybody here know if freebsd has a driver for Marvell 88E8057 nic chip? >> >> > > Marvell provides FreeBSD drivers. If you don't have a philosophical > objection to using a manufacturer's binary driver, you might find what > you need at their website. > > http://www.marvell.com/drivers/search.do > > I think they provide one FreeBSD driver for all of their chipsets. > Don't know if it supports the 88E8057. > i do. i found that page last thursday. and a saw a few freebsd drivers. but not for 88E8057. thanks thought.... From owner-freebsd-net@FreeBSD.ORG Mon Oct 26 20:35:02 2009 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 24FF71065697 for ; Mon, 26 Oct 2009 20:35:02 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from mail-bw0-f209.google.com (mail-bw0-f209.google.com [209.85.218.209]) by mx1.freebsd.org (Postfix) with ESMTP id BA6848FC12 for ; Mon, 26 Oct 2009 20:35:01 +0000 (UTC) Received: by bwz1 with SMTP id 1so2768393bwz.13 for ; Mon, 26 Oct 2009 13:35:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.143.21 with SMTP id s21mr438537fau.54.1256589300282; Mon, 26 Oct 2009 13:35:00 -0700 (PDT) From: Vlad Galu Date: Mon, 26 Oct 2009 22:34:40 +0200 Message-ID: To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: quagga ignoring RTM_DELETE messages? 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, 26 Oct 2009 20:35:02 -0000 Hi list, sorry for the noise here. I'm experiencing a weird issue with the latest Quagga from ports, on a 8.0-RC1. It was configured to redistribute kernel routes to BGP, which it does. However, when a route is deleted, it's still announced to the BGP peer. RTM_DELETE was picked up by "route monitor"... This exact same setup used to work before upgrading to RELENG_8. Am I missing something? Thanks, Vlad From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 00:01:31 2009 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 36E08106568F; Tue, 27 Oct 2009 00:01:31 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id C4E8F8FC08; Tue, 27 Oct 2009 00:01:30 +0000 (UTC) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.14.3/jtpda-5.4) with ESMTP id n9QNk2XY049171 ; Tue, 27 Oct 2009 00:46:02 +0100 (CET) X-Ids: 165 Received: from heho.snv.jussieu.fr (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.14.3/8.14.3) with ESMTP id n9QNk1AO075048; Tue, 27 Oct 2009 00:46:01 +0100 (CET) (envelope-from arno@heho.snv.jussieu.fr) Received: (from arno@localhost) by heho.snv.jussieu.fr (8.14.3/8.14.3/Submit) id n9QNk0nx075045; Tue, 27 Oct 2009 00:46:00 +0100 (CET) (envelope-from arno) To: freebsd-fs@freebsd.org From: "Arno J. Klaassen" Date: Tue, 27 Oct 2009 00:46:00 +0100 Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: ClamAV 0.94.2/9944/Mon Oct 26 22:00:04 2009 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at jchkmail2.jussieu.fr with ID 4AE634BA.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 4AE634BA.000/134.157.184.22/heho.snv.jussieu.fr/heho.snv.jussieu.fr/ Cc: freebsd-net@freebsd.org Subject: ZFS and 'traditional' nfs-export 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, 27 Oct 2009 00:01:31 -0000 Hello, I googled a bit on this question but could not find a clear answer : is there any risk/inconvenience/advantage in exporting a ZFS-fs by just putting it in /etc/exports the old way and leaving the 'sharenfs' option on the filesystem off? I'd like to replace a UFS-based server serving mostly linux-clients which work well now with a ZFS-fs, and somehow am a bit waterfearing changing the nfs=E8options which worked great till now. Thank you in advance, regards, Arno From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 17:27:45 2009 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 8B5E4106566C for ; Tue, 27 Oct 2009 17:27:45 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from tomjudge.vm.bytemark.co.uk (tomjudge.vm.bytemark.co.uk [80.68.91.100]) by mx1.freebsd.org (Postfix) with ESMTP id 4C5708FC1B for ; Tue, 27 Oct 2009 17:27:45 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 903BE48A75; Tue, 27 Oct 2009 17:09:27 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at tomjudge.vm.bytemark.co.uk Received: from tomjudge.vm.bytemark.co.uk ([127.0.0.1]) by localhost (tomjudge.vm.bytemark.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X-QaRiVZbto3; Tue, 27 Oct 2009 17:09:22 +0000 (GMT) Received: from rita.nodomain (unknown [192.168.205.6]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 5F41848A74; Tue, 27 Oct 2009 17:09:21 +0000 (GMT) Message-ID: <4AE72910.8090708@tomjudge.com> Date: Tue, 27 Oct 2009 17:08:32 +0000 From: Tom Judge User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "pyunyh@gmail.com" , rwilliams@borderware.com, David Christensen , Xin LI , Stanislav Sedov Subject: bce(4) BCM5907 CTX write errors on 7.2 driver 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, 27 Oct 2009 17:27:45 -0000 Hi, Has anyone seen these errors before: http://www.freebsd.org/cgi/query-pr.cgi?pr=135836&cat= The system is a Dell R610 and it happens on both cold and warm boots. I am about to check a second chassis, and test with 8, and will follow up after my tests. Tom From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 18:44:43 2009 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 CAA69106566C for ; Tue, 27 Oct 2009 18:44:43 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from mail-bw0-f209.google.com (mail-bw0-f209.google.com [209.85.218.209]) by mx1.freebsd.org (Postfix) with ESMTP id 567968FC1E for ; Tue, 27 Oct 2009 18:44:43 +0000 (UTC) Received: by bwz1 with SMTP id 1so26220bwz.13 for ; Tue, 27 Oct 2009 11:44:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.6.9 with SMTP id 9mr2799360fax.84.1256669082212; Tue, 27 Oct 2009 11:44:42 -0700 (PDT) In-Reply-To: References: From: Vlad Galu Date: Tue, 27 Oct 2009 20:44:22 +0200 Message-ID: To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: quagga ignoring RTM_DELETE messages? 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, 27 Oct 2009 18:44:43 -0000 On Mon, Oct 26, 2009 at 10:34 PM, Vlad Galu wrote: > Hi list, sorry for the noise here. > > I'm experiencing a weird issue with the latest Quagga from ports, on a > 8.0-RC1. It was configured to redistribute kernel routes to BGP, which > it does. However, when a route is deleted, it's still announced to the > BGP peer. RTM_DELETE was picked up by "route monitor"... This exact > same setup used to work before upgrading to RELENG_8. Am I missing > something? > > Thanks, > Vlad > So, everybody happy with Quagga + RELENG_8? From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 18:50:47 2009 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 6D76F1065670 for ; Tue, 27 Oct 2009 18:50:47 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by mx1.freebsd.org (Postfix) with ESMTP id 39B5D8FC1F for ; Tue, 27 Oct 2009 18:50:47 +0000 (UTC) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.14.3/8.14.3) with ESMTP id n9RIoiVD004770; Tue, 27 Oct 2009 14:50:44 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <200910271850.n9RIoiVD004770@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 27 Oct 2009 14:50:52 -0400 To: Vlad Galu , freebsd-net@freebsd.org From: Mike Tancsa In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: Subject: Re: quagga ignoring RTM_DELETE messages? 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, 27 Oct 2009 18:50:47 -0000 At 02:44 PM 10/27/2009, Vlad Galu wrote: >On Mon, Oct 26, 2009 at 10:34 PM, Vlad Galu wrote: > > Hi list, sorry for the noise here. > > > > I'm experiencing a weird issue with the latest Quagga from ports, on a > > 8.0-RC1. It was configured to redistribute kernel routes to BGP, which > > it does. However, when a route is deleted, it's still announced to the > > BGP peer. RTM_DELETE was picked up by "route monitor"... This exact > > same setup used to work before upgrading to RELENG_8. Am I missing > > something? > > > > Thanks, > > Vlad > > > >So, everybody happy with Quagga + RELENG_8? I havent tried it yet. Can you post your quagga config and I will try and recreate here on my RELENG_8 test box. ---Mike >_______________________________________________ >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" -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 19:32:35 2009 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 C92081065676; Tue, 27 Oct 2009 19:32:35 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) by mx1.freebsd.org (Postfix) with ESMTP id 96B2C8FC34; Tue, 27 Oct 2009 19:32:35 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=lerami; d=lerctr.org; h=Received:From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language:X-Spam-Score:X-LERCTR-Spam-Score:X-Spam-Report:X-LERCTR-Spam-Report:DomainKey-Status; b=tT1wgu5YDDPTWn/vwasFXgROXzSizFTimLVgl+sV8oy9wag8D30TyJhePoEGMpImepAtuALsfSamJkTeQdFUAVpdXpe9Wuu+n8I5cPHwe98MciQL0F86PAnABnFqijvk9bNpd0HTh1XNmvANjmT5YUEC28uApMlMq7syp7sKGAo=; Received: from 64.3.1.253.ptr.us.xo.net ([64.3.1.253]:25890 helo=LROSENMAN) by thebighonker.lerctr.org with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1N2rTx-000NjV-1y; Tue, 27 Oct 2009 14:13:26 -0500 From: "Larry Rosenman" To: "'Arno J. Klaassen'" , References: In-Reply-To: Date: Tue, 27 Oct 2009 14:13:14 -0500 Message-ID: <00b301ca5739$8e9b3850$abd1a8f0$@org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcpWmLxwrIIYd6LzRmiquNBtjbXfxgAoKxag Content-Language: en-us X-Spam-Score: -2.3 (--) X-LERCTR-Spam-Score: -2.3 (--) X-Spam-Report: SpamScore (-2.3/5.0) ALL_TRUSTED=-1.8, BAYES_00=-2.599, SARE_SUB_OBFU_OTHER=0.135, TVD_RCVD_IP=1.931 X-LERCTR-Spam-Report: SpamScore (-2.3/5.0) ALL_TRUSTED=-1.8, BAYES_00=-2.599, SARE_SUB_OBFU_OTHER=0.135, TVD_RCVD_IP=1.931 DomainKey-Status: no signature Cc: freebsd-net@freebsd.org Subject: RE: ZFS and 'traditional' nfs-export 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, 27 Oct 2009 19:32:35 -0000 ZFS makes its own version of the exports file. Just do it that way, and be safe. You can pass the full set of NFS options in the sharenfs parameter.... --=20 Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 -----Original Message----- From: owner-freebsd-net@freebsd.org = [mailto:owner-freebsd-net@freebsd.org] On Behalf Of Arno J. Klaassen Sent: Monday, October 26, 2009 6:46 PM To: freebsd-fs@freebsd.org Cc: freebsd-net@freebsd.org Subject: ZFS and 'traditional' nfs-export Hello, I googled a bit on this question but could not find a clear answer : is there any risk/inconvenience/advantage in exporting a ZFS-fs by just putting it in /etc/exports the old way and leaving the 'sharenfs' option on the filesystem off? I'd like to replace a UFS-based server serving mostly linux-clients which work well now with a ZFS-fs, and somehow am a bit waterfearing changing the nfs=E8options which worked great till now. Thank you in advance, regards, Arno _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 20:12:11 2009 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 A871A106566B for ; Tue, 27 Oct 2009 20:12:11 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from tomjudge.vm.bytemark.co.uk (tomjudge.vm.bytemark.co.uk [80.68.91.100]) by mx1.freebsd.org (Postfix) with ESMTP id 681C08FC08 for ; Tue, 27 Oct 2009 20:12:11 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 3D22348A57; Tue, 27 Oct 2009 20:12:10 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at tomjudge.vm.bytemark.co.uk Received: from tomjudge.vm.bytemark.co.uk ([127.0.0.1]) by localhost (tomjudge.vm.bytemark.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GvC-vL+XIpjC; Tue, 27 Oct 2009 20:12:06 +0000 (GMT) Received: from rita.nodomain (unknown [192.168.205.6]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id AB04048A1E; Tue, 27 Oct 2009 20:12:05 +0000 (GMT) Message-ID: <4AE753E4.6050205@tomjudge.com> Date: Tue, 27 Oct 2009 20:11:16 +0000 From: Tom Judge User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: net@freebsd.org References: <4AE72910.8090708@tomjudge.com> In-Reply-To: <4AE72910.8090708@tomjudge.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "pyunyh@gmail.com" , Xin LI , David Christensen , rwilliams@borderware.com, Stanislav Sedov Subject: Re: bce(4) BCM5907 CTX write errors on 7.2 driver 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, 27 Oct 2009 20:12:11 -0000 Tom Judge wrote: > Hi, > > Has anyone seen these errors before: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=135836&cat= > > The system is a Dell R610 and it happens on both cold and warm boots. > > I am about to check a second chassis, and test with 8, and will follow > up after my tests. > Here are my tests with 3 of the 13th Gen Dell chassis. http://www.tomjudge.com/index.php/FreeBSD/Dell_13th_Gen_Servers Summary: R710 is fine R410 is fine once you can get it to PXE load correctly R610 is no good at the moment. Tom From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 20:41:37 2009 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 41E1E1065693 for ; Tue, 27 Oct 2009 20:41:37 +0000 (UTC) (envelope-from prvs=1551678ed3=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id CAA068FC2C for ; Tue, 27 Oct 2009 20:41:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk; s=Multiplay; t=1256675446; x=1257280246; q=dns/txt; h=Received: Message-ID:From:To:Cc:References:Subject:Date:MIME-Version: Content-Type:Content-Transfer-Encoding; bh=NvTKuqohyGdp0wwj5h3xD 5bs4iPnosg9oTgCgwtCdgs=; b=YgV/fWpUXeVI7Nb6YkRqjRkqs9pgWSRRMMqwz hSefAmaQG+Z/snblga6rmXRpx4winRr21dvZSjRfL/bo/gz3/Oa1hb3DRy0Ea95+ kMH9xVUru+629X2gVqCg36Xx0bFOlW5tJCADWq1OI+CYETD46RabFGrUj8A4CBXi qDOhGk= X-MDAV-Processed: mail1.multiplay.co.uk, Tue, 27 Oct 2009 20:30:46 +0000 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v10.0.4) with ESMTP id md50008434728.msg for ; Tue, 27 Oct 2009 20:30:45 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Tue, 27 Oct 2009 20:30:45 +0000 (not processed: message from trusted or authenticated source) X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 188.220.16.96 X-Return-Path: prvs=1551678ed3=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: net@freebsd.org Message-ID: From: "Steven Hartland" To: "Tom Judge" , References: <4AE72910.8090708@tomjudge.com> <4AE753E4.6050205@tomjudge.com> Date: Tue, 27 Oct 2009 20:30:38 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5843 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Cc: pyunyh@gmail.com, rwilliams@borderware.com, David Christensen , Xin LI , Stanislav Sedov Subject: Re: bce(4) BCM5907 CTX write errors on 7.2 driver 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, 27 Oct 2009 20:41:37 -0000 M610 is also broken due to unsupported bge revision :( Regards Steve ----- Original Message ----- From: "Tom Judge" To: Cc: ; "Xin LI" ; "David Christensen" ; ; "Stanislav Sedov" Sent: Tuesday, October 27, 2009 8:11 PM Subject: Re: bce(4) BCM5907 CTX write errors on 7.2 driver > Tom Judge wrote: >> Hi, >> >> Has anyone seen these errors before: >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=135836&cat= >> >> The system is a Dell R610 and it happens on both cold and warm boots. >> >> I am about to check a second chassis, and test with 8, and will follow up after my tests. >> > > Here are my tests with 3 of the 13th Gen Dell chassis. > > http://www.tomjudge.com/index.php/FreeBSD/Dell_13th_Gen_Servers > > Summary: > > R710 is fine > R410 is fine once you can get it to PXE load correctly > > R610 is no good at the moment. > > Tom > > _______________________________________________ > 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" > ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 20:41:45 2009 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 73EFD1065745 for ; Tue, 27 Oct 2009 20:41:45 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 102FE8FC26 for ; Tue, 27 Oct 2009 20:41:44 +0000 (UTC) Received: by mail-bw0-f213.google.com with SMTP id 5so163287bwz.3 for ; Tue, 27 Oct 2009 13:41:44 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.14.83 with SMTP id f19mr1238754faa.92.1256676104445; Tue, 27 Oct 2009 13:41:44 -0700 (PDT) In-Reply-To: <200910271850.n9RIoiVD004770@lava.sentex.ca> References: <200910271850.n9RIoiVD004770@lava.sentex.ca> From: Vlad Galu Date: Tue, 27 Oct 2009 22:41:24 +0200 Message-ID: To: Mike Tancsa Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org Subject: Re: quagga ignoring RTM_DELETE messages? 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, 27 Oct 2009 20:41:45 -0000 On Tue, Oct 27, 2009 at 8:50 PM, Mike Tancsa wrote: > At 02:44 PM 10/27/2009, Vlad Galu wrote: >> >> On Mon, Oct 26, 2009 at 10:34 PM, Vlad Galu wrote: >> > Hi list, sorry for the noise here. >> > >> > I'm experiencing a weird issue with the latest Quagga from ports, on a >> > 8.0-RC1. It was configured to redistribute kernel routes to BGP, which >> > it does. However, when a route is deleted, it's still announced to the >> > BGP peer. RTM_DELETE was picked up by "route monitor"... This exact >> > same setup used to work before upgrading to RELENG_8. Am I missing >> > something? >> > >> > Thanks, >> > Vlad >> > >> >> So, everybody happy with Quagga + RELENG_8? > > I havent tried it yet. Can you post your quagga config and I will try and > recreate here on my RELENG_8 test box. > > =A0 =A0 =A0 =A0---Mike > > >> _______________________________________________ >> 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" > > -------------------------------------------------------------------- > Mike Tancsa, =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0tel +1 519 651 3400 > Sentex Communications, =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0mike@sentex.net > Providing Internet since 1994 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0www.= sentex.net > Cambridge, Ontario Canada =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= www.sentex.net/mike > > Sure Mike, thanks! Here's the bgpd.conf: -- cut here -- router bgp bgp router-id redistribute kernel neighbor remote-as neighbor next-hop-self neighbor soft-reconfiguration inbound neighbor route-map filtru out route-map filtru permit 10 set community 5483:10000 6746:10000 additive set ip next-hop 192.168.192.168 -- and here -- A sniffer runs on this machine, watching all inbound traffic for DDoS attacks, and nullroutes the attacked IP. What it actually does is to add a static route towards the attacked IP, through 127.0.0.1, with the following flags set: RTF_UP|RTF_GATEWAY|RTF_HOST|RTF_BLACKHOLE|RTF_STATIC. Then, the static route is seen by Quagga and redistributed into BGP. After a while, the monitoring software removes the static route, and Quagga used (on 7.x) to also stop announcing it to the neighbor. For some reason, this second part doesn't happen anymore, although the static route is clearly not in the routing table anymore, and "route monitor" sees the kernel's RTM_DEL message (and so should Quagga). For the record, the same setup almost works with OpenBGPD, the only difference being that I have to replace 127.0.0.1 with another reachable (directly connected) IP when setting the static route, otherwise OpenBGPD ignores it (which I suspect is due to some internal check). OpenBGPD correctly stops exporting the static route to the BGP peer once it's removed from the routing table by the monitoring software. Thanks for looking into this! From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 21:22:03 2009 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 96FD61065670 for ; Tue, 27 Oct 2009 21:22:03 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from tomjudge.vm.bytemark.co.uk (tomjudge.vm.bytemark.co.uk [80.68.91.100]) by mx1.freebsd.org (Postfix) with ESMTP id 542FE8FC14 for ; Tue, 27 Oct 2009 21:22:03 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 22FBB48A58; Tue, 27 Oct 2009 21:22:02 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at tomjudge.vm.bytemark.co.uk Received: from tomjudge.vm.bytemark.co.uk ([127.0.0.1]) by localhost (tomjudge.vm.bytemark.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X6IykLbRiq8p; Tue, 27 Oct 2009 21:21:58 +0000 (GMT) Received: from rita.nodomain (unknown [192.168.205.6]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 96F8748A4B; Tue, 27 Oct 2009 21:21:57 +0000 (GMT) Message-ID: <4AE76444.7070309@tomjudge.com> Date: Tue, 27 Oct 2009 21:21:08 +0000 From: Tom Judge User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: Steven Hartland References: <4AE72910.8090708@tomjudge.com> <4AE753E4.6050205@tomjudge.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: net@freebsd.org Subject: Re: bce(4) BCM5907 CTX write errors on 7.2 driver 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, 27 Oct 2009 21:22:03 -0000 Steven Hartland wrote: > M610 is also broken due to unsupported bge revision :( > Hi Steve, This seems to be a missing PHY driver for bce(4)+SerDes rather than a bge issue, see PR:kern/134658 You already refrenced this in a thread on current@ releated to an HP system. I have added this info to my page. Tom > ----- Original Message ----- From: "Tom Judge" > To: > Cc: ; "Xin LI" ; "David > Christensen" ; ; > "Stanislav Sedov" > Sent: Tuesday, October 27, 2009 8:11 PM > Subject: Re: bce(4) BCM5907 CTX write errors on 7.2 driver > > >> Tom Judge wrote: >>> Hi, >>> >>> Has anyone seen these errors before: >>> >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=135836&cat= >>> >>> The system is a Dell R610 and it happens on both cold and warm boots. >>> >>> I am about to check a second chassis, and test with 8, and will >>> follow up after my tests. >>> >> >> Here are my tests with 3 of the 13th Gen Dell chassis. >> >> http://www.tomjudge.com/index.php/FreeBSD/Dell_13th_Gen_Servers >> >> Summary: >> >> R710 is fine >> R410 is fine once you can get it to PXE load correctly >> >> R610 is no good at the moment. >> >> Tom >> >> _______________________________________________ >> 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" >> > > > ================================================ > This e.mail is private and confidential between Multiplay (UK) Ltd. > and the person or entity to whom it is addressed. In the event of > misdirection, the recipient is prohibited from using, copying, > printing or otherwise disseminating it or any information contained in > it. > In the event of misdirection, illegible or incomplete transmission > please telephone +44 845 868 1337 > or return the E.mail to postmaster@multiplay.co.uk. > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 21:30:04 2009 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 834861065670 for ; Tue, 27 Oct 2009 21:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 592578FC18 for ; Tue, 27 Oct 2009 21:30:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9RLU45T071518 for ; Tue, 27 Oct 2009 21:30:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9RLU4G0071513; Tue, 27 Oct 2009 21:30:04 GMT (envelope-from gnats) Date: Tue, 27 Oct 2009 21:30:04 GMT Message-Id: <200910272130.n9RLU4G0071513@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Tom Judge Cc: Subject: Re: kern/139761: [bce] bce driver on IBM HS22 [No PHY found on Child MII bus] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tom Judge List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Oct 2009 21:30:04 -0000 The following reply was made to PR kern/139761; it has been noted by GNATS. From: Tom Judge To: bug-followup@FreeBSD.org, sebastian.tymkow@gmail.com Cc: Subject: Re: kern/139761: [bce] bce driver on IBM HS22 [No PHY found on Child MII bus] Date: Tue, 27 Oct 2009 21:25:30 +0000 Hi, This seems to be a duplicate of: kern/136417 Tom From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 21:39:33 2009 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 CA824106566C for ; Tue, 27 Oct 2009 21:39:33 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id 5FE9F8FC0C for ; Tue, 27 Oct 2009 21:39:32 +0000 (UTC) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.14.3/jtpda-5.4) with ESMTP id n9RLdVgx092407 ; Tue, 27 Oct 2009 22:39:31 +0100 (CET) X-Ids: 166 Received: from heho.snv.jussieu.fr (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.14.3/8.14.3) with ESMTP id n9RLdU1Y007932; Tue, 27 Oct 2009 22:39:30 +0100 (CET) (envelope-from arno@heho.snv.jussieu.fr) Received: (from arno@localhost) by heho.snv.jussieu.fr (8.14.3/8.14.3/Submit) id n9RLdTss007929; Tue, 27 Oct 2009 22:39:29 +0100 (CET) (envelope-from arno) To: "Larry Rosenman" From: "Arno J. Klaassen" References: <00b301ca5739$8e9b3850$abd1a8f0$@org> Date: Tue, 27 Oct 2009 22:39:29 +0100 In-Reply-To: <00b301ca5739$8e9b3850$abd1a8f0$@org> (Larry Rosenman's message of "Tue\, 27 Oct 2009 14\:13\:14 -0500") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: ClamAV 0.94.2/9950/Tue Oct 27 19:28:02 2009 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at jchkmail.jussieu.fr with ID 4AE76893.003 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 4AE76893.003/134.157.184.22/heho.snv.jussieu.fr/heho.snv.jussieu.fr/ Cc: freebsd-net@freebsd.org Subject: Re: ZFS and 'traditional' nfs-export 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, 27 Oct 2009 21:39:33 -0000 hello, "Larry Rosenman" writes: > ZFS makes its own version of the exports file. > > Just do it that way, and be safe. > > You can pass the full set of NFS options in the sharenfs parameter.... ah ok, I see. Thanks for answering. I got fooled by the man zfs(1M) example : zfs set sharenfs='rw=@123.123.0.0/16,root=neo' tank/home This syntax does not seem to work for me (8.0RC2). Maybe an extra line could be added that one can just set the sharenfs property to exactly the same character string as in /etc/exports. Once again, merci. Arno From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 21:40:03 2009 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 90DBF1065670 for ; Tue, 27 Oct 2009 21:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 669CD8FC16 for ; Tue, 27 Oct 2009 21:40:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9RLe3AJ081065 for ; Tue, 27 Oct 2009 21:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9RLe3RE081064; Tue, 27 Oct 2009 21:40:03 GMT (envelope-from gnats) Date: Tue, 27 Oct 2009 21:40:03 GMT Message-Id: <200910272140.n9RLe3RE081064@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Tom Judge Cc: Subject: Re: kern/135836: [bce] bce BCM5709 Watchdog after warm boot - ok after cold boot X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tom Judge List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Oct 2009 21:40:03 -0000 The following reply was made to PR kern/135836; it has been noted by GNATS. From: Tom Judge To: bug-followup@FreeBSD.org, rwilliams@borderware.com Cc: Subject: Re: kern/135836: [bce] bce BCM5709 Watchdog after warm boot - ok after cold boot Date: Tue, 27 Oct 2009 21:30:51 +0000 Hi, This seems to be a duplicate of: kern/134788 Tom From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 21:40:05 2009 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 750A5106568D for ; Tue, 27 Oct 2009 21:40:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4AB988FC0C for ; Tue, 27 Oct 2009 21:40:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9RLe5GW081091 for ; Tue, 27 Oct 2009 21:40:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9RLe54x081089; Tue, 27 Oct 2009 21:40:05 GMT (envelope-from gnats) Date: Tue, 27 Oct 2009 21:40:05 GMT Message-Id: <200910272140.n9RLe54x081089@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Tom Judge Cc: Subject: Re: kern/134658: [bce] bce driver fails on PowerEdge m610 blade. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tom Judge List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Oct 2009 21:40:05 -0000 The following reply was made to PR kern/134658; it has been noted by GNATS. From: Tom Judge To: bug-followup@FreeBSD.org, harald_jensas@dell.com Cc: Subject: Re: kern/134658: [bce] bce driver fails on PowerEdge m610 blade. Date: Tue, 27 Oct 2009 21:32:24 +0000 Hi, This seems to be a duplicate of these 2: kern/139761 kern/136417 Tom From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 21:56:20 2009 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 46F6C1065670 for ; Tue, 27 Oct 2009 21:56:20 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from tomjudge.vm.bytemark.co.uk (tomjudge.vm.bytemark.co.uk [80.68.91.100]) by mx1.freebsd.org (Postfix) with ESMTP id 0A28F8FC15 for ; Tue, 27 Oct 2009 21:56:19 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 4A04148A70 for ; Tue, 27 Oct 2009 21:56:19 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at tomjudge.vm.bytemark.co.uk Received: from tomjudge.vm.bytemark.co.uk ([127.0.0.1]) by localhost (tomjudge.vm.bytemark.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0wx0gxFf0lrq for ; Tue, 27 Oct 2009 21:56:16 +0000 (GMT) Received: from rita.nodomain (unknown [192.168.205.6]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 670DD48A57 for ; Tue, 27 Oct 2009 21:56:16 +0000 (GMT) Message-ID: <4AE76C4F.7030900@tomjudge.com> Date: Tue, 27 Oct 2009 21:55:27 +0000 From: Tom Judge User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: bce(4) PRs - brief analysis 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, 27 Oct 2009 21:56:20 -0000 Hi, I went looking though all the PRs related to bce(4) this afternoon trying to shed some light on my R610 issue and came across the following duplicates: No SerDes PHY Support: kern/139761 kern/136417 kern/134658 - and possibly kern/118238 however this is different controller. CTX Write Errors: kern/135836 kern/134788 What is the correct way to report these duplicates? Also the follow 3 seem to be from a time when the bce driver was very buggy: kern/107850 kern/100858 kern/108542 These issues should no longer be present in 7.0+ ( I have not tested any other 6.X releases however I do have a patched 6.2 that works correctly based on changes that went into HEAD leading up to /Fri Jul 20 09:19:15 2007 UTC). Tom / From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 22:00:14 2009 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 0989F106568D for ; Tue, 27 Oct 2009 22:00:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9EFAF8FC1C for ; Tue, 27 Oct 2009 22:00:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9RM09ic097342 for ; Tue, 27 Oct 2009 22:00:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9RM09TO097341; Tue, 27 Oct 2009 22:00:09 GMT (envelope-from gnats) Date: Tue, 27 Oct 2009 22:00:09 GMT Message-Id: <200910272200.n9RM09TO097341@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Tom Judge Cc: Subject: Re: kern/107850: [bce] bce driver link negotiation is faulty X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tom Judge List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Oct 2009 22:00:14 -0000 The following reply was made to PR kern/107850; it has been noted by GNATS. From: Tom Judge To: bug-followup@FreeBSD.org, olavi@ipunplugged.com Cc: Subject: Re: kern/107850: [bce] bce driver link negotiation is faulty Date: Tue, 27 Oct 2009 21:51:05 +0000 This bug should not be present in modern releases (7.0+). Tom From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 22:00:14 2009 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 4658A1065696 for ; Tue, 27 Oct 2009 22:00:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id EA70E8FC30 for ; Tue, 27 Oct 2009 22:00:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9RM0Cxc097373 for ; Tue, 27 Oct 2009 22:00:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9RM0CXZ097372; Tue, 27 Oct 2009 22:00:12 GMT (envelope-from gnats) Date: Tue, 27 Oct 2009 22:00:12 GMT Message-Id: <200910272200.n9RM0CXZ097372@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Tom Judge Cc: Subject: Re: kern/108542: [bce] Huge network latencies with 6.2-RELEASE / STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tom Judge List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Oct 2009 22:00:14 -0000 The following reply was made to PR kern/108542; it has been noted by GNATS. From: Tom Judge To: bug-followup@FreeBSD.org, remy@unix-asp.com Cc: Subject: Re: kern/108542: [bce] Huge network latencies with 6.2-RELEASE / STABLE Date: Tue, 27 Oct 2009 21:53:41 +0000 This should not be a problem in more modern releases (7.0+). Tom From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 22:04:41 2009 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 10D411065692 for ; Tue, 27 Oct 2009 22:04:41 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by mx1.freebsd.org (Postfix) with ESMTP id E0D7E8FC24 for ; Tue, 27 Oct 2009 22:04:40 +0000 (UTC) Received: from [10.9.200.131] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Tue, 27 Oct 2009 14:50:08 -0700 X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201 Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.31]) by IRVEXCHHUB01.corp.ad.broadcom.com ([10.9.200.131]) with mapi; Tue, 27 Oct 2009 14:50:08 -0700 From: "David Christensen" To: "Tom Judge" , "net@freebsd.org" Date: Tue, 27 Oct 2009 14:50:06 -0700 Thread-Topic: bce(4) BCM5907 CTX write errors on 7.2 driver Thread-Index: AcpXKESXOfeMu5fGSQKvXKU8qBiU7AAJQWRg Message-ID: <5D267A3F22FD854F8F48B3D2B52381933A04B49180@IRVEXCHCCR01.corp.ad.broadcom.com> References: <4AE72910.8090708@tomjudge.com> In-Reply-To: <4AE72910.8090708@tomjudge.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-WSS-ID: 66F9B49A0UC29063522-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: "pyunyh@gmail.com" , "rwilliams@borderware.com" , Xin LI , Stanislav Sedov , Gideon Naim Subject: RE: bce(4) BCM5907 CTX write errors on 7.2 driver 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, 27 Oct 2009 22:04:41 -0000 > Has anyone seen these errors before: >=20 > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D135836&cat=3D >=20 > The system is a Dell R610 and it happens on both cold and warm boots. >=20 > I am about to check a second chassis, and test with 8, and=20 > will follow up after my tests. Yes, I've seen these errors on a Dell r710. The problem is related to an interaction between the FreeBSD driver and the bootcode firmware on the BCM5709 controller which can cause the bootcode firmware to=20 enable certain hardware blocks in the chip while the FreeBSD driver is=20 attempting to reset the device. This allows RX traffic to enter the=20 controller before the device is fully initialized. The fix is to upgrade the BCM5709 bootcode to version 5.02 or later. I'm checking if Dell has posted updated firmware which can address the problem. Dave= From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 22:11:51 2009 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 9EFB7106568D for ; Tue, 27 Oct 2009 22:11:51 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from tomjudge.vm.bytemark.co.uk (tomjudge.vm.bytemark.co.uk [80.68.91.100]) by mx1.freebsd.org (Postfix) with ESMTP id 5D5E88FC12 for ; Tue, 27 Oct 2009 22:11:51 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 8347E48A6E; Tue, 27 Oct 2009 22:11:50 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at tomjudge.vm.bytemark.co.uk Received: from tomjudge.vm.bytemark.co.uk ([127.0.0.1]) by localhost (tomjudge.vm.bytemark.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SzeCVHiuU41X; Tue, 27 Oct 2009 22:11:47 +0000 (GMT) Received: from rita.nodomain (unknown [192.168.205.6]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 5468248A57; Tue, 27 Oct 2009 22:11:46 +0000 (GMT) Message-ID: <4AE76FF1.9010401@tomjudge.com> Date: Tue, 27 Oct 2009 22:10:57 +0000 From: Tom Judge User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: David Christensen References: <4AE72910.8090708@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B49180@IRVEXCHCCR01.corp.ad.broadcom.com> In-Reply-To: <5D267A3F22FD854F8F48B3D2B52381933A04B49180@IRVEXCHCCR01.corp.ad.broadcom.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "rwilliams@borderware.com" , Gideon Naim , "net@freebsd.org" Subject: Re: bce(4) BCM5907 CTX write errors on 7.2 driver 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, 27 Oct 2009 22:11:51 -0000 David Christensen wrote: >> Has anyone seen these errors before: >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=135836&cat= >> >> The system is a Dell R610 and it happens on both cold and warm boots. >> >> I am about to check a second chassis, and test with 8, and >> will follow up after my tests. >> > > Yes, I've seen these errors on a Dell r710. The problem is related > to an interaction between the FreeBSD driver and the bootcode firmware > on the BCM5709 controller which can cause the bootcode firmware to > enable certain hardware blocks in the chip while the FreeBSD driver is > attempting to reset the device. This allows RX traffic to enter the > controller before the device is fully initialized. > > The fix is to upgrade the BCM5709 bootcode to version 5.02 or later. > I'm checking if Dell has posted updated firmware which can address > the problem. > > Hi David, Thanks for the rapid response. Dell have firmware 5.0.9 on their website here: http://tiny.cc/ex834 Will that work? Tom From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 22:18:46 2009 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 AB99E1065692 for ; Tue, 27 Oct 2009 22:18:46 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by mx1.freebsd.org (Postfix) with ESMTP id 8536D8FC14 for ; Tue, 27 Oct 2009 22:18:46 +0000 (UTC) Received: from [10.9.200.133] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Tue, 27 Oct 2009 15:18:36 -0700 X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201 Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.31]) by IRVEXCHHUB02.corp.ad.broadcom.com ([10.9.200.133]) with mapi; Tue, 27 Oct 2009 15:19:56 -0700 From: "David Christensen" To: "Tom Judge" Date: Tue, 27 Oct 2009 15:18:32 -0700 Thread-Topic: bce(4) BCM5907 CTX write errors on 7.2 driver Thread-Index: AcpXUoD5E9icl6lqQoqCQUWN1If1/wAAJcTA Message-ID: <5D267A3F22FD854F8F48B3D2B52381933A04B491AE@IRVEXCHCCR01.corp.ad.broadcom.com> References: <4AE72910.8090708@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B49180@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE76FF1.9010401@tomjudge.com> In-Reply-To: <4AE76FF1.9010401@tomjudge.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-WSS-ID: 66F9AE360UC29086733-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: "rwilliams@borderware.com" , Gideon Naim , "net@freebsd.org" Subject: RE: bce(4) BCM5907 CTX write errors on 7.2 driver 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, 27 Oct 2009 22:18:46 -0000 > Thanks for the rapid response. >=20 > Dell have firmware 5.0.9 on their website here: http://tiny.cc/ex834 >=20 > Will that work? Yes, that release does include a good version of BCM5709 bootcode (v5.06). I couldn't really tell until I downloaded the file and looked at the=20 temporary files inside. Thanks for the link. Dave= From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 22:29:09 2009 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 95A271065670 for ; Tue, 27 Oct 2009 22:29:09 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 2C7548FC1A for ; Tue, 27 Oct 2009 22:29:09 +0000 (UTC) Received: (qmail 29752 invoked by uid 399); 27 Oct 2009 22:29:08 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 27 Oct 2009 22:29:08 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4AE77437.4090700@FreeBSD.org> Date: Tue, 27 Oct 2009 15:29:11 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: freebsd-net@freebsd.org X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: benjsc@freebsd.org, sam@freebsd.org, thompsa@freebsd.org Subject: Can we turn off WPI_DEBUG 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, 27 Oct 2009 22:29:09 -0000 I cc'ed those who seem to have put the most/recent effort into sys/dev/wpi. Is there any objection to turning off WPI_DEBUG by default? it creates a lot of spam that the average user doesn't need. I use my 3945abg every day and haven't had any problems with it for ages so I think it's safe to say we're out of the period were debug by default is needed? Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 22:34:37 2009 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 F3C221065670 for ; Tue, 27 Oct 2009 22:34:36 +0000 (UTC) (envelope-from remodeler@alentogroup.org) Received: from courriel.marmotmail.com (courriel.marmotmail.com [85.17.36.172]) by mx1.freebsd.org (Postfix) with ESMTP id B88DE8FC26 for ; Tue, 27 Oct 2009 22:34:36 +0000 (UTC) Received: from bruce.epifora.com (localhost.local [127.0.0.1]) by courriel.marmotmail.com (Postfix) with ESMTP id 58A1A23978E for ; Wed, 28 Oct 2009 00:37:31 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by bruce.epifora.com (Postfix) with ESMTP id DF60D4761F9 for ; Tue, 27 Oct 2009 17:51:52 -0500 (EST) Received: from bruce.epifora.com ([127.0.0.1]) by localhost (bruce.epifora.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26123-02 for ; Tue, 27 Oct 2009 17:51:51 -0500 (EST) Received: from alentogroup.org (localhost [127.0.0.1]) by bruce.epifora.com (Postfix) with ESMTP id 593494761F8 for ; Tue, 27 Oct 2009 17:51:51 -0500 (EST) From: "remodeler" To: freebsd-net@freebsd.org Date: Tue, 27 Oct 2009 17:51:51 -0500 Message-Id: <20091027224716.M1459@alentogroup.org> X-OriginatingIP: 127.0.0.1 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: Port-forwarding with IPFW / natd 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, 27 Oct 2009 22:34:37 -0000 Is there any reason to prefer port-forwarding with ipfw (forward ipaddr) vs. natd (-redirect_port), if I am using both subsystems in any case? I see natd uses libalias and an ipfw divert port, so my thought is that the ipfw approach would incur less overhead. Also, the ipfw approach permits a hostname for resolving where natd requires an IP address. Thank you. From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 22:46:28 2009 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 C9E901065695 for ; Tue, 27 Oct 2009 22:46:28 +0000 (UTC) (envelope-from remodeler@alentogroup.org) Received: from courriel.marmotmail.com (courriel.marmotmail.com [85.17.36.172]) by mx1.freebsd.org (Postfix) with ESMTP id 8EAA48FC1C for ; Tue, 27 Oct 2009 22:46:28 +0000 (UTC) Received: from bruce.epifora.com (localhost.local [127.0.0.1]) by courriel.marmotmail.com (Postfix) with ESMTP id EBCC723979E for ; Wed, 28 Oct 2009 00:49:22 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by bruce.epifora.com (Postfix) with ESMTP id 9F24F4761F9 for ; Tue, 27 Oct 2009 18:03:44 -0500 (EST) Received: from bruce.epifora.com ([127.0.0.1]) by localhost (bruce.epifora.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01948-10 for ; Tue, 27 Oct 2009 18:03:43 -0500 (EST) Received: from alentogroup.org (localhost [127.0.0.1]) by bruce.epifora.com (Postfix) with ESMTP id 1C5854761F8 for ; Tue, 27 Oct 2009 18:03:43 -0500 (EST) From: "remodeler" To: freebsd-net@freebsd.org Date: Tue, 27 Oct 2009 18:03:43 -0500 Message-Id: <20091027225454.M12540@alentogroup.org> X-OriginatingIP: 127.0.0.1 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: Netgraph question - multiple kernels 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, 27 Oct 2009 22:46:28 -0000 My understanding is that I can bind multiple machines running netgraph into one large netgraph, by using something like ng_ksocket nodes bound with a tunneling device. By doing this, is the restriction of one ng_ipfw node per netgraph global to all of the machines (one, and only one, ng_ipfw node)? If the ng_ksocket nodes are connected to ng_bridges on both of the machines, will only relevant network traffic cross the link - or all network traffic? Can I configure the link between the two machines so that I can directly connect a netgraph node on one machine to a node on the other, or must they communicate by the bridge-tunnel-tunnel-bridge structure? Thank you. From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 22:48:32 2009 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 65236106566B for ; Tue, 27 Oct 2009 22:48:32 +0000 (UTC) (envelope-from stas@deglitch.com) Received: from mx0.deglitch.com (backbone.deglitch.com [IPv6:2001:16d8:fffb:4::abba]) by mx1.freebsd.org (Postfix) with ESMTP id 0BDA18FC19 for ; Tue, 27 Oct 2009 22:48:31 +0000 (UTC) Received: from orion.SpringDaemons.com (unknown [77.232.3.143]) by mx0.deglitch.com (Postfix) with ESMTPA id B3FDA8FC4E; Wed, 28 Oct 2009 01:48:29 +0300 (MSK) Received: from orion (localhost [127.0.0.1]) by orion.SpringDaemons.com (Postfix) with SMTP id 8A0EE3985D; Wed, 28 Oct 2009 02:49:21 +0300 (MSK) Date: Wed, 28 Oct 2009 02:49:16 +0300 From: Stanislav Sedov To: "Steven Hartland" Message-Id: <20091028024916.2507b92d.stas@deglitch.com> In-Reply-To: References: <4AE72910.8090708@tomjudge.com> <4AE753E4.6050205@tomjudge.com> Organization: Deglitch Networks X-Mailer: carrier-pigeon Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Wed__28_Oct_2009_02_49_16_+0300_=3HqRw6xTZCF5jvF" Cc: pyunyh@gmail.com, David Christensen , rwilliams@borderware.com, net@freebsd.org, Tom Judge , Xin LI Subject: Re: bce(4) BCM5907 CTX write errors on 7.2 driver 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, 27 Oct 2009 22:48:32 -0000 --Signature=_Wed__28_Oct_2009_02_49_16_+0300_=3HqRw6xTZCF5jvF Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, 27 Oct 2009 20:30:38 -0000 "Steven Hartland" mentioned: > M610 is also broken due to unsupported bge revision :( >=20 What bge revision do you have? I recently committed support for new bge(4) chip revisions to HEAD, can you check, please, if HEAD recognize this adapter correctly? You can boot HEAD kernel on your 7.x/8.x userland for test purposes. Thanks! --=20 Stanislav Sedov ST4096-RIPE --Signature=_Wed__28_Oct_2009_02_49_16_+0300_=3HqRw6xTZCF5jvF Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJK54cBAAoJEKN82nOYvCd06hAP/1FKJ//lSEtuxP64UxlmER2E 57bjgP9C0HO0o2NVczrWl6z+TwLTe+skysDSKFd+hTUhGST/cVDM5eKqS2CYL0FP 5xPloQ6k1ZzcA8cdxprl8XnOxXjQdMzVom1m+A4Lhtrvlzsijnd6wkdBw8e+tNJU RVo4ZreaOp/V57uB/YBXVveNYBsbIArqRcLAOIgthE1DWLcuUI1/Heqz12fKnnhS Mi0UG1Uo9Hk651bF3GI2tDlo+KCol5T+MBqSItKGO95YjDPtWqKLtcqVrLs1j6ET FV9LxJogY1H0+AK4HLlAWQAc1fhrU419tsoQGSywKgolOKzUNIz6L6MaIOYA7kG+ cYRr10djq9kdpizCy6JkrJfrPLb+sve1oU17uKuH7bqZ2iKUrkokdFTe7X+yUGsg Wx+lqpgTBp9CXOc2WNTg5bAp14bnUTSerWwt7Glr/5AmXCeRv8oNzQhiMJkgHorq 9UvY8hGQNSDkDl+lVP+fMNCE1omjtz6l659BPtuI5Xvxbkkbq8EqXWYA23goeoUI 7b140JjyPmhScF4/k9WsrROTwKjnDhhPIoIm1kG6em3npdWa4ezMsPH8aCcRBpuZ S+XXAqEVZ3RBennQi6Hrfltq+wuY6LYi9r8svY6yQ+Ubr+IrqERD5DYxjEUkhclh FTaZ9h1mNzBvq3Zdb62K =tT8z -----END PGP SIGNATURE----- --Signature=_Wed__28_Oct_2009_02_49_16_+0300_=3HqRw6xTZCF5jvF-- From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 23:01:53 2009 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 92939106566C for ; Tue, 27 Oct 2009 23:01:53 +0000 (UTC) (envelope-from SRS0=V0aFnl=GQ=tomjudge.com=tom@srs.bis.na.blackberry.com) Received: from smtp07.bis.na.blackberry.com (smtp07.bis.na.blackberry.com [216.9.248.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5BC538FC1E for ; Tue, 27 Oct 2009 23:01:53 +0000 (UTC) Received: from bda307.bisx.prod.on.blackberry (bda307.bisx.prod.on.blackberry [172.20.232.67]) by srs.bis.na.blackberry.com (8.13.7 TEAMON/8.13.7) with ESMTP id n9RMXZ2u028910; Tue, 27 Oct 2009 22:33:35 GMT Received: from bda307.bisx.prod.on.blackberry (localhost.localdomain [127.0.0.1]) by bda307.bisx.prod.on.blackberry (8.13.7 TEAMON/8.13.7) with ESMTP id n9RMXplE002297; Tue, 27 Oct 2009 22:33:51 GMT X-rim-org-msg-ref-id: 444079893 Message-ID: <444079893-1256682829-cardhu_decombobulator_blackberry.rim.net-789454561-@bda313.bisx.prod.on.blackberry> X-Priority: Normal Sensitivity: Normal Importance: Normal To: "David Christensen" From: "Tom Judge" Date: Tue, 27 Oct 2009 22:37:08 +0000 Content-Type: text/plain MIME-Version: 1.0 Cc: "rwilliams@borderware.com" , Gideon Naim , "net@freebsd.org" Subject: Re: bce(4) BCM5907 CTX write errors on 7.2 driver X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: tom@tomjudge.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Oct 2009 23:01:53 -0000 First sorry for the top post, the blackberry won't allow me to bottom post or I can't find the option. I will try this update when I get to the office in the morning. Hopefully it will resolve the issue. Thanks Tom ------Original Message------ From: David Christensen To: Tom Judge Cc: net@freebsd.org Cc: rwilliams@borderware.com Cc: Gideon Naim Subject: RE: bce(4) BCM5907 CTX write errors on 7.2 driver Sent: 27 Oct 2009 17:18 > Thanks for the rapid response. > > Dell have firmware 5.0.9 on their website here: http://tiny.cc/ex834 > > Will that work? Yes, that release does include a good version of BCM5709 bootcode (v5.06). I couldn't really tell until I downloaded the file and looked at the temporary files inside. Thanks for the link. Dave Sent via BlackBerry from T-Mobile From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 23:02:18 2009 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 C29DA106568D for ; Tue, 27 Oct 2009 23:02:18 +0000 (UTC) (envelope-from prvs=1551678ed3=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 55BAA8FC35 for ; Tue, 27 Oct 2009 23:02:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk; s=Multiplay; t=1256684537; x=1257289337; q=dns/txt; h=Received: Message-ID:From:To:Cc:References:Subject:Date:MIME-Version: Content-Type:Content-Transfer-Encoding; bh=Ja1FFd+SXjxdkSxL23HKl /VvATyczfpKarH1bhUD2Bo=; b=b73Ie6dlRCoHAZJL5fItGJ06nDf0nBcf9Z/Ts XLCayXdfZPD9FFVA03+nWSEnB6wwy2/irteHJr7pJfJH3qqpcaZJyGXBDdWQ6ZuJ kNzaHp8XbzAf2g/fTGCP5R1uiGnF9Es+RVCN6r64d4CZLNOeezFzNX0WqZVcGyfa gvoJMQ= X-MDAV-Processed: mail1.multiplay.co.uk, Tue, 27 Oct 2009 23:02:17 +0000 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v10.0.4) with ESMTP id md50008435233.msg for ; Tue, 27 Oct 2009 23:02:17 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Tue, 27 Oct 2009 23:02:17 +0000 (not processed: message from trusted or authenticated source) X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 188.220.16.96 X-Return-Path: prvs=1551678ed3=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: net@freebsd.org Message-ID: From: "Steven Hartland" To: "Stanislav Sedov" References: <4AE72910.8090708@tomjudge.com> <4AE753E4.6050205@tomjudge.com> <20091028024916.2507b92d.stas@deglitch.com> Date: Tue, 27 Oct 2009 23:02:09 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5843 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Cc: pyunyh@gmail.com, David Christensen , Xin LI , net@freebsd.org, Tom Judge , rwilliams@borderware.com Subject: Re: bce(4) BCM5907 CTX write errors on 7.2 driver 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, 27 Oct 2009 23:02:18 -0000 Sorry I typo'ed there, should have said bce, is that still relevant?. We haven't been able to install any version yet, so can't just try a kernel, no way of getting data on to the machine without a working netcard ;-) Did this update include any updated PHY support for bce? As the the precise error indicates that as the issue, as can be seen here: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/134658 If it does will this be in an ISO snapshot yet, as that's the only way of testing? Regards Steve ----- Original Message ----- From: "Stanislav Sedov" > M610 is also broken due to unsupported bge revision :( > What bge revision do you have? I recently committed support for new bge(4) chip revisions to HEAD, can you check, please, if HEAD recognize this adapter correctly? You can boot HEAD kernel on your 7.x/8.x userland for test purposes. Thanks! -- Stanislav Sedov ST4096-RIPE ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 23:14:35 2009 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 96B65106568B for ; Tue, 27 Oct 2009 23:14:35 +0000 (UTC) (envelope-from ccowart@rescomp.berkeley.edu) Received: from hal.rescomp.berkeley.edu (hal.Rescomp.Berkeley.EDU [169.229.70.150]) by mx1.freebsd.org (Postfix) with ESMTP id 815C48FC08 for ; Tue, 27 Oct 2009 23:14:35 +0000 (UTC) Received: by hal.rescomp.berkeley.edu (Postfix, from userid 1225) id BFBCF597C97; Tue, 27 Oct 2009 16:14:34 -0700 (PDT) Date: Tue, 27 Oct 2009 16:14:34 -0700 From: Chris Cowart To: remodeler Message-ID: <20091027231434.GC11723@hal.rescomp.berkeley.edu> Mail-Followup-To: remodeler , freebsd-net@freebsd.org References: <20091027224716.M1459@alentogroup.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="96YOpH+ONegL0A3E" Content-Disposition: inline In-Reply-To: <20091027224716.M1459@alentogroup.org> Organization: RSSP-IT, UC Berkeley User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-net@freebsd.org Subject: Re: Port-forwarding with IPFW / natd 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, 27 Oct 2009 23:14:35 -0000 --96YOpH+ONegL0A3E Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable remodeler wrote: > Is there any reason to prefer port-forwarding with ipfw (forward ipaddr) = vs. > natd (-redirect_port), if I am using both subsystems in any case? I see n= atd > uses libalias and an ipfw divert port, so my thought is that the ipfw app= roach > would incur less overhead. Also, the ipfw approach permits a hostname for > resolving where natd requires an IP address. Using natd (or ipfw nat) has the ability to manipulate the IP address and ports of a packet. The fwd capability in ipfw does not modify the layer 3 headers, but instead short-circuits the next-hop logic. Take a look at the fwd description in ipfw(8). I would recommend using the ipfw built-in nat support (search for NAT in ipfw(8)) instead of the old-style divert solution. As I understand it, divert has overhead related to copying the packets to and from userland, which is unnecessary when using the in-kernel implementation. --=20 Chris Cowart Network Technical Lead Network & Infrastructure Services, RSSP-IT UC Berkeley --96YOpH+ONegL0A3E Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iQIcBAEBAwAGBQJK537aAAoJEC8b9sM8ejXti/YP/jbvz218pJ4+nHewFJKQL9qL wvVJySRz5Tw1jbFQ96JyNWtdCQphZ8JOKEwnsbVl9lxvNj7kWVLf++uX5BIdjLfE 6NxbKfcBzneANo7//4ddIGa4uG+K5tqO+CSiKfmOV8yt1bToU9va4r9Cnkl8tjKh I1Ddlwm1c2cu38DINN7c8nA6CCwV01Jh9uUrx/xsMHupwfhLGKd0CSUs5LKjSX2Q kyfYeuPTjXbKjeWmDk4SEp0DzfTWQ15BEAyGdMKGMe5Wla10ITaLBs4petgQZzlV WND4BhXCC1aEqE/R6qN+O3OM4bS3A6YKCOPojKwuKCT4xvKiBiOncyWLfA/k9NjJ zbcv7pBjqm/ucDgJxqxo7NAb5DFU1L14HdFMuF03/UCxsNp7+h7fpUMnZ9zfHuo2 JBdBAlMdoyADlAQPJDoiscz+q2e5XqsdPcQ/o6+ZghFZez1HYY2mYz1MMxOAY9BM krnSM69fh6/uR6pildJuNBZ7Jfm7xcZjpKuHOvK6JHiBl0oKbgycwzWs+h9eOTrd 4BWxLawCEHruxKh3dfikea9WdaaBokL2Nkc1GTdtyrCilgJHluRvUpoDfcYIkLuf lPfVSh3AjfLWzxaNoqeai12kGCX++5XLpxEn3GGsZo8qi8wgUuB1J2URCT0OTivW Knf3o+HhOKGKEW2ZHxK2 =jAGS -----END PGP SIGNATURE----- --96YOpH+ONegL0A3E-- From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 23:17:29 2009 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 9ADB61065670 for ; Tue, 27 Oct 2009 23:17:29 +0000 (UTC) (envelope-from stas@deglitch.com) Received: from mx0.deglitch.com (backbone.deglitch.com [IPv6:2001:16d8:fffb:4::abba]) by mx1.freebsd.org (Postfix) with ESMTP id 4045A8FC16 for ; Tue, 27 Oct 2009 23:17:29 +0000 (UTC) Received: from orion.SpringDaemons.com (unknown [77.232.3.143]) by mx0.deglitch.com (Postfix) with ESMTPA id 03A028FC4E; Wed, 28 Oct 2009 02:17:28 +0300 (MSK) Received: from orion (localhost [127.0.0.1]) by orion.SpringDaemons.com (Postfix) with SMTP id BFEEF39858; Wed, 28 Oct 2009 03:18:19 +0300 (MSK) Date: Wed, 28 Oct 2009 03:18:19 +0300 From: Stanislav Sedov To: "Steven Hartland" Message-Id: <20091028031819.c965c22d.stas@deglitch.com> In-Reply-To: References: <4AE72910.8090708@tomjudge.com> <4AE753E4.6050205@tomjudge.com> <20091028024916.2507b92d.stas@deglitch.com> Organization: Deglitch Networks X-Mailer: carrier-pigeon Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Wed__28_Oct_2009_03_18_19_+0300__9P/vzTrH_K_aVqB" Cc: pyunyh@gmail.com, David Christensen , Xin LI , net@freebsd.org, Tom Judge , rwilliams@borderware.com Subject: Re: bce(4) BCM5907 CTX write errors on 7.2 driver 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, 27 Oct 2009 23:17:29 -0000 --Signature=_Wed__28_Oct_2009_03_18_19_+0300__9P/vzTrH_K_aVqB Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, 27 Oct 2009 23:02:09 -0000 "Steven Hartland" mentioned: > Sorry I typo'ed there, should have said bce, is that still relevant?. >=20 > We haven't been able to install any version yet, so can't just > try a kernel, no way of getting data on to the machine without > a working netcard ;-) >=20 > Did this update include any updated PHY support for bce? As the > the precise error indicates that as the issue, as can be seen here: > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/134658 >=20 > If it does will this be in an ISO snapshot yet, as that's the only=20 > way of testing? >=20 If I understand the PR comments right, the code to support this PHY should be present in 8.0. So you can start by trying out 8.0-RC1 ISO image (or USB stick image, fwiw). --=20 Stanislav Sedov ST4096-RIPE --Signature=_Wed__28_Oct_2009_03_18_19_+0300__9P/vzTrH_K_aVqB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJK543LAAoJEKN82nOYvCd0regP/3tRv3LstogwPFNYOWeFbBJ3 2wXwoPi+HM/e4645hJHe68pP0nffLbDd8B6/xH9qnadJHsAMX5iG9NukeuTz6ha7 20LWszJ/VLqhvcFp6D+6n3wXH5CyI40ZgBwoA+sjwSw5/tP/RARkQ9S0VpRlWalh SGAVXTRLvRbpKvPMIJ+2e+yyRJqK1xq40xNYJuwEQWcGrIBdV7LHszjBoAdcyYt4 DywwnPx7IMcWQ4Bc5ov5y1gcLvfAhKTOoyACsKJPTJG48AN5HJMxOUWvPy6RzDLF 4Wcn3hALAv8KQh7n/h3CdGIzC4cNcPWcDrsJHGRUel9k3bNV4Y3NCP0zCRUs2jhH zAcJUmaRW74SffzbaDniffkRQN3gd3RnNDMuG3C0TmT+EoKwjQGU0s2ZGI9c/Wzw WGI+CHTPcWwrouY0A5jnLVB4Ouk6iFzQUv5a0R5li95v1yAXOH0nczLRjS2IQKTQ fyM2ZqoF69U4KgbEGTIkYmXCtEbmPH0AffpmJqRhfPQfPJ3/mc/sR5W+ZC4p+qNv qLCYDfIFosPcdx7VF7AIzcZOVnOtMTCx/8DvPj9Git5c4s929crOYol816DYZcAZ kJOcEYkfNnJw3UA1zVuPiMHSWoHBgN9Th/FXxIbYyaRrjzHesmBG3l7szz2ml+qv OEFMQjAqYEG1bikGFZ3F =wHKV -----END PGP SIGNATURE----- --Signature=_Wed__28_Oct_2009_03_18_19_+0300__9P/vzTrH_K_aVqB-- From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 23:18:21 2009 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 5EE6D1065695; Tue, 27 Oct 2009 23:18:21 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from mail.clearchain.com (leo.clearchain.com [199.73.29.74]) by mx1.freebsd.org (Postfix) with ESMTP id 21CCF8FC0C; Tue, 27 Oct 2009 23:18:20 +0000 (UTC) Received: from [192.168.0.151] (wcl.ml.unisa.edu.au [130.220.166.5]) (authenticated bits=0) by mail.clearchain.com (8.14.3/8.14.3) with ESMTP id n9RMwUpQ003927 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 28 Oct 2009 09:28:38 +1030 (CST) (envelope-from Benjamin.Close@clearchain.com) Message-ID: <4AE77BF8.3040907@clearchain.com> Date: Wed, 28 Oct 2009 09:32:16 +1030 From: Benjamin Close User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4pre) Gecko/20090915 Lightning/1.0pre Thunderbird/3.0b4 MIME-Version: 1.0 To: Doug Barton References: <4AE77437.4090700@FreeBSD.org> In-Reply-To: <4AE77437.4090700@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (mail.clearchain.com [199.73.29.74]); Wed, 28 Oct 2009 09:28:41 +1030 (CST) Cc: freebsd-net@FreeBSD.org, benjsc@FreeBSD.org, sam@FreeBSD.org, thompsa@FreeBSD.org Subject: Re: Can we turn off WPI_DEBUG 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, 27 Oct 2009 23:18:21 -0000 On 28/10/09 08:59, Doug Barton wrote: > I cc'ed those who seem to have put the most/recent effort into > sys/dev/wpi. > > Is there any objection to turning off WPI_DEBUG by default? it creates > a lot of spam that the average user doesn't need. I use my 3945abg > every day and haven't had any problems with it for ages so I think > it's safe to say we're out of the period were debug by default is needed? > I've no objections, I was originally turned on to aid in helping user issues. Many of these seem to have now been solved. Cheers, Benjamin From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 23:36:07 2009 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 B15141065679 for ; Tue, 27 Oct 2009 23:36:07 +0000 (UTC) (envelope-from prvs=1551678ed3=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 4338D8FC21 for ; Tue, 27 Oct 2009 23:36:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk; s=Multiplay; t=1256686566; x=1257291366; q=dns/txt; h=Received: Message-ID:From:To:Cc:References:Subject:Date:MIME-Version: Content-Type:Content-Transfer-Encoding; bh=k1iSMyAqVnZ/se3i3R34K kh7ZctzUTAePtwLh5HIQFo=; b=hN1a64ENjUZauM1h+eD5uBMx3XlvWAt6Z+1ZS V3ppQ6qShwR6vb7EJ20abqVEXTmqps19YBh5xNcMBMDWCBhUuCywvE0LkYkHfwnq sAbZR7WUv+vwhqKT9tND9LF7ZsY7ORjRxpcXh2PIEQJuDwB7spPEXLiMKVKhydse 3DfIjQ= X-MDAV-Processed: mail1.multiplay.co.uk, Tue, 27 Oct 2009 23:36:06 +0000 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v10.0.4) with ESMTP id md50008435322.msg for ; Tue, 27 Oct 2009 23:36:06 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Tue, 27 Oct 2009 23:36:06 +0000 (not processed: message from trusted or authenticated source) X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 188.220.16.96 X-Return-Path: prvs=1551678ed3=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: net@freebsd.org Message-ID: <43816B76DBB041EDBFFD09C5089B7F75@multiplay.co.uk> From: "Steven Hartland" To: "Stanislav Sedov" References: <4AE72910.8090708@tomjudge.com><4AE753E4.6050205@tomjudge.com><20091028024916.2507b92d.stas@deglitch.com> <20091028031819.c965c22d.stas@deglitch.com> Date: Tue, 27 Oct 2009 23:36:01 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5843 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Cc: pyunyh@gmail.com, David Christensen , Xin LI , net@freebsd.org, Tom Judge , rwilliams@borderware.com Subject: Re: bce(4) BCM5907 CTX write errors on 7.2 driver 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, 27 Oct 2009 23:36:07 -0000 On Tue, 27 Oct 2009 23:02:09 -0000 "Steven Hartland" mentioned: > If I understand the PR comments right, the code to support this PHY > should be present in 8.0. So you can start by trying out 8.0-RC1 > ISO image (or USB stick image, fwiw). Just tried 8.0RC2 no go, PHY still not supported :( Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 23:37:02 2009 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 89D74106566C; Tue, 27 Oct 2009 23:37:02 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from pele.citylink.co.nz (pele.citylink.co.nz [202.8.44.226]) by mx1.freebsd.org (Postfix) with ESMTP id 187C28FC1C; Tue, 27 Oct 2009 23:37:01 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by pele.citylink.co.nz (Postfix) with ESMTP id B800D100E0; Wed, 28 Oct 2009 12:20:49 +1300 (NZDT) X-Virus-Scanned: Debian amavisd-new at citylink.co.nz Received: from pele.citylink.co.nz ([127.0.0.1]) by localhost (pele.citylink.co.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZB8yuoVB+Sca; Wed, 28 Oct 2009 12:20:44 +1300 (NZDT) Received: from citylink.fud.org.nz (unknown [202.8.44.45]) by pele.citylink.co.nz (Postfix) with ESMTP; Wed, 28 Oct 2009 12:20:44 +1300 (NZDT) Received: by citylink.fud.org.nz (Postfix, from userid 1001) id C126211475; Wed, 28 Oct 2009 12:20:43 +1300 (NZDT) Date: Wed, 28 Oct 2009 12:20:43 +1300 From: Andrew Thompson To: Doug Barton Message-ID: <20091027232043.GB16914@citylink.fud.org.nz> References: <4AE77437.4090700@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AE77437.4090700@FreeBSD.org> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-net@freebsd.org, benjsc@freebsd.org, sam@freebsd.org Subject: Re: Can we turn off WPI_DEBUG 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, 27 Oct 2009 23:37:02 -0000 On Tue, Oct 27, 2009 at 03:29:11PM -0700, Doug Barton wrote: > I cc'ed those who seem to have put the most/recent effort into > sys/dev/wpi. > > Is there any objection to turning off WPI_DEBUG by default? it creates > a lot of spam that the average user doesn't need. I use my 3945abg > every day and haven't had any problems with it for ages so I think > it's safe to say we're out of the period were debug by default is needed? Go for it. Andrew From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 23:37:21 2009 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 83B24106566C for ; Tue, 27 Oct 2009 23:37:21 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outW.internet-mail-service.net (outw.internet-mail-service.net [216.240.47.246]) by mx1.freebsd.org (Postfix) with ESMTP id 6D3A58FC17 for ; Tue, 27 Oct 2009 23:37:21 +0000 (UTC) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 296EFB094E; Tue, 27 Oct 2009 16:37:21 -0700 (PDT) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id BD6AB2D6014; Tue, 27 Oct 2009 16:37:20 -0700 (PDT) Message-ID: <4AE78430.5070305@elischer.org> Date: Tue, 27 Oct 2009 16:37:20 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: remodeler References: <20091027224716.M1459@alentogroup.org> In-Reply-To: <20091027224716.M1459@alentogroup.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Port-forwarding with IPFW / natd 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, 27 Oct 2009 23:37:21 -0000 remodeler wrote: > Is there any reason to prefer port-forwarding with ipfw (forward ipaddr) vs. > natd (-redirect_port), if I am using both subsystems in any case? I see natd > uses libalias and an ipfw divert port, so my thought is that the ipfw approach > would incur less overhead. Also, the ipfw approach permits a hostname for > resolving where natd requires an IP address. they do different things NAT changes the packets while fwd leaves them alone but just changes where they are delivered. which you use depends on what you are trying to do. > > Thank you. > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Tue Oct 27 23:41:55 2009 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 3CC4F1065676 for ; Tue, 27 Oct 2009 23:41:55 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outO.internet-mail-service.net (outo.internet-mail-service.net [216.240.47.238]) by mx1.freebsd.org (Postfix) with ESMTP id 260BB8FC0C for ; Tue, 27 Oct 2009 23:41:55 +0000 (UTC) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 08DDFAE083; Tue, 27 Oct 2009 16:41:55 -0700 (PDT) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id 8A3802D6018; Tue, 27 Oct 2009 16:41:54 -0700 (PDT) Message-ID: <4AE78541.50700@elischer.org> Date: Tue, 27 Oct 2009 16:41:53 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: remodeler References: <20091027225454.M12540@alentogroup.org> In-Reply-To: <20091027225454.M12540@alentogroup.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Netgraph question - multiple kernels 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, 27 Oct 2009 23:41:55 -0000 remodeler wrote: > My understanding is that I can bind multiple machines running netgraph into > one large netgraph, by using something like ng_ksocket nodes bound with a > tunneling device. you COULD do that, yes, but the two netgraphs are unaware of each other. > > By doing this, is the restriction of one ng_ipfw node per netgraph global to > all of the machines (one, and only one, ng_ipfw node)? no it's one per machine > If the ng_ksocket nodes > are connected to ng_bridges on both of the machines, will only relevant > network traffic cross the link - or all network traffic? ng_bridge does MAC address filtering. it only sends no broadcast packets to teh link where it has seen packets coming from that mac address. > Can I configure the > link between the two machines so that I can directly connect a netgraph node > on one machine to a node on the other, or must they communicate by the > bridge-tunnel-tunnel-bridge structure? You are sending the packet out of one netgraph and into another. how you get the packet there is your business.. you could use two ng_ether nodes and use a dedicated ethernet as a low latency tunnel. > > Thank you. > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Wed Oct 28 01:15:22 2009 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 23F331065696 for ; Wed, 28 Oct 2009 01:15:22 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from kennaway-macbookpro.config (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 408468FC15; Wed, 28 Oct 2009 01:15:21 +0000 (UTC) Message-ID: <4AE79B37.5010203@FreeBSD.org> Date: Wed, 28 Oct 2009 01:15:35 +0000 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: "Arno J. Klaassen" References: <00b301ca5739$8e9b3850$abd1a8f0$@org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Larry Rosenman Subject: Re: ZFS and 'traditional' nfs-export 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, 28 Oct 2009 01:15:22 -0000 Arno J. Klaassen wrote: > hello, > > "Larry Rosenman" writes: > >> ZFS makes its own version of the exports file. >> >> Just do it that way, and be safe. >> >> You can pass the full set of NFS options in the sharenfs parameter.... > > ah ok, I see. Thanks for answering. > > I got fooled by the man zfs(1M) example : > > zfs set sharenfs='rw=@123.123.0.0/16,root=neo' tank/home > > This syntax does not seem to work for me (8.0RC2). > Maybe an extra line could be added that one can just set > the sharenfs property to exactly the same character string > as in /etc/exports. Yeah that is the solaris notation -- various things in the manpages have not yet been customized for FreeBSD, which can be a bit confusing. The only limitation I've found in using sharenfs is that you can't specify multiple exports for the same filesystem, e.g. exporting to different hosts/networks with different options. The solaris notation above allows you to express this. Kris From owner-freebsd-net@FreeBSD.ORG Wed Oct 28 03:20:47 2009 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 8AC46106566C for ; Wed, 28 Oct 2009 03:20:47 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by mx1.freebsd.org (Postfix) with ESMTP id 69D208FC15 for ; Wed, 28 Oct 2009 03:20:47 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=rmac.psg.com) by ran.psg.com with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1N2z5Z-000Mo5-Ms; Wed, 28 Oct 2009 03:20:45 +0000 Received: from rmac.local.psg.com (localhost [127.0.0.1]) by rmac.psg.com (Postfix) with ESMTP id 202A12BBBA62; Wed, 28 Oct 2009 12:20:45 +0900 (JST) Date: Wed, 28 Oct 2009 12:20:45 +0900 Message-ID: From: Randy Bush To: Chris Cowart In-Reply-To: <20091027231434.GC11723@hal.rescomp.berkeley.edu> References: <20091027224716.M1459@alentogroup.org> <20091027231434.GC11723@hal.rescomp.berkeley.edu> User-Agent: Wanderlust/2.15.5 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: freebsd-net@freebsd.org, remodeler Subject: Re: Port-forwarding with IPFW / natd 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, 28 Oct 2009 03:20:47 -0000 > Using natd (or ipfw nat) has the ability to manipulate the IP address > and ports of a packet. The fwd capability in ipfw does not modify the > layer 3 headers, but instead short-circuits the next-hop logic. Take a > look at the fwd description in ipfw(8). > > I would recommend using the ipfw built-in nat support (search for NAT in > ipfw(8)) instead of the old-style divert solution. As I understand it, > divert has overhead related to copying the packets to and from userland, > which is unnecessary when using the in-kernel implementation. i keep circling this area too. my problem is that i use the nat of ppp for the external pppoe. but i want to redirect inbound ssh to a particular server. randy From owner-freebsd-net@FreeBSD.ORG Wed Oct 28 03:34:12 2009 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 EFA91106566C for ; Wed, 28 Oct 2009 03:34:12 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from tomjudge.vm.bytemark.co.uk (tomjudge.vm.bytemark.co.uk [80.68.91.100]) by mx1.freebsd.org (Postfix) with ESMTP id AC0E58FC1B for ; Wed, 28 Oct 2009 03:34:12 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id AFC4248A7D; Wed, 28 Oct 2009 03:34:11 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at tomjudge.vm.bytemark.co.uk Received: from tomjudge.vm.bytemark.co.uk ([127.0.0.1]) by localhost (tomjudge.vm.bytemark.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IV078jH4JqKS; Wed, 28 Oct 2009 03:34:06 +0000 (GMT) Received: from rita.nodomain (unknown [192.168.205.6]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 9162748A7C; Wed, 28 Oct 2009 03:34:05 +0000 (GMT) Message-ID: <4AE7BB7B.5060503@tomjudge.com> Date: Wed, 28 Oct 2009 03:33:15 +0000 From: Tom Judge User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: Steven Hartland References: <4AE72910.8090708@tomjudge.com><4AE753E4.6050205@tomjudge.com><20091028024916.2507b92d.stas@deglitch.com> <20091028031819.c965c22d.stas@deglitch.com> <43816B76DBB041EDBFFD09C5089B7F75@multiplay.co.uk> In-Reply-To: <43816B76DBB041EDBFFD09C5089B7F75@multiplay.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: David Christensen , Stanislav Sedov , net@freebsd.org Subject: Re: bce(4) BCM5907 CTX write errors on 7.2 driver 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, 28 Oct 2009 03:34:13 -0000 Steven Hartland wrote: > > On Tue, 27 Oct 2009 23:02:09 -0000 > "Steven Hartland" mentioned: > >> If I understand the PR comments right, the code to support this PHY >> should be present in 8.0. So you can start by trying out 8.0-RC1 >> ISO image (or USB stick image, fwiw). > > Just tried 8.0RC2 no go, PHY still not supported :( > Looking though the mii code it seems the SerDes PHY support was moved into the brgphy code in 2007. This driver however only seems to support the 5708S PHY and not the 5709. Maybe David can shed some light on the support for this. Tom From owner-freebsd-net@FreeBSD.ORG Wed Oct 28 08:21:23 2009 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 DD3E21065679; Wed, 28 Oct 2009 08:21:23 +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 B4CC68FC1E; Wed, 28 Oct 2009 08:21:23 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9S8LNRL073431; Wed, 28 Oct 2009 08:21:23 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9S8LNY8073427; Wed, 28 Oct 2009 08:21:23 GMT (envelope-from linimon) Date: Wed, 28 Oct 2009 08:21:23 GMT Message-Id: <200910280821.n9S8LNY8073427@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/140036: [iwn] [lor] lock order reversal with iwn0_com_lock and iwn0 softc lock 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, 28 Oct 2009 08:21:24 -0000 Old Synopsis: lock order reversal with iwn0_com_lock and iwn0 softc lock New Synopsis: [iwn] [lor] lock order reversal with iwn0_com_lock and iwn0 softc lock Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Wed Oct 28 08:20:57 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=140036 From owner-freebsd-net@FreeBSD.ORG Wed Oct 28 09:31:50 2009 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 6F25F1065694 for ; Wed, 28 Oct 2009 09:31:50 +0000 (UTC) (envelope-from Ivor.Prebeg@fer.hr) Received: from labs3.cc.fer.hr (labs3.cc.fer.hr [161.53.72.21]) by mx1.freebsd.org (Postfix) with ESMTP id 067578FC1B for ; Wed, 28 Oct 2009 09:31:49 +0000 (UTC) Received: from sluga.fer.hr (sluga.cc.fer.hr [161.53.72.14]) by labs3.cc.fer.hr (8.13.8+Sun/8.12.10) with ESMTP id n9S99xi3025725 for ; Wed, 28 Oct 2009 10:10:00 +0100 (CET) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 28 Oct 2009 10:09:59 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: LINKSYS WUSB600N, 802.11a/b/g Thread-Index: AcpXrmzykFPsxwH5Sm20tq5MwLZe1g== From: "Ivor Prebeg" To: X-Mailman-Approved-At: Wed, 28 Oct 2009 11:26:04 +0000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: LINKSYS WUSB600N, 802.11a/b/g 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, 28 Oct 2009 09:31:50 -0000 Does anyone know if this usb wifi adapter [LINKSYS WUSB600N, = 802.11a/b/g] works with -CURRENT or 8.0-RC? Thanks Ivor From owner-freebsd-net@FreeBSD.ORG Wed Oct 28 12:11:18 2009 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 8D2B01065696; Wed, 28 Oct 2009 12:11:18 +0000 (UTC) (envelope-from brueffer@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 624028FC12; Wed, 28 Oct 2009 12:11:18 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9SCBIXt074494; Wed, 28 Oct 2009 12:11:18 GMT (envelope-from brueffer@freefall.freebsd.org) Received: (from brueffer@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9SCBI9L074490; Wed, 28 Oct 2009 13:11:18 +0100 (CET) (envelope-from brueffer) Date: Wed, 28 Oct 2009 13:11:18 +0100 (CET) Message-Id: <200910281211.n9SCBI9L074490@freefall.freebsd.org> To: argp@census-labs.com, brueffer@FreeBSD.org, freebsd-net@FreeBSD.org, brueffer@FreeBSD.org From: brueffer@FreeBSD.org Cc: Subject: Re: kern/138130: [netinet] [patch] Resource leak in LibAliasRefreshModules() in file sys/netinet/libalias/alias.c 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, 28 Oct 2009 12:11:18 -0000 Synopsis: [netinet] [patch] Resource leak in LibAliasRefreshModules() in file sys/netinet/libalias/alias.c State-Changed-From-To: open->patched State-Changed-By: brueffer State-Changed-When: Wed Oct 28 13:10:37 CET 2009 State-Changed-Why: Committed, thanks! Responsible-Changed-From-To: freebsd-net->brueffer Responsible-Changed-By: brueffer Responsible-Changed-When: Wed Oct 28 13:10:37 CET 2009 Responsible-Changed-Why: MFC reminder. http://www.freebsd.org/cgi/query-pr.cgi?pr=138130 From owner-freebsd-net@FreeBSD.ORG Wed Oct 28 14:35:11 2009 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 032991065676 for ; Wed, 28 Oct 2009 14:35:11 +0000 (UTC) (envelope-from ml@netfence.it) Received: from cp-out8.libero.it (cp-out8.libero.it [212.52.84.108]) by mx1.freebsd.org (Postfix) with ESMTP id BAF468FC1E for ; Wed, 28 Oct 2009 14:35:10 +0000 (UTC) Received: from soth.ventu (151.51.2.140) by cp-out8.libero.it (8.5.107) id 4AE637A60040E67E for freebsd-net@freebsd.org; Wed, 28 Oct 2009 15:35:09 +0100 Received: from alamar.ventu (alamar.ventu [10.1.2.18]) by soth.ventu (8.14.3/8.14.2) with ESMTP id n9SEZ8Kr020580 for ; Wed, 28 Oct 2009 15:35:08 +0100 (CET) (envelope-from ml@netfence.it) Message-ID: <4AE8569C.1040209@netfence.it> Date: Wed, 28 Oct 2009 15:35:08 +0100 From: Andrea Venturoli User-Agent: Thunderbird 2.0.0.23 (X11/20090828) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: snort on multiple interfaces 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, 28 Oct 2009 14:35:11 -0000 Some years ago, I checked to see whether I would be able to let a single snort process listen on more than one NIC. At the time it was only possible in Linux. Now, I searched a bit, but nothing new came up. Did anything improve since then? Do we still need multiple snort processes to listen on more than one interface? Can some netgraph node help with this? bye & Thanks av. From owner-freebsd-net@FreeBSD.ORG Wed Oct 28 14:43:02 2009 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 9D7901065692 for ; Wed, 28 Oct 2009 14:43:02 +0000 (UTC) (envelope-from sh@keff.org) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 3B2C48FC1F for ; Wed, 28 Oct 2009 14:43:01 +0000 (UTC) Received: by bwz5 with SMTP id 5so1086520bwz.3 for ; Wed, 28 Oct 2009 07:43:01 -0700 (PDT) Received: by 10.204.20.143 with SMTP id f15mr3758587bkb.49.1256739527979; Wed, 28 Oct 2009 07:18:47 -0700 (PDT) Received: from ?10.156.17.105? (workstation1.tele2.se [192.71.219.1]) by mx.google.com with ESMTPS id 26sm1792161fks.2.2009.10.28.07.18.42 (version=SSLv3 cipher=RC4-MD5); Wed, 28 Oct 2009 07:18:43 -0700 (PDT) Message-ID: <4AE852C1.8090103@keff.org> Date: Wed, 28 Oct 2009 15:18:41 +0100 From: Sebastian Hyrwall User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Hi. Regarding "automatic vlan creation" 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, 28 Oct 2009 14:43:02 -0000 Hi Now that FreeBSD has support for writing , cloned_interfaces="em0.100" instead of having to create for example a vlan0 and then specify vlandev etc in ifconfig. What is the correct ifconfig-line in rc.conf for this? ifconfig_em0.100="" or ifconfig_em0_100="" does not work. Sincerely, Sebastian H From owner-freebsd-net@FreeBSD.ORG Wed Oct 28 14:43:29 2009 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 3A486106568B for ; Wed, 28 Oct 2009 14:43:29 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id CE3B48FC15 for ; Wed, 28 Oct 2009 14:43:28 +0000 (UTC) Received: by mail-bw0-f213.google.com with SMTP id 5so1086520bwz.3 for ; Wed, 28 Oct 2009 07:43:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.14.83 with SMTP id f19mr1389467faa.92.1256741008290; Wed, 28 Oct 2009 07:43:28 -0700 (PDT) In-Reply-To: <4AE8569C.1040209@netfence.it> References: <4AE8569C.1040209@netfence.it> From: Vlad Galu Date: Wed, 28 Oct 2009 16:43:08 +0200 Message-ID: To: Andrea Venturoli Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org Subject: Re: snort on multiple interfaces 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, 28 Oct 2009 14:43:29 -0000 On Wed, Oct 28, 2009 at 4:35 PM, Andrea Venturoli wrote: > Some years ago, I checked to see whether I would be able to let a single > snort process listen on more than one NIC. > At the time it was only possible in Linux. > In Linux the packet capture facility is implemented in a different (and very inefficient manner), via raw sockets (which means that, in order to reach userspace, a packet has to travel the whole IP stack - including firewall - until delivery to the user process). BSD has BPF, which basically delivers a copy of the packet to the userspace right before it enters the IP stack for kernel processing. Each network driver does this through the BPF_TAP() macro. > Now, I searched a bit, but nothing new came up. > > Did anything improve since then? Do we still need multiple snort processe= s > to listen on more than one interface? > Can some netgraph node help with this? You can try lagg(4) with the "loadbalance" option, ng_one2many(4), or ng_fec(4). > > =A0bye & Thanks > =A0 =A0 =A0 =A0av. > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Wed Oct 28 14:48:27 2009 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 E3A741065670 for ; Wed, 28 Oct 2009 14:48:27 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from tomjudge.vm.bytemark.co.uk (tomjudge.vm.bytemark.co.uk [80.68.91.100]) by mx1.freebsd.org (Postfix) with ESMTP id A557A8FC16 for ; Wed, 28 Oct 2009 14:48:27 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id B7D4348A7D; Wed, 28 Oct 2009 14:48:26 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at tomjudge.vm.bytemark.co.uk Received: from tomjudge.vm.bytemark.co.uk ([127.0.0.1]) by localhost (tomjudge.vm.bytemark.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eaGG+uj1vKHo; Wed, 28 Oct 2009 14:48:23 +0000 (GMT) Received: from rita.nodomain (unknown [192.168.205.6]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 6FDD848A7C; Wed, 28 Oct 2009 14:48:23 +0000 (GMT) Message-ID: <4AE85985.5080206@tomjudge.com> Date: Wed, 28 Oct 2009 14:47:33 +0000 From: Tom Judge User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: Andrea Venturoli References: <4AE8569C.1040209@netfence.it> In-Reply-To: <4AE8569C.1040209@netfence.it> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: snort on multiple interfaces 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, 28 Oct 2009 14:48:28 -0000 Andrea Venturoli wrote: > Some years ago, I checked to see whether I would be able to let a > single snort process listen on more than one NIC. > At the time it was only possible in Linux. > > Now, I searched a bit, but nothing new came up. > > Did anything improve since then? Do we still need multiple snort > processes to listen on more than one interface? > Can some netgraph node help with this? > You can do this using if_bridge in monitor mode like so: {/etc/rc.conf} ## DMZ Span Port cloned_interfaces="bridge0" ifconfig_fxp0="up promisc" ifconfig_fxp1="up promisc" ifconfig_bridge0="addm fxp0 addm fxp1 monitor up" And then have you snort process run on bridge0. Tom From owner-freebsd-net@FreeBSD.ORG Wed Oct 28 15:00:51 2009 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 5F4471065676 for ; Wed, 28 Oct 2009 15:00:51 +0000 (UTC) (envelope-from artis.caune@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id E56928FC16 for ; Wed, 28 Oct 2009 15:00:50 +0000 (UTC) Received: by bwz5 with SMTP id 5so1105812bwz.3 for ; Wed, 28 Oct 2009 08:00:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=+s5FSfuXbSW2cQk2TAOVKGjKKqHbcpj52WRnl4xl0jM=; b=ANX3XA/j8we0QLtTnDR6dvvpdUpeb1QzkYxb+AMRmy/IWveOajbl+IgzmVVLT/2pcg BRg80EFSjQMRRYaLTz3Q/vFW7wNcKbdL7Vc3QJH4lUAvQZhVal5oNoQx9ZxAfUjiXdu4 gEtwtmBqE45VEI0GCviGqm2Jh/njI70dQVOEo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ozYvGXBTqL+Lzux02zjoOPSxu3sjUIM9qQcOTQqKsUvvoumDjvnksJzx5LqhEvfTE3 DdxElnvamdv0lxm+2cWH/MpojT+4ibH1Z6w3c5horKmiPIY/YYOCPoUhn77AadrSyi92 pQCs9CJZKzjlH9ltDu+URtCpLvQSaWdr4x4Ic= MIME-Version: 1.0 Received: by 10.204.151.208 with SMTP id d16mr739175bkw.115.1256742049741; Wed, 28 Oct 2009 08:00:49 -0700 (PDT) In-Reply-To: <4AE852C1.8090103@keff.org> References: <4AE852C1.8090103@keff.org> Date: Wed, 28 Oct 2009 17:00:49 +0200 Message-ID: <9e20d71e0910280800q212d0235p8d7c7c4e07a8c9b6@mail.gmail.com> From: Artis Caune To: Sebastian Hyrwall Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org Subject: Re: Hi. Regarding "automatic vlan creation" 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, 28 Oct 2009 15:00:51 -0000 2009/10/28 Sebastian Hyrwall : > Hi > > Now that FreeBSD has support for writing =C2=A0, cloned_interfaces=3D"em0= .100" > instead of having to create for example a vlan0 and then specify vlandev = etc > in ifconfig. What is the correct ifconfig-line in rc.conf for this? > > ifconfig_em0.100=3D"" or ifconfig_em0_100=3D"" does not work. You probably forgot to put if_vlan_load=3D"YES" in /boot/loader.conf ifconfig_em0_100=3D"..." should work. --=20 Artis Caune Everything should be made as simple as possible, but not simpler. From owner-freebsd-net@FreeBSD.ORG Wed Oct 28 15:25:40 2009 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 24D0D1065676 for ; Wed, 28 Oct 2009 15:25:40 +0000 (UTC) (envelope-from sh@keff.org) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id B31658FC15 for ; Wed, 28 Oct 2009 15:25:39 +0000 (UTC) Received: by bwz5 with SMTP id 5so1134286bwz.3 for ; Wed, 28 Oct 2009 08:25:38 -0700 (PDT) Received: by 10.204.20.82 with SMTP id e18mr585889bkb.168.1256743538400; Wed, 28 Oct 2009 08:25:38 -0700 (PDT) Received: from ?10.156.17.105? (workstation1.tele2.se [192.71.219.1]) by mx.google.com with ESMTPS id 1sm1922468fkt.11.2009.10.28.08.25.35 (version=SSLv3 cipher=RC4-MD5); Wed, 28 Oct 2009 08:25:37 -0700 (PDT) Message-ID: <4AE8626E.8080505@keff.org> Date: Wed, 28 Oct 2009 16:25:34 +0100 From: Sebastian Hyrwall User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Artis Caune References: <4AE852C1.8090103@keff.org> <9e20d71e0910280800q212d0235p8d7c7c4e07a8c9b6@mail.gmail.com> In-Reply-To: <9e20d71e0910280800q212d0235p8d7c7c4e07a8c9b6@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Hi. Regarding "automatic vlan creation" 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, 28 Oct 2009 15:25:40 -0000 Hi. Ah ok. Well I did add that but maybe there was a typo somewhere else. Unfortuently I can't reach the server anymore (i wonder why heh ;) so I gave this email a try before going to the datacenter to fix it. Thanks for the input. Artis Caune skrev: > 2009/10/28 Sebastian Hyrwall : > >> Hi >> >> Now that FreeBSD has support for writing , cloned_interfaces="em0.100" >> instead of having to create for example a vlan0 and then specify vlandev etc >> in ifconfig. What is the correct ifconfig-line in rc.conf for this? >> >> ifconfig_em0.100="" or ifconfig_em0_100="" does not work. >> > > You probably forgot to put if_vlan_load="YES" in /boot/loader.conf > ifconfig_em0_100="..." should work. > > > > > From owner-freebsd-net@FreeBSD.ORG Wed Oct 28 14:46:12 2009 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 7B87B1065670 for ; Wed, 28 Oct 2009 14:46:12 +0000 (UTC) (envelope-from glenbarner@australia.edu) Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by mx1.freebsd.org (Postfix) with ESMTP id 614CA8FC12 for ; Wed, 28 Oct 2009 14:46:12 +0000 (UTC) Received: by pwj8 with SMTP id 8so870847pwj.3 for ; Wed, 28 Oct 2009 07:46:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.142.6.2 with SMTP id 2mr1060423wff.90.1256739189587; Wed, 28 Oct 2009 07:13:09 -0700 (PDT) Date: Wed, 28 Oct 2009 22:13:09 +0800 Message-ID: <5794edfe0910280713i68dbe43cxc40ced80bd0bf372@mail.gmail.com> From: glenn Barber To: freebsd-net@freebsd.org X-Mailman-Approved-At: Wed, 28 Oct 2009 15:44:48 +0000 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: 82575 NIC can't work with LAGG 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, 28 Oct 2009 14:46:12 -0000 In FreeBSD 8.0-RC1, igb can't work with lagg, however, em(82571) works. Is there something weird with igb driver? From owner-freebsd-net@FreeBSD.ORG Wed Oct 28 16:27:38 2009 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 B6EF8106566C for ; Wed, 28 Oct 2009 16:27:38 +0000 (UTC) (envelope-from jon@witchspace.com) Received: from queueout04-winn.ispmail.ntl.com (queueout04-winn.ispmail.ntl.com [81.103.221.58]) by mx1.freebsd.org (Postfix) with ESMTP id 0EC208FC1B for ; Wed, 28 Oct 2009 16:27:37 +0000 (UTC) Received: from aamtaout03-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout03-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20091028160542.MXJZ17277.mtaout03-winn.ispmail.ntl.com@aamtaout03-winn.ispmail.ntl.com> for ; Wed, 28 Oct 2009 16:05:42 +0000 Received: from witchspace.com ([82.15.251.148]) by aamtaout03-winn.ispmail.ntl.com (InterMail vG.2.02.00.01 201-2161-120-102-20060912) with SMTP id <20091028160542.JQFI2093.aamtaout03-winn.ispmail.ntl.com@witchspace.com> for ; Wed, 28 Oct 2009 16:05:42 +0000 Received: (qmail 9270 invoked from network); 28 Oct 2009 15:06:28 -0000 Received: from unknown (HELO core.home) (192.168.0.3) by 192.168.0.100 with SMTP; 28 Oct 2009 15:06:28 -0000 From: Jonathan Belson Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Date: Wed, 28 Oct 2009 16:05:40 +0000 Message-Id: <75F8B8C2-2BFE-434A-9E16-C34CAAF6C6E9@witchspace.com> To: freebsd-net@freebsd.org Mime-Version: 1.0 (Apple Message framework v1076) X-Mailer: Apple Mail (2.1076) X-Cloudmark-Analysis: v=1.0 c=1 a=INSGmp8vWH3cW5sZ1C4A:9 a=2eBDFmqfeI5k-685MksIHgqgsbkA:4 Subject: PF and DHCP 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, 28 Oct 2009 16:27:38 -0000 Hiya I have a server which acts as a gateway between the internet and my internal network. The external interface receives its IP address via DHCP. I set up pf.conf to allow DHCP packets via ports 67/68, but I notice that when the server boots, the DHCP exchange happens /before/ PF gets started. Does this mean that adding rules for DHCP isn't necessary (my firewall rules are block in/pass out, with a bit of NAT thrown in)? Does this mean that when my machine boots, there's a window between the interfaces coming up and the firewall being enabled? Thanks, --Jon From owner-freebsd-net@FreeBSD.ORG Wed Oct 28 16:33:33 2009 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 02405106566B for ; Wed, 28 Oct 2009 16:33:33 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: from acm.poly.edu (acm.poly.edu [128.238.9.200]) by mx1.freebsd.org (Postfix) with ESMTP id 958EA8FC20 for ; Wed, 28 Oct 2009 16:33:30 +0000 (UTC) Received: (qmail 47816 invoked from network); 28 Oct 2009 16:33:30 -0000 Received: from unknown (HELO ?10.0.0.158?) (spawk@128.238.64.31) by acm.poly.edu with AES256-SHA encrypted SMTP; 28 Oct 2009 16:33:30 -0000 Message-ID: <4AE8724F.50702@acm.poly.edu> Date: Wed, 28 Oct 2009 12:33:19 -0400 From: Boris Kochergin User-Agent: Thunderbird 2.0.0.23 (X11/20090910) MIME-Version: 1.0 To: Jonathan Belson References: <75F8B8C2-2BFE-434A-9E16-C34CAAF6C6E9@witchspace.com> In-Reply-To: <75F8B8C2-2BFE-434A-9E16-C34CAAF6C6E9@witchspace.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: PF and DHCP 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, 28 Oct 2009 16:33:33 -0000 Jonathan Belson wrote: > Hiya > > I have a server which acts as a gateway between the internet and my > internal network. The external interface receives its IP address via > DHCP. I set up pf.conf to allow DHCP packets via ports 67/68, but I > notice that when the server boots, the DHCP exchange happens /before/ > PF gets started. > > Does this mean that adding rules for DHCP isn't necessary (my firewall > rules are block in/pass out, with a bit of NAT thrown in)? To address just this question, it is a good idea to leave the rules that allow DHCP in there, as the DHCP client will need to renew its lease later, while the firewall is running. -Boris > Does this mean that when my machine boots, there's a window between > the interfaces coming up and the firewall being enabled? > > Thanks, > > --Jon > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Wed Oct 28 16:44:48 2009 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 D0C4A106566C for ; Wed, 28 Oct 2009 16:44:48 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (lor.one-eyed-alien.net [69.66.77.232]) by mx1.freebsd.org (Postfix) with ESMTP id 8BF7F8FC15 for ; Wed, 28 Oct 2009 16:44:48 +0000 (UTC) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.3/8.14.3) with ESMTP id n9SGhV8O071460; Wed, 28 Oct 2009 11:43:32 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.3/8.14.3/Submit) id n9SGhViB071459; Wed, 28 Oct 2009 11:43:31 -0500 (CDT) (envelope-from brooks) Date: Wed, 28 Oct 2009 11:43:30 -0500 From: Brooks Davis To: Sebastian Hyrwall Message-ID: <20091028164330.GA71430@lor.one-eyed-alien.net> References: <4AE852C1.8090103@keff.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AqsLC8rIMeq19msA" Content-Disposition: inline In-Reply-To: <4AE852C1.8090103@keff.org> User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Wed, 28 Oct 2009 11:43:32 -0500 (CDT) Cc: freebsd-net@freebsd.org Subject: Re: Hi. Regarding "automatic vlan creation" 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, 28 Oct 2009 16:44:48 -0000 --AqsLC8rIMeq19msA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 28, 2009 at 03:18:41PM +0100, Sebastian Hyrwall wrote: > Hi >=20 > Now that FreeBSD has support for writing , cloned_interfaces=3D"em0.100"= =20 > instead of having to create for example a vlan0 and then specify vlandev= =20 > etc in ifconfig. What is the correct ifconfig-line in rc.conf for this? >=20 > ifconfig_em0.100=3D"" or ifconfig_em0_100=3D"" does not work. It should be ifconfig_em0_100. -- Brooks --AqsLC8rIMeq19msA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iD8DBQFK6HSyXY6L6fI4GtQRAhI9AKDWNvForOWmodZgAPx6cBhPAxJgogCdHrsV Eb5ELRO7zONpEiPq/vnUigY= =AeHi -----END PGP SIGNATURE----- --AqsLC8rIMeq19msA-- From owner-freebsd-net@FreeBSD.ORG Wed Oct 28 18:23:29 2009 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 81CAD1065676 for ; Wed, 28 Oct 2009 18:23:29 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello089077035009.chello.pl [89.77.35.9]) by mx1.freebsd.org (Postfix) with ESMTP id 14B2E8FC1E for ; Wed, 28 Oct 2009 18:23:29 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 7201645CA0; Wed, 28 Oct 2009 18:54:39 +0100 (CET) Received: from localhost (chello089077035009.chello.pl [89.77.35.9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id E47F745B36; Wed, 28 Oct 2009 18:54:33 +0100 (CET) Date: Wed, 28 Oct 2009 18:54:33 +0100 From: Pawel Jakub Dawidek To: "Arno J. Klaassen" Message-ID: <20091028175433.GA1671@garage.freebsd.pl> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GvXjxJ+pjyke8COw" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-fs@freebsd.org, freebsd-net@freebsd.org Subject: Re: ZFS and 'traditional' nfs-export 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, 28 Oct 2009 18:23:29 -0000 --GvXjxJ+pjyke8COw Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 27, 2009 at 12:46:00AM +0100, Arno J. Klaassen wrote: >=20 > Hello, >=20 > I googled a bit on this question but could not find > a clear answer : >=20 > is there any risk/inconvenience/advantage in exporting > a ZFS-fs by just putting it in /etc/exports the old > way and leaving the 'sharenfs' option on the filesystem off? >=20 > I'd like to replace a UFS-based server serving mostly > linux-clients which work well now with a ZFS-fs, and somehow > am a bit waterfearing changing the nfs=E8options which worked > great till now. You can safely use /etc/exports without touching sharenfs property. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --GvXjxJ+pjyke8COw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFK6IVZForvXbEpPzQRAqVPAJkB5FeDxQwhxGdst8ZmO6R2/PEBCQCfQpoz EskaPcrzoAlTe+MxDPrNkO0= =Gb2R -----END PGP SIGNATURE----- --GvXjxJ+pjyke8COw-- From owner-freebsd-net@FreeBSD.ORG Wed Oct 28 18:37:51 2009 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 E12041065670; Wed, 28 Oct 2009 18:37: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 B89578FC1A; Wed, 28 Oct 2009 18:37:51 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9SIbpoB001979; Wed, 28 Oct 2009 18:37:51 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9SIbpaI001975; Wed, 28 Oct 2009 18:37:51 GMT (envelope-from linimon) Date: Wed, 28 Oct 2009 18:37:51 GMT Message-Id: <200910281837.n9SIbpaI001975@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/140051: [bce] [arp] ARP not sent through Bridge Firewall with BCE network dirver 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, 28 Oct 2009 18:37:52 -0000 Old Synopsis: ARP not sent through Bridge Firewall with BCE network dirver New Synopsis: [bce] [arp] ARP not sent through Bridge Firewall with BCE network dirver Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Wed Oct 28 18:37:36 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=140051 From owner-freebsd-net@FreeBSD.ORG Wed Oct 28 22:31:55 2009 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 2577F106568D for ; Wed, 28 Oct 2009 22:31:55 +0000 (UTC) (envelope-from artis.caune@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 9E51F8FC1F for ; Wed, 28 Oct 2009 22:31:54 +0000 (UTC) Received: by bwz5 with SMTP id 5so1613028bwz.3 for ; Wed, 28 Oct 2009 15:31:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=5Cuueg68ZEW7vUTBPC7DDotzstonzqEjTMXMvbWwWc0=; b=Nt+o6h4/ORcm/qGk7blj9Cz8RNS0c2jp2kjxZwo3H4+CxdrqMVnrn8Q7ESkTCFa9zU gYaSPKZW9PsU2KrEGN2rjgI5e91i6aPmzf81VlGpPIUf9+jVyiNFWL1l/YQTFnc3sO43 ueszXlXxpO0dN90/09F6GUaYSP5lUH3rmSWDE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=IZx+xjh+WZCcsreSqgX3BkLjO1FOTNRLrLwT+nLvjg1T4y8aYUEcpkFzhAe6v/QCKW S6g6fqE4M72Dm+XRru33pswtHmZa6viPDCn5mwrBwOzuYyjRzOIZTbbYB2PwVm97lwFn MD26gVJvoF0527buikQQEbH2fbO3uFINj+zyo= MIME-Version: 1.0 Received: by 10.204.34.78 with SMTP id k14mr1253247bkd.106.1256769109916; Wed, 28 Oct 2009 15:31:49 -0700 (PDT) In-Reply-To: <20091028164330.GA71430@lor.one-eyed-alien.net> References: <4AE852C1.8090103@keff.org> <20091028164330.GA71430@lor.one-eyed-alien.net> Date: Thu, 29 Oct 2009 00:31:49 +0200 Message-ID: <9e20d71e0910281531o56d82709ife0b76a59bff5f23@mail.gmail.com> From: Artis Caune To: Brooks Davis Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Sebastian Hyrwall , freebsd-net@freebsd.org Subject: Re: Hi. Regarding "automatic vlan creation" 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, 28 Oct 2009 22:31:55 -0000 2009/10/28 Brooks Davis : > On Wed, Oct 28, 2009 at 03:18:41PM +0100, Sebastian Hyrwall wrote: >> Hi >> >> Now that FreeBSD has support for writing =C2=A0, cloned_interfaces=3D"em= 0.100" >> instead of having to create for example a vlan0 and then specify vlandev >> etc in ifconfig. What is the correct ifconfig-line in rc.conf for this? >> >> ifconfig_em0.100=3D"" or ifconfig_em0_100=3D"" does not work. > > It should be ifconfig_em0_100. btw, wouldn't it be nice not to bother with loader.conf when using . syntax? This patch will load if_vlan automatically in this case: --- sbin/ifconfig/ifconfig.c 2009-10-26 14:11:16 +0000 +++ sbin/ifconfig/ifconfig.c 2009-10-28 21:43:07 +0000 @@ -998,6 +998,10 @@ break; } + /* try to load vlan module if interface name is device.vlan_id */ + if (index(name, '.') !=3D NULL) + strlcpy(ifname, "vlan", sizeof(ifname)); + /* turn interface and unit into module name */ strcpy(ifkind, "if_"); strlcpy(ifkind + MOD_PREFIX_LEN, ifname, --=20 Artis Caune Everything should be made as simple as possible, but not simpler. From owner-freebsd-net@FreeBSD.ORG Wed Oct 28 22:58:25 2009 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 3CE461065670 for ; Wed, 28 Oct 2009 22:58:25 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from tomjudge.vm.bytemark.co.uk (tomjudge.vm.bytemark.co.uk [80.68.91.100]) by mx1.freebsd.org (Postfix) with ESMTP id EE15D8FC08 for ; Wed, 28 Oct 2009 22:58:24 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 06F5348A77; Wed, 28 Oct 2009 22:58:24 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at tomjudge.vm.bytemark.co.uk Received: from tomjudge.vm.bytemark.co.uk ([127.0.0.1]) by localhost (tomjudge.vm.bytemark.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p3DRz9MI2PNB; Wed, 28 Oct 2009 22:58:21 +0000 (GMT) Received: from rita.nodomain (unknown [192.168.205.6]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 704D048A6E; Wed, 28 Oct 2009 22:58:20 +0000 (GMT) Message-ID: <4AE8CC59.7020004@tomjudge.com> Date: Wed, 28 Oct 2009 22:57:29 +0000 From: Tom Judge User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: David Christensen References: <4AE72910.8090708@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B49180@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE76FF1.9010401@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B491AE@IRVEXCHCCR01.corp.ad.broadcom.com> In-Reply-To: <5D267A3F22FD854F8F48B3D2B52381933A04B491AE@IRVEXCHCCR01.corp.ad.broadcom.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "rwilliams@borderware.com" , Gideon Naim , "net@freebsd.org" Subject: Re: bce(4) BCM5907 CTX write errors on 7.2 driver 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, 28 Oct 2009 22:58:25 -0000 David Christensen wrote: >> Thanks for the rapid response. >> >> Dell have firmware 5.0.9 on their website here: http://tiny.cc/ex834 >> >> Will that work? > > Yes, that release does include a good version of BCM5709 bootcode (v5.06). > I couldn't really tell until I downloaded the file and looked at the > temporary files inside. Thanks for the link. > > After fighting with the update process for a bit and then learning about the live cycle manager I have managed to test the R610 with the 5.0.9 firmware. On the face of it, it seems that this resolves the issue. Tom From owner-freebsd-net@FreeBSD.ORG Wed Oct 28 23:10:05 2009 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 C6A8F1065694 for ; Wed, 28 Oct 2009 23:10:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B69888FC14 for ; Wed, 28 Oct 2009 23:10:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9SNA5nX032340 for ; Wed, 28 Oct 2009 23:10:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9SNA5Bu032339; Wed, 28 Oct 2009 23:10:05 GMT (envelope-from gnats) Date: Wed, 28 Oct 2009 23:10:05 GMT Message-Id: <200910282310.n9SNA5Bu032339@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Sten Spans Cc: Subject: Re: kern/139145: IPv6 blackhole / reject routes broken X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Sten Spans List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Oct 2009 23:10:05 -0000 The following reply was made to PR kern/139145; it has been noted by GNATS. From: Sten Spans To: FreeBSD-gnats-submit@FreeBSD.org Cc: Subject: Re: kern/139145: IPv6 blackhole / reject routes broken Date: Thu, 29 Oct 2009 00:05:45 +0100 (CET) On Fri, 25 Sep 2009, FreeBSD-gnats-submit@FreeBSD.org wrote: >> Category: kern >> Responsible: freebsd-bugs >> Synopsis: IPv6 blackhole / reject routes broken >> Arrival-Date: Fri Sep 25 22:50:01 UTC 2009 Not sure which commit fixed it but this issue seems to be fixed in 8.0-RC2: traceroute to 2a02:898:17:1234:: (2a02:898:17:1234::) from 2001:7b8:666:ffff:0:42ff:fe00:4, 30 hops max, 24 byte packets 1 gw.deepthought.blinkenlights.nl (2001:7b8:666:ffff::1) 0.292 ms 0.227 ms 0.193 ms 2 hobby-gw.jun1.galilei.network.bit.nl (2001:7b8:3:47::2) 0.357 ms 0.402 ms 0.461 ms 3 nikhef.ams-ix.ipv6.intouch.net (2001:7f8:1::a500:8954:1) 2.603 ms 2.494 ms 2.234 ms 4 2001:6e0:8954:205b:1::2 (2001:6e0:8954:205b:1::2) 5.103 ms 5.144 ms 5.829 ms 5 ge-0-0-1-0.dcg-1.ipv6.coloclue.net (2a02:898:0:301::a) 5.238 ms 6.026 ms 6.345 ms 6 eddie.blinkenlights.nl (2a02:898::74:2) 3.18 ms 3.158 ms 4.044 ms 7 * * * -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - Anthem From owner-freebsd-net@FreeBSD.ORG Thu Oct 29 00:09:40 2009 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 523CC1065697; Thu, 29 Oct 2009 00:09:40 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (lor.one-eyed-alien.net [69.66.77.232]) by mx1.freebsd.org (Postfix) with ESMTP id D6AD08FC22; Thu, 29 Oct 2009 00:09:39 +0000 (UTC) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.3/8.14.3) with ESMTP id n9T08N9m075048; Wed, 28 Oct 2009 19:08:23 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.3/8.14.3/Submit) id n9T08NSx075046; Wed, 28 Oct 2009 19:08:23 -0500 (CDT) (envelope-from brooks) Date: Wed, 28 Oct 2009 19:08:22 -0500 From: Brooks Davis To: Artis Caune Message-ID: <20091029000822.GA74744@lor.one-eyed-alien.net> References: <4AE852C1.8090103@keff.org> <20091028164330.GA71430@lor.one-eyed-alien.net> <9e20d71e0910281531o56d82709ife0b76a59bff5f23@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline In-Reply-To: <9e20d71e0910281531o56d82709ife0b76a59bff5f23@mail.gmail.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Wed, 28 Oct 2009 19:08:24 -0500 (CDT) Cc: Sebastian Hyrwall , freebsd-net@freebsd.org, Brooks Davis Subject: Re: Hi. Regarding "automatic vlan creation" 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, 29 Oct 2009 00:09:40 -0000 --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 29, 2009 at 12:31:49AM +0200, Artis Caune wrote: > 2009/10/28 Brooks Davis : > > On Wed, Oct 28, 2009 at 03:18:41PM +0100, Sebastian Hyrwall wrote: > >> Hi > >> > >> Now that FreeBSD has support for writing ??, cloned_interfaces=3D"em0.= 100" > >> instead of having to create for example a vlan0 and then specify vland= ev > >> etc in ifconfig. What is the correct ifconfig-line in rc.conf for this? > >> > >> ifconfig_em0.100=3D"" or ifconfig_em0_100=3D"" does not work. > > > > It should be ifconfig_em0_100. >=20 > btw, wouldn't it be nice not to bother with loader.conf when using > . syntax? > This patch will load if_vlan automatically in this case: Sorry but my reation is: eww. There's no way I'd commit that. You'd be randomly loading the vlan code for any interface that had a dot in it. The real change we should make it to add device vlan to GENERIC. It's long past time for it to be in by default. -- Brooks > --- sbin/ifconfig/ifconfig.c 2009-10-26 14:11:16 +0000 > +++ sbin/ifconfig/ifconfig.c 2009-10-28 21:43:07 +0000 > @@ -998,6 +998,10 @@ > break; > } >=20 > + /* try to load vlan module if interface name is device.vlan_id */ > + if (index(name, '.') !=3D NULL) > + strlcpy(ifname, "vlan", sizeof(ifname)); > + > /* turn interface and unit into module name */ > strcpy(ifkind, "if_"); > strlcpy(ifkind + MOD_PREFIX_LEN, ifname, >=20 >=20 >=20 >=20 >=20 > --=20 > Artis Caune >=20 > Everything should be made as simple as possible, but not simpler. > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >=20 --T4sUOijqQbZv57TR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iD8DBQFK6Nz2XY6L6fI4GtQRAuwDAKDX4q0cJkdMV84GmYJasdvqWRmt6QCgutWi 50tqnMpMK1lUg2fGcxm4LVI= =i/pQ -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR-- From owner-freebsd-net@FreeBSD.ORG Thu Oct 29 00:10:04 2009 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 347E01065694 for ; Thu, 29 Oct 2009 00:10:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 09C788FC16 for ; Thu, 29 Oct 2009 00:10:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9T0A3uK083542 for ; Thu, 29 Oct 2009 00:10:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9T0A3cV083541; Thu, 29 Oct 2009 00:10:03 GMT (envelope-from gnats) Date: Thu, 29 Oct 2009 00:10:03 GMT Message-Id: <200910290010.n9T0A3cV083541@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Mark Atkinson Cc: Subject: Re: kern/124127: [msk] watchdog timeout (missed Tx interrupts) -- recovering X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mark Atkinson List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Oct 2009 00:10:04 -0000 The following reply was made to PR kern/124127; it has been noted by GNATS. From: Mark Atkinson To: freebsd prs Cc: Subject: Re: kern/124127: [msk] watchdog timeout (missed Tx interrupts) -- recovering Date: Wed, 28 Oct 2009 17:03:52 -0700 (PDT) =0A=0AOn the unpatched -current kernel, built=0A=0AFreeBSD hellfire.filamen= t.org 9.0-CURRENT FreeBSD 9.0-CURRENT #14: Mon Oct 19 09:12:03 PDT 2009 =0A= =0AI recieved the following panic today related to this:=0A=0AFatal trap 12= : page fault while in kernel mode=0Acpuid =3D 0; apic id =3D 00=0Afault vir= tual address =3D 0xdeadc10a=0Afault code =3D supervisor read= , page not present=0Ainstruction pointer =3D 0x20:0xc0987410=0Astack po= inter =3D 0x28:0xd533dac0=0Aframe pointer =3D 0x28:0xd5= 33dae8=0Acode segment =3D base 0x0, limit 0xfffff, type 0x1b=0A = =3D DPL 0, pres 1, def32 1, gran 1=0Aprocessor eflag= s =3D interrupt enabled, resume, IOPL =3D 0=0Acurrent process = =3D 0 (mskc0 taskq)=0APhysical memory: 495 MB=0ADumping 132 MB: 117 101 8= 5 69 53 37 21 5=0A=0AReading symbols from /boot/kernel/linux.ko...Reading s= ymbols from /boot/kernel/linux.ko.symbols...done.=0Adone.=0ALoaded symbols = for /boot/kernel/linux.ko=0A#0 0xc08907a9 in doadump () at /usr/src/sys/ke= rn/kern_shutdown.c:254=0A254 }=0A(kgdb) bt=0A#0 0xc08907a9 in doadump = () at /usr/src/sys/kern/kern_shutdown.c:254=0A#1 0xc04f7e37 in db_fncall (= dummy1=3D-1067299898, dummy2=3D0, dummy3=3D-718022488,=0A dummy4=3D0xd53= 3d898 "\200%t=C3") at /usr/src/sys/ddb/db_command.c:548=0A#2 0xc04f8214 in= db_command (last_cmdp=3D0xc0da059c, cmd_table=3D0x0, dopager=3D1)=0A at= /usr/src/sys/ddb/db_command.c:445=0A#3 0xc04f8352 in db_command_loop () a= t /usr/src/sys/ddb/db_command.c:498=0A#4 0xc04fa05e in db_trap (type=3D12,= code=3D0) at /usr/src/sys/ddb/db_main.c:229=0A#5 0xc08bf2d2 in kdb_reente= r () at /usr/src/sys/kern/subr_kdb.c:398=0A#6 0xc0ba9b62 in trap_fatal (fr= ame=3D0x1, eva=3D3735929098)=0A at /usr/src/sys/i386/i386/trap.c:938=0A#= 7 0xc0baa483 in trap (frame=3D0xd533da80) at /usr/src/sys/i386/i386/trap.c= :339=0A#8 0xc0b8e4ab in Xlcall_syscall () at /usr/src/sys/i386/i386/except= ion.s:241=0A#9 0xc0987410 in in_lltable_lookup (llt=3D0xc39e1000, flags=3D= Variable "flags" is not available.=0A)=0A at /usr/src/sys/netinet/in.c:1= 380=0A#10 0xc0982470 in arpintr (m=3D0xc3baeb00) at /usr/src/sys/netinet/if= _ether.c:642=0A#11 0xc094227a in netisr_dispatch_src (proto=3D7, source=3D0= , m=3D0xc0de)=0A at /usr/src/sys/net/netisr.c:932=0A#12 0xc09424dd in ne= tisr_unregister (nhp=3D0xc0de)=0A at /usr/src/sys/net/netisr.c:583=0A#13= 0xc093ac69 in ether_demux (ifp=3D0x0, m=3D0xc3baeb00)=0A at /usr/src/sy= s/net/if_ethersubr.c:911=0A#14 0xc093b1ce in ether_output (ifp=3D0xc36ad400= , m=3D0xc3baeb00, dst=3D0xc0c55c27,=0A ro=3D0x301010a) at /usr/src/sys/n= et/if_ethersubr.c:181=0A---Type to continue, or q to quit= ---=0A#15 0xc070b032 in msk_handle_events (sc=3D0xc3686c00)=0A at /usr/s= rc/sys/dev/msk/if_msk.c:3048=0A#16 0xc070b828 in msk_int_task (arg=3D0xc368= 6c00, pending=3D1)=0A at /usr/src/sys/dev/msk/if_msk.c:3625=0A#17 0xc08c= ac8c in taskqueue_run (queue=3D0xc36bf380)=0A at /usr/src/sys/kern/subr_= taskqueue.c:72=0A#18 0xc08cadcc in taskqueue_thread_loop (arg=3D0xc3686c8c)= =0A at /usr/src/sys/kern/subr_taskqueue.c:90=0A#19 0xc0869271 in fork_ex= it (callout=3D0xc08cad67 ,=0A arg=3D0xc3686c8c= , frame=3D0xd533dd38) at /usr/src/sys/kern/kern_fork.c:854=0A#20 0xc0b8e520= in Xatpic_intr0 () at atpic_vector.s:62=0A#21 0x00000000 in ?? ()=0A=0A=0A= From owner-freebsd-net@FreeBSD.ORG Thu Oct 29 01:44:36 2009 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 0E5131065679 for ; Thu, 29 Oct 2009 01:44:36 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.freebsd.org (Postfix) with ESMTP id D18E58FC12 for ; Thu, 29 Oct 2009 01:44:35 +0000 (UTC) Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id n9T1iTdo019768; Wed, 28 Oct 2009 18:44:29 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 28 Oct 2009 18:44:04 -0700 Message-ID: In-Reply-To: <200910282310.n9SNA5Bu032339@freefall.freebsd.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: kern/139145: IPv6 blackhole / reject routes broken Thread-Index: AcpYI9l11xTdbgUORT6ji/bK1+Fs9QAFIiSg References: <200910282310.n9SNA5Bu032339@freefall.freebsd.org> From: "Li, Qing" To: "Sten Spans" , Cc: Subject: RE: kern/139145: IPv6 blackhole / reject routes broken 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, 29 Oct 2009 01:44:36 -0000 I remember looking at this bug and tried to reproduce it ... If my memory serves me right, I believe this bug was fixed by=20 svn r197364, committed on 9/20. RC1 was built on 9/17. Another symptom of this bug is the "route get" command issued=20 on any lo0 addresses returns "destination: default" instead=20 of "destination: lo0". -- Qing > -----Original Message----- > From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd- > net@freebsd.org] On Behalf Of Sten Spans > Sent: Wednesday, October 28, 2009 4:10 PM > To: freebsd-net@freebsd.org > Subject: Re: kern/139145: IPv6 blackhole / reject routes broken >=20 > The following reply was made to PR kern/139145; it has been noted by > GNATS. >=20 > From: Sten Spans > To: FreeBSD-gnats-submit@FreeBSD.org > Cc: > Subject: Re: kern/139145: IPv6 blackhole / reject routes broken > Date: Thu, 29 Oct 2009 00:05:45 +0100 (CET) >=20 > On Fri, 25 Sep 2009, FreeBSD-gnats-submit@FreeBSD.org wrote: >=20 > >> Category: kern > >> Responsible: freebsd-bugs > >> Synopsis: IPv6 blackhole / reject routes broken > >> Arrival-Date: Fri Sep 25 22:50:01 UTC 2009 >=20 > Not sure which commit fixed it but this issue seems to > be fixed in 8.0-RC2: >=20 > traceroute to 2a02:898:17:1234:: (2a02:898:17:1234::) from > 2001:7b8:666:ffff:0:42ff:fe00:4, 30 hops max, 24 byte packets > 1 gw.deepthought.blinkenlights.nl (2001:7b8:666:ffff::1) 0.292 ms > 0.227 ms 0.193 ms > 2 hobby-gw.jun1.galilei.network.bit.nl (2001:7b8:3:47::2) 0.357 ms > 0.402 ms 0.461 ms > 3 nikhef.ams-ix.ipv6.intouch.net (2001:7f8:1::a500:8954:1) 2.603 > ms 2.494 ms 2.234 ms > 4 2001:6e0:8954:205b:1::2 (2001:6e0:8954:205b:1::2) 5.103 ms > 5.144 ms 5.829 ms > 5 ge-0-0-1-0.dcg-1.ipv6.coloclue.net (2a02:898:0:301::a) 5.238 ms > 6.026 ms 6.345 ms > 6 eddie.blinkenlights.nl (2a02:898::74:2) 3.18 ms 3.158 ms 4.044 > ms > 7 * * * >=20 > -- > Sten Spans >=20 > "There is a crack in everything, that's how the light gets in." > Leonard Cohen - Anthem > _______________________________________________ > 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 Oct 29 07:33:05 2009 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 40DE81065670; Thu, 29 Oct 2009 07:33:05 +0000 (UTC) (envelope-from sten@blinkenlights.nl) Received: from mx0.blinkenlights.nl (mx0.blinkenlights.nl [IPv6:2001:7b8:666:8000::25]) by mx1.freebsd.org (Postfix) with ESMTP id D45A88FC17; Thu, 29 Oct 2009 07:33:04 +0000 (UTC) Received: from bastard.snore.nl (bastard.snore.nl [IPv6:2001:7b8:666:ffff:0:42ff:fe00:4]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx0.blinkenlights.nl (Postfix) with ESMTPS id 3F8EBCF380; Thu, 29 Oct 2009 08:33:04 +0100 (CET) Received: by bastard.snore.nl (Postfix, from userid 1000) id 0895128A102; Thu, 29 Oct 2009 08:33:03 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by bastard.snore.nl (Postfix) with ESMTP id CA3E528A101; Thu, 29 Oct 2009 08:33:03 +0100 (CET) Date: Thu, 29 Oct 2009 08:33:03 +0100 (CET) From: Sten Spans X-X-Sender: sten@bastard.snore.nl To: "Li, Qing" In-Reply-To: Message-ID: References: <200910282310.n9SNA5Bu032339@freefall.freebsd.org> User-Agent: Alpine 0.99999 (DEB 796 2007-11-08) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, FreeBSD-gnats-submit@FreeBSD.org Subject: RE: kern/139145: IPv6 blackhole / reject routes broken 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, 29 Oct 2009 07:33:05 -0000 On Wed, 28 Oct 2009, Li, Qing wrote: > I remember looking at this bug and tried to reproduce it ... > > If my memory serves me right, I believe this bug was fixed by > svn r197364, committed on 9/20. RC1 was built on 9/17. > > Another symptom of this bug is the "route get" command issued > on any lo0 addresses returns "destination: default" instead > of "destination: lo0". That indeed looks like the culprit, thanks for fixing it. -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - Anthem From owner-freebsd-net@FreeBSD.ORG Thu Oct 29 07:40:02 2009 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 E9A791065679 for ; Thu, 29 Oct 2009 07:40:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8CCFE8FC16 for ; Thu, 29 Oct 2009 07:40:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9T7e2gV003930 for ; Thu, 29 Oct 2009 07:40:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9T7e2Au003929; Thu, 29 Oct 2009 07:40:02 GMT (envelope-from gnats) Date: Thu, 29 Oct 2009 07:40:02 GMT Message-Id: <200910290740.n9T7e2Au003929@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Sten Spans Cc: Subject: RE: kern/139145: IPv6 blackhole / reject routes broken X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Sten Spans List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Oct 2009 07:40:03 -0000 The following reply was made to PR kern/139145; it has been noted by GNATS. From: Sten Spans To: "Li, Qing" Cc: FreeBSD-gnats-submit@FreeBSD.org, freebsd-net@freebsd.org Subject: RE: kern/139145: IPv6 blackhole / reject routes broken Date: Thu, 29 Oct 2009 08:33:03 +0100 (CET) On Wed, 28 Oct 2009, Li, Qing wrote: > I remember looking at this bug and tried to reproduce it ... > > If my memory serves me right, I believe this bug was fixed by > svn r197364, committed on 9/20. RC1 was built on 9/17. > > Another symptom of this bug is the "route get" command issued > on any lo0 addresses returns "destination: default" instead > of "destination: lo0". That indeed looks like the culprit, thanks for fixing it. -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - Anthem From owner-freebsd-net@FreeBSD.ORG Thu Oct 29 07:40:04 2009 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 6BCEE106566B for ; Thu, 29 Oct 2009 07:40:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 41A728FC18 for ; Thu, 29 Oct 2009 07:40:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9T7e3oE003956 for ; Thu, 29 Oct 2009 07:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9T7e3nj003955; Thu, 29 Oct 2009 07:40:03 GMT (envelope-from gnats) Date: Thu, 29 Oct 2009 07:40:03 GMT Message-Id: <200910290740.n9T7e3nj003955@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Bernhard Schmidt Cc: Subject: Re: kern/140036: [iwn] [lor] lock order reversal with iwn0_com_lock and iwn0 softc lock X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bernhard Schmidt List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Oct 2009 07:40:04 -0000 The following reply was made to PR kern/140036; it has been noted by GNATS. From: Bernhard Schmidt To: bug-followup@freebsd.org, kaduk@mit.edu Cc: Subject: Re: kern/140036: [iwn] [lor] lock order reversal with iwn0_com_lock and iwn0 softc lock Date: Thu, 29 Oct 2009 08:19:44 +0100 Hi, Removing the IWN_LOCK(sc) leads to races when calling iwn_cmd(). It's better to drop the IEEE80211_LOCK(ic). I do have a patch in test which hopefully will hit the tree soon. -- Bernhard From owner-freebsd-net@FreeBSD.ORG Thu Oct 29 09:17:29 2009 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 3A888106566B; Thu, 29 Oct 2009 09:17:29 +0000 (UTC) (envelope-from artis.caune@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 945028FC1B; Thu, 29 Oct 2009 09:17:28 +0000 (UTC) Received: by bwz5 with SMTP id 5so2062158bwz.3 for ; Thu, 29 Oct 2009 02:17:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=NJK++usZ41zmm+NqIvDx+3JaHbj7z5CsghaZtMDWtuY=; b=IbIYE3VsR8FWCInOcOP/kcfAhPc94Tajiv0L67eEHb6dInbvwJLwHrlbdhrz68pg3+ kC9b0p6m782VNwKBUbnl0yU0INKqu/NIyN3m51Eo/FJk0xpQeYqLaiFDk7JU1HpuH+l+ jxxTYI61MS/kMCMslRLfV2HkFFQX5ORrfcR/g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=iLUT9isQOrNmTujZowU/sIw62tp4YXAypP5Q8z10/mruAXDoYNL3FldtKUdpLf6aX8 NkDeq0XX+qVKqN/jk+ZHm2Ij57e2A+t79scXwnHukPZCmDvyCn4PhqGciEiGM6HUSSkt Nu8+dgvoM70jY06bzxKvwRpN1IUfB2MizLo0o= MIME-Version: 1.0 Received: by 10.204.10.136 with SMTP id p8mr3107529bkp.56.1256807847192; Thu, 29 Oct 2009 02:17:27 -0700 (PDT) In-Reply-To: <20091029000822.GA74744@lor.one-eyed-alien.net> References: <4AE852C1.8090103@keff.org> <20091028164330.GA71430@lor.one-eyed-alien.net> <9e20d71e0910281531o56d82709ife0b76a59bff5f23@mail.gmail.com> <20091029000822.GA74744@lor.one-eyed-alien.net> Date: Thu, 29 Oct 2009 11:17:27 +0200 Message-ID: <9e20d71e0910290217k58493c3enb7dc303f50385533@mail.gmail.com> From: Artis Caune To: Brooks Davis Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Sebastian Hyrwall , freebsd-net@freebsd.org Subject: Re: Hi. Regarding "automatic vlan creation" 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, 29 Oct 2009 09:17:29 -0000 2009/10/29 Brooks Davis : >> btw, wouldn't it be nice not to bother with loader.conf when using >> . syntax? >> This patch will load if_vlan automatically in this case: > > Sorry but my reation is: eww. =C2=A0There's no way I'd commit that. =C2= =A0You'd be > randomly loading the vlan code for any interface that had a dot in it. You are right, forgot about 'ifconfig rename'. > The real change we should make it to add device vlan to GENERIC. =C2=A0It= 's > long past time for it to be in by default. It's even better, what's need to be done to move it to GENERIC? --=20 Artis Caune Everything should be made as simple as possible, but not simpler. From owner-freebsd-net@FreeBSD.ORG Thu Oct 29 13:53:02 2009 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 BF63E10656A3 for ; Thu, 29 Oct 2009 13:53:02 +0000 (UTC) (envelope-from freebsd-net@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 4F21F8FC2F for ; Thu, 29 Oct 2009 13:53:02 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1N3VQx-0000DH-6w for freebsd-net@freebsd.org; Thu, 29 Oct 2009 14:52:59 +0100 Received: from 207.155.204.151.ptr.us.xo.net ([207.155.204.151]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Oct 2009 14:52:59 +0100 Received: from atkin901 by 207.155.204.151.ptr.us.xo.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Oct 2009 14:52:59 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-net@freebsd.org From: Mark Atkinson Date: Thu, 29 Oct 2009 06:52:34 -0700 Lines: 88 Message-ID: References: <200910290010.n9T0A3cV083541@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 207.155.204.151.ptr.us.xo.net User-Agent: Thunderbird 2.0.0.23 (X11/20091009) In-Reply-To: <200910290010.n9T0A3cV083541@freefall.freebsd.org> Sender: news Subject: Re: kern/124127: [msk] watchdog timeout (missed Tx interrupts) -- recovering 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, 29 Oct 2009 13:53:02 -0000 Wow, not sure what to blame for that charset nightmare. Apologies. Here's the original message: On the unpatched -current kernel, built FreeBSD hellfire.filament.org 9.0-CURRENT FreeBSD 9.0-CURRENT #14: Mon Oct 19 09:12:03 PDT 2009 I recieved the following panic today related to this: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xdeadc10a fault code = supervisor read, page not present instruction pointer = 0x20:0xc0987410 stack pointer = 0x28:0xd533dac0 frame pointer = 0x28:0xd533dae8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (mskc0 taskq) Physical memory: 495 MB Dumping 132 MB: 117 101 85 69 53 37 21 5 Reading symbols from /boot/kernel/linux.ko...Reading symbols from /boot/kernel/linux.ko.symbols...done. done. Loaded symbols for /boot/kernel/linux.ko #0 0xc08907a9 in doadump () at /usr/src/sys/kern/kern_shutdown.c:254 254 } (kgdb) bt #0 0xc08907a9 in doadump () at /usr/src/sys/kern/kern_shutdown.c:254 #1 0xc04f7e37 in db_fncall (dummy1=-1067299898, dummy2=0, dummy3=-718022488, dummy4=0xd533d898 "\200%tÃ") at /usr/src/sys/ddb/db_command.c:548 #2 0xc04f8214 in db_command (last_cmdp=0xc0da059c, cmd_table=0x0, dopager=1) at /usr/src/sys/ddb/db_command.c:445 #3 0xc04f8352 in db_command_loop () at /usr/src/sys/ddb/db_command.c:498 #4 0xc04fa05e in db_trap (type=12, code=0) at /usr/src/sys/ddb/db_main.c:229 #5 0xc08bf2d2 in kdb_reenter () at /usr/src/sys/kern/subr_kdb.c:398 #6 0xc0ba9b62 in trap_fatal (frame=0x1, eva=3735929098) at /usr/src/sys/i386/i386/trap.c:938 #7 0xc0baa483 in trap (frame=0xd533da80) at /usr/src/sys/i386/i386/trap.c:339 #8 0xc0b8e4ab in Xlcall_syscall () at /usr/src/sys/i386/i386/exception.s:241 #9 0xc0987410 in in_lltable_lookup (llt=0xc39e1000, flags=Variable "flags" is not available. ) at /usr/src/sys/netinet/in.c:1380 #10 0xc0982470 in arpintr (m=0xc3baeb00) at /usr/src/sys/netinet/if_ether.c:642 #11 0xc094227a in netisr_dispatch_src (proto=7, source=0, m=0xc0de) at /usr/src/sys/net/netisr.c:932 #12 0xc09424dd in netisr_unregister (nhp=0xc0de) at /usr/src/sys/net/netisr.c:583 #13 0xc093ac69 in ether_demux (ifp=0x0, m=0xc3baeb00) at /usr/src/sys/net/if_ethersubr.c:911 #14 0xc093b1ce in ether_output (ifp=0xc36ad400, m=0xc3baeb00, dst=0xc0c55c27, ro=0x301010a) at /usr/src/sys/net/if_ethersubr.c:181 ---Type to continue, or q to quit--- #15 0xc070b032 in msk_handle_events (sc=0xc3686c00) at /usr/src/sys/dev/msk/if_msk.c:3048 #16 0xc070b828 in msk_int_task (arg=0xc3686c00, pending=1) at /usr/src/sys/dev/msk/if_msk.c:3625 #17 0xc08cac8c in taskqueue_run (queue=0xc36bf380) at /usr/src/sys/kern/subr_taskqueue.c:72 #18 0xc08cadcc in taskqueue_thread_loop (arg=0xc3686c8c) at /usr/src/sys/kern/subr_taskqueue.c:90 #19 0xc0869271 in fork_exit (callout=0xc08cad67 , arg=0xc3686c8c, frame=0xd533dd38) at /usr/src/sys/kern/kern_fork.c:854 #20 0xc0b8e520 in Xatpic_intr0 () at atpic_vector.s:62 #21 0x00000000 in ?? () Mark Atkinson wrote: > The following reply was made to PR kern/124127; it has been noted by GNATS. > > From: Mark Atkinson > To: freebsd prs > Cc: > Subject: Re: kern/124127: [msk] watchdog timeout (missed Tx interrupts) -- recovering > Date: Wed, 28 Oct 2009 17:03:52 -0700 (PDT) From owner-freebsd-net@FreeBSD.ORG Thu Oct 29 16:49:09 2009 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 DF711106566B; Thu, 29 Oct 2009 16:49:09 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.27]) by mx1.freebsd.org (Postfix) with ESMTP id 7C4F38FC21; Thu, 29 Oct 2009 16:49:09 +0000 (UTC) Received: by qw-out-2122.google.com with SMTP id 9so517354qwb.7 for ; Thu, 29 Oct 2009 09:49:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=sK9TSpL7gOS16/7T3zPXRmfm3rbrODv36ihxBPO4mOY=; b=iHEUJXl2G5VAJbolvIuoldmBn+wdDCD2lLPIIfzD6KGSlzBPMuow8I+IQfZCHoCITi HT+MZwDfCGl6nHoWjvE5Jq9GqVJZ4LeSKo8wETvsS+u1w3cr11Jaddt3Y0YGzWDCdubY 2nA+1Vw/jvaq7QmQlrmpPF0+BiBAzf6zuLTjo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=RcmwR+O7GKjbfqIRJnjbPZ6Dc2RMFuL95AoD15T7p9rriBX6JS+7U7SrDnFuGYKFQf SHMp+6tSFw0u+cgYxKEUl38zgNhyOA9kzZ3HAixQn/64aUr3Dl8+2CyVd9DaKlNj4SdP k7PKADD+4G+WMhuAvo7SrKEFvDpuNdmPsdFe0= Received: by 10.224.12.198 with SMTP id y6mr176066qay.207.1256834948553; Thu, 29 Oct 2009 09:49:08 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id 22sm1420051qyk.10.2009.10.29.09.49.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 29 Oct 2009 09:49:06 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Thu, 29 Oct 2009 09:49:09 -0700 From: Pyun YongHyeon Date: Thu, 29 Oct 2009 09:49:09 -0700 To: Mark Atkinson Message-ID: <20091029164909.GA13275@michelle.cdnetworks.com> References: <200910290010.n9T0A3cV083541@freefall.freebsd.org> 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, bug-followup@FreeBSD.org Subject: Re: kern/124127: [msk] watchdog timeout (missed Tx interrupts) -- recovering 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: Thu, 29 Oct 2009 16:49:10 -0000 On Thu, Oct 29, 2009 at 06:52:34AM -0700, Mark Atkinson wrote: > Wow, not sure what to blame for that charset nightmare. Apologies. > Here's the original message: > > On the unpatched -current kernel, built > > FreeBSD hellfire.filament.org 9.0-CURRENT FreeBSD 9.0-CURRENT #14: Mon > Oct 19 09:12:03 PDT 2009 > > I recieved the following panic today related to this: > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0xdeadc10a > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc0987410 > stack pointer = 0x28:0xd533dac0 > frame pointer = 0x28:0xd533dae8 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 0 (mskc0 taskq) > Physical memory: 495 MB > Dumping 132 MB: 117 101 85 69 53 37 21 5 > > Reading symbols from /boot/kernel/linux.ko...Reading symbols from > /boot/kernel/linux.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/linux.ko > #0 0xc08907a9 in doadump () at /usr/src/sys/kern/kern_shutdown.c:254 > 254 } > (kgdb) bt > #0 0xc08907a9 in doadump () at /usr/src/sys/kern/kern_shutdown.c:254 > #1 0xc04f7e37 in db_fncall (dummy1=-1067299898, dummy2=0, > dummy3=-718022488, > dummy4=0xd533d898 "\200%t?") at /usr/src/sys/ddb/db_command.c:548 > #2 0xc04f8214 in db_command (last_cmdp=0xc0da059c, cmd_table=0x0, > dopager=1) > at /usr/src/sys/ddb/db_command.c:445 > #3 0xc04f8352 in db_command_loop () at /usr/src/sys/ddb/db_command.c:498 > #4 0xc04fa05e in db_trap (type=12, code=0) at > /usr/src/sys/ddb/db_main.c:229 > #5 0xc08bf2d2 in kdb_reenter () at /usr/src/sys/kern/subr_kdb.c:398 > #6 0xc0ba9b62 in trap_fatal (frame=0x1, eva=3735929098) > at /usr/src/sys/i386/i386/trap.c:938 > #7 0xc0baa483 in trap (frame=0xd533da80) at > /usr/src/sys/i386/i386/trap.c:339 > #8 0xc0b8e4ab in Xlcall_syscall () at > /usr/src/sys/i386/i386/exception.s:241 > #9 0xc0987410 in in_lltable_lookup (llt=0xc39e1000, flags=Variable > "flags" is not available. > ) > at /usr/src/sys/netinet/in.c:1380 > #10 0xc0982470 in arpintr (m=0xc3baeb00) at > /usr/src/sys/netinet/if_ether.c:642 > #11 0xc094227a in netisr_dispatch_src (proto=7, source=0, m=0xc0de) > at /usr/src/sys/net/netisr.c:932 > #12 0xc09424dd in netisr_unregister (nhp=0xc0de) > at /usr/src/sys/net/netisr.c:583 > #13 0xc093ac69 in ether_demux (ifp=0x0, m=0xc3baeb00) > at /usr/src/sys/net/if_ethersubr.c:911 > #14 0xc093b1ce in ether_output (ifp=0xc36ad400, m=0xc3baeb00, > dst=0xc0c55c27, > ro=0x301010a) at /usr/src/sys/net/if_ethersubr.c:181 > ---Type to continue, or q to quit--- > #15 0xc070b032 in msk_handle_events (sc=0xc3686c00) > at /usr/src/sys/dev/msk/if_msk.c:3048 > #16 0xc070b828 in msk_int_task (arg=0xc3686c00, pending=1) > at /usr/src/sys/dev/msk/if_msk.c:3625 > #17 0xc08cac8c in taskqueue_run (queue=0xc36bf380) > at /usr/src/sys/kern/subr_taskqueue.c:72 > #18 0xc08cadcc in taskqueue_thread_loop (arg=0xc3686c8c) > at /usr/src/sys/kern/subr_taskqueue.c:90 > #19 0xc0869271 in fork_exit (callout=0xc08cad67 , > arg=0xc3686c8c, frame=0xd533dd38) at /usr/src/sys/kern/kern_fork.c:854 > #20 0xc0b8e520 in Xatpic_intr0 () at atpic_vector.s:62 > #21 0x00000000 in ?? () > I think it's not a bug of msk(4). Qin Li fixed the bug in arp code. See r198301. For watchdog timeout issues on 88E8053 controller, did you ever try disabling MSI? msk(4) was changed a lot since 7.0-RELEASE to support newer controllers and added several workarounds to address silicon bugs. So don't blindly apply experimental patches to your controller. 88E8053 also has a couple of hardware bugs but I guess msk(4) already incorporated required workarounds. So if you can reliably reproduce watchdog timeouts please let me know. From owner-freebsd-net@FreeBSD.ORG Thu Oct 29 16:50:03 2009 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 AD5381065670 for ; Thu, 29 Oct 2009 16:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 825D38FC13 for ; Thu, 29 Oct 2009 16:50:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9TGo29V087533 for ; Thu, 29 Oct 2009 16:50:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9TGo2Nj087532; Thu, 29 Oct 2009 16:50:02 GMT (envelope-from gnats) Date: Thu, 29 Oct 2009 16:50:02 GMT Message-Id: <200910291650.n9TGo2Nj087532@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Pyun YongHyeon Cc: Subject: Re: kern/124127: [msk] watchdog timeout (missed Tx interrupts) -- recovering X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Pyun YongHyeon List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Oct 2009 16:50:03 -0000 The following reply was made to PR kern/124127; it has been noted by GNATS. From: Pyun YongHyeon To: Mark Atkinson Cc: freebsd-net@freebsd.org, bug-followup@FreeBSD.org Subject: Re: kern/124127: [msk] watchdog timeout (missed Tx interrupts) -- recovering Date: Thu, 29 Oct 2009 09:49:09 -0700 On Thu, Oct 29, 2009 at 06:52:34AM -0700, Mark Atkinson wrote: > Wow, not sure what to blame for that charset nightmare. Apologies. > Here's the original message: > > On the unpatched -current kernel, built > > FreeBSD hellfire.filament.org 9.0-CURRENT FreeBSD 9.0-CURRENT #14: Mon > Oct 19 09:12:03 PDT 2009 > > I recieved the following panic today related to this: > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0xdeadc10a > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc0987410 > stack pointer = 0x28:0xd533dac0 > frame pointer = 0x28:0xd533dae8 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 0 (mskc0 taskq) > Physical memory: 495 MB > Dumping 132 MB: 117 101 85 69 53 37 21 5 > > Reading symbols from /boot/kernel/linux.ko...Reading symbols from > /boot/kernel/linux.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/linux.ko > #0 0xc08907a9 in doadump () at /usr/src/sys/kern/kern_shutdown.c:254 > 254 } > (kgdb) bt > #0 0xc08907a9 in doadump () at /usr/src/sys/kern/kern_shutdown.c:254 > #1 0xc04f7e37 in db_fncall (dummy1=-1067299898, dummy2=0, > dummy3=-718022488, > dummy4=0xd533d898 "\200%t?") at /usr/src/sys/ddb/db_command.c:548 > #2 0xc04f8214 in db_command (last_cmdp=0xc0da059c, cmd_table=0x0, > dopager=1) > at /usr/src/sys/ddb/db_command.c:445 > #3 0xc04f8352 in db_command_loop () at /usr/src/sys/ddb/db_command.c:498 > #4 0xc04fa05e in db_trap (type=12, code=0) at > /usr/src/sys/ddb/db_main.c:229 > #5 0xc08bf2d2 in kdb_reenter () at /usr/src/sys/kern/subr_kdb.c:398 > #6 0xc0ba9b62 in trap_fatal (frame=0x1, eva=3735929098) > at /usr/src/sys/i386/i386/trap.c:938 > #7 0xc0baa483 in trap (frame=0xd533da80) at > /usr/src/sys/i386/i386/trap.c:339 > #8 0xc0b8e4ab in Xlcall_syscall () at > /usr/src/sys/i386/i386/exception.s:241 > #9 0xc0987410 in in_lltable_lookup (llt=0xc39e1000, flags=Variable > "flags" is not available. > ) > at /usr/src/sys/netinet/in.c:1380 > #10 0xc0982470 in arpintr (m=0xc3baeb00) at > /usr/src/sys/netinet/if_ether.c:642 > #11 0xc094227a in netisr_dispatch_src (proto=7, source=0, m=0xc0de) > at /usr/src/sys/net/netisr.c:932 > #12 0xc09424dd in netisr_unregister (nhp=0xc0de) > at /usr/src/sys/net/netisr.c:583 > #13 0xc093ac69 in ether_demux (ifp=0x0, m=0xc3baeb00) > at /usr/src/sys/net/if_ethersubr.c:911 > #14 0xc093b1ce in ether_output (ifp=0xc36ad400, m=0xc3baeb00, > dst=0xc0c55c27, > ro=0x301010a) at /usr/src/sys/net/if_ethersubr.c:181 > ---Type to continue, or q to quit--- > #15 0xc070b032 in msk_handle_events (sc=0xc3686c00) > at /usr/src/sys/dev/msk/if_msk.c:3048 > #16 0xc070b828 in msk_int_task (arg=0xc3686c00, pending=1) > at /usr/src/sys/dev/msk/if_msk.c:3625 > #17 0xc08cac8c in taskqueue_run (queue=0xc36bf380) > at /usr/src/sys/kern/subr_taskqueue.c:72 > #18 0xc08cadcc in taskqueue_thread_loop (arg=0xc3686c8c) > at /usr/src/sys/kern/subr_taskqueue.c:90 > #19 0xc0869271 in fork_exit (callout=0xc08cad67 , > arg=0xc3686c8c, frame=0xd533dd38) at /usr/src/sys/kern/kern_fork.c:854 > #20 0xc0b8e520 in Xatpic_intr0 () at atpic_vector.s:62 > #21 0x00000000 in ?? () > I think it's not a bug of msk(4). Qin Li fixed the bug in arp code. See r198301. For watchdog timeout issues on 88E8053 controller, did you ever try disabling MSI? msk(4) was changed a lot since 7.0-RELEASE to support newer controllers and added several workarounds to address silicon bugs. So don't blindly apply experimental patches to your controller. 88E8053 also has a couple of hardware bugs but I guess msk(4) already incorporated required workarounds. So if you can reliably reproduce watchdog timeouts please let me know. From owner-freebsd-net@FreeBSD.ORG Thu Oct 29 17:30:48 2009 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 121DE1065676 for ; Thu, 29 Oct 2009 17:30:48 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from tomjudge.vm.bytemark.co.uk (tomjudge.vm.bytemark.co.uk [80.68.91.100]) by mx1.freebsd.org (Postfix) with ESMTP id C363F8FC20 for ; Thu, 29 Oct 2009 17:30:47 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 9F06F48A81; Thu, 29 Oct 2009 17:30:46 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at tomjudge.vm.bytemark.co.uk Received: from tomjudge.vm.bytemark.co.uk ([127.0.0.1]) by localhost (tomjudge.vm.bytemark.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IA-MU7WjJJvj; Thu, 29 Oct 2009 17:30:43 +0000 (GMT) Received: from rita.nodomain (unknown [192.168.205.6]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 926E548A7C; Thu, 29 Oct 2009 17:30:42 +0000 (GMT) Message-ID: <4AE9D10F.4040703@tomjudge.com> Date: Thu, 29 Oct 2009 17:29:51 +0000 From: Tom Judge User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: David Christensen References: <4AE72910.8090708@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B49180@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE76FF1.9010401@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B491AE@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE8CC59.7020004@tomjudge.com> In-Reply-To: <4AE8CC59.7020004@tomjudge.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "rwilliams@borderware.com" , Gideon Naim , "net@freebsd.org" Subject: Re: bce(4) BCM5907 CTX write errors on 7.2 driver 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, 29 Oct 2009 17:30:48 -0000 Tom Judge wrote: > David Christensen wrote: >>> Thanks for the rapid response. >>> >>> Dell have firmware 5.0.9 on their website here: http://tiny.cc/ex834 >>> >>> Will that work? >> >> Yes, that release does include a good version of BCM5709 bootcode >> (v5.06). >> I couldn't really tell until I downloaded the file and looked at the >> temporary files inside. Thanks for the link. >> >> > > After fighting with the update process for a bit and then learning about > the live cycle manager I have managed to test the R610 with the 5.0.9 > firmware. > > On the face of it, it seems that this resolves the issue. > After a reboot this morning the error has resurfaced and the box is again useless. Tom From owner-freebsd-net@FreeBSD.ORG Thu Oct 29 17:50:05 2009 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 656D0106566B for ; Thu, 29 Oct 2009 17:50:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 554128FC30 for ; Thu, 29 Oct 2009 17:50:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9THo5IM038989 for ; Thu, 29 Oct 2009 17:50:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9THo5Fi038988; Thu, 29 Oct 2009 17:50:05 GMT (envelope-from gnats) Date: Thu, 29 Oct 2009 17:50:05 GMT Message-Id: <200910291750.n9THo5Fi038988@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Mark Atkinson Cc: Subject: Re: kern/124127: [msk] watchdog timeout (missed Tx interrupts) -- recovering X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mark Atkinson List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Oct 2009 17:50:05 -0000 The following reply was made to PR kern/124127; it has been noted by GNATS. From: Mark Atkinson To: pyunyh@gmail.com Cc: bug-followup@FreeBSD.org Subject: Re: kern/124127: [msk] watchdog timeout (missed Tx interrupts) -- recovering Date: Thu, 29 Oct 2009 10:47:47 -0700 (PDT) ----- Original Message ---- From: Pyun YongHyeon Sent: Thu, October 29, 2009 9:49:09 AM Subject: Re: kern/124127: [msk] watchdog timeout (missed Tx interrupts) -- recovering >I think it's not a bug of msk(4). Qin Li fixed the bug in arp code. >See r198301. Thanks I saw the intr call in the trace and assumed wrong, the 'lltable' should have tipped me off. >For watchdog timeout issues on 88E8053 controller, did you ever try >disabling MSI? I haven't tried that lately in -current, last time I did that msk did not work at all. Will retry and report back. > msk(4) was changed a lot since 7.0-RELEASE to >support newer controllers and added several workarounds to address >silicon bugs. So don't blindly apply experimental patches to your >controller. Yes, this box runs -current constantly, only recently did I have to give up my dual Intel adapter and go back to using the on-board pci-e yukon, and thus re-experiencing this issue. > 88E8053 also has a couple of hardware bugs but I guess >msk(4) already incorporated required workarounds. So if you can >reliably reproduce watchdog timeouts please let me know. It still repros on -current, hence me trying out the experimental patches in the PR and reporting back. As I reported in this PR earlier I could still hit the watchdog after a week of runtime, but as of now I don't have a reliable repro. BTW thanks for all your hard work on hardware NIC support. Very much appreciated. From owner-freebsd-net@FreeBSD.ORG Thu Oct 29 18:06:33 2009 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 4CE151065676 for ; Thu, 29 Oct 2009 18:06:33 +0000 (UTC) (envelope-from AStultz@datatekcorp.com) Received: from datatekcorp.com (h-68-167-242-186.nycmny83.static.covad.net [68.167.242.186]) by mx1.freebsd.org (Postfix) with ESMTP id 01CDA8FC1E for ; Thu, 29 Oct 2009 18:06:32 +0000 (UTC) X-MDAV-Processed: datatekcorp.com, Thu, 29 Oct 2009 13:51:38 -0400 Received: from AStultz08 by datatekcorp.com (Cipher TLSv1:RC4-MD5:128) (MDaemon PRO v10.0.4) with ESMTP id md50000251071.msg for ; Thu, 29 Oct 2009 13:51:37 -0400 X-Spam-Processed: datatekcorp.com, Thu, 29 Oct 2009 13:51:37 -0400 (not processed: message from valid local sender) X-MDOP-RefID: str=0001.0A090209.4AE9D627.01B2,ss=1,fgs=0 (_st=1 _vt=0 _iwf=0) X-Return-Path: AStultz@datatekcorp.com X-Envelope-From: AStultz@datatekcorp.com X-MDaemon-Deliver-To: freebsd-net@freebsd.org From: "Alan Stultz" To: Date: Thu, 29 Oct 2009 13:53:41 -0400 Message-ID: <00de01ca58c0$c0471710$ae01a8c0@datatekcorp.com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.3350 Thread-Index: AcpYwMAG8lF1DfgmTYqkRLGbTrIjTw== Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: IPsec v3 question 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, 29 Oct 2009 18:06:33 -0000 Hello All: I have a question about the implementation of IPsec version 3 in FreeBSD. We are porting from FreeBSD 5.4 to 7.2 and currently run an IPv6 application with IPsec version 2 and IKEv1 open source from the KAME group. Since the KAME group disbanded (around when 5.4 was released), I don't know what RFCs for IPsec and IPv6 are currently implemented in various FreeBSD releases. I'm most interested in the following: RFC4301 - Security Arch. for the Internet Protocol RFC4302 - IP Authentication Header RFC4303 - IP ESP RFC4308 - Cryptographic Suites for IPsec If anyone has a list or knowledge of the latest IPv6 RFCs supported in FreeBSD, I would appreciate any info on them. Thanks in advance, Alan From owner-freebsd-net@FreeBSD.ORG Thu Oct 29 18:12:34 2009 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 2EEE21065670 for ; Thu, 29 Oct 2009 18:12:34 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by mx1.freebsd.org (Postfix) with ESMTP id 095628FC15 for ; Thu, 29 Oct 2009 18:12:33 +0000 (UTC) Received: from [10.9.200.133] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Thu, 29 Oct 2009 11:05:39 -0700 X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201 Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by IRVEXCHHUB02.corp.ad.broadcom.com ([10.9.200.133]) with mapi; Thu, 29 Oct 2009 11:07:01 -0700 From: "David Christensen" To: "Tom Judge" Date: Thu, 29 Oct 2009 11:05:37 -0700 Thread-Topic: bce(4) BCM5907 CTX write errors on 7.2 driver Thread-Index: AcpYvZUvlI/Ka8HMQzO8nD0QpoRfTwABCT2A Message-ID: <5D267A3F22FD854F8F48B3D2B52381933A054DE883@IRVEXCHCCR01.corp.ad.broadcom.com> References: <4AE72910.8090708@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B49180@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE76FF1.9010401@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B491AE@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE8CC59.7020004@tomjudge.com> <4AE9D10F.4040703@tomjudge.com> In-Reply-To: <4AE9D10F.4040703@tomjudge.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-WSS-ID: 66F706F93A01040636-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: "rwilliams@borderware.com" , Gideon Naim , "net@freebsd.org" Subject: RE: bce(4) BCM5907 CTX write errors on 7.2 driver 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, 29 Oct 2009 18:12:34 -0000 > > After fighting with the update process for a bit and then learning=20 > > about the live cycle manager I have managed to test the=20 > R610 with the=20 > > 5.0.9 firmware. > >=20 > > On the face of it, it seems that this resolves the issue. > > > After a reboot this morning the error has resurfaced and the=20 > box is again useless. Can you try a different test? Power-on the system with the network cable attached to an idle switch (i.e. keep all network traffic from being forwarded to the NIC during driver initialization). Does the system power up successfully? Repeatedly? The problem I saw=20 was caused by network traffic being handled by the NIC during driver initialization. If you still see the same behavior then this might be a different issue. Dave= From owner-freebsd-net@FreeBSD.ORG Thu Oct 29 20:06:07 2009 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 18E71106568F for ; Thu, 29 Oct 2009 20:06:07 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from tomjudge.vm.bytemark.co.uk (tomjudge.vm.bytemark.co.uk [80.68.91.100]) by mx1.freebsd.org (Postfix) with ESMTP id C81D58FC26 for ; Thu, 29 Oct 2009 20:06:06 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id BE4BF48A7F; Thu, 29 Oct 2009 20:06:05 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at tomjudge.vm.bytemark.co.uk Received: from tomjudge.vm.bytemark.co.uk ([127.0.0.1]) by localhost (tomjudge.vm.bytemark.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BCRPn6tnQmZf; Thu, 29 Oct 2009 20:06:02 +0000 (GMT) Received: from rita.nodomain (unknown [192.168.205.6]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id C68E848A7D; Thu, 29 Oct 2009 20:06:01 +0000 (GMT) Message-ID: <4AE9F576.4060101@tomjudge.com> Date: Thu, 29 Oct 2009 20:05:10 +0000 From: Tom Judge User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: David Christensen References: <4AE72910.8090708@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B49180@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE76FF1.9010401@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B491AE@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE8CC59.7020004@tomjudge.com> <4AE9D10F.4040703@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A054DE883@IRVEXCHCCR01.corp.ad.broadcom.com> In-Reply-To: <5D267A3F22FD854F8F48B3D2B52381933A054DE883@IRVEXCHCCR01.corp.ad.broadcom.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "rwilliams@borderware.com" , Gideon Naim , "net@freebsd.org" Subject: Re: bce(4) BCM5907 CTX write errors on 7.2 driver 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, 29 Oct 2009 20:06:07 -0000 David Christensen wrote: >>> After fighting with the update process for a bit and then learning >>> about the live cycle manager I have managed to test the >> R610 with the >>> 5.0.9 firmware. >>> >>> On the face of it, it seems that this resolves the issue. >>> >> After a reboot this morning the error has resurfaced and the >> box is again useless. > > Can you try a different test? Power-on the system with the network > cable attached to an idle switch (i.e. keep all network traffic from > being forwarded to the NIC during driver initialization). Does the > system power up successfully? Repeatedly? The problem I saw > was caused by network traffic being handled by the NIC during driver > initialization. If you still see the same behavior then this might > be a different issue. > Looks like we are heading in the right direction here. Setup: R610[bce1]->Netgear 100/10 unmanaged switch-[uplink]->Managed server access switch. The R610 is the only thing connected to the netgear switch. When the uplink was severed during boot up it was reconnected after the link up event and while the NFS mounts where being mounted. Cold reboots are with the server shutdown with the psu's remaining connected and then restarted. Warm are just 'shutdown -r now' Ice are from the psus disconnected from the mains supply. These results are time ordered. Type Uplink Result Warm No Works Warm No Works Warm No Works Cold No Works Warm No Works Cold No Works Warm No Works Ice No Works Warn No Works Ice Yes Works Warm Yes Works Cold Yes Works Warm Yes Works Ice Bybass Works Warm Bypass Fails Cold Bypass Works - paniced on shutdown spin lock (sched) held to long pid 0 Cold Bypass Works Warm Bypass Fails We can provide full remote access to the following hardware (via enterprise drac) if required and on site hands if this will help get this issue resolved. 3 * R610 4 * R410 7 * R710 Tom From owner-freebsd-net@FreeBSD.ORG Thu Oct 29 20:40:49 2009 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 779A5106568B for ; Thu, 29 Oct 2009 20:40:49 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by mx1.freebsd.org (Postfix) with ESMTP id 5087E8FC1E for ; Thu, 29 Oct 2009 20:40:49 +0000 (UTC) Received: from [10.9.200.131] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Thu, 29 Oct 2009 13:38:09 -0700 X-Server-Uuid: 02CED230-5797-4B57-9875-D5D2FEE4708A Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by IRVEXCHHUB01.corp.ad.broadcom.com ([10.9.200.131]) with mapi; Thu, 29 Oct 2009 13:38:09 -0700 From: "David Christensen" To: "Tom Judge" Date: Thu, 29 Oct 2009 13:38:07 -0700 Thread-Topic: bce(4) BCM5907 CTX write errors on 7.2 driver Thread-Index: AcpY00YpDhc23wGsQISrxcu9QvSrXgAAIYIA Message-ID: <5D267A3F22FD854F8F48B3D2B52381933A19B35A55@IRVEXCHCCR01.corp.ad.broadcom.com> References: <4AE72910.8090708@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B49180@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE76FF1.9010401@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B491AE@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE8CC59.7020004@tomjudge.com> <4AE9D10F.4040703@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A054DE883@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE9F576.4060101@tomjudge.com> In-Reply-To: <4AE9F576.4060101@tomjudge.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-WSS-ID: 66F722BB5KG35658623-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: "rwilliams@borderware.com" , Gideon Naim , "net@freebsd.org" Subject: RE: bce(4) BCM5907 CTX write errors on 7.2 driver 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, 29 Oct 2009 20:40:49 -0000 > > Can you try a different test? Power-on the system with the network=20 > > cable attached to an idle switch (i.e. keep all network=20 > traffic from=20 > > being forwarded to the NIC during driver initialization). Does the=20 > > system power up successfully? Repeatedly? The problem I saw was=20 > > caused by network traffic being handled by the NIC during driver=20 > > initialization. If you still see the same behavior then=20 > this might be=20 > > a different issue. > >=20 >=20 > Looks like we are heading in the right direction here. >=20 The next test is to diable the LOM's management firmware but boot to an active network. Get the User Diag utility at the bottom of http://www.broadcom.com/support/ethernet_nic/netxtremeii.php. Run the uxdiag utility with the command line: "C:\>uxdiag -c 0 -mfw 0 -c 1 -mfw 0 -c 2 -mfw 0 -c 3 mfw 0" The "-c X" specifies with LOM to use while the "-mfw 0" disables the firmware. Use the appropriate number of "-c X" values for the number of ports on your system (the r710 has 4 ports). To re-enable the firmware do the following: "C:\>uxdiag -c 0 -mfw 1 -c 1 -mfw 1 -c 2 -mfw 1 -c 3 mfw 1" Finally, the routine bce_print_adapter_info() in HEAD prints out both the bootcode and management firmware versions. If you can get those same changes into your release I'd like to see the versions reported on your system. Dave= From owner-freebsd-net@FreeBSD.ORG Thu Oct 29 21:38:18 2009 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 B70051065670 for ; Thu, 29 Oct 2009 21:38:18 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from tomjudge.vm.bytemark.co.uk (tomjudge.vm.bytemark.co.uk [80.68.91.100]) by mx1.freebsd.org (Postfix) with ESMTP id 6FD928FC0C for ; Thu, 29 Oct 2009 21:38:18 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 1B38748A7F; Thu, 29 Oct 2009 21:38:17 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at tomjudge.vm.bytemark.co.uk Received: from tomjudge.vm.bytemark.co.uk ([127.0.0.1]) by localhost (tomjudge.vm.bytemark.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yvc4xwVZBJ4A; Thu, 29 Oct 2009 21:38:13 +0000 (GMT) Received: from rita.nodomain (unknown [192.168.205.6]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id D9AF248A7D; Thu, 29 Oct 2009 21:38:12 +0000 (GMT) Message-ID: <4AEA0B11.2050209@tomjudge.com> Date: Thu, 29 Oct 2009 21:37:21 +0000 From: Tom Judge User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: David Christensen References: <4AE72910.8090708@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B49180@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE76FF1.9010401@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B491AE@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE8CC59.7020004@tomjudge.com> <4AE9D10F.4040703@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A054DE883@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE9F576.4060101@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A19B35A55@IRVEXCHCCR01.corp.ad.broadcom.com> In-Reply-To: <5D267A3F22FD854F8F48B3D2B52381933A19B35A55@IRVEXCHCCR01.corp.ad.broadcom.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "rwilliams@borderware.com" , Gideon Naim , "net@freebsd.org" Subject: Re: bce(4) BCM5907 CTX write errors on 7.2 driver 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, 29 Oct 2009 21:38:18 -0000 David Christensen wrote: >>> Can you try a different test? Power-on the system with the network >>> cable attached to an idle switch (i.e. keep all network >> traffic from >>> being forwarded to the NIC during driver initialization). Does the >>> system power up successfully? Repeatedly? The problem I saw was >>> caused by network traffic being handled by the NIC during driver >>> initialization. If you still see the same behavior then >> this might be >>> a different issue. >>> >> Looks like we are heading in the right direction here. >> > > > The next test is to diable the LOM's management firmware but boot to > an active network. Get the User Diag utility at the bottom of > http://www.broadcom.com/support/ethernet_nic/netxtremeii.php. > Run the uxdiag utility with the command line: > "C:\>uxdiag -c 0 -mfw 0 -c 1 -mfw 0 -c 2 -mfw 0 -c 3 mfw 0" > The "-c X" specifies with LOM to use while the "-mfw 0" disables > the firmware. Use the appropriate number of "-c X" values for > the number of ports on your system (the r710 has 4 ports). > To re-enable the firmware do the following: > "C:\>uxdiag -c 0 -mfw 1 -c 1 -mfw 1 -c 2 -mfw 1 -c 3 mfw 1" > > Finally, the routine bce_print_adapter_info() in HEAD prints out both > the bootcode and management firmware versions. If you can get those > same changes into your release I'd like to see the versions reported > on your system. > Here is the info from a boot of 8.0 RC2. ASIC: 0x57092003 B/C: 5.0.6 Rev: C0 Bus: PCIe x4, 2.5Gb/s Flags: MSI|MFW MFW: NCS 2.0.3 And looking at this it seems dells update CD was not up to date enough and I only got 5.0.6 firmware not 5.0.9. I will update this now and retest. TJ From owner-freebsd-net@FreeBSD.ORG Thu Oct 29 21:52:51 2009 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 66B7E106566B for ; Thu, 29 Oct 2009 21:52:51 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by mx1.freebsd.org (Postfix) with ESMTP id EB4F98FC0C for ; Thu, 29 Oct 2009 21:52:50 +0000 (UTC) Received: from [10.9.200.133] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Thu, 29 Oct 2009 14:52:10 -0700 X-Server-Uuid: D3C04415-6FA8-4F2C-93C1-920E106A2031 Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by IRVEXCHHUB02.corp.ad.broadcom.com ([10.9.200.133]) with mapi; Thu, 29 Oct 2009 14:53:32 -0700 From: "David Christensen" To: "Tom Judge" Date: Thu, 29 Oct 2009 14:52:09 -0700 Thread-Topic: bce(4) BCM5907 CTX write errors on 7.2 driver Thread-Index: AcpY4IlgdvfsN5XsSm6bryoasNMrRQAAV56g Message-ID: <5D267A3F22FD854F8F48B3D2B52381933A19B35AB0@IRVEXCHCCR01.corp.ad.broadcom.com> References: <4AE72910.8090708@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B49180@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE76FF1.9010401@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B491AE@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE8CC59.7020004@tomjudge.com> <4AE9D10F.4040703@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A054DE883@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE9F576.4060101@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A19B35A55@IRVEXCHCCR01.corp.ad.broadcom.com> <4AEA0B11.2050209@tomjudge.com> In-Reply-To: <4AEA0B11.2050209@tomjudge.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-WSS-ID: 66F4D1005S464960283-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: "rwilliams@borderware.com" , Gideon Naim , "net@freebsd.org" Subject: RE: bce(4) BCM5907 CTX write errors on 7.2 driver 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, 29 Oct 2009 21:52:51 -0000 > > The next test is to diable the LOM's management firmware=20 > but boot to=20 > > an active network. Get the User Diag utility at the bottom of=20 > > http://www.broadcom.com/support/ethernet_nic/netxtremeii.php. > > Run the uxdiag utility with the command line: > > "C:\>uxdiag -c 0 -mfw 0 -c 1 -mfw 0 -c 2 -mfw 0 -c 3 mfw 0" > > The "-c X" specifies with LOM to use while the "-mfw 0"=20 > disables the=20 > > firmware. Use the appropriate number of "-c X" values for=20 > the number=20 > > of ports on your system (the r710 has 4 ports). > > To re-enable the firmware do the following: > > "C:\>uxdiag -c 0 -mfw 1 -c 1 -mfw 1 -c 2 -mfw 1 -c 3 mfw 1" > >=20 > > Finally, the routine bce_print_adapter_info() in HEAD=20 > prints out both=20 > > the bootcode and management firmware versions. If you can=20 > get those=20 > > same changes into your release I'd like to see the versions=20 > reported=20 > > on your system. > >=20 >=20 > Here is the info from a boot of 8.0 RC2. >=20 > ASIC: 0x57092003 > B/C: 5.0.6 > Rev: C0 > Bus: PCIe x4, 2.5Gb/s > Flags: MSI|MFW > MFW: NCS 2.0.3 >=20 > And looking at this it seems dells update CD was not up to=20 > date enough and I only got 5.0.6 firmware not 5.0.9. The package version and the bootcode version are similar but they are not the same. The bootcode you have (v5.0.6) is sufficient to fix the problem. Dave= From owner-freebsd-net@FreeBSD.ORG Thu Oct 29 22:05:48 2009 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 639F1106568F for ; Thu, 29 Oct 2009 22:05:48 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from tomjudge.vm.bytemark.co.uk (tomjudge.vm.bytemark.co.uk [80.68.91.100]) by mx1.freebsd.org (Postfix) with ESMTP id 1AC348FC14 for ; Thu, 29 Oct 2009 22:05:47 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 1924A48A81; Thu, 29 Oct 2009 22:05:47 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at tomjudge.vm.bytemark.co.uk Received: from tomjudge.vm.bytemark.co.uk ([127.0.0.1]) by localhost (tomjudge.vm.bytemark.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iAgpZve3RQGQ; Thu, 29 Oct 2009 22:05:44 +0000 (GMT) Received: from rita.nodomain (unknown [192.168.205.6]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 615EC48A7F; Thu, 29 Oct 2009 22:05:43 +0000 (GMT) Message-ID: <4AEA1183.7050306@tomjudge.com> Date: Thu, 29 Oct 2009 22:04:51 +0000 From: Tom Judge User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: David Christensen References: <4AE72910.8090708@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B49180@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE76FF1.9010401@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B491AE@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE8CC59.7020004@tomjudge.com> <4AE9D10F.4040703@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A054DE883@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE9F576.4060101@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A19B35A55@IRVEXCHCCR01.corp.ad.broadcom.com> <4AEA0B11.2050209@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A19B35AB0@IRVEXCHCCR01.corp.ad.broadcom.com> In-Reply-To: <5D267A3F22FD854F8F48B3D2B52381933A19B35AB0@IRVEXCHCCR01.corp.ad.broadcom.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "rwilliams@borderware.com" , Gideon Naim , "net@freebsd.org" Subject: Re: bce(4) BCM5907 CTX write errors on 7.2 driver 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, 29 Oct 2009 22:05:48 -0000 David Christensen wrote: >>> The next test is to diable the LOM's management firmware >> but boot to >>> an active network. Get the User Diag utility at the bottom of >>> http://www.broadcom.com/support/ethernet_nic/netxtremeii.php. >>> Run the uxdiag utility with the command line: >>> "C:\>uxdiag -c 0 -mfw 0 -c 1 -mfw 0 -c 2 -mfw 0 -c 3 mfw 0" >>> The "-c X" specifies with LOM to use while the "-mfw 0" >> disables the >>> firmware. Use the appropriate number of "-c X" values for >> the number >>> of ports on your system (the r710 has 4 ports). >>> To re-enable the firmware do the following: >>> "C:\>uxdiag -c 0 -mfw 1 -c 1 -mfw 1 -c 2 -mfw 1 -c 3 mfw 1" >>> >>> Finally, the routine bce_print_adapter_info() in HEAD >> prints out both >>> the bootcode and management firmware versions. If you can >> get those >>> same changes into your release I'd like to see the versions >> reported >>> on your system. >>> >> Here is the info from a boot of 8.0 RC2. >> >> ASIC: 0x57092003 >> B/C: 5.0.6 >> Rev: C0 >> Bus: PCIe x4, 2.5Gb/s >> Flags: MSI|MFW >> MFW: NCS 2.0.3 >> >> And looking at this it seems dells update CD was not up to >> date enough and I only got 5.0.6 firmware not 5.0.9. > > The package version and the bootcode version are similar but > they are not the same. The bootcode you have (v5.0.6) is > sufficient to fix the problem. > Ok just checked in the life cycle manager and it has 5.0.9 installed my bad. Running the other test now. Tom From owner-freebsd-net@FreeBSD.ORG Fri Oct 30 08:26:49 2009 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 DF2331065670 for ; Fri, 30 Oct 2009 08:26:49 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mx01.netsrc.de (mx01.netsrc.de [89.107.71.100]) by mx1.freebsd.org (Postfix) with ESMTP id A02488FC13 for ; Fri, 30 Oct 2009 08:26:49 +0000 (UTC) Received: from jessie.localnet (unknown [212.185.121.50]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.netsrc.de (Postfix) with ESMTP id AD46B192FD9; Fri, 30 Oct 2009 09:26:47 +0100 (CET) From: Bernhard Schmidt To: freebsd-net@freebsd.org Date: Fri, 30 Oct 2009 09:26:32 +0100 User-Agent: KMail/1.12.1 (Linux/2.6.30-2-686; KDE/4.3.1; i686; ; ) References: <20091009170839.142800@gmx.net> <11167f520910241241o6a1ada3cmf076add6374a1add@mail.gmail.com> <200910251024.06856.bschmidt@techwires.net> In-Reply-To: <200910251024.06856.bschmidt@techwires.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200910300926.32286.bschmidt@techwires.net> Cc: "Sam Fourman Jr." , Rui Paulo Subject: Re: Intel WiFi 5100/5300 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Oct 2009 08:26:50 -0000 On Sunday 25 October 2009 10:24:06 Bernhard Schmidt wrote: > On Saturday 24 October 2009 21:41:39 Sam Fourman Jr. wrote: > > Just wanted to make everyone aware that OpenBSD just 1 hour ago commited > > a bunch of changes to their iwn driver. maybe some of it is useful for > > FreeBSD as well? > > Definitely, I'll look into that. Another update: * ICT interrupts for 5000/6000 series * New firmware * Initial support for 1000 series and initial bits for upcoming 6000 series (untested as hardware is not available to the general public) * Many bug fixes, including workarounds for hardware bugs * Addresses kern/140036 Most of this stuff has been obtained from OpeBSD. Testes/Feedback welcome! http://techwires.net/~bschmidt/patches/freebsd/iwn/iwn_merge_20081028.diff.bz2 -- Bernhard From owner-freebsd-net@FreeBSD.ORG Fri Oct 30 17:43:07 2009 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 134D5106568D for ; Fri, 30 Oct 2009 17:43:07 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from tomjudge.vm.bytemark.co.uk (tomjudge.vm.bytemark.co.uk [80.68.91.100]) by mx1.freebsd.org (Postfix) with ESMTP id BF0C08FC18 for ; Fri, 30 Oct 2009 17:43:06 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 8289DDCF8B; Fri, 30 Oct 2009 17:43:05 +0000 (GMT) X-Virus-Scanned: Debian amavisd-new at tomjudge.vm.bytemark.co.uk Received: from tomjudge.vm.bytemark.co.uk ([127.0.0.1]) by localhost (tomjudge.vm.bytemark.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7uDw4Hr4B8Uo; Fri, 30 Oct 2009 17:43:01 +0000 (GMT) Received: from rita.nodomain (unknown [192.168.205.6]) by tomjudge.vm.bytemark.co.uk (Postfix) with ESMTP id 2F3EB48A67; Fri, 30 Oct 2009 17:43:01 +0000 (GMT) Message-ID: <4AEB2571.7090006@tomjudge.com> Date: Fri, 30 Oct 2009 17:42:09 +0000 From: Tom Judge User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: David Christensen References: <4AE72910.8090708@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B49180@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE76FF1.9010401@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B491AE@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE8CC59.7020004@tomjudge.com> <4AE9D10F.4040703@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A054DE883@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE9F576.4060101@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A19B35A55@IRVEXCHCCR01.corp.ad.broadcom.com> <4AEA0B11.2050209@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A19B35AB0@IRVEXCHCCR01.corp.ad.broadcom.com> <4AEA1183.7050306@tomjudge.com> In-Reply-To: <4AEA1183.7050306@tomjudge.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "rwilliams@borderware.com" , Gideon Naim , "net@freebsd.org" Subject: Re: bce(4) BCM5907 CTX write errors on 7.2 driver X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Oct 2009 17:43:07 -0000 Tom Judge wrote: > David Christensen wrote: >>>> The next test is to diable the LOM's management firmware >>> but boot to >>>> an active network. After disabling the management firmware and doing 1 cold reboot and 3 warms all worked correctly. After re enabling the firmware and doing 1 cold reboot and 3 warms, the cold works correctly and the warms all failed. Tom >>>> Finally, the routine bce_print_adapter_info() in HEAD >>> prints out both >>>> the bootcode and management firmware versions. If you can >>> get those >>>> same changes into your release I'd like to see the versions >>> reported >>>> on your system. >>>> >>> Here is the info from a boot of 8.0 RC2. >>> >>> ASIC: 0x57092003 >>> B/C: 5.0.6 >>> Rev: C0 >>> Bus: PCIe x4, 2.5Gb/s >>> Flags: MSI|MFW >>> MFW: NCS 2.0.3 >>> >>> And looking at this it seems dells update CD was not up to date >>> enough and I only got 5.0.6 firmware not 5.0.9. >> >> The package version and the bootcode version are similar but >> they are not the same. The bootcode you have (v5.0.6) is >> sufficient to fix the problem. >> > > Ok just checked in the life cycle manager and it has 5.0.9 installed my > bad. > > Running the other test now. > From owner-freebsd-net@FreeBSD.ORG Fri Oct 30 22:05:23 2009 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 5B954106568B for ; Fri, 30 Oct 2009 22:05:23 +0000 (UTC) (envelope-from zibbe@cisko.org) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id EDBCA8FC15 for ; Fri, 30 Oct 2009 22:05:22 +0000 (UTC) Received: by bwz5 with SMTP id 5so4130033bwz.3 for ; Fri, 30 Oct 2009 15:05:22 -0700 (PDT) Received: by 10.204.34.84 with SMTP id k20mr1477010bkd.199.1256939105764; Fri, 30 Oct 2009 14:45:05 -0700 (PDT) Received: from ?172.17.1.247? (fw.sth1.keff.org [212.247.153.198]) by mx.google.com with ESMTPS id 22sm1624427fkr.47.2009.10.30.14.45.01 (version=SSLv3 cipher=RC4-MD5); Fri, 30 Oct 2009 14:45:02 -0700 (PDT) Sender: Sebastian Hyrwall Message-ID: <4AEB7AE8.5090101@keff.org> Date: Sat, 31 Oct 2009 00:46:48 +0100 From: Sebastian Hyrwall User-Agent: Thunderbird 2.0.0.19 (X11/20081209) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Hi. /31 on ethernet links X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Oct 2009 22:05:23 -0000 Hi. Is there any way to use /31's on ordinary ethernet links in 7.2? "ifconfig addr dest-addr" does not work either. It keeps setting the last ip as broadcast. Sincerley, Sebastian H From owner-freebsd-net@FreeBSD.ORG Fri Oct 30 22:20:52 2009 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 AF220106566B for ; Fri, 30 Oct 2009 22:20:52 +0000 (UTC) (envelope-from zibbe@cisko.org) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 4A4858FC14 for ; Fri, 30 Oct 2009 22:20:52 +0000 (UTC) Received: by bwz5 with SMTP id 5so4144196bwz.3 for ; Fri, 30 Oct 2009 15:20:51 -0700 (PDT) Received: by 10.204.24.65 with SMTP id u1mr1525096bkb.176.1256941249872; Fri, 30 Oct 2009 15:20:49 -0700 (PDT) Received: from ?172.17.1.247? (fw.sth1.keff.org [212.247.153.198]) by mx.google.com with ESMTPS id 18sm778944fkq.7.2009.10.30.15.20.46 (version=SSLv3 cipher=RC4-MD5); Fri, 30 Oct 2009 15:20:47 -0700 (PDT) Sender: Sebastian Hyrwall Message-ID: <4AEB834D.1050907@keff.org> Date: Sat, 31 Oct 2009 01:22:37 +0100 From: Sebastian Hyrwall User-Agent: Thunderbird 2.0.0.19 (X11/20081209) MIME-Version: 1.0 To: Chuck Swiger References: <4AEB7AE8.5090101@keff.org> <18C758A7-1908-4D1A-BDCA-80FF7FD8BC22@mac.com> In-Reply-To: <18C758A7-1908-4D1A-BDCA-80FF7FD8BC22@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Hi. /31 on ethernet links X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Oct 2009 22:20:52 -0000 Chuck Swiger skrev: > On Oct 30, 2009, at 4:46 PM, Sebastian Hyrwall wrote: >> Is there any way to use /31's on ordinary ethernet links in 7.2? >> "ifconfig addr dest-addr" does not work either. It keeps setting the >> last ip as broadcast. > > A /31 subnet is only defined for point-to-point network links, per: > > http://www.rfc-editor.org/rfc/rfc3021.txt > > Ordinary ethernet links have BROADCAST flag set instead of POINTOPOINT. > > Regards, Well how do I set the POINTOPOINT flag and remove the BROADCAST-flag on ethernet links? Or are you implying that it does not belong on ethernet links :) Cause Cisco and Linux support /31 (ptp's) on ordinary ethernet links. Sincerely, Sebastian H From owner-freebsd-net@FreeBSD.ORG Fri Oct 30 22:27:37 2009 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 93EB7106566B for ; Fri, 30 Oct 2009 22:27:37 +0000 (UTC) (envelope-from zibbe@cisko.org) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 2D8608FC1A for ; Fri, 30 Oct 2009 22:27:36 +0000 (UTC) Received: by bwz5 with SMTP id 5so4150032bwz.3 for ; Fri, 30 Oct 2009 15:27:36 -0700 (PDT) Received: by 10.204.26.130 with SMTP id e2mr1531806bkc.144.1256941656069; Fri, 30 Oct 2009 15:27:36 -0700 (PDT) Received: from ?172.17.1.247? (fw.sth1.keff.org [212.247.153.198]) by mx.google.com with ESMTPS id z15sm2883005fkz.14.2009.10.30.15.27.33 (version=SSLv3 cipher=RC4-MD5); Fri, 30 Oct 2009 15:27:33 -0700 (PDT) Sender: Sebastian Hyrwall Message-ID: <4AEB84E3.1070908@keff.org> Date: Sat, 31 Oct 2009 01:29:23 +0100 From: Sebastian Hyrwall User-Agent: Thunderbird 2.0.0.19 (X11/20081209) MIME-Version: 1.0 To: Freddie Cash References: <4AEB7AE8.5090101@keff.org> <18C758A7-1908-4D1A-BDCA-80FF7FD8BC22@mac.com> <4AEB834D.1050907@keff.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Hi. /31 on ethernet links X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Oct 2009 22:27:37 -0000 Freddie Cash skrev: > Reading the man page for ifconfig will show the "ptp" option for > ifconfig, that configures the interface as a point-to-point > interface.. :) > It will also show that it seems to be only for bridgeing, # ifconfig fxp0 ptp fxp0 ifconfig: unable to get bridge flags: Invalid argument > > > On Fri, Oct 30, 2009 at 5:22 PM, Sebastian Hyrwall > wrote: > > Chuck Swiger skrev: > > On Oct 30, 2009, at 4:46 PM, Sebastian Hyrwall wrote: > > Is there any way to use /31's on ordinary ethernet links > in 7.2? "ifconfig addr dest-addr" does not work either. It > keeps setting the last ip as broadcast. > > > A /31 subnet is only defined for point-to-point network links, > per: > > http://www.rfc-editor.org/rfc/rfc3021.txt > > Ordinary ethernet links have BROADCAST flag set instead of > POINTOPOINT. > > Regards, > > Well how do I set the POINTOPOINT flag and remove the > BROADCAST-flag on ethernet links? Or are you implying that it does > not belong on ethernet links :) > Cause Cisco and Linux support /31 (ptp's) on ordinary ethernet links. > > Sincerely, > > Sebastian H > _______________________________________________ > 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 > " > > > > > -- > Freddie Cash > fjwcash@gmail.com From owner-freebsd-net@FreeBSD.ORG Fri Oct 30 22:37:26 2009 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 20DAE1065679 for ; Fri, 30 Oct 2009 22:37:26 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout018.mac.com (asmtpout018.mac.com [17.148.16.93]) by mx1.freebsd.org (Postfix) with ESMTP id 0E8B88FC08 for ; Fri, 30 Oct 2009 22:37:25 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from cswiger1.apple.com ([17.227.140.124]) by asmtp018.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0KSC00BC2MUDW590@asmtp018.mac.com> for freebsd-net@freebsd.org; Fri, 30 Oct 2009 15:37:25 -0700 (PDT) Message-id: From: Chuck Swiger To: Sebastian Hyrwall In-reply-to: <4AEB834D.1050907@keff.org> Date: Fri, 30 Oct 2009 15:37:25 -0700 References: <4AEB7AE8.5090101@keff.org> <18C758A7-1908-4D1A-BDCA-80FF7FD8BC22@mac.com> <4AEB834D.1050907@keff.org> X-Mailer: Apple Mail (2.936) Cc: freebsd-net@freebsd.org Subject: Re: Hi. /31 on ethernet links X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Oct 2009 22:37:26 -0000 On Oct 30, 2009, at 5:22 PM, Sebastian Hyrwall wrote: >> A /31 subnet is only defined for point-to-point network links, per: >> >> http://www.rfc-editor.org/rfc/rfc3021.txt >> >> Ordinary ethernet links have BROADCAST flag set instead of >> POINTOPOINT. >> > > Well how do I set the POINTOPOINT flag and remove the BROADCAST-flag > on ethernet links? Or are you implying that it does not belong on > ethernet links :) Cause Cisco and Linux support /31 (ptp's) on > ordinary ethernet links. Ethernet point-to-point links are normally handled by ppp / pppd in PPPoE mode, but possibly something like: ifconfig en0 inet 192.1.1.10 inet 192.1.1.2 ...would give you a POINTOPOINT link instead. If not, you can probably fake things out by either using a /30 and wrapping the /31 inside, or using a /32 and an explicit default route via your ethernet interface. Regards, -- -Chuck From owner-freebsd-net@FreeBSD.ORG Fri Oct 30 22:43:48 2009 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 59204106566B for ; Fri, 30 Oct 2009 22:43:48 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout011.mac.com (asmtpout011.mac.com [17.148.16.86]) by mx1.freebsd.org (Postfix) with ESMTP id 4569A8FC1C for ; Fri, 30 Oct 2009 22:43:48 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed Received: from cswiger1.apple.com ([17.227.140.124]) by asmtp011.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0KSC00C44N4ZQR20@asmtp011.mac.com> for freebsd-net@freebsd.org; Fri, 30 Oct 2009 15:43:48 -0700 (PDT) Message-id: From: Chuck Swiger To: Sebastian Hyrwall In-reply-to: Date: Fri, 30 Oct 2009 15:43:47 -0700 References: <4AEB7AE8.5090101@keff.org> <18C758A7-1908-4D1A-BDCA-80FF7FD8BC22@mac.com> <4AEB834D.1050907@keff.org> X-Mailer: Apple Mail (2.936) Cc: "freebsd-net@freebsd.org Net" Subject: Re: Hi. /31 on ethernet links X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Oct 2009 22:43:48 -0000 On Oct 30, 2009, at 3:37 PM, Chuck Swiger wrote: > ifconfig en0 inet 192.1.1.10 inet 192.1.1.2 Whoops-- copy-paste-typo; instead should be: ifconfig en0 inet 192.1.1.10 192.1.1.11 -- -Chuck From owner-freebsd-net@FreeBSD.ORG Fri Oct 30 22:53:04 2009 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 6FC35106566C for ; Fri, 30 Oct 2009 22:53:04 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-yx0-f171.google.com (mail-yx0-f171.google.com [209.85.210.171]) by mx1.freebsd.org (Postfix) with ESMTP id E70B38FC0C for ; Fri, 30 Oct 2009 22:53:03 +0000 (UTC) Received: by yxe1 with SMTP id 1so3251116yxe.3 for ; Fri, 30 Oct 2009 15:53:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=qZf+NazVOse86RHngmf78vzzVRzmRMvEtSjMgSjDkA4=; b=l/XScv+wHQHNYtbbFr+kNEOEGAbmq2fUCJNMQ8kiRtMdgZqIdk4hnK1Aa1knt9IiFK NZcXMD9hS5SytPqRuVhuRqi6i+vnU/kTCm1hPE6nOHVMXCjL4w+iMRsCPU/rjB3Beax4 fV5Jnc0E7Ld8Fp0iBaRH+V1aLcLqnQoAvjBkg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=RBB5e0AjWMAFPmvNZlODEh4o5lPoYZWeH7M66HkQSr0rlTyERy1yHFysFKq6/I8UPq Fnr14SqSo/Fl9OnjBZHy1rXm4/i0nLzDcKuPHgC8nq/iJYbjSC3apsqhPe/OmzX6rIk3 KNpfP2oWRzybT1Q957xsb4EFi9jyCp2OUtbYk= MIME-Version: 1.0 Received: by 10.150.89.41 with SMTP id m41mr4050758ybb.187.1256941452456; Fri, 30 Oct 2009 15:24:12 -0700 (PDT) In-Reply-To: <4AEB834D.1050907@keff.org> References: <4AEB7AE8.5090101@keff.org> <18C758A7-1908-4D1A-BDCA-80FF7FD8BC22@mac.com> <4AEB834D.1050907@keff.org> Date: Fri, 30 Oct 2009 15:24:12 -0700 Message-ID: From: Freddie Cash To: Sebastian Hyrwall Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re: Hi. /31 on ethernet links X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Oct 2009 22:53:04 -0000 Reading the man page for ifconfig will show the "ptp" option for ifconfig, that configures the interface as a point-to-point interface.. :) On Fri, Oct 30, 2009 at 5:22 PM, Sebastian Hyrwall wrote: > Chuck Swiger skrev: > >> On Oct 30, 2009, at 4:46 PM, Sebastian Hyrwall wrote: >> >>> Is there any way to use /31's on ordinary ethernet links in 7.2? >>> "ifconfig addr dest-addr" does not work either. It keeps setting the last ip >>> as broadcast. >>> >> >> A /31 subnet is only defined for point-to-point network links, per: >> >> http://www.rfc-editor.org/rfc/rfc3021.txt >> >> Ordinary ethernet links have BROADCAST flag set instead of POINTOPOINT. >> >> Regards, >> > Well how do I set the POINTOPOINT flag and remove the BROADCAST-flag on > ethernet links? Or are you implying that it does not belong on ethernet > links :) > Cause Cisco and Linux support /31 (ptp's) on ordinary ethernet links. > > Sincerely, > > Sebastian H > _______________________________________________ > 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" > -- Freddie Cash fjwcash@gmail.com From owner-freebsd-net@FreeBSD.ORG Fri Oct 30 23:12:42 2009 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 42B20106566B for ; Fri, 30 Oct 2009 23:12:42 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout022.mac.com (asmtpout022.mac.com [17.148.16.97]) by mx1.freebsd.org (Postfix) with ESMTP id 3122A8FC18 for ; Fri, 30 Oct 2009 23:12:41 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from cswiger1.apple.com ([17.227.140.124]) by asmtp022.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0KSC00LV0LN3UX30@asmtp022.mac.com> for freebsd-net@freebsd.org; Fri, 30 Oct 2009 15:11:28 -0700 (PDT) Message-id: <18C758A7-1908-4D1A-BDCA-80FF7FD8BC22@mac.com> From: Chuck Swiger To: Sebastian Hyrwall In-reply-to: <4AEB7AE8.5090101@keff.org> Date: Fri, 30 Oct 2009 15:11:27 -0700 References: <4AEB7AE8.5090101@keff.org> X-Mailer: Apple Mail (2.936) Cc: freebsd-net@freebsd.org Subject: Re: Hi. /31 on ethernet links X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Oct 2009 23:12:42 -0000 On Oct 30, 2009, at 4:46 PM, Sebastian Hyrwall wrote: > Is there any way to use /31's on ordinary ethernet links in 7.2? > "ifconfig addr dest-addr" does not work either. It keeps setting the > last ip as broadcast. A /31 subnet is only defined for point-to-point network links, per: http://www.rfc-editor.org/rfc/rfc3021.txt Ordinary ethernet links have BROADCAST flag set instead of POINTOPOINT. Regards, -- -Chuck From owner-freebsd-net@FreeBSD.ORG Fri Oct 30 23:19:47 2009 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 9247C106566C for ; Fri, 30 Oct 2009 23:19:47 +0000 (UTC) (envelope-from zibbe@cisko.org) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 29E2D8FC13 for ; Fri, 30 Oct 2009 23:19:46 +0000 (UTC) Received: by bwz5 with SMTP id 5so4191553bwz.3 for ; Fri, 30 Oct 2009 16:19:45 -0700 (PDT) Received: by 10.204.13.204 with SMTP id d12mr421951bka.61.1256944785690; Fri, 30 Oct 2009 16:19:45 -0700 (PDT) Received: from ?172.17.1.247? (fw.sth1.keff.org [212.247.153.198]) by mx.google.com with ESMTPS id d13sm991843fka.52.2009.10.30.16.19.44 (version=SSLv3 cipher=RC4-MD5); Fri, 30 Oct 2009 16:19:44 -0700 (PDT) Sender: Sebastian Hyrwall Message-ID: <4AEB911E.1070104@keff.org> Date: Sat, 31 Oct 2009 02:21:34 +0100 From: Sebastian Hyrwall User-Agent: Thunderbird 2.0.0.19 (X11/20081209) MIME-Version: 1.0 To: Chuck Swiger References: <4AEB7AE8.5090101@keff.org> <18C758A7-1908-4D1A-BDCA-80FF7FD8BC22@mac.com> <4AEB834D.1050907@keff.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Hi. /31 on ethernet links X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Oct 2009 23:19:47 -0000 Chuck Swiger skrev: > On Oct 30, 2009, at 5:22 PM, Sebastian Hyrwall wrote: >>> A /31 subnet is only defined for point-to-point network links, per: >>> >>> http://www.rfc-editor.org/rfc/rfc3021.txt >>> >>> Ordinary ethernet links have BROADCAST flag set instead of POINTOPOINT. >>> >> >> Well how do I set the POINTOPOINT flag and remove the BROADCAST-flag >> on ethernet links? Or are you implying that it does not belong on >> ethernet links :) Cause Cisco and Linux support /31 (ptp's) on >> ordinary ethernet links. > > Ethernet point-to-point links are normally handled by ppp / pppd in > PPPoE mode, but possibly something like: > > ifconfig en0 inet 192.1.1.10 inet 192.1.1.2 > > ...would give you a POINTOPOINT link instead. If not, you can > probably fake things out by either using a /30 and wrapping the /31 > inside, or using a /32 and an explicit default route via your > ethernet interface. > Unfortunetly that doesn't work. It just sets 192.1.1.2 as broadcast. Well wrapping a /31 inside of a /30 kinda defeats the purpose :) If Cisco,Linux and NetBSD support it so should FreeBSD imho. > Regards, From owner-freebsd-net@FreeBSD.ORG Sat Oct 31 01:03:06 2009 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 84E831065679; Sat, 31 Oct 2009 01:03:06 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id 14E188FC17; Sat, 31 Oct 2009 01:03:05 +0000 (UTC) Received: from lstewart-laptop.caia.swin.edu.au (216-239-45-4.google.com [216.239.45.4]) (authenticated bits=0) by lauren.room52.net (8.14.3/8.14.3) with ESMTP id n9V12u3M062828 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 31 Oct 2009 12:02:57 +1100 (EST) (envelope-from lstewart@freebsd.org) Message-ID: <4AEB8CBC.5050705@freebsd.org> Date: Fri, 30 Oct 2009 18:02:52 -0700 From: Lawrence Stewart User-Agent: Thunderbird 2.0.0.23 (X11/20090909) MIME-Version: 1.0 To: Doug Barton References: <4AE77437.4090700@FreeBSD.org> In-Reply-To: <4AE77437.4090700@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,RDNS_DYNAMIC, SPF_SOFTFAIL autolearn=disabled version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on lauren.room52.net Cc: freebsd-net@freebsd.org, benjsc@freebsd.org, sam@freebsd.org, thompsa@freebsd.org Subject: WPI panic (was: Can we turn off WPI_DEBUG) 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, 31 Oct 2009 01:03:06 -0000 Doug Barton wrote: > I cc'ed those who seem to have put the most/recent effort into > sys/dev/wpi. > > Is there any objection to turning off WPI_DEBUG by default? it creates > a lot of spam that the average user doesn't need. I use my 3945abg > every day and haven't had any problems with it for ages so I think > it's safe to say we're out of the period were debug by default is needed? Doug, have you ever experienced the issue with your 3945 card that I reported here: http://lists.freebsd.org/pipermail/freebsd-net/2009-October/023348.html I'm guessing you haven't by your comment about lack of problems. Do you run with INVARIANTS in your kernel? Cheers, Lawrence From owner-freebsd-net@FreeBSD.ORG Sat Oct 31 01:22:16 2009 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 2A7F81065679 for ; Sat, 31 Oct 2009 01:22:16 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id AE1788FC15 for ; Sat, 31 Oct 2009 01:22:15 +0000 (UTC) Received: (qmail 15231 invoked by uid 399); 31 Oct 2009 01:22:14 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 31 Oct 2009 01:22:14 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4AEB9150.1040304@FreeBSD.org> Date: Fri, 30 Oct 2009 18:22:24 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: Lawrence Stewart References: <4AE77437.4090700@FreeBSD.org> <4AEB8CBC.5050705@freebsd.org> In-Reply-To: <4AEB8CBC.5050705@freebsd.org> X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, benjsc@freebsd.org, sam@freebsd.org, thompsa@freebsd.org Subject: Re: WPI 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: Sat, 31 Oct 2009 01:22:16 -0000 Lawrence Stewart wrote: > Doug Barton wrote: >> I cc'ed those who seem to have put the most/recent effort into >> sys/dev/wpi. >> >> Is there any objection to turning off WPI_DEBUG by default? it creates >> a lot of spam that the average user doesn't need. I use my 3945abg >> every day and haven't had any problems with it for ages so I think >> it's safe to say we're out of the period were debug by default is needed? > > Doug, have you ever experienced the issue with your 3945 card that I > reported here: > > http://lists.freebsd.org/pipermail/freebsd-net/2009-October/023348.html > > I'm guessing you haven't by your comment about lack of problems. No, I have not had those problems at all. I routinely associate with both WPA and WPA2 routers, as well as open routers at coffee shops and such. > Do you run with INVARIANTS in your kernel? Yes, and up till recently I've been running with witness as well. Wish I could be more help, Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-net@FreeBSD.ORG Sat Oct 31 01:32:00 2009 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 0E1121065695 for ; Sat, 31 Oct 2009 01:32:00 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by mx1.freebsd.org (Postfix) with ESMTP id E6C648FC15 for ; Sat, 31 Oct 2009 01:31:59 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=rmac.psg.com) by ran.psg.com with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1N42ow-000A8f-05; Sat, 31 Oct 2009 01:31:58 +0000 Received: from rmac.local.psg.com (localhost [127.0.0.1]) by rmac.psg.com (Postfix) with ESMTP id 800BB2BCB678; Sat, 31 Oct 2009 10:31:57 +0900 (JST) Date: Sat, 31 Oct 2009 10:31:57 +0900 Message-ID: From: Randy Bush To: Chuck Swiger In-Reply-To: <18C758A7-1908-4D1A-BDCA-80FF7FD8BC22@mac.com> References: <4AEB7AE8.5090101@keff.org> <18C758A7-1908-4D1A-BDCA-80FF7FD8BC22@mac.com> User-Agent: Wanderlust/2.15.5 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: Sebastian Hyrwall , freebsd-net@freebsd.org Subject: Re: Hi. /31 on ethernet links 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, 31 Oct 2009 01:32:00 -0000 /31 on point to point ether is exceedingly common in inter-router topologies. you may be amused to also read draft-kohno-ipv6-prefixlen-p2p-00.txt randy From owner-freebsd-net@FreeBSD.ORG Sat Oct 31 08:01:55 2009 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 DF1BC106566B for ; Sat, 31 Oct 2009 08:01:55 +0000 (UTC) (envelope-from sthaug@nethelp.no) Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by mx1.freebsd.org (Postfix) with SMTP id EB3858FC1C for ; Sat, 31 Oct 2009 08:01:54 +0000 (UTC) Received: (qmail 83256 invoked from network); 31 Oct 2009 08:01:52 -0000 Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 31 Oct 2009 08:01:52 -0000 Date: Sat, 31 Oct 2009 09:01:52 +0100 (CET) Message-Id: <20091031.090152.74670981.sthaug@nethelp.no> To: sh@keff.org From: sthaug@nethelp.no In-Reply-To: <4AEB834D.1050907@keff.org> References: <4AEB7AE8.5090101@keff.org> <18C758A7-1908-4D1A-BDCA-80FF7FD8BC22@mac.com> <4AEB834D.1050907@keff.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Hi. /31 on ethernet links 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, 31 Oct 2009 08:01:55 -0000 > > A /31 subnet is only defined for point-to-point network links, per: > > > > http://www.rfc-editor.org/rfc/rfc3021.txt > > > > Ordinary ethernet links have BROADCAST flag set instead of POINTOPOINT. > > > > Regards, > Well how do I set the POINTOPOINT flag and remove the BROADCAST-flag on > ethernet links? Or are you implying that it does not belong on ethernet > links :) > Cause Cisco and Linux support /31 (ptp's) on ordinary ethernet links. No, Cisco does not *support* it. They make it available, which is a completely different story. We have asked Cisco repeatedly, through official channels, whether they *support* /31 on Ethernet links. The answer is always that it *may* work, use at your own peril. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-net@FreeBSD.ORG Sat Oct 31 09:56:44 2009 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 D151F106566B for ; Sat, 31 Oct 2009 09:56:44 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by mx1.freebsd.org (Postfix) with ESMTP id B0E478FC0C for ; Sat, 31 Oct 2009 09:56:44 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=rmac.psg.com) by ran.psg.com with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1N4AhP-000Bbf-92; Sat, 31 Oct 2009 09:56:43 +0000 Received: from rmac.local.psg.com (localhost [127.0.0.1]) by rmac.psg.com (Postfix) with ESMTP id C4C192BD13E5; Sat, 31 Oct 2009 18:56:42 +0900 (JST) Date: Sat, 31 Oct 2009 18:56:42 +0900 Message-ID: From: Randy Bush To: sthaug@nethelp.no In-Reply-To: <20091031.090152.74670981.sthaug@nethelp.no> References: <4AEB7AE8.5090101@keff.org> <18C758A7-1908-4D1A-BDCA-80FF7FD8BC22@mac.com> <4AEB834D.1050907@keff.org> <20091031.090152.74670981.sthaug@nethelp.no> User-Agent: Wanderlust/2.15.5 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: freebsd-net@freebsd.org Subject: Re: Hi. /31 on ethernet links 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, 31 Oct 2009 09:56:44 -0000 > No, Cisco does not *support* it. They make it available, which is a > completely different story. > > We have asked Cisco repeatedly, through official channels, whether > they *support* /31 on Ethernet links. The answer is always that it > *may* work, use at your own peril. i have managed O(10^3) ciscos in isp backbone(s). /31s predominate for ether links in that space. though i suspect there is more multipoint in the enterprise space. we need to be able to use /31s and /127s on freebsd if it is to be used in the routing space. randy From owner-freebsd-net@FreeBSD.ORG Sat Oct 31 10:08:39 2009 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 D66EC106568B for ; Sat, 31 Oct 2009 10:08:39 +0000 (UTC) (envelope-from sthaug@nethelp.no) Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by mx1.freebsd.org (Postfix) with SMTP id 247C18FC0C for ; Sat, 31 Oct 2009 10:08:38 +0000 (UTC) Received: (qmail 14394 invoked from network); 31 Oct 2009 10:08:37 -0000 Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 31 Oct 2009 10:08:37 -0000 Date: Sat, 31 Oct 2009 11:08:37 +0100 (CET) Message-Id: <20091031.110837.41706473.sthaug@nethelp.no> To: randy@psg.com From: sthaug@nethelp.no In-Reply-To: References: <4AEB834D.1050907@keff.org> <20091031.090152.74670981.sthaug@nethelp.no> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Hi. /31 on ethernet links 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, 31 Oct 2009 10:08:39 -0000 > > We have asked Cisco repeatedly, through official channels, whether > > they *support* /31 on Ethernet links. The answer is always that it > > *may* work, use at your own peril. > > i have managed O(10^3) ciscos in isp backbone(s). /31s predominate for > ether links in that space. though i suspect there is more multipoint in > the enterprise space. > > we need to be able to use /31s and /127s on freebsd if it is to be used > in the routing space. I agree about that. However, I was simply reacting to the claim that it was *supported* by Cisco. We have asked both Cisco and Juniper, and neither company is willing to state that it is *supported*. Our Ethernet core links are /30 for IPv4 and /124 for IPv6. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-net@FreeBSD.ORG Sat Oct 31 10:41:28 2009 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 CD1B01065670 for ; Sat, 31 Oct 2009 10:41:28 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by mx1.freebsd.org (Postfix) with ESMTP id B3A3F8FC17 for ; Sat, 31 Oct 2009 10:41:28 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=rmac.psg.com) by ran.psg.com with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1N4BOi-000Bhn-77; Sat, 31 Oct 2009 10:41:28 +0000 Received: from rmac.local.psg.com (localhost [127.0.0.1]) by rmac.psg.com (Postfix) with ESMTP id AC5302BD157A; Sat, 31 Oct 2009 19:41:27 +0900 (JST) Date: Sat, 31 Oct 2009 19:41:27 +0900 Message-ID: From: Randy Bush To: sthaug@nethelp.no In-Reply-To: <20091031.110837.41706473.sthaug@nethelp.no> References: <4AEB834D.1050907@keff.org> <20091031.090152.74670981.sthaug@nethelp.no> <20091031.110837.41706473.sthaug@nethelp.no> User-Agent: Wanderlust/2.15.5 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: freebsd-net@freebsd.org Subject: Re: Hi. /31 on ethernet links 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, 31 Oct 2009 10:41:28 -0000 > However, I was simply reacting to the claim that it was *supported* by > Cisco. have you noticed a difference in the bug rate between things that are 'supported by cisco' and those that just happen to be there? :) but you're right. i liked. our p2ps are /30s, not /31s. and we're moving from /126 to /127. randy From owner-freebsd-net@FreeBSD.ORG Sat Oct 31 11:42:25 2009 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 B5C5F1065676 for ; Sat, 31 Oct 2009 11:42:25 +0000 (UTC) (envelope-from nvass9573@gmx.com) Received: from mail.gmx.com (unknown [213.165.64.42]) by mx1.freebsd.org (Postfix) with SMTP id 092998FC19 for ; Sat, 31 Oct 2009 11:42:24 +0000 (UTC) Received: (qmail invoked by alias); 31 Oct 2009 11:42:23 -0000 Received: from adsl-49.91.140.20.tellas.gr (EHLO [169.254.0.102]) [91.140.20.49] by mail.gmx.com (mp-eu003) with SMTP; 31 Oct 2009 12:42:23 +0100 X-Authenticated: #46156728 X-Provags-ID: V01U2FsdGVkX18InRhxSmYIcUcicOCiMMiWISUg74U504ztPgqi8o asyVEThvPoyNmO Message-ID: <4AEC2297.40805@gmx.com> Date: Sat, 31 Oct 2009 13:42:15 +0200 From: Nikos Vassiliadis User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Sebastian Hyrwall References: <4AEB7AE8.5090101@keff.org> <18C758A7-1908-4D1A-BDCA-80FF7FD8BC22@mac.com> <4AEB834D.1050907@keff.org> <4AEB911E.1070104@keff.org> In-Reply-To: <4AEB911E.1070104@keff.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.75 Cc: freebsd-net@freebsd.org Subject: Re: Hi. /31 on ethernet links 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, 31 Oct 2009 11:42:25 -0000 Sebastian Hyrwall wrote: > Chuck Swiger skrev: >> inside, or using a /32 and an explicit default route via your >> ethernet interface. >> > Unfortunetly that doesn't work. It just sets 192.1.1.2 as broadcast. > > Well wrapping a /31 inside of a /30 kinda defeats the purpose :) > You could still use a /32 and then add a route for the other IP via the ethernet interface. This is effectively the same with a /31. From owner-freebsd-net@FreeBSD.ORG Sat Oct 31 13:35:17 2009 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 453EC106566C for ; Sat, 31 Oct 2009 13:35:17 +0000 (UTC) (envelope-from zibbe@cisko.org) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id D005D8FC13 for ; Sat, 31 Oct 2009 13:35:16 +0000 (UTC) Received: by bwz5 with SMTP id 5so4625761bwz.3 for ; Sat, 31 Oct 2009 06:35:15 -0700 (PDT) Received: by 10.204.33.194 with SMTP id i2mr2164456bkd.146.1256996115418; Sat, 31 Oct 2009 06:35:15 -0700 (PDT) Received: from ?172.17.1.247? (fw.sth1.keff.org [212.247.153.198]) by mx.google.com with ESMTPS id c28sm2581981fka.54.2009.10.31.06.35.13 (version=SSLv3 cipher=RC4-MD5); Sat, 31 Oct 2009 06:35:13 -0700 (PDT) Sender: Sebastian Hyrwall Message-ID: <4AEC599F.90202@keff.org> Date: Sat, 31 Oct 2009 16:37:03 +0100 From: Sebastian Hyrwall User-Agent: Thunderbird 2.0.0.19 (X11/20081209) MIME-Version: 1.0 To: Nikos Vassiliadis References: <4AEB7AE8.5090101@keff.org> <18C758A7-1908-4D1A-BDCA-80FF7FD8BC22@mac.com> <4AEB834D.1050907@keff.org> <4AEB911E.1070104@keff.org> <4AEC2297.40805@gmx.com> In-Reply-To: <4AEC2297.40805@gmx.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Hi. /31 on ethernet links 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, 31 Oct 2009 13:35:17 -0000 Nikos Vassiliadis skrev: > Sebastian Hyrwall wrote: >> Chuck Swiger skrev: >>> inside, or using a /32 and an explicit default route via your >>> ethernet interface. >>> >> Unfortunetly that doesn't work. It just sets 192.1.1.2 as broadcast. >> >> Well wrapping a /31 inside of a /30 kinda defeats the purpose :) >> > > You could still use a /32 and then add a route for the other IP via > the ethernet interface. This is effectively the same with a /31. > Does not work, # ifconfig re0.212 172.16.25.10 netmask 255.255.255.255 # route add 172.16.25.11 -iface re0.212 add host 172.16.25.11: gateway re0.212 # ping 172.16.25.11 36 bytes from 172.16.25.10: Redirect Host(New addr: 172.16.25.11) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 0054 bdbb 0 0000 40 01 0000 172.16.25.10 172.16.25.11 From owner-freebsd-net@FreeBSD.ORG Sat Oct 31 15:42:34 2009 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 1A2BF106568B for ; Sat, 31 Oct 2009 15:42:34 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 9DD988FC17 for ; Sat, 31 Oct 2009 15:42:33 +0000 (UTC) Received: by bwz5 with SMTP id 5so4715753bwz.3 for ; Sat, 31 Oct 2009 08:42:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=1qtj9zCvNgusgtiuG9uTTR+0V1hp72ZhCe4tnEcotvc=; b=YNmzPa6/A1Xs/07fpa18XzeOPuD7V6vym8FAYWCiz/2v9mSOP7LJJkGOzgtljEZy8t r1gMIIiWdJ7441PfpM0JCRLnjylD5aYEEZkn/YgYM9Ly7L6Dfh7xsvYtP10Dgt/ufLIT cKJ6FUDE+K9Esjjd1FeygSk9mEftcxAxQPhvs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ib7WeqqmhgvI9N/gDKxqBoL/jDLK23qboFCY2iwLpvn0P2WDRVaJh31IQMbTIQBvCS AUv1AFq5ewvTnuGi15yKiypobYFTqOzPluHZ1/gFrMa16Zupvujd0YfFE5ncYFfQEl/u R9qDH21se07zwUGuiJUm9E8RP1Y29NEVnOhdo= MIME-Version: 1.0 Received: by 10.204.34.73 with SMTP id k9mr2235555bkd.45.1257003752363; Sat, 31 Oct 2009 08:42:32 -0700 (PDT) In-Reply-To: <200910300926.32286.bschmidt@techwires.net> References: <20091009170839.142800@gmx.net> <11167f520910241241o6a1ada3cmf076add6374a1add@mail.gmail.com> <200910251024.06856.bschmidt@techwires.net> <200910300926.32286.bschmidt@techwires.net> Date: Sat, 31 Oct 2009 15:42:31 +0000 Message-ID: <179b97fb0910310842o63b48746r9380e4bf29cdc856@mail.gmail.com> From: Brandon Gooch To: Bernhard Schmidt Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "Sam Fourman Jr." , freebsd-net@freebsd.org, Rui Paulo Subject: Re: Intel WiFi 5100/5300 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, 31 Oct 2009 15:42:34 -0000 On Fri, Oct 30, 2009 at 8:26 AM, Bernhard Schmidt wrote: > On Sunday 25 October 2009 10:24:06 Bernhard Schmidt wrote: >> On Saturday 24 October 2009 21:41:39 Sam Fourman Jr. wrote: >> > Just wanted to make everyone aware that OpenBSD just 1 hour ago commit= ed >> > a bunch of changes to their iwn driver. maybe some of it is useful for >> > FreeBSD as well? >> >> Definitely, I'll look into that. > > Another update: > > * ICT interrupts for 5000/6000 series > * New firmware > * Initial support for 1000 series and initial bits for upcoming 6000 =A0s= eries > (untested as hardware is not available to the general public) > * Many bug fixes, including workarounds for hardware bugs > * Addresses kern/140036 > > Most of this stuff has been obtained from OpeBSD. Testes/Feedback welcome= ! > > http://techwires.net/~bschmidt/patches/freebsd/iwn/iwn_merge_20081028.dif= f.bz2 > > -- > Bernhard This is working VERY well with my 4965. I haven't had a single issue with stability, no firmware errors, I associate with APs much more quickly, and it's measurably faster. Thanks for all of your hard work Bernhard! Hope we see this in the tree soo= n... -Brandon From owner-freebsd-net@FreeBSD.ORG Sat Oct 31 16:01:46 2009 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 E01331065692 for ; Sat, 31 Oct 2009 16:01:46 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 6C7688FC24 for ; Sat, 31 Oct 2009 16:01:46 +0000 (UTC) Received: by bwz5 with SMTP id 5so4729465bwz.3 for ; Sat, 31 Oct 2009 09:01:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=BLOksJIUo4yGsJFVGS9DmY7HtRaljSvKKiFDKajkhNQ=; b=Wrggzjr06o+hPCGB0jfMVs0xXSLWnf6BdKehEUYwTdEZxbYK+JditxzU4nNbwSPrv3 jMLOSlsRuq0309krh8wz21UmGpTpqvGEFVlw6yzYqzGWeSeTbAGNqpa5FuDvJgDHVpib N/PbfW6Yr4YQ6pIyM3tuKeuHpnxLp73RGh5KU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=J/UCBUj0382G5UhKu1/2wxvB9DyM5elnhk6KsRG6FMmg+S7uyXxcEkiVV9Evnhbc3d X3Ob7RsPTDXnxxAcmYNDxgpmLpASd14AAc0Y4LXu1igq8mTMoPLvv22A6PiYvBFw9Dwa 0HB5TXH4WifsVtpdowgAyI3JRbzYRQ/6CFDg0= MIME-Version: 1.0 Received: by 10.204.154.150 with SMTP id o22mr2207715bkw.154.1257004905230; Sat, 31 Oct 2009 09:01:45 -0700 (PDT) In-Reply-To: <200910300926.32286.bschmidt@techwires.net> References: <20091009170839.142800@gmx.net> <11167f520910241241o6a1ada3cmf076add6374a1add@mail.gmail.com> <200910251024.06856.bschmidt@techwires.net> <200910300926.32286.bschmidt@techwires.net> Date: Sat, 31 Oct 2009 16:01:45 +0000 Message-ID: <179b97fb0910310901tf8686b1u87a21c3408c93471@mail.gmail.com> From: Brandon Gooch To: Bernhard Schmidt Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "Sam Fourman Jr." , freebsd-net@freebsd.org, Rui Paulo Subject: Re: Intel WiFi 5100/5300 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, 31 Oct 2009 16:01:47 -0000 On Fri, Oct 30, 2009 at 8:26 AM, Bernhard Schmidt wrote: > On Sunday 25 October 2009 10:24:06 Bernhard Schmidt wrote: >> On Saturday 24 October 2009 21:41:39 Sam Fourman Jr. wrote: >> > Just wanted to make everyone aware that OpenBSD just 1 hour ago commit= ed >> > a bunch of changes to their iwn driver. maybe some of it is useful for >> > FreeBSD as well? >> >> Definitely, I'll look into that. > > Another update: > > * ICT interrupts for 5000/6000 series > * New firmware > * Initial support for 1000 series and initial bits for upcoming 6000 =A0s= eries > (untested as hardware is not available to the general public) > * Many bug fixes, including workarounds for hardware bugs > * Addresses kern/140036 > > Most of this stuff has been obtained from OpeBSD. Testes/Feedback welcome= ! > > http://techwires.net/~bschmidt/patches/freebsd/iwn/iwn_merge_20081028.dif= f.bz2 > > -- > Bernhard This is working VERY well with my 4965. In fact, I haven't had a single issue with stability, I associate with APs much more quickly, and it's measurably faster. Thanks Bernhard From owner-freebsd-net@FreeBSD.ORG Sat Oct 31 17:46:18 2009 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 1E9B91065670 for ; Sat, 31 Oct 2009 17:46:18 +0000 (UTC) (envelope-from freebsd@levsha.org.ua) Received: from expo.ukrweb.net (mail.univua.net [91.202.128.78]) by mx1.freebsd.org (Postfix) with ESMTP id CE2DA8FC1D for ; Sat, 31 Oct 2009 17:46:17 +0000 (UTC) Received: from levsha by expo.ukrweb.net with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1N4I23-0008zd-6O; Sat, 31 Oct 2009 19:46:31 +0200 Date: Sat, 31 Oct 2009 19:46:31 +0200 From: Mykola Dzham To: Bernhard Schmidt Message-ID: <20091031174631.GA32588@expo.ukrweb.net> References: <20091009170839.142800@gmx.net> <11167f520910241241o6a1ada3cmf076add6374a1add@mail.gmail.com> <200910251024.06856.bschmidt@techwires.net> <200910300926.32286.bschmidt@techwires.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200910300926.32286.bschmidt@techwires.net> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-net@freebsd.org Subject: Re: Intel WiFi 5100/5300 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, 31 Oct 2009 17:46:18 -0000 Bernhard Schmidt wrote: > On Sunday 25 October 2009 10:24:06 Bernhard Schmidt wrote: > > On Saturday 24 October 2009 21:41:39 Sam Fourman Jr. wrote: > > > Just wanted to make everyone aware that OpenBSD just 1 hour ago commited > > > a bunch of changes to their iwn driver. maybe some of it is useful for > > > FreeBSD as well? > > > > Definitely, I'll look into that. > > Another update: > > * ICT interrupts for 5000/6000 series > * New firmware > * Initial support for 1000 series and initial bits for upcoming 6000 series > (untested as hardware is not available to the general public) > * Many bug fixes, including workarounds for hardware bugs > * Addresses kern/140036 > > Most of this stuff has been obtained from OpeBSD. Testes/Feedback welcome! > > http://techwires.net/~bschmidt/patches/freebsd/iwn/iwn_merge_20081028.diff.bz2 This update fix my panic. And now if_iwn detect my Intel 5100BGN : iwn0: mem 0xec800000-0xec801fff irq 17 at device 0.0 on pci6 iwn0: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xec800000 iwn0: attempting to allocate 1 MSI vectors (1 supported) msi: routing MSI IRQ 259 to local APIC 0 vector 48 iwn0: using IRQ 259 for MSI iwn0: MIMO 1T2R, MoW, address 00:16:ea:5c:6c:d8 iwn0: [MPSAFE] iwn0: [ITHREAD] iwn0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps iwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps iwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps iwn0: 11na MCS: 15Mbps 30Mbps 45Mbps 60Mbps 90Mbps 120Mbps 135Mbps 150Mbps 30Mbps 60Mbps 90Mbps 120Mbps 180Mbps 240Mbps 270Mbps 300Mbp s iwn0: 11ng MCS: 15Mbps 30Mbps 45Mbps 60Mbps 90Mbps 120Mbps 135Mbps 150Mbps 30Mbps 60Mbps 90Mbps 120Mbps 180Mbps 240Mbps 270Mbps 300Mbp s And now my card cat scan networks and connect to AP when i create wlan interface manually: ifconfig wlan0 create wlandev iwn0 wlanmode sta ifconfig wlan0 up /etc/rc.d/wpa_supplicant start wlan0 dhclient wlan0 But sometimes i receive error: iwn0: iwn5000_post_alive: could not configure WiMAX coexistence, error 35 iwn0: iwn_init_locked: could not initialize hardware, error 35 And adapter not work after this error kldunload if_iwn && kldload if_iwn does not fix problem, only reboot. If i add any other options to ifconfig wlan0 create (for example mode, country, or up) i always receive this error. Thanks! -- LEFT-(UANIC|RIPE) JID: levsha@jabber.net.ua PGP fingerprint: 1BCD 7C80 2E04 7282 C944 B0E0 7E67 619E 4E72 9280 From owner-freebsd-net@FreeBSD.ORG Sat Oct 31 18:30:08 2009 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 9D44E106566B for ; Sat, 31 Oct 2009 18:30:08 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [195.88.108.3]) by mx1.freebsd.org (Postfix) with ESMTP id 5636B8FC18 for ; Sat, 31 Oct 2009 18:30:08 +0000 (UTC) Received: from localhost (amavis.fra.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id F3A1241C64C; Sat, 31 Oct 2009 19:30:06 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([195.88.108.3]) by localhost (amavis.fra.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id nU8nAO1j81xg; Sat, 31 Oct 2009 19:30:06 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id 2C18B41C677; Sat, 31 Oct 2009 19:30:06 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id C56384448E6; Sat, 31 Oct 2009 18:27:52 +0000 (UTC) Date: Sat, 31 Oct 2009 18:27:52 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Randy Bush In-Reply-To: Message-ID: <20091031180545.C91695@maildrop.int.zabbadoz.net> References: <4AEB834D.1050907@keff.org> <20091031.090152.74670981.sthaug@nethelp.no> <20091031.110837.41706473.sthaug@nethelp.no> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, sthaug@nethelp.no Subject: Re: Hi. /31 on ethernet links 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, 31 Oct 2009 18:30:08 -0000 On Sat, 31 Oct 2009, Randy Bush wrote: Hi, >> However, I was simply reacting to the claim that it was *supported* by >> Cisco. > > have you noticed a difference in the bug rate between things that are > 'supported by cisco' and those that just happen to be there? :) > > but you're right. i liked. our p2ps are /30s, not /31s. and we're > moving from /126 to /127. I am sorry, I couldn't resist; I hope you won't take everything at face value... though I hope you'll seriously think of some things... Oh what /30 /31 bikeshed and how old it is? I prefer to speak of p_t_p for point-to-point in contrast to p2p for peer-2-peer btw. I seem to remember that it used to be like that but unfortunately neither the vendors nor the people who are writing (IETF) specs make a difference anymore. I do not understand, though I know some, people who are not using a /64 on an Ethernet IPv6 link; may it be ptp or not. I know there is an old enough bikeshed out about that as well as some prosposed standards. /127 really sounds fighting a system to me. It's not that you couldn't address each atom in hour house already I'd wildy guess with a /48 but ... some people always have trouble freeing their mind from things that were like that 20 years and further back. Have you ever thought of limiting your scoped link-local space on Ethernet? So why do you need valid IPs on your interfaces at all? Why do you need more than a single global unicast address? Save your IPv6 addresses for the neighbour's fridges and toasters. /bz -- Bjoern A. Zeeb Even on Oct. 31st there is no candy with this mail. From owner-freebsd-net@FreeBSD.ORG Sat Oct 31 20:21:48 2009 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 EBDA71065670 for ; Sat, 31 Oct 2009 20:21:48 +0000 (UTC) (envelope-from iprebeg@freebsd.org) Received: from maja.zesoi.fer.hr (maja.zesoi.fer.hr [161.53.64.3]) by mx1.freebsd.org (Postfix) with ESMTP id A99C98FC12 for ; Sat, 31 Oct 2009 20:21:48 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by maja.zesoi.fer.hr (Postfix) with ESMTP id 483E08023 for ; Sat, 31 Oct 2009 21:21:47 +0100 (CET) Received: from maja.zesoi.fer.hr ([127.0.0.1]) by localhost (maja.zesoi.fer.hr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S1wkMrmxVjrD for ; Sat, 31 Oct 2009 21:21:44 +0100 (CET) Received: from valeria.zesoi.fer.hr (valeria.zesoi.fer.hr [161.53.64.29]) by maja.zesoi.fer.hr (Postfix) with ESMTP id 79EF19FB92 for ; Sat, 31 Oct 2009 21:21:44 +0100 (CET) Date: Sat, 31 Oct 2009 21:12:26 +0100 From: iprebeg@freebsd.org To: freebsd-net@freebsd.org Message-ID: <20091031201226.GA6044@valeria.zesoi.fer.hr> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lrZ03NoBR/3+SXJZ" Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Subject: AR5212 wlan adapter 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, 31 Oct 2009 20:21:49 -0000 --lrZ03NoBR/3+SXJZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I have D-LINK DWA-520 adapter (AR5212 chipset) running on 8.0-BETA2 machine (same thing on -RC1). It appears as ath0 interface, but I can't get scan results.=20 ifconfig ath0 up scan=20 reports that it can't get scan results. When I add wpa_supplicant configuration and try to start it, it reports errors with IOCTL.=20 Do I miss something here? Any help? --lrZ03NoBR/3+SXJZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) iEYEARECAAYFAkrsmioACgkQHE64Rwv9Fd5dZgCfarPQEPuK/7a4Zj1UOgLfo6yT c54AnRXCxLOW+7bHab4koVTg9VjewXNV =rGEQ -----END PGP SIGNATURE----- --lrZ03NoBR/3+SXJZ-- From owner-freebsd-net@FreeBSD.ORG Sat Oct 31 20:34:49 2009 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 94BCF1065670 for ; Sat, 31 Oct 2009 20:34:49 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mx01.netsrc.de (mx01.netsrc.de [89.107.71.100]) by mx1.freebsd.org (Postfix) with ESMTP id 3B25E8FC12 for ; Sat, 31 Oct 2009 20:34:49 +0000 (UTC) Received: from maja.lab.techwires.net (dslb-088-065-215-154.pools.arcor-ip.net [88.65.215.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.netsrc.de (Postfix) with ESMTP id 687B0192FD9; Sat, 31 Oct 2009 21:34:47 +0100 (CET) Received: from maja.lab.techwires.net (localhost [127.0.0.1]) by maja.lab.techwires.net (8.14.3/8.14.3) with ESMTP id n9VKYmmF039661; Sat, 31 Oct 2009 21:34:48 +0100 (CET) (envelope-from bschmidt@techwires.net) Received: (from bschmidt@localhost) by maja.lab.techwires.net (8.14.3/8.14.3/Submit) id n9VKYmWR039660; Sat, 31 Oct 2009 21:34:48 +0100 (CET) (envelope-from bschmidt@techwires.net) X-Authentication-Warning: maja.lab.sad1.techwires.net: bschmidt set sender to bschmidt@techwires.net using -f From: Bernhard Schmidt To: freebsd-net@freebsd.org Date: Sat, 31 Oct 2009 21:34:47 +0100 User-Agent: KMail/1.12.1 (FreeBSD/9.0-CURRENT; KDE/4.3.1; amd64; ; ) References: <20091031201226.GA6044@valeria.zesoi.fer.hr> In-Reply-To: <20091031201226.GA6044@valeria.zesoi.fer.hr> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <200910312134.47541.bschmidt@techwires.net> Cc: iprebeg@freebsd.org Subject: Re: AR5212 wlan adapter 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, 31 Oct 2009 20:34:49 -0000 On Saturday 31 October 2009 21:12:26 iprebeg@freebsd.org wrote: > I have D-LINK DWA-520 adapter (AR5212 chipset) running on 8.0-BETA2 > machine (same thing on -RC1). It appears as ath0 interface, but I can't > get scan results. > ifconfig ath0 up scan > reports that it can't get scan results. > When I add wpa_supplicant configuration and try to start it, it reports > errors with IOCTL. > > Do I miss something here? > > Any help? man ath ifconfig wlan0 create wlandev ath0 ifconfig wlan0 up ifconfig wlan0 scan -- Bernhard From owner-freebsd-net@FreeBSD.ORG Sat Oct 31 21:03:53 2009 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 13DC0106566B for ; Sat, 31 Oct 2009 21:03:53 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mx01.netsrc.de (mx01.netsrc.de [89.107.71.100]) by mx1.freebsd.org (Postfix) with ESMTP id C3C1F8FC13 for ; Sat, 31 Oct 2009 21:03:52 +0000 (UTC) Received: from maja.lab.techwires.net (dslb-088-065-215-154.pools.arcor-ip.net [88.65.215.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.netsrc.de (Postfix) with ESMTP id 9175D192FD9; Sat, 31 Oct 2009 22:03:51 +0100 (CET) Received: from maja.lab.techwires.net (localhost [127.0.0.1]) by maja.lab.techwires.net (8.14.3/8.14.3) with ESMTP id n9VL3roJ002127; Sat, 31 Oct 2009 22:03:53 +0100 (CET) (envelope-from bschmidt@techwires.net) Received: (from bschmidt@localhost) by maja.lab.techwires.net (8.14.3/8.14.3/Submit) id n9VL3rRi002126; Sat, 31 Oct 2009 22:03:53 +0100 (CET) (envelope-from bschmidt@techwires.net) X-Authentication-Warning: maja.lab.sad1.techwires.net: bschmidt set sender to bschmidt@techwires.net using -f From: Bernhard Schmidt To: freebsd-net@freebsd.org Date: Sat, 31 Oct 2009 22:03:53 +0100 User-Agent: KMail/1.12.1 (FreeBSD/9.0-CURRENT; KDE/4.3.1; amd64; ; ) References: <20091009170839.142800@gmx.net> <200910300926.32286.bschmidt@techwires.net> <20091031174631.GA32588@expo.ukrweb.net> In-Reply-To: <20091031174631.GA32588@expo.ukrweb.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200910312203.53266.bschmidt@techwires.net> Cc: Mykola Dzham Subject: Re: Intel WiFi 5100/5300 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, 31 Oct 2009 21:03:53 -0000 On Saturday 31 October 2009 18:46:31 Mykola Dzham wrote: > But sometimes i receive error: > > iwn0: iwn5000_post_alive: could not configure WiMAX coexistence, error 35 > iwn0: iwn_init_locked: could not initialize hardware, error 35 > > And adapter not work after this error kldunload if_iwn && kldload > if_iwn does not fix problem, only reboot. > If i add any other options to ifconfig wlan0 create (for example mode, > country, or up) i always receive this error. Does it help if you add a bit of delay between kldunload and kldload? I have the feeling that your device is either still powered down or gets powered down on the way. somewhere. I'm not able to reproduce this myself, yet I'm trying. Thanks for the feedback! By the way, current iwn development is done here: http://svn.techwires.net/ -- Bernhard From owner-freebsd-net@FreeBSD.ORG Sat Oct 31 23:40:03 2009 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 E9F0F106566B for ; Sat, 31 Oct 2009 23:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DA2B68FC0A for ; Sat, 31 Oct 2009 23:40:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9VNe3rv022342 for ; Sat, 31 Oct 2009 23:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9VNe372022341; Sat, 31 Oct 2009 23:40:03 GMT (envelope-from gnats) Date: Sat, 31 Oct 2009 23:40:03 GMT Message-Id: <200910312340.n9VNe372022341@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Benjamin Kaduk Cc: Subject: Re: kern/140036: [iwn] [lor] lock order reversal with iwn0_com_lock and iwn0 softc lock X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Benjamin Kaduk List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Oct 2009 23:40:04 -0000 The following reply was made to PR kern/140036; it has been noted by GNATS. From: Benjamin Kaduk To: Bernhard Schmidt Cc: bug-followup@freebsd.org Subject: Re: kern/140036: [iwn] [lor] lock order reversal with iwn0_com_lock and iwn0 softc lock Date: Sat, 31 Oct 2009 19:24:59 -0400 (EDT) Indeed, I think I saw a lockup a couple days ago, possibly when my card had dissociated and was trying to reassociate. Thanks for looking into this, -Ben On Thu, 29 Oct 2009, Bernhard Schmidt wrote: > Hi, > > Removing the IWN_LOCK(sc) leads to races when calling iwn_cmd(). It's better > to drop the IEEE80211_LOCK(ic). I do have a patch in test which hopefully will > hit the tree soon. > > -- > Bernhard >