From owner-freebsd-net@FreeBSD.ORG Sun Jan 11 02:44: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 718BD106566B for ; Sun, 11 Jan 2009 02:44:53 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [220.233.188.227]) by mx1.freebsd.org (Postfix) with ESMTP id BD14C8FC17 for ; Sun, 11 Jan 2009 02:44:52 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id n0B2io7O041278; Sun, 11 Jan 2009 13:44:50 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sun, 11 Jan 2009 13:44:50 +1100 (EST) From: Ian Smith To: Skip Ford In-Reply-To: <20090110210250.GA894@menantico.com> Message-ID: <20090111132334.S21590@sola.nimnet.asn.au> References: <20090109083642.GA7507@rebelion.Sisis.de> <20090110105455.GA932@menantico.com> <20090110152531.GA32657@rebelion.Sisis.de> <20090110210250.GA894@menantico.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1795683103-1231641890=:21590" Cc: freebsd-net@freebsd.org, Matthias Apitz Subject: Re: FreeBSD 7.0R && ADSL 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, 11 Jan 2009 02:44:53 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1795683103-1231641890=:21590 Content-Type: TEXT/PLAIN; charset=unknown-8bit Content-Transfer-Encoding: 8BIT On Sat, 10 Jan 2009, Skip Ford wrote: > Matthias Apitz wrote: > > El día Saturday, January 10, 2009 a las 05:54:56AM -0500, Skip Ford escribió: > > > Matthias Apitz wrote: > > > > What kind of software I could use in FreeBSD? There is some port > > > > net/rp-pppoe but the man pages speaks about incoming connections? > > > > What else? > > > > > > Are you having problems using ppp(8)? PPPoE has been just another > > > dialup connection for years. Example configurations are available in > > > /usr/share/examples/ppp. > > > > > > If you really want a port, net/mpd is the way to go. ppp(8) is userland > > > while mpd is kernel. I wish it was in base. I was going to say that being in ports isn't too far away, but then realised that unless it's in base it can't be used for installation .. so +1 on that wish. > > Thanks for all the hints. The problem was that for many years I have > > only used 'normal' pppd connections (over modems, ISDN or UMTS), but > > never PPPoE. So I went to the ports and did search 'name=pppoe' and > > ended up in net/rp-pppoe and was confused. It seems that just ppp(8) is > > what I have to use. Thx again. > > Yeah, pppd(8) doesn't do PPPoE AFAIK. In addition to the examples I > already posted, there's a PPPoE section in the handbook which covers > everything instead of just ppp.conf: > > http://www.freebsd.org/doc/en/books/handbook/pppoe.html That section maybe could suggest mpd as an alternative, too. When I first was setting up for pppoe Bruce Simpson strongly urged me to try mpd instead, which was advice that I'm still appreciating. Last I heard, pppd(8) was getting close to being deprecated (not to suggest that ppp(8) using pppoe is in any similar state of neglect) cheers, Ian --0-1795683103-1231641890=:21590-- From owner-freebsd-net@FreeBSD.ORG Sun Jan 11 20:35: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 58765106566B for ; Sun, 11 Jan 2009 20:35:16 +0000 (UTC) (envelope-from jason.dicioccio@ods.org) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by mx1.freebsd.org (Postfix) with ESMTP id 12EC78FC19 for ; Sun, 11 Jan 2009 20:35:15 +0000 (UTC) (envelope-from jason.dicioccio@ods.org) Received: by yw-out-2324.google.com with SMTP id 9so4278631ywe.13 for ; Sun, 11 Jan 2009 12:35:15 -0800 (PST) Received: by 10.65.115.12 with SMTP id s12mr3865338qbm.111.1231706114421; Sun, 11 Jan 2009 12:35:14 -0800 (PST) Received: from ?192.168.5.50? (75-101-10-223.dsl.dynamic.sonic.net [75.101.10.223]) by mx.google.com with ESMTPS id s12sm5120095qbs.10.2009.01.11.12.35.12 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 11 Jan 2009 12:35:13 -0800 (PST) Sender: Jason DiCioccio Message-ID: <496A5800.5080506@ods.org> Date: Sun, 11 Jan 2009 12:35:12 -0800 From: Jason DiCioccio User-Agent: Thunderbird 2.0.0.19 (Windows/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: Still trying to debug mbuf leak.. Anyone familiar with uma_*? 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, 11 Jan 2009 20:35:16 -0000 So I've got various vmcores here from kmem_malloc failures.. I already know that it's an excess of mbufs that's causing the crash, I'm just trying to figure out what the mbufs contain so that I can try and figure out where they came from.. Currently I'm able to get at (uma_zone_t)zone_mbuf, but I'm unsure how to get to the actual mbuf data from there. I've tried looking the the uma_keg, etc. No luck so far. Is there anyone familiar with these data structures that could point me in the right direction? (kgdb) p *zone_mbuf $66 = {uz_name = 0xc076d6d1 "mbuf", uz_lock = 0xc1048108, uz_keg = 0xc1048100, uz_link = {le_next = 0xc1047180, le_prev = 0xc104812c}, uz_full_bucket = { lh_first = 0x0}, uz_free_bucket = {lh_first = 0x0}, uz_ctor = 0xc05068f0 , uz_dtor = 0xc0507040 , uz_init = 0, uz_fini = 0, uz_allocs = 137806761, uz_frees = 136018292, uz_fails = 136, uz_fills = 4, uz_count = 128, uz_cpu = {{ uc_freebucket = 0xc73a8c48, uc_allocbucket = 0x0, uc_allocs = 0, uc_frees = 0}}} Thanks! -JD- From owner-freebsd-net@FreeBSD.ORG Sun Jan 11 21:31:13 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 C61EA1065673 for ; Sun, 11 Jan 2009 21:31:13 +0000 (UTC) (envelope-from joost@jodocus.org) Received: from viefep19-int.chello.at (viefep19-int.chello.at [62.179.121.39]) by mx1.freebsd.org (Postfix) with ESMTP id 21BC98FC22 for ; Sun, 11 Jan 2009 21:31:12 +0000 (UTC) (envelope-from joost@jodocus.org) Received: from edge01.upc.biz ([192.168.13.236]) by viefep19-int.chello.at (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20090111211417.YUMP27723.viefep19-int.chello.at@edge01.upc.biz> for ; Sun, 11 Jan 2009 22:14:17 +0100 Received: from bps.jodocus.org ([77.248.200.61]) by edge01.upc.biz with edge id 2MEG1b00z1Kyz9101MEHfl; Sun, 11 Jan 2009 22:14:17 +0100 X-SourceIP: 77.248.200.61 Received: from jodocus.org (localhost [IPv6:::1]) by bps.jodocus.org (8.14.2/8.14.2) with ESMTP id n0BLEGfl053954 for ; Sun, 11 Jan 2009 22:14:16 +0100 (CET) (envelope-from joost@jodocus.org) Received: from 192.168.100.227 (SquirrelMail authenticated user joost) by jodocus.org with HTTP; Sun, 11 Jan 2009 22:14:16 +0100 (CET) Message-ID: <1694.192.168.100.227.1231708456.squirrel@jodocus.org> Date: Sun, 11 Jan 2009 22:14:16 +0100 (CET) From: "Joost Bekkers" To: freebsd-net@freebsd.org User-Agent: SquirrelMail/1.4.13 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (bps.jodocus.org [IPv6:::1]); Sun, 11 Jan 2009 22:14:16 +0100 (CET) X-Virus-Scanned: ClamAV 0.94.2/8852/Sun Jan 11 20:31:01 2009 on bps.jodocus.org X-Virus-Status: Clean Subject: pxeboot(8) after pxelinux 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, 11 Jan 2009 21:31:14 -0000 Hello I've been playing with chainloading pxeboot after pxelinux and its menu feature. It's working, but I had to do something weird. I'm wondering if anybody can come up with a logical explanation. (and feeding the search engines for people experiencing the same problem is a nice added bonus) After pxeboot starts it first does a dhcp request and proceeds to load /boot/loader.rc, which fails if pxelinux was part of the process. tftp requests leave the host, answers are send back, but are ignored by the client and the download times out. The loader then proceeds to try /boot/boot.conf, this succeeds (read: the client receives a ENOTFOUND and reacts accordingly. It does NOT time-out) The only significant event I could find between the two downloads was the closing and re-opening of the pxe socket (netif_close() and netif_open()) And indeed if I add netif_close() and netif_open() to the dhcp code in pxe_open() everything works. I checked the pxe documentation and didn't see anything about not being allowed to receive packets on different ports, the API looks to have been written to specificaly support it. I don't think pxeboot is at fault here, but I'd really like to know if there is a good explanation for this behaviour. Thanks, Joost Bekkers From owner-freebsd-net@FreeBSD.ORG Sun Jan 11 22:54: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 A7CBB106566C for ; Sun, 11 Jan 2009 22:54:22 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 848928FC0C for ; Sun, 11 Jan 2009 22:54:22 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 2A77746B06; Sun, 11 Jan 2009 17:54:22 -0500 (EST) Date: Sun, 11 Jan 2009 22:54:22 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Jason DiCioccio In-Reply-To: <496A5800.5080506@ods.org> Message-ID: References: <496A5800.5080506@ods.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: Still trying to debug mbuf leak.. Anyone familiar with uma_*? 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, 11 Jan 2009 22:54:22 -0000 On Sun, 11 Jan 2009, Jason DiCioccio wrote: > So I've got various vmcores here from kmem_malloc failures.. I already know > that it's an excess of mbufs that's causing the crash, I'm just trying to > figure out what the mbufs contain so that I can try and figure out where > they came from.. > > Currently I'm able to get at (uma_zone_t)zone_mbuf, but I'm unsure how to > get to the actual mbuf data from there. I've tried looking the the uma_keg, > etc. No luck so far. Is there anyone familiar with these data structures > that could point me in the right direction? It might require tweaking to work as things have changed a bit, but last time I was futzing with the mbuf allocator I put a UMA state dumper into src/tools/tools/umastat. It inspects /dev/kmem (or a core, I suppose) to print out the layout of cached data across per-cpu caches, etc. I'm not sure it would be all that useful for debugging a leak, but might prove informative for getting a sense of how it fits together, and the source code might be useful similarly. Robert N M Watson Computer Laboratory University of Cambridge > > (kgdb) p *zone_mbuf > $66 = {uz_name = 0xc076d6d1 "mbuf", uz_lock = 0xc1048108, uz_keg = > 0xc1048100, > uz_link = {le_next = 0xc1047180, le_prev = 0xc104812c}, uz_full_bucket = { > lh_first = 0x0}, uz_free_bucket = {lh_first = 0x0}, > uz_ctor = 0xc05068f0 , uz_dtor = 0xc0507040 , > uz_init = 0, uz_fini = 0, uz_allocs = 137806761, uz_frees = 136018292, > uz_fails = 136, uz_fills = 4, uz_count = 128, uz_cpu = {{ > uc_freebucket = 0xc73a8c48, uc_allocbucket = 0x0, uc_allocs = 0, > uc_frees = 0}}} > > Thanks! > -JD- > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Mon Jan 12 11:06:56 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 A11E810656D3 for ; Mon, 12 Jan 2009 11:06:56 +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 8A6458FC0C for ; Mon, 12 Jan 2009 11:06:56 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0CB6uKK092067 for ; Mon, 12 Jan 2009 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0CB6t8U092063 for freebsd-net@FreeBSD.org; Mon, 12 Jan 2009 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 12 Jan 2009 11:06:55 GMT Message-Id: <200901121106.n0CB6t8U092063@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, 12 Jan 2009 11:06:57 -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/130311 net [wlan_xauth] [panic] hostapd restart causing kernel pa o bin/130159 net [patch] ppp(8) fails to correctly set routes 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/129846 net [panic] /usr/sbin/ppp causes panic "Sleeping thread ow o kern/129793 net [ip6] [patch] Locking related leaks in the kernel (rou o kern/129750 net [ath] Atheros AR5006 exits on "cannot map register spa o kern/129719 net [tcp] [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 [panic] Kernel panic with EtherIP (may be related to S o kern/129352 net [xl] [patch] xl0 watchdog timeout o kern/129219 net [ppp] Kernel panic when using kernel mode ppp o kern/129135 net [vge] vge driver on a VIA mini-ITX not working 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 kern/128247 net [ip6] [panic] Fatal Trap 12 in ip6_forward = o conf/128030 net [request] Isn't it time to enable IPsec in GENERIC? 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: 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 f kern/126564 net [ath] doesn't work with my PCI-E X1 wireless network a o kern/126561 net [nlm] [patch] NLM (rpclockd) RPC UNLOCK failure (stall o kern/126475 net [ath] [panic] ath pcmcia card inevitably panics under o kern/126469 net [fxp] [panic] fxp(4) related kernel panic 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 [in] Network: 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 f kern/125195 net [fxp] fxp(4) driver failed to initialize device Intel o kern/124904 net [fxp] EEPROM corruption with Compaq NC3163 NIC 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/123881 net [tcp] Turning on TCP blackholing causes slow localhost 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 o 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/123200 net [netgraph] Server failure due to netgraph mpd and dhcp 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/123066 net [ipsec] [panic] kernel trap with ipsec 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 p kern/122794 net [lagg] Kernel panic after brings lagg(8) up if NICs ar 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 [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/122427 net [apm] [panic] apm and mDNSResponder cause panic during 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 f kern/122252 net [ipmi] [bge] IPMI problem with BCM5704 (does not work 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 kern/121983 net [fxp] fxp0 MBUF and PAE 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 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 [panic] gnugk causes kernel panic when closing UDP soc 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 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/119361 net [bge] bge(4) transmit performance problem o kern/119345 net [ath] Unsuported Atheros 5424/2424 and CPU speedstep n o kern/119225 net [wi] 7.0-RC1 no carrier with Prism 2.5 wifi card [regr o bin/118987 net ifconfig(8): ifconfig -l (address_family) does not wor o kern/118880 net [ip6] IP_RECVDSTADDR & IP_SENDSRCADDR not implemented 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 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/116328 net [bge]: Solid hang with bge interface o kern/116185 net [iwi] if_iwi driver leads system to reboot o kern/116077 net [ip] [patch] 6.2-STABLE panic during use of multi-cast o kern/115239 net [ipnat] panic with 'kmem_map too small' using ipnat o kern/114915 net [patch] [pcn] pcn (sys/pci/if_pcn.c) ethernet driver f o kern/114839 net [fxp] fxp looses ability to speak with traffic o kern/114714 net [gre][patch] gre(4) is not MPSAFE and does not support o kern/113842 net [ip6] PF_INET6 proto domain state can't be cleared wit o kern/112722 net [udp] IP v4 udp fragmented packet reject o kern/112686 net [patm] patm driver freezes System (FreeBSD 6.2-p4) i38 o bin/112557 net [patch] ppp(8) lock file should not use symlink name o kern/112528 net [nfs] NFS over TCP under load hangs with "impossible p o kern/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 bin/108895 net pppd(8): PPPoE dead connections on 6.2 [regression] o kern/108542 net [bce]: Huge network latencies with 6.2-RELEASE / STABL o kern/107944 net [wi] [patch] Forget to unlock mutex-locks o conf/107035 net [patch] bridge interface given in rc.conf not taking a 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 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 conf/102502 net [patch] ifconfig name does't rename netgraph node in n 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/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/96030 net [bfe] [patch] Install hangs with Broadcomm 440x NIC in 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 o kern/93378 net [tcp] Slow data transfer in Postfix and Cyrus IMAP (wo f kern/92552 net A serious bug in most network drivers from 5.X to 6.X o kern/92090 net [bge] bge0: watchdog timeout -- resetting 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/87521 net [ipf] [panic] using ipfilter "auth" keyword leads to k s kern/86920 net [ndis] ifconfig: SIOCS80211: Invalid argument [regress o kern/86103 net [ipf] Illegal NAT Traversal in IPFilter o kern/84202 net [ed] [patch] Holtek HT80232 PCI NIC recognition on Fre 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 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/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/70904 net [ipf] ipfilter ipnat problem with h323 proxy support o kern/64556 net [sis] if_sis short cable fix problems with NetGear FA3 s kern/60293 net FreeBSD arp poison patch o kern/54383 net [nfs] [patch] NFS root configurations without dynamic 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/27474 net [ipf] [ppp] Interactive use of user PPP and ipfilter c o conf/23063 net [patch] for static ARP tables in rc.network 205 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Jan 12 11:07:52 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 4995610656FC for ; Mon, 12 Jan 2009 11:07:52 +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 1A4158FC13 for ; Mon, 12 Jan 2009 11:07:52 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0CB7pF8093146 for ; Mon, 12 Jan 2009 11:07:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0CB7p4e093142 for net@FreeBSD.org; Mon, 12 Jan 2009 11:07:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 12 Jan 2009 11:07:51 GMT Message-Id: <200901121107.n0CB7p4e093142@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: net@FreeBSD.org Cc: Subject: Current problem reports assigned to 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, 12 Jan 2009 11:07:54 -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 -------------------------------------------------------------------------------- s kern/117717 net [panic] Kernel panic with Bittorrent client. 1 problem total. From owner-freebsd-net@FreeBSD.ORG Mon Jan 12 18:25: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 E14631065672; Mon, 12 Jan 2009 18:25:17 +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 BED568FC22; Mon, 12 Jan 2009 18:25:17 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id n0CIPF8A026583; Mon, 12 Jan 2009 10:25:16 -0800 (PST) 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: Mon, 12 Jan 2009 10:25:12 -0800 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: HEADSUP: arp-v2 has been committed Thread-Index: AclyPINDLzqKTA8HQUmWbWJoyRt36wCozjMA References: <20081227202117.F3B14341A3@cavin02.kulnet.kuleuven.ac.be><200812281613.49404.tijl@ulyssis.org> From: "Li, Qing" To: "Gerald Pfeifer" , Cc: Tijl Coosemans , freebsd-net@freebsd.org, freebsd-current@freebsd.org, Qing Li Subject: RE: HEADSUP: arp-v2 has been committed 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, 12 Jan 2009 18:25:18 -0000 I have revived the RTF_LLINFO definition in route.h. A new kernel option "COMPAT_ROUTE_FLAGS" is introduced, all for providing binary compatibility for existing ports. I could have made the RTF_LLINFO bit only applicable with _KERNEL. Without rehashing the discussion we all had on this topic on=20 both -current@ and -net@ MLs last month, moving forward, all=20 arp-v2 affected ports should continue to be modified and updated=20 with the understanding the RTF_LLINFO, RTF_WASCLONED etc. flags are=20 obsolete. There are no support for the semantics of these flag bits in the kernel, other than returning these bits to userland for the existing ports.=20 Please sync-up to the following revision: SVN rev 187094 on 2009-01-12 11:24:32Z by qingli Thanks, -- Qing > -----Original Message----- > From: Gerald Pfeifer [mailto:gerald@pfeifer.com] > Sent: Friday, January 09, 2009 1:27 AM > To: Li, Qing > Cc: Tijl Coosemans; Qing Li; freebsd-net@freebsd.org; freebsd- > current@freebsd.org > Subject: RE: HEADSUP: arp-v2 has been committed >=20 > On Tue, 30 Dec 2008, Li, Qing wrote: > > I don't think we can provide binary compatibility without putting > > back RTF_LLINFO exactly as it was. My preference is to continue down > > the new path without RTF_LLINFO. >=20 > So, you are saying that applications built on FreeBSD 7 or earlier > that use RTF_LLINFO will no longer work properly on FreeBSD 8 after > your change? >=20 > Ignoring everything else, that would be a killer and the one reason > to definitely change the current situation. Otherwise, ISVs will need > two builds, one for FreeBSD 7 and earlier and one for FreeBSD 8, and > believe me, that is bad, bad, bad. Or rather: unlikely. (GNU/Linux > distributions do provide this level of compatibility.) >=20 > > We still have some time before the 8.0 release. It's straightforward > > for me to retain some of the RTF_LLINFO support in the new kernel if > > and when the situation becomes necessary. >=20 > Sounds like that is the case? >=20 > > Since the affected ports now have the conditional code around > > RTF_LLINFO, the updates would allow these ports to compile in > > both -current and in the previous releases. >=20 > emulators/wine still is broken, and upstream Wine has not accepted > the patch yet. I believe one reason likely is the above, and the > fact that this may break commercial builds of Wine. >=20 > How are you going to address this? >=20 > Gerald > -- > Gerald (Jerry) Pfeifer gerald@pfeifer.com > http://www.pfeifer.com/gerald/ From owner-freebsd-net@FreeBSD.ORG Mon Jan 12 19:10: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 A560B10658D3 for ; Mon, 12 Jan 2009 19:10: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 936FB8FC22 for ; Mon, 12 Jan 2009 19:10:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0CJA2q2060336 for ; Mon, 12 Jan 2009 19:10:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0CJA2wT060335; Mon, 12 Jan 2009 19:10:02 GMT (envelope-from gnats) Date: Mon, 12 Jan 2009 19:10:02 GMT Message-Id: <200901121910.n0CJA2wT060335@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Axel Scheepers Cc: Subject: Re: kern/119432: [arp] route add -host <host> -iface <nic> causes arp entry with nic's arp address [regression] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Axel Scheepers List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 19:10:04 -0000 The following reply was made to PR kern/119432; it has been noted by GNATS. From: Axel Scheepers To: bug-followup@FreeBSD.org, axel@axel.truedestiny.net Cc: Subject: Re: kern/119432: [arp] route add -host <host> -iface <nic> causes arp entry with nic's arp address [regression] Date: Mon, 12 Jan 2009 19:47:23 +0100 Hi again, Back on FreeBSD(7.1-RELEASE-p1) for my home router ;) I can confirm using -net -netmask 255.255.255.255 -interface -cloning works ok; /etc/rc.conf: ifconfig_fxp0="inet x.x.x.x netmask 255.255.255.255 link0 polling" static_routes="sipspoof default" route_sipspoof="-net 192.168.0.1 -netmask 255.255.255.255 -interface x.x.x.x -cloning" route_default="default 192.168.0.1" taliesin# ping -c 2 69.147.83.33 PING 69.147.83.33 (69.147.83.33): 56 data bytes 64 bytes from 69.147.83.33: icmp_seq=0 ttl=48 time=173.483 ms 64 bytes from 69.147.83.33: icmp_seq=1 ttl=48 time=209.926 ms --- 69.147.83.33 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 173.483/191.704/209.926/18.222 ms Setting defaultrouter will not work since that gets set before the static routes are setup hence the need for the default static route. Kind regards, Axel Scheepers From owner-freebsd-net@FreeBSD.ORG Mon Jan 12 20:37:01 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 1D9501065670 for ; Mon, 12 Jan 2009 20:37:01 +0000 (UTC) (envelope-from jchambers@ucla.edu) Received: from out-21.smtp.ucla.edu (out-21.smtp.ucla.edu [169.232.47.166]) by mx1.freebsd.org (Postfix) with ESMTP id 1E2688FC1E for ; Mon, 12 Jan 2009 20:37:00 +0000 (UTC) (envelope-from jchambers@ucla.edu) Received: from mail.ucla.edu (mail.ucla.edu [169.232.48.151]) by smtp-4.smtp.ucla.edu (8.14.3/8.14.3) with ESMTP id n0CKQ618008815 for ; Mon, 12 Jan 2009 12:26:06 -0800 Received: from computer.local ([149.142.36.207]) (authenticated bits=0) by mail.ucla.edu (8.13.8/8.13.8) with ESMTP id n0CKQ6H4008054 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 12 Jan 2009 12:26:06 -0800 Message-ID: <496BA75E.7020309@ucla.edu> Date: Mon, 12 Jan 2009 12:26:06 -0800 From: Jason Chambers Organization: UCLA User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: freebsd-net@freebsd.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Probable-Spam: no X-Scanned-By: smtp.ucla.edu on 169.232.47.244 Subject: Network is unreachable and other related errors 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, 12 Jan 2009 20:37:03 -0000 Hello all, Wondering if anyone else experiences errors such as "Network is unreachable" and the like when using security auditing tools like nmap, nessus, etc. I found a PR from a long time ago that appears relevant but it was abandoned: http://www.freebsd.org/cgi/query-pr.cgi?pr=102741&cat= As a result of this condition some tools are completely unusable. A nessus scan returns all scanned hosts as dead seconds after starting a scan. Nmap is unable to scan a system because it immediately goes into a loop of the following: sendto in send_ip_packet: sendto(4, packet, 44, 0, xxx.xxx.xxx.xxx, 16) => Network is unreachable Offending packet: TCP xxx.xxx.xxx.xxx:55555 > xxx.xxx.xxx.xxx:80 S ttl=56 id=xxxx iplen=11264 seq=xxxx win=1024 Sleeping 15 seconds then retrying sendto in send_ip_packet: sendto(4, packet, 44, 0, xxx.xxx.xxx.xxx, 16) => Network is unreachable Offending packet: TCP xxx.xxx.xxx.xxx:55555 > xxx.xxx.xxx.xxx:80 S ttl=56 id=xxxx iplen=11264 seq=xxxx win=1024 Sleeping 60 seconds then retrying It's obviously related in part to the hardware configuration of a device however I'm not sure where to look next. The network controller does not seem to make a difference. So far I've not experienced anything related to this issue when running Linux on the same hardware. Any ideas where to look next ? Regards, --Jason From owner-freebsd-net@FreeBSD.ORG Mon Jan 12 20:37: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 10593106575A for ; Mon, 12 Jan 2009 20:37:27 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-bw0-f20.google.com (mail-bw0-f20.google.com [209.85.218.20]) by mx1.freebsd.org (Postfix) with ESMTP id 6B4358FC17 for ; Mon, 12 Jan 2009 20:37:25 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by bwz13 with SMTP id 13so7042554bwz.19 for ; Mon, 12 Jan 2009 12:37:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=GxzsgMQ0S2QSnuOA7AnBgSORGeA4Kla5lH1HkK+id/k=; b=YZ7Uuk7jPfFrtL7pDkOSBUr86sQNpkMFSfCFE9CWM4GJ+RHXQVPE0ojQQMaPOYxzFT WnkMANF9EE+dsfEeDCpUlfMK3VzWnNJph5o9oPpRfzEKEaGHq9ECa+ve0+uS+IIt6sXm y+Ds0FDJFVs4FTnfPVdJju8Gj/JpCfSk4P8YE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=hr6W/v6dMlO0uwBqd5Et7yaEXCAfSluDJld2P4XhbMVH4fds4r6KLlwAyT6BFyU7p1 AMLRkKJP77SrU20Mm1sXHF+JwsSkjIOEjnsDyTTwyd+dZuniRpyQeUzN+H2XT5b4da/K MqHIu9UVFoLZ4J4hjQeg0+rWzXrX+9/NlEy3w= Received: by 10.181.60.14 with SMTP id n14mr11090557bkk.79.1231791142027; Mon, 12 Jan 2009 12:12:22 -0800 (PST) Received: by 10.181.26.3 with HTTP; Mon, 12 Jan 2009 12:12:21 -0800 (PST) Message-ID: <7d6fde3d0901121212i3acf282dj6bc3b7d59a044e5e@mail.gmail.com> Date: Mon, 12 Jan 2009 12:12:21 -0800 From: "Garrett Cooper" To: "Li, Qing" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081227202117.F3B14341A3@cavin02.kulnet.kuleuven.ac.be> <200812281613.49404.tijl@ulyssis.org> Cc: Gerald Pfeifer , freebsd-net@freebsd.org, Qing Li , freebsd-current@freebsd.org, Tijl Coosemans , erwin@freebsd.org Subject: Re: HEADSUP: arp-v2 has been committed 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, 12 Jan 2009 20:37:30 -0000 On Mon, Jan 12, 2009 at 10:25 AM, Li, Qing wrote: > I have revived the RTF_LLINFO definition in route.h. > A new kernel option "COMPAT_ROUTE_FLAGS" is introduced, all > for providing binary compatibility for existing ports. > I could have made the RTF_LLINFO bit only applicable with _KERNEL. > > Without rehashing the discussion we all had on this topic on > both -current@ and -net@ MLs last month, moving forward, all > arp-v2 affected ports should continue to be modified and updated > with the understanding the RTF_LLINFO, RTF_WASCLONED etc. flags are > obsolete. There are no support for the semantics of these > flag bits in the kernel, other than returning these bits to > userland for the existing ports. > > Please sync-up to the following revision: > > SVN rev 187094 on 2009-01-12 11:24:32Z by qingli > > Thanks, > > -- Qing > > >> -----Original Message----- >> From: Gerald Pfeifer [mailto:gerald@pfeifer.com] >> Sent: Friday, January 09, 2009 1:27 AM >> To: Li, Qing >> Cc: Tijl Coosemans; Qing Li; freebsd-net@freebsd.org; freebsd- >> current@freebsd.org >> Subject: RE: HEADSUP: arp-v2 has been committed >> >> On Tue, 30 Dec 2008, Li, Qing wrote: >> > I don't think we can provide binary compatibility without putting >> > back RTF_LLINFO exactly as it was. My preference is to continue down >> > the new path without RTF_LLINFO. >> >> So, you are saying that applications built on FreeBSD 7 or earlier >> that use RTF_LLINFO will no longer work properly on FreeBSD 8 after >> your change? >> >> Ignoring everything else, that would be a killer and the one reason >> to definitely change the current situation. Otherwise, ISVs will need >> two builds, one for FreeBSD 7 and earlier and one for FreeBSD 8, and >> believe me, that is bad, bad, bad. Or rather: unlikely. (GNU/Linux >> distributions do provide this level of compatibility.) >> >> > We still have some time before the 8.0 release. It's straightforward >> > for me to retain some of the RTF_LLINFO support in the new kernel if >> > and when the situation becomes necessary. >> >> Sounds like that is the case? >> >> > Since the affected ports now have the conditional code around >> > RTF_LLINFO, the updates would allow these ports to compile in >> > both -current and in the previous releases. >> >> emulators/wine still is broken, and upstream Wine has not accepted >> the patch yet. I believe one reason likely is the above, and the >> fact that this may break commercial builds of Wine. >> >> How are you going to address this? >> >> Gerald Oh, btw... wine works well when you set the RTF_LLINFO value to 0 with arp-v2, AFAICT. -Garrett From owner-freebsd-net@FreeBSD.ORG Mon Jan 12 20:47:56 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 5309A106564A; Mon, 12 Jan 2009 20:47:56 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-bw0-f20.google.com (mail-bw0-f20.google.com [209.85.218.20]) by mx1.freebsd.org (Postfix) with ESMTP id 426118FC0A; Mon, 12 Jan 2009 20:47:55 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by bwz13 with SMTP id 13so7061116bwz.19 for ; Mon, 12 Jan 2009 12:47:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=5IDgRy9IcANQeXKOMWOApeSBvkhx7cPZi7tevbg5PSQ=; b=Er0t7BvKx4vz8Flw5bFVecss1UEDjSkSo7ZxJQoX2TAfCSNn61KSBWSvYzmq8FSgvP AkQw5i9lPm3O6AGIHjonoZ9ca6DuHB1cCtoQx1fS7w3ZyneL/DV/UEXf6MAjdmU6ONbR HgJXKKtqwU1e7kiKXUuQ8mBe6pDgqkPcN9Plk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=oMKt2HS0Q1OvnruEPJOmn3LzHSOqTT3Bw+0KuX4dpm33OQ1HF1Y/vDbccYEsVjsfp6 JOH+TF7UTEuGhFzX+7Y18hD5aF5oAHjtsXBgSolUakviJR72vLaxP9G7rTRMl5ORvdKI EF7DTBmkA3GhHMb23rB9argp1MuyWN7Bjp2JU= Received: by 10.181.201.18 with SMTP id d18mr10141900bkq.72.1231793274163; Mon, 12 Jan 2009 12:47:54 -0800 (PST) Received: by 10.181.26.3 with HTTP; Mon, 12 Jan 2009 12:47:54 -0800 (PST) Message-ID: <7d6fde3d0901121247t31ee0d8cp6d46cf9b3b256fad@mail.gmail.com> Date: Mon, 12 Jan 2009 12:47:54 -0800 From: "Garrett Cooper" To: "Julian Elischer" In-Reply-To: <496BAA26.9010200@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081227202117.F3B14341A3@cavin02.kulnet.kuleuven.ac.be> <200812281613.49404.tijl@ulyssis.org> <7d6fde3d0901121212i3acf282dj6bc3b7d59a044e5e@mail.gmail.com> <496BAA26.9010200@elischer.org> Cc: "Li, Qing" , Gerald Pfeifer , freebsd-net@freebsd.org, Qing Li , freebsd-current@freebsd.org, Tijl Coosemans Subject: Re: HEADSUP: arp-v2 has been committed 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, 12 Jan 2009 20:47:56 -0000 On Mon, Jan 12, 2009 at 12:37 PM, Julian Elischer wrote: > Garrett Cooper wrote: > > I think setting it to a value of 0 has two good points... > > In code that does: > if (XXX & RTF_LLINFO) { > yyy() > } > the optimiser should simply remove the code, > or at worst give an error messages that makes people go look for > the answer, and secondly, > the conditional > > #if defined(RTF_LLINFO) && (RTF_LLINFO != 0) > > can be easily used to make code conditionally do the right thing > for different versions of freeBSD, > possibly trivially replacing earlier occurances of > > #ifdef RTF_LLINFO > > > >> >> Oh, btw... wine works well when you set the RTF_LLINFO value to 0 >> with arp-v2, AFAICT. >> -Garrett That's basically what I did (2 instances in the file had to be replaced) -- #ifndef RTF_LLINFO /* Insert code here with 0. */ #else /* Insert code here with RTF_LLINFO. */ #endif The code checks to see if sysctl exists, and then defaults to Linux-y behavior, so other OS'es with proper sysctl support could be broken by this change. I tested this out with Steam and wine-doors, but unfortunately I ran into OpenGL issues that prevented me from playing Steam games -_-... Cheers, -Garrett From owner-freebsd-net@FreeBSD.ORG Mon Jan 12 21:06: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 91B311065673; Mon, 12 Jan 2009 21:06:32 +0000 (UTC) (envelope-from prvs=julian=2560a13b2@elischer.org) Received: from smtp-outbound.ironport.com (smtp-outbound.ironport.com [63.251.108.112]) by mx1.freebsd.org (Postfix) with ESMTP id 725708FC12; Mon, 12 Jan 2009 21:06:32 +0000 (UTC) (envelope-from prvs=julian=2560a13b2@elischer.org) Received: from unknown (HELO julian-mac.elischer.org) ([10.251.60.87]) by smtp-outbound.ironport.com with ESMTP; 12 Jan 2009 12:38:00 -0800 Message-ID: <496BAA26.9010200@elischer.org> Date: Mon, 12 Jan 2009 12:37:58 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: Garrett Cooper References: <20081227202117.F3B14341A3@cavin02.kulnet.kuleuven.ac.be> <200812281613.49404.tijl@ulyssis.org> <7d6fde3d0901121212i3acf282dj6bc3b7d59a044e5e@mail.gmail.com> In-Reply-To: <7d6fde3d0901121212i3acf282dj6bc3b7d59a044e5e@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Li, Qing" , Gerald Pfeifer , freebsd-net@freebsd.org, Qing Li , freebsd-current@freebsd.org, Tijl Coosemans Subject: Re: HEADSUP: arp-v2 has been committed 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, 12 Jan 2009 21:06:33 -0000 Garrett Cooper wrote: I think setting it to a value of 0 has two good points... In code that does: if (XXX & RTF_LLINFO) { yyy() } the optimiser should simply remove the code, or at worst give an error messages that makes people go look for the answer, and secondly, the conditional #if defined(RTF_LLINFO) && (RTF_LLINFO != 0) can be easily used to make code conditionally do the right thing for different versions of freeBSD, possibly trivially replacing earlier occurances of #ifdef RTF_LLINFO > > Oh, btw... wine works well when you set the RTF_LLINFO value to 0 > with arp-v2, AFAICT. > -Garrett > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Tue Jan 13 00:02:14 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 085FA106564A for ; Tue, 13 Jan 2009 00:02:14 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from arcturus.maxiscale.com (arcturus.maxiscale.com [76.231.178.136]) by mx1.freebsd.org (Postfix) with ESMTP id BE3E88FC0C for ; Tue, 13 Jan 2009 00:02:13 +0000 (UTC) (envelope-from psteele@maxiscale.com) X-ASG-Debug-ID: 1231804932-048400000000-QdxwpM X-Barracuda-URL: http://10.100.1.25:8000/cgi-bin/mark.cgi Received: from polaris.maxiscale.com (localhost [127.0.0.1]) by arcturus.maxiscale.com (Spam Firewall) with ESMTP id 849493720D for ; Mon, 12 Jan 2009 16:02:12 -0800 (PST) Received: from polaris.maxiscale.com (polaris.maxiscale.com [10.100.1.24]) by arcturus.maxiscale.com with ESMTP id k2XOQWnMU2KJh5CM for ; Mon, 12 Jan 2009 16:02:12 -0800 (PST) X-ASG-Whitelist: Client X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 X-ASG-Orig-Subj: Broadcast packet not being sent Date: Mon, 12 Jan 2009 16:02:11 -0800 Message-ID: <2ACA3DE8F9758A48B8BE2C7A847F91F247A128@polaris.maxiscale.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Broadcast packet not being sent Thread-Index: Acl1Ei8tNQutfMoUTYKAVTX8jVjsIA== From: "Peter Steele" To: X-Barracuda-Connect: polaris.maxiscale.com[10.100.1.24] X-Barracuda-Start-Time: 1231804932 X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at maxiscale.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Broadcast packet not being sent 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, 13 Jan 2009 00:02:14 -0000 I am using scapy to construct a UDP broadcast packet. The code I'm using is: =20 packet=3DEther(dst=3D"ff:ff:ff:ff:ff:ff")/IP(dst=3D"255.255.255.255")/UDP= (dpor t=3D33333)/payload sendp(packet) Send 1 packets. =20 This works fine when I have an IP assigned to the box. However, when no IP is assigned, I get the following messages: The sendp generates these warnings: =20 WARNING: No route found for IPv6 destination :: (no default route?) WARNING: No route found (no default route?) WARNING: No route found (no default route?) WARNING: No route found (no default route?) =20 Sent 1 packets. =20 I assume these warnings are okay, since of course there can't be a route in a scenario like the one I'm using. It's the same environment a DHCP client would face. However, despite scapy saying the packet was sent, it does not in fact leave the machine (I've confirmed this with tcpdump). As I said, if the box has an IP address, then the packet is sent as expected, but that defeats the purpose since we are developing a custom DHCP-like protocol. =20 The only think suspicious that I am seeing is this error in /var/log/messages: =20 Jan 12 16:13:52 kernel: looutput: af=3D31 unexpected =20 I get one of these each time I try to send a broadcast when no IP is assigned. I did an google search but did not any useful hits on this. If anyone here has any idea what's going on, I'd appreciate some feedback. I think I have the correct packet constructed, but clearly something is wrong, and it may very well be user error. =20 Peter =20 From owner-freebsd-net@FreeBSD.ORG Tue Jan 13 01:11:15 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 6798310656C0 for ; Tue, 13 Jan 2009 01:11:15 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from arcturus.maxiscale.com (arcturus.maxiscale.com [76.231.178.136]) by mx1.freebsd.org (Postfix) with ESMTP id 435E18FC25 for ; Tue, 13 Jan 2009 01:11:14 +0000 (UTC) (envelope-from psteele@maxiscale.com) X-ASG-Debug-ID: 1231809054-2da900020000-QdxwpM X-Barracuda-URL: http://10.100.1.25:8000/cgi-bin/mark.cgi Received: from polaris.maxiscale.com (localhost [127.0.0.1]) by arcturus.maxiscale.com (Spam Firewall) with ESMTP id EA56A37209 for ; Mon, 12 Jan 2009 17:10:54 -0800 (PST) Received: from polaris.maxiscale.com (polaris.maxiscale.com [10.100.1.24]) by arcturus.maxiscale.com with ESMTP id TRrfnAANFECdQ4tA for ; Mon, 12 Jan 2009 17:10:54 -0800 (PST) X-ASG-Whitelist: Client 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 X-ASG-Orig-Subj: RE: Broadcast packet not being sent Date: Mon, 12 Jan 2009 17:10:51 -0800 Message-ID: <2ACA3DE8F9758A48B8BE2C7A847F91F247A13A@polaris.maxiscale.com> In-Reply-To: <2ACA3DE8F9758A48B8BE2C7A847F91F247A128@polaris.maxiscale.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Broadcast packet not being sent Thread-Index: Acl1Ei8tNQutfMoUTYKAVTX8jVjsIAACYJKQ References: <2ACA3DE8F9758A48B8BE2C7A847F91F247A128@polaris.maxiscale.com> From: "Peter Steele" To: "Peter Steele" , X-Barracuda-Connect: polaris.maxiscale.com[10.100.1.24] X-Barracuda-Start-Time: 1231809057 X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at maxiscale.com Cc: Subject: RE: Broadcast packet not being sent 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, 13 Jan 2009 01:11:16 -0000 Problem solved. I have to explicitly set cond.iface before sending the packet. User error... -----Original Message----- From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org] On Behalf Of Peter Steele Sent: Monday, January 12, 2009 4:02 PM To: freebsd-net@freebsd.org Subject: Broadcast packet not being sent I am using scapy to construct a UDP broadcast packet. The code I'm using is: =20 packet=3DEther(dst=3D"ff:ff:ff:ff:ff:ff")/IP(dst=3D"255.255.255.255")/UDP= (dpor t=3D33333)/payload sendp(packet) Send 1 packets. =20 This works fine when I have an IP assigned to the box. However, when no IP is assigned, I get the following messages: The sendp generates these warnings: =20 WARNING: No route found for IPv6 destination :: (no default route?) WARNING: No route found (no default route?) WARNING: No route found (no default route?) WARNING: No route found (no default route?) =20 Sent 1 packets. =20 I assume these warnings are okay, since of course there can't be a route in a scenario like the one I'm using. It's the same environment a DHCP client would face. However, despite scapy saying the packet was sent, it does not in fact leave the machine (I've confirmed this with tcpdump). As I said, if the box has an IP address, then the packet is sent as expected, but that defeats the purpose since we are developing a custom DHCP-like protocol. =20 The only think suspicious that I am seeing is this error in /var/log/messages: =20 Jan 12 16:13:52 kernel: looutput: af=3D31 unexpected =20 I get one of these each time I try to send a broadcast when no IP is assigned. I did an google search but did not any useful hits on this. If anyone here has any idea what's going on, I'd appreciate some feedback. I think I have the correct packet constructed, but clearly something is wrong, and it may very well be user error. =20 Peter =20 _______________________________________________ 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 Jan 13 05:44:01 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 8425B106564A for ; Tue, 13 Jan 2009 05:44:01 +0000 (UTC) (envelope-from dimitar.vassilev@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.30]) by mx1.freebsd.org (Postfix) with ESMTP id 389C38FC16 for ; Tue, 13 Jan 2009 05:44:00 +0000 (UTC) (envelope-from dimitar.vassilev@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so4549377yxb.13 for ; Mon, 12 Jan 2009 21:44:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=+CDScej2acmPUkv5rDsGGjbVc3lDobyoHzkerSeQYfc=; b=u76uNJPIr6ajvE1Kl19L13kLdADlY94AzaLJ+UoP+Mju22oJeEOaRTv0UZoFfrFPVm H6h6IM4aMyCNvo7Zsw550/G0+3yB0M1mLvN3nJLX8BjL/lUCGaWygD+Upy7yYKNYfujN /OMUy2BMIn2nuTneHIhvETT1cZly9+xsuImCE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=yIQzieLylB5EglckIHDEcyY2QVTmZ8lOqKUG5G3tlkV6MqHqwyOJqZsuktrl809r0+ EYh9krHIU2Y6xtng7hSRCD3bVC5yVklFLG4AtA21i/1iyYiY9HKgpvcpAYKaa9zje+HE Vbrb4zPXZPHgF/eiz+67f/9BtkeyHl6kT6FOg= Received: by 10.150.228.2 with SMTP id a2mr3473621ybh.201.1231823640429; Mon, 12 Jan 2009 21:14:00 -0800 (PST) Received: by 10.151.133.7 with HTTP; Mon, 12 Jan 2009 21:14:00 -0800 (PST) Message-ID: <59adc1a0901122114v15efa47ahba8beef6ace4ddb0@mail.gmail.com> Date: Tue, 13 Jan 2009 07:14:00 +0200 From: "Dimitar Vasilev" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: setfib+pf 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, 13 Jan 2009 05:44:01 -0000 Hi, I originally posted my message to questions, however no response for about a week. Therefore I'm reposting here. Original question available at http://lists.freebsd.org/pipermail/freebsd-questions/2009-January/190056.html For those who prefer reading human text, here are my questions: I'd like to ask on the best options for using setfib and pf in a non-BGP environment. I will run 2 uplinks, with VLANs for internal networks and want to fail over external links if one of them fails.(Extended note as of 13.01: Uplink routers will be a WRT54GL with OpenWRT and an Alix box hopefully. Vlan tagging also possible there. Alix will be the controlling router station for failover). Currently pf supports to the best of my knowledge: a) rtable - this means i can create the routing tables with setfib and then use pass from .... rtable N( N >1 <16) or give out directly network ranges b) route-to - pass in/out on X from ... route-to c) packet tagging - i can tag networks and use standalone or through routing tags. Anyone aware if is it ok to use /etc/gateways without running routed or how can i label routes alternatively? If I apply the same for /etc/networks or both /etc/gateways and networks will it be ok? pass in from any to $big_salad via $fridge keep state for example? d) pass in from route N(192.168.1.1 for example) to... - saw this on http://www.mail-archive.com/pf@benzedrine.cx/msg07220.html and requires BGP to make tags speak anything but network numbers. e) use the vlan id's I'd much appreciate if someone thinks with me for the best options of using the setfib features along with pf. Thanks and regards, Dimitar Vassilev From owner-freebsd-net@FreeBSD.ORG Tue Jan 13 10:49: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 0C17E1065672 for ; Tue, 13 Jan 2009 10:49:24 +0000 (UTC) (envelope-from freebsd-net@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 871A38FC0C for ; Tue, 13 Jan 2009 10:49:23 +0000 (UTC) (envelope-from freebsd-net@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LMgpk-0005Z4-3S for freebsd-net@freebsd.org; Tue, 13 Jan 2009 10:49:20 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 Jan 2009 10:49:20 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 Jan 2009 10:49:20 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-net@freebsd.org From: Ivan Voras Date: Tue, 13 Jan 2009 11:49:01 +0100 Lines: 44 Message-ID: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigBD4346EF0EB31B6302AAC76C" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.19 (X11/20090105) X-Enigmail-Version: 0.95.0 Sender: news Subject: IPv6, ssh and ipfw 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, 13 Jan 2009 10:49:24 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigBD4346EF0EB31B6302AAC76C Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, I'm experimenting with IPv6 and so far all is well except one thing: my ssh sessions are dropped/stalled after a few minutes. I'm using ipfw and by monitoring its dynamic/state-keeping rules I see that it's timeouting the rules after 60 seconds (this time is configured in net.inet.ip.fw.dyn_ack_lifetime). The problem is, this is not happening with IPv4 ssh sessions. I see the timeout is counting down for my dynamic/stateful IPv4 ssh session but it's reset before it reaches 0, which is consistent with observed behaviour - on Windows, I can start putty, hybernate or sleep the OS (i.e. the machine practically turns off) and wake it up another day to see the ssh session still alive. Aside from obvious DOS opportunities on the server, I like this behaviour. This is *not* apparently created by using keepalive messages since they are obviously not sent while the machine is sleeping (and they are disabled in sshd_conf). Why is ssh over IPv6 behaving differently than on IPv4? Is there a special hack for ssh on IPv4? This is on 6-STABLE. --------------enigBD4346EF0EB31B6302AAC76C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJbHGdldnAQVacBcgRApp6AKCOz98vu8wXaDwibQOGDito3xaMMQCeMYF7 jDH9O8oUeLnwHdnYGVYYfCQ= =ptUV -----END PGP SIGNATURE----- --------------enigBD4346EF0EB31B6302AAC76C-- From owner-freebsd-net@FreeBSD.ORG Tue Jan 13 11:03: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 EB0CF106567C; Tue, 13 Jan 2009 11:03:42 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.freebsd.org (Postfix) with ESMTP id 48D2F8FC14; Tue, 13 Jan 2009 11:03:41 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: by ug-out-1314.google.com with SMTP id 30so233248ugs.39 for ; Tue, 13 Jan 2009 03:03:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:subject:date :message-id:mime-version:content-type:x-mailer:thread-index :x-mimeole; bh=slyDW/xUnTsJKGKiYNFlQ3hh2pMuMxXfH7A23qrkE1A=; b=ssiQAWBxmSkLTwePBONVZkVqcRQ4QdM6caB0IifN+Xyrp+sXbWHA9NtBnGsdiAhJBE l6a/opy93V8sE4XDBHhnLoEgT5OaTWaAp1GWZC5oca/+ho4N1r7BI40sALUglKHPLKR5 CM8CMxeaUKhFMUhk8auZlHLCr7lfTe3dWlGeU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:x-mimeole; b=RrVtrHBUwCcbon1Q8xmmD/3iztlINzUCW4JrHIwOUHlaOMDEIOZGuTgHo2uqI7dW7q q7DH3LznQZku1VF+OJuaBaAHkuz1LNniGC12yq3odiJJ0GdUZxSa4UQfp0v2+qUK0KRC aBUEgFe5aepVR1GMv8w8AxDd2pNEACSAi8vLg= Received: by 10.67.100.10 with SMTP id c10mr1887083ugm.2.1231844613261; Tue, 13 Jan 2009 03:03:33 -0800 (PST) Received: from mtllpt03 (bzq-79-180-238-90.red.bezeqint.net [79.180.238.90]) by mx.google.com with ESMTPS id 39sm874112ugb.43.2009.01.13.03.01.40 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 13 Jan 2009 03:03:32 -0800 (PST) From: "Yony Yossef" To: , Date: Tue, 13 Jan 2009 13:01:43 +0200 Message-ID: <000501c9756e$9563d550$39ed1aac@mtl.com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acl1beAG6FuxsdXgT3+8lg6M7YA9JQAABcXg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Eitan Shefi , Oleg Kats , Liran Liss Subject: Using device.hints to determine network device unit number 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, 13 Jan 2009 11:03:44 -0000 Hi, I would like to determine the unit number of my network cards, make the device on pci0:16 appear always as mtnic0 and pci0:9 appear always as mtnic1. # pciconf -l | grep mtnic mtnic0@pci0:19:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 rev=0xa0 hdr=0x00 mtnic1@pci0:16:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 rev=0xa0 hdr=0x00 Is it done by /boot/device.hints? if so, how? I've tried: hint.mtnic.0.at="pci0:16" hint.mtnic.1.at="pci0:19" but it doesn't work. They keep switching upon reboot. I'm using FreeBSD 7.0. Thanks Yony From owner-freebsd-net@FreeBSD.ORG Tue Jan 13 11:25:19 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 5C16F106564A for ; Tue, 13 Jan 2009 11:25:19 +0000 (UTC) (envelope-from yoniy@mellanox.co.il) Received: from mellanox.co.il (mail.mellanox.co.il [194.90.237.43]) by mx1.freebsd.org (Postfix) with ESMTP id 8E9D48FC0A for ; Tue, 13 Jan 2009 11:25:17 +0000 (UTC) (envelope-from yoniy@mellanox.co.il) Received: from Internal Mail-Server by MTLPINE1 (envelope-from yoniy@mellanox.co.il) with SMTP; 13 Jan 2009 12:58:34 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Tue, 13 Jan 2009 12:58:32 +0200 Message-ID: <5D49E7A8952DC44FB38C38FA0D758EAD01736127@mtlexch01.mtl.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Using device.hints to determine network device unit number Thread-Index: Acl1beAG6FuxsdXgT3+8lg6M7YA9JQ== From: "Yehonatan Yossef" To: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Eitan Shefi , Oleg Kats , Liran Liss Subject: Using device.hints to determine network device unit number 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, 13 Jan 2009 11:25:19 -0000 Hi,=20 =20 I would like to determine the unit number of my network cards, make the device on pci0:16 appear always as mtnic0 and pci0:9 appear always as mtnic1. =20 # pciconf -l | grep mtnic mtnic0@pci0:19:0:0: class=3D0x020000 card=3D0x001715b3 = chip=3D0x636815b3 rev=3D0xa0 hdr=3D0x00 mtnic1@pci0:16:0:0: class=3D0x020000 card=3D0x001715b3 = chip=3D0x636815b3 rev=3D0xa0 hdr=3D0x00 =20 Is it done by /boot/device.hints? if so, how? I've tried: =20 hint.mtnic.0.at=3D"pci0:16" hint.mtnic.1.at=3D"pci0:19" =20 but it doesn't work. They keep switching upon reboot. I'm using FreeBSD 7.0. =20 Thanks Yony =20 From owner-freebsd-net@FreeBSD.ORG Tue Jan 13 12: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 8C70C106564A for ; Tue, 13 Jan 2009 12: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 7A4EE8FC1D for ; Tue, 13 Jan 2009 12:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0DCe35e004789 for ; Tue, 13 Jan 2009 12: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 n0DCe340004788; Tue, 13 Jan 2009 12:40:03 GMT (envelope-from gnats) Date: Tue, 13 Jan 2009 12:40:03 GMT Message-Id: <200901131240.n0DCe340004788@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Boris MARECHAL Cc: Subject: Re: kern/123066: [ipsec] [panic] kernel trap with ipsec X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Boris MARECHAL List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 12:40:03 -0000 The following reply was made to PR kern/123066; it has been noted by GNATS. From: Boris MARECHAL To: bug-followup@FreeBSD.org, msaf1980@rambler.ru Cc: Subject: Re: kern/123066: [ipsec] [panic] kernel trap with ipsec Date: Tue, 13 Jan 2009 13:38:22 +0100 --Apple-Mail-59-140032122 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit seems linked with kern/124609: [ipsec] [panic] ipsec 'remainder too big' panic with ping -s 3989 --Apple-Mail-59-140032122 Content-Disposition: attachment; filename=smime.p7s Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFczCCBW8w ggRXoAMCAQICCnDGsUgWa/KQamQwDQYJKoZIhvcNAQEEBQAwgZExCzAJBgNVBAYTAkZSMQ0wCwYD VQQIEwROb3JkMRowGAYDVQQHExFWaWxsZW5ldXZlIGQnQXNjcTEuMCwGA1UEChMlTkVUQVNRIC0g U2VjdXJlIEludGVybmV0IENvbm5lY3Rpdml0eTEnMCUGA1UECxMeTkVUQVNRIENlcnRpZmljYXRp b24gQXV0aG9yaXR5MB4XDTA4MDEwMzExMTIzNFoXDTEwMDEwMjExMTIzNFowgdQxCzAJBgNVBAYU AkZSMQ0wCwYDVQQIFAROb3JkMS4wLAYDVQQKFCVORVRBU1EgLSBTZWN1cmUgSW50ZXJuZXQgQ29u bmVjdGl2aXR5MScwJQYDVQQLFB5ORVRBU1EgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxGjAYBgNV BAcUEVZpbGxlbmV1dmUgZCdBc2NxMRcwFQYDVQQDFA5Cb3JpcyBNQVJFQ0hBTDEoMCYGCSqGSIb3 DQEJARYZYm9yaXMubWFyZWNoYWxAbmV0YXNxLmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkC gYEA5GEoHCGB2ZhZx/I7Jq0hetpb+HPf2DKzieLoklK125o3RaSdHELZYnWB2Cvi6xRG5p+wmOl2 ABo0qwxkve2QfdapHXppQo2aNVp++Z528p22ASaQzJnzBT9JTPVxMFopgMbMBgCmMrye6lpI3laW HEoCcIrfD4Vfus4i62JCwvMCAwEAAaOCAgYwggICMAwGA1UdEwEB/wQCMAAwHQYDVR0OBBYEFDIY DOPzGbqvpVtqkCbFSKhMMB2wMIG+BgNVHSMEgbYwgbOAFCcq6x3ZRNo6F3NqCSAgySWo+X+yoYGX pIGUMIGRMQswCQYDVQQGEwJGUjENMAsGA1UECBMETm9yZDEaMBgGA1UEBxMRVmlsbGVuZXV2ZSBk J0FzY3ExLjAsBgNVBAoTJU5FVEFTUSAtIFNlY3VyZSBJbnRlcm5ldCBDb25uZWN0aXZpdHkxJzAl BgNVBAsTHk5FVEFTUSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eYIBADAOBgNVHQ8BAf8EBAMCBeAw EQYJYIZIAYb4QgEBBAQDAgWgMIHNBgNVHR8EgcUwgcIwWqBYoFaGVGxkYXA6Ly9wa2kubmV0YXNx LmNvbS9jbj1md2NhLG91PWNhcyxvPW5ldGFzcSxkYz1mcj9jZXJ0aWZpY2F0ZVJldm9jYXRpb25M aXN0O2JpbmFyeTA4oDagNIYyaHR0cDovL2ludHJhbmV0Lm5ldGFzcS5jb20vaW50cmFuZXQvcGtp L25ldGFzcS5jcmwwKqAooCaGJGh0dHA6Ly93d3cubmV0YXNxLmNvbS9wa2kvbmV0YXNxLmNybDAf BglghkgBhvhCAQ0EEhYQVXNlciBDZXJ0aWZpY2F0ZTANBgkqhkiG9w0BAQQFAAOCAQEATwF5SdOw IoofZ5U2A16VEBBstYXne5mBItzdvsU8U2AlPXVXcr3/ZsvM0J9ivjKRge1LHVaOgChpxBN5aGhD QfKrWVYPALiqn8gQYWlJ5hmlJvxeAQOBU/hpLx9Y5bJ+3DQBjyDsghdRCL6/0Ym5Aj/VgEiTI/1t hgK6XNCRyonyTnArtGGhgwEqxOSSQ2zkUvg24DLhzSdUMtC+NydUyatJsHiqVuxuM22wVmCQCbjq M9hjGfae9zD1ieAPyeqEHmyCqwBeYblH3EXxnWwXRdKU2VzH1ZAJr5du5hEmlB5yCSEEqMP6joYJ w0QErq8VZxj1SlbEECPqrYz/muQDRzGCAxIwggMOAgEBMIGgMIGRMQswCQYDVQQGEwJGUjENMAsG A1UECBMETm9yZDEaMBgGA1UEBxMRVmlsbGVuZXV2ZSBkJ0FzY3ExLjAsBgNVBAoTJU5FVEFTUSAt IFNlY3VyZSBJbnRlcm5ldCBDb25uZWN0aXZpdHkxJzAlBgNVBAsTHk5FVEFTUSBDZXJ0aWZpY2F0 aW9uIEF1dGhvcml0eQIKcMaxSBZr8pBqZDAJBgUrDgMCGgUAoIIBxzAYBgkqhkiG9w0BCQMxCwYJ KoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wOTAxMTMxMjM4MjJaMCMGCSqGSIb3DQEJBDEWBBQs /AQv77ynpgALw0zBqFApHWO1FDCBsQYJKwYBBAGCNxAEMYGjMIGgMIGRMQswCQYDVQQGEwJGUjEN MAsGA1UECBMETm9yZDEaMBgGA1UEBxMRVmlsbGVuZXV2ZSBkJ0FzY3ExLjAsBgNVBAoTJU5FVEFT USAtIFNlY3VyZSBJbnRlcm5ldCBDb25uZWN0aXZpdHkxJzAlBgNVBAsTHk5FVEFTUSBDZXJ0aWZp Y2F0aW9uIEF1dGhvcml0eQIKcMaxSBZr8pBqZDCBswYLKoZIhvcNAQkQAgsxgaOggaAwgZExCzAJ BgNVBAYTAkZSMQ0wCwYDVQQIEwROb3JkMRowGAYDVQQHExFWaWxsZW5ldXZlIGQnQXNjcTEuMCwG A1UEChMlTkVUQVNRIC0gU2VjdXJlIEludGVybmV0IENvbm5lY3Rpdml0eTEnMCUGA1UECxMeTkVU QVNRIENlcnRpZmljYXRpb24gQXV0aG9yaXR5AgpwxrFIFmvykGpkMA0GCSqGSIb3DQEBAQUABIGA UFUnxt5ghZ6XqG+YvpeOozRotFeS2nQT0A8Dr8y6YYAxOOB0NZXxkDRY7ubWzCt0X8WDunfdu8Oe OO7aGRKMaPr3d3eZp4R2LPTQcf5Vgtu9+D2GyrlEMFeBohpy2PoVHNpIwc44y9r7b8+rvuojFhUo xDwp9XGQYm6Oi4kvpxcAAAAAAAA= --Apple-Mail-59-140032122-- From owner-freebsd-net@FreeBSD.ORG Tue Jan 13 13:36: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 8BC251065670 for ; Tue, 13 Jan 2009 13:36:31 +0000 (UTC) (envelope-from eitans@mellanox.co.il) Received: from mellanox.co.il (mail.mellanox.co.il [194.90.237.43]) by mx1.freebsd.org (Postfix) with ESMTP id BF5648FC1B for ; Tue, 13 Jan 2009 13:36:30 +0000 (UTC) (envelope-from eitans@mellanox.co.il) Received: from Internal Mail-Server by MTLPINE1 (envelope-from eitans@mellanox.co.il) with SMTP; 13 Jan 2009 15:09:46 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Tue, 13 Jan 2009 15:09:11 +0200 Message-ID: <5D49E7A8952DC44FB38C38FA0D758EAD0173629B@mtlexch01.mtl.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: When configuring 2 VLANs to be on the same subnet, only one works. Thread-Index: Acl1gCBZG2HxXxCuQrOAz+bjPdf4vg== From: "Eitan Shefi" To: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: When configuring 2 VLANs to be on the same subnet, only one works. 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, 13 Jan 2009 13:36:31 -0000 I'm testing a NIC driver. I use 2 directly connected FreeBSD-7.0 hosts. When I create 2 VLANs for the same interface (mtnic0), on each host, and configure the VLANs on each host to be on the same subnet: ping works only to one of the VLANs. =20 I run: On sw259:=20 /sbin/ifconfig vlan1 create vlan 1 vlandev mtnic0 /sbin/ifconfig vlan2 create vlan 2 vlandev mtnic0 /sbin/ifconfig vlan1 91.154.12.5 netmask 255.0.0.0 /sbin/ifconfig vlan2 91.155.12.5 netmask 255.0.0.0 =20 On sw260:=20 /sbin/ifconfig vlan1 create vlan 1 vlandev mtnic0 /sbin/ifconfig vlan2 create vlan 2 vlandev mtnic0 /sbin/ifconfig vlan1 91.154.12.6 netmask 255.0.0.0 /sbin/ifconfig vlan2 91.155.12.6 netmask 255.0.0.0 =20 Now on sw259 run:=20 ping 91.154.12.6 - works.=20 ping 91.155.12.6 - does not work.=20 =20 I saw the same behavior also when running via a different NIC. =20 =20 Is this expected ? =20 =20 Thanks, Eitan. From owner-freebsd-net@FreeBSD.ORG Tue Jan 13 14:09:54 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 46B0F10656C3 for ; Tue, 13 Jan 2009 14:09:54 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id E4CEE8FC18 for ; Tue, 13 Jan 2009 14:09:53 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Subject:Message-ID:Reply-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender; b=BKo9SoeKwtH3mcVMbU0yLYga9wUxZkxE8/Z3/e3I5m1Bbpc/v7LdIhYCuNGZkQiwCWth35lgzBIyBNdYQnYpd1t+C7rQVl3xcyDKMXvjCmC2eg/pZ4UJlCIihXaFifnxSaC8UPL4XAafV5eOp96lFevAjOLx/yUjX53SOdS8VkA=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1LMjxn-0008Re-Er; Tue, 13 Jan 2009 17:09:51 +0300 Date: Tue, 13 Jan 2009 17:09:50 +0300 From: Eygene Ryabinkin To: Eitan Shefi Message-ID: <+3+JfrHHIEz9xs7kOtLRj9ebGAs@HEwlnNW4tuDdZ1V6ihYwW3pQ/cw> References: <5D49E7A8952DC44FB38C38FA0D758EAD0173629B@mtlexch01.mtl.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5D49E7A8952DC44FB38C38FA0D758EAD0173629B@mtlexch01.mtl.com> Sender: rea-fbsd@codelabs.ru Cc: freebsd-net@freebsd.org Subject: Re: When configuring 2 VLANs to be on the same subnet, only one works. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rea-fbsd@codelabs.ru List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 14:09:54 -0000 EItan, good day. Tue, Jan 13, 2009 at 03:09:11PM +0200, Eitan Shefi wrote: > I use 2 directly connected FreeBSD-7.0 hosts. > When I create 2 VLANs for the same interface (mtnic0), on each host, and > configure the VLANs on each host to be on the same subnet: > ping works only to one of the VLANs. > > I run: > On sw259: > /sbin/ifconfig vlan1 create vlan 1 vlandev mtnic0 > /sbin/ifconfig vlan2 create vlan 2 vlandev mtnic0 > /sbin/ifconfig vlan1 91.154.12.5 netmask 255.0.0.0 > /sbin/ifconfig vlan2 91.155.12.5 netmask 255.0.0.0 > > On sw260: > /sbin/ifconfig vlan1 create vlan 1 vlandev mtnic0 > /sbin/ifconfig vlan2 create vlan 2 vlandev mtnic0 > /sbin/ifconfig vlan1 91.154.12.6 netmask 255.0.0.0 > /sbin/ifconfig vlan2 91.155.12.6 netmask 255.0.0.0 > > Now on sw259 run: > ping 91.154.12.6 - works. > ping 91.155.12.6 - does not work. You're running two interfaces on the same /8 subnet at one host. I bet that your routing table specifies that packets both for 91.154.12.6 and 91.155.12.6 should go through the same interface, probably vlan1. Could you show output of 'netstat -rn', 'route get 91.154.12.6' and 'route get 91.155.12.6'? Also try to spawn tcpdump on the interface that packets for 91.154.12.6 are routed to and look for the captured packets when pinging 91.155.12.6. Your local firewall could also prevent packets from being pushed to the network, but this actually depens on your configuration. -- Eygene _ ___ _.--. # \`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard / ' ` , __.--' # to read the on-line manual )/' _/ \ `-_, / # while single-stepping the kernel. `-'" `"\_ ,_.-;_.-\_ ', fsc/as # _.-'_./ {_.' ; / # -- FreeBSD Developers handbook {_.-``-' {_/ # From owner-freebsd-net@FreeBSD.ORG Tue Jan 13 14:19: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 CD7331065676 for ; Tue, 13 Jan 2009 14:19:22 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id 185FE8FC13 for ; Tue, 13 Jan 2009 14:19:21 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: by blah.sun-fish.com (Postfix, from userid 1002) id 402DA1B11612; Tue, 13 Jan 2009 15:03:08 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on malcho.cmotd.com X-Spam-Level: X-Spam-Status: No, score=-10.6 required=5.0 tests=ALL_TRUSTED,BAYES_00, HTML_MESSAGE autolearn=ham version=3.2.5 Received: from hater.cmotd.com (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id B626E1B1160F; Tue, 13 Jan 2009 15:03:04 +0100 (CET) Message-Id: From: Stefan Lambrev To: Eitan Shefi In-Reply-To: <5D49E7A8952DC44FB38C38FA0D758EAD0173629B@mtlexch01.mtl.com> Mime-Version: 1.0 (Apple Message framework v930.3) Date: Tue, 13 Jan 2009 16:03:04 +0200 References: <5D49E7A8952DC44FB38C38FA0D758EAD0173629B@mtlexch01.mtl.com> X-Mailer: Apple Mail (2.930.3) X-Virus-Scanned: ClamAV 0.94/8857/Tue Jan 13 08:35:27 2009 on blah.cmotd.com X-Virus-Status: Clean Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re: When configuring 2 VLANs to be on the same subnet, only one works. 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, 13 Jan 2009 14:19:23 -0000 Greetings, For me your configuration looks invalid. Try with netmask 255.255.0.0 The question here is why freebsd allow this. On Jan 13, 2009, at 3:09 PM, Eitan Shefi wrote: > I'm testing a NIC driver. > I use 2 directly connected FreeBSD-7.0 hosts. > When I create 2 VLANs for the same interface (mtnic0), on each host, > and > configure the VLANs on each host to be on the same subnet: > ping works only to one of the VLANs. > > I run: > On sw259: > /sbin/ifconfig vlan1 create vlan 1 vlandev mtnic0 > /sbin/ifconfig vlan2 create vlan 2 vlandev mtnic0 > /sbin/ifconfig vlan1 91.154.12.5 netmask 255.0.0.0 > /sbin/ifconfig vlan2 91.155.12.5 netmask 255.0.0.0 > > On sw260: > /sbin/ifconfig vlan1 create vlan 1 vlandev mtnic0 > /sbin/ifconfig vlan2 create vlan 2 vlandev mtnic0 > /sbin/ifconfig vlan1 91.154.12.6 netmask 255.0.0.0 > /sbin/ifconfig vlan2 91.155.12.6 netmask 255.0.0.0 > > Now on sw259 run: > ping 91.154.12.6 - works. > ping 91.155.12.6 - does not work. > > I saw the same behavior also when running via a different NIC. > > > Is this expected ? > > > Thanks, > Eitan. > _______________________________________________ > 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" -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-net@FreeBSD.ORG Tue Jan 13 15:53: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 560B810656E5 for ; Tue, 13 Jan 2009 15:53:21 +0000 (UTC) (envelope-from aman.jassal@esigetel.fr) Received: from mail.esigetel.fr (venus.esigetel.fr [192.134.106.8]) by mx1.freebsd.org (Postfix) with ESMTP id D22098FC1B for ; Tue, 13 Jan 2009 15:53:20 +0000 (UTC) (envelope-from aman.jassal@esigetel.fr) Received: by mail.esigetel.fr (Postfix, from userid 65534) id 6754A1052B; Tue, 13 Jan 2009 16:35:08 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on venus.esigetel.avon X-Spam-Level: X-Spam-Status: No, score=-4.0 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=unavailable version=3.1.8 Received: from localhost (localhost [127.0.0.1]) by mail.esigetel.fr (Postfix) with ESMTP id 29D5C10541; Tue, 13 Jan 2009 16:35:07 +0100 (CET) X-Virus-Scanned: amavisd-new at esigetel.fr Received: from mail.esigetel.fr ([127.0.0.1]) by localhost (venus.esigetel.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j3guYKCEdf67; Tue, 13 Jan 2009 16:35:01 +0100 (CET) Received: from webmail.esigetel.fr (neo.ecampus.avon [192.168.106.14]) by mail.esigetel.fr (Postfix) with ESMTP id 95A8C1052A; Tue, 13 Jan 2009 16:35:01 +0100 (CET) Received: from 193.49.124.107 (proxying for unknown) by webmail.esigetel.fr with HTTP; Tue, 13 Jan 2009 16:35:01 +0100 (CET) Message-ID: <52831.193.49.124.107.1231860901.squirrel@webmail.esigetel.fr> In-Reply-To: References: <5D49E7A8952DC44FB38C38FA0D758EAD0173629B@mtlexch01.mtl.com> Date: Tue, 13 Jan 2009 16:35:01 +0100 (CET) From: "JASSAL Aman" To: "Eitan Shefi" User-Agent: SquirrelMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-net@freebsd.org Subject: Re: When configuring 2 VLANs to be on the same subnet, only one works. 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, 13 Jan 2009 15:53:21 -0000 Hello Eitan, I am no expert but I believe Stefan is right, your having a netmask of 255.0.0.0 does look strange. The way I see it, I think you are trying to configure 2 IP addresses belonging to the same subnet (91.0.0.0/8) on your interface, but only the first address is taken into account (91.154.12.5 on sw259 and 91.154.12.6 on sw260). Hence ping 91.154.12.6 from sw259 fails. Setting a netmask of 255.255.0.0 as Stefan suggested should solve your problem. Kind regards, Aman Jassal Le Mar 13 janvier 2009 15:03, Stefan Lambrev a écrit : > Greetings, > > > For me your configuration looks invalid. Try with netmask 255.255.0.0 > The question here is why freebsd allow this. > > > On Jan 13, 2009, at 3:09 PM, Eitan Shefi wrote: > > >> I'm testing a NIC driver. >> I use 2 directly connected FreeBSD-7.0 hosts. >> When I create 2 VLANs for the same interface (mtnic0), on each host, >> and configure the VLANs on each host to be on the same subnet: ping works >> only to one of the VLANs. >> >> I run: >> On sw259: >> /sbin/ifconfig vlan1 create vlan 1 vlandev mtnic0 >> /sbin/ifconfig vlan2 create vlan 2 vlandev mtnic0 >> /sbin/ifconfig vlan1 91.154.12.5 netmask 255.0.0.0 >> /sbin/ifconfig vlan2 91.155.12.5 netmask 255.0.0.0 >> >> >> On sw260: >> /sbin/ifconfig vlan1 create vlan 1 vlandev mtnic0 >> /sbin/ifconfig vlan2 create vlan 2 vlandev mtnic0 >> /sbin/ifconfig vlan1 91.154.12.6 netmask 255.0.0.0 >> /sbin/ifconfig vlan2 91.155.12.6 netmask 255.0.0.0 >> >> >> Now on sw259 run: >> ping 91.154.12.6 - works. ping 91.155.12.6 - does not work. >> >> I saw the same behavior also when running via a different NIC. >> >> >> >> Is this expected ? >> >> >> >> Thanks, >> Eitan. >> _______________________________________________ >> 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" >> > > -- > Best Wishes, > Stefan Lambrev > ICQ# 24134177 > > > > > > > _______________________________________________ > 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 Jan 13 17:59: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 77FD5106564A for ; Tue, 13 Jan 2009 17:59:05 +0000 (UTC) (envelope-from prvs=julian=257c50d56@elischer.org) Received: from smtp-outbound.ironport.com (smtp-outbound.ironport.com [63.251.108.112]) by mx1.freebsd.org (Postfix) with ESMTP id 63E398FC1A for ; Tue, 13 Jan 2009 17:59:05 +0000 (UTC) (envelope-from prvs=julian=257c50d56@elischer.org) Received: from unknown (HELO julian-mac.elischer.org) ([10.251.60.222]) by smtp-outbound.ironport.com with ESMTP; 13 Jan 2009 09:30:40 -0800 Message-ID: <496CCFBF.3010008@elischer.org> Date: Tue, 13 Jan 2009 09:30:39 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: Dimitar Vasilev References: <59adc1a0901122114v15efa47ahba8beef6ace4ddb0@mail.gmail.com> In-Reply-To: <59adc1a0901122114v15efa47ahba8beef6ace4ddb0@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: setfib+pf 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, 13 Jan 2009 17:59:05 -0000 Dimitar Vasilev wrote: > Hi, I originally posted my message to questions, however no response for > about a week. Therefore I'm reposting here. Original question available at > http://lists.freebsd.org/pipermail/freebsd-questions/2009-January/190056.html > For those who prefer reading human text, here are my questions: > > I'd like to ask on the best options for using setfib and pf in a non-BGP > environment. I will run 2 uplinks, with VLANs for internal networks and want > to fail over external links if one of them fails.(Extended note as of 13.01: > Uplink routers will be a WRT54GL with OpenWRT and an Alix box hopefully. > Vlan tagging also possible there. Alix will be the controlling router > station for failover). > > Currently pf supports to the best of my knowledge: > > a) rtable - this means i can create the routing tables with setfib and then > use pass from .... rtable N( N >1 <16) or give out directly network ranges ( 0 <= N < 16 ) i.e. 0 through 15 (for now) > b) route-to - pass in/out on X from ... route-to > c) packet tagging - i can tag networks and use standalone or through routing > tags. Anyone aware if is it ok to use /etc/gateways without running routed > or how can i label routes alternatively? If I apply the same for > /etc/networks or both /etc/gateways and networks will it be ok? > > pass in from any to $big_salad via $fridge keep state for example? > > d) pass in from route N(192.168.1.1 for example) to... - saw this on > http://www.mail-archive.com/pf@benzedrine.cx/msg07220.html and requires BGP > to make tags speak anything but network numbers. > e) use the vlan id's > > I'd much appreciate if someone thinks with me for the best options of using > the setfib features along with pf. I know setfib but I don't know pf unfortunately.. I use ipfw (which is why ipfw has fib support :-) possibly Max Lair may know both.. > > Thanks and regards, > Dimitar Vassilev > _______________________________________________ > 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 Jan 13 20:10: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 27EF11065677 for ; Tue, 13 Jan 2009 20:10: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 161DB8FC23 for ; Tue, 13 Jan 2009 20:10:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0DKA2U9039813 for ; Tue, 13 Jan 2009 20:10:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0DKA2o5039812; Tue, 13 Jan 2009 20:10:02 GMT (envelope-from gnats) Date: Tue, 13 Jan 2009 20:10:02 GMT Message-Id: <200901132010.n0DKA2o5039812@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Jason Brand Cc: Subject: Re: kern/128917: [wpi] [panic] if_wpi and wpa+tkip causing kernel panic X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jason Brand List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 20:10:03 -0000 The following reply was made to PR kern/128917; it has been noted by GNATS. From: Jason Brand To: bug-followup@FreeBSD.org;, kitambi@epicsol.org Cc: Subject: Re: kern/128917: [wpi] [panic] if_wpi and wpa+tkip causing kernel panic Date: Tue, 13 Jan 2009 15:01:05 -0500 Additional information: I have managed to reproduce this issue on different network that uses WPA+TKIP, with PAP as the phase2 method. Backtrace: Breakpoint 1 at 0xc058bc5c: file pcpu.h, line 196. (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xc058c347 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc058c652 in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc07e34f3 in trap_fatal (frame=0xe6db9ba0, eva=65535) at /usr/src/sys/i386/i386/trap.c:939 #4 0xc07e3750 in trap_pfault (frame=0xe6db9ba0, usermode=0, eva=65535) at /usr/src/sys/i386/i386/trap.c:852 #5 0xc07e4122 in trap (frame=0xe6db9ba0) at /usr/src/sys/i386/i386/trap.c:530 #6 0xc07ca90b in calltrap () at /usr/src/sys/i386/i386/exception.s:159 #7 0xc0a17dfc in wpi_ops (arg0=0xc68fe000, pending=1) at /usr/src/sys/modules/wpi/../../dev/wpi/if_wpi.c:2411 #8 0xc05bf795 in taskqueue_run (queue=0xc68f7a00) at /usr/src/sys/kern/subr_taskqueue.c:282 #9 0xc05bf99b in taskqueue_thread_loop (arg=0xc68ff9b4) at /usr/src/sys/kern/subr_taskqueue.c:401 #10 0xc0567eb9 in fork_exit (callout=0xc05bf8e0 , arg=0xc68ff9b4, frame=0xe6db9d38) at /usr/src/sys/kern/kern_fork.c:804 #11 0xc07ca980 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:264 WPA information: Selected interface 'wpi0' bssid=00:0c:e6:xx:xx:xx ssid= id=2 pairwise_cipher=TKIP group_cipher=TKIP key_mgmt=WPA/IEEE 802.1X/EAP wpa_state=ASSOCIATED ip_address=0.0.0.0 Supplicant PAE state=HELD suppPortStatus=Unauthorized EAP state=FAILURE selectedMethod=21 (EAP-TTLS) EAP TLS cipher=(NONE) EAP-TTLSv0 Phase2 method=PAP From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 08:09: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 3DBEC1065673; Wed, 14 Jan 2009 08:09:45 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.185]) by mx1.freebsd.org (Postfix) with ESMTP id D687A8FC13; Wed, 14 Jan 2009 08:09:44 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: by rn-out-0910.google.com with SMTP id j71so467074rne.12 for ; Wed, 14 Jan 2009 00:09:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:mime-version:content-type:content-transfer-encoding :content-disposition; bh=/ic+S2d/kcl4K05WCTpx6gzQLUJM5a3PfLtgN2khRL4=; b=nZAcTpGYX3nMI9iuGaOA6KoEcOZJEuJaCDA0VEdmLynxbgMfkjpr/hY477/ufFyPII h6uhmtiaW9a63qbntSJaKKVmRoIZLWxgDghe0P/wXEOW3ESCNdAdaZRGPFNEe0dJG8Ij agr0PxXnJSMvre4xhsIGMwViNtjJBv1fOtdf0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:mime-version:content-type :content-transfer-encoding:content-disposition; b=qELCR3ttjwABDI1YhZ3nWr0Dqf90Kfwiyy5rDDToCe5NLivqZ/av/Mes/DuB9RfZRw UEeB3nJad+AdLnR46VP45htVQIARAQ0qqU6DMbI7cCZb4scPY03ZSaZK+l1S/zCdeoMU EBaIjXMhCw2RcrDhe9CxX9PpVW8JqZ8NH41Ls= Received: by 10.151.85.9 with SMTP id n9mr1405070ybl.150.1231920584041; Wed, 14 Jan 2009 00:09:44 -0800 (PST) Received: by 10.150.229.15 with HTTP; Wed, 14 Jan 2009 00:09:44 -0800 (PST) Message-ID: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> Date: Wed, 14 Jan 2009 10:09:44 +0200 From: "Yony Yossef" To: freebsd-net@freebsd.org, freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: eitans@mellanox.co.il, oleg@mellanox.co.il, liranl@mellanox.co.il Subject: howto determine network device unit number? device.hints? 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, 14 Jan 2009 08:09:45 -0000 Hi, I would like to determine the unit number of my network cards, e.g. make the device on pci0:16 be assigned every time with unit number 0 and pci0:19 with unit number 1. Is it done by /boot/device.hints? if so, how? My cards are: mtnic0@pci0:19:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 rev=0xa0 hdr=0x00 mtnic1@pci0:16:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 rev=0xa0 hdr=0x00 So I've tried: hint.mtnic.0.at="pci0:16" hint.mtnic.1.at="pci0:19" but it doesn't work. They keep switching arbitrarily. I'm using FreeBSD 7.0. Thanks Yony From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 16:39: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 3867F1065698; Wed, 14 Jan 2009 16:39:04 +0000 (UTC) (envelope-from fazaeli@sepehrs.com) Received: from sepehrs.com (www.sepehrs.com [213.217.59.98]) by mx1.freebsd.org (Postfix) with ESMTP id DE62C8FC1D; Wed, 14 Jan 2009 16:39:01 +0000 (UTC) (envelope-from fazaeli@sepehrs.com) Received: from [192.168.1.180] ([192.168.1.180]) by sepehrs.com (8.13.6/8.13.6) with ESMTP id n0EGeddx049081; Wed, 14 Jan 2009 20:10:39 +0330 (IRST) (envelope-from fazaeli@sepehrs.com) Message-ID: <496E11B7.3010608@sepehrs.com> Date: Wed, 14 Jan 2009 19:54:23 +0330 From: "H.fazaeli" User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Yony Yossef References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> In-Reply-To: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Sepehr-MailScanner-Information: Please contact the ISP for more information X-Sepehr-MailScanner: Found to be clean X-Sepehr-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.399, required 5, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60) X-MailScanner-From: fazaeli@sepehrs.com X-Spam-Status: No Cc: eitans@mellanox.co.il, freebsd-net@freebsd.org, oleg@mellanox.co.il, freebsd-questions@freebsd.org, liranl@mellanox.co.il Subject: Re: howto determine network device unit number? device.hints? 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, 14 Jan 2009 16:39:05 -0000 you may not change unit numbers as they are strictly controlled by kernel. However, on freebsd 5.3+, you may use 'ifconfig name ' to achieve the same affect Yony Yossef wrote: > Hi, > > I would like to determine the unit number of my network cards, e.g. > make the device on pci0:16 be assigned every time with unit number 0 > and pci0:19 with unit number 1. > > Is it done by /boot/device.hints? > if so, how? > > My cards are: > > mtnic0@pci0:19:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 > rev=0xa0 hdr=0x00 > mtnic1@pci0:16:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 > rev=0xa0 hdr=0x00 > > So I've tried: > > hint.mtnic.0.at="pci0:16" > hint.mtnic.1.at="pci0:19" > > but it doesn't work. They keep switching arbitrarily. > I'm using FreeBSD 7.0. > > Thanks > Yony > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > > -- Best regards. Hooman Fazaeli Sepehr S. T. Co. Ltd. Web: http://www.sepehrs.com Tel: (9821)88975701-2 Fax: (9821)88983352 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21:22:01 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 9DE31106566B; Wed, 14 Jan 2009 21:22:01 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by mx1.freebsd.org (Postfix) with ESMTP id F19208FC0C; Wed, 14 Jan 2009 21:22:00 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: by ug-out-1314.google.com with SMTP id 30so339744ugs.39 for ; Wed, 14 Jan 2009 13:22:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references:subject :date:message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:x-mimeole:in-reply-to; bh=Bbs7Eg8jRJigA724edIgwwP1dfjGei1wOujtWT587Zo=; b=hCFRg+k8RnSd94j8Kq8DWnmzI38C+iSeaWDNGjFDNUHAaWEwANrNguEp1pgaqcPCaU Kj3KokzcizbuIBzkyV/z1WCgpoioSzS2v0An+yZzALU8XkV445OFtxcxN3HRMN2N4wbP CHUGFe6ieA1zaX8WxGL47asUFH0e21sd9kJBw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :x-mimeole:in-reply-to; b=CawGrMsLB2jisc5/DwNFMNeeBio2V9f+iUbCQfIof1txNnSGo0qVFLSs+YwyWGR+dT IR3LXWqscIMx67s+5KauZsiaDeEv5UfZLETwaqgggDBNmx6aUu3hwj709ZVeuDuz7mto b6Br589vnUq0Pysr0HoNfcIW8NsYMUoegi3tU= Received: by 10.66.224.19 with SMTP id w19mr2894987ugg.71.1231968119963; Wed, 14 Jan 2009 13:21:59 -0800 (PST) Received: from mtllpt03 (bzq-79-180-238-90.red.bezeqint.net [79.180.238.90]) by mx.google.com with ESMTPS id 40sm5382118uge.51.2009.01.14.13.21.55 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 14 Jan 2009 13:21:58 -0800 (PST) From: "Yony Yossef" To: "'H.fazaeli'" , "Yony Yossef" References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> <496E11B7.3010608@sepehrs.com> Date: Wed, 14 Jan 2009 23:21:50 +0200 Message-ID: <000a01c9768e$1ff65240$220f000a@mtl.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acl2ZLFIvz5BW5IpTT+eTfDCOC1kvQAKTARQ X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 In-Reply-To: <496E11B7.3010608@sepehrs.com> Cc: Eitan Shefi , freebsd-net@freebsd.org, Oleg Kats , freebsd-questions@freebsd.org, Liran Liss Subject: RE: howto determine network device unit number? device.hints? 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, 14 Jan 2009 21:22:02 -0000 > > you may not change unit numbers as they are strictly > controlled by kernel. > However, on freebsd 5.3+, you may use 'ifconfig name ' > to achieve the same affect > Sorry, I don't understand the usage of ifconfig you suggested and the effect it will cause. Can you please explain it? Yony > > Yony Yossef wrote: > > Hi, > > > > I would like to determine the unit number of my network cards, e.g. > > make the device on pci0:16 be assigned every time with unit > number 0 > > and pci0:19 with unit number 1. > > > > Is it done by /boot/device.hints? > > if so, how? > > > > My cards are: > > > > mtnic0@pci0:19:0:0: class=0x020000 card=0x001715b3 > chip=0x636815b3 > > rev=0xa0 hdr=0x00 > > mtnic1@pci0:16:0:0: class=0x020000 card=0x001715b3 > chip=0x636815b3 > > rev=0xa0 hdr=0x00 > > > > So I've tried: > > > > hint.mtnic.0.at="pci0:16" > > hint.mtnic.1.at="pci0:19" > > > > but it doesn't work. They keep switching arbitrarily. > > I'm using FreeBSD 7.0. > > > > Thanks > > Yony From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21:22:55 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 46552106567E; Wed, 14 Jan 2009 21:22:55 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1BCCF8FC1A; Wed, 14 Jan 2009 21:22:55 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ELMstV049310; Wed, 14 Jan 2009 21:22:54 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ELMseV049306; Wed, 14 Jan 2009 21:22:54 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 21:22:54 GMT Message-Id: <200901142122.n0ELMseV049306@freefall.freebsd.org> To: scheidell@secnap.net, vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: i386/45773: [bge] Softboot causes autoconf failure on Broadcom 5703 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, 14 Jan 2009 21:22:56 -0000 Synopsis: [bge] Softboot causes autoconf failure on Broadcom 5703 State-Changed-From-To: open->feedback State-Changed-By: vwe State-Changed-When: Wed Jan 14 21:21:47 UTC 2009 State-Changed-Why: Michael, can you please tell us if you're still seeing the issue with late{r|est} releases? Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 21:21:47 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=45773 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21:24:09 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 366531065932; Wed, 14 Jan 2009 21:24:09 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0A3948FC0A; Wed, 14 Jan 2009 21:24:09 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ELO8Jo049390; Wed, 14 Jan 2009 21:24:08 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ELO88i049386; Wed, 14 Jan 2009 21:24:08 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 21:24:08 GMT Message-Id: <200901142124.n0ELO88i049386@freefall.freebsd.org> To: nebpub@yahoo.fr, vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/73538: [bge] problem with the Broadcom BCM5788 Gigabit Ethernet 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, 14 Jan 2009 21:24:10 -0000 Synopsis: [bge] problem with the Broadcom BCM5788 Gigabit Ethernet State-Changed-From-To: open->feedback State-Changed-By: vwe State-Changed-When: Wed Jan 14 21:23:10 UTC 2009 State-Changed-Why: Ben, is this still an issue with recent releases? Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 21:23:10 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=73538 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21:24: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 604D41065672; Wed, 14 Jan 2009 21:24:23 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id B46E88FC24; Wed, 14 Jan 2009 21:24:22 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: by ug-out-1314.google.com with SMTP id 30so339912ugs.39 for ; Wed, 14 Jan 2009 13:24:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references:subject :date:message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:x-mimeole:in-reply-to; bh=2G3hJK5DrqV8EvhW/aDYWUXSPtndl/EDv/677ZY2aTA=; b=tztvsV5YyAHlEYXtnpNk8QqmLU0XidEhqUO4hQNzRoOaZmwkemhSOo0b0/YbIyJg6c s7XTZiwLCYkRt9Ez/9ltefhI6dVgChlI24KYSM6Ae/uP7YfU5T+26Ph0inzcqGa7Qe9O eKSkIxE1uGi0h7BtginjG/F8rStfH9HegviSk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :x-mimeole:in-reply-to; b=NO4G7YtOXdFPszniaL3gAmmZR1LN/RNqAZ2WB5Nuk5pDuCW4Pno8J50fBe35M8AD1d HkPcSeCWRL1EV/DP/A7du6T2JTIv7s42Rsq4QlakEKqwR+x9ylrh21s/ASDECS4kTrUO 4TPUVu3OZE1O9X7vbeveoCs+BPeV++4XcaElM= Received: by 10.67.25.9 with SMTP id c9mr2907496ugj.14.1231968261357; Wed, 14 Jan 2009 13:24:21 -0800 (PST) Received: from mtllpt03 (bzq-79-180-238-90.red.bezeqint.net [79.180.238.90]) by mx.google.com with ESMTPS id u1sm5380686uge.55.2009.01.14.13.24.19 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 14 Jan 2009 13:24:20 -0800 (PST) From: "Yony Yossef" To: "'H.fazaeli'" References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> <496E11B7.3010608@sepehrs.com> Date: Wed, 14 Jan 2009 23:24:12 +0200 Message-ID: <000b01c9768e$745aa160$220f000a@mtl.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acl2ZLFIvz5BW5IpTT+eTfDCOC1kvQAKbJWQ X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 In-Reply-To: <496E11B7.3010608@sepehrs.com> Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org Subject: RE: howto determine network device unit number? device.hints? 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, 14 Jan 2009 21:24:24 -0000 > -----Original Message----- > From: H.fazaeli [mailto:fazaeli@sepehrs.com] > Sent: Wednesday, January 14, 2009 6:24 PM > To: Yony Yossef > Cc: freebsd-net@freebsd.org; freebsd-questions@freebsd.org; > Eitan Shefi; Oleg Kats; Liran Liss > Subject: Re: howto determine network device unit number? device.hints? > > > you may not change unit numbers as they are strictly > controlled by kernel. > However, on freebsd 5.3+, you may use 'ifconfig name ' > to achieve the same affect > Sorry, I don't understand the usage of ifconfig you suggested and the effect it will cause. Can you please explain it? Yony > > Yony Yossef wrote: > > Hi, > > > > I would like to determine the unit number of my network cards, e.g. > > make the device on pci0:16 be assigned every time with unit > number 0 > > and pci0:19 with unit number 1. > > > > Is it done by /boot/device.hints? > > if so, how? > > > > My cards are: > > > > mtnic0@pci0:19:0:0: class=0x020000 card=0x001715b3 > chip=0x636815b3 > > rev=0xa0 hdr=0x00 > > mtnic1@pci0:16:0:0: class=0x020000 card=0x001715b3 > chip=0x636815b3 > > rev=0xa0 hdr=0x00 > > > > So I've tried: > > > > hint.mtnic.0.at="pci0:16" > > hint.mtnic.1.at="pci0:19" > > > > but it doesn't work. They keep switching arbitrarily. > > I'm using FreeBSD 7.0. > > > > Thanks > > Yony > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > > > > > > > > -- > > > Best regards. > > Hooman Fazaeli > Sepehr S. T. Co. Ltd. > > Web: http://www.sepehrs.com > Tel: (9821)88975701-2 > Fax: (9821)88983352 > > > > > From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21:27:49 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 F41A6106581B; Wed, 14 Jan 2009 21:27:48 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C9D6F8FC0C; Wed, 14 Jan 2009 21:27:48 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ELRmmT049460; Wed, 14 Jan 2009 21:27:48 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ELRm9G049456; Wed, 14 Jan 2009 21:27:48 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 21:27:48 GMT Message-Id: <200901142127.n0ELRm9G049456@freefall.freebsd.org> To: bsdjoe@gmail.com, vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/75407: [an] an(4): no carrier after short time 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, 14 Jan 2009 21:27:50 -0000 Synopsis: [an] an(4): no carrier after short time State-Changed-From-To: open->feedback State-Changed-By: vwe State-Changed-When: Wed Jan 14 21:27:10 UTC 2009 State-Changed-Why: Joe, is this report still true for recent releases? Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 21:27:10 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=75407 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21:33:06 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 BE2311065A6D; Wed, 14 Jan 2009 21:33:06 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 920348FC33; Wed, 14 Jan 2009 21:33:06 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ELX612058189; Wed, 14 Jan 2009 21:33:06 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ELX5F9058176; Wed, 14 Jan 2009 21:33:05 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 21:33:05 GMT Message-Id: <200901142133.n0ELX5F9058176@freefall.freebsd.org> To: liudasb@centras.lt, vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/79262: [dc] Adaptec ANA-6922 not fully supported 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, 14 Jan 2009 21:33:09 -0000 Synopsis: [dc] Adaptec ANA-6922 not fully supported State-Changed-From-To: open->feedback State-Changed-By: vwe State-Changed-When: Wed Jan 14 21:32:23 UTC 2009 State-Changed-Why: Liudas, is this issue still true for recent releases? Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 21:32:23 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=79262 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21:34:11 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 71D631065A53; Wed, 14 Jan 2009 21:34:11 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 45DA68FC29; Wed, 14 Jan 2009 21:34:11 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ELYBxh058336; Wed, 14 Jan 2009 21:34:11 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ELYAtk058332; Wed, 14 Jan 2009 21:34:10 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 21:34:10 GMT Message-Id: <200901142134.n0ELYAtk058332@freefall.freebsd.org> To: doconnor@gsoft.com.au, vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/81644: [vge] vge(4) does not work properly when loaded as a KLD 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, 14 Jan 2009 21:34:13 -0000 Synopsis: [vge] vge(4) does not work properly when loaded as a KLD State-Changed-From-To: open->feedback State-Changed-By: vwe State-Changed-When: Wed Jan 14 21:33:26 UTC 2009 State-Changed-Why: Daniel, is this PR still true for recent releases? Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 21:33:26 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=81644 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21:34:54 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 5B83D1065CCF; Wed, 14 Jan 2009 21:34:54 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 32E338FC2A; Wed, 14 Jan 2009 21:34:54 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ELYsR4058382; Wed, 14 Jan 2009 21:34:54 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ELYsJ3058378; Wed, 14 Jan 2009 21:34:54 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 21:34:54 GMT Message-Id: <200901142134.n0ELYsJ3058378@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/82497: [vge] vge(4) on AMD64 only works when loaded late, not in loader.conf 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, 14 Jan 2009 21:34:56 -0000 Synopsis: [vge] vge(4) on AMD64 only works when loaded late, not in loader.conf Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 21:34:42 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=82497 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21:36:28 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 950731065888; Wed, 14 Jan 2009 21:36:28 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 67D688FC0C; Wed, 14 Jan 2009 21:36:28 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ELaSOu058446; Wed, 14 Jan 2009 21:36:28 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ELaSFZ058442; Wed, 14 Jan 2009 21:36:28 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 21:36:28 GMT Message-Id: <200901142136.n0ELaSFZ058442@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/85266: [xe] [patch] xe(4) driver does not recognise Xircom XE2000 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, 14 Jan 2009 21:36:31 -0000 Synopsis: [xe] [patch] xe(4) driver does not recognise Xircom XE2000 Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 21:36:08 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=85266 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21:36:56 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 976041065818; Wed, 14 Jan 2009 21:36:56 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 68BE28FC18; Wed, 14 Jan 2009 21:36:56 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ELauiS058492; Wed, 14 Jan 2009 21:36:56 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ELauwd058488; Wed, 14 Jan 2009 21:36:56 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 21:36:56 GMT Message-Id: <200901142136.n0ELauwd058488@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/87194: [fxp] fxp(4) promiscuous mode seems to corrupt hw-csum 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, 14 Jan 2009 21:37:00 -0000 Synopsis: [fxp] fxp(4) promiscuous mode seems to corrupt hw-csum Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 21:36:45 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=87194 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21: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 9F01E10657EE; Wed, 14 Jan 2009 21:40:04 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6FA9C8FC0C; Wed, 14 Jan 2009 21:40:04 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ELe4VR058627; Wed, 14 Jan 2009 21:40:04 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ELe4g4058623; Wed, 14 Jan 2009 21:40:04 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 21:40:04 GMT Message-Id: <200901142140.n0ELe4g4058623@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/87506: [vr] [patch] Fix alias support on vr 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, 14 Jan 2009 21:40:06 -0000 Synopsis: [vr] [patch] Fix alias support on vr interfaces Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 21:39:50 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=87506 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21:42:09 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 4CEA61065C42; Wed, 14 Jan 2009 21:42:09 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1BB698FC08; Wed, 14 Jan 2009 21:42:09 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ELg8N9065423; Wed, 14 Jan 2009 21:42:08 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ELg80s065419; Wed, 14 Jan 2009 21:42:08 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 21:42:08 GMT Message-Id: <200901142142.n0ELg80s065419@freefall.freebsd.org> To: kerneljake@hotmail.com, vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/88082: [ath] [panic] cts protection for ath0 causes 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: Wed, 14 Jan 2009 21:42:14 -0000 Synopsis: [ath] [panic] cts protection for ath0 causes panic State-Changed-From-To: open->feedback State-Changed-By: vwe State-Changed-When: Wed Jan 14 21:40:31 UTC 2009 State-Changed-Why: Jake, is this problem still true with later releases? I'm pretty sure I've used CTS on ath myself and have never seen such a panic. Please give us feedback so we don't need to check things which aren't broken. Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 21:40:31 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=88082 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21:42:32 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 491DA1065D27; Wed, 14 Jan 2009 21:42:32 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1F51D8FC22; Wed, 14 Jan 2009 21:42:32 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ELgW7e065472; Wed, 14 Jan 2009 21:42:32 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ELgVL6065468; Wed, 14 Jan 2009 21:42:31 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 21:42:31 GMT Message-Id: <200901142142.n0ELgVL6065468@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/90890: [vr] Problems with network: vr0: tx shutdown timeout 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, 14 Jan 2009 21:42:33 -0000 Synopsis: [vr] Problems with network: vr0: tx shutdown timeout Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 21:42:21 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=90890 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21:43:32 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 39D22106597B; Wed, 14 Jan 2009 21:43:32 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 10C588FC1B; Wed, 14 Jan 2009 21:43:32 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ELhVP8065550; Wed, 14 Jan 2009 21:43:31 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ELhVMe065546; Wed, 14 Jan 2009 21:43:31 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 21:43:31 GMT Message-Id: <200901142143.n0ELhVMe065546@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/91311: [aue] aue interface hanging 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, 14 Jan 2009 21:43:33 -0000 Synopsis: [aue] aue interface hanging Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 21:42:54 UTC 2009 Responsible-Changed-Why: probably more usb related? someone might check that. Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=91311 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21:43:55 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 B437A1065D67; Wed, 14 Jan 2009 21:43:55 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 867F08FC1E; Wed, 14 Jan 2009 21:43:55 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ELhtIS065596; Wed, 14 Jan 2009 21:43:55 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ELht9g065592; Wed, 14 Jan 2009 21:43:55 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 21:43:55 GMT Message-Id: <200901142143.n0ELht9g065592@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/91364: [ral] [wep] WF-511 RT2500 Card PCI and WEP 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, 14 Jan 2009 21:43:58 -0000 Synopsis: [ral] [wep] WF-511 RT2500 Card PCI and WEP Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 21:43:46 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=91364 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21:45:28 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 1EFE41065CD5; Wed, 14 Jan 2009 21:45:28 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id EA89C8FC1D; Wed, 14 Jan 2009 21:45:27 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ELjR5L065660; Wed, 14 Jan 2009 21:45:27 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ELjR5U065656; Wed, 14 Jan 2009 21:45:27 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 21:45:27 GMT Message-Id: <200901142145.n0ELjR5U065656@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/91859: [ndis] if_ndis does not work with Asus WL-138 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, 14 Jan 2009 21:45:29 -0000 Synopsis: [ndis] if_ndis does not work with Asus WL-138 Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 21:45:17 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=91859 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21:48:54 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 EEFE510658F3; Wed, 14 Jan 2009 21:48:54 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C36768FC0C; Wed, 14 Jan 2009 21:48:54 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ELmsHp065729; Wed, 14 Jan 2009 21:48:54 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ELmspT065725; Wed, 14 Jan 2009 21:48:54 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 21:48:54 GMT Message-Id: <200901142148.n0ELmspT065725@freefall.freebsd.org> To: pbelanger@pt.com, vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/92279: [dc] Core faults everytime I reboot, possible NIC issue. 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, 14 Jan 2009 21:48:56 -0000 Synopsis: [dc] Core faults everytime I reboot, possible NIC issue. State-Changed-From-To: open->feedback State-Changed-By: vwe State-Changed-When: Wed Jan 14 21:47:07 UTC 2009 State-Changed-Why: Paul, by any chance, do you have a backtrace for us? w/o a backtrace, I don't see a chance to imagine the call path and thus we don't know where it breaks. If you don't have one handy and can't reprodruce the panic, please give us feedback so we can close the PR - thanks. Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 21:47:07 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=92279 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21:50:07 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 4E0341065808; Wed, 14 Jan 2009 21:50:07 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 22A2A8FC18; Wed, 14 Jan 2009 21:50:07 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ELo7Bn065852; Wed, 14 Jan 2009 21:50:07 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ELo7eR065848; Wed, 14 Jan 2009 21:50:07 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 21:50:07 GMT Message-Id: <200901142150.n0ELo7eR065848@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/92675: [fxp] [patch] fxp(4) unable to recover from occasional receiver unit allocation failure 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, 14 Jan 2009 21:50:08 -0000 Synopsis: [fxp] [patch] fxp(4) unable to recover from occasional receiver unit allocation failure Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 21:49:57 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=92675 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21:50:43 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 327641065A4B; Wed, 14 Jan 2009 21:50:43 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 07CC58FC27; Wed, 14 Jan 2009 21:50:43 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ELogJD070591; Wed, 14 Jan 2009 21:50:42 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ELognp070581; Wed, 14 Jan 2009 21:50:42 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 21:50:42 GMT Message-Id: <200901142150.n0ELognp070581@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/93886: [ath] Atheros/D-Link DWL-G650 long delay to associate on 6.1-PRERELEASE 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, 14 Jan 2009 21:50:44 -0000 Synopsis: [ath] Atheros/D-Link DWL-G650 long delay to associate on 6.1-PRERELEASE Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 21:50:32 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=93886 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21:51:16 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 11BB11065DC4; Wed, 14 Jan 2009 21:51:16 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DCCE78FC26; Wed, 14 Jan 2009 21:51:15 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ELpF19072670; Wed, 14 Jan 2009 21:51:15 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ELpFIf072666; Wed, 14 Jan 2009 21:51:15 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 21:51:15 GMT Message-Id: <200901142151.n0ELpFIf072666@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/94162: [bge] 6.x kenel stale with bge(4) 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, 14 Jan 2009 21:51:17 -0000 Synopsis: [bge] 6.x kenel stale with bge(4) Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 21:51:06 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=94162 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21:51: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 A5B80106568B; Wed, 14 Jan 2009 21:51:51 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7D8D08FC08; Wed, 14 Jan 2009 21:51:51 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ELppRD072716; Wed, 14 Jan 2009 21:51:51 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ELppqL072712; Wed, 14 Jan 2009 21:51:51 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 21:51:51 GMT Message-Id: <200901142151.n0ELppqL072712@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/94863: [bge] [patch] hack to get bge(4) working on IBM e326m 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, 14 Jan 2009 21:51:54 -0000 Synopsis: [bge] [patch] hack to get bge(4) working on IBM e326m Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 21:51:39 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=94863 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 21:52:19 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 5BF071065C4F; Wed, 14 Jan 2009 21:52:19 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 301DC8FC1E; Wed, 14 Jan 2009 21:52:19 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ELqJIP072762; Wed, 14 Jan 2009 21:52:19 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ELqJYB072758; Wed, 14 Jan 2009 21:52:19 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 21:52:19 GMT Message-Id: <200901142152.n0ELqJYB072758@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/95519: [ral] ral0 could not map mbuf 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, 14 Jan 2009 21:52:21 -0000 Synopsis: [ral] ral0 could not map mbuf Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 21:52:09 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=95519 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 22:13:01 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 79D521065727 for ; Wed, 14 Jan 2009 22:13:01 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.freebsd.org (Postfix) with ESMTP id B094E8FC1E for ; Wed, 14 Jan 2009 22:13:00 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by nf-out-0910.google.com with SMTP id h3so127779nfh.33 for ; Wed, 14 Jan 2009 14:12:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=popvJljn6elXYDxYTVneW9M1uzFDTf1ikAW5oFKuySQ=; b=c52I7P/b8eVyEkp9lFgcTyWQNW9iZ/1ebkJs+PxP6zw0eHFwM7vykpwiMM3lSW5uit LC3lXZuqW3X+WyYLtnbPm2Ldqyaj294MYnI/uKL1JjA9ngv/D1ZGtcd9Jgpz4+iAhcEs /5xdOxBN9QgpMh/++dbo5fPJYoi/8DMSNX5P0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=Gs1C3idGm0yMYO+mmA1hPWx2azFtpnlkE6hgNT5SraiyEbEE5SmTLl9kMZVFGfVFvT A7PAo3MVwiWmYcDoJ7hWITNDvTuGxrybIX8ObmTsew/GusXZiujlGJu3WpyW8vKlOuL3 6CCDHsEzzuaoGw+62MKPImzBdwDJmIl3LdmCY= Received: by 10.210.59.14 with SMTP id h14mr785784eba.29.1231971179817; Wed, 14 Jan 2009 14:12:59 -0800 (PST) Received: by 10.210.61.13 with HTTP; Wed, 14 Jan 2009 14:12:59 -0800 (PST) Message-ID: <3a142e750901141412l10dd16cax6c82903f74350eff@mail.gmail.com> Date: Wed, 14 Jan 2009 23:12:59 +0100 From: "Paul B. Mahol" To: vwe@freebsd.org In-Reply-To: <200901142145.n0ELjR5U065656@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200901142145.n0ELjR5U065656@freefall.freebsd.org> Cc: freebsd-net@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: kern/91859: [ndis] if_ndis does not work with Asus WL-138 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, 14 Jan 2009 22:13:03 -0000 If I'm not mistaken this report is bogus. Correct way to make ndis miniport module is via ndisgen which is shell script for ndiscvt. Report is bogus because OP did not kldload module which have been created with ndiscvt: kldload ndis kldload if_ndis kldload ./created_module_sys.ko -- Paul From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 22:16: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 71D8A106567B for ; Wed, 14 Jan 2009 22:16:39 +0000 (UTC) (envelope-from vwe@freebsd.org) Received: from frontmail.ipactive.de (frontmail.maindns.de [85.214.95.103]) by mx1.freebsd.org (Postfix) with ESMTP id 2D33A8FC0A for ; Wed, 14 Jan 2009 22:16:38 +0000 (UTC) (envelope-from vwe@freebsd.org) Received: from mail.vtec.ipme.de (Q7da7.q.ppp-pool.de [89.53.125.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id 4034A12883F for ; Wed, 14 Jan 2009 23:16:30 +0100 (CET) Received: from [192.168.16.4] (dardanos.sz.vwsoft.com [192.168.16.4]) by mail.vtec.ipme.de (Postfix) with ESMTP id 6B5C02E915 for ; Wed, 14 Jan 2009 23:16:24 +0100 (CET) From: vwe To: freebsd-net@freebsd.org Content-Type: text/plain Date: Wed, 14 Jan 2009 23:16:23 +0100 Message-Id: <1231971383.53310.8.camel@dardanos.sz.vwsoft.com> Mime-Version: 1.0 X-Mailer: Evolution 2.24.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit MailScanner-NULL-Check: 1232576186.67628@J9a+x1oCx3DAR0tv15AeVw X-MailScanner-ID: 6B5C02E915.0511A X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: vwe@freebsd.org X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: vwe@freebsd.org Subject: sorry for the noise ;) 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, 14 Jan 2009 22:16:39 -0000 I'm currently in the process of reassigning a lot of network related PRs from bugs@ to net@. Most of these are old, some are still valid. Please don't hesitate to take a look at them and fix or close them if you think these are outdated and already fixed. Please be sure the number of PRs assigned to net@ will grow further ;) This is in preparation of our next bugathon (not yet officially announced) being held from 2009-01-30 to 2009-02-01. We're going to have a network bugathon then. An official announcement will be send the in a few days. If you're uncomfortable with the number of PRs... well... we'll be happy to see you fixing these issues! :) Thanks Volker From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 22:19:24 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 512BB10657C1; Wed, 14 Jan 2009 22:19:24 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 278458FC0C; Wed, 14 Jan 2009 22:19:24 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0EMJOEZ088105; Wed, 14 Jan 2009 22:19:24 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0EMJNtE088101; Wed, 14 Jan 2009 22:19:23 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 22:19:23 GMT Message-Id: <200901142219.n0EMJNtE088101@freefall.freebsd.org> To: bsdjoe@gmail.com, vwe@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/75407: [an] an(4): no carrier after short time 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, 14 Jan 2009 22:19:24 -0000 Synopsis: [an] an(4): no carrier after short time State-Changed-From-To: feedback->suspended State-Changed-By: vwe State-Changed-When: Wed Jan 14 22:19:07 UTC 2009 State-Changed-Why: mail to submitter bounces http://www.freebsd.org/cgi/query-pr.cgi?pr=75407 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 22:20: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 9BAA410656DD; Wed, 14 Jan 2009 22:20:04 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 717F48FC0A; Wed, 14 Jan 2009 22:20:04 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0EMK4kh088158; Wed, 14 Jan 2009 22:20:04 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0EMK49Q088154; Wed, 14 Jan 2009 22:20:04 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 22:20:04 GMT Message-Id: <200901142220.n0EMK49Q088154@freefall.freebsd.org> To: pbelanger@pt.com, vwe@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/92279: [dc] Core faults everytime I reboot, possible NIC issue. 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, 14 Jan 2009 22:20:05 -0000 Synopsis: [dc] Core faults everytime I reboot, possible NIC issue. State-Changed-From-To: feedback->suspended State-Changed-By: vwe State-Changed-When: Wed Jan 14 22:19:53 UTC 2009 State-Changed-Why: mail to submitter bounces http://www.freebsd.org/cgi/query-pr.cgi?pr=92279 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 22:22:50 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 C83CD10656BD; Wed, 14 Jan 2009 22:22:50 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9E6408FC13; Wed, 14 Jan 2009 22:22:50 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0EMMoS6095101; Wed, 14 Jan 2009 22:22:50 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0EMMoZJ095097; Wed, 14 Jan 2009 22:22:50 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 22:22:50 GMT Message-Id: <200901142222.n0EMMoZJ095097@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/100839: [txp] txp driver inconsistently stops working when the interface is brought down and back up 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, 14 Jan 2009 22:22:51 -0000 Synopsis: [txp] txp driver inconsistently stops working when the interface is brought down and back up Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 22:22:38 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=100839 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 22:24:21 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 63C3C1065672; Wed, 14 Jan 2009 22:24:21 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3A9EE8FC13; Wed, 14 Jan 2009 22:24:21 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0EMOLet095166; Wed, 14 Jan 2009 22:24:21 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0EMOLC6095162; Wed, 14 Jan 2009 22:24:21 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 22:24:21 GMT Message-Id: <200901142224.n0EMOLC6095162@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/103059: [bce] [patch] "Error mapping mbuf into TX chain!" (tentative patch) 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, 14 Jan 2009 22:24:21 -0000 Synopsis: [bce] [patch] "Error mapping mbuf into TX chain!" (tentative patch) Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 22:24:09 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=103059 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 22:24:54 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 106E51065687; Wed, 14 Jan 2009 22:24:54 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D9AB28FC1D; Wed, 14 Jan 2009 22:24:53 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0EMOrkA095212; Wed, 14 Jan 2009 22:24:53 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0EMOrWF095208; Wed, 14 Jan 2009 22:24:53 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 22:24:53 GMT Message-Id: <200901142224.n0EMOrWF095208@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/103135: [ipsec] ipsec with ipfw divert (not NAT) encodes a packet twice breaking PMTUD 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, 14 Jan 2009 22:24:55 -0000 Synopsis: [ipsec] ipsec with ipfw divert (not NAT) encodes a packet twice breaking PMTUD Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 22:24:42 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=103135 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 22:25:49 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 265CD1065677; Wed, 14 Jan 2009 22:25:49 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id F1AFA8FC23; Wed, 14 Jan 2009 22:25:48 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0EMPm4T095270; Wed, 14 Jan 2009 22:25:48 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0EMPmTZ095266; Wed, 14 Jan 2009 22:25:48 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 22:25:48 GMT Message-Id: <200901142225.n0EMPmTZ095266@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/103191: Unpredictable reboot 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, 14 Jan 2009 22:25:49 -0000 Synopsis: Unpredictable reboot Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 22:25:36 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=103191 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 22:27:15 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 0542C106568E; Wed, 14 Jan 2009 22:27:15 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CF6448FC25; Wed, 14 Jan 2009 22:27:14 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0EMREVX095413; Wed, 14 Jan 2009 22:27:14 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0EMRE5W095409; Wed, 14 Jan 2009 22:27:14 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 22:27:14 GMT Message-Id: <200901142227.n0EMRE5W095409@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/104485: [bge] Broadcom BCM5704C: Intermittent on newer chip version: CS0424 P20 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, 14 Jan 2009 22:27:16 -0000 Synopsis: [bge] Broadcom BCM5704C: Intermittent on newer chip version: CS0424 P20 Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 22:27:04 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=104485 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 22:27:58 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 28138106572A; Wed, 14 Jan 2009 22:27:58 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id F2ED38FC2C; Wed, 14 Jan 2009 22:27:57 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0EMRvhr095460; Wed, 14 Jan 2009 22:27:57 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0EMRvWN095456; Wed, 14 Jan 2009 22:27:57 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 22:27:57 GMT Message-Id: <200901142227.n0EMRvWN095456@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/105945: Address can disappear from network interface 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, 14 Jan 2009 22:27:59 -0000 Synopsis: Address can disappear from network interface Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 22:27:47 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=105945 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 22:28:25 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 698A41065781; Wed, 14 Jan 2009 22:28:25 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3F85B8FC1C; Wed, 14 Jan 2009 22:28:25 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0EMSPWU095514; Wed, 14 Jan 2009 22:28:25 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0EMSPhf095510; Wed, 14 Jan 2009 22:28:25 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 22:28:25 GMT Message-Id: <200901142228.n0EMSPhf095510@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/106243: [nve] double fault panic in if_nve.c on high loads 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, 14 Jan 2009 22:28:26 -0000 Synopsis: [nve] double fault panic in if_nve.c on high loads Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 22:28:15 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=106243 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 22:43:00 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 8EC051065670; Wed, 14 Jan 2009 22:43:00 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 648778FC0A; Wed, 14 Jan 2009 22:43:00 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0EMh0FY011306; Wed, 14 Jan 2009 22:43:00 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0EMgxsR011302; Wed, 14 Jan 2009 22:42:59 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 22:42:59 GMT Message-Id: <200901142242.n0EMgxsR011302@freefall.freebsd.org> To: root@net1.cc, vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/89876: [txp] [patch] txp driver doesn't work with latest firmware 03.xxx.xxx 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, 14 Jan 2009 22:43:01 -0000 Synopsis: [txp] [patch] txp driver doesn't work with latest firmware 03.xxx.xxx State-Changed-From-To: open->feedback State-Changed-By: vwe State-Changed-When: Wed Jan 14 22:41:48 UTC 2009 State-Changed-Why: Doichin, the patch isn't available for download anymore, so we're unable to check that issue. Can you please give us the patch so a maintainer can take a look? Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 22:41:48 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=89876 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 23:22:24 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 D2E4B10656CC; Wed, 14 Jan 2009 23:22:24 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A69DC8FC1D; Wed, 14 Jan 2009 23:22:24 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ENMOFK040087; Wed, 14 Jan 2009 23:22:24 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ENMOuR040083; Wed, 14 Jan 2009 23:22:24 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 23:22:24 GMT Message-Id: <200901142322.n0ENMOuR040083@freefall.freebsd.org> To: pi@LF.net, vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/90086: [hang] 5.4p8 on supermicro P8SCT hangs during boot if connected to ethernet 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, 14 Jan 2009 23:22:25 -0000 Synopsis: [hang] 5.4p8 on supermicro P8SCT hangs during boot if connected to ethernet State-Changed-From-To: open->feedback State-Changed-By: vwe State-Changed-When: Wed Jan 14 23:21:21 UTC 2009 State-Changed-Why: Kurt, can you still reproduce the reported problem? sounds like fun! ;) If it's solved, please feed back so we might close that PR. Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 23:21:21 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=90086 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 23:23:36 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 AB38410656CD; Wed, 14 Jan 2009 23:23:36 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8104E8FC18; Wed, 14 Jan 2009 23:23:36 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ENNafV040137; Wed, 14 Jan 2009 23:23:36 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ENNavF040133; Wed, 14 Jan 2009 23:23:36 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 23:23:36 GMT Message-Id: <200901142323.n0ENNavF040133@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/93019: [ppp] ppp and tunX problems: no traffic after restarting ppp 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, 14 Jan 2009 23:23:37 -0000 Synopsis: [ppp] ppp and tunX problems: no traffic after restarting ppp Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 23:23:25 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=93019 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 23:24:58 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 64B541065676; Wed, 14 Jan 2009 23:24:58 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 391CD8FC12; Wed, 14 Jan 2009 23:24:58 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ENOw96040201; Wed, 14 Jan 2009 23:24:58 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ENOvTK040197; Wed, 14 Jan 2009 23:24:57 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 23:24:57 GMT Message-Id: <200901142324.n0ENOvTK040197@freefall.freebsd.org> To: jost2345@users.sourceforge.net, vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/96268: [socket] TCP socket performance drops by 3000% if packets are split at the first byte 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, 14 Jan 2009 23:24:59 -0000 Synopsis: [socket] TCP socket performance drops by 3000% if packets are split at the first byte State-Changed-From-To: open->feedback State-Changed-By: vwe State-Changed-When: Wed Jan 14 23:24:23 UTC 2009 State-Changed-Why: Jost, do you still see this issue with recent releases? Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 23:24:23 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=96268 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 23:26: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 535C510656D7; Wed, 14 Jan 2009 23:26:04 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 297BA8FC1A; Wed, 14 Jan 2009 23:26:04 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ENQ4ES040273; Wed, 14 Jan 2009 23:26:04 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ENQ4CW040269; Wed, 14 Jan 2009 23:26:04 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 23:26:04 GMT Message-Id: <200901142326.n0ENQ4CW040269@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/97306: [netgraph] NG_L2TP locks after connection with failed authentication 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, 14 Jan 2009 23:26:05 -0000 Synopsis: [netgraph] NG_L2TP locks after connection with failed authentication Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 23:25:52 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=97306 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 23:27:08 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 911E51065697; Wed, 14 Jan 2009 23:27:08 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 667DF8FC17; Wed, 14 Jan 2009 23:27:08 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ENR8iC040326; Wed, 14 Jan 2009 23:27:08 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ENR7vM040322; Wed, 14 Jan 2009 23:27:07 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 23:27:07 GMT Message-Id: <200901142327.n0ENR7vM040322@freefall.freebsd.org> To: eddy@ncv.ru, vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: bin/97392: ppp(8) hangs instead terminating 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, 14 Jan 2009 23:27:10 -0000 Synopsis: ppp(8) hangs instead terminating State-Changed-From-To: open->feedback State-Changed-By: vwe State-Changed-When: Wed Jan 14 23:26:38 UTC 2009 State-Changed-Why: Eddy, is this still an issue with recent releases? Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 23:26:38 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=97392 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 23:27:42 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 58E141065703; Wed, 14 Jan 2009 23:27:42 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2ECF28FC29; Wed, 14 Jan 2009 23:27:42 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ENRgvf040373; Wed, 14 Jan 2009 23:27:42 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ENRg5F040369; Wed, 14 Jan 2009 23:27:42 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 23:27:42 GMT Message-Id: <200901142327.n0ENRg5F040369@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: bin/98218: wpa_supplicant(8) blacklist not working 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, 14 Jan 2009 23:27:43 -0000 Synopsis: wpa_supplicant(8) blacklist not working Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 23:27:31 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=98218 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 23:30:25 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 555581065687; Wed, 14 Jan 2009 23:30:25 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2B1118FC08; Wed, 14 Jan 2009 23:30:25 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ENUPJX042987; Wed, 14 Jan 2009 23:30:25 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ENUP14042980; Wed, 14 Jan 2009 23:30:25 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 23:30:25 GMT Message-Id: <200901142330.n0ENUP14042980@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/104751: [netgraph] kernel panic, when getting info about my traffic by module ng_ipacct and oppenning www page in browser 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, 14 Jan 2009 23:30:25 -0000 Synopsis: [netgraph] kernel panic, when getting info about my traffic by module ng_ipacct and oppenning www page in browser Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 23:30:06 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=104751 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 23:31:38 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 12642106566B; Wed, 14 Jan 2009 23:31:38 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DD58F8FC14; Wed, 14 Jan 2009 23:31:37 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ENVbVD048407; Wed, 14 Jan 2009 23:31:37 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ENVb4v048403; Wed, 14 Jan 2009 23:31:37 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 23:31:37 GMT Message-Id: <200901142331.n0ENVb4v048403@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/105348: [ath] ath device stopps TX 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, 14 Jan 2009 23:31:39 -0000 Synopsis: [ath] ath device stopps TX Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 23:31:27 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=105348 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 23:32:36 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 5FF7E1065675; Wed, 14 Jan 2009 23:32:36 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 35E708FC0C; Wed, 14 Jan 2009 23:32:36 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ENWaOt048693; Wed, 14 Jan 2009 23:32:36 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ENWaqI048687; Wed, 14 Jan 2009 23:32:36 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 23:32:36 GMT Message-Id: <200901142332.n0ENWaqI048687@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/106974: [bge] packet loose and linkup problem 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, 14 Jan 2009 23:32:37 -0000 Synopsis: [bge] packet loose and linkup problem Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 23:32:25 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=106974 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 23:33: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 2A2C8106568B; Wed, 14 Jan 2009 23:33:02 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 000F78FC14; Wed, 14 Jan 2009 23:33:01 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ENX1bw049044; Wed, 14 Jan 2009 23:33:01 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ENX1CK049040; Wed, 14 Jan 2009 23:33:01 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 23:33:01 GMT Message-Id: <200901142333.n0ENX1CK049040@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org 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 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2009 23:33:03 -0000 Synopsis: [bce] bce driver link negotiation is faulty Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 23:32:52 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=107850 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 23:33:54 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 47393106564A; Wed, 14 Jan 2009 23:33:54 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1E3AC8FC22; Wed, 14 Jan 2009 23:33:54 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ENXsfl049320; Wed, 14 Jan 2009 23:33:54 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ENXr93049316; Wed, 14 Jan 2009 23:33:53 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 23:33:53 GMT Message-Id: <200901142333.n0ENXr93049316@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/109251: [re] [patch] if_re cardbus card won't attach 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, 14 Jan 2009 23:33:54 -0000 Synopsis: [re] [patch] if_re cardbus card won't attach Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 23:33:43 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=109251 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 23:34:47 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 4BBDA1065675; Wed, 14 Jan 2009 23:34:47 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2283B8FC17; Wed, 14 Jan 2009 23:34:46 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ENYkke049368; Wed, 14 Jan 2009 23:34:46 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ENYkmB049364; Wed, 14 Jan 2009 23:34:46 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 23:34:46 GMT Message-Id: <200901142334.n0ENYkmB049364@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/110140: [ipw] ipw fails under load 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, 14 Jan 2009 23:34:48 -0000 Synopsis: [ipw] ipw fails under load Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 23:34:36 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=110140 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 23:35:19 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 0DAF410656CB; Wed, 14 Jan 2009 23:35:19 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D98828FC24; Wed, 14 Jan 2009 23:35:18 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ENZIU4049417; Wed, 14 Jan 2009 23:35:18 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ENZIKe049413; Wed, 14 Jan 2009 23:35:18 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 23:35:18 GMT Message-Id: <200901142335.n0ENZIKe049413@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/111457: [ral] ral(4) freeze 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, 14 Jan 2009 23:35:19 -0000 Synopsis: [ral] ral(4) freeze Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 23:35:08 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=111457 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 23:35:43 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 9BF6F1065676; Wed, 14 Jan 2009 23:35:43 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 722EB8FC18; Wed, 14 Jan 2009 23:35:43 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ENZhPf049463; Wed, 14 Jan 2009 23:35:43 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ENZhOH049459; Wed, 14 Jan 2009 23:35:43 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 23:35:43 GMT Message-Id: <200901142335.n0ENZhOH049459@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/112570: [bge] packet loss with bge driver on BCM5704 chipset 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, 14 Jan 2009 23:35:44 -0000 Synopsis: [bge] packet loss with bge driver on BCM5704 chipset Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 23:35:33 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=112570 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 23:36:37 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 6E42E106566B; Wed, 14 Jan 2009 23:36:37 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 44B1C8FC18; Wed, 14 Jan 2009 23:36:37 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ENab1G049524; Wed, 14 Jan 2009 23:36:37 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ENabgJ049520; Wed, 14 Jan 2009 23:36:37 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 23:36:37 GMT Message-Id: <200901142336.n0ENabgJ049520@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/113895: [xl] xl0 fails on 6.2-RELEASE but worked fine on 5.5-RELEASE [regression] 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, 14 Jan 2009 23:36:38 -0000 Synopsis: [xl] xl0 fails on 6.2-RELEASE but worked fine on 5.5-RELEASE [regression] Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 23:36:28 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=113895 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 23:37:47 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 D8A1F1065704; Wed, 14 Jan 2009 23:37:47 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AD7258FC1F; Wed, 14 Jan 2009 23:37:47 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ENblGl049574; Wed, 14 Jan 2009 23:37:47 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ENblYH049570; Wed, 14 Jan 2009 23:37:47 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 23:37:47 GMT Message-Id: <200901142337.n0ENblYH049570@freefall.freebsd.org> To: stefano.guidi@it.transport.bombardier.com, vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/114899: [bge] bge0: watchdog timeout -- resetting 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, 14 Jan 2009 23:37:48 -0000 Synopsis: [bge] bge0: watchdog timeout -- resetting State-Changed-From-To: open->feedback State-Changed-By: vwe State-Changed-When: Wed Jan 14 23:37:14 UTC 2009 State-Changed-Why: Stefano, do you still experience that issue with recent releases? Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 23:37:14 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=114899 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 23:43:53 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 D474710656CE; Wed, 14 Jan 2009 23:43:53 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AA09A8FC13; Wed, 14 Jan 2009 23:43:53 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ENhrkk056499; Wed, 14 Jan 2009 23:43:53 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ENhrg5056495; Wed, 14 Jan 2009 23:43:53 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 23:43:53 GMT Message-Id: <200901142343.n0ENhrg5056495@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/116444: [ath] Atheros 5005G (AR5212) miniPCI: unable to attach device hal status 3 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, 14 Jan 2009 23:43:55 -0000 Synopsis: [ath] Atheros 5005G (AR5212) miniPCI: unable to attach device hal status 3 Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 23:43:43 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=116444 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 23:51:11 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 0210D1065670; Wed, 14 Jan 2009 23:51:11 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CC39D8FC1A; Wed, 14 Jan 2009 23:51:10 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ENpAx2063396; Wed, 14 Jan 2009 23:51:10 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ENpA2k063392; Wed, 14 Jan 2009 23:51:10 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 23:51:10 GMT Message-Id: <200901142351.n0ENpA2k063392@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/118897: [bfe] Kernel Panic acquiring IP address from DHCP server on newly enabled netcard 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, 14 Jan 2009 23:51:11 -0000 Synopsis: [bfe] Kernel Panic acquiring IP address from DHCP server on newly enabled netcard Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Wed Jan 14 23:51:00 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=118897 From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 23:56:26 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 0DD7A1065670; Wed, 14 Jan 2009 23:56:26 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D83DA8FC0C; Wed, 14 Jan 2009 23:56:25 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0ENuPir063486; Wed, 14 Jan 2009 23:56:25 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0ENuPw1063482; Wed, 14 Jan 2009 23:56:25 GMT (envelope-from vwe) Date: Wed, 14 Jan 2009 23:56:25 GMT Message-Id: <200901142356.n0ENuPw1063482@freefall.freebsd.org> To: pi@LF.net, vwe@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/90086: [hang] 5.4p8 on supermicro P8SCT hangs during boot if connected to ethernet 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, 14 Jan 2009 23:56:26 -0000 Synopsis: [hang] 5.4p8 on supermicro P8SCT hangs during boot if connected to ethernet State-Changed-From-To: feedback->suspended State-Changed-By: vwe State-Changed-When: Wed Jan 14 23:56:09 UTC 2009 State-Changed-Why: mail to submitter bounces http://www.freebsd.org/cgi/query-pr.cgi?pr=90086 From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 00: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 89A93106566B for ; Thu, 15 Jan 2009 00: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 5CE518FC0A for ; Thu, 15 Jan 2009 00:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0F0U3ar085522 for ; Thu, 15 Jan 2009 00:30:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0F0U3kb085521; Thu, 15 Jan 2009 00:30:03 GMT (envelope-from gnats) Date: Thu, 15 Jan 2009 00:30:03 GMT Message-Id: <200901150030.n0F0U3kb085521@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: "Daniel O'Connor" Cc: Subject: Re: kern/81644: [vge] vge(4) does not work properly when loaded as a KLD X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel O'Connor List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2009 00:30:04 -0000 The following reply was made to PR kern/81644; it has been noted by GNATS. From: "Daniel O'Connor" To: bug-followup@freebsd.org, doconnor@gsoft.com.au Cc: Subject: Re: kern/81644: [vge] vge(4) does not work properly when loaded as a KLD Date: Thu, 15 Jan 2009 10:44:19 +1030 I don't have any test hardware handy anymore, sorry. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 01: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 593901065672 for ; Thu, 15 Jan 2009 01: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 463188FC16 for ; Thu, 15 Jan 2009 01:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0F1e2fu039596 for ; Thu, 15 Jan 2009 01: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 n0F1e2Pe039595; Thu, 15 Jan 2009 01:40:02 GMT (envelope-from gnats) Date: Thu, 15 Jan 2009 01:40:02 GMT Message-Id: <200901150140.n0F1e2Pe039595@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Tom Judge Cc: Subject: Re: kern/96268: [socket] TCP socket performance drops by 3000% if packets are split at the first byte 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: Thu, 15 Jan 2009 01:40:03 -0000 The following reply was made to PR kern/96268; it has been noted by GNATS. From: Tom Judge To: bug-followup@FreeBSD.org, jost2345@users.sourceforge.net Cc: Subject: Re: kern/96268: [socket] TCP socket performance drops by 3000% if packets are split at the first byte Date: Wed, 14 Jan 2009 19:31:11 -0600 I have seen this issue on 7.0-RELEASE. It seems to be related to the nagle algorithm being enable by default on connections on the loop back interface. One application level work around is to set the TCP_NODELAY option on the socket so that the nagle algorithem is disabled. This bug affects users of php java bridge as newer release talk to a JVM over a tcp socket bound to localhost, and the typical packets passing back and forward are very small. It is also possible to reproduce this bug using PHP 5. I can attach test scripts if required. Tom From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 01: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 1C001106566B for ; Thu, 15 Jan 2009 01: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 E3DB08FC0A for ; Thu, 15 Jan 2009 01:40:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0F1e4Vg039627 for ; Thu, 15 Jan 2009 01:40:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0F1e47H039626; Thu, 15 Jan 2009 01:40:04 GMT (envelope-from gnats) Date: Thu, 15 Jan 2009 01:40:04 GMT Message-Id: <200901150140.n0F1e47H039626@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Tom Judge Cc: Subject: Re: kern/87194: [fxp] fxp(4) promiscuous mode seems to corrupt hw-csum 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: Thu, 15 Jan 2009 01:40:05 -0000 The following reply was made to PR kern/87194; it has been noted by GNATS. From: Tom Judge To: bug-followup@FreeBSD.org, green@freebsd.org Cc: Subject: Re: kern/87194: [fxp] fxp(4) promiscuous mode seems to corrupt hw-csum Date: Wed, 14 Jan 2009 19:22:17 -0600 Can you add the output of ifconfig bridge0 as if_bridge should downgrade the active hardware features to match the other members in the bridge. Also have you tried "ifconfig fxp0 -txsum -rxsum" to disable the hardware checksumming? I have a number of bridges with all fxp members working fine under 6.2 and 7.0 do you still have these problems on a newer release than 6.0? Tom From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 02:08: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 8D7981065704; Thu, 15 Jan 2009 02:08:18 +0000 (UTC) (envelope-from yongari@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 610DF8FC25; Thu, 15 Jan 2009 02:08:18 +0000 (UTC) (envelope-from yongari@FreeBSD.org) Received: from freefall.freebsd.org (yongari@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0F28Ibf060640; Thu, 15 Jan 2009 02:08:18 GMT (envelope-from yongari@freefall.freebsd.org) Received: (from yongari@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0F28Hud060636; Thu, 15 Jan 2009 02:08:17 GMT (envelope-from yongari) Date: Thu, 15 Jan 2009 02:08:17 GMT Message-Id: <200901150208.n0F28Hud060636@freefall.freebsd.org> To: sonicy@otenet.gr, yongari@FreeBSD.org, freebsd-net@FreeBSD.org, yongari@FreeBSD.org From: yongari@FreeBSD.org Cc: Subject: Re: kern/118897: [bfe] Kernel Panic acquiring IP address from DHCP server on newly enabled netcard 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, 15 Jan 2009 02:08:18 -0000 Synopsis: [bfe] Kernel Panic acquiring IP address from DHCP server on newly enabled netcard State-Changed-From-To: open->feedback State-Changed-By: yongari State-Changed-When: Thu Jan 15 02:06:33 UTC 2009 State-Changed-Why: I think all known bugs in bfe(4) were fixed. Can you still reproduce the issue on 6.4-RELEASE or 7.1-RELEASE? Responsible-Changed-From-To: freebsd-net->yongari Responsible-Changed-By: yongari Responsible-Changed-When: Thu Jan 15 02:06:33 UTC 2009 Responsible-Changed-Why: Grab. http://www.freebsd.org/cgi/query-pr.cgi?pr=118897 From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 02:14:43 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 B41221065672; Thu, 15 Jan 2009 02:14:43 +0000 (UTC) (envelope-from yongari@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A1D238FC16; Thu, 15 Jan 2009 02:14:43 +0000 (UTC) (envelope-from yongari@FreeBSD.org) Received: from freefall.freebsd.org (yongari@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0F2EhLa068691; Thu, 15 Jan 2009 02:14:43 GMT (envelope-from yongari@freefall.freebsd.org) Received: (from yongari@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0F2EhRi068687; Thu, 15 Jan 2009 02:14:43 GMT (envelope-from yongari) Date: Thu, 15 Jan 2009 02:14:43 GMT Message-Id: <200901150214.n0F2EhRi068687@freefall.freebsd.org> To: dan@mail.neosystem.cz, yongari@FreeBSD.org, freebsd-net@FreeBSD.org, yongari@FreeBSD.org From: yongari@FreeBSD.org Cc: Subject: Re: kern/92675: [fxp] [patch] fxp(4) unable to recover from occasional receiver unit allocation failure 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, 15 Jan 2009 02:14:44 -0000 Synopsis: [fxp] [patch] fxp(4) unable to recover from occasional receiver unit allocation failure State-Changed-From-To: open->feedback State-Changed-By: yongari State-Changed-When: Thu Jan 15 02:13:36 UTC 2009 State-Changed-Why: fxp(4) in CURRENT has more robust code to cope with resource exhaustion. I think you can use fxp(4) in CURRENT without problems on 7.1-RELEASE or stable/7. Would you give it try? Also fxp(4) in HEAD supports Rx checksum offloading for 82559 so you may get slightly better performance. Responsible-Changed-From-To: freebsd-net->yongari Responsible-Changed-By: yongari Responsible-Changed-When: Thu Jan 15 02:13:36 UTC 2009 Responsible-Changed-Why: Grab. http://www.freebsd.org/cgi/query-pr.cgi?pr=92675 From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 04:32: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 4D19B1065674 for ; Thu, 15 Jan 2009 04:32:32 +0000 (UTC) (envelope-from dimitar.vassilev@gmail.com) Received: from mail-gx0-f21.google.com (mail-gx0-f21.google.com [209.85.217.21]) by mx1.freebsd.org (Postfix) with ESMTP id 9E6108FC26 for ; Thu, 15 Jan 2009 04:32:31 +0000 (UTC) (envelope-from dimitar.vassilev@gmail.com) Received: by gxk14 with SMTP id 14so1001998gxk.19 for ; Wed, 14 Jan 2009 20:32:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=HPdQYgbTVRJ4bq9HHWuUM+DQEC/ZyqgJT7SjQeqg/1c=; b=Q4MsNxBjlg7Hf7G9/XQxCdshSV927UVAUeNLKFD2pCzyieVP1pngPgzChSRvp3v2x1 XP7yJNUQBJz6VoiFkgCyMgEUplOYcuX356p0Y/rGhs0/DmpBG/YLM/3iu9BRSB6lCWKo ewJjRsNreFzKef2mWB4ZKg916ul4jOOI2n2NM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=XI6CP2nRd4IeCrDk+OQOhqoCu8y6FwNasSsyRwejf+xQQ0o4xFQq4xz/C+SeuxftI+ VWwuKbGnEgM+VSkdWdPC1Qod+IppMrC6PXN96Nbn4+WFPGFFOi1iNydpzoPpjNQ/o8oO FEHGnVIqqMY9YMuZTOY7nfDNp9G5zZRju4z3A= Received: by 10.151.47.7 with SMTP id z7mr3205001ybj.167.1231993951010; Wed, 14 Jan 2009 20:32:31 -0800 (PST) Received: by 10.151.133.7 with HTTP; Wed, 14 Jan 2009 20:32:30 -0800 (PST) Message-ID: <59adc1a0901142032u5c6bb08y5c8768aa43d1d56a@mail.gmail.com> Date: Thu, 15 Jan 2009 06:32:30 +0200 From: "Dimitar Vasilev" To: "Julian Elischer" In-Reply-To: <496CCFBF.3010008@elischer.org> MIME-Version: 1.0 References: <59adc1a0901122114v15efa47ahba8beef6ace4ddb0@mail.gmail.com> <496CCFBF.3010008@elischer.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re: setfib+pf 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, 15 Jan 2009 04:32:32 -0000 > > >> >> I'd much appreciate if someone thinks with me for the best options of >> using >> the setfib features along with pf. >> > > I know setfib but I don't know pf unfortunately.. I use ipfw > (which is why ipfw has fib support :-) > > > possibly Max Lair may know both.. > > Hi Julian, Could you sched some light on the ipfw and setfib as an example. Seems the person you're referring to is busy. The rest I will figure out on my own. If there are results - I will share back. Thanks, Dimitar From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 06:04: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 BB16C106564A for ; Thu, 15 Jan 2009 06:04:43 +0000 (UTC) (envelope-from prvs=julian=2597c6704@elischer.org) Received: from smtp-outbound.ironport.com (smtp-outbound.ironport.com [63.251.108.112]) by mx1.freebsd.org (Postfix) with ESMTP id A6DC78FC1A for ; Thu, 15 Jan 2009 06:04:43 +0000 (UTC) (envelope-from prvs=julian=2597c6704@elischer.org) Received: from unknown (HELO julian-mac.elischer.org) ([10.251.60.222]) by smtp-outbound.ironport.com with ESMTP; 14 Jan 2009 21:36:08 -0800 Message-ID: <496ECB47.4060005@elischer.org> Date: Wed, 14 Jan 2009 21:36:07 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: Dimitar Vasilev References: <59adc1a0901122114v15efa47ahba8beef6ace4ddb0@mail.gmail.com> <496CCFBF.3010008@elischer.org> <59adc1a0901142032u5c6bb08y5c8768aa43d1d56a@mail.gmail.com> In-Reply-To: <59adc1a0901142032u5c6bb08y5c8768aa43d1d56a@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: setfib+pf 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, 15 Jan 2009 06:04:44 -0000 Dimitar Vasilev wrote: > > > I'd much appreciate if someone thinks with me for the best > options of using > the setfib features along with pf. > > > I know setfib but I don't know pf unfortunately.. I use ipfw > (which is why ipfw has fib support :-) > > > possibly Max Lair may know both.. > > Hi Julian, > Could you sched some light on the ipfw and setfib as an example. Seems > the person you're referring to is busy. The rest I will figure out on my > own. If there are results - I will share back. > Thanks, > Dimitar well, you need to tell me a little more about what you want to do. From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 06:56:15 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 2D4141065670; Thu, 15 Jan 2009 06:56:15 +0000 (UTC) (envelope-from sonicy@otenet.gr) Received: from aiolos.otenet.gr (aiolos.otenet.gr [83.235.67.30]) by mx1.freebsd.org (Postfix) with ESMTP id 4A5BF8FC0A; Thu, 15 Jan 2009 06:56:14 +0000 (UTC) (envelope-from sonicy@otenet.gr) Received: from atlantis.dyndns.org (athedsl-4527830.home.otenet.gr [94.70.226.222]) by aiolos.otenet.gr (8.13.8/8.13.8/Debian-3) with ESMTP id n0F6CDbC021318; Thu, 15 Jan 2009 08:12:13 +0200 Message-ID: <496ED3BD.3040906@otenet.gr> Date: Thu, 15 Jan 2009 08:12:13 +0200 From: Manolis Kiagias User-Agent: Thunderbird 2.0.0.17 (X11/20081011) MIME-Version: 1.0 To: yongari@FreeBSD.org References: <200901150208.n0F28Hud060636@freefall.freebsd.org> In-Reply-To: <200901150208.n0F28Hud060636@freefall.freebsd.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-7 Content-Transfer-Encoding: 7bit Cc: freebsd-net@FreeBSD.org Subject: Re: kern/118897: [bfe] Kernel Panic acquiring IP address from DHCP server on newly enabled netcard 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, 15 Jan 2009 06:56:15 -0000 yongari@FreeBSD.org wrote: > Synopsis: [bfe] Kernel Panic acquiring IP address from DHCP server on newly enabled netcard > > State-Changed-From-To: open->feedback > State-Changed-By: yongari > State-Changed-When: Thu Jan 15 02:06:33 UTC 2009 > State-Changed-Why: > I think all known bugs in bfe(4) were fixed. > Can you still reproduce the issue on 6.4-RELEASE or 7.1-RELEASE? > > > Responsible-Changed-From-To: freebsd-net->yongari > Responsible-Changed-By: yongari > Responsible-Changed-When: Thu Jan 15 02:06:33 UTC 2009 > Responsible-Changed-Why: > Grab. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=118897 > > > I'll give it a try this afternoon and let you know. From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 08:26: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 7D9421065679; Thu, 15 Jan 2009 08:26:33 +0000 (UTC) (envelope-from fazaeli@sepehrs.com) Received: from sepehrs.com (www.sepehrs.com [213.217.59.98]) by mx1.freebsd.org (Postfix) with ESMTP id AA6828FC0A; Thu, 15 Jan 2009 08:26:32 +0000 (UTC) (envelope-from fazaeli@sepehrs.com) Received: from [192.168.1.180] ([192.168.1.180]) by sepehrs.com (8.13.6/8.13.6) with ESMTP id n0F8gDh3056576; Thu, 15 Jan 2009 12:12:14 +0330 (IRST) (envelope-from fazaeli@sepehrs.com) Message-ID: <496EF30E.4010304@sepehrs.com> Date: Thu, 15 Jan 2009 11:55:50 +0330 From: "H.fazaeli" User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) To: Yony Yossef References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> <496E11B7.3010608@sepehrs.com> <000b01c9768e$745aa160$220f000a@mtl.com> In-Reply-To: <000b01c9768e$745aa160$220f000a@mtl.com> Content-Transfer-Encoding: 7bit X-Sepehr-MailScanner-Information: Please contact the ISP for more information X-Sepehr-MailScanner: Found to be clean X-Sepehr-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.901, required 5, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60, HTML_40_50 0.50, HTML_MESSAGE 0.00, MIME_HTML_ONLY 0.00) X-MailScanner-From: fazaeli@sepehrs.com X-Spam-Status: No MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org Subject: Re: howto determine network device unit number? device.hints? 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, 15 Jan 2009 08:26:34 -0000 for example, say you have 2 interface em0 and em1 which you like to swap their minor numbers: ifconfig em0 name tmp ifconfig em1 name em0 ifconfig em0 name em1 or to assign cisco-like names to you interfaces: ifconfig xl0 name fastEthernet0 ifconfig em0 name gigaEthernet0 ifconfig fastEthernet0 192.168.1.0/24 Yony Yossef wrote: -----Original Message----- From: H.fazaeli [[1]mailto:fazaeli@sepehrs.com] Sent: Wednesday, January 14, 2009 6:24 PM To: Yony Yossef Cc: [2]freebsd-net@freebsd.org; [3]freebsd-questions@freebsd.org; Eitan Shefi; Oleg Kats; Liran Liss Subject: Re: howto determine network device unit number? device.hints? you may not change unit numbers as they are strictly controlled by kernel. However, on freebsd 5.3+, you may use 'ifconfig name ' to achieve the same affect Sorry, I don't understand the usage of ifconfig you suggested and the effect it will cause. Can you please explain it? Yony Yony Yossef wrote: Hi, I would like to determine the unit number of my network cards, e.g. make the device on pci0:16 be assigned every time with unit number 0 and pci0:19 with unit number 1. Is it done by /boot/device.hints? if so, how? My cards are: mtnic0@pci0:19:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 rev=0xa0 hdr=0x00 mtnic1@pci0:16:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 rev=0xa0 hdr=0x00 So I've tried: hint.mtnic.0.at="pci0:16" hint.mtnic.1.at="pci0:19" but it doesn't work. They keep switching arbitrarily. I'm using FreeBSD 7.0. Thanks Yony _______________________________________________ [4]freebsd-questions@freebsd.org mailing list [5]http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [6]"freebsd-questions-unsubscribe@freebsd.org" -- Best regards. Hooman Fazaeli [7] Sepehr S. T. Co. Ltd. Web: [8]http://www.sepehrs.com Tel: (9821)88975701-2 Fax: (9821)88983352 _______________________________________________ [9]freebsd-net@freebsd.org mailing list [10]http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to [11]"freebsd-net-unsubscribe@freebsd.org" -- Best regards. Hooman Fazaeli [12] Sepehr S. T. Co. Ltd. Web: [13]http://www.sepehrs.com Tel: (9821)88975701-2 Fax: (9821)88983352 References 1. mailto:fazaeli@sepehrs.com 2. mailto:freebsd-net@freebsd.org 3. mailto:freebsd-questions@freebsd.org 4. mailto:freebsd-questions@freebsd.org 5. http://lists.freebsd.org/mailman/listinfo/freebsd-questions 6. mailto:freebsd-questions-unsubscribe@freebsd.org 7. mailto:hf@sepehrs.com 8. http://www.sepehrs.com/ 9. mailto:freebsd-net@freebsd.org 10. http://lists.freebsd.org/mailman/listinfo/freebsd-net 11. mailto:freebsd-net-unsubscribe@freebsd.org 12. mailto:hf@sepehrs.com 13. http://www.sepehrs.com/ From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 08:37: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 9F0791065674; Thu, 15 Jan 2009 08:37:45 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: from mail-ew0-f30.google.com (mail-ew0-f30.google.com [209.85.219.30]) by mx1.freebsd.org (Postfix) with ESMTP id C8D1F8FC18; Thu, 15 Jan 2009 08:37:44 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: by ewy11 with SMTP id 11so325010ewy.19 for ; Thu, 15 Jan 2009 00:37:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references:subject :date:message-id:mime-version:content-type:x-mailer:thread-index :x-mimeole:in-reply-to; bh=PZ9EBLYFGouhBMz06Mx+RaxE3WmOuLcUtp5gmfF6PyY=; b=aZafvr8VywiOFVk1WQ2fi3kRHEIuxzsd4pqq9lN/y0XW7GyH5dqGsQboHWV82P2iCB viE6/qESTu494/TSA0eOhfL5EEUDKyvE7PF0fq9T/gKGQyVIRhCRW+wN4du02eYGisZo i67vS1U7okH45He8NhERgwSmbKU5x9OIuv/08= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:x-mimeole:in-reply-to; b=YIOBNOPjr8/y6cvZZxcdztiVdFvPz1kOoSARFoi15o25/Q3zltjRVnjPV5d7De3QGa Itj6SpANK55Kd0FIaEw9mVZTxTn70ZjuyVMsyF9u1t6FtkKoqfycGVQ6ISUcBAGO1iip MQW7KzZFJRbmied29GxsEWQSWBhDxXXeamuRk= Received: by 10.67.103.11 with SMTP id f11mr3090400ugm.12.1232008662961; Thu, 15 Jan 2009 00:37:42 -0800 (PST) Received: from mtllpt03 (DSL212-235-20-133.bb.netvision.net.il [212.235.20.133]) by mx.google.com with ESMTPS id 27sm1162803ugp.25.2009.01.15.00.37.02 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 15 Jan 2009 00:37:41 -0800 (PST) From: "Yony Yossef" To: "'H.fazaeli'" References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> <496E11B7.3010608@sepehrs.com> <000b01c9768e$745aa160$220f000a@mtl.com> <496EF30E.4010304@sepehrs.com> Date: Thu, 15 Jan 2009 10:37:00 +0200 Message-ID: <000c01c976ec$87e040b0$220f000a@mtl.com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acl26wFlKPeQCw3YQj23tbj6NbKhDAAANzPg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 In-Reply-To: <496EF30E.4010304@sepehrs.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Eitan Shefi , freebsd-net@freebsd.org, Oleg Kats , freebsd-questions@freebsd.org, Liran Liss Subject: RE: howto determine network device unit number? device.hints? 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, 15 Jan 2009 08:37:46 -0000 Thanks for the explanation. So there's no way to determine this in advance.. I must build a script that contains my own mapping between MAC addresses and the wanted interface names and run it after each driver load, rename the interfaces if necessary. It seems quite wrong, don't you agree? And how come the unit number is given an arbitrary value? Is there a good reason for that? Yony _____ From: H.fazaeli [mailto:fazaeli@sepehrs.com] Sent: Thursday, January 15, 2009 10:26 AM To: Yony Yossef Cc: freebsd-net@freebsd.org; freebsd-questions@freebsd.org Subject: Re: howto determine network device unit number? device.hints? for example, say you have 2 interface em0 and em1 which you like to swap their minor numbers: ifconfig em0 name tmp ifconfig em1 name em0 ifconfig em0 name em1 or to assign cisco-like names to you interfaces: ifconfig xl0 name fastEthernet0 ifconfig em0 name gigaEthernet0 ifconfig fastEthernet0 192.168.1.0/24 Yony Yossef wrote: -----Original Message----- From: H.fazaeli [mailto:fazaeli@sepehrs.com] Sent: Wednesday, January 14, 2009 6:24 PM To: Yony Yossef Cc: freebsd-net@freebsd.org; freebsd-questions@freebsd.org; Eitan Shefi; Oleg Kats; Liran Liss Subject: Re: howto determine network device unit number? device.hints? you may not change unit numbers as they are strictly controlled by kernel. However, on freebsd 5.3+, you may use 'ifconfig name ' to achieve the same affect Sorry, I don't understand the usage of ifconfig you suggested and the effect it will cause. Can you please explain it? Yony Yony Yossef wrote: Hi, I would like to determine the unit number of my network cards, e.g. make the device on pci0:16 be assigned every time with unit number 0 and pci0:19 with unit number 1. Is it done by /boot/device.hints? if so, how? My cards are: mtnic0@pci0:19:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 rev=0xa0 hdr=0x00 mtnic1@pci0:16:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 rev=0xa0 hdr=0x00 So I've tried: hint.mtnic.0.at="pci0:16" hint.mtnic.1.at="pci0:19" but it doesn't work. They keep switching arbitrarily. I'm using FreeBSD 7.0. Thanks Yony _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" -- Best regards. Hooman Fazaeli Sepehr S. T. Co. Ltd. Web: http://www.sepehrs.com Tel: (9821)88975701-2 Fax: (9821)88983352 _______________________________________________ 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" -- Best regards. Hooman Fazaeli Sepehr S. T. Co. Ltd. Web: http://www.sepehrs.com Tel: (9821)88975701-2 Fax: (9821)88983352 From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 08:48: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 68DA7106566B for ; Thu, 15 Jan 2009 08:48:11 +0000 (UTC) (envelope-from prvs=julian=2597c6704@elischer.org) Received: from smtp-outbound.ironport.com (smtp-outbound.ironport.com [63.251.108.112]) by mx1.freebsd.org (Postfix) with ESMTP id 4D35C8FC0A for ; Thu, 15 Jan 2009 08:48:11 +0000 (UTC) (envelope-from prvs=julian=2597c6704@elischer.org) Received: from unknown (HELO julian-mac.elischer.org) ([10.251.60.222]) by smtp-outbound.ironport.com with ESMTP; 15 Jan 2009 00:48:11 -0800 Message-ID: <496EF849.7040909@elischer.org> Date: Thu, 15 Jan 2009 00:48:09 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: Yony Yossef References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> <496E11B7.3010608@sepehrs.com> <000b01c9768e$745aa160$220f000a@mtl.com> <496EF30E.4010304@sepehrs.com> <000c01c976ec$87e040b0$220f000a@mtl.com> In-Reply-To: <000c01c976ec$87e040b0$220f000a@mtl.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Liran Liss , freebsd-net@freebsd.org, Oleg Kats , "'H.fazaeli'" , Eitan Shefi , freebsd-questions@freebsd.org Subject: Re: howto determine network device unit number? device.hints? 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, 15 Jan 2009 08:48:11 -0000 Yony Yossef wrote: > Thanks for the explanation. > > So there's no way to determine this in advance.. > I must build a script that contains my own mapping between MAC addresses and > the wanted interface names and run it after each driver load, rename the > interfaces if necessary. you must agree it's flexible. > It seems quite wrong, don't you agree? > > And how come the unit number is given an arbitrary value? Is there a good > reason for that? device discovery depends on what slot you put the card into. so if you move it, it's number may change. also, how do you identify the particular card you want to have a particular unit number? considering it may move (and for example USB network interfaces WILL move if you add a keyboard or any other device.. also to do as you want would take 2 passes. first one to find the numbers needed and another to do what's left. > > Yony > > > > _____ > > From: H.fazaeli [mailto:fazaeli@sepehrs.com] > Sent: Thursday, January 15, 2009 10:26 AM > To: Yony Yossef > Cc: freebsd-net@freebsd.org; freebsd-questions@freebsd.org > Subject: Re: howto determine network device unit number? device.hints? > > > > for example, say you have 2 interface em0 and em1 which > you like to swap their minor numbers: > > ifconfig em0 name tmp > ifconfig em1 name em0 > ifconfig em0 name em1 > > or to assign cisco-like names to you interfaces: > > ifconfig xl0 name fastEthernet0 > ifconfig em0 name gigaEthernet0 > ifconfig fastEthernet0 192.168.1.0/24 > > > Yony Yossef wrote: > > > > > > > > -----Original Message----- > > From: H.fazaeli [mailto:fazaeli@sepehrs.com] > > Sent: Wednesday, January 14, 2009 6:24 PM > > To: Yony Yossef > > Cc: freebsd-net@freebsd.org; freebsd-questions@freebsd.org; > > Eitan Shefi; Oleg Kats; Liran Liss > > Subject: Re: howto determine network device unit number? device.hints? > > > > > > you may not change unit numbers as they are strictly > > controlled by kernel. > > However, on freebsd 5.3+, you may use 'ifconfig name ' > > to achieve the same affect > > > > > > > > Sorry, I don't understand the usage of ifconfig you suggested and the effect > > it will cause. > > Can you please explain it? > > Yony > > > > > > Yony Yossef wrote: > > > > Hi, > > > > I would like to determine the unit number of my network cards, e.g. > > make the device on pci0:16 be assigned every time with unit > > > > number 0 > > > > and pci0:19 with unit number 1. > > > > Is it done by /boot/device.hints? > > if so, how? > > > > My cards are: > > > > mtnic0@pci0:19:0:0: class=0x020000 card=0x001715b3 > > > > chip=0x636815b3 > > > > rev=0xa0 hdr=0x00 > > mtnic1@pci0:16:0:0: class=0x020000 card=0x001715b3 > > > > chip=0x636815b3 > > > > rev=0xa0 hdr=0x00 > > > > So I've tried: > > > > hint.mtnic.0.at="pci0:16" > > hint.mtnic.1.at="pci0:19" > > > > but it doesn't work. They keep switching arbitrarily. > > I'm using FreeBSD 7.0. > > > > Thanks > > Yony > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > > > > "freebsd-questions-unsubscribe@freebsd.org" > > > > > > > > From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 09:25: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 5AE681065670; Thu, 15 Jan 2009 09:25:53 +0000 (UTC) (envelope-from root@net1.cc) Received: from server1.net1.cc (server1.net1.cc [213.137.48.2]) by mx1.freebsd.org (Postfix) with ESMTP id 0F1428FC21; Thu, 15 Jan 2009 09:25:52 +0000 (UTC) (envelope-from root@net1.cc) Received: from support.net1.cc ([213.137.58.124]) by server1.net1.cc with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LNO6F-00018H-GC; Thu, 15 Jan 2009 11:01:15 +0200 Message-ID: <496EFB53.80609@net1.cc> Date: Thu, 15 Jan 2009 11:01:07 +0200 From: NetOne - Doichin Dokov User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: vwe@FreeBSD.org References: <200901142242.n0EMgxsR011302@freefall.freebsd.org> In-Reply-To: <200901142242.n0EMgxsR011302@freefall.freebsd.org> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-net@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/89876: [txp] [patch] txp driver doesn't work with latest firmware 03.xxx.xxx 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, 15 Jan 2009 09:25:53 -0000 vwe@FreeBSD.org íàïèñà: > Synopsis: [txp] [patch] txp driver doesn't work with latest firmware 03.xxx.xxx > > State-Changed-From-To: open->feedback > State-Changed-By: vwe > State-Changed-When: Wed Jan 14 22:41:48 UTC 2009 > State-Changed-Why: > Doichin, > the patch isn't available for download anymore, so we're unable to > check that issue. Can you please give us the patch so a maintainer > can take a look? > > > Responsible-Changed-From-To: freebsd-bugs->freebsd-net > Responsible-Changed-By: vwe > Responsible-Changed-When: Wed Jan 14 22:41:48 UTC 2009 > Responsible-Changed-Why: > > Over to maintainer(s). > > http://www.freebsd.org/cgi/query-pr.cgi?pr=89876 > > Unfortunately it's been a while since I had the need to run those two txp cards I have, and eventually have abandoned the idea of using them at all. I do not keep the patch, but as long as i remember the main thing in it was copying the newest firmware available from the linux's txp (or whatever it was named) driver. I do still keep those cards, and can test them under the latest FBSD and report back later today on the status of the problem. Kind regards, Doichin From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 09:26: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 77E3F106566B; Thu, 15 Jan 2009 09:26:36 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: from mail-ew0-f30.google.com (mail-ew0-f30.google.com [209.85.219.30]) by mx1.freebsd.org (Postfix) with ESMTP id 97ED58FC1D; Thu, 15 Jan 2009 09:26:35 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: by ewy11 with SMTP id 11so332105ewy.19 for ; Thu, 15 Jan 2009 01:26:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references:subject :date:message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:x-mimeole:in-reply-to; bh=lWhGXq89Xm6/iBLbSj+8fH+b7Da78Dz3MGjgAjfu868=; b=ACiFOyxmvOSy7+EGx8ZHiaXr1aKoC2mPRQZGJorDbEM9fZGUoqxZAil0RUYc6oarvT Tp6JrllIwOLS4E+hY923fpQaEUbJ5nJ9rHmtCMoBYP++pNzX3ckni6VzQdpLAUZUz/6R PESgdwGNqtx5aa6vA7WESDZDeFFjBQR+7FiuQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :x-mimeole:in-reply-to; b=HRbRenjh8gS/dh9PkVnpKkvC1kc5qapYvEKnYOQeRlioQRedO3/nDKCtgC+b9Zcikz FuRZTwfEmEqRRDdvqyJ5LAiazBSRCCXREmZ4WGZFd3U2sDh7O6HfPOJ8RGIsucIEYx+2 TwmJSHCr42MTLGkVAmeRjq2rgmiRqk0cgEmoQ= Received: by 10.67.116.7 with SMTP id t7mr3099084ugm.63.1232011593830; Thu, 15 Jan 2009 01:26:33 -0800 (PST) Received: from mtllpt03 (DSL212-235-20-133.bb.netvision.net.il [212.235.20.133]) by mx.google.com with ESMTPS id o30sm1259739ugd.35.2009.01.15.01.26.31 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 15 Jan 2009 01:26:33 -0800 (PST) From: "Yony Yossef" To: "'Julian Elischer'" , "Yony Yossef" References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> <496E11B7.3010608@sepehrs.com> <000b01c9768e$745aa160$220f000a@mtl.com> <496EF30E.4010304@sepehrs.com> <000c01c976ec$87e040b0$220f000a@mtl.com> <496EF849.7040909@elischer.org> Date: Thu, 15 Jan 2009 11:26:34 +0200 Message-ID: <001501c976f3$5d7a81d0$220f000a@mtl.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acl27gFhXI+l5Z9aQiKGrodDmmFA4AABHJ6w X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 In-Reply-To: <496EF849.7040909@elischer.org> Cc: Liran Liss , freebsd-net@freebsd.org, Oleg Kats , "'H.fazaeli'" , Eitan Shefi , freebsd-questions@freebsd.org Subject: RE: howto determine network device unit number? device.hints? 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, 15 Jan 2009 09:26:38 -0000 > Yony Yossef wrote: > > Thanks for the explanation. > > > > So there's no way to determine this in advance.. > > I must build a script that contains my own mapping between MAC > > addresses and the wanted interface names and run it after > each driver > > load, rename the interfaces if necessary. > > you must agree it's flexible. > > > It seems quite wrong, don't you agree? > > > > And how come the unit number is given an arbitrary value? > Is there a > > good reason for that? > > device discovery depends on what slot you put the card into. > so if you move it, it's number may change. > > also, how do you identify the particular card you want to > have a particular unit number? considering it may move (and > for example USB network interfaces WILL move if you add a > keyboard or any other device.. > > also to do as you want would take 2 passes. > first one to find the numbers needed and another to do what's left. > Julian, I'm not talking about the case where I'm physically switching card locations on the PCI bus. All I'm doing is unloading and reloading the driver. Unit numbers change and it makes my automatic subnet configuration (/etc/rc.conf) assign bad IPs. I still don't get the reason for this arbitrarily assigned unit numbers and what is the common solution for it. Except post load rename of the interfaces. Yony > > > > > Yony > > > > > > > > _____ > > > > From: H.fazaeli [mailto:fazaeli@sepehrs.com] > > Sent: Thursday, January 15, 2009 10:26 AM > > To: Yony Yossef > > Cc: freebsd-net@freebsd.org; freebsd-questions@freebsd.org > > Subject: Re: howto determine network device unit number? > device.hints? > > > > > > > > for example, say you have 2 interface em0 and em1 which you like to > > swap their minor numbers: > > > > ifconfig em0 name tmp > > ifconfig em1 name em0 > > ifconfig em0 name em1 > > > > or to assign cisco-like names to you interfaces: > > > > ifconfig xl0 name fastEthernet0 > > ifconfig em0 name gigaEthernet0 > > ifconfig fastEthernet0 192.168.1.0/24 > > > > > > Yony Yossef wrote: > > > > > > > > > > > > > > > > -----Original Message----- > > > > From: H.fazaeli [mailto:fazaeli@sepehrs.com] > > > > Sent: Wednesday, January 14, 2009 6:24 PM > > > > To: Yony Yossef > > > > Cc: freebsd-net@freebsd.org; freebsd-questions@freebsd.org; > > > > Eitan Shefi; Oleg Kats; Liran Liss > > > > Subject: Re: howto determine network device unit number? > device.hints? > > > > > > > > > > > > you may not change unit numbers as they are strictly > > > > controlled by kernel. > > > > However, on freebsd 5.3+, you may use 'ifconfig name > ' > > > > to achieve the same affect > > > > > > > > > > > > > > > > Sorry, I don't understand the usage of ifconfig you > suggested and the > > effect > > > > it will cause. > > > > Can you please explain it? > > > > Yony > > > > > > > > > > > > Yony Yossef wrote: > > > > > > > > Hi, > > > > > > > > I would like to determine the unit number of my network cards, e.g. > > > > make the device on pci0:16 be assigned every time with unit > > > > > > > > number 0 > > > > > > > > and pci0:19 with unit number 1. > > > > > > > > Is it done by /boot/device.hints? > > > > if so, how? > > > > > > > > My cards are: > > > > > > > > mtnic0@pci0:19:0:0: class=0x020000 card=0x001715b3 > > > > > > > > chip=0x636815b3 > > > > > > > > rev=0xa0 hdr=0x00 > > > > mtnic1@pci0:16:0:0: class=0x020000 card=0x001715b3 > > > > > > > > chip=0x636815b3 > > > > > > > > rev=0xa0 hdr=0x00 > > > > > > > > So I've tried: > > > > > > > > hint.mtnic.0.at="pci0:16" > > > > hint.mtnic.1.at="pci0:19" > > > > > > > > but it doesn't work. They keep switching arbitrarily. > > > > I'm using FreeBSD 7.0. > > > > > > > > Thanks > > > > Yony > > > > _______________________________________________ > > > > freebsd-questions@freebsd.org mailing list > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > > To unsubscribe, send any mail to > > > > > > > > "freebsd-questions-unsubscribe@freebsd.org" > > > > > > > > > > > > > > > > > > From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 09:38: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 EC2BA1065680; Thu, 15 Jan 2009 09:38:55 +0000 (UTC) (envelope-from fazaeli@sepehrs.com) Received: from sepehrs.com (www.sepehrs.com [213.217.59.98]) by mx1.freebsd.org (Postfix) with ESMTP id B6B1E8FC1D; Thu, 15 Jan 2009 09:38:54 +0000 (UTC) (envelope-from fazaeli@sepehrs.com) Received: from [192.168.1.180] ([192.168.1.180]) by sepehrs.com (8.13.6/8.13.6) with ESMTP id n0F9gQtB057075; Thu, 15 Jan 2009 13:12:26 +0330 (IRST) (envelope-from fazaeli@sepehrs.com) Message-ID: <496F012A.2040807@sepehrs.com> Date: Thu, 15 Jan 2009 12:56:02 +0330 From: "H.fazaeli" User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Yony Yossef References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> <496E11B7.3010608@sepehrs.com> <000b01c9768e$745aa160$220f000a@mtl.com> <496EF30E.4010304@sepehrs.com> <000c01c976ec$87e040b0$220f000a@mtl.com> In-Reply-To: <000c01c976ec$87e040b0$220f000a@mtl.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Sepehr-MailScanner-Information: Please contact the ISP for more information X-Sepehr-MailScanner: Found to be clean X-Sepehr-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.399, required 5, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60) X-MailScanner-From: fazaeli@sepehrs.com X-Spam-Status: No Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org, Yony Yossef Subject: Re: howto determine network device unit number? device.hints? 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, 15 Jan 2009 09:38:56 -0000 Yony Yossef wrote: > Thanks for the explanation. > > So there's no way to determine this in advance.. > What do you mean by 'in advance'? Assuming a fixed hardware configuration, when the kernel is loaded, you know all the interface names and can rename them, i.e., in rc.local. > I must build a script that contains my own mapping between MAC addresses and > the wanted interface names and run it after each driver load, rename the > interfaces if necessary. > I do not quite understand your requirement. Can you please explain? Do you need a script that works on multiple machines with different hardwares? > It seems quite wrong, don't you agree? > > And how come the unit number is given an arbitrary value? Is there a good > reason for that? > > Yony > > > > _____ > > From: H.fazaeli [mailto:fazaeli@sepehrs.com] > Sent: Thursday, January 15, 2009 10:26 AM > To: Yony Yossef > Cc: freebsd-net@freebsd.org; freebsd-questions@freebsd.org > Subject: Re: howto determine network device unit number? device.hints? > > > > for example, say you have 2 interface em0 and em1 which > you like to swap their minor numbers: > > ifconfig em0 name tmp > ifconfig em1 name em0 > ifconfig em0 name em1 > > or to assign cisco-like names to you interfaces: > > ifconfig xl0 name fastEthernet0 > ifconfig em0 name gigaEthernet0 > ifconfig fastEthernet0 192.168.1.0/24 > > > Yony Yossef wrote: > > > > > > > > -----Original Message----- > > From: H.fazaeli [mailto:fazaeli@sepehrs.com] > > Sent: Wednesday, January 14, 2009 6:24 PM > > To: Yony Yossef > > Cc: freebsd-net@freebsd.org; freebsd-questions@freebsd.org; > > Eitan Shefi; Oleg Kats; Liran Liss > > Subject: Re: howto determine network device unit number? device.hints? > > > > > > you may not change unit numbers as they are strictly > > controlled by kernel. > > However, on freebsd 5.3+, you may use 'ifconfig name ' > > to achieve the same affect > > > > > > > > Sorry, I don't understand the usage of ifconfig you suggested and the effect > > it will cause. > > Can you please explain it? > > Yony > > > > > > Yony Yossef wrote: > > > > Hi, > > > > I would like to determine the unit number of my network cards, e.g. > > make the device on pci0:16 be assigned every time with unit > > > > number 0 > > > > and pci0:19 with unit number 1. > > > > Is it done by /boot/device.hints? > > if so, how? > > > > My cards are: > > > > mtnic0@pci0:19:0:0: class=0x020000 card=0x001715b3 > > > > chip=0x636815b3 > > > > rev=0xa0 hdr=0x00 > > mtnic1@pci0:16:0:0: class=0x020000 card=0x001715b3 > > > > chip=0x636815b3 > > > > rev=0xa0 hdr=0x00 > > > > So I've tried: > > > > hint.mtnic.0.at="pci0:16" > > hint.mtnic.1.at="pci0:19" > > > > but it doesn't work. They keep switching arbitrarily. > > I'm using FreeBSD 7.0. > > > > Thanks > > Yony > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > > > > "freebsd-questions-unsubscribe@freebsd.org" > > > > > > > > > -- Best regards. Hooman Fazaeli Sepehr S. T. Co. Ltd. Web: http://www.sepehrs.com Tel: (9821)88975701-2 Fax: (9821)88983352 From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 09:43: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 2ABDC106564A; Thu, 15 Jan 2009 09:43:38 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: from mail-ew0-f30.google.com (mail-ew0-f30.google.com [209.85.219.30]) by mx1.freebsd.org (Postfix) with ESMTP id 583468FC0A; Thu, 15 Jan 2009 09:43:37 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: by ewy11 with SMTP id 11so333883ewy.19 for ; Thu, 15 Jan 2009 01:43:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references:subject :date:message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:x-mimeole:in-reply-to; bh=xsPT3d+0IL9XY84ltFV3bhmX7EL0o5yfqCDtWJlUfdE=; b=YJQGLN2nxQ8UzJdTFa65fUo01S81FSbZadP8vjaS4/svkgFEzz5/WLTX37eXuiKzhb CxV61HMzmJUXBMl4sQ9whhPwToXJP+x2OG04oLAr2ix9oc3AVhLxL+IwfWojXwT1W6RU pWlJ/Ro/LzyYteCx9XkvYbGKM48k+LlSOBYwA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :x-mimeole:in-reply-to; b=B+dbKfOKpzihT95cWp3SVljEdMkMcZj9RO2CPp2vGVsvY7VxVCPyD9jR6R0Wc3Gd+w H+u6w4P/O+JteIxRWlY6duzhCsE7XGP9zxyn17Wm0gBD84FiTgJ1/VU4kdpSBOcqYsDq zR1ixULmpSegWCGpm84KaJbTR03LjYbsQr8d0= Received: by 10.66.220.12 with SMTP id s12mr3117666ugg.22.1232012616311; Thu, 15 Jan 2009 01:43:36 -0800 (PST) Received: from mtllpt03 (DSL212-235-20-133.bb.netvision.net.il [212.235.20.133]) by mx.google.com with ESMTPS id k1sm1314945ugf.3.2009.01.15.01.43.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 15 Jan 2009 01:43:35 -0800 (PST) From: "Yony Yossef" To: "'H.fazaeli'" , "Yony Yossef" References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> <496E11B7.3010608@sepehrs.com> <000b01c9768e$745aa160$220f000a@mtl.com> <496EF30E.4010304@sepehrs.com> <000c01c976ec$87e040b0$220f000a@mtl.com> <496F012A.2040807@sepehrs.com> Date: Thu, 15 Jan 2009 11:43:38 +0200 Message-ID: <001601c976f5$c015f7a0$220f000a@mtl.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acl282dJkYXRPzzTRvu2fMZek88u+AAACrCg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 In-Reply-To: <496F012A.2040807@sepehrs.com> Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org, Yony Yossef Subject: RE: howto determine network device unit number? device.hints? 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, 15 Jan 2009 09:43:38 -0000 > Yony Yossef wrote: > > Thanks for the explanation. > > > > So there's no way to determine this in advance.. > > > What do you mean by 'in advance'? Assuming a fixed hardware > configuration, when the kernel is loaded, you know all the > interface names and can rename them, i.e., in rc.local. >From the beginning: I have a FreeBSD7 machine with two network cards, both carry the same device name "mtnic". My driver is a kernel module loaded manualy using kldload. Upon load, the driver registers the net device by the name "mtnic", that is what you see in ifconfig. Problem is, this unit number is not constant and changing arbitrarily every time I reload the driver (card A unit number=0 & card B un=1 or the other way around). Therefore, IP assignment to mtnic0 by /etc/rc.conf may assign an interface with an IP belongs to another subnet, since rc.conf is not changing. Of course I can keep my own MAC-to-interface mapping and rename the interfaces after I load the driver. It doesn't sound like a reasonable solution though. Plus, I still don't understand why the unit number should change at all, instead of being determined according to the card PCI location or some other constant. Yony > > > I must build a script that contains my own mapping between MAC > > addresses and the wanted interface names and run it after > each driver > > load, rename the interfaces if necessary. > > > I do not quite understand your requirement. Can you please explain? > Do you need a script that works on multiple machines with > different hardwares? > > > It seems quite wrong, don't you agree? > > > > And how come the unit number is given an arbitrary value? > Is there a > > good reason for that? > > > > Yony From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 10:01:20 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 0748A106564A for ; Thu, 15 Jan 2009 10:01:20 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id A6DC08FC12 for ; Thu, 15 Jan 2009 10:01:19 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Subject:Message-ID:Reply-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender; b=Z1a4lDAPEodKGgCjXjEL3mgBSq2afh3PRuHPXUaoCeCn5MfNAvLZ6YppSXaaMUjKcesx1TJBdPiVGWDNi4V12R6Tiw+mfLAVrOl03xlJar9MypVGrG0Ds4AWuBeUJE8kbh+uqtzoLpETHxE/JHQ/psCSocq0HKac0K64cUpCtfc=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1LNP2I-000OVF-DL; Thu, 15 Jan 2009 13:01:14 +0300 Date: Thu, 15 Jan 2009 13:01:12 +0300 From: Eygene Ryabinkin To: Yony Yossef Message-ID: References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> <496E11B7.3010608@sepehrs.com> <000b01c9768e$745aa160$220f000a@mtl.com> <496EF30E.4010304@sepehrs.com> <000c01c976ec$87e040b0$220f000a@mtl.com> <496EF849.7040909@elischer.org> <001501c976f3$5d7a81d0$220f000a@mtl.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001501c976f3$5d7a81d0$220f000a@mtl.com> Sender: rea-fbsd@codelabs.ru Cc: Liran Liss , freebsd-net@freebsd.org, Oleg Kats , "'H.fazaeli'" , 'Julian Elischer' , Eitan Shefi , freebsd-questions@freebsd.org Subject: Re: howto determine network device unit number? device.hints? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rea-fbsd@codelabs.ru List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2009 10:01:20 -0000 Yony, good day. Thu, Jan 15, 2009 at 11:26:34AM +0200, Yony Yossef wrote: > All I'm doing is unloading and reloading the driver. > Unit numbers change and it makes my automatic subnet configuration > (/etc/rc.conf) assign bad IPs. You're using your own driver, aren't you? If yes, could you show your device_method_t structure and the corresponding identify, probe, attach and detach routines? You're setting the unit numbers via 'if_initname(ifp, device_get_name(dev), device_get_unit(dev))' or alike? > I still don't get the reason for this arbitrarily assigned unit numbers and > what is the common solution for it. Except post load rename of the > interfaces. I was under impression that the unit number are coming from the parent busses and they should be stable, at least for the case when the parent bus driver isn't unloaded (and for PCI it should be the case). So, either the driver sets device unit names weirdly or you hit some bug. -- Eygene _ ___ _.--. # \`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard / ' ` , __.--' # to read the on-line manual )/' _/ \ `-_, / # while single-stepping the kernel. `-'" `"\_ ,_.-;_.-\_ ', fsc/as # _.-'_./ {_.' ; / # -- FreeBSD Developers handbook {_.-``-' {_/ # From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 10:29: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 A1579106566B for ; Thu, 15 Jan 2009 10:29:11 +0000 (UTC) (envelope-from on@cs.ait.ac.th) Received: from mail.cs.ait.ac.th (mail.cs.ait.ac.th [192.41.170.16]) by mx1.freebsd.org (Postfix) with ESMTP id 7D1968FC0A for ; Thu, 15 Jan 2009 10:29:10 +0000 (UTC) (envelope-from on@cs.ait.ac.th) Received: from banyan.cs.ait.ac.th (banyan.cs.ait.ac.th [192.41.170.5]) by mail.cs.ait.ac.th (8.13.1/8.13.1) with ESMTP id n0F9kNod024511 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Jan 2009 16:46:23 +0700 (ICT) (envelope-from on@banyan.cs.ait.ac.th) Received: (from on@localhost) by banyan.cs.ait.ac.th (8.14.2/8.12.11) id n0F9nCWt065667; Thu, 15 Jan 2009 16:49:12 +0700 (ICT) Date: Thu, 15 Jan 2009 16:49:12 +0700 (ICT) Message-Id: <200901150949.n0F9nCWt065667@banyan.cs.ait.ac.th> From: Olivier Nicole To: yonyossef.lists@gmail.com In-reply-to: <001601c976f5$c015f7a0$220f000a@mtl.com> (yonyossef.lists@gmail.com) References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> <496E11B7.3010608@sepehrs.com> <000b01c9768e$745aa160$220f000a@mtl.com> <496EF30E.4010304@sepehrs.com> <000c01c976ec$87e040b0$220f000a@mtl.com> <496F012A.2040807@sepehrs.com> <001601c976f5$c015f7a0$220f000a@mtl.com> X-Virus-Scanned: on CSIM by amavisd-milter (http://www.amavis.org/) Cc: freebsd-net@freebsd.org, fazaeli@sepehrs.com, freebsd-questions@freebsd.org, yonyossef.lists@gmail.com Subject: Re: howto determine network device unit number? device.hints? 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, 15 Jan 2009 10:29:11 -0000 Hi, Sorry to jump in but... > Problem is, this unit number is not constant and changing arbitrarily every > time I reload the driver (card A unit number=0 & card B un=1 or the other > way around). Since I have been using FreeBSD, the NIC had always been given the same unit number (that is, unless I play and swap the hardware inside the machine). And that is the normal behaviour. Of course at each boot the interface em0 remains interface em0 and ithe interface em1 remains interface em1, else it would be a headache. > Plus, I still don't understand why the unit number should change at all, > instead of being determined according to the card PCI location or some other > constant. Not only it should not change, but you are the first person I ever see mentioning that it change at each boot. Bests, Olivier From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 10:47: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 861D41065674; Thu, 15 Jan 2009 10:47:31 +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 3F77D8FC2D; Thu, 15 Jan 2009 10:47:31 +0000 (UTC) (envelope-from freebsd@levsha.org.ua) Received: from levsha by expo.ukrweb.net with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LNPDm-00089K-S4; Thu, 15 Jan 2009 12:13:06 +0200 Date: Thu, 15 Jan 2009 12:13:06 +0200 From: Mykola Dzham To: "H.fazaeli" Message-ID: <20090115101306.GG39618@expo.ukrweb.net> References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> <496E11B7.3010608@sepehrs.com> <000b01c9768e$745aa160$220f000a@mtl.com> <496EF30E.4010304@sepehrs.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <496EF30E.4010304@sepehrs.com> X-Operating-System: FreeBSD/7.0-STABLE (i386) User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org Subject: Re: howto determine network device unit number? device.hints? 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, 15 Jan 2009 10:47:32 -0000 H.fazaeli wrote: > > for example, say you have 2 interface em0 and em1 which > you like to swap their minor numbers: > ifconfig em0 name tmp > ifconfig em1 name em0 > ifconfig em0 name em1 > or to assign cisco-like names to you interfaces: > ifconfig xl0 name fastEthernet0 > ifconfig em0 name gigaEthernet0 > ifconfig fastEthernet0 192.168.1.0/24 > Yony Yossef wrote: Interface renaming is complex when you use ng_ether: if ng_ether loaded before renaming, then ng_ether node name remain unchanged after ifconfig ... name -- Mykola Dzham, LEFT-(UANIC|RIPE) JID: levsha@jabber.net.ua From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 11:15: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 7B17D1065673; Thu, 15 Jan 2009 11:15:44 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: from mail-ew0-f30.google.com (mail-ew0-f30.google.com [209.85.219.30]) by mx1.freebsd.org (Postfix) with ESMTP id A3D648FC14; Thu, 15 Jan 2009 11:15:43 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: by ewy11 with SMTP id 11so346410ewy.19 for ; Thu, 15 Jan 2009 03:15:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references:subject :date:message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:x-mimeole:in-reply-to; bh=yIH6EUJPOMf5KdIb+ojBFGfQpOZSwytc350nqPq1ql8=; b=ZHd6c46sNeDfW35l38RlABGj9uuGfZHUt1myzvjqeP1a28xhKY/TLiLNQwrSizmYu0 kKpO+N5aeitPArO0w3RDHrvNGvfDQZuxvhgbdLVDaGpanLSV/EEDVFze5U02Io+81tsW w+zqGj23lG7igxH7sMSCwJjxR6d3N+nbGLdoQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :x-mimeole:in-reply-to; b=EKcXBjrBV7CKXFMRctWrhRps7AmmeQXndur4Yl8fnFeuqi/KhmcuiUQdW+XwI1aMsA L6cNI3ucBSqa5wauJgK9uPc+qeHDEA2EVYdAfS0rKRrjUjsblZ+sza0f5/rc0vFnL7BH JkhpD4UV8Fh7aeztlauueKVhPDhtT05CCin3M= Received: by 10.67.115.15 with SMTP id s15mr3145055ugm.56.1232018142576; Thu, 15 Jan 2009 03:15:42 -0800 (PST) Received: from mtllpt03 (DSL212-235-20-133.bb.netvision.net.il [212.235.20.133]) by mx.google.com with ESMTPS id q1sm1487845uge.23.2009.01.15.03.15.40 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 15 Jan 2009 03:15:41 -0800 (PST) From: "Yony Yossef" To: , "Yony Yossef" References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> <496E11B7.3010608@sepehrs.com> <000b01c9768e$745aa160$220f000a@mtl.com> <496EF30E.4010304@sepehrs.com> <000c01c976ec$87e040b0$220f000a@mtl.com> <496EF849.7040909@elischer.org> <001501c976f3$5d7a81d0$220f000a@mtl.com> Date: Thu, 15 Jan 2009 13:15:53 +0200 Message-ID: <001701c97702$a301bd90$220f000a@mtl.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acl2+QecVlhjxwpkRWiLitQBNobj5gACUw4A X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 In-Reply-To: Cc: Liran Liss , freebsd-net@freebsd.org, Oleg Kats , "'H.fazaeli'" , 'Julian Elischer' , Eitan Shefi , freebsd-questions@freebsd.org Subject: RE: howto determine network device unit number? device.hints? 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, 15 Jan 2009 11:15:45 -0000 > -----Original Message----- > From: rea-fbsd@codelabs.ru [mailto:rea-fbsd@codelabs.ru] > Sent: Thursday, January 15, 2009 12:01 PM > To: Yony Yossef > Cc: 'Julian Elischer'; Liran Liss; freebsd-net@freebsd.org; > Oleg Kats; 'H.fazaeli'; Eitan Shefi; freebsd-questions@freebsd.org > Subject: Re: howto determine network device unit number? device.hints? > > Yony, good day. > > Thu, Jan 15, 2009 at 11:26:34AM +0200, Yony Yossef wrote: > > All I'm doing is unloading and reloading the driver. > > Unit numbers change and it makes my automatic subnet configuration > > (/etc/rc.conf) assign bad IPs. > > You're using your own driver, aren't you? If yes, could you > show your device_method_t structure and the corresponding > identify, probe, attach and detach routines? You're setting > the unit numbers via 'if_initname(ifp, device_get_name(dev), > device_get_unit(dev))' or alike? My device has 2 ports, therefore my if_initname is that: if_initname(dev, device_get_name(mdev->pdev), port + 2 * device_get_unit(mdev->pdev)); > > I still don't get the reason for this arbitrarily assigned unit > > numbers and what is the common solution for it. Except post load > > rename of the interfaces. > > I was under impression that the unit number are coming from > the parent busses and they should be stable, at least for the > case when the parent bus driver isn't unloaded (and for PCI > it should be the case). So, either the driver sets device > unit names weirdly or you hit some bug. > -- > Eygene This is what I captured the last time it happened. # pciconf -l | grep mtnic mtnic0@pci0:19:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 rev=0xa0 hdr=0x00 mtnic1@pci0:16:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 rev=0xa0 hdr=0x00 # kldunload if_mtnic # kldload if_mtnic # pciconf -l | grep mtnic mtnic1@pci0:19:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 rev=0xa0 hdr=0x00 mtnic0@pci0:16:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 rev=0xa0 hdr=0x00 From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 11:37: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 DEEF2106564A for ; Thu, 15 Jan 2009 11:37:42 +0000 (UTC) (envelope-from dimitar.vassilev@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by mx1.freebsd.org (Postfix) with ESMTP id 979C08FC0A for ; Thu, 15 Jan 2009 11:37:42 +0000 (UTC) (envelope-from dimitar.vassilev@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so407336ywe.13 for ; Thu, 15 Jan 2009 03:37:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=cBfSbrexU/1BpMEFmUmJfCwQVfcRPlydk3npp3To7M0=; b=qCcgz2PYiVklVnW/XHOePnhMJ/Twz8oT2U6eMtKdRBqqysdOluax+ZOA2kYQnWukwt fIGSLWgt4k6/5qbAUilOaQmIgEml6XB9Iys10ewD+XaZK3R7fXRXalbv95T4gDwVg6oW ry0ydt8buaalXWnH7P0geW55Qm3+FxG5FU9yA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=eWPRRbXHkJwdeQZUB2Es4iR84VRoHuPRxFppp2f3XD/DomlL3R/LwS9Gdd32qI3fsd FP5mPPOXTq8UsVWEWlNomq0LZB+MLR3SZG3K1xO0YTXcHe4ilrnVcYOyRLkgcLdIqG5l El0Lssgh232N1Wsx4BrGDIJkEHTu8a/6f1Dn8= Received: by 10.151.14.5 with SMTP id r5mr391164ybi.206.1232019461930; Thu, 15 Jan 2009 03:37:41 -0800 (PST) Received: by 10.151.133.7 with HTTP; Thu, 15 Jan 2009 03:37:41 -0800 (PST) Message-ID: <59adc1a0901150337n5fa35de0vd079f8e764d13b31@mail.gmail.com> Date: Thu, 15 Jan 2009 13:37:41 +0200 From: "Dimitar Vasilev" To: "Julian Elischer" In-Reply-To: <496ECB47.4060005@elischer.org> MIME-Version: 1.0 References: <59adc1a0901122114v15efa47ahba8beef6ace4ddb0@mail.gmail.com> <496CCFBF.3010008@elischer.org> <59adc1a0901142032u5c6bb08y5c8768aa43d1d56a@mail.gmail.com> <496ECB47.4060005@elischer.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re: setfib+pf 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, 15 Jan 2009 11:37:43 -0000 2009/1/15 Julian Elischer > Dimitar Vasilev wrote: > >> >> >> I'd much appreciate if someone thinks with me for the best >> options of using >> the setfib features along with pf. >> >> >> I know setfib but I don't know pf unfortunately.. I use ipfw >> (which is why ipfw has fib support :-) >> >> >> possibly Max Lair may know both.. >> >> Hi Julian, >> Could you sched some light on the ipfw and setfib as an example. Seems the >> person you're referring to is busy. The rest I will figure out on my own. If >> there are results - I will share back. >> Thanks, >> Dimitar >> > > > well, you need to tell me a little more about what you want to do. Thanks - here is the schema: Lan1(browsing clients) | -------------- ---------------- | WRT |-------------| ALIX |-----------Lan2 (DMZ stuff, splitted into various networks, vlans,etc) -------------- --------------- | | ----------- ---------------- | Uplink| | Uplink | ------------ ---------------- I will have two uplinks and would like to failover uplink of clients from lan 1 and lan 2 depending on which link is up, keeping Lan2 accessible via the both uplinks, using something like tunnel1.foobar and tunnel2.foobar, as well as keeping LAN2 isolated from the clients via vlan and firewall rules allowing ssh mostly. As will have various private networks,tunnels,etc and no BGP, I would like to take advantage of setfib. Thanks. Best regards, Dimitar Vassilev From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 12:35: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 59CC71065675; Thu, 15 Jan 2009 12:35:16 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id 040DA8FC14; Thu, 15 Jan 2009 12:35:15 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Subject:Message-ID:Reply-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender; b=oHoGECQ7wvuNWSIdafIgk7W1Vvvb3P+9xlXERyCHEhSGxkeTo3HTpMBB9GYHb66TgaPsJkDbSEGV9eMeJ6KiaJmWa7B+hqzG+Q9TiAHtr1YIjZaOaNQlM49NE6qp7UjWOvvkeacFxBGpjn+UXWl+8W2VM17/vG7omFzMlwF1Rwk=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1LNRRH-000BXA-WF; Thu, 15 Jan 2009 15:35:12 +0300 Date: Thu, 15 Jan 2009 15:35:09 +0300 From: Eygene Ryabinkin To: Yony Yossef Message-ID: References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> <496E11B7.3010608@sepehrs.com> <000b01c9768e$745aa160$220f000a@mtl.com> <496EF30E.4010304@sepehrs.com> <000c01c976ec$87e040b0$220f000a@mtl.com> <496EF849.7040909@elischer.org> <001501c976f3$5d7a81d0$220f000a@mtl.com> <001701c97702$a301bd90$220f000a@mtl.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001701c97702$a301bd90$220f000a@mtl.com> Sender: rea-fbsd@codelabs.ru Cc: Liran Liss , freebsd-net@freebsd.org, Oleg Kats , "'H.fazaeli'" , 'Julian Elischer' , Eitan Shefi , freebsd-questions@freebsd.org Subject: Re: howto determine network device unit number? device.hints? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rea-fbsd@codelabs.ru List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2009 12:35:17 -0000 Thu, Jan 15, 2009 at 01:15:53PM +0200, Yony Yossef wrote: > > You're using your own driver, aren't you? If yes, could you > > show your device_method_t structure and the corresponding > > identify, probe, attach and detach routines? You're setting > > the unit numbers via 'if_initname(ifp, device_get_name(dev), > > device_get_unit(dev))' or alike? > > My device has 2 ports, therefore my if_initname is that: > > if_initname(dev, device_get_name(mdev->pdev), > port + 2 * device_get_unit(mdev->pdev)); So, you totally have four network interfaces -- two for each PCI device? > This is what I captured the last time it happened. > > # pciconf -l | grep mtnic > mtnic0@pci0:19:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 > rev=0xa0 hdr=0x00 > mtnic1@pci0:16:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 > rev=0xa0 hdr=0x00 > > # kldunload if_mtnic > # kldload if_mtnic > > # pciconf -l | grep mtnic > mtnic1@pci0:19:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 > rev=0xa0 hdr=0x00 > mtnic0@pci0:16:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 > rev=0xa0 hdr=0x00 Could you do the following: 1. Boot with verbose kernel mode (push '5' on the boot screen). 2. Kldload your module and provide the full list of kernel messages you will see after this action. 3. Kldunload and again, provide all messages kernel will print for this. 4. Kldload again and supply all messages for the last time. This will show the PCI enumeration sequence and probe order for your driver pci device units. This might shed some light on the problem. Thanks. -- Eygene _ ___ _.--. # \`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard / ' ` , __.--' # to read the on-line manual )/' _/ \ `-_, / # while single-stepping the kernel. `-'" `"\_ ,_.-;_.-\_ ', fsc/as # _.-'_./ {_.' ; / # -- FreeBSD Developers handbook {_.-``-' {_/ # From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 13:06: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 1C65510656C6 for ; Thu, 15 Jan 2009 13:06:31 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id DD3258FC1A for ; Thu, 15 Jan 2009 13:06:30 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 62BBC211571; Thu, 15 Jan 2009 08:06:30 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Thu, 15 Jan 2009 08:06:30 -0500 X-Sasl-enc: IzmbNV+XKk4Bi9thRDrV5t40pX01nKP+Ade67BaI4LH5 1232024790 Received: from empiric.lon.incunabulum.net (radius-82-150-131-239.dsdeurne.nl [82.150.131.239]) by mail.messagingengine.com (Postfix) with ESMTPSA id 1934FCA29; Thu, 15 Jan 2009 08:06:29 -0500 (EST) Message-ID: <496F34D2.7050605@FreeBSD.org> Date: Thu, 15 Jan 2009 13:06:26 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.19 (X11/20090107) MIME-Version: 1.0 To: Yony Yossef References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> <496E11B7.3010608@sepehrs.com> <000b01c9768e$745aa160$220f000a@mtl.com> <496EF30E.4010304@sepehrs.com> <000c01c976ec$87e040b0$220f000a@mtl.com> In-Reply-To: <000c01c976ec$87e040b0$220f000a@mtl.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Liran Liss , freebsd-net@freebsd.org, Oleg Kats , "'H.fazaeli'" , Eitan Shefi , freebsd-questions@freebsd.org Subject: Re: howto determine network device unit number? device.hints? 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, 15 Jan 2009 13:06:31 -0000 Yony Yossef wrote: > Thanks for the explanation. > > So there's no way to determine this in advance.. > I must build a script that contains my own mapping between MAC addresses and > the wanted interface names and run it after each driver load, rename the > interfaces if necessary. > It seems quite wrong, don't you agree? > > And how come the unit number is given an arbitrary value? Is there a good > reason for that? > Normally the PCI probe runs in the opposite direction from that of Linux. It's largely to do with how the NEWBUS code walks the PCI bus. From a systems management point of view, yeah, it's irritating, however it would probably take more effort (i.e. kernel code) to try to patch it to work differently, and not everyone has free time to sit down and patch the kernel. That and (unlike Solaris) there is no *direct* mapping between the card's driver number on the bus and its network driver number. In your case I'm not sure why your two cards would flip order. Could it be how your BIOS and hardware set up the PCI IDSEL lines at boot? From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 13:16: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 72CCE106571F; Thu, 15 Jan 2009 13:16:11 +0000 (UTC) (envelope-from root@net1.cc) Received: from server1.net1.cc (server1.net1.cc [213.137.48.2]) by mx1.freebsd.org (Postfix) with ESMTP id 28F628FC20; Thu, 15 Jan 2009 13:16:10 +0000 (UTC) (envelope-from root@net1.cc) Received: from support.net1.cc ([213.137.58.124]) by server1.net1.cc with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LNS4u-0001qu-KQ; Thu, 15 Jan 2009 15:16:08 +0200 Message-ID: <496F3710.2090205@net1.cc> Date: Thu, 15 Jan 2009 15:16:00 +0200 From: NetOne - Doichin Dokov User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: vwe@FreeBSD.org References: <200901142242.n0EMgxsR011302@freefall.freebsd.org> <496EFB53.80609@net1.cc> In-Reply-To: <496EFB53.80609@net1.cc> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-net@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/89876: [txp] [patch] txp driver doesn't work with latest firmware 03.xxx.xxx 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, 15 Jan 2009 13:16:12 -0000 NetOne - Doichin Dokov íàïèñà: > vwe@FreeBSD.org íàïèñà: >> Synopsis: [txp] [patch] txp driver doesn't work with latest firmware >> 03.xxx.xxx >> >> State-Changed-From-To: open->feedback >> State-Changed-By: vwe >> State-Changed-When: Wed Jan 14 22:41:48 UTC 2009 >> State-Changed-Why: Doichin, >> the patch isn't available for download anymore, so we're unable to >> check that issue. Can you please give us the patch so a maintainer >> can take a look? >> >> >> Responsible-Changed-From-To: freebsd-bugs->freebsd-net >> Responsible-Changed-By: vwe >> Responsible-Changed-When: Wed Jan 14 22:41:48 UTC 2009 >> Responsible-Changed-Why: >> Over to maintainer(s). >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=89876 >> >> > Unfortunately it's been a while since I had the need to run those two > txp cards I have, and eventually have abandoned the idea of using them > at all. I do not keep the patch, but as long as i remember the main > thing in it was copying the newest firmware available from the linux's > txp (or whatever it was named) driver. > > I do still keep those cards, and can test them under the latest FBSD > and report back later today on the status of the problem. > > Kind regards, > Doichin > I've now placed one of the cards I have in a FreeBSD 7.0 machine - it's still not recognized (booted) properly. Here's the boot log: ... Jan 15 15:08:41 test kernel: txp0: <3Com 3cR990B-TXM Etherlink with 3XP Processor> port 0x2080-0x20ff mem 0x42000000-0x4200007f irq 11 at device 14.0 on pci0 Jan 15 15:08:41 test kernel: txp0: not waiting for boot Jan 15 15:08:41 test kernel: device_attach: txp0 attach returned -1 ... Here's the related pciconf: txp0@pci0:0:14:0: class=0x020000 card=0x100010b7 chip=0x990410b7 rev=0x03 hdr=0x00 vendor = '3COM Corp, Networking Division' device = '3CR990B-TM-X Etherlink 10/100 with 3XP Processor' class = network subclass = ethernet If you're interested in fixing this problem, you might have a look at the driver included in the Linux kernel - it works fine with this card. Unfortunately I no longer need to use those cards, and can afford to spend any time on this issue, what I could help is with testing. I could also provide an SSH access to a machine with this card installed, if this would be of any help resolving the issue. Kind regards, Doichin From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 15:01: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 401651065670; Thu, 15 Jan 2009 15:01:43 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 10A6E8FC17; Thu, 15 Jan 2009 15:01:43 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 943C9212657; Thu, 15 Jan 2009 10:01:42 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Thu, 15 Jan 2009 10:01:42 -0500 X-Sasl-enc: hT3+O1CtVhKCPvAR68BEkZY2e0EoN5AJ2tcayOh8G+FE 1232031702 Received: from empiric.lon.incunabulum.net (radius-82-150-131-239.dsdeurne.nl [82.150.131.239]) by mail.messagingengine.com (Postfix) with ESMTPSA id C212B24B27; Thu, 15 Jan 2009 10:01:40 -0500 (EST) Message-ID: <496F4FD1.4080602@FreeBSD.org> Date: Thu, 15 Jan 2009 15:01:37 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.19 (X11/20090107) MIME-Version: 1.0 To: Yony Yossef References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> <496E11B7.3010608@sepehrs.com> <000b01c9768e$745aa160$220f000a@mtl.com> <496EF30E.4010304@sepehrs.com> <000c01c976ec$87e040b0$220f000a@mtl.com> <496F34D2.7050605@FreeBSD.org> In-Reply-To: <496F34D2.7050605@FreeBSD.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Liran Liss , freebsd-net@freebsd.org, Oleg Kats , "'H.fazaeli'" , Eitan Shefi , freebsd-questions@freebsd.org Subject: Re: howto determine network device unit number? device.hints? 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, 15 Jan 2009 15:01:43 -0000 Yony, Bruce M. Simpson wrote: >> >> And how come the unit number is given an arbitrary value? Is there a >> good >> reason for that? >> > ... > > In your case I'm not sure why your two cards would flip order. Could > it be how your BIOS and hardware set up the PCI IDSEL lines at boot? If this is the case on your system, then you really need to provide more data about your hardware, i.e. motherboard, BIOS, vendor information etc. as others point out. Based on the data you've provided about the issue to date, my best guess is that something in the above is different on your system (which is why I mentioned IDSEL lines -- the mechanism PCI uses to actually assign bus numbers electrically). Normally the behaviour of FreeBSD's bus probes is well known -- nexus is walked for child buses, then these buses are plumbed into NEWBUS, e.g. cpu0...cpuN on nexus itself, PCI buses, and PCI subordinate buses in that order. * You mention you don't encounter the issue with Linux, but you may already be aware that udev can tie driver instance number(s) to specific MAC addresses, although this process isn't fully automatic and any given distro may or may not create the persistent udev rules on a first run -- so this is comparing apples with oranges. * [PCI-Express is a special case though, and I've had to sit down and do some work with commercial clients to make sure their appliance was able to detect devices being in particular slot numbers. Again, though, it's just as subject to the PCI enumeration order further up on the bus hierarchy as non-PCI-Express drivers.] So your issue may not be a simple matter of "this seems wrong, this doesn't work", though I am sorry to hear it isn't working for you right now. There are a lot of dynamic factors in the overall picture of the system, and what seems to work as expected for many users, may not be working for you, and we really need basic hardware information, when folk see things like this happening, for any volunteer(s) out there to come up with the right solution, let alone the true picture of what's actually going on in your specific case. thanks BMS From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 16:48: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 05EF81065673; Thu, 15 Jan 2009 16:48:24 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id A279F8FC21; Thu, 15 Jan 2009 16:48:23 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Subject:Message-ID:Reply-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender; b=oJ/hyQ9dsPXEdzllzhEOvTq9ELAhlfH7Uka3yq9sVXZCZXU5KskAOu7EeOXRbKR99GS8UtiejXbvDG+qN0oLq9Cnas+JYqezRIbS8ZcX6n7iW5djRnTt79OKH63wau6qMloHOLQ6IpF5jH3/q4qZ2NQ71hoW4i2MPGALq/UV40k=; Received: from phoenix.codelabs.ru (ppp91-76-14-132.pppoe.mtu-net.ru [91.76.14.132]) by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1LNVOH-0007In-U4; Thu, 15 Jan 2009 19:48:22 +0300 Date: Thu, 15 Jan 2009 19:48:19 +0300 From: Eygene Ryabinkin To: "Bruce M. Simpson" Message-ID: <+b/MqS4l8z9bOD9y4AZP70mtFL0@kjaK+/sQ5DW5981v71UogZJPf/0> References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> <496E11B7.3010608@sepehrs.com> <000b01c9768e$745aa160$220f000a@mtl.com> <496EF30E.4010304@sepehrs.com> <000c01c976ec$87e040b0$220f000a@mtl.com> <496F34D2.7050605@FreeBSD.org> <496F4FD1.4080602@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <496F4FD1.4080602@FreeBSD.org> Sender: rea-fbsd@codelabs.ru Cc: Liran Liss , freebsd-net@freebsd.org, Oleg Kats , "'H.fazaeli'" , Yony Yossef , Eitan Shefi , freebsd-questions@freebsd.org Subject: Re: howto determine network device unit number? device.hints? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rea-fbsd@codelabs.ru List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2009 16:48:24 -0000 Bruce, good day. Thu, Jan 15, 2009 at 03:01:37PM +0000, Bruce M. Simpson wrote: > Bruce M. Simpson wrote: > > In your case I'm not sure why your two cards would flip order. Could > > it be how your BIOS and hardware set up the PCI IDSEL lines at boot? > > If this is the case on your system, then you really need to provide more > data about your hardware, i.e. motherboard, BIOS, vendor information > etc. as others point out. I wanted to stress only one point: simple 'kldunload ' and 'kldload ' makes devices to flip for Yony's case. This means that unless some PCI hotplug stuff is here (which I don't believe to be present, because no physical cards are touched and there is actually a small amount of PCI hotplug support in FreeBSD), no physical PCI devices get added or removed from the PCI child tree. It looks like that something goes wrong during the PCI tree reprobe on the driver module loading. Correct me if I am wrong, but pci_driver_added from /sys/pci/pci.c will invoke device_get_children() to get the list of the attached devices, and for PCI case the list should be static. Here is what I get for the 'kldload if_em' with verbose boot: ----- pci0: driver added found-> vendor=0x8086, dev=0x283e, revid=0x02 domain=0, bus=0, slot=31, func=3 class=0c-05-00, hdrtype=0x00, mfdev=0 cmdreg=0x0001, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=18 pci0:0:31:3: reprobing on driver added pci1: driver added pci2: driver added pci3: driver added pci4: driver added pci5: driver added found-> vendor=0x8086, dev=0x1010, revid=0x01 domain=0, bus=5, slot=3, func=0 class=02-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0017, statreg=0x0230, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0xff (63750 ns), maxlat=0x00 (0 ns) intpin=a, irq=16 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit pci0:5:3:0: reprobing on driver added em0: port 0xb880-0xb8bf mem 0xff7c0000-0xff7dffff irq 16 at device 3.0 on pci5 pcib5: em0 requested memory range 0xff7c0000-0xff7dffff: good pcib5: em0 requested I/O range 0xb880-0xb8bf: in range em0: [FILTER] em0: bpf attached em0: Ethernet address: NN:NN:NN:NN:NN:NN found-> vendor=0x8086, dev=0x1010, revid=0x01 domain=0, bus=5, slot=3, func=1 class=02-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0017, statreg=0x0230, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0xff (63750 ns), maxlat=0x00 (0 ns) intpin=b, irq=17 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit pci0:5:3:1: reprobing on driver added em1: port 0xbc00-0xbc3f mem 0xff7e0000-0xff7fffff irq 17 at device 3.1 on pci5 pcib5: em1 requested memory range 0xff7e0000-0xff7fffff: good pcib5: em1 requested I/O range 0xbc00-0xbc3f: in range em1: [FILTER] em1: bpf attached em1: Ethernet address: NN:NN:NN:NN:NN:NN ----- And this message is stable across repeated kldunload/kldload. I guess that when Yony will enable verbose boot and will show us kernel messages from two successive kldunload/kldload sequences, we will get some additional information about what's going on. -- Eygene _ ___ _.--. # \`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard / ' ` , __.--' # to read the on-line manual )/' _/ \ `-_, / # while single-stepping the kernel. `-'" `"\_ ,_.-;_.-\_ ', fsc/as # _.-'_./ {_.' ; / # -- FreeBSD Developers handbook {_.-``-' {_/ # From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 17:39:56 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 9F5FF106566B; Thu, 15 Jan 2009 17:39:56 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: from mail-gx0-f21.google.com (mail-gx0-f21.google.com [209.85.217.21]) by mx1.freebsd.org (Postfix) with ESMTP id C4C9D8FC0C; Thu, 15 Jan 2009 17:39:55 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: by gxk14 with SMTP id 14so1322551gxk.19 for ; Thu, 15 Jan 2009 09:39:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=C+z3GX0OlJYqZquQggeoQ3rl3sQF3MUVVSjcnQkD5Zk=; b=jTqEg0Xfx24dXcI/AJgq7G2ut2rndgrzTZqfnd+UlrZybF3oKF1o5HgMR3fwS1BBqp LpgSQl+BxuMQJFgrjEy8Q+J0RhTYnrN0A5F4oMpWMaH3FYKMdITH7f0qHNANLzHVvSRo nSG8uXAk4VR78ozy2XPkDCdivZvGeJagLOH4E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=UK0WbvIQyHg5cE6RGpYUyFFYBgQp3QZvCajHp8P6OitYF9W2b8LDjrJJ8ue3PUOcA+ 3PzXOPH+A6zn57rImDl6cU32VgKddVPBsEFAa8fkWt7tLL/Dwonhs1VNVRAv6AAl4Ueh RMTMVlfXz9JyoL0rFM+8ZHZI5PpL0P3vAuta8= Received: by 10.150.58.5 with SMTP id g5mr4380479yba.145.1232041194513; Thu, 15 Jan 2009 09:39:54 -0800 (PST) Received: by 10.150.229.15 with HTTP; Thu, 15 Jan 2009 09:39:54 -0800 (PST) Message-ID: <20def4870901150939h69f8826cobfd46bc99941dcf3@mail.gmail.com> Date: Thu, 15 Jan 2009 19:39:54 +0200 From: "Yony Yossef" To: rea-fbsd@codelabs.ru In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> <496E11B7.3010608@sepehrs.com> <000b01c9768e$745aa160$220f000a@mtl.com> <496EF30E.4010304@sepehrs.com> <000c01c976ec$87e040b0$220f000a@mtl.com> <496EF849.7040909@elischer.org> <001501c976f3$5d7a81d0$220f000a@mtl.com> <001701c97702$a301bd90$220f000a@mtl.com> Cc: Yehonatan Yossef , Liran Liss , freebsd-net@freebsd.org, Oleg Kats , "H.fazaeli" , Julian Elischer , Eitan Shefi , freebsd-questions@freebsd.org Subject: Re: howto determine network device unit number? device.hints? 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, 15 Jan 2009 17:39:57 -0000 > Thu, Jan 15, 2009 at 01:15:53PM +0200, Yony Yossef wrote: > > > You're using your own driver, aren't you? If yes, could you show > > > your device_method_t structure and the corresponding identify, > > > probe, attach and detach routines? You're setting the > unit numbers > > > via 'if_initname(ifp, device_get_name(dev), > device_get_unit(dev))' > > > or alike? > > > > My device has 2 ports, therefore my if_initname is that: > > > > if_initname(dev, device_get_name(mdev->pdev), > > port + 2 * device_get_unit(mdev->pdev)); > > So, you totally have four network interfaces -- two for each > PCI device? > > > This is what I captured the last time it happened. > > > > # pciconf -l | grep mtnic > > mtnic0@pci0:19:0:0: class=0x020000 card=0x001715b3 > chip=0x636815b3 > > rev=0xa0 hdr=0x00 > > mtnic1@pci0:16:0:0: class=0x020000 card=0x001715b3 > chip=0x636815b3 > > rev=0xa0 hdr=0x00 > > > > # kldunload if_mtnic > > # kldload if_mtnic > > > > # pciconf -l | grep mtnic > > mtnic1@pci0:19:0:0: class=0x020000 card=0x001715b3 > chip=0x636815b3 > > rev=0xa0 hdr=0x00 > > mtnic0@pci0:16:0:0: class=0x020000 card=0x001715b3 > chip=0x636815b3 > > rev=0xa0 hdr=0x00 > > Could you do the following: > > 1. Boot with verbose kernel mode (push '5' on the boot screen). > 2. Kldload your module and provide the full list of kernel messages > you will see after this action. > 3. Kldunload and again, provide all messages kernel will print > for this. > 4. Kldload again and supply all messages for the last time. > > This will show the PCI enumeration sequence and probe order > for your driver pci device units. This might shed some light > on the problem. > This is the flow I've done, you can see the swapping happened again: [root@sw247 ~]# pciconf -l | grep mtnic mtnic0@pci0:19:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 rev=0xa0 hdr=0x00 mtnic1@pci0:16:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 rev=0xa0 hdr=0x00 [root@sw247 ~]# kldunload if_mtnic [root@sw247 ~]# kldload if_mtnic [root@sw247 ~]# pciconf -l | grep mtnic mtnic1@pci0:19:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 rev=0xa0 hdr=0x00 mtnic0@pci0:16:0:0: class=0x020000 card=0x001715b3 chip=0x636815b3 rev=0xa0 hdr=0x00 /var/log/messages during this flow (the brackets are my addition ofcourse): [kldunload if_mtnic] Jan 15 19:27:46 sw247 kernel: mtnic0: Destroying netdev on port:0 Jan 15 19:27:46 sw247 kernel: mtnic0: Destroying netdev on port:1 Jan 15 19:27:46 sw247 kernel: mtnic0: Reseting device... Jan 15 19:27:46 sw247 kernel: mtnic0: Reset complete. Jan 15 19:27:46 sw247 kernel: mtnic0: detached Jan 15 19:27:46 sw247 kernel: mtnic1: Destroying netdev on port:0 Jan 15 19:27:46 sw247 kernel: mtnic1: Destroying netdev on port:1 Jan 15 19:27:47 sw247 kernel: mtnic1: Reseting device... Jan 15 19:27:47 sw247 kernel: mtnic1: Reset complete. Jan 15 19:27:47 sw247 kernel: mtnic1: detached [kldload if_mtnic] Jan 15 19:28:04 sw247 kernel: pci0: driver added Jan 15 19:28:04 sw247 kernel: found-> vendor=0x0e11, dev=0xb203, revid=0x03 Jan 15 19:28:04 sw247 kernel: domain=0, bus=0, slot=4, func=0 Jan 15 19:28:04 sw247 kernel: class=08-80-00, hdrtype=0x00, mfdev=1 Jan 15 19:28:04 sw247 kernel: cmdreg=0x0103, statreg=0x0290, cachelnsz=0 (dwords) Jan 15 19:28:04 sw247 kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Jan 15 19:28:04 sw247 kernel: intpin=a, irq=25 Jan 15 19:28:04 sw247 kernel: powerspec 3 supports D0 D3 current D0 Jan 15 19:28:04 sw247 kernel: pci0:0:4:0: reprobing on driver added Jan 15 19:28:04 sw247 kernel: found-> vendor=0x0e11, dev=0xb204, revid=0x03 Jan 15 19:28:04 sw247 kernel: domain=0, bus=0, slot=4, func=2 Jan 15 19:28:04 sw247 kernel: class=08-80-00, hdrtype=0x00, mfdev=1 Jan 15 19:28:04 sw247 kernel: cmdreg=0x0117, statreg=0x0290, cachelnsz=16 (dwords) Jan 15 19:28:04 sw247 kernel: lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Jan 15 19:28:04 sw247 kernel: intpin=b, irq=26 Jan 15 19:28:04 sw247 kernel: powerspec 3 supports D0 D3 current D0 Jan 15 19:28:04 sw247 kernel: pci0:0:4:2: reprobing on driver added Jan 15 19:28:04 sw247 kernel: found-> vendor=0x103c, dev=0x3302, revid=0x00 Jan 15 19:28:04 sw247 kernel: domain=0, bus=0, slot=4, func=6 Jan 15 19:28:04 sw247 kernel: class=0c-07-01, hdrtype=0x00, mfdev=1 Jan 15 19:28:04 sw247 kernel: cmdreg=0x0002, statreg=0x0290, cachelnsz=0 (dwords) Jan 15 19:28:04 sw247 kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Jan 15 19:28:04 sw247 kernel: intpin=a, irq=25 Jan 15 19:28:04 sw247 kernel: powerspec 3 supports D0 D3 current D0 Jan 15 19:28:04 sw247 kernel: pci0:0:4:6: reprobing on driver added Jan 15 19:28:04 sw247 kernel: pci1: driver added Jan 15 19:28:04 sw247 kernel: pci2: driver added Jan 15 19:28:04 sw247 kernel: pci8: driver added Jan 15 19:28:04 sw247 kernel: pci9: driver added Jan 15 19:28:04 sw247 kernel: pci10: driver added Jan 15 19:28:04 sw247 kernel: pci11: driver added Jan 15 19:28:04 sw247 kernel: pci12: driver added Jan 15 19:28:04 sw247 kernel: pci13: driver added Jan 15 19:28:04 sw247 kernel: pci14: driver added Jan 15 19:28:04 sw247 kernel: pci15: driver added Jan 15 19:28:04 sw247 kernel: pci16: driver added Jan 15 19:28:04 sw247 kernel: found-> vendor=0x15b3, dev=0x6368, revid=0xa0 Jan 15 19:28:04 sw247 kernel: domain=0, bus=16, slot=0, func=0 Jan 15 19:28:04 sw247 kernel: class=02-00-00, hdrtype=0x00, mfdev=0 Jan 15 19:28:04 sw247 kernel: cmdreg=0x0046, statreg=0x0010, cachelnsz=16 (dwords) Jan 15 19:28:04 sw247 kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Jan 15 19:28:04 sw247 kernel: intpin=a, irq=20 Jan 15 19:28:04 sw247 kernel: powerspec 3 supports D0 D3 current D0 Jan 15 19:28:04 sw247 kernel: MSI-X supports 256 messages in map 0x10 Jan 15 19:28:04 sw247 kernel: pci0:16:0:0: reprobing on driver added Jan 15 19:28:04 sw247 kernel: mtnic0: mem 0xfde00000-0xfdefffff,0xf7000000-0xf77fffff irq 20 at device 0.0 onpci16 Jan 15 19:28:04 sw247 kernel: mtnic: Mellanox NIC driver v1.2.0 (20090112-1316) Jan 15 19:28:04 sw247 kernel: mtnic0: Initializing mtnic Jan 15 19:28:04 sw247 kernel: pcib5: mtnic0 requested memory range 0xfde00000-0xfdefffff: good Jan 15 19:28:04 sw247 kernel: pcib5: mtnic0 requested memory range 0xf7000000-0xf77fffff: good Jan 15 19:28:04 sw247 kernel: mtnic0: Number of LRO sessions per ring: 32 Jan 15 19:28:04 sw247 kernel: mtnic0: Reseting device... Jan 15 19:28:04 sw247 kernel: mtnic0: Reset complete. Jan 15 19:28:04 sw247 kernel: mtnic0: FW version:2.6.0 Jan 15 19:28:04 sw247 kernel: mtnic0: Board ID: Jan 15 19:28:04 sw247 kernel: mtnic0: Using 1 tx rings for port:1 [4096] Jan 15 19:28:04 sw247 kernel: mtnic0: Using 4 rx rings for port:1 [1024] Jan 15 19:28:04 sw247 kernel: mtnic0: Using 1 tx rings for port:2 [4096] Jan 15 19:28:04 sw247 kernel: mtnic0: Using 4 rx rings for port:2 [1024] Jan 15 19:28:04 sw247 kernel: mtnic0: Initializing MSIX Jan 15 19:28:04 sw247 kernel: mtnic0: Enabling MSI-X (11 vectors) Jan 15 19:28:04 sw247 kernel: mtnic0: attempting to allocate 11 MSI-X vectors (256 supported) Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 256 to vector 53 Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 257 to vector 54 Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 258 to vector 55 Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 259 to vector 56 Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 260 to vector 57 Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 261 to vector 58 Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 262 to vector 59 Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 263 to vector 60 Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 264 to vector 61 Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 265 to vector 62 Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 266 to vector 63 Jan 15 19:28:04 sw247 kernel: mtnic0: using IRQs 256-266 for MSI-X Jan 15 19:28:04 sw247 kernel: mtnic0: Board ID:MT_0920110004 Jan 15 19:28:04 sw247 kernel: msi: Assigning MSI-X IRQ 256 to local APIC 1 Jan 15 19:28:04 sw247 kernel: mtnic0: [MPSAFE] Jan 15 19:28:04 sw247 kernel: mtnic0: [ITHREAD] Jan 15 19:28:04 sw247 kernel: mtnic0: Activating port:1 Jan 15 19:28:04 sw247 kernel: mtnic0: Allocated 5 CQs on port:0 name:mtnic unit:0 ifc:0 Jan 15 19:28:04 sw247 kernel: mtnic0: bpf attached Jan 15 19:28:04 sw247 kernel: mtnic0: Ethernet address: 00:02:c9:02:13:2d Jan 15 19:28:04 sw247 kernel: mtnic0: Activating port:2 Jan 15 19:28:04 sw247 kernel: mtnic0: Allocated 5 CQs on port:1 name:mtnic unit:0 ifc:1 Jan 15 19:28:04 sw247 kernel: mtnic1: bpf attached Jan 15 19:28:04 sw247 kernel: mtnic1: Ethernet address: 00:02:c9:02:13:2e Jan 15 19:28:04 sw247 kernel: pci19: driver added Jan 15 19:28:04 sw247 kernel: found-> vendor=0x15b3, dev=0x6368, revid=0xa0 Jan 15 19:28:04 sw247 kernel: domain=0, bus=19, slot=0, func=0 Jan 15 19:28:04 sw247 kernel: class=02-00-00, hdrtype=0x00, mfdev=0 Jan 15 19:28:04 sw247 kernel: cmdreg=0x0046, statreg=0x0010, cachelnsz=16 (dwords) Jan 15 19:28:04 sw247 kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Jan 15 19:28:04 sw247 kernel: intpin=a, irq=16 Jan 15 19:28:04 sw247 kernel: powerspec 3 supports D0 D3 current D0 Jan 15 19:28:04 sw247 kernel: MSI-X supports 256 messages in map 0x10 Jan 15 19:28:04 sw247 kernel: pci0:19:0:0: reprobing on driver added Jan 15 19:28:04 sw247 kernel: mtnic1: mem 0xfdf00000-0xfdffffff,0xf7800000-0xf7ffffff irq 16 at device 0.0 onpci19 Jan 15 19:28:04 sw247 kernel: mtnic1: Initializing mtnic Jan 15 19:28:04 sw247 kernel: pcib4: mtnic1 requested memory range 0xfdf00000-0xfdffffff: good Jan 15 19:28:04 sw247 kernel: pcib4: mtnic1 requested memory range 0xf7800000-0xf7ffffff: good Jan 15 19:28:04 sw247 kernel: mtnic1: Number of LRO sessions per ring: 32 Jan 15 19:28:04 sw247 kernel: mtnic1: Reseting device... Jan 15 19:28:04 sw247 kernel: mtnic1: Reset complete. Jan 15 19:28:04 sw247 kernel: mtnic1: FW version:2.6.0 Jan 15 19:28:04 sw247 kernel: mtnic1: Board ID: Jan 15 19:28:04 sw247 kernel: mtnic1: Using 1 tx rings for port:1 [4096] Jan 15 19:28:04 sw247 kernel: mtnic1: Using 4 rx rings for port:1 [1024] Jan 15 19:28:04 sw247 kernel: mtnic1: Using 1 tx rings for port:2 [4096] Jan 15 19:28:04 sw247 kernel: mtnic1: Using 4 rx rings for port:2 [1024] Jan 15 19:28:04 sw247 kernel: mtnic1: Initializing MSIX Jan 15 19:28:04 sw247 kernel: mtnic1: Enabling MSI-X (11 vectors) Jan 15 19:28:04 sw247 kernel: mtnic1: attempting to allocate 11 MSI-X vectors (256 supported) Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 267 to vector 64 Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 268 to vector 65 Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 269 to vector 66 Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 270 to vector 67 Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 271 to vector 68 Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 272 to vector 69 Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 273 to vector 70 Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 274 to vector 71 Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 275 to vector 72 Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 276 to vector 73 Jan 15 19:28:04 sw247 kernel: msi: routing MSI-X IRQ 277 to vector 74 Jan 15 19:28:04 sw247 kernel: mtnic1: using IRQs 267-277 for MSI-X Jan 15 19:28:04 sw247 kernel: mtnic1: Board ID:MT_0920110004 Jan 15 19:28:04 sw247 kernel: msi: Assigning MSI-X IRQ 267 to local APIC 2 Jan 15 19:28:04 sw247 kernel: mtnic1: [MPSAFE] Jan 15 19:28:04 sw247 kernel: mtnic1: [ITHREAD] Jan 15 19:28:04 sw247 kernel: mtnic1: Activating port:1 Jan 15 19:28:04 sw247 kernel: mtnic1: Allocated 5 CQs on port:0 name:mtnic unit:1 ifc:2 Jan 15 19:28:04 sw247 kernel: mtnic2: bpf attached Jan 15 19:28:04 sw247 kernel: mtnic2: Ethernet address: 00:02:c9:02:17:f7 Jan 15 19:28:04 sw247 kernel: mtnic1: Activating port:2 Jan 15 19:28:04 sw247 kernel: mtnic1: Allocated 5 CQs on port:1 name:mtnic unit:1 ifc:3 Jan 15 19:28:04 sw247 kernel: mtnic3: bpf attached Jan 15 19:28:04 sw247 kernel: mtnic3: Ethernet address: 00:02:c9:02:17:f8 Jan 15 19:28:04 sw247 kernel: mtnic0: Port is down, ignoring multicast change. Jan 15 19:28:04 sw247 kernel: mtnic0: Change MTU called, driver is not running. flags:0x0 Jan 15 19:28:04 sw247 kernel: msi: Assigning MSI-X IRQ 257 to local APIC 3 Jan 15 19:28:04 sw247 kernel: mtnic0: [MPSAFE] Jan 15 19:28:04 sw247 kernel: mtnic0: [ITHREAD] Jan 15 19:28:04 sw247 kernel: msi: Assigning MSI-X IRQ 258 to local APIC 0 Jan 15 19:28:04 sw247 kernel: mtnic0: [MPSAFE] Jan 15 19:28:04 sw247 kernel: mtnic0: [ITHREAD] Jan 15 19:28:04 sw247 kernel: msi: Assigning MSI-X IRQ 259 to local APIC 1 Jan 15 19:28:04 sw247 kernel: mtnic0: [MPSAFE] Jan 15 19:28:04 sw247 kernel: mtnic0: [ITHREAD] Jan 15 19:28:04 sw247 kernel: msi: Assigning MSI-X IRQ 260 to local APIC 2 Jan 15 19:28:04 sw247 kernel: mtnic0: [MPSAFE] Jan 15 19:28:04 sw247 kernel: mtnic0: [ITHREAD] Jan 15 19:28:04 sw247 kernel: msi: Assigning MSI-X IRQ 261 to local APIC 3 Jan 15 19:28:04 sw247 kernel: mtnic0: [MPSAFE] Jan 15 19:28:04 sw247 kernel: mtnic0: [ITHREAD] Jan 15 19:28:04 sw247 kernel: mtnic0: Port 1 - link up Jan 15 19:28:05 sw247 kernel: mtnic0: Port is down, ignoring multicast change. Jan 15 19:28:05 sw247 kernel: mtnic0: Change MTU called, driver is not running. flags:0x0 Jan 15 19:28:05 sw247 kernel: msi: Assigning MSI-X IRQ 262 to local APIC 0 Jan 15 19:28:05 sw247 kernel: mtnic0: [MPSAFE] Jan 15 19:28:05 sw247 kernel: mtnic0: [ITHREAD] Jan 15 19:28:05 sw247 kernel: msi: Assigning MSI-X IRQ 263 to local APIC 1 Jan 15 19:28:05 sw247 kernel: mtnic0: [MPSAFE] Jan 15 19:28:05 sw247 kernel: mtnic0: [ITHREAD] Jan 15 19:28:05 sw247 kernel: msi: Assigning MSI-X IRQ 264 to local APIC 2 Jan 15 19:28:05 sw247 kernel: mtnic0: [MPSAFE] Jan 15 19:28:05 sw247 kernel: mtnic0: [ITHREAD] Jan 15 19:28:05 sw247 kernel: msi: Assigning MSI-X IRQ 265 to local APIC 3 Jan 15 19:28:05 sw247 kernel: mtnic0: [MPSAFE] Jan 15 19:28:05 sw247 kernel: mtnic0: [ITHREAD] Jan 15 19:28:05 sw247 kernel: msi: Assigning MSI-X IRQ 266 to local APIC 0 Jan 15 19:28:05 sw247 kernel: mtnic0: [MPSAFE] Jan 15 19:28:05 sw247 kernel: mtnic0: [ITHREAD] Jan 15 19:28:05 sw247 kernel: mtnic0: Port 2 - link up Jan 15 19:28:05 sw247 kernel: mtnic1: Port is down, ignoring multicast change. Jan 15 19:28:05 sw247 kernel: Jan 15 19:28:05 sw247 kernel: mtnic1: Change MTU called, driver is not running. flags:0x0 Jan 15 19:28:05 sw247 kernel: Jan 15 19:28:05 sw247 kernel: msi: Assigning MSI-X IRQ 268 to local APIC 1 Jan 15 19:28:05 sw247 kernel: mtnic1: [MPSAFE] Jan 15 19:28:05 sw247 kernel: Jan 15 19:28:05 sw247 kernel: mtnic1: [ITHREAD] Jan 15 19:28:05 sw247 kernel: msi: Assigning MSI-X IRQ 269 to local APIC 2 Jan 15 19:28:05 sw247 kernel: mtnic1: [MPSAFE] Jan 15 19:28:05 sw247 kernel: Jan 15 19:28:05 sw247 kernel: mtnic1: [ITHREAD] Jan 15 19:28:05 sw247 kernel: msi: Assigning MSI-X IRQ 270 to local APIC 3 Jan 15 19:28:05 sw247 kernel: Jan 15 19:28:05 sw247 kernel: mtnic1: [MPSAFE] Jan 15 19:28:05 sw247 kernel: mtnic1: [ITHREAD] Jan 15 19:28:05 sw247 kernel: msi: Assigning MSI-X IRQ 271 to local APIC 0 Jan 15 19:28:05 sw247 kernel: Jan 15 19:28:05 sw247 kernel: mtnic1: [MPSAFE] Jan 15 19:28:05 sw247 kernel: mtnic1: [ITHREAD] Jan 15 19:28:05 sw247 kernel: msi: Assigning MSI-X IRQ 272 to local APIC 1 Jan 15 19:28:05 sw247 kernel: Jan 15 19:28:05 sw247 kernel: mtnic Jan 15 19:28:05 sw247 kernel: 1: [ Jan 15 19:28:05 sw247 kernel: MPSAF Jan 15 19:28:05 sw247 kernel: E] Jan 15 19:28:05 sw247 kernel: Jan 15 19:28:05 sw247 kernel: mtnic1: Jan 15 19:28:05 sw247 kernel: [ITH Jan 15 19:28:05 sw247 kernel: READ] Jan 15 19:28:05 sw247 kernel: Jan 15 19:28:05 sw247 kernel: mtnic1: Port is down, ignoring multicast change. Jan 15 19:28:05 sw247 kernel: mtnic1: Change MTU called, driver is not running. flags:0x0 Jan 15 19:28:05 sw247 kernel: msi: Assigning MSI-X IRQ 273 to local APIC 2 Jan 15 19:28:05 sw247 kernel: mtnic1: [MPSAFE] Jan 15 19:28:05 sw247 kernel: Jan 15 19:28:05 sw247 kernel: mtnic1: [ITHREAD] Jan 15 19:28:05 sw247 kernel: msi: Assigning MSI-X IRQ 274 to local APIC 3 Jan 15 19:28:05 sw247 kernel: Jan 15 19:28:05 sw247 kernel: mtnic1: [MPSAFE] Jan 15 19:28:05 sw247 kernel: mtnic1: [ITHREAD] Jan 15 19:28:05 sw247 kernel: msi: Assigning MSI-X IRQ 275 to local APIC 0 Jan 15 19:28:05 sw247 kernel: mtnic1: [MPSAFE] Jan 15 19:28:05 sw247 kernel: mtnic1: [ITHREAD] Jan 15 19:28:05 sw247 kernel: msi: Assigning MSI-X IRQ 276 to local APIC 1 Jan 15 19:28:05 sw247 kernel: mtnic1: [MPSAFE] Jan 15 19:28:05 sw247 kernel: mtnic1: [ITHREAD] Jan 15 19:28:05 sw247 kernel: msi: Assigning MSI-X IRQ 277 to local APIC 2 Jan 15 19:28:05 sw247 kernel: mtnic1: [MPSAFE] Jan 15 19:28:05 sw247 kernel: mtnic1: [ITHREAD] From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 17:48:56 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 5037F106564A; Thu, 15 Jan 2009 17:48:56 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 1EBF48FC12; Thu, 15 Jan 2009 17:48:55 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 2CA3C2184E8; Thu, 15 Jan 2009 12:45:00 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Thu, 15 Jan 2009 12:45:00 -0500 X-Sasl-enc: 3LYbA499XRQaOOvx9RtDBt7TUMGh4/4AIJ43pHXE10VI 1232041499 Received: from empiric.lon.incunabulum.net (radius-82-150-131-239.dsdeurne.nl [82.150.131.239]) by mail.messagingengine.com (Postfix) with ESMTPSA id 831B23A784; Thu, 15 Jan 2009 12:44:58 -0500 (EST) Message-ID: <496F7618.8050809@FreeBSD.org> Date: Thu, 15 Jan 2009 17:44:56 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.19 (X11/20090107) MIME-Version: 1.0 To: rea-fbsd@codelabs.ru References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> <496E11B7.3010608@sepehrs.com> <000b01c9768e$745aa160$220f000a@mtl.com> <496EF30E.4010304@sepehrs.com> <000c01c976ec$87e040b0$220f000a@mtl.com> <496F34D2.7050605@FreeBSD.org> <496F4FD1.4080602@FreeBSD.org> <+b/MqS4l8z9bOD9y4AZP70mtFL0@kjaK+/sQ5DW5981v71UogZJPf/0> In-Reply-To: <+b/MqS4l8z9bOD9y4AZP70mtFL0@kjaK+/sQ5DW5981v71UogZJPf/0> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Liran Liss , freebsd-net@freebsd.org, Oleg Kats , "'H.fazaeli'" , Yony Yossef , Eitan Shefi , freebsd-questions@freebsd.org Subject: Re: howto determine network device unit number? device.hints? 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, 15 Jan 2009 17:48:56 -0000 Eygene Ryabinkin wrote: > ... > I wanted to stress only one point: simple 'kldunload ' and > 'kldload ' makes devices to flip for Yony's case. This means > that unless some PCI hotplug stuff is here (which I don't believe to be > present, because no physical cards are touched and there is actually a > small amount of PCI hotplug support in FreeBSD), no physical PCI devices > get added or removed from the PCI child tree. It looks like that > something goes wrong during the PCI tree reprobe on the driver module > loading. > BTW: Thanks for looking further at the software layer first. VIM is a wee bit easier to use than a bus analyzer. Most motherboards don't support PCI geographical addressing, so... I wager it's the network driver code which may be the source of the problem, based on your analysis! If this code just doing a blind bump of an instance count and using that as a "unit number"... well, that's OK and expected for software virtual devices, but is counter-intuitive for something like hardware. But I don't have any mtnic source, so this is pure speculation on my part. > Correct me if I am wrong, but pci_driver_added from /sys/pci/pci.c will > invoke device_get_children() to get the list of the attached devices, > and for PCI case the list should be static. > Yup, that's right. > I guess that when Yony will enable verbose boot and will show us kernel > messages from two successive kldunload/kldload sequences, we will get > some additional information about what's going on. > Hopefully he will chime in... [bms does some google searching *before* he thinks about throwing his toys out of the pram at the Orignal.Poster.] ding :-) [a light bulb above bms' head] So... Yony. you're writing a driver. Maybe there's a bug in it? That's cool, dude. Hope it's a nice card and you plan on sharing the sweets with the rest of the class. ;-) But seriously, please mention that you are writing a driver in general questions you might ask about the whole system, otherwise, FreeBSD volunteers will run around going "Is core code broken?" and that's not so good for community stress levels as a whole. with lemonade, BMS From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 18:07: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 6DE8F1065674; Thu, 15 Jan 2009 18:07:37 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.189]) by mx1.freebsd.org (Postfix) with ESMTP id E7DB08FC24; Thu, 15 Jan 2009 18:07:36 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: by rn-out-0910.google.com with SMTP id j71so1285333rne.12 for ; Thu, 15 Jan 2009 10:07:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=+55ODQ09S9HFR/14cH7nNor2JtcZ6crb90j6Ok64kUU=; b=dHwHqJHmuHLoioeluSXfewXm2dMHNIOuVCoCW6+mvhmbTPf3LtGf/MFajMpa7RLn4b rgG2ARV6dy0V0wxA06zXXx8yXJKcvtKrQLQV4bKTz3Z/FD6sMNwINhfXBZR0gB76TaLH XEW0V3ix/VgcwfheEfcD/cQHzNb7Uo1+x0Mx4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=DOcOBJ9GpYYPqsAv/7usyFDXtAx+O74purZI0kWbWSc/4mpGuhd8vBH5m2YH7a3j8p sxzMSHqALUkeVPD4TxqAhC91O+p07z7uLBu+n3h0gidRMEcPzFVzN1yd2VoynvQ/Gmak cp5QMwZSzsa+VctCSMc3ANlo/oDZk9GUYIjnc= Received: by 10.150.228.2 with SMTP id a2mr3853332ybh.149.1232042856034; Thu, 15 Jan 2009 10:07:36 -0800 (PST) Received: by 10.150.229.15 with HTTP; Thu, 15 Jan 2009 10:07:35 -0800 (PST) Message-ID: <20def4870901151007s643f6910h1f6dca058852e4b1@mail.gmail.com> Date: Thu, 15 Jan 2009 20:07:35 +0200 From: "Yony Yossef" To: "Bruce M. Simpson" In-Reply-To: <496F7618.8050809@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> <496E11B7.3010608@sepehrs.com> <000b01c9768e$745aa160$220f000a@mtl.com> <496EF30E.4010304@sepehrs.com> <000c01c976ec$87e040b0$220f000a@mtl.com> <496F34D2.7050605@FreeBSD.org> <496F4FD1.4080602@FreeBSD.org> <+b/MqS4l8z9bOD9y4AZP70mtFL0@kjaK+/sQ5DW5981v71UogZJPf/0> <496F7618.8050809@FreeBSD.org> Cc: Liran Liss , freebsd-net@freebsd.org, Oleg Kats , "H.fazaeli" , Eitan Shefi , rea-fbsd@codelabs.ru, freebsd-questions@freebsd.org Subject: Re: howto determine network device unit number? device.hints? 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, 15 Jan 2009 18:07:38 -0000 > Eygene Ryabinkin wrote: > > ... > > I wanted to stress only one point: simple 'kldunload ' and > > 'kldload ' makes devices to flip for Yony's case. > This means > > that unless some PCI hotplug stuff is here (which I don't > believe to > > be present, because no physical cards are touched and there is > > actually a small amount of PCI hotplug support in FreeBSD), no > > physical PCI devices get added or removed from the PCI > child tree. It > > looks like that something goes wrong during the PCI tree reprobe on > > the driver module loading. > > > > BTW: Thanks for looking further at the software layer first. > > VIM is a wee bit easier to use than a bus analyzer. > > Most motherboards don't support PCI geographical addressing, > so... I wager it's the network driver code which may be the > source of the problem, based on your analysis! > > If this code just doing a blind bump of an instance count and > using that as a "unit number"... well, that's OK and expected > for software virtual devices, but is counter-intuitive for > something like hardware. > > But I don't have any mtnic source, so this is pure > speculation on my part. > > > Correct me if I am wrong, but pci_driver_added from /sys/pci/pci.c > > will invoke device_get_children() to get the list of the attached > > devices, and for PCI case the list should be static. > > > > Yup, that's right. > > > I guess that when Yony will enable verbose boot and will show us > > kernel messages from two successive kldunload/kldload sequences, we > > will get some additional information about what's going on. > > > > Hopefully he will chime in... > > [bms does some google searching *before* he thinks about > throwing his toys out of the pram at the Orignal.Poster.] > > ding :-) [a light bulb above bms' head] > > So... Yony. you're writing a driver. > Maybe there's a bug in it? > That's cool, dude. > Hope it's a nice card and you plan on sharing the sweets with > the rest of the class. ;-) > > But seriously, please mention that you are writing a driver > in general questions you might ask about the whole system, > otherwise, FreeBSD volunteers will run around going "Is core > code broken?" and that's not so good for community stress > levels as a whole. > > with lemonade, > BMS Sorry for risking the whole community with a massive heart attack Bruce :) Yes, I am writing a driver and yes, it still has a bug or two I guess.. About sharing it with the rest of the class, that's something I wanted to ask you guys: what's the procedure for a 10GigE driver to apply for the FreeBSD kernel? Mellanox has started porting it's products to FreeBSD about a year ago, hoping to see our 10GigE and InfiniBand drivers inbox next year. Yony From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 18:37: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 EF9DB1065676; Thu, 15 Jan 2009 18:37:43 +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 9398F8FC1C; Thu, 15 Jan 2009 18:37:43 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) 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 n0FICBK3081334; Thu, 15 Jan 2009 12:12:11 -0600 (CST) (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 n0FICBV2081333; Thu, 15 Jan 2009 12:12:11 -0600 (CST) (envelope-from brooks) Date: Thu, 15 Jan 2009 12:12:11 -0600 From: Brooks Davis To: Yony Yossef Message-ID: <20090115181211.GA81115@lor.one-eyed-alien.net> References: <20def4870901140009y1f007108y92797d5f79ffac08@mail.gmail.com> <496E11B7.3010608@sepehrs.com> <000b01c9768e$745aa160$220f000a@mtl.com> <496EF30E.4010304@sepehrs.com> <000c01c976ec$87e040b0$220f000a@mtl.com> <496F34D2.7050605@FreeBSD.org> <496F4FD1.4080602@FreeBSD.org> <+b/MqS4l8z9bOD9y4AZP70mtFL0@kjaK+/sQ5DW5981v71UogZJPf/0> <496F7618.8050809@FreeBSD.org> <20def4870901151007s643f6910h1f6dca058852e4b1@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+HP7ph2BbKc20aGI" Content-Disposition: inline In-Reply-To: <20def4870901151007s643f6910h1f6dca058852e4b1@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]); Thu, 15 Jan 2009 12:12:12 -0600 (CST) Cc: Liran Liss , freebsd-net@freebsd.org, Oleg Kats , "H.fazaeli" , rea-fbsd@codelabs.ru, Eitan Shefi , "Bruce M. Simpson" , freebsd-questions@freebsd.org Subject: Re: howto determine network device unit number? device.hints? 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, 15 Jan 2009 18:37:44 -0000 --+HP7ph2BbKc20aGI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 15, 2009 at 08:07:35PM +0200, Yony Yossef wrote: > > Eygene Ryabinkin wrote: > > > ... > > > I wanted to stress only one point: simple 'kldunload ' and > > > 'kldload ' makes devices to flip for Yony's case. > > This means > > > that unless some PCI hotplug stuff is here (which I don't > > believe to > > > be present, because no physical cards are touched and there is > > > actually a small amount of PCI hotplug support in FreeBSD), no > > > physical PCI devices get added or removed from the PCI > > child tree. It > > > looks like that something goes wrong during the PCI tree reprobe on > > > the driver module loading. > > > > > > > BTW: Thanks for looking further at the software layer first. > > > > VIM is a wee bit easier to use than a bus analyzer. > > > > Most motherboards don't support PCI geographical addressing, > > so... I wager it's the network driver code which may be the > > source of the problem, based on your analysis! > > > > If this code just doing a blind bump of an instance count and > > using that as a "unit number"... well, that's OK and expected > > for software virtual devices, but is counter-intuitive for > > something like hardware. > > > > But I don't have any mtnic source, so this is pure > > speculation on my part. > > > > > Correct me if I am wrong, but pci_driver_added from /sys/pci/pci.c > > > will invoke device_get_children() to get the list of the attached > > > devices, and for PCI case the list should be static. > > > > > > > Yup, that's right. > > > > > I guess that when Yony will enable verbose boot and will show us > > > kernel messages from two successive kldunload/kldload sequences, we > > > will get some additional information about what's going on. > > > > > > > Hopefully he will chime in... > > > > [bms does some google searching *before* he thinks about > > throwing his toys out of the pram at the Orignal.Poster.] > > > > ding :-) [a light bulb above bms' head] > > > > So... Yony. you're writing a driver. > > Maybe there's a bug in it? > > That's cool, dude. > > Hope it's a nice card and you plan on sharing the sweets with > > the rest of the class. ;-) > > > > But seriously, please mention that you are writing a driver > > in general questions you might ask about the whole system, > > otherwise, FreeBSD volunteers will run around going "Is core > > code broken?" and that's not so good for community stress > > levels as a whole. > > > > with lemonade, > > BMS >=20 > Sorry for risking the whole community with a massive heart attack Bruce :) > Yes, I am writing a driver and yes, it still has a bug or two I guess.. > About sharing it with the rest of the class, that's something I wanted > to ask you guys: what's the procedure for a 10GigE driver to apply > for the FreeBSD kernel? Pretty much just get it working, make sure it's licensed under a BSD, MIT, or ISC license (ideally, others are possible, but require more approval), and then find someone to review and commit it or sponsor the maintainer for a commit bit. =20 > Mellanox has started porting it's products to FreeBSD about a year > ago, hoping to see our 10GigE and InfiniBand drivers inbox next year. Excellent. -- Brooks >=20 > Yony > _______________________________________________ > 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 --+HP7ph2BbKc20aGI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iD8DBQFJb3x6XY6L6fI4GtQRAgLWAJwO108Llz3MltWJZ6PT8sa51g007QCfXvsB KaBJchcgQVnEQijFHWhcrnE= =y5TT -----END PGP SIGNATURE----- --+HP7ph2BbKc20aGI-- From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 21:11:19 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 283D51065702; Thu, 15 Jan 2009 21:11:19 +0000 (UTC) (envelope-from sonicy@otenet.gr) Received: from rosebud.otenet.gr (rosebud.otenet.gr [83.235.67.32]) by mx1.freebsd.org (Postfix) with ESMTP id 82BA98FC0C; Thu, 15 Jan 2009 21:11:18 +0000 (UTC) (envelope-from sonicy@otenet.gr) Received: from atlantis.dyndns.org (athedsl-4447372.home.otenet.gr [79.129.204.124]) by rosebud.otenet.gr (8.13.8/8.13.8/Debian-3) with ESMTP id n0FLBGIq030738; Thu, 15 Jan 2009 23:11:16 +0200 Message-ID: <496FA674.20002@otenet.gr> Date: Thu, 15 Jan 2009 23:11:16 +0200 From: Manolis Kiagias User-Agent: Thunderbird 2.0.0.17 (X11/20081011) MIME-Version: 1.0 To: Manolis Kiagias References: <200901150208.n0F28Hud060636@freefall.freebsd.org> <496ED3BD.3040906@otenet.gr> In-Reply-To: <496ED3BD.3040906@otenet.gr> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-7 Content-Transfer-Encoding: 7bit Cc: freebsd-net@FreeBSD.org, yongari@FreeBSD.org Subject: Re: kern/118897: [bfe] Kernel Panic acquiring IP address from DHCP server on newly enabled netcard 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, 15 Jan 2009 21:11:19 -0000 Manolis Kiagias wrote: > yongari@FreeBSD.org wrote: > >> Synopsis: [bfe] Kernel Panic acquiring IP address from DHCP server on newly enabled netcard >> >> State-Changed-From-To: open->feedback >> State-Changed-By: yongari >> State-Changed-When: Thu Jan 15 02:06:33 UTC 2009 >> State-Changed-Why: >> I think all known bugs in bfe(4) were fixed. >> Can you still reproduce the issue on 6.4-RELEASE or 7.1-RELEASE? >> >> >> Responsible-Changed-From-To: freebsd-net->yongari >> Responsible-Changed-By: yongari >> Responsible-Changed-When: Thu Jan 15 02:06:33 UTC 2009 >> Responsible-Changed-Why: >> Grab. >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=118897 >> >> >> >> > I'll give it a try this afternoon and let you know. > > Continuing with this, I just realized that the machine that replaced the one exhibiting this, does not have a bfe(4) but a bge(4). I no longer have access to any machine with bfe. FWIW, bge(4) works fine performing the same steps. Please feel free to close this report. From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 21:38:37 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 3B8131065673; Thu, 15 Jan 2009 21:38:37 +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 107648FC0A; Thu, 15 Jan 2009 21:38:37 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0FLca2f079978; Thu, 15 Jan 2009 21:38:36 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0FLcaCm079974; Thu, 15 Jan 2009 21:38:36 GMT (envelope-from linimon) Date: Thu, 15 Jan 2009 21:38:36 GMT Message-Id: <200901152138.n0FLcaCm079974@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: misc/130586: [re] if_re doesn't always attach to Realtek 8111C 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, 15 Jan 2009 21:38:37 -0000 Old Synopsis: if_re doesn't always attach to Realtek 8111C New Synopsis: [re] if_re doesn't always attach to Realtek 8111C Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Thu Jan 15 21:38:20 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=130586 From owner-freebsd-net@FreeBSD.ORG Thu Jan 15 21:59:13 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 6B1FA1065673 for ; Thu, 15 Jan 2009 21:59:13 +0000 (UTC) (envelope-from jostb2345@yahoo.de) Received: from web27006.mail.ukl.yahoo.com (web27006.mail.ukl.yahoo.com [217.146.177.6]) by mx1.freebsd.org (Postfix) with SMTP id B48478FC1D for ; Thu, 15 Jan 2009 21:59:12 +0000 (UTC) (envelope-from jostb2345@yahoo.de) Received: (qmail 44780 invoked by uid 60001); 15 Jan 2009 21:32:31 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.de; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=loMEOXclkw9n/7/24VN3V978/xELpXGGJgUUL3tITBgtLnnD1hO6wHyESFW2fKi+D4fvohLVtSib8bVPr0PHhbaFk7ntRwgbbKtEFRTfVSTM7OYhd17tqKZei6Vbkzz9074gjJMbXvcQO8b193n4UxHTq5zYsvARE/BeFO7YOug=; X-YMail-OSG: CopQfwoVM1ny.FihAOIyHu54ThAuNv8WC3gSS3AyRt6n88RxMstAmkhoHlpMOBY3cpy2lHqK2ohCShkp77MtCGQQDwTLxK0dcv21wrzl3Vugm7qNwuM9XGAWb3woe7NduAVRYp.QwnJjCF8RnEpxpziO3g-- Received: from [85.179.13.141] by web27006.mail.ukl.yahoo.com via HTTP; Thu, 15 Jan 2009 21:32:31 GMT X-Mailer: YahooMailWebService/0.7.260.1 Date: Thu, 15 Jan 2009 21:32:31 +0000 (GMT) From: Jost Boekemeier To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org In-Reply-To: <200901142324.n0ENOvTK040197@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <577907.44747.qm@web27006.mail.ukl.yahoo.com> Cc: Subject: Re: kern/96268: [socket] TCP socket performance drops by 3000% if packets are split at the first byte X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jostb2345@yahoo.de List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2009 21:59:13 -0000 Hi, from my point of view this issue can be closed.=20 TCP write/write/read sequences are bad on any operating system, it's just t= hat other OS are a little bit smarter. -- I think Jon Nagle has had a propo= sal to fix/remove this unconditional delay, but I don't know if it has been= implemented. Furthermore this problem has been fixed on application level. And I think P= atrick van Staveren maintains a FreeBSD port which uses unix domain- instea= d of TCP socket communication. Regards, Jost B=F6kemeier =0A=0A=0A From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 00:46: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 696A9106566B; Fri, 16 Jan 2009 00:46:39 +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 355538FC18; Fri, 16 Jan 2009 00:46:38 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id n0G0kaNg027820; Thu, 15 Jan 2009 16:46:36 -0800 (PST) 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: Thu, 15 Jan 2009 16:46:36 -0800 Message-ID: In-Reply-To: <3c1674c90901142046n6cd3c328kc0936190c2516a2a@mail.gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Bacula: VERY SLOW on SAME host Thread-Index: Acl2zE2Nia2Gm12QQjG/brk43Q8xigApxB6Q References: <3c1674c90901142046n6cd3c328kc0936190c2516a2a@mail.gmail.com> From: "Li, Qing" To: "Larry Rosenman" Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: RE: Bacula: VERY SLOW on SAME host 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, 16 Jan 2009 00:46:39 -0000 This is a known issue and it's easily reproducible using the=20 netperf tool. I am working on a permanent solution. In the meantime you can use the following workaround, as suggested by Kip: route add -host (if-ip) -iface lo0 -- Qing > -----Original Message----- > From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd- > current@freebsd.org] On Behalf Of Kip Macy > Sent: Wednesday, January 14, 2009 8:47 PM > To: Larry Rosenman > Cc: freebsd-current@freebsd.org > Subject: Re: Bacula: VERY SLOW on SAME host >=20 > arpv2 - add an localhost interface route as a workaround >=20 > -Kip >=20 > On Wed, Jan 14, 2009 at 8:35 PM, Larry Rosenman wrote: > > Greetings, > > Somethings changed (Around the 1st of the year?) where my bacula > jobs > > take FOREVER to backup on the same host > > with the StorageDaemon and Director. If I change it to use 127.0.0.1 > > instead of the address on the em card, it's fine. > > > > If I use the address on the em nics, it's like 4kb/sec as opposed to > > multi-megabytes/sec. > > > > I'm looking for how to find what broke. > > > > Other networking to the host is fine, but this is TCP within the same > host, > > but using the IP address on the em interface. > > > > I see the TCP Send-Q fill up, and it's extremely slow. > > > > What data do you need to help debug this? > > > > > > > > -- > > 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 > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current- > unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current- > unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 02:16:07 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 46BBE1065670; Fri, 16 Jan 2009 02:16:07 +0000 (UTC) (envelope-from yongari@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 358D98FC0A; Fri, 16 Jan 2009 02:16:07 +0000 (UTC) (envelope-from yongari@FreeBSD.org) Received: from freefall.freebsd.org (yongari@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0G2G7IP089840; Fri, 16 Jan 2009 02:16:07 GMT (envelope-from yongari@freefall.freebsd.org) Received: (from yongari@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0G2G7Sv089836; Fri, 16 Jan 2009 02:16:07 GMT (envelope-from yongari) Date: Fri, 16 Jan 2009 02:16:07 GMT Message-Id: <200901160216.n0G2G7Sv089836@freefall.freebsd.org> To: hrkfdn@gmail.com, yongari@FreeBSD.org, freebsd-net@FreeBSD.org, yongari@FreeBSD.org From: yongari@FreeBSD.org Cc: Subject: Re: kern/130586: [re] if_re doesn't always attach to Realtek 8111C 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, 16 Jan 2009 02:16:07 -0000 Synopsis: [re] if_re doesn't always attach to Realtek 8111C State-Changed-From-To: open->feedback State-Changed-By: yongari State-Changed-When: Fri Jan 16 02:14:46 UTC 2009 State-Changed-Why: I believe HEAD has fix for the issue. Would you try re(4) in HEAD? To get the re(4) of HEAD you may have to get following files from HEAD and rebuild kernel. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/re/if_re.c http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/if_rlreg.h http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/if_rl.c Responsible-Changed-From-To: freebsd-net->yongari Responsible-Changed-By: yongari Responsible-Changed-When: Fri Jan 16 02:14:46 UTC 2009 Responsible-Changed-Why: Grab. http://www.freebsd.org/cgi/query-pr.cgi?pr=130586 From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 02:30: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 3252E1065670 for ; Fri, 16 Jan 2009 02:30:24 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from QMTA09.emeryville.ca.mail.comcast.net (qmta09.emeryville.ca.mail.comcast.net [76.96.30.96]) by mx1.freebsd.org (Postfix) with ESMTP id 19B898FC16 for ; Fri, 16 Jan 2009 02:30:24 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from OMTA02.emeryville.ca.mail.comcast.net ([76.96.30.19]) by QMTA09.emeryville.ca.mail.comcast.net with comcast id 40tk1b0010QkzPwA92ERQX; Fri, 16 Jan 2009 02:14:25 +0000 Received: from [192.168.1.104] ([71.57.105.220]) by OMTA02.emeryville.ca.mail.comcast.net with comcast id 42EP1b0094lKpr38N2EQak; Fri, 16 Jan 2009 02:14:25 +0000 Message-ID: <496FED82.3000303@tomjudge.com> Date: Thu, 15 Jan 2009 20:14:26 -0600 From: Tom Judge User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: jostb2345@yahoo.de References: <577907.44747.qm@web27006.mail.ukl.yahoo.com> In-Reply-To: <577907.44747.qm@web27006.mail.ukl.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-net@FreeBSD.org, freebsd-bugs@FreeBSD.org, vwe@FreeBSD.org Subject: Re: kern/96268: [socket] TCP socket performance drops by 3000% if packets are split at the first byte 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, 16 Jan 2009 02:30:24 -0000 Jost Boekemeier wrote: > Hi, > > from my point of view this issue can be closed. > > TCP write/write/read sequences are bad on any operating system, it's just that other OS are a little bit smarter. -- I think Jon Nagle has had a proposal to fix/remove this unconditional delay, but I don't know if it has been implemented. > > Furthermore this problem has been fixed on application level. And I think Patrick van Staveren maintains a FreeBSD port which uses unix domain- instead of TCP socket communication. > > > Regards, > Jost Bökemeier > Hi Jost, I'm not sure if Patrick (I work with him) has a port using unix domain sockets in production. I do know however that patches to PHP (That add the no delay socket option to the sockets API) where submitted after we found the work around for this issue and they where accepted. And that we have a patched php java bridge client running in production. My response was just to say that I have also seen this bug on a more recent release. Regards Tom From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 04:24:19 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 47B0710656C5 for ; Fri, 16 Jan 2009 04:24:19 +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 1DBF58FC08 for ; Fri, 16 Jan 2009 04:24:19 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from localhost.lerctr.org ([127.0.0.1]:56714 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LNfzt-000D7n-8t; Thu, 15 Jan 2009 22:07:55 -0600 Received: from 76.205.169.61 (SquirrelMail authenticated user ler) by webmail.lerctr.org with HTTP; Thu, 15 Jan 2009 22:07:53 -0600 (CST) Message-ID: In-Reply-To: References: <3c1674c90901142046n6cd3c328kc0936190c2516a2a@mail.gmail.com> Date: Thu, 15 Jan 2009 22:07:53 -0600 (CST) From: "Larry Rosenman" To: "Li, Qing" User-Agent: SquirrelMail/1.4.17 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Spam-Score: -4.4 (----) X-LERCTR-Spam-Score: -4.4 (----) X-Spam-Report: SpamScore (-4.4/5.0) ALL_TRUSTED=-1.8,BAYES_00=-2.599 X-LERCTR-Spam-Report: SpamScore (-4.4/5.0) ALL_TRUSTED=-1.8,BAYES_00=-2.599 DomainKey-Status: no signature Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: RE: Bacula: VERY SLOW on SAME host 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, 16 Jan 2009 04:24:19 -0000 On Thu, January 15, 2009 6:46 pm, Li, Qing wrote: > This is a known issue and it's easily reproducible using the > netperf tool. > > I am working on a permanent solution. > > In the meantime you can use the following workaround, as suggested > by Kip: > > route add -host (if-ip) -iface lo0 > Thanks, Qing! If you have code you'd like me to test, feel free. On a related note, is the arp table supposed to be empty now? $ arp -an $ ping 192.168.200.5 PING 192.168.200.5 (192.168.200.5): 56 data bytes 64 bytes from 192.168.200.5: icmp_seq=0 ttl=255 time=0.810 ms 64 bytes from 192.168.200.5: icmp_seq=1 ttl=255 time=0.292 ms ^C --- 192.168.200.5 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.292/0.551/0.810/0.259 ms $ arp -an $ uname -a FreeBSD borg.lerctr.org 8.0-CURRENT FreeBSD 8.0-CURRENT #1: Wed Jan 14 17:16:03 CST 2009 root@borg.lerctr.org:/usr/obj/usr/src/sys/BORG amd64 $ > -- Qing > > >> -----Original Message----- >> From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd- >> current@freebsd.org] On Behalf Of Kip Macy >> Sent: Wednesday, January 14, 2009 8:47 PM >> To: Larry Rosenman >> Cc: freebsd-current@freebsd.org >> Subject: Re: Bacula: VERY SLOW on SAME host >> >> arpv2 - add an localhost interface route as a workaround >> >> -Kip >> >> On Wed, Jan 14, 2009 at 8:35 PM, Larry Rosenman > wrote: >> > Greetings, >> > Somethings changed (Around the 1st of the year?) where my bacula >> jobs >> > take FOREVER to backup on the same host >> > with the StorageDaemon and Director. If I change it to use > 127.0.0.1 >> > instead of the address on the em card, it's fine. >> > >> > If I use the address on the em nics, it's like 4kb/sec as opposed to >> > multi-megabytes/sec. >> > >> > I'm looking for how to find what broke. >> > >> > Other networking to the host is fine, but this is TCP within the > same >> host, >> > but using the IP address on the em interface. >> > >> > I see the TCP Send-Q fill up, and it's extremely slow. >> > >> > What data do you need to help debug this? >> > >> > >> > >> > -- >> > 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 >> > _______________________________________________ >> > freebsd-current@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-current >> > To unsubscribe, send any mail to "freebsd-current- >> unsubscribe@freebsd.org" >> > >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current- >> unsubscribe@freebsd.org" > -- 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 From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 05:05:01 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 17C9A106566B; Fri, 16 Jan 2009 05:05:01 +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 F186A8FC14; Fri, 16 Jan 2009 05:04:59 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id n0G54wUl017009; Thu, 15 Jan 2009 21:04:58 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Thu, 15 Jan 2009 21:04:53 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Bacula: VERY SLOW on SAME host Thread-Index: Acl3kAN8TZdnv+vVTamy1eWu6h2OTgABuiOv References: <3c1674c90901142046n6cd3c328kc0936190c2516a2a@mail.gmail.com> From: "Li, Qing" To: "Larry Rosenman" Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: RE: Bacula: VERY SLOW on SAME host 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, 16 Jan 2009 05:05:01 -0000 Hi Larry, This empty arp output issue appears to be a recent breakage on amd64. The world+kernel built on Jan. 12 out of my last commit for i386 (r187094) appears to be fine. The problem=20 is being investigated ... -- Qing -----Original Message----- From: Larry Rosenman [mailto:ler@lerctr.org] Sent: Thu 1/15/2009 8:07 PM To: Li, Qing Cc: freebsd-current@freebsd.org; freebsd-net@freebsd.org Subject: RE: Bacula: VERY SLOW on SAME host =20 On Thu, January 15, 2009 6:46 pm, Li, Qing wrote: > This is a known issue and it's easily reproducible using the > netperf tool. > > I am working on a permanent solution. > > In the meantime you can use the following workaround, as suggested > by Kip: > > route add -host (if-ip) -iface lo0 > Thanks, Qing! If you have code you'd like me to test, feel free. On a related note, is the arp table supposed to be empty now? $ arp -an $ ping 192.168.200.5 PING 192.168.200.5 (192.168.200.5): 56 data bytes 64 bytes from 192.168.200.5: icmp_seq=3D0 ttl=3D255 time=3D0.810 ms 64 bytes from 192.168.200.5: icmp_seq=3D1 ttl=3D255 time=3D0.292 ms ^C --- 192.168.200.5 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev =3D 0.292/0.551/0.810/0.259 ms $ arp -an $ uname -a FreeBSD borg.lerctr.org 8.0-CURRENT FreeBSD 8.0-CURRENT #1: Wed Jan 14 17:16:03 CST 2009 root@borg.lerctr.org:/usr/obj/usr/src/sys/BORG=20 amd64 $ > -- Qing > > >> -----Original Message----- >> From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd- >> current@freebsd.org] On Behalf Of Kip Macy >> Sent: Wednesday, January 14, 2009 8:47 PM >> To: Larry Rosenman >> Cc: freebsd-current@freebsd.org >> Subject: Re: Bacula: VERY SLOW on SAME host >> >> arpv2 - add an localhost interface route as a workaround >> >> -Kip >> >> On Wed, Jan 14, 2009 at 8:35 PM, Larry Rosenman > wrote: >> > Greetings, >> > Somethings changed (Around the 1st of the year?) where my bacula >> jobs >> > take FOREVER to backup on the same host >> > with the StorageDaemon and Director. If I change it to use > 127.0.0.1 >> > instead of the address on the em card, it's fine. >> > >> > If I use the address on the em nics, it's like 4kb/sec as opposed = to >> > multi-megabytes/sec. >> > >> > I'm looking for how to find what broke. >> > >> > Other networking to the host is fine, but this is TCP within the > same >> host, >> > but using the IP address on the em interface. >> > >> > I see the TCP Send-Q fill up, and it's extremely slow. >> > >> > What data do you need to help debug this? >> > >> > >> > >> > -- >> > 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 >> > _______________________________________________ >> > freebsd-current@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-current >> > To unsubscribe, send any mail to "freebsd-current- >> unsubscribe@freebsd.org" >> > >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current- >> unsubscribe@freebsd.org" > --=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 From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 08:29:01 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 4DB0B1065674; Fri, 16 Jan 2009 08:29:01 +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 22E8C8FC1C; Fri, 16 Jan 2009 08:29:01 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0G8T0m6005945; Fri, 16 Jan 2009 08:29:00 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0G8T0f1005941; Fri, 16 Jan 2009 08:29:00 GMT (envelope-from linimon) Date: Fri, 16 Jan 2009 08:29:00 GMT Message-Id: <200901160829.n0G8T0f1005941@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/130605: [tcp] Certain hardware produces "Network is unreachable" errors for scanning tools 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, 16 Jan 2009 08:29:01 -0000 Old Synopsis: Certain hardware produces "Network is unreachable" errors for scanning tools New Synopsis: [tcp] Certain hardware produces "Network is unreachable" errors for scanning tools Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Fri Jan 16 08:22:56 UTC 2009 Responsible-Changed-Why: I'm guessing this is a driver problem rather than 'tcp', but I'll use that as a placeholder for now. Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=130605 From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 08:59:30 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 830F310657A6 for ; Fri, 16 Jan 2009 08:59:30 +0000 (UTC) (envelope-from invite+ke5r5rmn@facebookmail.com) Received: from vipmx-out.facebook.com (outmail001.sctm.tfbnw.net [204.15.20.236]) by mx1.freebsd.org (Postfix) with ESMTP id 68ECB8FC19 for ; Fri, 16 Jan 2009 08:59:30 +0000 (UTC) (envelope-from invite+ke5r5rmn@facebookmail.com) Received: from localhost.localdomain ([10.18.255.175]) by vipmx-out.facebook.com [vipemail002.snc1.facebook.com] (8.13.1/8.13.6) with ESMTP id n0G8xUAd024292 for ; Fri, 16 Jan 2009 00:59:30 -0800 X-Facebook: from zuckmail by localhost.localdomain with local (ZuckMail); Date: Fri, 16 Jan 2009 00:59:30 -0800 To: Freebsd-net From: Dima Antipov Message-ID: <5e20420639e9f7c14343f571febd5f68@localhost.localdomain> X-Priority: 3 X-Mailer: ZuckMail [version 1.00] X-Facebook-Notify: general_invite Errors-To: invite+ke5r5rmn@facebookmail.com MIME-Version: 1.0 Content-Type: text/plain; charset = "UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: =?utf-8?q?D=C3=A9couvrez_mon_profil_Facebook?= X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dima Antipov List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2009 08:59:31 -0000 Bonjour Freebsd-net, J'ai cr=C3=A9=C3=A9 mon profil Facebook sur lequel je peux publier mes photos, mes vid=C3=A9os et des =C3=A9v=C3=A9nements. Je souhaite vous ajouter =C3=A0 mes amis pour que vous puissiez y acc=C3=A9der. Pour cela, vous devez d'abord vous inscrire =C3=A0 Facebook ! Vous pourrez ensuite cr=C3=A9er votre propre profil. Merci, Dima Pour vous inscrire =C3=A0 Facebook, suivez le lien ci-dessous : http://www.facebook.com/p.php?i=3D1186987124&k=3D6YF4Q4WYPYVM5CEIXFY6X3&r From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 09:10: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 317D010656ED; Fri, 16 Jan 2009 09:10:40 +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 F07218FC12; Fri, 16 Jan 2009 09:10:39 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id n0G9AZtl003614; Fri, 16 Jan 2009 01:10:36 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Fri, 16 Jan 2009 01:10:30 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Bacula: VERY SLOW on SAME host Thread-Index: Acl3kAN8TZdnv+vVTamy1eWu6h2OTgAKWA0j References: <3c1674c90901142046n6cd3c328kc0936190c2516a2a@mail.gmail.com> From: "Li, Qing" To: "Larry Rosenman" , Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: RE: Bacula: VERY SLOW on SAME host 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, 16 Jan 2009 09:10:52 -0000 Thanks to Pawel Jakub Dawidek, I found the empty "arp -an" output bug. The bug was introduced in my last commit that attempted at=20 providing some level of binary compatibility. Please sync file ./src/sys/net/rtsock.c to svn r187328=20 Thanks, -- Qing -----Original Message----- From: Larry Rosenman [mailto:ler@lerctr.org] Sent: Thu 1/15/2009 8:07 PM To: Li, Qing Cc: freebsd-current@freebsd.org; freebsd-net@freebsd.org Subject: RE: Bacula: VERY SLOW on SAME host =20 On Thu, January 15, 2009 6:46 pm, Li, Qing wrote: > This is a known issue and it's easily reproducible using the > netperf tool. > > I am working on a permanent solution. > > In the meantime you can use the following workaround, as suggested > by Kip: > > route add -host (if-ip) -iface lo0 > Thanks, Qing! If you have code you'd like me to test, feel free. On a related note, is the arp table supposed to be empty now? $ arp -an $ ping 192.168.200.5 PING 192.168.200.5 (192.168.200.5): 56 data bytes 64 bytes from 192.168.200.5: icmp_seq=3D0 ttl=3D255 time=3D0.810 ms 64 bytes from 192.168.200.5: icmp_seq=3D1 ttl=3D255 time=3D0.292 ms ^C --- 192.168.200.5 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev =3D 0.292/0.551/0.810/0.259 ms $ arp -an $ uname -a FreeBSD borg.lerctr.org 8.0-CURRENT FreeBSD 8.0-CURRENT #1: Wed Jan 14 17:16:03 CST 2009 root@borg.lerctr.org:/usr/obj/usr/src/sys/BORG=20 amd64 $ > -- Qing > > >> -----Original Message----- >> From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd- >> current@freebsd.org] On Behalf Of Kip Macy >> Sent: Wednesday, January 14, 2009 8:47 PM >> To: Larry Rosenman >> Cc: freebsd-current@freebsd.org >> Subject: Re: Bacula: VERY SLOW on SAME host >> >> arpv2 - add an localhost interface route as a workaround >> >> -Kip >> >> On Wed, Jan 14, 2009 at 8:35 PM, Larry Rosenman > wrote: >> > Greetings, >> > Somethings changed (Around the 1st of the year?) where my bacula >> jobs >> > take FOREVER to backup on the same host >> > with the StorageDaemon and Director. If I change it to use > 127.0.0.1 >> > instead of the address on the em card, it's fine. >> > >> > If I use the address on the em nics, it's like 4kb/sec as opposed = to >> > multi-megabytes/sec. >> > >> > I'm looking for how to find what broke. >> > >> > Other networking to the host is fine, but this is TCP within the > same >> host, >> > but using the IP address on the em interface. >> > >> > I see the TCP Send-Q fill up, and it's extremely slow. >> > >> > What data do you need to help debug this? >> > >> > >> > >> > -- >> > 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 >> > _______________________________________________ >> > freebsd-current@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-current >> > To unsubscribe, send any mail to "freebsd-current- >> unsubscribe@freebsd.org" >> > >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current- >> unsubscribe@freebsd.org" > --=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 From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 09:20: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 128F8106568F for ; Fri, 16 Jan 2009 09:20:23 +0000 (UTC) (envelope-from need4spam@bk.ru) Received: from f253.mail.ru (f253.mail.ru [194.186.55.139]) by mx1.freebsd.org (Postfix) with ESMTP id C45B18FC08 for ; Fri, 16 Jan 2009 09:20:22 +0000 (UTC) (envelope-from need4spam@bk.ru) Received: from mail by f253.mail.ru with local id 1LNksH-000M7S-00 for freebsd-net@freebsd.org; Fri, 16 Jan 2009 12:20:21 +0300 Received: from [62.182.89.99] by win.mail.ru with HTTP; Fri, 16 Jan 2009 12:20:21 +0300 From: Alexey Ivanov To: freebsd-net@freebsd.org Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: [62.182.89.99] Date: Fri, 16 Jan 2009 12:20:21 +0300 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: X-Spam: Not detected X-Mras: Ok Subject: TARPIT for pf/ipfw X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alexey Ivanov List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2009 09:20:23 -0000 Is there any command identical to: iptables -A INPUT -p tcp -m tcp -dport 80 -j TARPIT If no, does anyone ever tried to implement this feature? From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 09:54: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 F1D1D1065673 for ; Fri, 16 Jan 2009 09:54:24 +0000 (UTC) (envelope-from ivo.vachkov@gmail.com) Received: from mail-gx0-f21.google.com (mail-gx0-f21.google.com [209.85.217.21]) by mx1.freebsd.org (Postfix) with ESMTP id AA2B28FC12 for ; Fri, 16 Jan 2009 09:54:24 +0000 (UTC) (envelope-from ivo.vachkov@gmail.com) Received: by gxk14 with SMTP id 14so1689995gxk.19 for ; Fri, 16 Jan 2009 01:54:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=B36Atd7H8e2TyWyZiStHc0FZ9zds2gmtsgEFc8vOTj8=; b=SsvuMgqsTUMeCGAHB6D8XEuN1icHDG41lW3B33Jr+2YoQbeORoggMAxt8/MP92Ex25 BuXNZoh2ZU1VSk7DrpsAi+3VP+l8mVrtYw/Ucwm92kZoJrW9Gsvu4UDQloeUq+S6DZw4 MnpWs1pDWMZrMcZqGO91IH+2mU9MXnlOSz85c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=moz7BUorb7k+vLyUUG4E6ELt0jWkIAcLpT7pj39vNoH1kAUkb6XG/jHcEKFAR6ko3N wKRLPFgWO8LZ3rcQjilxhY4j4ZtroC9LHaK4gfmEal/6PPI5PL/2TN/dsKps+Lu3Ey4T geB7gnb5iHAbAclM8qfVPk7foeh1YXAkBq9rY= Received: by 10.150.216.3 with SMTP id o3mr5768869ybg.84.1232098302573; Fri, 16 Jan 2009 01:31:42 -0800 (PST) Received: by 10.151.26.9 with HTTP; Fri, 16 Jan 2009 01:31:42 -0800 (PST) Message-ID: Date: Fri, 16 Jan 2009 11:31:42 +0200 From: "Ivo Vachkov" To: "Alexey Ivanov" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-net@freebsd.org Subject: Re: TARPIT for pf/ipfw 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, 16 Jan 2009 09:54:25 -0000 what does TARPIT do ? On Fri, Jan 16, 2009 at 11:20 AM, Alexey Ivanov wrote: > Is there any command identical to: > iptables -A INPUT -p tcp -m tcp -dport 80 -j TARPIT > > If no, does anyone ever tried to implement this feature? > > _______________________________________________ > 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" > -- "UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity." Dennis Ritchie From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 10:06: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 63924106564A for ; Fri, 16 Jan 2009 10:06:31 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from smtp.zeninc.net (smtp.zeninc.net [80.67.176.25]) by mx1.freebsd.org (Postfix) with ESMTP id 1F2208FC20 for ; Fri, 16 Jan 2009 10:06:30 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from astro.zen.inc (astro.zen.inc [192.168.1.239]) by smtp.zeninc.net (smtpd) with ESMTP id 9C3A72798B8; Fri, 16 Jan 2009 11:06:29 +0100 (CET) Received: by astro.zen.inc (Postfix, from userid 1000) id 8048A1704B; Fri, 16 Jan 2009 11:11:39 +0100 (CET) Date: Fri, 16 Jan 2009 11:11:39 +0100 From: VANHULLEBUS Yvan To: Giulio Ferro Message-ID: <20090116101139.GA19489@zeninc.net> References: <49685F15.7080605@zirakzigil.org> <20090110100357.GB2718@zeninc.net> <49688A88.4080503@zirakzigil.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49688A88.4080503@zirakzigil.org> User-Agent: All mail clients suck. This one just sucks less. Cc: freebsd-net@freebsd.org Subject: Re: NATT patch on current 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, 16 Jan 2009 10:06:31 -0000 Hi. The netipsec.c patch should not have been present, it has probably been generated either by a manipulation error from myself or by some race condition between a svn up and a svn diff to produce the patch. Please test the following patch: http://people.freebsd.org/~vanhu/NAT-T/patch-natt-test-TRUNK-2009-01-16.diff It also have updated values for INP_ESPINUDP* flags, so you DO NEED to also recompile ipsec-tools !!! The patch has been generated from a new svn diff, so it will apply cleanly. It seems to compile, but I could NOT test it as I have strange compilation issues with some other part of kernel's sources (in ata/atapci/chipsets, on which I do not have any modifications...), even with a tree without modifications and a GENERIC kernel... If that patch is ok, I'll remove soon the previous patch (http://people.freebsd.org/~vanhu/NAT-T/patch-natt-test-HEAD-2008-07-21.diff) as it contains at least one wrong patch. Yvan. From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 10:21: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 EBC3F1065670 for ; Fri, 16 Jan 2009 10:21:55 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.190]) by mx1.freebsd.org (Postfix) with ESMTP id B60668FC25 for ; Fri, 16 Jan 2009 10:21:55 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by rn-out-0910.google.com with SMTP id j71so1625389rne.12 for ; Fri, 16 Jan 2009 02:21:55 -0800 (PST) MIME-Version: 1.0 Received: by 10.150.51.2 with SMTP id y2mr5829257yby.138.1232100006374; Fri, 16 Jan 2009 02:00:06 -0800 (PST) In-Reply-To: References: Date: Fri, 16 Jan 2009 12:00:06 +0200 Message-ID: From: Vlad GALU To: Ivo Vachkov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Alexey Ivanov Subject: Re: TARPIT for pf/ipfw 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, 16 Jan 2009 10:21:56 -0000 This particular iptables module keeps the incoming connection up and running, but it sends ACKs advertising a window size of 0 bytes, so that the remote end can't send any data until the local process has decided it's ok to do so. Basically it's used to slow down spammers and worms. On Fri, Jan 16, 2009 at 11:31 AM, Ivo Vachkov wrote: > what does TARPIT do ? > > On Fri, Jan 16, 2009 at 11:20 AM, Alexey Ivanov wrote: >> Is there any command identical to: >> iptables -A INPUT -p tcp -m tcp -dport 80 -j TARPIT >> >> If no, does anyone ever tried to implement this feature? >> >> _______________________________________________ >> 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" >> > > > > -- > "UNIX is basically a simple operating system, but you have to be a > genius to understand the simplicity." Dennis Ritchie > _______________________________________________ > 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" > -- ~/.signature: no such file or directory From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 10:53:58 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 E620110658AB for ; Fri, 16 Jan 2009 10:53:58 +0000 (UTC) (envelope-from dimitar.vassilev@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by mx1.freebsd.org (Postfix) with ESMTP id 9A7A28FC1F for ; Fri, 16 Jan 2009 10:53:58 +0000 (UTC) (envelope-from dimitar.vassilev@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so612619yxb.13 for ; Fri, 16 Jan 2009 02:53:58 -0800 (PST) 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=tdT0Uo4KcAsUc6dXuPQvzwyKDeuD66UffszuQQ42IBc=; b=Uw7BugIqlb1RnF3Swx5xw8p1tvN2HNV7wjGKHR443uRg7fhy5KrxqjCKiWQHxZQcNg Lp2LvE+YrTpi98lkiweRo5u/5a5Zm1g0+sxznjwC7at87HWA3QTuB5tK58OvgTyX9fgJ lVp/OVMOLQfG8egdVJa7Z4OO21XGkY0VcJ2LI= 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=x9WHOy52JF56jUffeB31u/jXjtnF0rMnlcJRN/arVFQUx8XVNesQxkjsjaa5NoBqpA MsBXTD1wASxnLSBnJO14Rrs+UO46AAzRNpVQ8WDVO2+Mqk/cNh4thVDVRDgtOBkl6QfW 9LJ+70IhLhO606iWEVOjTM/AVMjDDgssiX9Cs= MIME-Version: 1.0 Received: by 10.150.148.7 with SMTP id v7mr1150414ybd.68.1232103236259; Fri, 16 Jan 2009 02:53:56 -0800 (PST) In-Reply-To: References: Date: Fri, 16 Jan 2009 12:52:56 +0200 Message-ID: <59adc1a0901160252w2f4c47bbs66db4ab377024784@mail.gmail.com> From: Dimitar Vasilev To: Vlad GALU Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, Ivo Vachkov , Alexey Ivanov Subject: Re: TARPIT for pf/ipfw 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, 16 Jan 2009 10:53:59 -0000 see spamd for mail and you may use the don't peer list of sbl . 2009/1/16 Vlad GALU > This particular iptables module keeps the incoming connection up and > running, but it sends ACKs advertising a window size of 0 bytes, so > that the remote end can't send any data until the local process has > decided it's ok to do so. Basically it's used to slow down spammers > and worms. > > On Fri, Jan 16, 2009 at 11:31 AM, Ivo Vachkov > wrote: > > what does TARPIT do ? > > > > On Fri, Jan 16, 2009 at 11:20 AM, Alexey Ivanov wrote: > >> Is there any command identical to: > >> iptables -A INPUT -p tcp -m tcp -dport 80 -j TARPIT > >> > >> If no, does anyone ever tried to implement this feature? > >> > >> _______________________________________________ > >> 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" > >> > > > > > > > > -- > > "UNIX is basically a simple operating system, but you have to be a > > genius to understand the simplicity." Dennis Ritchie > > _______________________________________________ > > 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" > > > > > > -- > ~/.signature: no such file or directory > _______________________________________________ > 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 Fri Jan 16 10:53:59 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 09A2C10658B0 for ; Fri, 16 Jan 2009 10:53:59 +0000 (UTC) (envelope-from dimitar.vassilev@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.239]) by mx1.freebsd.org (Postfix) with ESMTP id CB7F58FC20 for ; Fri, 16 Jan 2009 10:53:58 +0000 (UTC) (envelope-from dimitar.vassilev@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1587074rvf.43 for ; Fri, 16 Jan 2009 02:53:58 -0800 (PST) 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=5SkEnIHkOI/MG3nyEyIw9bpUATDTZZOSDWPSb1iCfXE=; b=dMP/UZA+LchKXQmDsN5fqFGgKKk6E/c+0O6xVwgMecmk+BXggBKvOOOeymmUl6GI9N gOJe5Mal7cIwvw9TCtW9WL1Q9em+aRELMguw7E1U07Ions7Fgvo+CjsUmGE6AgWEnHqx SN/thI3YeNpFynPHef6OJ9pKdFSWrrz8wgPBg= 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=BerhGvTXDRO7eZSVzYY8pmLHqwpr90u130ED9b78W+7pSlPYqZaWtAm953R2Nkzy9I VZTLcZUhNR1BNYeXoJbSk+JdtLGCsIIk3OxLmJCbkO/5lw6UL8q0Lamilfv+vB1pVGTg hBvTLBR6c2ob07i/kmyU92l/Ihl8jBy66W4rg= MIME-Version: 1.0 Received: by 10.142.238.4 with SMTP id l4mr271312wfh.98.1232103238551; Fri, 16 Jan 2009 02:53:58 -0800 (PST) In-Reply-To: References: Date: Fri, 16 Jan 2009 12:53:58 +0200 Message-ID: <59adc1a0901160253me54571cl1799cafbf9634273@mail.gmail.com> From: Dimitar Vasilev To: Vlad GALU Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, Ivo Vachkov , Alexey Ivanov Subject: Re: TARPIT for pf/ipfw 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, 16 Jan 2009 10:54:00 -0000 see spamd for mail and you may use the don't peer list of sbl . 2009/1/16 Vlad GALU > This particular iptables module keeps the incoming connection up and > running, but it sends ACKs advertising a window size of 0 bytes, so > that the remote end can't send any data until the local process has > decided it's ok to do so. Basically it's used to slow down spammers > and worms. > > On Fri, Jan 16, 2009 at 11:31 AM, Ivo Vachkov > wrote: > > what does TARPIT do ? > > > > On Fri, Jan 16, 2009 at 11:20 AM, Alexey Ivanov wrote: > >> Is there any command identical to: > >> iptables -A INPUT -p tcp -m tcp -dport 80 -j TARPIT > >> > >> If no, does anyone ever tried to implement this feature? > >> > >> _______________________________________________ > >> 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" > >> > > > > > > > > -- > > "UNIX is basically a simple operating system, but you have to be a > > genius to understand the simplicity." Dennis Ritchie > > _______________________________________________ > > 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" > > > > > > -- > ~/.signature: no such file or directory > _______________________________________________ > 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 Fri Jan 16 11:07: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 582F8106566B for ; Fri, 16 Jan 2009 11:07:46 +0000 (UTC) (envelope-from dimitar.vassilev@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mx1.freebsd.org (Postfix) with ESMTP id 0FA108FC0C for ; Fri, 16 Jan 2009 11:07:45 +0000 (UTC) (envelope-from dimitar.vassilev@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so614613ywe.13 for ; Fri, 16 Jan 2009 03:07:45 -0800 (PST) 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=14xsknLyYlaDbyLPjDyM8V/DFUKGYXv7Y56dBVxkgzI=; b=J/5l6aVCCbOvtP1fEhW1qFd9+O990W81xTFzCipTJVkGd6mJZx73oy5BUVU3JjFzJB 32D+Tbo3CQ0qWMWHVmdZmevtXhnCjC0FmEsKmVJ3q3VBbcWpA1+Hr+wGgpNczDth4rKI 9bP8iVNGNwmoB3WXyONj4PmuE7Gy28B6p0o4k= 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=PzFtbNkrp3NkQRFmZesK0l4Gk1k70R9AhspBrAPjs9h9NKw603SogU9oa85SJUSEn2 WcXbQmkRSfyzzgGsHeLiP4CVLJG0JXTzP1ET4aavp6QH/IfmCGTUDndOEFko2CvbYNm4 TTEE1SoJswlCQDhAc4w2Xfz13pXq5XwxC5cc0= MIME-Version: 1.0 Received: by 10.150.139.8 with SMTP id m8mr3573818ybd.99.1232103176290; Fri, 16 Jan 2009 02:52:56 -0800 (PST) In-Reply-To: References: Date: Fri, 16 Jan 2009 12:52:56 +0200 Message-ID: <59adc1a0901160252w2f4c47bbs66db4ab377024784@mail.gmail.com> From: Dimitar Vasilev To: Vlad GALU Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, Ivo Vachkov , Alexey Ivanov Subject: Re: TARPIT for pf/ipfw 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, 16 Jan 2009 11:07:46 -0000 see spamd for mail and you may use the don't peer list of sbl . 2009/1/16 Vlad GALU > This particular iptables module keeps the incoming connection up and > running, but it sends ACKs advertising a window size of 0 bytes, so > that the remote end can't send any data until the local process has > decided it's ok to do so. Basically it's used to slow down spammers > and worms. > > On Fri, Jan 16, 2009 at 11:31 AM, Ivo Vachkov > wrote: > > what does TARPIT do ? > > > > On Fri, Jan 16, 2009 at 11:20 AM, Alexey Ivanov wrote: > >> Is there any command identical to: > >> iptables -A INPUT -p tcp -m tcp -dport 80 -j TARPIT > >> > >> If no, does anyone ever tried to implement this feature? > >> > >> _______________________________________________ > >> 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" > >> > > > > > > > > -- > > "UNIX is basically a simple operating system, but you have to be a > > genius to understand the simplicity." Dennis Ritchie > > _______________________________________________ > > 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" > > > > > > -- > ~/.signature: no such file or directory > _______________________________________________ > 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 Fri Jan 16 11:09: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 DFC4B10656F4 for ; Fri, 16 Jan 2009 11:09:46 +0000 (UTC) (envelope-from dimitar.vassilev@gmail.com) Received: from mail-gx0-f21.google.com (mail-gx0-f21.google.com [209.85.217.21]) by mx1.freebsd.org (Postfix) with ESMTP id 833818FC16 for ; Fri, 16 Jan 2009 11:09:46 +0000 (UTC) (envelope-from dimitar.vassilev@gmail.com) Received: by gxk14 with SMTP id 14so1709256gxk.19 for ; Fri, 16 Jan 2009 03:09:45 -0800 (PST) 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=1M0pvJ4L8ef2nSBRRUwbKu1CQiEJrluMn83uWDUMS8Y=; b=kT34jy2yuFNcmOLDtlEbwgkR0EDs0g4U5MSPVFjjKaSseyaGWQmbSRcAlKwrmJEQzY pyTODdzO9IBC/efw0J5Ca1rVc8lkB1QNwMFQunOwzIwx7ptGUnGzdzcFL7icRw1zNkjZ 3+etjlbK8qKFgCa4Tlf2545VjjsRXPJAMWVMg= 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=uPj8pc8fn7lpS+/Jy7uX8Wz5F2qBS4Ra2ZtGkMLOipbw+lnkanB2pnskt5nMFpWSU/ Jdyb2Bk8z/q62LafgsT8blbfixEqqCYJtLMi/XEIHYHZGKEHtau9qogkhBz831uG+yCw pPMM/36v6iMhWtxAqu9j0wg7+gV6j5cWNgttA= MIME-Version: 1.0 Received: by 10.150.156.9 with SMTP id d9mr5872905ybe.187.1232103206264; Fri, 16 Jan 2009 02:53:26 -0800 (PST) In-Reply-To: References: Date: Fri, 16 Jan 2009 12:52:56 +0200 Message-ID: <59adc1a0901160252w2f4c47bbs66db4ab377024784@mail.gmail.com> From: Dimitar Vasilev To: Vlad GALU Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, Ivo Vachkov , Alexey Ivanov Subject: Re: TARPIT for pf/ipfw 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, 16 Jan 2009 11:09:47 -0000 see spamd for mail and you may use the don't peer list of sbl . 2009/1/16 Vlad GALU > This particular iptables module keeps the incoming connection up and > running, but it sends ACKs advertising a window size of 0 bytes, so > that the remote end can't send any data until the local process has > decided it's ok to do so. Basically it's used to slow down spammers > and worms. > > On Fri, Jan 16, 2009 at 11:31 AM, Ivo Vachkov > wrote: > > what does TARPIT do ? > > > > On Fri, Jan 16, 2009 at 11:20 AM, Alexey Ivanov wrote: > >> Is there any command identical to: > >> iptables -A INPUT -p tcp -m tcp -dport 80 -j TARPIT > >> > >> If no, does anyone ever tried to implement this feature? > >> > >> _______________________________________________ > >> 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" > >> > > > > > > > > -- > > "UNIX is basically a simple operating system, but you have to be a > > genius to understand the simplicity." Dennis Ritchie > > _______________________________________________ > > 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" > > > > > > -- > ~/.signature: no such file or directory > _______________________________________________ > 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 Fri Jan 16 12:05: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 3C56B1065ABF for ; Fri, 16 Jan 2009 12:05:50 +0000 (UTC) (envelope-from john@roof1.dnepro.net) Received: from roof1.dnepro.net (a66.dnepro.net [212.3.111.66]) by mx1.freebsd.org (Postfix) with ESMTP id 5EB0F8FC1A for ; Fri, 16 Jan 2009 12:05:48 +0000 (UTC) (envelope-from john@roof1.dnepro.net) Received: from roof1.dnepro.net (localhost [127.0.0.1]) by roof1.dnepro.net (8.14.3/8.14.3) with ESMTP id n0GBoQAN023862 for ; Fri, 16 Jan 2009 13:50:26 +0200 (EET) (envelope-from john@roof1.dnepro.net) Received: (from john@localhost) by roof1.dnepro.net (8.14.3/8.14.3/Submit) id n0GBoQQw023861 for freebsd-net@freebsd.org; Fri, 16 Jan 2009 13:50:26 +0200 (EET) (envelope-from john) Date: Fri, 16 Jan 2009 13:50:26 +0200 From: Eugene Perevyazko To: freebsd-net@freebsd.org Message-ID: <20090116115026.GA98057@roof1.dnepro.net> Mail-Followup-To: freebsd-net@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.94, clamav-milter version 0.94 on roof1.dnepro.net X-Virus-Status: Clean Subject: Re: TARPIT for pf/ipfw 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, 16 Jan 2009 12:06:06 -0000 On Fri, Jan 16, 2009 at 12:20:21PM +0300, Alexey Ivanov wrote: > Is there any command identical to: > iptables -A INPUT -p tcp -m tcp -dport 80 -j TARPIT > > If no, does anyone ever tried to implement this feature? I'm thinking on implementing it in ipfw but it'll be a week or two later, when I will have some free time. Eugene Perevyazko From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 12:40:26 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 A34231065686 for ; Fri, 16 Jan 2009 12:40:26 +0000 (UTC) (envelope-from dudu.meyer@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.173]) by mx1.freebsd.org (Postfix) with ESMTP id 7B72F8FC17 for ; Fri, 16 Jan 2009 12:40:26 +0000 (UTC) (envelope-from dudu.meyer@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so1744104wfg.7 for ; Fri, 16 Jan 2009 04:40:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=Qe+n8loGzUsMQt/1hAIxHT+5SmT85c4Kii9l82sQVDc=; b=Sq8giHQiIJS0bXMZSHyttfKz7k04PEh8Gg03irUFsr3O/uxzWQDXBKy7tt9t2XoFAI /+j1LrL0KiStXJG6fNxnTTLNkrXqxfZufbMMIZ18NWIQ77wA8gLwtIKCcWs7mYH7ef1N LuJoISdTWcggy+uXE/0Q/qCiifm3LGT0gXaZg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=wldwpnctUvoEiphjcyLNKHejaCZPTNwtQVZjqh8CD379Okdpsve4psFIxBrJ7xWsJH z/zv94YjtvI2AIre8gIraQ4io4AiIlD5VK5fG1Juaf4BrCE5r18s8+q/u8CwWRFbqbxT svkB2kR6MpDJtDeEnalHmUg7x7eVDa5KtpgRI= MIME-Version: 1.0 Received: by 10.142.173.14 with SMTP id v14mr1012912wfe.245.1232108054869; Fri, 16 Jan 2009 04:14:14 -0800 (PST) Date: Fri, 16 Jan 2009 10:14:14 -0200 Message-ID: From: Eduardo Meyer To: net@freebsd.org, current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Multiple Routing Tables (FIB) + IPFW problem as (I?) expected 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, 16 Jan 2009 12:40:26 -0000 Hello, I am trying the new FIB stuff on -STABLE with IPFW, I made many tests and it did not work as I expected. Quick testing: # lynx -dump http://www.whatismyip.org 200.165.75.10 # setfib -1 lynx -dump http://www.whatismyip.org 189.52.141.2 # setfib -2 lynx -dump http://www.whatismyip.org 201.91.92.154 # ipfw -q flush # ipfw add 1 setfib 1 all from any to any 00001 setfib 1 ip from any to any # lynx -dump http://www.whatismyip.org 200.165.75.10 Check for counters: # ipfw -q add 2 allow all from any to any fib 1 # ipfw show 00001 388599 139653215 setfib 1 ip from any to any 00002 4253 2221474 allow ip from any to any fib 1 65535 2419650 983279227 allow ip from any to any # lynx -dump http://www.whatismyip.org 200.165.75.10 # setfib -1 lynx -dump http://www.whatismyip.org 189.52.141.2 Is anything wrong with my concepts? I would like to know if -CURRENT has the same behavior, can someone please test? -- =========== Eduardo Meyer pessoal: dudu.meyer@gmail.com profissional: ddm.farmaciap@saude.gov.br From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 13:00: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 234931065677 for ; Fri, 16 Jan 2009 13:00: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 E39B28FC1E for ; Fri, 16 Jan 2009 13:00:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0GD03Ur007748 for ; Fri, 16 Jan 2009 13:00:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0GD03ea007747; Fri, 16 Jan 2009 13:00:03 GMT (envelope-from gnats) Date: Fri, 16 Jan 2009 13:00:03 GMT Message-Id: <200901161300.n0GD03ea007747@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Marc Peters Cc: Subject: Re: kern/128917: [wpi] [panic] if_wpi and wpa+tkip causing kernel panic X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marc Peters List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2009 13:00:04 -0000 The following reply was made to PR kern/128917; it has been noted by GNATS. From: Marc Peters To: bug-followup@FreeBSD.org, kitambi@epicsol.org Cc: Subject: Re: kern/128917: [wpi] [panic] if_wpi and wpa+tkip causing kernel panic Date: Fri, 16 Jan 2009 13:34:29 +0100 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am hitting this too on a network with an airport extreme access point when it uses "WPA/WPA2". With these Security Setting Apple just uses TKIP and trying to force FreeBSD to use AES-CCMP in /etc/wpa_supplicant.conf doesn't work, e.g. wpi cannot connect to the network. Using only WPA2 on this access point will provide AES and no more panics. here is some additional information as suggested on the STABLE-ML: from a textdump: msgbuf.txt: [snipping dmesg and startup-messages] Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0xffff fault code = supervisor read, page not present instruction pointer = 0x20:0xc0e70dfc stack pointer = 0x28:0xe58bbbe0 frame pointer = 0x28:0xe58bbc9c 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 = 25 (wpi0 taskq) ddb.txt (just bt output here): db> bt Tracing pid 25 tid 100024 td 0xc5189af0 wpi_ops(c52c5000,1,c0b7cf36,0,0,...) at wpi_ops+0x89c taskqueue_run(c52ab200,c52ab21c,0,c0b7cf36,0,...) at taskqueue_run+0x175 taskqueue_thread_loop(c52c69b4,e58bbd38,0,0,0,...) at taskqueue_thread_loop+0xbb fork_exit(c07fb2b0,c52c69b4,e58bbd38) at fork_exit+0x99 fork_trampoline() at fork_trampoline+0x8 - --- trap 0, eip = 0, esp = 0xe58bbd70, ebp = 0 --- version.txt: FreeBSD 7.1-STABLE #0: Thu Jan 15 13:51:12 CET 2009 root@lappi.agentur.local:/usr/obj/usr/src/sys/DEBUG_DRM gdb gdb> file /boot/YOUR_KERNEL/if_wpi.ko Reading symbols from /boot/kernel/if_wpi.ko...Reading symbols from /boot/kernel/if_wpi.ko.symbols...done. gdb> l *wpi_ops+0x89c 0x9dfc is in wpi_ops (/usr/src/sys/modules/wpi/../../dev/wpi/if_wpi.c:2411). 2406 /* update adapter's configuration */ 2407 sc->config.associd = 0; 2408 sc->config.filter &= ~htole32(WPI_FILTER_BSS); 2409 IEEE80211_ADDR_COPY(sc->config.bssid, ni->ni_bssid); 2410 sc->config.chan = ieee80211_chan2ieee(ic, ni->ni_chan); 2411 if (IEEE80211_IS_CHAN_2GHZ(ni->ni_chan)) { 2412 sc->config.flags |= htole32(WPI_CONFIG_AUTO | 2413 WPI_CONFIG_24GHZ); 2414 } 2415 switch (ic->ic_curmode) { -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAklwftUACgkQCnBgS+kUGEtEDwCeLB9z3ynmx9yyXcl3+DTJqTyk 5XQAnRY2PTpFlWrF+5bQqN7ygkV9tMch =XAks -----END PGP SIGNATURE----- From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 13:12:16 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 B87CE1065672 for ; Fri, 16 Jan 2009 13:12:16 +0000 (UTC) (envelope-from lists.br@gmail.com) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6AEE48FC1B for ; Fri, 16 Jan 2009 13:12:16 +0000 (UTC) (envelope-from lists.br@gmail.com) Received: by el-out-1112.google.com with SMTP id z25so429005ele.18 for ; Fri, 16 Jan 2009 05:12:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to:references :subject:date:mime-version:content-type:content-transfer-encoding :x-priority:x-msmail-priority:x-mailer:x-mimeole; bh=Ff5VNjHtZpmkRzG0/PtFsWo7SIa3DPKGrm7VGez83jc=; b=rlaV80AjlJzbFeocf0S2jGocVxzQB9yBqPVscbjWuVzEuCMjoeFTcX/yF31HIeF8/h c94wPefTx+T+Dhac7v6gxWMFY03yjVwAiLmDVIidTY5RSXztNVEz7Eg3eyuTHgcgi75g JaPeV1EyQ/gsUhr9/2dw9/XxsqjdCY4/5Vnuk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:references:subject:date:mime-version :content-type:content-transfer-encoding:x-priority:x-msmail-priority :x-mailer:x-mimeole; b=xtFZF6Zk9tPiYJf/4q3q40CoGmCuoQfz9cnLib26sWKlZZ2zv7zDrwcApu54uDXp0p 3zwMi/1L0rdG/urJApNnGT8tyWnnvs9Psh/ZujMMuUZvp50CGaGE4lhIUWuPzBmOlP+3 3oNFE5nLD+ltVhEwFegtAUXJuaSV9fEwPkNwE= Received: by 10.90.88.16 with SMTP id l16mr1314362agb.3.1232110247906; Fri, 16 Jan 2009 04:50:47 -0800 (PST) Received: from adnote989 (189-46-93-120.dsl.telesp.net.br [189.46.93.120]) by mx.google.com with ESMTPS id 6sm1005251agd.2.2009.01.16.04.50.46 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 16 Jan 2009 04:50:47 -0800 (PST) Message-ID: <43745E4B2C034B1F8657F115B9E5DDA8@adnote989> From: "Luiz Otavio O Souza" To: "Eduardo Meyer" , References: Date: Fri, 16 Jan 2009 10:50:37 -0200 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.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Mailman-Approved-At: Fri, 16 Jan 2009 13:36:44 +0000 Cc: Subject: Re: Multiple Routing Tables (FIB) + IPFW problem as (I?) expected 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, 16 Jan 2009 13:12:17 -0000 > Hello, > > I am trying the new FIB stuff on -STABLE with IPFW, I made many tests > and it did not work as I expected. > > Quick testing: > > # lynx -dump http://www.whatismyip.org > 200.165.75.10 > > # setfib -1 lynx -dump http://www.whatismyip.org > 189.52.141.2 > > # setfib -2 lynx -dump http://www.whatismyip.org > 201.91.92.154 > > # ipfw -q flush > # ipfw add 1 setfib 1 all from any to any > 00001 setfib 1 ip from any to any > > # lynx -dump http://www.whatismyip.org > 200.165.75.10 > > Check for counters: > > # ipfw -q add 2 allow all from any to any fib 1 > # ipfw show > 00001 388599 139653215 setfib 1 ip from any to any > 00002 4253 2221474 allow ip from any to any fib 1 > 65535 2419650 983279227 allow ip from any to any > > # lynx -dump http://www.whatismyip.org > 200.165.75.10 > > # setfib -1 lynx -dump http://www.whatismyip.org > 189.52.141.2 > > Is anything wrong with my concepts? I would like to know if -CURRENT > has the same behavior, can someone please test? > > -- > =========== > Eduardo Meyer > pessoal: dudu.meyer@gmail.com > profissional: ddm.farmaciap@saude.gov.br Eduardo, This will not work this way... The socket used by lynx (in this case) get its data is routed by the default fib table (1) before ipfw can see the packet. When ipfw rule is applied the packet is already routed and you wont get what you want. As far as i know (not too much :)) you will need to use the fwd rules to redirect the local packets. Setfib rules work for packets that are comming from an interface and need to be routed to another (non local traffic). Setfib will not re-route the packet. Luiz From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 19:37:52 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 E27FA106566B; Fri, 16 Jan 2009 19:37:52 +0000 (UTC) (envelope-from prvs=julian=26000d075@elischer.org) Received: from smtp-outbound.ironport.com (smtp-outbound.ironport.com [63.251.108.112]) by mx1.freebsd.org (Postfix) with ESMTP id B2F9F8FC0C; Fri, 16 Jan 2009 19:37:52 +0000 (UTC) (envelope-from prvs=julian=26000d075@elischer.org) Received: from unknown (HELO julian-mac.elischer.org) ([10.251.60.21]) by smtp-outbound.ironport.com with ESMTP; 16 Jan 2009 11:09:27 -0800 Message-ID: <4970DB6C.4030200@elischer.org> Date: Fri, 16 Jan 2009 11:09:32 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: Eduardo Meyer References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org, net@freebsd.org Subject: Re: Multiple Routing Tables (FIB) + IPFW problem as (I?) expected 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, 16 Jan 2009 19:37:53 -0000 Eduardo Meyer wrote: > Hello, > > I am trying the new FIB stuff on -STABLE with IPFW, I made many tests > and it did not work as I expected. > > Quick testing: > > # lynx -dump http://www.whatismyip.org > 200.165.75.10 > > # setfib -1 lynx -dump http://www.whatismyip.org > 189.52.141.2 > > # setfib -2 lynx -dump http://www.whatismyip.org > 201.91.92.154 > so you have 3 tables with different default routes? > # ipfw -q flush > # ipfw add 1 setfib 1 all from any to any > 00001 setfib 1 ip from any to any > > # lynx -dump http://www.whatismyip.org > 200.165.75.10 > > Check for counters: > > # ipfw -q add 2 allow all from any to any fib 1 > # ipfw show obviously you did some other commands here.. something generated 2 million packets.. > 00001 388599 139653215 setfib 1 ip from any to any > 00002 4253 2221474 allow ip from any to any fib 1 > 65535 2419650 983279227 allow ip from any to any > > # lynx -dump http://www.whatismyip.org > 200.165.75.10 > > # setfib -1 lynx -dump http://www.whatismyip.org > 189.52.141.2 > > Is anything wrong with my concepts? I would like to know if -CURRENT > has the same behavior, can someone please test? this is expected.. setfib in the firewall can only change the fib on an outgoing packet AFTER it has already done its routing decision. setfib in ipfw is basically for packets that you are ROUTING, (i.e. you are a gateway) and is expected to be run in INCOMING packets before they make their routing decision.. I was thinking of adding a 'reroute' ipfw keyword.. kind of like 'fwd {original dest} ip from any to any' because 'fwd' does cause the routing decision to be redone. The fib of the process that opens the socket controls where packets from the local machine are sent. From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 19:58: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 1C042106564A; Fri, 16 Jan 2009 19:58:18 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E659D8FC1E; Fri, 16 Jan 2009 19:58:17 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (gavin@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0GJwHKT021016; Fri, 16 Jan 2009 19:58:17 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0GJwHui021012; Fri, 16 Jan 2009 19:58:17 GMT (envelope-from gavin) Date: Fri, 16 Jan 2009 19:58:17 GMT Message-Id: <200901161958.n0GJwHui021012@freefall.freebsd.org> To: gavin@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: kern/130628: NFS / rpc.lockd deadlock on 7.1-R 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, 16 Jan 2009 19:58:18 -0000 Synopsis: NFS / rpc.lockd deadlock on 7.1-R Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: gavin Responsible-Changed-When: Fri Jan 16 19:55:38 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). Looks like there should be pretty much all the info here necessary to figure this out. To submitter: are you using TCP or UDP NFS mounts? http://www.freebsd.org/cgi/query-pr.cgi?pr=130628 From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 20:24: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 4D7371065673; Fri, 16 Jan 2009 20:24:16 +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 238BC8FC14; Fri, 16 Jan 2009 20:24:15 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from 64.3.1.253.ptr.us.xo.net ([64.3.1.253]:44398 helo=LROSENMAN) by thebighonker.lerctr.org with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LNvEi-000Ljk-2c; Fri, 16 Jan 2009 14:24:13 -0600 From: "Larry Rosenman" To: "'Li, Qing'" , References: <3c1674c90901142046n6cd3c328kc0936190c2516a2a@mail.gmail.com> In-Reply-To: Date: Fri, 16 Jan 2009 14:24:01 -0600 Message-ID: <006501c97818$64f732c0$2ee59840$@org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acl3kAN8TZdnv+vVTamy1eWu6h2OTgAKWA0jABe8FSA= Content-Language: en-us X-Spam-Score: -2.4 (--) X-LERCTR-Spam-Score: -2.4 (--) X-Spam-Report: SpamScore (-2.4/5.0) ALL_TRUSTED=-1.8, BAYES_00=-2.599, TVD_RCVD_IP=1.931, TW_SV=0.077 X-LERCTR-Spam-Report: SpamScore (-2.4/5.0) ALL_TRUSTED=-1.8, BAYES_00=-2.599, TVD_RCVD_IP=1.931, TW_SV=0.077 DomainKey-Status: no signature Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: RE: Bacula: VERY SLOW on SAME host 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, 16 Jan 2009 20:24:17 -0000 verified to fix the arp problem! Thanks, Qing! -- 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-current@freebsd.org [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Li, Qing Sent: Friday, January 16, 2009 3:11 AM To: Larry Rosenman; ato@iem.pw.edu.pl Cc: freebsd-net@freebsd.org; freebsd-current@freebsd.org Subject: RE: Bacula: VERY SLOW on SAME host Thanks to Pawel Jakub Dawidek, I found the empty "arp -an" output bug. The bug was introduced in my last commit that attempted at providing some level of binary compatibility. Please sync file ./src/sys/net/rtsock.c to svn r187328 Thanks, -- Qing -----Original Message----- From: Larry Rosenman [mailto:ler@lerctr.org] Sent: Thu 1/15/2009 8:07 PM To: Li, Qing Cc: freebsd-current@freebsd.org; freebsd-net@freebsd.org Subject: RE: Bacula: VERY SLOW on SAME host On Thu, January 15, 2009 6:46 pm, Li, Qing wrote: > This is a known issue and it's easily reproducible using the > netperf tool. > > I am working on a permanent solution. > > In the meantime you can use the following workaround, as suggested > by Kip: > > route add -host (if-ip) -iface lo0 > Thanks, Qing! If you have code you'd like me to test, feel free. On a related note, is the arp table supposed to be empty now? $ arp -an $ ping 192.168.200.5 PING 192.168.200.5 (192.168.200.5): 56 data bytes 64 bytes from 192.168.200.5: icmp_seq=0 ttl=255 time=0.810 ms 64 bytes from 192.168.200.5: icmp_seq=1 ttl=255 time=0.292 ms ^C --- 192.168.200.5 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.292/0.551/0.810/0.259 ms $ arp -an $ uname -a FreeBSD borg.lerctr.org 8.0-CURRENT FreeBSD 8.0-CURRENT #1: Wed Jan 14 17:16:03 CST 2009 root@borg.lerctr.org:/usr/obj/usr/src/sys/BORG amd64 $ > -- Qing > > >> -----Original Message----- >> From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd- >> current@freebsd.org] On Behalf Of Kip Macy >> Sent: Wednesday, January 14, 2009 8:47 PM >> To: Larry Rosenman >> Cc: freebsd-current@freebsd.org >> Subject: Re: Bacula: VERY SLOW on SAME host >> >> arpv2 - add an localhost interface route as a workaround >> >> -Kip >> >> On Wed, Jan 14, 2009 at 8:35 PM, Larry Rosenman > wrote: >> > Greetings, >> > Somethings changed (Around the 1st of the year?) where my bacula >> jobs >> > take FOREVER to backup on the same host >> > with the StorageDaemon and Director. If I change it to use > 127.0.0.1 >> > instead of the address on the em card, it's fine. >> > >> > If I use the address on the em nics, it's like 4kb/sec as opposed to >> > multi-megabytes/sec. >> > >> > I'm looking for how to find what broke. >> > >> > Other networking to the host is fine, but this is TCP within the > same >> host, >> > but using the IP address on the em interface. >> > >> > I see the TCP Send-Q fill up, and it's extremely slow. >> > >> > What data do you need to help debug this? >> > >> > >> > >> > -- >> > 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 >> > _______________________________________________ >> > freebsd-current@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-current >> > To unsubscribe, send any mail to "freebsd-current- >> unsubscribe@freebsd.org" >> > >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current- >> unsubscribe@freebsd.org" > -- 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 _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 21:37:57 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 E42FC1065677 for ; Fri, 16 Jan 2009 21:37:57 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by mx1.freebsd.org (Postfix) with ESMTP id CA3C38FC2D for ; Fri, 16 Jan 2009 21:37:57 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay10.apple.com (relay10.apple.com [17.128.113.47]) by mail-out3.apple.com (Postfix) with ESMTP id ACCD94CB3412; Fri, 16 Jan 2009 13:21:15 -0800 (PST) Received: from relay10.apple.com (unknown [127.0.0.1]) by relay10.apple.com (Symantec Brightmail Gateway) with ESMTP id 94E0C28050; Fri, 16 Jan 2009 13:21:15 -0800 (PST) X-AuditID: 1180712f-ac171bb0000012d3-3c-4970fa4b3075 Received: from cswiger1.apple.com (cswiger1.apple.com [17.227.140.124]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay10.apple.com (Apple SCV relay) with ESMTP id 7A6DD2805C; Fri, 16 Jan 2009 13:21:15 -0800 (PST) Message-Id: <06EC1210-8D3E-4F47-A1DE-F0AE038929D9@mac.com> From: Chuck Swiger To: Eugene Perevyazko In-Reply-To: <20090116115026.GA98057@roof1.dnepro.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Fri, 16 Jan 2009 13:21:15 -0800 References: <20090116115026.GA98057@roof1.dnepro.net> X-Mailer: Apple Mail (2.930.3) X-Brightmail-Tracker: AAAAAA== Cc: freebsd-net@freebsd.org Subject: Re: TARPIT for pf/ipfw 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, 16 Jan 2009 21:37:58 -0000 On Jan 16, 2009, at 3:50 AM, Eugene Perevyazko wrote: > On Fri, Jan 16, 2009 at 12:20:21PM +0300, Alexey Ivanov wrote: >> Is there any command identical to: >> iptables -A INPUT -p tcp -m tcp -dport 80 -j TARPIT >> >> If no, does anyone ever tried to implement this feature? > > I'm thinking on implementing it in ipfw but it'll be a week or two > later, > when I will have some free time. Note that net/honeyd and security/labrea offer somewhat similar functionality. -- -Chuck From owner-freebsd-net@FreeBSD.ORG Fri Jan 16 22:45:56 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 16CB1106564A; Fri, 16 Jan 2009 22:45:56 +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 E1ADD8FC16; Fri, 16 Jan 2009 22:45:55 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0GMjtEv049825; Fri, 16 Jan 2009 22:45:55 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0GMjteM049821; Fri, 16 Jan 2009 22:45:55 GMT (envelope-from linimon) Date: Fri, 16 Jan 2009 22:45:55 GMT Message-Id: <200901162245.n0GMjteM049821@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: conf/130555: [rc.d] [patch] No good way to set ipfilter variables at boot time 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, 16 Jan 2009 22:45:56 -0000 Old Synopsis: [patch] No good way to set ipfilter variables at boot time New Synopsis: [rc.d] [patch] No good way to set ipfilter variables at boot time Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Fri Jan 16 22:44:56 UTC 2009 Responsible-Changed-Why: Perhaps the folks on -net can evaluate this. http://www.freebsd.org/cgi/query-pr.cgi?pr=130555 From owner-freebsd-net@FreeBSD.ORG Sat Jan 17 00:50: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 17C79106564A; Sat, 17 Jan 2009 00:50:33 +0000 (UTC) (envelope-from jason.dicioccio@ods.org) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by mx1.freebsd.org (Postfix) with ESMTP id 2F5678FC1B; Sat, 17 Jan 2009 00:50:31 +0000 (UTC) (envelope-from jason.dicioccio@ods.org) Received: by nf-out-0910.google.com with SMTP id h3so287317nfh.33 for ; Fri, 16 Jan 2009 16:50:31 -0800 (PST) Received: by 10.210.20.17 with SMTP id 17mr3960824ebt.37.1232153430858; Fri, 16 Jan 2009 16:50:30 -0800 (PST) Received: by 10.210.11.1 with HTTP; Fri, 16 Jan 2009 16:50:30 -0800 (PST) Message-ID: Date: Fri, 16 Jan 2009 16:50:30 -0800 From: "Jason DiCioccio" To: vwe@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200812311353.mBVDraLJ042040@freefall.freebsd.org> Cc: freebsd-net@freebsd.org, freebsd-bugs@freebsd.org, bugs-followup@freebsd.org Subject: Re: kern/130059: [panic] Leaking 50k mbufs/hour 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, 17 Jan 2009 00:50:33 -0000 I narrowed this bug down to the following patch to djb's ucspi-tcp (adds ipv6 functionality): http://www.fefe.de/ucspi/ I don't think that userland processes should be able to wreak that much havoc on the network stack. Another thing of note is that even if I kill the processes causing the problem, the mbufs are never reclaimed. Seems like a permanent leak. When I got rid of the ipv6 patch, the mbufs stopped building up and everything has been fine.. Note that the ipv6 traffic for this process was fairly minimal. From owner-freebsd-net@FreeBSD.ORG Sat Jan 17 01:00:15 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 ABC94106566B for ; Sat, 17 Jan 2009 01:00:15 +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 9B1818FC14 for ; Sat, 17 Jan 2009 01:00:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0H10534047006 for ; Sat, 17 Jan 2009 01:00:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0H105sr047005; Sat, 17 Jan 2009 01:00:05 GMT (envelope-from gnats) Date: Sat, 17 Jan 2009 01:00:05 GMT Message-Id: <200901170100.n0H105sr047005@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: "Jason DiCioccio" Cc: Subject: Re: kern/130059: [panic] Leaking 50k mbufs/hour X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jason DiCioccio List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2009 01:00:15 -0000 The following reply was made to PR kern/130059; it has been noted by GNATS. From: "Jason DiCioccio" To: bug-followup@freebsd.org Cc: Subject: Re: kern/130059: [panic] Leaking 50k mbufs/hour Date: Fri, 16 Jan 2009 16:51:47 -0800 I narrowed this bug down to the following patch to djb's ucspi-tcp (adds ipv6 functionality): http://www.fefe.de/ucspi/ I don't think that userland processes should be able to wreak that much havoc on the network stack. Another thing of note is that even if I kill the processes causing the problem, the mbufs are never reclaimed. Seems like a permanent leak. When I got rid of the ipv6 patch, the mbufs stopped building up and everything has been fine.. Note that the ipv6 traffic for this process was fairly minimal. From owner-freebsd-net@FreeBSD.ORG Sat Jan 17 15:50: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 C971C106566B; Sat, 17 Jan 2009 15:50:55 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id 71BC58FC1D; Sat, 17 Jan 2009 15:50:55 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1LOD3l-000K1O-UF; Sat, 17 Jan 2009 17:26:06 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n0HFQ0vL004415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 17 Jan 2009 17:26:00 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n0HFPxe8005055; Sat, 17 Jan 2009 17:25:59 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n0HFPxS0005054; Sat, 17 Jan 2009 17:25:59 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 17 Jan 2009 17:25:59 +0200 From: Kostik Belousov To: yongari@freebsd.org Message-ID: <20090117152559.GN48057@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/JIF1IJL1ITjxcV4" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1LOD3l-000K1O-UF ab8a21edc69eeb16a04b3e08aeced1f8 X-Terabit: YES Cc: freebsd-net@freebsd.org Subject: age(4) corrupts packets 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, 17 Jan 2009 15:50:56 -0000 --/JIF1IJL1ITjxcV4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I have to use a machine with ASUS motherboard, that has age(4) ethernet adapter. It seems that active use of the net causes corrupted frames, like the following ssh disconnect (after doing find / in the shell): Disconnecting: Corrupted MAC on input. Machine runs reasonably latest stable/7. Any advice ? Anything I should try to tweak ? Do you need additional information ? I can test patches on this box. age0: mem 0xfeac0000-0xfeafffff irq 17 at device 0.0 on pci2 age0: Reserved 0x40000 bytes for rid 0x10 type 3 at 0xfeac0000 age0: PCI device revision : 0x00b0 age0: Chip id/revision : 0x9006 age0: 1280 Tx FIFO, 2364 Rx FIFO age0: MSIX count : 0 age0: MSI count : 1 age0: attempting to allocate 1 MSI vectors (1 supported) msi: routing MSI IRQ 256 to vector 52 age0: using IRQ 256 for MSI age0: Using 1 MSI messages. age0: Read request size : 512 bytes. age0: TLP payload size : 128 bytes. age0: PCI VPD capability not found! miibus0: on age0 atphy0: PHY 0 on miibus0 atphy0: OUI 0x001374, model 0x0001, rev. 5 atphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto age0: bpf attached age0: Ethernet address: 00:1f:c6:b9:cc:a7 msi: Assigning MSI IRQ 256 to local APIC 0 --/JIF1IJL1ITjxcV4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAklx+IcACgkQC3+MBN1Mb4iFagCeLD9Jiyo3GG9E52gJQcMP8Aun LowAoNKMR0tCdvqMQoNMxg09m5mqs+ja =QQFa -----END PGP SIGNATURE----- --/JIF1IJL1ITjxcV4-- From owner-freebsd-net@FreeBSD.ORG Sat Jan 17 17:25: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 7E096106566B for ; Sat, 17 Jan 2009 17:25:18 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: from web63908.mail.re1.yahoo.com (web63908.mail.re1.yahoo.com [69.147.97.123]) by mx1.freebsd.org (Postfix) with SMTP id 253BE8FC18 for ; Sat, 17 Jan 2009 17:25:17 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: (qmail 93162 invoked by uid 60001); 17 Jan 2009 16:58:37 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Message-ID; b=SrBXSoviSIXyjERwOGvhSBQAHz3rno2NNZxRG4DbXWhR5rTe1AD/AxrzYErdRPgU3+N5Yf/NTAldXvb+ITAhGbQS6L9RleDvuAJvF9k6uTVRynsUHC3RxesTwgA5oPINKn/2l3qDAc8vA1SV+bUPo7Uk6Kk0ZU35MEOmUzcE1J0=; X-YMail-OSG: ksmCfBkVM1nT1KPPwSV7XdNp9NNUPYCY80RZaUG_7eplgDG4T5T8GEiHeCIdTo_.G3zQZr5ZB46dN02D1H8fYLMYZW.LxmlFHDSrcOSvwphlYUdg4IKntfsbekDbnF90NGkXA_kLsgZgcQMaI70ylZ_GT90WAFkjFeFZcYMtfMQ7WHIZsFM8HpnZEA-- Received: from [98.242.222.229] by web63908.mail.re1.yahoo.com via HTTP; Sat, 17 Jan 2009 08:58:37 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Sat, 17 Jan 2009 08:58:37 -0800 (PST) From: Barney Cordoba To: yongari@freebsd.org, Kostik Belousov In-Reply-To: <20090117152559.GN48057@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <144876.14982.qm@web63908.mail.re1.yahoo.com> Cc: freebsd-net@freebsd.org Subject: Re: age(4) corrupts packets X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: barney_cordoba@yahoo.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2009 17:25:18 -0000 Use a plug in card. ASUS always puts junk on their MBs. --- On Sat, 1/17/09, Kostik Belousov wrote: > From: Kostik Belousov > Subject: age(4) corrupts packets > To: yongari@freebsd.org > Cc: freebsd-net@freebsd.org > Date: Saturday, January 17, 2009, 10:25 AM > I have to use a machine with ASUS motherboard, that has > age(4) ethernet > adapter. It seems that active use of the net causes > corrupted frames, > like the following ssh disconnect (after doing find / in > the shell): > Disconnecting: Corrupted MAC on input. > > Machine runs reasonably latest stable/7. > > Any advice ? Anything I should try to tweak ? Do you need > additional > information ? > > I can test patches on this box. > > age0: > mem 0xfeac0000-0xfeafffff irq 17 at device 0.0 on pci2 > age0: Reserved 0x40000 bytes for rid 0x10 type 3 at > 0xfeac0000 > age0: PCI device revision : 0x00b0 > age0: Chip id/revision : 0x9006 > age0: 1280 Tx FIFO, 2364 Rx FIFO > age0: MSIX count : 0 > age0: MSI count : 1 > age0: attempting to allocate 1 MSI vectors (1 supported) > msi: routing MSI IRQ 256 to vector 52 > age0: using IRQ 256 for MSI > age0: Using 1 MSI messages. > age0: Read request size : 512 bytes. > age0: TLP payload size : 128 bytes. > age0: PCI VPD capability not found! > miibus0: on age0 > atphy0: PHY 0 on miibus0 > atphy0: OUI 0x001374, model 0x0001, rev. 5 > atphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, > 1000baseT-FDX, auto > age0: bpf attached > age0: Ethernet address: 00:1f:c6:b9:cc:a7 > msi: Assigning MSI IRQ 256 to local APIC 0 From owner-freebsd-net@FreeBSD.ORG Sat Jan 17 20:28: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 F291E1065670 for ; Sat, 17 Jan 2009 20:28:51 +0000 (UTC) (envelope-from prt@prt.org) Received: from smtp5.uk.umis.net (smtp5.uk.umis.net [217.65.166.40]) by mx1.freebsd.org (Postfix) with ESMTP id BE9BA8FC13 for ; Sat, 17 Jan 2009 20:28:51 +0000 (UTC) (envelope-from prt@prt.org) Received: from kate.prtsystems.ltd.uk ([217.65.165.35]) by smtp5.uk.umis.net with esmtpa (Exim 4.63 (FreeBSD)) (envelope-from ) id 1LOHT5-000BnU-Ne for freebsd-net@freebsd.org; Sat, 17 Jan 2009 20:08:31 +0000 Message-ID: <49723ABE.6010409@prt.org> Date: Sat, 17 Jan 2009 20:08:30 +0000 From: Paul Thornton User-Agent: Thunderbird 2.0.0.19 (Windows/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: pppoed problem with reconnections 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, 17 Jan 2009 20:28:52 -0000 Hi folks, I am currently doing some lab testing with 6.3-release and a pppoe setup where each user has their own VLAN. On the termination box have an em interface with about 200 VLANs configured on it, and have a ppp.conf looking like this: default: set log Chat Command Phase enable pap enable chap allow mode direct set mru 1462 set mtu 1462 set timeout 0 enable lqr accept dns set dns 192.168.1.1 192.168.1.2 set radius /etc/ppp/radius.conf set ifaddr 192.168.254.254/32 cv1001e: set device PPPoE:vlan1001:cv1001 cv1002e: set device PPPoE:vlan1002:cv1002 cv1003e: set device PPPoE:vlan1003:cv1003 cv1004e: set device PPPoE:vlan1004:cv1004 (and so on for several pages) There are multiple pppoed processes running, one for each VLAN (this might seem wasteful but there are other reasons for doing it this way). All user authentication and IP address assignment is handled by the radius server, and each user ID has a static IP address. The problem I'm seeing is as follows: - PPPoE connection comes in, is authenticated, and a ppp process is exec()ed by pppoed. - This connection has the user's IP address, say 192.168.254.1. - Everything works as expected. This is a Good Thing. - The PPPoE connection is then not disconnected cleanly (say network cable pulled out, or machine reboots, etc) - Back on the termination box, there is still a ppp process running using that address. - When you try and reconnect as the original user, it fails because the address cannot be assigned (already in use). Things then stay like this for ever until I kill the ppp process that was connected with the pppoed running on that VLAN. I don't want to set a timeout as I want these sessions to be always on. Is there any way to configure pppoed to kill the old ppp process before trying to launch the new one, so the IP address is released? I guess I'm asking the reverse of the age old "how do I deny multiple logins" question - how do I allow it, but have the new one boot the old one off? Thanks, Paul. From owner-freebsd-net@FreeBSD.ORG Sat Jan 17 21:32:24 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 E08A51065678; Sat, 17 Jan 2009 21:32:24 +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 B65368FC2C; Sat, 17 Jan 2009 21:32:24 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0HLWOgH036910; Sat, 17 Jan 2009 21:32:24 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0HLWOpg036904; Sat, 17 Jan 2009 21:32:24 GMT (envelope-from linimon) Date: Sat, 17 Jan 2009 21:32:24 GMT Message-Id: <200901172132.n0HLWOpg036904@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/130652: [kernel] [patch] Possible deadlock in rt_check() (sys/net/route.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: Sat, 17 Jan 2009 21:32:25 -0000 Old Synopsis: Possible deadlock in rt_check() (sys/net/route.c) New Synopsis: [kernel] [patch] Possible deadlock in rt_check() (sys/net/route.c) Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sat Jan 17 21:31:56 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=130652