From owner-freebsd-net@FreeBSD.ORG Mon Feb 16 00:46: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 182C11065674 for ; Mon, 16 Feb 2009 00:46:40 +0000 (UTC) (envelope-from php_webmaster@kvetinywaniek.cz) Received: from mailadmin.rpsnet.cz (mail.rpsnet.cz [88.103.228.10]) by mx1.freebsd.org (Postfix) with ESMTP id 9909B8FC12 for ; Mon, 16 Feb 2009 00:46:39 +0000 (UTC) (envelope-from php_webmaster@kvetinywaniek.cz) Received: from localhost (localhost [127.0.0.1]) by mailadmin.rpsnet.cz (Postfix) with ESMTP id 5331C781B58 for ; Mon, 16 Feb 2009 01:18:37 +0100 (CET) Received: from mailadmin.rpsnet.cz ([127.0.0.1]) by localhost ( [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24085-01-11 for ; Mon, 16 Feb 2009 01:18:37 +0100 (CET) Received: by mailadmin.rpsnet.cz (Postfix, from userid 1005) id 68FDF781C0B; Mon, 16 Feb 2009 01:18:11 +0100 (CET) To: freebsd-net@freebsd.org From: Bank of Baroda. Content-Transfer-Encoding: 8bit Message-Id: <20090216001811.68FDF781C0B@mailadmin.rpsnet.cz> Date: Mon, 16 Feb 2009 01:18:11 +0100 (CET) X-Virus-Scanned: amavisd-new at X-Amavis-Alert: BAD HEADER Improper use of control character (char 0D hex) in message header 'From': From: Bank of Baroda. \r\n MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: BOB Alert: Please Read This** X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2009 00:46:40 -0000 [1]Bank of Baroda [2][USEMAP:weblinks_india.gif] [3]Click to register for regular updates Dear Baroda Customer, We recently reviewed your account because we know your past experience, we are to protect your account from being accessed by an unauthorized third party. Therefore, as a preventative measure, we have temporarily limited access to sensitive account features. To restore your account access, we need you to confirm your identity, to do so click the secure link below and proceed to verify your information: [4]http://bobibanking.com Important Notice You are strictly advised to match your sensitive details correctly to avoid further complications. Thank for Banking with Us. Bank of Baroda Online Customer Service [brown1.gif] [5]Powered by Emovez © 2008 Bank of Baroda. All rights reserved. [6]Disclaimer For optimum view of this site you must have IE 5.0 and 1024 by 768 pixels References 1. http://www.bankofbaroda.co.in/ 2. LYNXIMGMAP:file://localhost/tmp/tmpd99Mng.html#Map 3. file://localhost/register.asp 4. http://www.mynettransact.com/baroda.php?bank=www.bankofbaroda.com 5. http://www.e-movez.com/ 6. file://localhost/disclaimer.asp From owner-freebsd-net@FreeBSD.ORG Mon Feb 16 03:04:41 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 ACFFB10656BE; Mon, 16 Feb 2009 03:04:41 +0000 (UTC) (envelope-from sat@freebsd.org) Received: from smtp3.powertech.no (smtp3.powertech.no [195.159.0.178]) by mx1.freebsd.org (Postfix) with ESMTP id 69FFC8FC14; Mon, 16 Feb 2009 03:04:41 +0000 (UTC) (envelope-from sat@freebsd.org) Received: from vettviten.no (unknown [195.159.103.46]) by smtp3.powertech.no (Postfix) with ESMTP id 34901209396; Mon, 16 Feb 2009 03:42:47 +0100 (CET) Date: Mon, 16 Feb 2009 03:42:42 +0100 Received: from localhost ([127.0.0.1]) by vettviten.no; Mon, 16 Feb 2009 03:42:39 +0100 From: =?Windows-1251?B?wuvg5A==?= To: freebsd-net@freebsd.org Message-Id: <20090216024247.34901209396@smtp3.powertech.no> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1251" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: =?windows-1251?b?z/Du5ODsIPHx++vq6CDxIPHg6fLu4iDt4CBuYXJvZC5y?= =?windows-1251?q?u?= X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: chizh-k@narod.ru List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2009 03:04:43 -0000 Ïðîäàì òåêñòîâûå ññûëêè ñ ñàéòîâ: [1]http://holodnoeleto.narod.ru ÏÐ4 ÒÈÖ 200 [2]http://christystudio.narod.ru ÏÐ0 ÒÈÖ 300 [3]http://larinaksusha.narod.ru ÏÐ3 ÒÈÖ 120 [4]http://via-gra1.narod.ru ÏÐ0 ÒÈÖ 325 [5]http://zoostation.narod.ru ÏÐ2 ÒÈÖ 300 Ðàññìîòðþ âàðèàíòû äîëãîñðî÷íîãî ñîòðóäíè÷åñòâà. ICQ 407484954 References 1. http://holodnoeleto.narod.ru/ 2. http://christystudio.narod.ru/ 3. http://larinaksusha.narod.ru/ 4. http://via-gra1.narod.ru/ 5. http://zoostation.narod.ru/ From owner-freebsd-net@FreeBSD.ORG Mon Feb 16 06:33:46 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 48139106564A; Mon, 16 Feb 2009 06:33:46 +0000 (UTC) (envelope-from az@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1EEAC8FC14; Mon, 16 Feb 2009 06:33:46 +0000 (UTC) (envelope-from az@FreeBSD.org) Received: from freefall.freebsd.org (az@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n1G6XjbC056447; Mon, 16 Feb 2009 06:33:45 GMT (envelope-from az@freefall.freebsd.org) Received: (from az@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1G6XjvN056435; Mon, 16 Feb 2009 06:33:45 GMT (envelope-from az) Date: Mon, 16 Feb 2009 06:33:45 GMT Message-Id: <200902160633.n1G6XjvN056435@freefall.freebsd.org> To: andrey.zverev@electro-com.ru, az@FreeBSD.org, freebsd-net@FreeBSD.org From: az@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: Mon, 16 Feb 2009 06:33:46 -0000 Synopsis: [bge] packet loose and linkup problem State-Changed-From-To: open->closed State-Changed-By: az State-Changed-When: Mon Feb 16 06:33:44 UTC 2009 State-Changed-Why: As originator close this PR, since i can not check this situation on newest releases. http://www.freebsd.org/cgi/query-pr.cgi?pr=106974 From owner-freebsd-net@FreeBSD.ORG Mon Feb 16 09:53:44 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 536071065670; Mon, 16 Feb 2009 09:53:44 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 27BF38FC0C; Mon, 16 Feb 2009 09:53:44 +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 n1G9riET039220; Mon, 16 Feb 2009 09:53:44 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1G9riqj039216; Mon, 16 Feb 2009 09:53:44 GMT (envelope-from linimon) Date: Mon, 16 Feb 2009 09:53:44 GMT Message-Id: <200902160953.n1G9riqj039216@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/131738: [re] re0: watchdog timeout (missed Tx interrupts) -- recovering X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2009 09:53:44 -0000 Synopsis: [re] re0: watchdog timeout (missed Tx interrupts) -- recovering Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Mon Feb 16 09:53:32 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=131738 From owner-freebsd-net@FreeBSD.ORG Mon Feb 16 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 1C135106566B for ; Mon, 16 Feb 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 05C8C8FC0C for ; Mon, 16 Feb 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 n1GB6uET096207 for ; Mon, 16 Feb 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 n1GB6tRg096203 for freebsd-net@FreeBSD.org; Mon, 16 Feb 2009 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 16 Feb 2009 11:06:55 GMT Message-Id: <200902161106.n1GB6tRg096203@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, 16 Feb 2009 11:06:58 -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/131738 net [re] re0: watchdog timeout (missed Tx interrupts) -- r o bin/131567 net [socket] [patch] Update for regression/sockets/unix_cm o kern/131549 net ifconfig(8) can't clear 'monitor' mode on the wireless o kern/131536 net [netinet] [patch] kernel does allow manipulation of su o bin/131365 net route(8): route add changes interpretation of network o kern/131310 net [panic] 7.1 panics with mpd netgraph interface changes o kern/131162 net [ath] Atheros driver bugginess and kernel crashes o kern/131153 net [iwi] iwi doesn't see a wireless network f kern/131087 net [ipw] [panic] ipw / iwi - no sent/received packets; iw o kern/130846 net [vge] vge0 not autonegotiating to 1000baseTX full dupl o kern/130820 net [ndis] wpa_supplicant(8) returns 'no space on device' o kern/130652 net [kernel] [patch] Possible deadlock in rt_check() (sys/ o kern/130628 net [nfs] NFS / rpc.lockd deadlock on 7.1-R f kern/130605 net [tcp] Certain hardware produces "Network is unreachabl o conf/130555 net [rc.d] [patch] No good way to set ipfilter variables a o kern/130525 net [ndis] [panic] 64 bit ar5008 ndisgen-erated driver cau o kern/130311 net [wlan_xauth] [panic] hostapd restart causing kernel pa o 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/129750 net [ath] Atheros AR5006 exits on "cannot map register spa f kern/129719 net [nfs] [panic] Panic during shutdown, tcp_ctloutput: in o kern/129580 net [ndis] Netgear WG311v3 (ndis) causes kenel trap at boo o kern/129517 net [ipsec] [panic] double fault / stack overflow o kern/129508 net [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 bin/128954 net ifconfig(8) deletes valid routes o kern/128917 net [wpi] [panic] if_wpi and wpa+tkip causing kernel panic o kern/128884 net [msk] if_msk page fault while in kernel mode o kern/128840 net [igb] page fault under load with igb/LRO o bin/128602 net [an] wpa_supplicant(8) crashes with an(4) o kern/128598 net [bluetooth] WARNING: attempt to net_add_domain(bluetoo o kern/128448 net [nfs] 6.4-RC1 Boot Fails if NFS Hostname cannot be res o conf/128334 net [request] use wpa_cli in the "WPA DHCP" situation o bin/128295 net [patch] ifconfig(8) does not print TOE4 or TOE6 capabi o bin/128001 net wpa_supplicant(8), wlan(4), and wi(4) issues o kern/127928 net [tcp] [patch] TCP bandwidth gets squeezed every time t o kern/127834 net [ixgbe] [patch] wrong error counting o kern/127826 net [iwi] iwi0 driver has reduced performance and connecti o kern/127815 net [gif] [patch] if_gif does not set vlan attributes from o kern/127724 net [rtalloc] rtfree: 0xc5a8f870 has 1 refs f bin/127719 net arp: Segmentation fault (core dumped) s kern/127587 net [bge] [request] if_bge(4) doesn't support BCM576X fami f kern/127528 net [icmp]: icmp socket receives icmp replies not owned by o bin/127192 net routed(8) removes the secondary alias IP of interface f kern/127145 net [wi]: prism (wi) driver crash at bigger traffic o kern/127102 net [wpi] Intel 3945ABG low throughput o kern/127057 net [udp] Unable to send UDP packet via IPv6 socket to IPv o kern/127050 net [carp] ipv6 does not work on carp interfaces [regressi o kern/126945 net [carp] CARP interface destruction with ifconfig destro o kern/126924 net [an] [patch] printf -> device_printf and simplify prob o kern/126895 net [patch] [ral] Add antenna selection (marked as TBD) o kern/126874 net [vlan]: Zebra problem if ifconfig vlanX destroy o bin/126822 net wpa_supplicant(8): WPA PSK does not work in adhoc mode o kern/126714 net [carp] CARP interface renaming makes system no longer o kern/126695 net rtfree messages and network disruption upon use of if_ o kern/126688 net [ixgbe] [patch] 1.4.7 ixgbe driver panic with 4GB and o kern/126475 net [ath] [panic] ath pcmcia card inevitably panics under o kern/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 [inet] [patch] internet control accesses beyond end of o bin/125922 net [patch] Deadlock in arp(8) o kern/125920 net [arp] Kernel Routing Table loses Ethernet Link status o kern/125845 net [netinet] [patch] tcp_lro_rx() should make use of hard o kern/125816 net [carp] [if_bridge] carp stuck in init when using bridg f kern/125502 net [ral] ifconfig ral0 scan produces no output unless in o kern/125258 net [socket] socket's SO_REUSEADDR option does not work o kern/125239 net [gre] kernel crash when using gre 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/123858 net [stf] [patch] stf not usable behind a NAT o kern/123796 net [ipf] FreeBSD 6.1+VPN+ipnat+ipf: port mapping does not o bin/123633 net ifconfig(8) doesn't set inet and ether address in one f kern/123617 net [tcp] breaking connection when client downloading file o kern/123603 net [tcp] tcp_do_segment and Received duplicate SYN o kern/123559 net [iwi] iwi periodically disassociates/associates [regre o bin/123465 net [ip6] route(8): route add -inet6 -interfac o kern/123463 net [ipsec] [panic] repeatable crash related to ipsec-tool o kern/123429 net [nfe] [hang] "ifconfig nfe up" causes a hard system lo o kern/123347 net [bge] bge1: watchdog timeout -- linkstate changed to D o conf/123330 net [nsswitch.conf] Enabling samba wins in nsswitch.conf c o kern/123256 net [wpi] panic: blockable sleep lock with wpi(4) f kern/123172 net [bce] Watchdog timeout problems with if_bce o kern/123160 net [ip] Panic and reboot at sysctl kern.polling.enable=0 o kern/122989 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/122954 net [lagg] IPv6 EUI64 incorrectly chosen for lagg devices o kern/122928 net [em] interface watchdog timeouts and stops receiving p f kern/122839 net [multicast] FreeBSD 7 multicast routing problem 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 bin/120060 net routed(8) deletes link-level routes in the presence of o kern/119945 net [rum] [panic] rum device in hostap mode, cause kernel o kern/119791 net [nfs] UDP NFS mount of aliased IP addresses from a Sol o kern/119617 net [nfs] nfs error on wpa network when reseting/shutdown f kern/119516 net [ip6] [panic] _mtx_lock_sleep: recursed on non-recursi o kern/119432 net [arp] route add -host -iface causes arp e o kern/119361 net [bge] bge(4) transmit performance problem o kern/119225 net [wi] 7.0-RC1 no carrier with Prism 2.5 wifi card [regr a bin/118987 net ifconfig(8): ifconfig -l (address_family) does not wor 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 s kern/117717 net [panic] Kernel panic with Bittorrent client. o kern/117448 net [carp] 6.2 kernel crash [regression] o kern/117423 net [vlan] Duplicate IP on different interfaces o bin/117339 net [patch] route(8): loading routing management commands o kern/117271 net [tap] OpenVPN TAP uses 99% CPU on releng_6 when if_tap o kern/117043 net [em] Intel PWLA8492MT Dual-Port Network adapter EEPROM o kern/116837 net [tun] [panic] [patch] ifconfig tunX destroy: panic o kern/116747 net [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile o bin/116643 net [patch] [request] fstat(1): add INET/INET6 socket deta o kern/116328 net [bge]: Solid hang with bge interface o kern/116185 net [iwi] if_iwi driver leads system to reboot o kern/115239 net [ipnat] panic with 'kmem_map too small' using ipnat o kern/115019 net [netgraph] ng_ether upper hook packet flow stops on ad o kern/115002 net [wi] if_wi timeout. failed allocation (busy bit). ifco o kern/114915 net [patch] [pcn] pcn (sys/pci/if_pcn.c) ethernet driver f f kern/114899 net [bge] bge0: watchdog timeout -- resetting 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 suppor o kern/113895 net [xl] xl0 fails on 6.2-RELEASE but worked fine on 5.5-R o kern/112722 net [ipsec] [udp] IP v4 udp fragmented packet reject o kern/112686 net [patm] patm driver freezes System (FreeBSD 6.2-p4) i38 o kern/112570 net [bge] packet loss with bge driver on BCM5704 chipset o bin/112557 net [patch] ppp(8) lock file should not use symlink name o kern/112528 net [nfs] NFS over TCP under load hangs with "impossible p o kern/111457 net [ral] ral(4) freeze o kern/110140 net [ipw] ipw fails under load o kern/109733 net [bge] bge link state issues [regression] o kern/109470 net [wi] Orinoco Classic Gold PC Card Can't Channel Hop o kern/109308 net [pppd] [panic] Multiple panics kernel ppp suspected [r o kern/109251 net [re] [patch] if_re cardbus card won't attach o bin/108895 net pppd(8): PPPoE dead connections on 6.2 [regression] o kern/108542 net [bce] Huge network latencies with 6.2-RELEASE / STABLE o kern/107944 net [wi] [patch] Forget to unlock mutex-locks o kern/107850 net [bce] bce driver link negotiation is faulty o conf/107035 net [patch] bridge 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 o kern/106243 net [nve] double fault panic in if_nve.c on high loads o kern/105945 net Address can disappear from network interface s kern/105943 net Network stack may modify read-only mbuf chain copies o bin/105925 net problems with ifconfig(8) and vlan(4) [regression] o kern/105348 net [ath] ath device stopps TX o kern/104851 net [inet6] [patch] On link routes not configured when usi o kern/104751 net [netgraph] kernel panic, when getting info about my tr o kern/104485 net [bge] Broadcom BCM5704C: Intermittent on newer chip ve o kern/103191 net Unpredictable reboot o kern/103135 net [ipsec] ipsec with ipfw divert (not NAT) encodes a pac o conf/102502 net [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/100839 net [txp] txp driver inconsistently stops working when the 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 bin/98218 net wpa_supplicant(8) blacklist not working f bin/97392 net ppp(8) hangs instead terminating o kern/97306 net [netgraph] NG_L2TP locks after connection with failed f kern/96268 net [socket] TCP socket performance drops by 3000% if pack o kern/96030 net [bfe] [patch] Install hangs with Broadcomm 440x NIC in o kern/95519 net [ral] ral0 could not map mbuf o kern/95288 net [pppd] [tty] [panic] if_ppp panic in sys/kern/tty_subr o kern/95277 net [netinet] [patch] IP Encapsulation mask_match() return o kern/95267 net packet drops periodically appear s kern/94863 net [bge] [patch] hack to get bge(4) working on IBM e326m o kern/94162 net [bge] 6.x kenel stale with bge(4) o kern/93886 net [ath] Atheros/D-Link DWL-G650 long delay to associate f kern/93378 net [tcp] Slow data transfer in Postfix and Cyrus IMAP (wo o kern/93019 net [ppp] ppp and tunX problems: no traffic after restarti f kern/92552 net A serious bug in most network drivers from 5.X to 6.X s kern/92279 net [dc] Core faults everytime I reboot, possible NIC issu o kern/92090 net [bge] bge0: watchdog timeout -- resetting o kern/91859 net [ndis] if_ndis does not work with Asus WL-138 s kern/91777 net [ipf] [patch] wrong behaviour with skip rule inside an o kern/91594 net [em] FreeBSD > 5.4 w/ACPI fails to detect Intel Pro/10 o kern/91364 net [ral] [wep] WF-511 RT2500 Card PCI and WEP o kern/91311 net [aue] aue interface hanging o kern/90890 net [vr] Problems with network: vr0: tx shutdown timeout s kern/90086 net [hang] 5.4p8 on supermicro P8SCT hangs during boot if f kern/89876 net [txp] [patch] txp driver doesn't work with latest firm f kern/88082 net [ath] [panic] cts protection for ath0 causes panic o kern/87521 net [ipf] [panic] using ipfilter "auth" keyword leads to k o kern/87506 net [vr] [patch] Fix alias support on vr interfaces o kern/87194 net [fxp] fxp(4) promiscuous mode seems to corrupt hw-csum s kern/86920 net [ndis] ifconfig: SIOCS80211: Invalid argument [regress o kern/86103 net [ipf] Illegal NAT Traversal in IPFilter o bin/85445 net ifconfig(8): deprecated keyword to ifconfig inoperativ o kern/85266 net [xe] [patch] xe(4) driver does not recognise Xircom XE o kern/84202 net [ed] [patch] Holtek HT80232 PCI NIC recognition on Fre o bin/82975 net route change does not parse classfull network as given o kern/82497 net [vge] vge(4) on AMD64 only works when loaded late, not f kern/81644 net [vge] vge(4) does not work properly when loaded as a K s kern/81147 net [net] [patch] em0 reinitialization while adding aliase o kern/80853 net [ed] [patch] add support for Compex RL2000/ISA in PnP o kern/79895 net [ipf] 5.4-RC2 breaks ipfilter NAT when using netgraph f kern/79262 net [dc] Adaptec ANA-6922 not fully supported o bin/79228 net [patch] extend arp(8) to be able to create blackhole r o kern/78090 net [ipf] ipf filtering on bridged packets doesn't work if p kern/77913 net [wi] [patch] Add the APDL-325 WLAN pccard to wi(4) o kern/77273 net [ipf] ipfilter breaks ipv6 statefull filtering on 5.3 s kern/77195 net [ipf] [patch] ipfilter ioctl SIOCGNATL does not match s kern/75407 net [an] an(4): no carrier after short time f kern/73538 net [bge] problem with the Broadcom BCM5788 Gigabit Ethern o kern/71469 net default route to internet magically disappears with mu o kern/70904 net [ipf] ipfilter ipnat problem with h323 proxy support o kern/64556 net [sis] if_sis short cable fix problems with NetGear FA3 s kern/60293 net [patch] FreeBSD arp poison patch o kern/54383 net [nfs] [patch] NFS root configurations without dynamic f i386/45773 net [bge] Softboot causes autoconf failure on Broadcom 570 s bin/41647 net ifconfig(8) doesn't accept lladdr along with inet addr s kern/39937 net ipstealth issue a kern/38554 net [patch] changing interface ipaddress doesn't seem to w o kern/35442 net [sis] [patch] Problem transmitting runts in if_sis dri o kern/34665 net [ipf] [hang] ipfilter rcmd proxy "hangs". o kern/27474 net [ipf] [ppp] Interactive use of user PPP and ipfilter c o conf/23063 net [patch] for static ARP tables in rc.network 259 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Feb 16 12:23: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 D2FB51065670 for ; Mon, 16 Feb 2009 12:23:20 +0000 (UTC) (envelope-from prt@prt.org) Received: from smtp6.uk.umis.net (smtp6.uk.umis.net [217.65.166.41]) by mx1.freebsd.org (Postfix) with ESMTP id 9D0508FC21 for ; Mon, 16 Feb 2009 12:23:20 +0000 (UTC) (envelope-from prt@prt.org) Received: from kate.prtsystems.ltd.uk ([217.65.165.35]) by smtp6.uk.umis.net with esmtpa (Exim 4.63 (FreeBSD)) (envelope-from ) id 1LZ2VK-0002dl-NM for freebsd-net@freebsd.org; Mon, 16 Feb 2009 12:23:18 +0000 Message-ID: <49995AB5.50200@prt.org> Date: Mon, 16 Feb 2009 12:23:17 +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: ipfw problems using divert and fwd at the same time with 6.3-release X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2009 12:23:21 -0000 Hi folks, I'm having trouble using NAT and forward in the same ipfw ruleset. It appears that the forward "wins" over the NAT regardless of ordering in the ipwf ruleset. I'm hoping that I'm missing something obvious; but is there a way to use these two together? Some background - I'm testing in the lab a potential setup to provide limited network access to a few subnets in 10.X address space, but if you aren't going to an "approved" address then you get forwarded to a web page running on port 8000 on the same box. This box is running 6.3-RELEASE-p9 and has two em interfaces. In this setup, 10.81.0.0/16 are my subnets. They are presented to the machine as a bunch of VLANs physically on em1, one /24 subnet per VLAN. The machine also does DHCP and DNS for each of these VLANs, and is the default gateway. em0 is the external IP address for the machine, currently 192.91.199.5 The machine has no problem accessing the 'net. If I remove the "clever" divert rules and the fwd rule, and make it a vanilla NAT setup, the client has no problem accessing the 'net. In this setup, I expect to be able to browse to www.prt.org (on 217.65.161.4) and that a machine in the 10.81.129.0/24 subnet has unrestricted NATted access to the 'net. Any other attempt at browsing should hit the forward and display the "no access" page from the server on the gateway machine. Using the following ruleset: > [root@xrg1 /var/tmp]# ipfw show > 00010 0 0 allow ip from any to any via lo0 > 00020 0 0 deny ip from any to 127.0.0.1 > 00022 0 0 deny ip from 127.0.0.1 to any > 00050 0 0 allow udp from any 67-68 to 255.255.255.255 dst-port 67-68 > 00052 0 0 allow udp from 10.81.0.0/16 67-68 to me dst-port 67-68 > 00054 0 0 allow udp from me 67-68 to 10.81.0.0/16 dst-port 67-68 > 00056 0 0 allow udp from 10.81.0.0/16 to me dst-port 53 > 00058 0 0 allow udp from me 53 to 10.81.0.0/16 > 00060 0 0 allow icmp from 10.81.0.0/16 to me > 00062 0 0 allow icmp from me to 10.81.0.0/16 > 00100 0 0 allow ip from 192.91.199.5 to any > 02000 0 0 divert 8668 ip from 10.81.0.0/16 to 217.65.161.4 dst-port 80 via em0 > 05000 0 0 divert 8668 ip from 10.81.129.0/24 to any via em0 > 06000 0 0 divert 8668 ip from any to me via em0 > 08000 0 0 fwd 127.0.0.1,8000 tcp from 10.81.0.0/16 to any dst-port 80 > 32000 0 0 allow ip from any to any If I browse "www.prt.org" on the client machine (10.81.2.246) I hit the fwd rule and I get my "Sorry you can't view this" webpage from the local server, and neither of the NAT rules are hit. (DNS on the client correctly resolves to 217.65.161.4) : > [root@xrg1 /var/tmp]# ipfw show > 00010 0 0 allow ip from any to any via lo0 > 00020 0 0 deny ip from any to 127.0.0.1 > 00022 0 0 deny ip from 127.0.0.1 to any > 00050 0 0 allow udp from any 67-68 to 255.255.255.255 dst-port 67-68 > 00052 0 0 allow udp from 10.81.0.0/16 67-68 to me dst-port 67-68 > 00054 0 0 allow udp from me 67-68 to 10.81.0.0/16 dst-port 67-68 > 00056 2 119 allow udp from 10.81.0.0/16 to me dst-port 53 > 00058 2 356 allow udp from me 53 to 10.81.0.0/16 > 00060 0 0 allow icmp from 10.81.0.0/16 to me > 00062 0 0 allow icmp from me to 10.81.0.0/16 > 00100 3 214 allow ip from 192.91.199.5 to any > 02000 0 0 divert 8668 ip from 10.81.0.0/16 to 217.65.161.4 dst-port 80 via em0 > 05000 0 0 divert 8668 ip from 10.81.129.0/24 to any via em0 > 06000 3 601 divert 8668 ip from any to me via em0 > 08000 43 4796 fwd 127.0.0.1,8000 tcp from 10.81.0.0/16 to any dst-port 80 > 32000 58 55935 allow ip from any to any If I remove rule 8000, then I can browse to www.prt.org as expected, and I hit the divert rules: > 00010 0 0 allow ip from any to any via lo0 > 00020 0 0 deny ip from any to 127.0.0.1 > 00022 0 0 deny ip from 127.0.0.1 to any > 00050 0 0 allow udp from any 67-68 to 255.255.255.255 dst-port 67-68 > 00052 0 0 allow udp from 10.81.0.0/16 67-68 to me dst-port 67-68 > 00054 0 0 allow udp from me 67-68 to 10.81.0.0/16 dst-port 67-68 > 00056 7 460 allow udp from 10.81.0.0/16 to me dst-port 53 > 00058 7 1247 allow udp from me 53 to 10.81.0.0/16 > 00060 0 0 allow icmp from 10.81.0.0/16 to me > 00062 0 0 allow icmp from me to 10.81.0.0/16 > 00100 45 3375 allow ip from 192.91.199.5 to any > 02000 38 5096 divert 8668 ip from 10.81.0.0/16 to 217.65.161.4 dst-port 80 via em0 > 05000 0 0 divert 8668 ip from 10.81.129.0/24 to any via em0 > 06000 75 37498 divert 8668 ip from any to me via em0 > 32000 273 142906 allow ip from any to any The natd config is trivial - I'm just launching it with: natd -port 8668 -same_ports -verbose interface em0 Does anyone have any ideas? I've spent the whole weekend trying various things (like extra permits of the "special" traffic before the fwd line) but it makes no difference - the fwd still wins over everything. Many thanks, Paul. From owner-freebsd-net@FreeBSD.ORG Mon Feb 16 12:48:01 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 B14E8106566C; Mon, 16 Feb 2009 12:48:01 +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 8D2018FC0A; Mon, 16 Feb 2009 12:48:01 +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 2F2A546B32; Mon, 16 Feb 2009 07:48:01 -0500 (EST) Date: Mon, 16 Feb 2009 12:48:01 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: current@FreeBSD.org, net@FreeBSD.org In-Reply-To: <20080526110543.J26343@fledge.watson.org> Message-ID: References: <20080526110543.J26343@fledge.watson.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: Subject: HEADS UP: IFF_NEEDSGIANT consumers to be disabled, removed (was: Re: Wiki page for non-MPSAFE network stack de-orbit scheduling) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2009 12:48:02 -0000 (Bcc to arch@) On Mon, 26 May 2008, Robert Watson wrote: > Just to keep track of things: > > http://wiki.freebsd.org/NONMPSAFE_DEORBIT Delayed by about six months, the merge and switch to the new USB stack in 8.x means that we're now fairly close to being able to pick up this project again. The goal remains to eliminate IFF_NEEDSGIANT, which is (mostly) the last piece of non-MPSAFE compatibility infrastructure in the network stack in -CURRENT. I removed support for non-MPSAFE network protocols before 7.0, and this is the support for non-MPSAFE network device drivers. As of the current moment in HEAD, the following drivers are flagged wth IFF_NEEDSGIANT: General network device drivers that still require Giant: if_ar if_ray if_sl if_sr Old USB network device drivers: if_axe if_cdce if_cue if_kue if_rue if_rum if_udav if_upgt if_ural if_urtw if_zyd Network device drivers intimately tangled with the old TTY code: if_cx if_ppp lf_sl A network device driver that appears to conditionally use IFF_NEEDSGIANT for the purposes of (sometimes) interacting with the old USB code: if_ndis The following schedule is proposed, assuming nothing goes horribly wrong with the new USB code in the next few weeks, and remaining nits relating to USB network and 802.11 drivers are handled: 16 February 2009 HEADS UP to lists (this e-mail) 01 March 2009 Disable build of all IFF_NEEDSGIANT drivers in 8.x 01 April 2009 Remove all IFF_NEEDSGIANT drivers from 8.x In the next couple of weeks, I'd like to resolve the status of (and eliminate) the if_ndis conditional use of IFF_NEEDSGIANT. There's also a chance that if_sl will get updated by Ed and myself to work with the new locking and TTY world orders -- the lock is easy, but the TTY update takes a bit of work. Perhaps someone will feel moved to do this for if_ppp and possibly if_cx as well. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-net@FreeBSD.ORG Mon Feb 16 13:00: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 6DF4D1065674 for ; Mon, 16 Feb 2009 13:00:07 +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 5549D8FC14 for ; Mon, 16 Feb 2009 13:00:07 +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 n1GD065r085120 for ; Mon, 16 Feb 2009 13:00:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1GD06XR085119; Mon, 16 Feb 2009 13:00:06 GMT (envelope-from gnats) Date: Mon, 16 Feb 2009 13:00:06 GMT Message-Id: <200902161300.n1GD06XR085119@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Bruce Cran Cc: Subject: Re: kern/131738: [re] re0: watchdog timeout (missed Tx interrupts) -- recovering X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bruce Cran List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2009 13:00:07 -0000 The following reply was made to PR kern/131738; it has been noted by GNATS. From: Bruce Cran To: Trevor Roydhouse Cc: bug-followup@FreeBSD.org Subject: Re: kern/131738: [re] re0: watchdog timeout (missed Tx interrupts) -- recovering Date: Mon, 16 Feb 2009 12:53:03 +0000 I also saw this message recently on my laptop which runs 8-CURRENT (20090205); the hardware is: re0: port 0x2000-0x20ff mem 0xd1010000-0xd1010fff,0xd1000000-0xd100ffff irq 19 at device 0.0 on pci10 re0: Chip rev. 0x24800000 re0: MAC rev. 0x00000000 miibus0: on re0 rlphy0: PHY 1 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto re0: Ethernet address: 00:1e:ec:f5:fd:4f re0: [FILTER] I'm connected to the Internet using 17Mb ADSL. -- Bruce Cran From owner-freebsd-net@FreeBSD.ORG Mon Feb 16 23:47:13 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 C20DD106566B; Mon, 16 Feb 2009 23:47:13 +0000 (UTC) (envelope-from prvs=julian=2911c668e@elischer.org) Received: from smtp-outbound.ironport.com (smtp-outbound.ironport.com [63.251.108.112]) by mx1.freebsd.org (Postfix) with ESMTP id A73308FC0A; Mon, 16 Feb 2009 23:47:13 +0000 (UTC) (envelope-from prvs=julian=2911c668e@elischer.org) Received: from jelischer-laptop.sfo.ironport.com (HELO julian-mac.elischer.org) ([10.251.22.38]) by smtp-outbound.ironport.com with ESMTP; 16 Feb 2009 15:34:00 -0800 Message-ID: <4999F7F9.4030204@elischer.org> Date: Mon, 16 Feb 2009 15:34:17 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: Robert Watson References: <20080526110543.J26343@fledge.watson.org> 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: HEADS UP: IFF_NEEDSGIANT consumers to be disabled, removed X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Feb 2009 23:47:14 -0000 Robert Watson wrote: > > (Bcc to arch@) > > On Mon, 26 May 2008, Robert Watson wrote: > >> Just to keep track of things: >> >> http://wiki.freebsd.org/NONMPSAFE_DEORBIT > > Delayed by about six months, the merge and switch to the new USB stack > in 8.x means that we're now fairly close to being able to pick up this > project again. The goal remains to eliminate IFF_NEEDSGIANT, which is > (mostly) the last piece of non-MPSAFE compatibility infrastructure in > the network stack in -CURRENT. I removed support for non-MPSAFE network > protocols before 7.0, and this is the support for non-MPSAFE network > device drivers. As of the current moment in HEAD, the following drivers > are flagged wth IFF_NEEDSGIANT: > > General network device drivers that still require Giant: > > if_ar > if_ray > if_sl > if_sr if_sr and if_ar are really simple and could probably be converted "trivially".. especially if their netgraph code is used. however I wonder if anyone still has that hardware (they are drivers for two sync serial cards). John Hay must have had some when he wrote the driver... > > Old USB network device drivers: > > if_axe > if_cdce > if_cue > if_kue > if_rue > if_rum > if_udav > if_upgt > if_ural > if_urtw > if_zyd > > Network device drivers intimately tangled with the old TTY code: > > if_cx > if_ppp > lf_sl > > A network device driver that appears to conditionally use IFF_NEEDSGIANT > for the purposes of (sometimes) interacting with the old USB code: > > if_ndis > > The following schedule is proposed, assuming nothing goes horribly wrong > with the new USB code in the next few weeks, and remaining nits relating > to USB network and 802.11 drivers are handled: > > 16 February 2009 HEADS UP to lists (this e-mail) > 01 March 2009 Disable build of all IFF_NEEDSGIANT drivers in 8.x > 01 April 2009 Remove all IFF_NEEDSGIANT drivers from 8.x > > In the next couple of weeks, I'd like to resolve the status of (and > eliminate) the if_ndis conditional use of IFF_NEEDSGIANT. There's also > a chance that if_sl will get updated by Ed and myself to work with the > new locking and TTY world orders -- the lock is easy, but the TTY update > takes a bit of work. Perhaps someone will feel moved to do this for > if_ppp and possibly if_cx as well. > > Robert N M Watson > Computer Laboratory > University of Cambridge > _______________________________________________ > 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 Feb 17 00:01: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 3EF87106566B; Tue, 17 Feb 2009 00:01:15 +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 2EBC68FC1D; Tue, 17 Feb 2009 00:01:15 +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 n1H01FtT093241; Tue, 17 Feb 2009 00:01:15 GMT (envelope-from yongari@freefall.freebsd.org) Received: (from yongari@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1H01ES5093237; Tue, 17 Feb 2009 00:01:14 GMT (envelope-from yongari) Date: Tue, 17 Feb 2009 00:01:14 GMT Message-Id: <200902170001.n1H01ES5093237@freefall.freebsd.org> To: fbsdbugs3@sentry.org, yongari@FreeBSD.org, freebsd-net@FreeBSD.org, yongari@FreeBSD.org From: yongari@FreeBSD.org Cc: Subject: Re: kern/131738: [re] re0: watchdog timeout (missed Tx interrupts) -- recovering X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2009 00:01:15 -0000 Synopsis: [re] re0: watchdog timeout (missed Tx interrupts) -- recovering State-Changed-From-To: open->feedback State-Changed-By: yongari State-Changed-When: Mon Feb 16 23:59:15 UTC 2009 State-Changed-Why: Would you try latest re(4) in HEAD(r188474)? Copying if_re.c, if_rl.c and if_rlreg.h from HEAD to 7-stable is enough to test this. Btw, the watchdog timeout is not real, it just indicates missing Tx completion interrupt. Otherwise you would have seen link state change message as watchdog involves resetting controller(e.g You can safely ignore this). Responsible-Changed-From-To: freebsd-net->yongari Responsible-Changed-By: yongari Responsible-Changed-When: Mon Feb 16 23:59:15 UTC 2009 Responsible-Changed-Why: Grab. http://www.freebsd.org/cgi/query-pr.cgi?pr=131738 From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 00:18:31 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 D00E81065673; Tue, 17 Feb 2009 00:18:31 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from sarah.protected-networks.net (sarah.protected-networks.net [IPv6:2001:470:1f07:4e1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 743EC8FC21; Tue, 17 Feb 2009 00:18:31 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [202.12.127.84]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: imb) by sarah.protected-networks.net (Postfix) with ESMTPSA id 309D76106; Mon, 16 Feb 2009 19:18:29 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=protected-networks.net; s=200705; t=1234829909; bh=TVK4SiWE2nGjjwD4VYWIKQXt50JE+BVSq/92n8YeA/8=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=Mk/nKC6n3oJQlxz1oP5cuwY6QMgnXmMWhEtdJ2RXicCPEJw5CooEcmHHmc2LDtVB7 uneTpaBjneFSbYcSjGjdwAMzL9hWpDE+vJn9flFrApHEpAr8Fvshbzf9yotWLlY DomainKey-Signature: a=rsa-sha1; s=200509; d=protected-networks.net; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:cc:subject: references:in-reply-to:x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=JfmAOKTDehqFSUcPJQo13LazaQrgJYgTJNwkHRKUrHQWCQvHLwq7B0shpabvvJnY5 VjbKTgX3UlmuroLYDM/3Wfefi/oTjzaiYa0F+9uhPxdtkzVzHRRS4Wd0GJhxJeZ Message-ID: <499A024A.60209@protected-networks.net> Date: Mon, 16 Feb 2009 19:18:18 -0500 From: Michael Butler User-Agent: Thunderbird 2.0.0.19 (X11/20090128) MIME-Version: 1.0 To: Robert Watson References: <20080526110543.J26343@fledge.watson.org> <4999F7F9.4030204@elischer.org> In-Reply-To: <4999F7F9.4030204@elischer.org> X-Enigmail-Version: 0.95.7 OpenPGP: id=0442D492 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: current@FreeBSD.org, net@FreeBSD.org Subject: Re: HEADS UP: IFF_NEEDSGIANT consumers to be disabled, removed X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 00:18:32 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Robert Watson wrote: > Network device drivers intimately tangled with the old TTY code: > > if_cx > if_ppp > lf_sl The old TTY code appears to be the reason that the bluetooth/ng_h4 driver was "abandoned". Not having investigated further, I do not know if it is practical to restore to functionality. Since I can no longer use my compact-flash adapted pcmcia card for the lack of the H4 driver in -current, I use a USB dongle .. as follows: The usage of rfcomm_sppd as documented in the handbook results in .. Feb 16 19:12:57 toshi kernel: ugen1.2: at usbus1 Feb 16 19:12:57 toshi kernel: ubt0: on usbus1 Feb 16 19:13:31 toshi kernel: pid 50258 (rfcomm_sppd) is using legacy pty devices .. when connecting to my GPS. Is this functionality to be impacted? Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkmaAkkACgkQQv9rrgRC1JK5rgCeM25FjOcNp/XHc5HuWV9yBSq8 IqMAmwVLP0QDIKMn5kDJhEa7gJN9mmq7 =sLMJ -----END PGP SIGNATURE----- From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 01:09:31 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 061B2106566C; Tue, 17 Feb 2009 01:09:31 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D0DB18FC18; Tue, 17 Feb 2009 01:09:30 +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 n1H19Uah040406; Tue, 17 Feb 2009 01:09:30 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1H19UWL040402; Tue, 17 Feb 2009 01:09:30 GMT (envelope-from linimon) Date: Tue, 17 Feb 2009 01:09:30 GMT Message-Id: <200902170109.n1H19UWL040402@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/131753: [altq] [panic] kernel panic in hfsc_dequeue X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 01:09:31 -0000 Old Synopsis: kernel panic in hfsc_dequeue New Synopsis: [altq] [panic] kernel panic in hfsc_dequeue Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Tue Feb 17 01:09:02 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=131753 From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 02:50:03 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0027D106566C for ; Tue, 17 Feb 2009 02:50:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C898C8FC12 for ; Tue, 17 Feb 2009 02:50:02 +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 n1H2o2a1015663 for ; Tue, 17 Feb 2009 02:50:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1H2o2Ew015662; Tue, 17 Feb 2009 02:50:02 GMT (envelope-from gnats) Date: Tue, 17 Feb 2009 02:50:02 GMT Message-Id: <200902170250.n1H2o2Ew015662@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: KUROSAWA Takahiro Cc: Subject: Re: kern/116837: [tun] [panic] [patch] ifconfig tunX destroy: panic X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: KUROSAWA Takahiro List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2009 02:50:03 -0000 The following reply was made to PR kern/116837; it has been noted by GNATS. From: KUROSAWA Takahiro To: bug-followup@FreeBSD.org, jkpyvxmzsa@mailinator.com Cc: Subject: Re: kern/116837: [tun] [panic] [patch] ifconfig tunX destroy: panic Date: Tue, 17 Feb 2009 11:42:00 +0900 This is fixed on recent 8-CURRENT, but probably not yet on 7.x. From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 09:47:07 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 8584F106568A for ; Tue, 17 Feb 2009 09:47:07 +0000 (UTC) (envelope-from vlad@prokk.net) Received: from smtp.prokk.net (smtp.prokk.net [195.16.77.5]) by mx1.freebsd.org (Postfix) with ESMTP id F34D78FC1A for ; Tue, 17 Feb 2009 09:47:06 +0000 (UTC) (envelope-from vlad@prokk.net) Received: from base (base.prokk.net [195.16.77.7]) by smtp.prokk.net (8.13.8/8.13.8) with ESMTP id n1H9I4D3070713; Tue, 17 Feb 2009 11:18:09 +0200 (EET) (envelope-from vlad@prokk.net) From: "Vladimir V. Kobal" To: References: In-Reply-To: Date: Tue, 17 Feb 2009 11:18:05 +0200 Organization: ProKK SE Message-ID: <000f01c990e0$a70c1230$f5243690$@net> MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcmNSOlqHRWIb0pWQWCvAs1QN5sbUQDk4KCA Content-Language: uk X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (smtp.prokk.net [195.16.77.5]); Tue, 17 Feb 2009 11:18:09 +0200 (EET) X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on smtp.prokk.net X-Virus-Status: Clean Cc: 'Sergey Pronin' Subject: RE: Synopsis: process swi1:net gives 100% CPU usage. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 09:47:07 -0000 I have the same problem with netgraph on 7.1-RELEASE, mpd 5.2, AMD Phenom. Dummynet, divert and pf are disabled in the kernel. While swi1:net (aka netgraph) is using 100% of CPU time m_tag_locate() and ng_iface_output() are constantly called from the infinite loop. Sergey, could you provide the content of mpd.conf and the output of "ngctl types". -----Original Message----- From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org] On Behalf Of Sergey Pronin Sent: Thursday, February 12, 2009 9:07 PM To: freebsd-net@freebsd.org Subject: Synopsis: process swi1:net gives 100% CPU usage. Synopsis: process swi1:net gives 100% CPU usage. Not depending on the conditions (no heavy load, not a lot of traffic passing through, not a lot of ng nodes) server stops to work properly. 1) swi1:net gives me 100% CPU usage. 2) server is not responding to icmp echo requests 3) ssh of course not working 4) mpd has an "ngsock" state at the top 5) tasq of the em0 card using 0% of the cpu. 6) rebooting the server helps. From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 10:21:46 2009 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E63691065675; Tue, 17 Feb 2009 10:21:46 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from mx.bulinfo.net (mx.bulinfo.net [193.194.156.1]) by mx1.freebsd.org (Postfix) with ESMTP id 5CEF98FC24; Tue, 17 Feb 2009 10:21:46 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from localhost (localhost [127.0.0.1]) by mx.bulinfo.net (Postfix) with ESMTP id 58B89C7F9; Tue, 17 Feb 2009 11:50:08 +0200 (EET) Received: from mx.bulinfo.net ([127.0.0.1]) by localhost (mx.bulinfo.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15078-08; Tue, 17 Feb 2009 11:50:05 +0200 (EET) Received: from [192.168.2.188] (pythia.bulinfo.net [212.72.195.5]) by mx.bulinfo.net (Postfix) with ESMTP id DDEE6C7F2; Tue, 17 Feb 2009 11:50:04 +0200 (EET) Message-ID: <499A884A.4040408@bulinfo.net> Date: Tue, 17 Feb 2009 11:50:02 +0200 From: Krassimir Slavchev User-Agent: Thunderbird 2.0.0.14 (X11/20080616) MIME-Version: 1.0 To: Julian Elischer References: <20080526110543.J26343@fledge.watson.org> <4999F7F9.4030204@elischer.org> In-Reply-To: <4999F7F9.4030204@elischer.org> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at mx.bulinfo.net Cc: Robert Watson , current@FreeBSD.org, net@FreeBSD.org Subject: Re: HEADS UP: IFF_NEEDSGIANT consumers to be disabled, removed X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 10:21:47 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Julian Elischer wrote: > Robert Watson wrote: >> >> (Bcc to arch@) >> >> On Mon, 26 May 2008, Robert Watson wrote: >> >>> Just to keep track of things: >>> >>> http://wiki.freebsd.org/NONMPSAFE_DEORBIT >> >> Delayed by about six months, the merge and switch to the new USB stack >> in 8.x means that we're now fairly close to being able to pick up this >> project again. The goal remains to eliminate IFF_NEEDSGIANT, which is >> (mostly) the last piece of non-MPSAFE compatibility infrastructure in >> the network stack in -CURRENT. I removed support for non-MPSAFE >> network protocols before 7.0, and this is the support for non-MPSAFE >> network device drivers. As of the current moment in HEAD, the >> following drivers are flagged wth IFF_NEEDSGIANT: >> >> General network device drivers that still require Giant: >> >> if_ar >> if_ray >> if_sl >> if_sr > > if_sr and if_ar are really simple and could probably > be converted "trivially".. especially if > their netgraph code is used. > > however I wonder if anyone still has that hardware (they are > drivers for two sync serial cards). I still have such Digi/Arnet SYNC/570i PCI card and I used to use it for a long time with 4.x and if_ar driver without any problems. Thanks to John Hay for well written driver! > > John Hay must have had some when he wrote the driver... > >> >> Old USB network device drivers: >> >> if_axe >> if_cdce >> if_cue >> if_kue >> if_rue >> if_rum >> if_udav >> if_upgt >> if_ural >> if_urtw >> if_zyd >> >> Network device drivers intimately tangled with the old TTY code: >> >> if_cx >> if_ppp >> lf_sl >> >> A network device driver that appears to conditionally use >> IFF_NEEDSGIANT for the purposes of (sometimes) interacting with the >> old USB code: >> >> if_ndis >> >> The following schedule is proposed, assuming nothing goes horribly >> wrong with the new USB code in the next few weeks, and remaining nits >> relating to USB network and 802.11 drivers are handled: >> >> 16 February 2009 HEADS UP to lists (this e-mail) >> 01 March 2009 Disable build of all IFF_NEEDSGIANT drivers in 8.x >> 01 April 2009 Remove all IFF_NEEDSGIANT drivers from 8.x >> >> In the next couple of weeks, I'd like to resolve the status of (and >> eliminate) the if_ndis conditional use of IFF_NEEDSGIANT. There's >> also a chance that if_sl will get updated by Ed and myself to work >> with the new locking and TTY world orders -- the lock is easy, but the >> TTY update takes a bit of work. Perhaps someone will feel moved to do >> this for if_ppp and possibly if_cx as well. >> >> Robert N M Watson >> Computer Laboratory >> University of Cambridge >> _______________________________________________ >> 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" > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFJmohKxJBWvpalMpkRAh44AJ4pmnYdK3XApm8FoVpWfHsqZIZF3gCdHKGZ 3V5VDG8kKg5OVkColCUu9cA= =0oAM -----END PGP SIGNATURE----- From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 10:26:06 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 6530D1065712; Tue, 17 Feb 2009 10:26:06 +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 3F47C8FC1C; Tue, 17 Feb 2009 10:26:06 +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 D048446B35; Tue, 17 Feb 2009 05:26:05 -0500 (EST) Date: Tue, 17 Feb 2009 10:26:05 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Krassimir Slavchev In-Reply-To: <499A884A.4040408@bulinfo.net> Message-ID: References: <20080526110543.J26343@fledge.watson.org> <4999F7F9.4030204@elischer.org> <499A884A.4040408@bulinfo.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: net@FreeBSD.org, Julian Elischer , current@FreeBSD.org Subject: Re: HEADS UP: IFF_NEEDSGIANT consumers to be disabled, removed X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 10:26:08 -0000 On Tue, 17 Feb 2009, Krassimir Slavchev wrote: >> if_sr and if_ar are really simple and could probably be converted >> "trivially".. especially if their netgraph code is used. >> >> however I wonder if anyone still has that hardware (they are drivers for >> two sync serial cards). > > I still have such Digi/Arnet SYNC/570i PCI card and I used to use it for a > long time with 4.x and if_ar driver without any problems. > > Thanks to John Hay for well written driver! I would be quite happy to see the remaining drivers be converted over -- when using IFF_NEEDSGIANT, they do potentially see a significant performance loss as a result of having to defer execution to Giant-holding contexts. However, the sooner the better, as stripping the Giant compat stuff will allow us to clean up the compat shims, in turn removing the need for deferred execution to avoid calling those shims in unfortunate contexts for multicast, and simplifies the forthcoming address list locking work. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 13:15: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 3D369106566B for ; Tue, 17 Feb 2009 13:15:21 +0000 (UTC) (envelope-from riaank@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155]) by mx1.freebsd.org (Postfix) with ESMTP id C9A788FC0C for ; Tue, 17 Feb 2009 13:15:20 +0000 (UTC) (envelope-from riaank@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so438555fgb.35 for ; Tue, 17 Feb 2009 05:15:19 -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=qPF4JFSk250Yu5tRsKDsGclSTtSmtNF2W7kr9sjeEr8=; b=pjrR5XuvqNcyEXA2s1GK7VcQ5ilkgMS0WAgJbuFlO56+LPZrd80zojDqPtX4N8OkAd Y4GkGyhSUM+EAxMQB3j6bIt31x0qQqahzCVPxvytGM5a18eIufmIBR+qMo/STJDcHkwi lgeaRkFZAWvqMNNOrChZCp6kkwdWumpDA7d6M= 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=PlRZyeNWNDM5oL9IXurFDcbvWPWR2dsmgcKqcEHSyuC/BQpcc4A703b0Y2+9ty6sdA pvVaVVUcGJ9a5RVpmJjlLIwxxA09uQ6saSCtcVoU+OkTHzZ//VrIjsMsGeBVUtiwlGI/ JXH56jbZNJsmrgHM1AjljufBOjqRUqefx56xY= MIME-Version: 1.0 Received: by 10.86.70.3 with SMTP id s3mr2002681fga.78.1234874886150; Tue, 17 Feb 2009 04:48:06 -0800 (PST) Date: Tue, 17 Feb 2009 14:48:06 +0200 Message-ID: <85c4b1850902170448p7a59d50bt6bdaa89aa01c51d7@mail.gmail.com> From: Riaan Kruger To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: NATT patch and FreeBSD's setkey X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 13:15:21 -0000 I see a lot of good work done on the nat-t patches for FreeBSD and ipsec-tools. I was wondering if the base setkey is due for an update? If so is anyone looking to update it? Has anyone had any success using the patched FreeBSD along with racoon2. Regards Riaan From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 14:28: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 9754A106566B for ; Tue, 17 Feb 2009 14:28:57 +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 525288FC1A for ; Tue, 17 Feb 2009 14:28:57 +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 CC4662798B8; Tue, 17 Feb 2009 15:28:55 +0100 (CET) Received: by astro.zen.inc (Postfix, from userid 1000) id C6AB217051; Tue, 17 Feb 2009 15:34:25 +0100 (CET) Date: Tue, 17 Feb 2009 15:34:25 +0100 From: VANHULLEBUS Yvan To: Riaan Kruger Message-ID: <20090217143425.GA58591@zeninc.net> References: <85c4b1850902170448p7a59d50bt6bdaa89aa01c51d7@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <85c4b1850902170448p7a59d50bt6bdaa89aa01c51d7@mail.gmail.com> User-Agent: All mail clients suck. This one just sucks less. Cc: freebsd-net@freebsd.org Subject: Re: NATT patch and FreeBSD's setkey X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 14:28:57 -0000 On Tue, Feb 17, 2009 at 02:48:06PM +0200, Riaan Kruger wrote: > I see a lot of good work done on the nat-t patches for FreeBSD and ipsec-tools. That's what we're trying to do, even if we know that there is still some work to do ! > I was wondering if the base setkey is due for an update? > If so is anyone looking to update it? Upgrading FreeBSD's setkey is not a new question.... Basically, there are various scenarios: - keep it (almost) without changes, it is enouth for basic (static) IPsec, and people who want to do dynamic keying, NAT-T, etc... will install ipsec-tools, so will have /usr/local/sbin/setkey. - same as upper, but do "something" to solve the problem when both /sbin/setkey and /usr/local/sbin/setkey (same for libipsec) are installed. - just remove setkey/libipsec from base system. People who want "real IPsec" will need ipsec-tools or something else, but we can't ensure no one will just need setkey/libipsec... - sync FreeBSD's setkey/libipsec from ipsec-tools. That won't solve all issues (/sbin Vs /usr/local/sbin), and this will need regular syncs with ipsec-tools. - Same as upper, but remove sources from /usr/src, consider ipsec-tools as a contrib (in /usr/src/contrib) and do "something" to automagically update sources when needed (as in /usr/ports). All those solutions solve some parts of the problems (except the first one, of course), but keeps/generates some others.... If someone has a magic solution without drawbacks, please tell us ! > Has anyone had any success using the patched FreeBSD along with racoon2. I just don't know what's the actual status of racoon2, but nat-t patchset is public and everyone can send changes if that helps interaction with other daemons (without breaking again the API if possible.....). Yvan. From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 14:45:07 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 DA76C1065675; Tue, 17 Feb 2009 14:45:07 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id 91D328FC1D; Tue, 17 Feb 2009 14:45:07 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (amavis.str.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 108A841C6BB; Tue, 17 Feb 2009 15:45:06 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([62.111.66.27]) by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id l4A6LG8CB9xh; Tue, 17 Feb 2009 15:45:05 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id AE32241C6A3; Tue, 17 Feb 2009 15:45:05 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id BD6F84448E6; Tue, 17 Feb 2009 14:41:41 +0000 (UTC) Date: Tue, 17 Feb 2009 14:41:41 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: VANHULLEBUS Yvan In-Reply-To: <20090217143425.GA58591@zeninc.net> Message-ID: <20090217143409.J53478@maildrop.int.zabbadoz.net> References: <85c4b1850902170448p7a59d50bt6bdaa89aa01c51d7@mail.gmail.com> <20090217143425.GA58591@zeninc.net> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, Riaan Kruger Subject: Re: NATT patch and FreeBSD's setkey X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 14:45:08 -0000 On Tue, 17 Feb 2009, VANHULLEBUS Yvan wrote: Hi, > If someone has a magic solution without drawbacks, please tell us ! I am not going to find my posting from a few years back but the solution is to keep the kernel and libipsec (and setkey) in base in sync and not install libipsec and setkey from the ipsec-tools port. Done. That obviously means that people who patch their kernel need to patch their user space as well but that should not be a problem as they rebuild anyway and need to build ipsec-tools racoon etc. on their own to use the new features as w/o changing the default options it doesn't work for nat-t. That also allows other 3rd party utilities using libipsec to continue to do so and use all "features" w/o needing another fork. >> Has anyone had any success using the patched FreeBSD along with racoon2. > > I just don't know what's the actual status of racoon2, but nat-t > patchset is public and everyone can send changes if that helps > interaction with other daemons (without breaking again the API if > possible.....). We have about 3 months left to get that patch in for 8; ideally 6 weeks. Can you update the nat-t patch in a way as discussed here before so that the extra address is in etc. and we can move forward? I basically do not care if racoon from ipsec-tools is not going to work for two weeks of HEAD or four as someone will quickly add a conditional patch to the port for a __FreeBSD_version > 8xxxxx and that can be removed once ipsec-tools properly detect the state of the system. /bz -- Bjoern A. Zeeb The greatest risk is not taking one. From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 14:47: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 15D2410656C5 for ; Tue, 17 Feb 2009 14:47:33 +0000 (UTC) (envelope-from jwm-freebsd-net@skepsi.net) Received: from mail.skepsi.net (mail.skepsi.net [208.86.225.194]) by mx1.freebsd.org (Postfix) with ESMTP id A91FB8FC19 for ; Tue, 17 Feb 2009 14:47:32 +0000 (UTC) (envelope-from jwm-freebsd-net@skepsi.net) Received: (qmail 50411 invoked from network); 17 Feb 2009 11:04:56 -0000 Received: from d60-65-30-215.col.wideopenwest.com (HELO pilot.skepsi.net) (65.60.215.30) by mail.skepsi.net with SMTP; 17 Feb 2009 11:04:56 -0000 Received: (nullmailer pid 27195 invoked by uid 1000); Tue, 17 Feb 2009 14:47:31 -0000 Date: Tue, 17 Feb 2009 09:47:31 -0500 From: Jason Morgan To: Jason Morgan Message-ID: <20090217144731.GA25475@skepsi.net> References: <20090214222342.GA45141@skepsi.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20090214222342.GA45141@skepsi.net> User-Agent: mutt/1.5.18 (FreeBSD 7.1-STABLE) Cc: freebsd-net@freebsd.org Subject: Re: WPA-EAP (ath driver): trouble maintaining connection X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 14:47:33 -0000 On 2009.02.14 17:23:42, Jason Morgan wrote: > > Hello, > > I have been having trouble maintaining a wireless connection at my > university, which uses the WPA-EAP protocol. I have played with my > wpa_supplicant.conf file, but haven't found anything that works. I > don't seems to have any trouble at home using a Linksys AP and > WPA-PSK. I was hoping someone here could point me in the right > direction---I am not very familiar with WPA and wireless > networking. Error messages and other relevant information below. (You > will notice that I lose connection every 5-10 minutes.) > > Thanks in advance. Some additional information in case that's helpful. $ pciconf -lv ath0@pci0:8:10:0: class=0x020000 card=0x132910cf chip=0x001b168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5006 family 802.11abg Wireless NIC' class = network subclass = ethernet Also, it seems that I am getting a lot more of these messages in /var/log/messages: Feb 15 11:49:48 sofie kernel: update_stats: bogus ndx0 -1, max 10, mode 3 Feb 15 11:49:54 sofie kernel: update_stats: bogus ndx0 -1, max 10, mode 3 Feb 15 11:49:54 sofie dhclient: New IP Address (ath0): 128.146.115.38 Feb 15 11:49:54 sofie dhclient: New Subnet Mask (ath0): 255.255.255.0 Feb 15 11:49:54 sofie dhclient: New Broadcast Address (ath0): 128.146.115.255 Feb 15 11:49:54 sofie dhclient: New Routers (ath0): 128.146.115.1 Feb 15 11:49:56 sofie kernel: update_stats: bogus ndx0 -1, max 10, mode 3 Feb 15 11:50:37 sofie last message repeated 4 times Feb 15 11:52:38 sofie last message repeated 14 times Feb 15 11:54:42 sofie last message repeated 14 times The ath manpage provides a bit of information ("This should not happen") on `bogus xmit rate' but not on `bogus ndx0'. Once again, any help would be greatly appreciated. ~Jason > $ uname -a > FreeBSD sofie.skepsi.net 7.1-STABLE FreeBSD 7.1-STABLE #3: Sun Feb 1 > 13:00:56 EST 2009 root@sofie.skepsi.net:/usr/obj/usr/src/sys/SOFIE > amd64 > > > $ cat /etc/wpa_supplicant.conf > ctrl_interface=/var/run/wpa_supplicant > ctrl_interface_group=wheel > eapol_version=1 > ap_scan=1 > fast_reauth=1 > > network={ > ssid="osuwireless" > scan_ssid=1 > key_mgmt=WPA-EAP > eap=PEAP > identity="xxx" > password="xxx" > phase1="peaplabel=0" > phase2="auth-MSCHAPV2" > priority=1 > } > > > $ cat /etc/dhclient.conf > # ath0 > interface "ath0" { > request subnet-mask, broadcast-address, time-offset, routers, > domain-name, domain-name-servers, host-name; > require subnet-mask, domain-name-servers; > } > > > $ cat /var/log/messages > > Feb 14 15:50:09 sofie kernel: ath0: link state changed to DOWN > Feb 14 15:50:09 sofie wpa_supplicant[403]: Trying to associate with > 00:0b:86:58:04:00 (SSID='osuwireless' freq=2437 MHz) > Feb 14 15:50:09 sofie wpa_supplicant[403]: CTRL-EVENT-DISCONNECTED - > Disconnect event - remove keys > Feb 14 15:50:19 sofie wpa_supplicant[403]: Authentication with > 00:00:00:00:00:00 timed out. > Feb 14 15:50:27 sofie wpa_supplicant[403]: Trying to associate with > 00:0b:86:58:02:80 (SSID='osuwireless' freq=2437 MHz) > Feb 14 15:50:27 sofie wpa_supplicant[403]: Association request to the > driver failed > Feb 14 15:50:32 sofie wpa_supplicant[403]: Authentication with > 00:0b:86:58:02:80 timed out. > Feb 14 15:50:39 sofie wpa_supplicant[403]: Trying to associate with > 00:0b:86:5d:3a:40 (SSID='osuwireless' freq=2412 MHz) > Feb 14 15:50:40 sofie kernel: ath0: link state changed to UP > Feb 14 15:50:40 sofie wpa_supplicant[403]: Associated with > 00:0b:86:5d:3a:40 > Feb 14 15:50:40 sofie wpa_supplicant[403]: CTRL-EVENT-EAP-STARTED EAP > authentication started > Feb 14 15:50:40 sofie wpa_supplicant[403]: CTRL-EVENT-EAP-METHOD EAP > vendor 0 method 25 (PEAP) selected > Feb 14 15:50:40 sofie wpa_supplicant[403]: OpenSSL: > tls_connection_handshake - Failed to read possible Application Data > error:00000000:lib(0):func(0):reason(0) > Feb 14 15:50:40 sofie wpa_supplicant[403]: EAP-MSCHAPV2: > Authentication succeeded > Feb 14 15:50:40 sofie wpa_supplicant[403]: EAP-TLV: TLV Result - > Success - EAP-TLV/Phase2 Completed > Feb 14 15:50:40 sofie wpa_supplicant[403]: CTRL-EVENT-EAP-SUCCESS EAP > authentication completed successfully > Feb 14 15:50:40 sofie wpa_supplicant[403]: WPA: Key negotiation > completed with 00:0b:86:5d:3a:40 [PTK=TKIP GTK=TKIP] > Feb 14 15:50:40 sofie wpa_supplicant[403]: CTRL-EVENT-CONNECTED - > Connection to 00:0b:86:5d:3a:40 completed (reauth) [id=1 id_str=] > Feb 14 15:50:40 sofie dhclient: New IP Address (ath0): 128.146.115.38 > Feb 14 15:50:40 sofie dhclient: New Subnet Mask (ath0): 255.255.255.0 > Feb 14 15:50:40 sofie dhclient: New Broadcast Address (ath0): > 128.146.115.255 > Feb 14 15:50:40 sofie dhclient: New Routers (ath0): 128.146.115.1 > Feb 14 15:55:48 sofie wpa_supplicant[403]: Trying to associate with > 00:0b:86:58:03:e0 (SSID='osuwireless' freq=2412 MHz) > Feb 14 15:55:48 sofie kernel: ath0: link state changed to DOWN > Feb 14 15:55:48 sofie wpa_supplicant[403]: CTRL-EVENT-DISCONNECTED - > Disconnect event - remove keys > Feb 14 15:55:58 sofie wpa_supplicant[403]: Authentication with > 00:00:00:00:00:00 timed out. > Feb 14 15:56:06 sofie wpa_supplicant[403]: Trying to associate with > 00:0b:86:58:04:00 (SSID='osuwireless' freq=2437 MHz) > Feb 14 15:56:16 sofie wpa_supplicant[403]: Authentication with > 00:0b:86:58:04:00 timed out. > Feb 14 15:56:23 sofie wpa_supplicant[403]: Trying to associate with > 00:0b:86:58:02:80 (SSID='osuwireless' freq=2437 MHz) > Feb 14 15:56:23 sofie wpa_supplicant[403]: Association request to the > driver failed > Feb 14 15:56:28 sofie wpa_supplicant[403]: Authentication with > 00:0b:86:58:02:80 timed out. > Feb 14 15:56:36 sofie wpa_supplicant[403]: Trying to associate with > 00:0b:86:5d:02:c0 (SSID='osuwireless' freq=2437 MHz) > Feb 14 15:56:36 sofie kernel: ath0: link state changed to UP > Feb 14 15:56:36 sofie wpa_supplicant[403]: Associated with > 00:0b:86:5d:02:c0 > Feb 14 15:56:36 sofie wpa_supplicant[403]: CTRL-EVENT-EAP-METHOD EAP > vendor 0 method 25 (PEAP) selected > Feb 14 15:56:36 sofie wpa_supplicant[403]: OpenSSL: > tls_connection_handshake - Failed to read possible Application Data > error:00000000:lib(0):func(0):reason(0) > Feb 14 15:56:43 sofie kernel: update_stats: bogus ndx0 -1, max 10, > mode 3 > Feb 14 15:57:14 sofie last message repeated 6 times > Feb 14 15:57:18 sofie wpa_supplicant[403]: CTRL-EVENT-EAP-STARTED EAP > authentication started > Feb 14 15:57:18 sofie wpa_supplicant[403]: CTRL-EVENT-EAP-METHOD EAP > vendor 0 method 25 (PEAP) selected > Feb 14 15:57:18 sofie wpa_supplicant[403]: OpenSSL: > tls_connection_handshake - Failed to read possible Application Data > error:00000000:lib(0):func(0):reason(0) > Feb 14 15:57:18 sofie wpa_supplicant[403]: EAP-MSCHAPV2: > Authentication succeeded > Feb 14 15:57:18 sofie wpa_supplicant[403]: EAP-TLV: TLV Result - > Success - EAP-TLV/Phase2 Completed > Feb 14 15:57:18 sofie wpa_supplicant[403]: CTRL-EVENT-EAP-SUCCESS EAP > authentication completed successfully > Feb 14 15:57:28 sofie kernel: update_stats: bogus ndx0 -1, max 10, > mode 3 > Feb 14 15:57:29 sofie kernel: ath0: link state changed to DOWN > Feb 14 15:57:29 sofie wpa_supplicant[403]: CTRL-EVENT-DISCONNECTED - > Disconnect event - remove keys > Feb 14 15:57:37 sofie wpa_supplicant[403]: Trying to associate with > 00:0b:86:5d:02:c0 (SSID='osuwireless' freq=2437 MHz) > Feb 14 15:57:37 sofie kernel: ath0: link state changed to UP > Feb 14 15:57:37 sofie wpa_supplicant[403]: Associated with > 00:0b:86:5d:02:c0 > Feb 14 15:57:37 sofie wpa_supplicant[403]: CTRL-EVENT-EAP-STARTED EAP > authentication started > Feb 14 15:57:37 sofie wpa_supplicant[403]: CTRL-EVENT-EAP-METHOD EAP > vendor 0 method 25 (PEAP) selected > Feb 14 15:57:37 sofie wpa_supplicant[403]: OpenSSL: > tls_connection_handshake - Failed to read possible Application Data > error:00000000:lib(0):func(0):reason(0) > Feb 14 15:57:37 sofie wpa_supplicant[403]: EAP-MSCHAPV2: > Authentication succeeded > Feb 14 15:57:37 sofie wpa_supplicant[403]: EAP-TLV: TLV Result - > Success - EAP-TLV/Phase2 Completed > Feb 14 15:57:37 sofie wpa_supplicant[403]: CTRL-EVENT-EAP-SUCCESS EAP > authentication completed successfully > Feb 14 15:57:41 sofie kernel: update_stats: bogus ndx0 -1, max 10, > mode 3 > Feb 14 15:57:41 sofie kernel: ath0: link state changed to DOWN > Feb 14 15:57:41 sofie wpa_supplicant[403]: CTRL-EVENT-DISCONNECTED - > Disconnect event - remove keys > Feb 14 15:57:49 sofie wpa_supplicant[403]: Trying to associate with > 00:0b:86:58:03:e0 (SSID='osuwireless' freq=2412 MHz) > Feb 14 15:57:49 sofie wpa_supplicant[403]: Association request to the > driver failed > Feb 14 15:57:54 sofie wpa_supplicant[403]: Authentication with > 00:0b:86:58:03:e0 timed out. > Feb 14 15:57:58 sofie dhclient: New IP Address (ath0): 128.146.115.38 > Feb 14 15:57:58 sofie dhclient: New Subnet Mask (ath0): 255.255.255.0 > Feb 14 15:57:58 sofie dhclient: New Broadcast Address (ath0): > 128.146.115.255 > Feb 14 15:57:58 sofie dhclient: New Routers (ath0): 128.146.115.1 > Feb 14 15:57:59 sofie dhclient: New Routers (ath0): 128.146.115.1 > Feb 14 15:58:01 sofie wpa_supplicant[403]: Trying to associate with > 00:0b:86:58:03:80 (SSID='osuwireless' freq=2412 MHz) > Feb 14 15:58:01 sofie kernel: ath0: link state changed to UP > Feb 14 15:58:01 sofie wpa_supplicant[403]: Associated with > 00:0b:86:58:03:80 > Feb 14 15:58:01 sofie wpa_supplicant[403]: CTRL-EVENT-EAP-STARTED EAP > authentication started > Feb 14 15:58:06 sofie wpa_supplicant[403]: CTRL-EVENT-EAP-METHOD EAP > vendor 0 method 25 (PEAP) selected > Feb 14 15:58:06 sofie wpa_supplicant[403]: OpenSSL: > tls_connection_handshake - Failed to read possible Application Data > error:00000000:lib(0):func(0):reason(0) > Feb 14 15:58:06 sofie wpa_supplicant[403]: EAP-MSCHAPV2: > Authentication succeeded > Feb 14 15:58:06 sofie wpa_supplicant[403]: EAP-TLV: TLV Result - > Success - EAP-TLV/Phase2 Completed > Feb 14 15:58:06 sofie wpa_supplicant[403]: CTRL-EVENT-EAP-SUCCESS EAP > authentication completed successfully > Feb 14 15:58:06 sofie wpa_supplicant[403]: WPA: Key negotiation > completed with 00:0b:86:58:03:80 [PTK=TKIP GTK=TKIP] > Feb 14 15:58:06 sofie wpa_supplicant[403]: CTRL-EVENT-CONNECTED - > Connection to 00:0b:86:58:03:80 completed (reauth) [id=1 id_str=] > Feb 14 15:58:25 sofie dhclient: New IP Address (ath0): 128.146.115.38 > Feb 14 15:58:25 sofie dhclient: New Subnet Mask (ath0): 255.255.255.0 > Feb 14 15:58:25 sofie dhclient: New Broadcast Address (ath0): > 128.146.115.255 > Feb 14 15:58:25 sofie dhclient: New Routers (ath0): 128.146.115.1 > Feb 14 16:03:34 sofie kernel: update_stats: bogus ndx0 -1, max 10, > mode 3 > Feb 14 16:06:56 sofie kernel: update_stats: bogus ndx0 -1, max 10, > mode 3 > Feb 14 16:06:57 sofie kernel: update_stats: bogus ndx0 -1, max 10, > mode 3 > > > Please let me know if additional information would be helpful. > > Cheers, > ~Jason > > > -- > ~ Jason Morgan > _______________________________________________ > 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" -- ~ Jason Morgan From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 14:50: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 C187B1065724 for ; Tue, 17 Feb 2009 14:50:58 +0000 (UTC) (envelope-from blogtiengviet@yahoo.com) Received: from web57103.mail.re3.yahoo.com (web57103.mail.re3.yahoo.com [216.252.111.116]) by mx1.freebsd.org (Postfix) with SMTP id 5F09C8FC0A for ; Tue, 17 Feb 2009 14:50:58 +0000 (UTC) (envelope-from blogtiengviet@yahoo.com) Received: (qmail 62968 invoked by uid 60001); 17 Feb 2009 14:24:16 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1234880656; bh=w4GLYkC0Rr636wPVsuIyWFWCxHzQsO2nZbiG6wf0cm0=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=UlyG65aCYZKIa7M9hNCKcOtx5N4nzkQO7PDXbxCySUarxjCgqea65ITZGakFm8eq1fhMolETIVkBFQHZM231RFDigcQ5nJS6lepHX4VC2ynQjfjCa0rqIyiJ2mDsP9m5NkacqvLO5JQGK+u/oULp/Jql39R65QhvnfIYvfNbomc= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=lUb52jO/KZaYgZuPp1+c1RAvxD9O5JtjKokYjybFS7GKhNnWcvmX4Gq4pVNdQxThUQ9hjj3u/wqZbGSdsJQIH+nrE5GTMKW9YRGGEsuNtm9f5KAoULuzo+wt1+nwqhjM9/5ruZi26JLKH5jxs9TnJdcQIldJhJehMasxaZ49xAI=; Message-ID: <292159.62731.qm@web57103.mail.re3.yahoo.com> X-YMail-OSG: OgWtrAQVM1nkv9d8HNm9Ac5hcpZ5atiisgUDaqeIIP7W0TPae6rr6_XsIfggs7Qac3vSFRjbmzgkyOA7Pckj11w_veXr24kON3AkdkJaGHOttYTVuMhdti41q05DhQ.8pexdxEPNW9ilQT6qrcozDRvi4Z4- Received: from [222.226.245.101] by web57103.mail.re3.yahoo.com via HTTP; Tue, 17 Feb 2009 06:24:16 PST X-Mailer: YahooMailWebService/0.7.289.1 Date: Tue, 17 Feb 2009 06:24:16 -0800 (PST) From: Blog Tieng Viet To: linimon@FreeBSD.org, freebsd-net@FreeBSD.org, freebsd-ipfw@FreeBSD.org In-Reply-To: <200902131430.n1DEUED7040530@freefall.freebsd.org> MIME-Version: 1.0 X-Mailman-Approved-At: Tue, 17 Feb 2009 16:42:17 +0000 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: How to protect FreeBSD from IP spoofing ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: blogtiengviet@yahoo.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2009 14:51:03 -0000 Dear all. I am a newbie of FreeBSD, would like to get alot of information about FreeBSD such as IPFW. I am annoyed by IP spoofing but dont have any way to prevent it. Can any one tell me how to do ? Thanks in advance. PS: I am using 6.4-PRERELEASE FreeBSD 6.4-PRERELEASE. The FreeBSD box is used for web server, and it is forwarded every parket of port 80 from LAN router. From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 17:20:46 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 6F1861065676; Tue, 17 Feb 2009 17:20:46 +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 44D938FC08; Tue, 17 Feb 2009 17:20:46 +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 n1HHKkls071498; Tue, 17 Feb 2009 17:20:46 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1HHKkIf071491; Tue, 17 Feb 2009 17:20:46 GMT (envelope-from linimon) Date: Tue, 17 Feb 2009 17:20:46 GMT Message-Id: <200902171720.n1HHKkIf071491@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/131781: [ndis] ndis keeps dropping the link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 17:20:47 -0000 Old Synopsis: ndis keeps dropping the link New Synopsis: [ndis] ndis keeps dropping the link Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Tue Feb 17 17:20:32 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=131781 From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 17:22: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 02C601065694 for ; Tue, 17 Feb 2009 17:22:58 +0000 (UTC) (envelope-from ady@ady.ro) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.freebsd.org (Postfix) with ESMTP id 917AE8FC12 for ; Tue, 17 Feb 2009 17:22:57 +0000 (UTC) (envelope-from ady@ady.ro) Received: by nf-out-0910.google.com with SMTP id e27so263198nfd.33 for ; Tue, 17 Feb 2009 09:22:56 -0800 (PST) MIME-Version: 1.0 Received: by 10.210.59.14 with SMTP id h14mr1880592eba.36.1234889737793; Tue, 17 Feb 2009 08:55:37 -0800 (PST) In-Reply-To: <292159.62731.qm@web57103.mail.re3.yahoo.com> References: <200902131430.n1DEUED7040530@freefall.freebsd.org> <292159.62731.qm@web57103.mail.re3.yahoo.com> Date: Tue, 17 Feb 2009 17:55:37 +0100 Message-ID: <78cb3d3f0902170855p70047aa0r655d8ba846d2458d@mail.gmail.com> From: Adrian Penisoara To: blogtiengviet@yahoo.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, freebsd-ipfw@freebsd.org Subject: Re: How to protect FreeBSD from IP spoofing ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 17:22:59 -0000 Hi, Check the ipfw(8) manual (includes examples) or rather go for pf (packetfilter) and check the pf.conf(5) manual. For pf you just need to add something like "antispoof for lo0". Regards, Adrian. On Tue, Feb 17, 2009 at 3:24 PM, Blog Tieng Viet wrote: > Dear all. > I am a newbie of FreeBSD, would like to get alot of information about > FreeBSD such as IPFW. > I am annoyed by IP spoofing but dont have any way to prevent it. > Can any one tell me how to do ? > Thanks in advance. > > PS: > I am using 6.4-PRERELEASE FreeBSD 6.4-PRERELEASE. > The FreeBSD box is used for web server, and it is forwarded every parket of > port 80 from LAN router. > > > > > _______________________________________________ > freebsd-ipfw@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw > To unsubscribe, send any mail to "freebsd-ipfw-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 17:48: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 7BD641065670 for ; Tue, 17 Feb 2009 17:48:01 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id F0FAE8FC13 for ; Tue, 17 Feb 2009 17:48:00 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id n1HHlxPL080013; Tue, 17 Feb 2009 18:47:59 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id n1HHlwQR080012; Tue, 17 Feb 2009 18:47:58 +0100 (CET) (envelope-from olli) Date: Tue, 17 Feb 2009 18:47:58 +0100 (CET) Message-Id: <200902171747.n1HHlwQR080012@lurza.secnetix.de> From: Oliver Fromme To: freebsd-net@FreeBSD.ORG X-Newsgroups: list.freebsd-net User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 17 Feb 2009 18:47:59 +0100 (CET) Cc: Subject: Packet filter performance on SMP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 17:48:01 -0000 Hi, I've asked this a week ago on the -ipfw list, but got no reply ... The -net list might be more appropriate. I'll have to implement a packet filter on machines with several cores (4 to 8). Which one of the available filters (IPFW, IPF, PF) will provide the best performance on such SMP machines? I heard that PF doesn't support SMP hardware very well -- is that true? Will IPFW be better? Thanks for any insights. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "We, the unwilling, led by the unknowing, are doing the impossible for the ungrateful. We have done so much, for so long, with so little, we are now qualified to do anything with nothing."         -- Mother Teresa From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 17:48: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 046521065670 for ; Tue, 17 Feb 2009 17:48:23 +0000 (UTC) (envelope-from espartano.mail@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153]) by mx1.freebsd.org (Postfix) with ESMTP id 8BB7F8FC1A for ; Tue, 17 Feb 2009 17:48:22 +0000 (UTC) (envelope-from espartano.mail@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so507102fgb.35 for ; Tue, 17 Feb 2009 09:48:21 -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=LXujSjWuKWwt3qI7j7CHyqvZPjLgLOSsUvAdrS9t1ak=; b=HNXGrIACt6/pwz+fJbz75PexTfqj3Dw/NWcT9z5LVO3go+vE8DBGiSwW7P4SqikGvp aLKKrE55zRKQiXuP+EE+925KO/EGSZ0Fw6tgwWvbFJRGTAXwzuS8HtfNB4Sv3UmY68H7 UDPMdbFEBo4km44lTBdSh0TktEQEblNGVb+3g= 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=h66WHvRdvpp2L1GDfjyuKu7nsSwYjWSgg4F6Eppaqy9UgTGPi65HwEqISBBNCtPUpc C29m+gJzN2BDBHQtpNPi4f6pTatFUWBrC4Q3h2rzZJKZ85GTgRIZzmg/dwuAavZwE7dL UcAT30Jnqg+UbNAiEElRAmFczRPkHM2azHr0c= MIME-Version: 1.0 Received: by 10.86.53.8 with SMTP id b8mr2163943fga.13.1234890904746; Tue, 17 Feb 2009 09:15:04 -0800 (PST) Date: Tue, 17 Feb 2009 11:15:04 -0600 Message-ID: From: Espartano To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: OT: Libnet 1.1 documentation X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 17:48:23 -0000 Hi folk, some one know where can i found the oficial documentation of Libnet 1.1.x ? or may be an tuto of it ? Thanks a lot. -- "Linux is for people who hate Windows, BSD is for people who love UNIX". "Social Engineer -> Because there is no patch for human stupidity" "The Unix Guru's View of Sex unzip ; strip ; touch ; grep ; finger ; mount ; fsck ; more ; yes ; umount ; sleep." "Documentation is like sex: when it is good, it is very, very good; and when it is bad, it is better than nothing." From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 18:22: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 78E21106567D; Tue, 17 Feb 2009 18:22:24 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id ACE358FC16; Tue, 17 Feb 2009 18:22:23 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by ewy14 with SMTP id 14so2630660ewy.19 for ; Tue, 17 Feb 2009 10:22:22 -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 :content-transfer-encoding; bh=jBiiX5sibT6sI8CnJcJm0j2bLqisv4rOmCzUB0Wlmo8=; b=QIIy0rKuHlmb4USdW147gBR4Y9kUbEk8/YdEACbSRB3AYPn2NDXjZKknB/XnN2M5ia MR13caN/kFs2qMuZNzh+qFAI4Jxq65TCuLbzOg9OybzUDntH56RJfW+Mbb2tDkGh24xx trY7DbPniGYITVwbHbmJLSNRjykH5zQR3g5CI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=XrIwILQ+Q2uQlV4nBiaHDOvK0HsUMsrXCALNN02stwhAQymx7/EqvjGHogyOQpIMCC nf5kM7CCrN11DkqshD6ZpDm1dWIgX3a6Tr0bTlNP6flC9FhrGIdUUf9AZA5Y7qkoQ/fx o9sFYbPWqyX5TcsITaUj68OG9LKU2ZVloLukk= MIME-Version: 1.0 Received: by 10.210.45.17 with SMTP id s17mr352837ebs.74.1234894942796; Tue, 17 Feb 2009 10:22:22 -0800 (PST) In-Reply-To: <200902171720.n1HHKkIf071491@freefall.freebsd.org> References: <200902171720.n1HHKkIf071491@freefall.freebsd.org> Date: Tue, 17 Feb 2009 19:22:22 +0100 Message-ID: <3a142e750902171022t74ac8b9am3b8b3bc283a6e46d@mail.gmail.com> From: "Paul B. Mahol" To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: weongyo@freebsd.org, adamk@voicenet.com, thompsa@freebsd.org Subject: Re: kern/131781: [ndis] ndis keeps dropping the link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 18:22:25 -0000 http://www.freebsd.org/cgi/query-pr.cgi?pr=131781 This one should not happen, 108 rate should get recognized. I will try to reproduce it on CURRENT. To OP, could you try 7 STABLE after 31 Jan? I guess it should not change anything but you never know. -- Paul From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 18:36: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 BB50C106564A for ; Tue, 17 Feb 2009 18:36:37 +0000 (UTC) (envelope-from prvs=julian=29260e750@elischer.org) Received: from smtp-outbound.ironport.com (smtp-outbound.ironport.com [63.251.108.112]) by mx1.freebsd.org (Postfix) with ESMTP id A7C918FC1A for ; Tue, 17 Feb 2009 18:36:37 +0000 (UTC) (envelope-from prvs=julian=29260e750@elischer.org) Received: from unknown (HELO julian-mac.elischer.org) ([10.251.60.150]) by smtp-outbound.ironport.com with ESMTP; 17 Feb 2009 10:08:11 -0800 Message-ID: <499AFD1D.4020907@elischer.org> Date: Tue, 17 Feb 2009 10:08:29 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: Oliver Fromme References: <200902171747.n1HHlwQR080012@lurza.secnetix.de> In-Reply-To: <200902171747.n1HHlwQR080012@lurza.secnetix.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@FreeBSD.ORG Subject: Re: Packet filter performance on SMP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 18:36:38 -0000 Oliver Fromme wrote: > Hi, > > I've asked this a week ago on the -ipfw list, but got no > reply ... The -net list might be more appropriate. > > I'll have to implement a packet filter on machines with > several cores (4 to 8). Which one of the available filters > (IPFW, IPF, PF) will provide the best performance on such > SMP machines? I heard that PF doesn't support SMP hardware > very well -- is that true? Will IPFW be better? Not a lot of testing has been done on this topic yet. I know that this is not what you want to hear but it is possible that you might be the person to try it out (using the tunables to disable different number of CPUs) and see how it works out. let us know if you get any interesting results. Ipfw has a single rw lock guarding the entire rule set but it only does a reader lock on packet processing so multiple CPUs can be in there at the same time. It does not however protect the statistics on each rule so if two cpus try update the stats at the same time, one of them will miss out. (this has been considered an acceptable loss of accuracy in order to maintain throughput I guess). > Thanks for any insights. > > Best regards > Oliver > From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 18: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 2AB82106567C for ; Tue, 17 Feb 2009 18:37:01 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from spamfish.visualtech.com (h-67-102-187-40.phlapafg.covad.net [67.102.187.40]) by mx1.freebsd.org (Postfix) with ESMTP id DBA2B8FC08 for ; Tue, 17 Feb 2009 18:36:59 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from mailstore.visualtech.com (unknown [67.102.187.41]) by spamfish.visualtech.com (Postfix) with ESMTPS id B0EB41F44A3; Tue, 17 Feb 2009 13:29:23 -0500 (EST) Received: from memory.visualtech.com (h-67-103-204-242.phlapafg.covad.net [67.103.204.242]) by mailstore.visualtech.com (Postfix) with ESMTP id 08664ADC25E; Tue, 17 Feb 2009 13:44:01 -0500 (EST) Date: Tue, 17 Feb 2009 13:34:04 -0500 From: Adam K Kirchhoff To: "Paul B. Mahol" Message-ID: <20090217133404.22275b25@memory.visualtech.com> In-Reply-To: <3a142e750902171022t74ac8b9am3b8b3bc283a6e46d@mail.gmail.com> References: <200902171720.n1HHKkIf071491@freefall.freebsd.org> <3a142e750902171022t74ac8b9am3b8b3bc283a6e46d@mail.gmail.com> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; i386-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-visualtech-MailScanner: Found to be clean Cc: freebsd-net@freebsd.org, weongyo@freebsd.org, thompsa@freebsd.org Subject: Re: kern/131781: [ndis] ndis keeps dropping the link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 18:37:01 -0000 On Tue, 17 Feb 2009 19:22:22 +0100 "Paul B. Mahol" wrote: > http://www.freebsd.org/cgi/query-pr.cgi?pr=131781 > > This one should not happen, 108 rate should get recognized. > I will try to reproduce it on CURRENT. > > To OP, could you try 7 STABLE after 31 Jan? I guess it should not > change anything but you never know. Sorry, I must have copied and pasted the uname output from the wrong machine. This is actually FreeBSD 7.1-STABLE #4: Mon Feb 16 16:37:18 EST 2009 :-) Could the fact that the rate is 108 also be causing problems for the native iwi driver? Adam -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 19:44: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 B97C11065672 for ; Tue, 17 Feb 2009 19:44:44 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.168]) by mx1.freebsd.org (Postfix) with ESMTP id 8D0888FC12 for ; Tue, 17 Feb 2009 19:44:44 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: by wf-out-1314.google.com with SMTP id 27so2831258wfd.7 for ; Tue, 17 Feb 2009 11:44:44 -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:content-type :content-transfer-encoding; bh=f27kbW56fIDvCtak0KdJqTVIfan2qdEziw7iVF+zwew=; b=n4vXH9VccwyGifEVzOc+RbPO7fUhHI462FD2uHrIzkcvOxHIxdA+bUAOlu59rRTSg9 gOu6KCONXfroT8SwHevWu0lOdXFynW2jNtLDnI8oS99r88+QOHPXd4xzXN4Hst29t8TW P5riFjes591q8GYZiOirfiOAAhJoBrbL9itTg= 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 :content-type:content-transfer-encoding; b=MTkVmRRLXodQNYqBgKIUxJGl50XNEQfTY5xRkQNKGNQvMm8zBW6fqtsB4Hl2pge8gh WsbhRcJwISWOYZrArgVM2daEaGpBqJSoIqJ9T6vwY1H/jLXAcq21uZuiFFxsOQkKRgKf nvDyvfkB5FoeyjqNXP87zs7EawIDHgcGX16mk= MIME-Version: 1.0 Received: by 10.143.3.7 with SMTP id f7mr3110472wfi.92.1234898480867; Tue, 17 Feb 2009 11:21:20 -0800 (PST) In-Reply-To: References: <85c4b1850902170448p7a59d50bt6bdaa89aa01c51d7@mail.gmail.com> <20090217143425.GA58591@zeninc.net> <20090217143409.J53478@maildrop.int.zabbadoz.net> Date: Tue, 17 Feb 2009 11:21:20 -0800 Message-ID: From: Kurt Buff To: freebsd-net@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Fwd: NATT patch and FreeBSD's setkey X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 19:44:45 -0000 My bad - didn't send to list. See below. ---------- Forwarded message ---------- From: Kurt Buff Date: Tue, Feb 17, 2009 at 11:20 AM Subject: Re: NATT patch and FreeBSD's setkey To: "Bjoern A. Zeeb" On Tue, Feb 17, 2009 at 6:41 AM, Bjoern A. Zeeb wrote: > On Tue, 17 Feb 2009, VANHULLEBUS Yvan wrote: > > Hi, > >> If someone has a magic solution without drawbacks, please tell us ! > > I am not going to find my posting from a few years back but the > solution is to keep the kernel and libipsec (and setkey) in base in > sync and not install libipsec and setkey from the ipsec-tools port. > Done. > > That obviously means that people who patch their kernel need to patch > their user space as well but that should not be a problem as they > rebuild anyway and need to build ipsec-tools racoon etc. on their own > to use the new features as w/o changing the default options it doesn't > work for nat-t. > > That also allows other 3rd party utilities using libipsec to continue > to do so and use all "features" w/o needing another fork. > > > >>> Has anyone had any success using the patched FreeBSD along with racoon2. >> >> I just don't know what's the actual status of racoon2, but nat-t >> patchset is public and everyone can send changes if that helps >> interaction with other daemons (without breaking again the API if >> possible.....). > > We have about 3 months left to get that patch in for 8; ideally 6 > weeks. Can you update the nat-t patch in a way as discussed here > before so that the extra address is in etc. and we can move forward? > > I basically do not care if racoon from ipsec-tools is not going to > work for two weeks of HEAD or four as someone will quickly add a > conditional patch to the port for a __FreeBSD_version > 8xxxxx and > that can be removed once ipsec-tools properly detect the state of the > system. > > /bz > > -- > Bjoern A. Zeeb The greatest risk is not taking one. Forgive my ignorance, but is this the same patch required by' /usr/ports/security/ike - Shrew Soft IKE daemon and client tools'? Kurt From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 22:14:08 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB76C106568B for ; Tue, 17 Feb 2009 22:14:08 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.freebsd.org (Postfix) with ESMTP id 6AF598FC15 for ; Tue, 17 Feb 2009 22:14:08 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by nf-out-0910.google.com with SMTP id e27so274346nfd.33 for ; Tue, 17 Feb 2009 14:14:07 -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 :content-transfer-encoding; bh=mg4vuwqquVgmwh+uIHl48MHOpqBh98ZChNY+kh9HE1o=; b=aRKWsEgDsUAHt7uvYfIanwqw5OSjs/YXrEcMjhOp9bOB/G1beaDw9qV/OnvquJB6sD 1lSQC2cxLT457AnTzzwvsJrwG9q+subDJCVYjRboKa/MqsjthvcAe/rv1vcEU23LKTC4 zPnWIcOo80kuL3qdbAcOxIOc4QuZ4kqSfgVdc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=bNEhIB4tNxkofrT+TWQ2/oegHgyylP+EJ36Me82buH9UhL3Ws/Wedcfh7KGqHhkC5s EbHiynFIgK2nQWj8Ui8Of295XTZeB1bX/PIQgLNW4QbQm4ue6aVvjydk5LTCQaY+3znO OIFaq7ba99yQeyUxvuK5nP4zQ2o0uoITlkXmo= MIME-Version: 1.0 Received: by 10.210.29.17 with SMTP id c17mr1531490ebc.177.1234908847554; Tue, 17 Feb 2009 14:14:07 -0800 (PST) In-Reply-To: <20090217133404.22275b25@memory.visualtech.com> References: <200902171720.n1HHKkIf071491@freefall.freebsd.org> <3a142e750902171022t74ac8b9am3b8b3bc283a6e46d@mail.gmail.com> <20090217133404.22275b25@memory.visualtech.com> Date: Tue, 17 Feb 2009 23:14:07 +0100 Message-ID: <3a142e750902171414p438d184bl54a1569e27490634@mail.gmail.com> From: "Paul B. Mahol" To: Adam K Kirchhoff Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: kern/131781: [ndis] ndis keeps dropping the link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 22:14:09 -0000 On 2/17/09, Adam K Kirchhoff wrote: > On Tue, 17 Feb 2009 19:22:22 +0100 > "Paul B. Mahol" wrote: > >> http://www.freebsd.org/cgi/query-pr.cgi?pr=131781 >> >> This one should not happen, 108 rate should get recognized. >> I will try to reproduce it on CURRENT. >> >> To OP, could you try 7 STABLE after 31 Jan? I guess it should not >> change anything but you never know. > > Sorry, I must have copied and pasted the uname output from the wrong > machine. This is actually FreeBSD 7.1-STABLE #4: Mon Feb 16 16:37:18 > EST 2009 :-) miniport dump NDIS_STATUS_UNSUPPORTED_MEDIA for error in ndis_setstate() for setting OID_802_11_CONFIGURATION. > Could the fact that the rate is 108 also be causing problems for the > native iwi driver? Unlikely, bug is in ndisulator initialization code. -- Paul From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 22:29:49 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 234A110656D3 for ; Tue, 17 Feb 2009 22:29:49 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from spamfish.visualtech.com (h-67-102-187-40.phlapafg.covad.net [67.102.187.40]) by mx1.freebsd.org (Postfix) with ESMTP id CA4338FC1C for ; Tue, 17 Feb 2009 22:29:48 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from mailstore.visualtech.com (unknown [67.102.187.41]) by spamfish.visualtech.com (Postfix) with ESMTPS id CADA51F454B; Tue, 17 Feb 2009 17:23:15 -0500 (EST) Received: from sorrow.ashke.com (c-68-45-151-98.hsd1.nj.comcast.net [68.45.151.98]) by mailstore.visualtech.com (Postfix) with ESMTP id A8BC6ADC25B; Tue, 17 Feb 2009 17:37:56 -0500 (EST) From: Adam K Kirchhoff To: freebsd-net@freebsd.org Date: Tue, 17 Feb 2009 17:27:52 -0500 User-Agent: KMail/1.10.4 (FreeBSD/7.1-STABLE; KDE/4.1.4; i386; ; ) References: <200902171720.n1HHKkIf071491@freefall.freebsd.org> <20090217133404.22275b25@memory.visualtech.com> <3a142e750902171414p438d184bl54a1569e27490634@mail.gmail.com> In-Reply-To: <3a142e750902171414p438d184bl54a1569e27490634@mail.gmail.com> MIME-Version: 1.0 Message-Id: <200902171727.53156.adamk@voicenet.com> X-visualtech-MailScanner: Found to be clean Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "Paul B. Mahol" Subject: Re: kern/131781: [ndis] ndis keeps dropping the link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 22:29:49 -0000 On Tuesday 17 February 2009 17:14:07 Paul B. Mahol wrote: > On 2/17/09, Adam K Kirchhoff wrote: > > On Tue, 17 Feb 2009 19:22:22 +0100 > > > > "Paul B. Mahol" wrote: > >> http://www.freebsd.org/cgi/query-pr.cgi?pr=131781 > >> > >> This one should not happen, 108 rate should get recognized. > >> I will try to reproduce it on CURRENT. > >> > >> To OP, could you try 7 STABLE after 31 Jan? I guess it should not > >> change anything but you never know. > > > > Sorry, I must have copied and pasted the uname output from the wrong > > machine. This is actually FreeBSD 7.1-STABLE #4: Mon Feb 16 16:37:18 > > EST 2009 :-) > > miniport dump NDIS_STATUS_UNSUPPORTED_MEDIA for error in > ndis_setstate() for setting OID_802_11_CONFIGURATION. Sorry if I seem slow, but are you asking me to check something there, or just stating what you think the problem is? :-) > > Could the fact that the rate is 108 also be causing problems for the > > native iwi driver? > > Unlikely, bug is in ndisulator initialization code. Oh well :-) I'll take what I can get at this point. Adam -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 22:48:41 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 AE0551065675 for ; Tue, 17 Feb 2009 22:48:41 +0000 (UTC) (envelope-from kalin@el.net) Received: from mail.el.net (mail.el.net [74.1.12.120]) by mx1.freebsd.org (Postfix) with ESMTP id 4BBC58FC1D for ; Tue, 17 Feb 2009 22:48:41 +0000 (UTC) (envelope-from kalin@el.net) Received: (qmail 86360 invoked by uid 1008); 17 Feb 2009 23:24:18 -0000 Received: from unknown (HELO kalins-macbook-pro.local) (kalin@el.net@74.1.12.115) by mail.el.net with ESMTPA; 17 Feb 2009 23:24:18 -0000 Message-ID: <499B3888.2000701@el.net> Date: Tue, 17 Feb 2009 17:22:00 -0500 From: kalin m User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: freebsd-net@freebsd.org, freebsd-mobile@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: sms gprs gsm edge X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 22:48:42 -0000 hi all... just looking for a few pointers for setting up a sms gateway. if somebody would like to share some knowledge on successfully implemented hardware (gprs/gsm/edge modems/drivers) and software like kannel, smstools, etc... for example i just talked to a salesperson at a company called moxa (http://www.moxa.com/product/oncell_g3100.htm) and was looking at their g3100 model gprs modem. according to their own specifications they have freebsd drivers. anybody has had any experience with those?! any information will be appreciated.. thank you.... From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 23:40: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 0E1E91065672; Tue, 17 Feb 2009 23:40:46 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [91.103.162.4]) by mx1.freebsd.org (Postfix) with ESMTP id C23D88FC15; Tue, 17 Feb 2009 23:40:45 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from localhost (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 00D2019E027; Wed, 18 Feb 2009 00:20:48 +0100 (CET) Received: from [192.168.1.2] (r5bb235.net.upc.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id B494519E023; Wed, 18 Feb 2009 00:20:45 +0100 (CET) Message-ID: <499B464C.5020409@quip.cz> Date: Wed, 18 Feb 2009 00:20:44 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: cz, cs, en, en-us MIME-Version: 1.0 To: kalin m References: <499B3888.2000701@el.net> In-Reply-To: <499B3888.2000701@el.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: sms gprs gsm edge X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 23:40:46 -0000 kalin m wrote: > > hi all... > > just looking for a few pointers for setting up a sms gateway. > if somebody would like to share some knowledge on successfully > implemented hardware (gprs/gsm/edge modems/drivers) and software like > kannel, smstools, etc... > > for example i just talked to a salesperson at a company called moxa > (http://www.moxa.com/product/oncell_g3100.htm) and was looking at their > g3100 model gprs modem. according to their own specifications they have > freebsd drivers. anybody has had any experience with those?! > > any information will be appreciated.. > thank you.... I used Siemens MC35i GSM modem over COM1 with smstools few years ago (with FreeBSD 4.x). No special drivers needed. It was used to send and receive SMS with our custom PHP web application. I don't know what is your definition of "sms gateway". Miroslav Lachman From owner-freebsd-net@FreeBSD.ORG Tue Feb 17 23:45:12 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C7B81065687; Tue, 17 Feb 2009 23:45:12 +0000 (UTC) (envelope-from peo@intersonic.se) Received: from neonpark.inter-sonic.com (neonpark.inter-sonic.com [212.247.8.98]) by mx1.freebsd.org (Postfix) with ESMTP id 100178FC28; Tue, 17 Feb 2009 23:45:12 +0000 (UTC) (envelope-from peo@intersonic.se) X-Virus-Scanned: amavisd-new at BSDLabs AB Message-ID: <499B4878.7060103@intersonic.se> Date: Wed, 18 Feb 2009 00:30:00 +0100 From: Per olof Ljungmark Organization: Intersonic AB User-Agent: Thunderbird 2.0.0.19 (X11/20090208) MIME-Version: 1.0 To: kalin m References: <499B3888.2000701@el.net> In-Reply-To: <499B3888.2000701@el.net> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: sms gprs gsm edge X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Feb 2009 23:45:13 -0000 kalin m wrote: > > hi all... > > just looking for a few pointers for setting up a sms gateway. > if somebody would like to share some knowledge on successfully > implemented hardware (gprs/gsm/edge modems/drivers) and software like > kannel, smstools, etc... > > for example i just talked to a salesperson at a company called moxa > (http://www.moxa.com/product/oncell_g3100.htm) and was looking at their > g3100 model gprs modem. according to their own specifications they have > freebsd drivers. anybody has had any experience with those?! > Hi, I know that a collegue here used a Siemens TC65 GSM Modem together with smstools and sms_client from ports to set up a sms paging system that works well. If you'd like I could ask him to send you more detailed info on how it was implemented. I also believe that the engine in this modem is available in various packages, the TC65 is a standalone unit needing only the sim card and antenna to work. It is connected over a usb to serial adapter and required no special drivers. -- per From owner-freebsd-net@FreeBSD.ORG Wed Feb 18 10:16: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 A4B7710656D4 for ; Wed, 18 Feb 2009 10:16:57 +0000 (UTC) (envelope-from dikshie@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.29]) by mx1.freebsd.org (Postfix) with ESMTP id 5C3E18FC1F for ; Wed, 18 Feb 2009 10:16:57 +0000 (UTC) (envelope-from dikshie@gmail.com) Received: by yx-out-2324.google.com with SMTP id 31so1382858yxl.13 for ; Wed, 18 Feb 2009 02:16:56 -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=7JmoHWICPr6oP6NqWVNXVTLkEVWcqbgCCny9BLfGEe4=; b=VmeqAHTM4HBv9MVK4ntNjcRJYMFCi1o1UDBds5kLfXXYOopk1uzG6aRCTduZiM3AgK +5J57AUiTirDNrQO8Vwe1qFuO068GUW3s0FvLjt12RDetbRUxXrSP+x7dTdeAZtDhdIm dT3BjLy1LkOxID6f1Wx/lmX+1Z04k1zhg7HUg= 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=fzPtWKN73Rn+oBTo/AfLJLMwyr0kP+Ox/fQiNQcBG/OOIDplbIj/QNtibmCe2LrsnL j9DTNqTloM1E2bdWHdlqcXKQAeCkqBmf1W0YGClBCmMIOwM/vf18XpdVvsy2r9gGVOU+ LpyZzxsJ3391KPIVKIOqPCJqglsRt5rsARc0E= MIME-Version: 1.0 Received: by 10.150.225.14 with SMTP id x14mr530345ybg.66.1234950624877; Wed, 18 Feb 2009 01:50:24 -0800 (PST) Date: Wed, 18 Feb 2009 18:50:24 +0900 Message-ID: <910e60e80902180150n41a592ffyb62ea53beb24f1ef@mail.gmail.com> From: dikshie To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: panic: _rw_wlock_hard X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Feb 2009 10:17:01 -0000 Hi, does anyone see this panic on -HEAD: panic: _rw_wlock_hard: recursing but non-recursive rw radix node head @ /usr/src/sys/net/route.c:831 kdb_enter() at kdb_enter+0x3a panic() at panic+0x136 _rw_wlock_hard() at _rw_wlock_hard+0x66 _rw_wlock() at _rw_wlock+0xae rtquest1_fib() at rtquest1_fib+0x95 rtquest_fib() at rtquest_fib+0x5e in_rtquest() at in_rtquest+0x3b in_rtqkill() at in_rtqkill+0x7f rn_walktree() at rn_walktree+0x65 in_rtqtimo() at in_rtqtimo+0xb0 softclock() at softclock+0x24a intr_event_execute_handlers() at intr_event_execute_handlers+0x125 ithread_loop() at ithread_loop+0x9f fork_exit() at fork_exit+0xb8 fork_trampoline() at fork_trampoline+0x8 -HEAD built on Feb 16 14:26:25 JST. -- -dikshie- From owner-freebsd-net@FreeBSD.ORG Wed Feb 18 11:06: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 6979710656CB for ; Wed, 18 Feb 2009 11:06:22 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.freebsd.org (Postfix) with ESMTP id EE2C48FC1C for ; Wed, 18 Feb 2009 11:06:21 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by nf-out-0910.google.com with SMTP id e27so304106nfd.33 for ; Wed, 18 Feb 2009 03:06:21 -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 :content-transfer-encoding; bh=AL6hX8yZrGCZH2v3ecXPpsMgu7u+azVHx/6e9LD3qLo=; b=BcQxPXC5j4Nfi8JJCgBrhu1PWo5oFjgMV7kV7SRDQWtHRFngW53a3YgSVYdnstjQB/ Nu+PlFULfGRDb/2j7uVVVpuDSIhAY+w8KouRXAfw4rii6Sw247/w+FmFOPE/5YQBhA7n j+zS6JJBJHE92q+8H/s3gtedaoo8JiX0f3cTk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=JZ+eJ2xOE1nrKsOv3WROEyXe6Sik1RmtNNzQixtPfP70FAoaSq5mvEevPuABtm83jb L45dvRTgc0Ze0YtQ3pcJktw09a4u4qGrdu9beVATibDetFaTBN4A5HeRoWzdZltvG6K3 BIhGcxB/YlPrzVU/inL+9x3C3vF0Xz4rpnVHo= MIME-Version: 1.0 Received: by 10.210.12.18 with SMTP id 18mr1547251ebl.180.1234955181055; Wed, 18 Feb 2009 03:06:21 -0800 (PST) In-Reply-To: <200902171727.53156.adamk@voicenet.com> References: <200902171720.n1HHKkIf071491@freefall.freebsd.org> <20090217133404.22275b25@memory.visualtech.com> <3a142e750902171414p438d184bl54a1569e27490634@mail.gmail.com> <200902171727.53156.adamk@voicenet.com> Date: Wed, 18 Feb 2009 12:06:21 +0100 Message-ID: <3a142e750902180306x390fd549led076474f4fae06b@mail.gmail.com> From: "Paul B. Mahol" To: Adam K Kirchhoff Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: kern/131781: [ndis] ndis keeps dropping the link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Feb 2009 11:06:23 -0000 On 2/17/09, Adam K Kirchhoff wrote: > On Tuesday 17 February 2009 17:14:07 Paul B. Mahol wrote: >> On 2/17/09, Adam K Kirchhoff wrote: >> > On Tue, 17 Feb 2009 19:22:22 +0100 >> > >> > "Paul B. Mahol" wrote: >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=131781 >> >> >> >> This one should not happen, 108 rate should get recognized. >> >> I will try to reproduce it on CURRENT. >> >> >> >> To OP, could you try 7 STABLE after 31 Jan? I guess it should not >> >> change anything but you never know. >> > >> > Sorry, I must have copied and pasted the uname output from the wrong >> > machine. This is actually FreeBSD 7.1-STABLE #4: Mon Feb 16 16:37:18 >> > EST 2009 :-) >> >> miniport dump NDIS_STATUS_UNSUPPORTED_MEDIA for error in >> ndis_setstate() for setting OID_802_11_CONFIGURATION. > > Sorry if I seem slow, but are you asking me to check something there, or > just > stating what you think the problem is? :-) You can add printf() before "ndis_set_info(sc, OID_802_11_CONFIGURATION, &config, &len);" in ndis_setstate_80211() to check what value for config.nc_dsconfig is by default. Also try changing "sysctl debug.ndis=1" and post console debug ouput again. > >> > Could the fact that the rate is 108 also be causing problems for the >> > native iwi driver? >> >> Unlikely, bug is in ndisulator initialization code. > > Oh well :-) I'll take what I can get at this point. > > Adam > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > -- Paul From owner-freebsd-net@FreeBSD.ORG Wed Feb 18 12:45: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 B4DA11065670 for ; Wed, 18 Feb 2009 12:45:42 +0000 (UTC) (envelope-from sepron@gmail.com) Received: from mail-gx0-f224.google.com (mail-gx0-f224.google.com [209.85.217.224]) by mx1.freebsd.org (Postfix) with ESMTP id 5E4C58FC14 for ; Wed, 18 Feb 2009 12:45:42 +0000 (UTC) (envelope-from sepron@gmail.com) Received: by gxk24 with SMTP id 24so6693123gxk.19 for ; Wed, 18 Feb 2009 04:45:41 -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:content-type; bh=/WJ2GjOOYdwf4/k9ARxPqebRFZ4W4Skb8epp5WewYyA=; b=spytAwqmf+9oTEBK9GsRmkezGz4Qtm5TJd31iwbsCxtZ2NdGUppuaBmVy8SuYMEIM2 gtBVh6B1aGp3D4k7Jzkiphf2duKEAHWLdIrp51bp+c6TUSE+2Qbq8EYDf44KfWyoEQi1 Yb5L8mTz0l/CtrKW4WEu1TQp+wgmFAgbADIeE= 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 :content-type; b=AXKUwmeuQYWtMOBWq6XD0Fva3YpLuyY6oMoxcNj9gYmuV82Q799MASfKoz2DahWC9i XD7n8Kn+e+ZyOlfAr5sp4B4McjFeKDGXAPcxFeuz241rifiHeimBAYWNVUELuY6wpdIP OKDB9e0dZXXIZAU//tmdZBz05To7tP68ilJwY= MIME-Version: 1.0 Received: by 10.151.47.7 with SMTP id z7mr26391ybj.110.1234961141886; Wed, 18 Feb 2009 04:45:41 -0800 (PST) In-Reply-To: <000f01c990e0$a70c1230$f5243690$@net> References: <000f01c990e0$a70c1230$f5243690$@net> Date: Wed, 18 Feb 2009 15:45:41 +0300 Message-ID: From: Sergey Pronin To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Synopsis: process swi1:net gives 100% CPU usage. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Feb 2009 12:45:43 -0000 Good day. As I'm using mpd4 I have mpd.conf and mpd.links. There are lots of static ngs created. So I'll post just a pattern of my mpd.conf: pppoe_def: set bundle disable multilink set bundle disable round-robin set bundle enable noretry set ipcp dns X.X.X.X Y.Y.Y.Y set iface disable on-demand set iface disable proxy-arp set iface enable tcpmssfix set link keep-alive 3 12 # set link mtu 1300 # set link mru 1460 set link max-redial -1 set pppoe service "*" set pppoe enable incoming set link enable chap set link enable chap-md5 set link enable chap-msv1 set link enable chap-msv2 set link disable passive callback no-orig-auth check-magic log -chat -bund -fsm -pptp set iface up-script "/root/scripts/up-script.pl" set iface down-script "/root/scripts/down-script.pl" set ipcp disable vjcomp set auth disable internal set auth enable radius-auth set radius server Z.Z.Z.Z password 1812 1813 set radius timeout 10 set radius retries 3 #ngctl types There are 27 total types: Type name Number of living nodes --------- ---------------------- pppoe 144 socket 2222 iface 2077 hole 0 gif_demux 0 gif 0 frame_relay 0 ether 560 echo 0 cisco 0 vjc 3 tty 0 tee 0 tcpmss 233 bridge 0 rfc1490 0 pptpgre 0 bpf 0 ppp 2076 one2many 0 async 0 mppc 0 lmi 0 UI 0 l2tp 0 ksocket 0 ip_input 0 I've tried to compile the kernel with and without netgraph options. I haven't seen any benefit. swi1:net still uses 100% CPU. I have the same problem with netgraph on 7.1-RELEASE, mpd 5.2, AMD Phenom. > Dummynet, divert and pf > are disabled in the kernel. > > While swi1:net (aka netgraph) is using 100% of CPU time m_tag_locate() and > ng_iface_output() > are constantly called from the infinite loop. > > Sergey, could you provide the content of mpd.conf and the output of "ngctl > types". > From owner-freebsd-net@FreeBSD.ORG Wed Feb 18 13:05: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 92AF61065690 for ; Wed, 18 Feb 2009 13:05:42 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from spamfish.visualtech.com (h-67-102-187-40.phlapafg.covad.net [67.102.187.40]) by mx1.freebsd.org (Postfix) with ESMTP id 486998FC13 for ; Wed, 18 Feb 2009 13:05:41 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from mailstore.visualtech.com (unknown [67.102.187.41]) by spamfish.visualtech.com (Postfix) with ESMTPS id 08F3E1F458B; Wed, 18 Feb 2009 07:59:33 -0500 (EST) Received: from memory.visualtech.com (h-67-103-204-242.phlapafg.covad.net [67.103.204.242]) by mailstore.visualtech.com (Postfix) with ESMTP id A37D0ADC25B; Wed, 18 Feb 2009 08:14:22 -0500 (EST) Date: Wed, 18 Feb 2009 08:04:20 -0500 From: Adam K Kirchhoff To: "Paul B. Mahol" Message-ID: <20090218080420.681788d2@memory.visualtech.com> In-Reply-To: <3a142e750902180306x390fd549led076474f4fae06b@mail.gmail.com> References: <200902171720.n1HHKkIf071491@freefall.freebsd.org> <20090217133404.22275b25@memory.visualtech.com> <3a142e750902171414p438d184bl54a1569e27490634@mail.gmail.com> <200902171727.53156.adamk@voicenet.com> <3a142e750902180306x390fd549led076474f4fae06b@mail.gmail.com> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; i386-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-visualtech-MailScanner: Found to be clean Cc: freebsd-net@freebsd.org Subject: Re: kern/131781: [ndis] ndis keeps dropping the link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Feb 2009 13:05:43 -0000 On Wed, 18 Feb 2009 12:06:21 +0100 "Paul B. Mahol" wrote: > On 2/17/09, Adam K Kirchhoff wrote: > > On Tuesday 17 February 2009 17:14:07 Paul B. Mahol wrote: > >> On 2/17/09, Adam K Kirchhoff wrote: > >> > On Tue, 17 Feb 2009 19:22:22 +0100 > >> > > >> > "Paul B. Mahol" wrote: > >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=131781 > >> >> > >> >> This one should not happen, 108 rate should get recognized. > >> >> I will try to reproduce it on CURRENT. > >> >> > >> >> To OP, could you try 7 STABLE after 31 Jan? I guess it should not > >> >> change anything but you never know. > >> > > >> > Sorry, I must have copied and pasted the uname output from the wrong > >> > machine. This is actually FreeBSD 7.1-STABLE #4: Mon Feb 16 16:37:18 > >> > EST 2009 :-) > >> > >> miniport dump NDIS_STATUS_UNSUPPORTED_MEDIA for error in > >> ndis_setstate() for setting OID_802_11_CONFIGURATION. > > > > Sorry if I seem slow, but are you asking me to check something there, or > > just > > stating what you think the problem is? :-) > > You can add printf() before "ndis_set_info(sc, > OID_802_11_CONFIGURATION, &config, &len);" in ndis_setstate_80211() to > check what value for config.nc_dsconfig is by default. I'll try that shortly. > Also try changing "sysctl debug.ndis=1" and post console debug ouput again. This was strange. If I boot up and enable debugging before I try to run '/etc/rc.d/netif start ndis0' everything works just fine. I get an IP address and stay connected (at least under a light load). This is the output: ndis_newstate: INIT -> INIT ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS ERROR: c0001392 (unknown error) Setting BSSID to ff:ff:ff:ff:ff:ff Setting ESSID to "" ndis0: no matching rate for: 108 ndis_newstate: INIT -> RUN ndis0: link state changed to UP ndis_newstate: RUN -> INIT Setting channel to 2412000kHz ndis0: couldn't change DS config to 2412000kHz: 19 Setting BSSID to ff:ff:ff:ff:ff:ff Setting ESSID to "Mckella280Front" ndis0: link state changed to DOWN ndis0: no matching rate for: 108 ndis_newstate: INIT -> RUN ndis0: link state changed to UP If I then stop the network on that device, disable debug, and try to start it up again, I get the same problem as before: ndis0: couldn't change DS config to 2412000kHz: 19 ndis0: link state changed to DOWN ndis0: no matching rate for: 108 ndis0: link state changed to UP ndis0: couldn't change DS config to 2412000kHz: 19 ndis0: link state changed to DOWN ndis0: no matching rate for: 108 ndis0: link state changed to UP ndis0: link state changed to DOWN If I then stop the network, enable debugging, and start up the network, the problem persists. Adam -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-net@FreeBSD.ORG Wed Feb 18 15:33: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 1E92B1065673 for ; Wed, 18 Feb 2009 15:33:58 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id 995CB8FC1C for ; Wed, 18 Feb 2009 15:33:56 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by ewy14 with SMTP id 14so3061113ewy.19 for ; Wed, 18 Feb 2009 07:33:56 -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 :content-transfer-encoding; bh=bW2aOqZdWU2Uxjm0BoIVAFoJRd0jaPPYAuCfRkdfpgU=; b=jq2OakIQhNRyRvd+4rCa2N79W7+pzgSN/5CmNge8EZMzKwvK6TGa4QPY9i2iWNrOuN thE/vbdICLJyoAEV8c+WG9vZZwP8wLqmqNexBJPRGR/qsIF18S1ax9JxuMFHQgUz9cxd UsUh6PbPrAJh58ZIICs/Xls9htNw9/K/I9RTQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=tIneoNo9t9+p7JXrfF5abxapSGNjNfm6aCLUsS+n5MbF/tkHRpM8tyDMBr1gF5fzhj 3Yxaaj2OlrhT5XBNL694rBpB1MXHJrd1MNVGcsqnn2QljjuXcIqLYCDksWaHXPLy1tye BHodNecvxjfKaXILTncj66FPdovPViJ4n5ako= MIME-Version: 1.0 Received: by 10.210.91.7 with SMTP id o7mr3290437ebb.61.1234971236178; Wed, 18 Feb 2009 07:33:56 -0800 (PST) In-Reply-To: <20090218080420.681788d2@memory.visualtech.com> References: <200902171720.n1HHKkIf071491@freefall.freebsd.org> <20090217133404.22275b25@memory.visualtech.com> <3a142e750902171414p438d184bl54a1569e27490634@mail.gmail.com> <200902171727.53156.adamk@voicenet.com> <3a142e750902180306x390fd549led076474f4fae06b@mail.gmail.com> <20090218080420.681788d2@memory.visualtech.com> Date: Wed, 18 Feb 2009 16:33:56 +0100 Message-ID: <3a142e750902180733o679b050ck8d9287f0bdd860e7@mail.gmail.com> From: "Paul B. Mahol" To: Adam K Kirchhoff Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: kern/131781: [ndis] ndis keeps dropping the link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Feb 2009 15:33:58 -0000 On 2/18/09, Adam K Kirchhoff wrote: > On Wed, 18 Feb 2009 12:06:21 +0100 > "Paul B. Mahol" wrote: > >> On 2/17/09, Adam K Kirchhoff wrote: >> > On Tuesday 17 February 2009 17:14:07 Paul B. Mahol wrote: >> >> On 2/17/09, Adam K Kirchhoff wrote: >> >> > On Tue, 17 Feb 2009 19:22:22 +0100 >> >> > >> >> > "Paul B. Mahol" wrote: >> >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=131781 >> >> >> >> >> >> This one should not happen, 108 rate should get recognized. >> >> >> I will try to reproduce it on CURRENT. >> >> >> >> >> >> To OP, could you try 7 STABLE after 31 Jan? I guess it should not >> >> >> change anything but you never know. >> >> > >> >> > Sorry, I must have copied and pasted the uname output from the wrong >> >> > machine. This is actually FreeBSD 7.1-STABLE #4: Mon Feb 16 16:37:18 >> >> > EST 2009 :-) >> >> >> >> miniport dump NDIS_STATUS_UNSUPPORTED_MEDIA for error in >> >> ndis_setstate() for setting OID_802_11_CONFIGURATION. >> > >> > Sorry if I seem slow, but are you asking me to check something there, or >> > just >> > stating what you think the problem is? :-) >> >> You can add printf() before "ndis_set_info(sc, >> OID_802_11_CONFIGURATION, &config, &len);" in ndis_setstate_80211() to >> check what value for config.nc_dsconfig is by default. > > I'll try that shortly. > >> Also try changing "sysctl debug.ndis=1" and post console debug ouput >> again. > > This was strange. If I boot up and enable debugging before I try to > run '/etc/rc.d/netif start ndis0' everything works just fine. I get an > IP address and stay connected (at least under a light load). This is > the output: > > ndis_newstate: INIT -> INIT > ndis0: NDIS ERROR: c00013a7 (unknown error) > ndis0: NDIS ERROR: c0001392 (unknown error) these two errors means: EVENT_NDIS_ADAPTER_CHECK_ERROR EVENT_NDIS_INVALID_VALUE_FROM_ADAPTER Looks like minport driver doesnt like your card. Are you absolutly sure that you are using right miniport driver? > Setting BSSID to ff:ff:ff:ff:ff:ff > Setting ESSID to "" > ndis0: no matching rate for: 108 > ndis_newstate: INIT -> RUN > ndis0: link state changed to UP > ndis_newstate: RUN -> INIT > Setting channel to 2412000kHz > ndis0: couldn't change DS config to 2412000kHz: 19 > Setting BSSID to ff:ff:ff:ff:ff:ff > Setting ESSID to "Mckella280Front" > ndis0: link state changed to DOWN > ndis0: no matching rate for: 108 > ndis_newstate: INIT -> RUN > ndis0: link state changed to UP > > If I then stop the network on that device, disable debug, and try to > start it up again, I get the same problem as before: > > ndis0: couldn't change DS config to 2412000kHz: 19 > ndis0: link state changed to DOWN > ndis0: no matching rate for: 108 > ndis0: link state changed to UP > ndis0: couldn't change DS config to 2412000kHz: 19 > ndis0: link state changed to DOWN > ndis0: no matching rate for: 108 > ndis0: link state changed to UP > ndis0: link state changed to DOWN > > If I then stop the network, enable debugging, and start up the network, > the problem persists. > You are starting ndis0 in same way in both cases? -- Paul From owner-freebsd-net@FreeBSD.ORG Wed Feb 18 15:36:03 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 B98F2106566B for ; Wed, 18 Feb 2009 15:36:03 +0000 (UTC) (envelope-from prt@prt.org) Received: from smtp6.uk.umis.net (smtp6.uk.umis.net [217.65.166.41]) by mx1.freebsd.org (Postfix) with ESMTP id 8405F8FC0A for ; Wed, 18 Feb 2009 15:36:03 +0000 (UTC) (envelope-from prt@prt.org) Received: from kate.prtsystems.ltd.uk ([217.65.165.35]) by smtp6.uk.umis.net with esmtpa (Exim 4.63 (FreeBSD)) (envelope-from ) id 1LZoSv-000K1I-Oo for freebsd-net@freebsd.org; Wed, 18 Feb 2009 15:36:01 +0000 Message-ID: <499C2ADF.3070700@prt.org> Date: Wed, 18 Feb 2009 15:35:59 +0000 From: Paul Thornton User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <49995AB5.50200@prt.org> In-Reply-To: <49995AB5.50200@prt.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ipfw problems using divert and fwd at the same time with 6.3-release X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2009 15:36:04 -0000 I have found the error of my ways... For the purposes of the archives, I'm posting what actually made this work. It is a very simple fix and I don't quite know how I missed trying this out during my frustrations. Before the "ipfw fwd..." line you need one or more "ipfw skipto..." lines to ensure that you don't accidentally match the more specific addresses on the fwd. What's interesting is that I'd had "ipfw allow..." lines before the "ipfe fwd..." line doing a similar thing to skipto, and it didn't work. So I amended the ruleset to the following (other rules stay the same): > 06000 515 153945 divert 8668 ip from any to me via em0 > 07000 48 5472 skipto 32000 ip from 10.81.0.0/16 to 217.65.161.4 dst-port 80 > 07100 0 0 skipto 32000 ip from 10.81.129.0/24 to any > 08000 94 10434 fwd 127.0.0.1,8000 tcp from 10.81.0.0/16 to any dst-port 80 > 32000 499 230890 allow ip from any to any Paul. From owner-freebsd-net@FreeBSD.ORG Wed Feb 18 16:13:29 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4B5010656DC for ; Wed, 18 Feb 2009 16:13:29 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from spamfish.visualtech.com (h-67-102-187-40.phlapafg.covad.net [67.102.187.40]) by mx1.freebsd.org (Postfix) with ESMTP id 69DBF8FC14 for ; Wed, 18 Feb 2009 16:13:28 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from mailstore.visualtech.com (unknown [67.102.187.41]) by spamfish.visualtech.com (Postfix) with ESMTPS id 8BCA81F4419; Wed, 18 Feb 2009 11:07:37 -0500 (EST) Received: from memory.visualtech.com (h-67-103-204-242.phlapafg.covad.net [67.103.204.242]) by mailstore.visualtech.com (Postfix) with ESMTP id 615A2ADC25E; Wed, 18 Feb 2009 11:22:28 -0500 (EST) Date: Wed, 18 Feb 2009 11:12:23 -0500 From: Adam K Kirchhoff To: "Paul B. Mahol" Message-ID: <20090218111223.4483b923@memory.visualtech.com> In-Reply-To: <3a142e750902180733o679b050ck8d9287f0bdd860e7@mail.gmail.com> References: <200902171720.n1HHKkIf071491@freefall.freebsd.org> <20090217133404.22275b25@memory.visualtech.com> <3a142e750902171414p438d184bl54a1569e27490634@mail.gmail.com> <200902171727.53156.adamk@voicenet.com> <3a142e750902180306x390fd549led076474f4fae06b@mail.gmail.com> <20090218080420.681788d2@memory.visualtech.com> <3a142e750902180733o679b050ck8d9287f0bdd860e7@mail.gmail.com> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; i386-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-visualtech-MailScanner: Found to be clean Cc: freebsd-net@freebsd.org Subject: Re: kern/131781: [ndis] ndis keeps dropping the link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Feb 2009 16:13:30 -0000 On Wed, 18 Feb 2009 16:33:56 +0100 "Paul B. Mahol" wrote: > On 2/18/09, Adam K Kirchhoff wrote: > > On Wed, 18 Feb 2009 12:06:21 +0100 > > "Paul B. Mahol" wrote: > > > >> On 2/17/09, Adam K Kirchhoff wrote: > >> > On Tuesday 17 February 2009 17:14:07 Paul B. Mahol wrote: > >> >> On 2/17/09, Adam K Kirchhoff wrote: > >> >> > On Tue, 17 Feb 2009 19:22:22 +0100 > >> >> > > >> >> > "Paul B. Mahol" wrote: > >> >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=131781 > >> >> >> > >> >> >> This one should not happen, 108 rate should get recognized. > >> >> >> I will try to reproduce it on CURRENT. > >> >> >> > >> >> >> To OP, could you try 7 STABLE after 31 Jan? I guess it should not > >> >> >> change anything but you never know. > >> >> > > >> >> > Sorry, I must have copied and pasted the uname output from the wrong > >> >> > machine. This is actually FreeBSD 7.1-STABLE #4: Mon Feb 16 16:37:18 > >> >> > EST 2009 :-) > >> >> > >> >> miniport dump NDIS_STATUS_UNSUPPORTED_MEDIA for error in > >> >> ndis_setstate() for setting OID_802_11_CONFIGURATION. > >> > > >> > Sorry if I seem slow, but are you asking me to check something there, or > >> > just > >> > stating what you think the problem is? :-) > >> > >> You can add printf() before "ndis_set_info(sc, > >> OID_802_11_CONFIGURATION, &config, &len);" in ndis_setstate_80211() to > >> check what value for config.nc_dsconfig is by default. > > > > I'll try that shortly. > > > >> Also try changing "sysctl debug.ndis=1" and post console debug ouput > >> again. > > > > This was strange. If I boot up and enable debugging before I try to > > run '/etc/rc.d/netif start ndis0' everything works just fine. I get an > > IP address and stay connected (at least under a light load). This is > > the output: > > > > ndis_newstate: INIT -> INIT > > ndis0: NDIS ERROR: c00013a7 (unknown error) > > ndis0: NDIS ERROR: c0001392 (unknown error) > > these two errors means: > > EVENT_NDIS_ADAPTER_CHECK_ERROR > EVENT_NDIS_INVALID_VALUE_FROM_ADAPTER > > Looks like minport driver doesnt like your card. > Are you absolutly sure that you are using right miniport driver? Frankly, no. This laptop came with a broadcom minipci card. I replaced it with the intel one that I'm now using since intel network cards have native drivers under FreeBSD :-) I've downloaded the latest drivers from the intel website ( http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&Inst=Yes&ProductID=1637&DwnldID=17228&strOSs=45&OSFullName=Windows*%20XP%20Home%20Edition&lang=eng ) and used them to generate the driver with ndisgen. Is there a recommended windows driver to use with ndis for this intel network card? > > Setting BSSID to ff:ff:ff:ff:ff:ff > > Setting ESSID to "" > > ndis0: no matching rate for: 108 > > ndis_newstate: INIT -> RUN > > ndis0: link state changed to UP > > ndis_newstate: RUN -> INIT > > Setting channel to 2412000kHz > > ndis0: couldn't change DS config to 2412000kHz: 19 > > Setting BSSID to ff:ff:ff:ff:ff:ff > > Setting ESSID to "Mckella280Front" > > ndis0: link state changed to DOWN > > ndis0: no matching rate for: 108 > > ndis_newstate: INIT -> RUN > > ndis0: link state changed to UP > > > > If I then stop the network on that device, disable debug, and try to > > start it up again, I get the same problem as before: > > > > ndis0: couldn't change DS config to 2412000kHz: 19 > > ndis0: link state changed to DOWN > > ndis0: no matching rate for: 108 > > ndis0: link state changed to UP > > ndis0: couldn't change DS config to 2412000kHz: 19 > > ndis0: link state changed to DOWN > > ndis0: no matching rate for: 108 > > ndis0: link state changed to UP > > ndis0: link state changed to DOWN > > > > If I then stop the network, enable debugging, and start up the network, > > the problem persists. > > > > You are starting ndis0 in same way in both cases? Yes. I booted up with the ifconfig_ndis0 line commented out in /etc/rc.conf. I then uncommented the line, enabled debugging, and started the network with '/etc/rc.d/netif start ndis0'. I then brought the network down, disabled debugging, and started the network with the same command. After stopping the interface, and re-enabling networking, I started the interface with the same command the third time. Adam -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-net@FreeBSD.ORG Wed Feb 18 18:27:38 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 51BD0106564A for ; Wed, 18 Feb 2009 18:27:38 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id AD5BD8FC0A for ; Wed, 18 Feb 2009 18:27:37 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by ewy14 with SMTP id 14so25778ewy.19 for ; Wed, 18 Feb 2009 10:27:36 -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 :content-transfer-encoding; bh=Gqe5v3OZnqtmjq/9tGxGicytPYbqDGgOEf4+cADW2A4=; b=kx7ao+emx+Q/PzTR8e5bn5xOKTvw7xR1G4pe8H73mnzNhm02TnC4Tdh5Pe66x0YmwP IEKJ6aD7m3vIUyFsDEflw8Yqge38USCnX7Mu5RiUClIa6AfWR5+84Uu3uS4/C5hi6hNl 5w3vPTXJqTZv8An3lBg4QoxwCwUMohZfq7vi4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=PZzksvIrIYvgqqfujTwt/CM9D/8IKDbQy4mC73LPJE6sAok9607TZ6eJ6eOmMotIOn PJjA2LlODf1I3R742EDl18HZAK2vSn0K5pgJOLM8jD/1Rt4EjDHtOYqCaYKdMwjtk+ig peJjQAQIBWP9xwwiptBMtON4LZjS6yes5I91M= MIME-Version: 1.0 Received: by 10.210.52.15 with SMTP id z15mr1421ebz.195.1234981656762; Wed, 18 Feb 2009 10:27:36 -0800 (PST) In-Reply-To: <20090218111223.4483b923@memory.visualtech.com> References: <200902171720.n1HHKkIf071491@freefall.freebsd.org> <20090217133404.22275b25@memory.visualtech.com> <3a142e750902171414p438d184bl54a1569e27490634@mail.gmail.com> <200902171727.53156.adamk@voicenet.com> <3a142e750902180306x390fd549led076474f4fae06b@mail.gmail.com> <20090218080420.681788d2@memory.visualtech.com> <3a142e750902180733o679b050ck8d9287f0bdd860e7@mail.gmail.com> <20090218111223.4483b923@memory.visualtech.com> Date: Wed, 18 Feb 2009 19:27:36 +0100 Message-ID: <3a142e750902181027q25863f39ycc342d6506949eb9@mail.gmail.com> From: "Paul B. Mahol" To: Adam K Kirchhoff Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: kern/131781: [ndis] ndis keeps dropping the link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Feb 2009 18:27:38 -0000 On 2/18/09, Adam K Kirchhoff wrote: > On Wed, 18 Feb 2009 16:33:56 +0100 > "Paul B. Mahol" wrote: > >> On 2/18/09, Adam K Kirchhoff wrote: >> > On Wed, 18 Feb 2009 12:06:21 +0100 >> > "Paul B. Mahol" wrote: >> > >> >> On 2/17/09, Adam K Kirchhoff wrote: >> >> > On Tuesday 17 February 2009 17:14:07 Paul B. Mahol wrote: >> >> >> On 2/17/09, Adam K Kirchhoff wrote: >> >> >> > On Tue, 17 Feb 2009 19:22:22 +0100 >> >> >> > >> >> >> > "Paul B. Mahol" wrote: >> >> >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=131781 >> >> >> >> >> >> >> >> This one should not happen, 108 rate should get recognized. >> >> >> >> I will try to reproduce it on CURRENT. >> >> >> >> >> >> >> >> To OP, could you try 7 STABLE after 31 Jan? I guess it should not >> >> >> >> change anything but you never know. >> >> >> > >> >> >> > Sorry, I must have copied and pasted the uname output from the >> >> >> > wrong >> >> >> > machine. This is actually FreeBSD 7.1-STABLE #4: Mon Feb 16 >> >> >> > 16:37:18 >> >> >> > EST 2009 :-) >> >> >> >> >> >> miniport dump NDIS_STATUS_UNSUPPORTED_MEDIA for error in >> >> >> ndis_setstate() for setting OID_802_11_CONFIGURATION. >> >> > >> >> > Sorry if I seem slow, but are you asking me to check something there, >> >> > or >> >> > just >> >> > stating what you think the problem is? :-) >> >> >> >> You can add printf() before "ndis_set_info(sc, >> >> OID_802_11_CONFIGURATION, &config, &len);" in ndis_setstate_80211() to >> >> check what value for config.nc_dsconfig is by default. >> > >> > I'll try that shortly. >> > >> >> Also try changing "sysctl debug.ndis=1" and post console debug ouput >> >> again. >> > >> > This was strange. If I boot up and enable debugging before I try to >> > run '/etc/rc.d/netif start ndis0' everything works just fine. I get an >> > IP address and stay connected (at least under a light load). This is >> > the output: >> > >> > ndis_newstate: INIT -> INIT >> > ndis0: NDIS ERROR: c00013a7 (unknown error) >> > ndis0: NDIS ERROR: c0001392 (unknown error) >> >> these two errors means: >> >> EVENT_NDIS_ADAPTER_CHECK_ERROR >> EVENT_NDIS_INVALID_VALUE_FROM_ADAPTER >> >> Looks like minport driver doesnt like your card. >> Are you absolutly sure that you are using right miniport driver? > > Frankly, no. This laptop came with a broadcom minipci card. I > replaced it with the intel one that I'm now using since intel network > cards have native drivers under FreeBSD :-) I've downloaded the latest > drivers from the intel website > ( > http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&Inst=Yes&ProductID=1637&DwnldID=17228&strOSs=45&OSFullName=Windows*%20XP%20Home%20Edition&lang=eng > ) > and used them to generate the driver with ndisgen. Is there a > recommended windows driver to use with ndis for this intel network card? > >> > Setting BSSID to ff:ff:ff:ff:ff:ff >> > Setting ESSID to "" >> > ndis0: no matching rate for: 108 >> > ndis_newstate: INIT -> RUN >> > ndis0: link state changed to UP >> > ndis_newstate: RUN -> INIT >> > Setting channel to 2412000kHz >> > ndis0: couldn't change DS config to 2412000kHz: 19 >> > Setting BSSID to ff:ff:ff:ff:ff:ff >> > Setting ESSID to "Mckella280Front" >> > ndis0: link state changed to DOWN >> > ndis0: no matching rate for: 108 >> > ndis_newstate: INIT -> RUN >> > ndis0: link state changed to UP >> > >> > If I then stop the network on that device, disable debug, and try to >> > start it up again, I get the same problem as before: >> > >> > ndis0: couldn't change DS config to 2412000kHz: 19 >> > ndis0: link state changed to DOWN >> > ndis0: no matching rate for: 108 >> > ndis0: link state changed to UP >> > ndis0: couldn't change DS config to 2412000kHz: 19 >> > ndis0: link state changed to DOWN >> > ndis0: no matching rate for: 108 >> > ndis0: link state changed to UP >> > ndis0: link state changed to DOWN >> > >> > If I then stop the network, enable debugging, and start up the network, >> > the problem persists. >> > >> >> You are starting ndis0 in same way in both cases? > > Yes. I booted up with the ifconfig_ndis0 line commented out > in /etc/rc.conf. I then uncommented the line, enabled debugging, and > started the network with '/etc/rc.d/netif start ndis0'. I then brought > the network down, disabled debugging, and started the network with the > same command. After stopping the interface, and re-enabling > networking, I started the interface with the same command the third > time. > > Adam > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > Did you copied whole ndis relevant debug output? scan results are missing. Are you using wpa_supplicant? -- Paul From owner-freebsd-net@FreeBSD.ORG Wed Feb 18 18:50: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 E5FBE106564A for ; Wed, 18 Feb 2009 18:50:27 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from spamfish.visualtech.com (h-67-102-187-40.phlapafg.covad.net [67.102.187.40]) by mx1.freebsd.org (Postfix) with ESMTP id 7BB268FC08 for ; Wed, 18 Feb 2009 18:50:27 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from mailstore.visualtech.com (unknown [67.102.187.41]) by spamfish.visualtech.com (Postfix) with ESMTPS id B994B1F4489; Wed, 18 Feb 2009 13:44:48 -0500 (EST) Received: from memory.visualtech.com (h-67-103-204-242.phlapafg.covad.net [67.103.204.242]) by mailstore.visualtech.com (Postfix) with ESMTP id 1E944ADC25E; Wed, 18 Feb 2009 13:59:42 -0500 (EST) Date: Wed, 18 Feb 2009 13:49:35 -0500 From: Adam K Kirchhoff To: "Paul B. Mahol" Message-ID: <20090218134935.14f0a8c2@memory.visualtech.com> In-Reply-To: <3a142e750902181027q25863f39ycc342d6506949eb9@mail.gmail.com> References: <200902171720.n1HHKkIf071491@freefall.freebsd.org> <20090217133404.22275b25@memory.visualtech.com> <3a142e750902171414p438d184bl54a1569e27490634@mail.gmail.com> <200902171727.53156.adamk@voicenet.com> <3a142e750902180306x390fd549led076474f4fae06b@mail.gmail.com> <20090218080420.681788d2@memory.visualtech.com> <3a142e750902180733o679b050ck8d9287f0bdd860e7@mail.gmail.com> <20090218111223.4483b923@memory.visualtech.com> <3a142e750902181027q25863f39ycc342d6506949eb9@mail.gmail.com> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; i386-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-visualtech-MailScanner: Found to be clean Cc: freebsd-net@freebsd.org Subject: Re: kern/131781: [ndis] ndis keeps dropping the link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Feb 2009 18:50:28 -0000 On Wed, 18 Feb 2009 19:27:36 +0100 "Paul B. Mahol" wrote: > On 2/18/09, Adam K Kirchhoff wrote: > > On Wed, 18 Feb 2009 16:33:56 +0100 > > "Paul B. Mahol" wrote: > > > >> On 2/18/09, Adam K Kirchhoff wrote: > >> > On Wed, 18 Feb 2009 12:06:21 +0100 > >> > "Paul B. Mahol" wrote: > >> > > >> >> On 2/17/09, Adam K Kirchhoff wrote: > >> >> > On Tuesday 17 February 2009 17:14:07 Paul B. Mahol wrote: > >> >> >> On 2/17/09, Adam K Kirchhoff wrote: > >> >> >> > On Tue, 17 Feb 2009 19:22:22 +0100 > >> >> >> > > >> >> >> > "Paul B. Mahol" wrote: > >> >> >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=131781 > >> >> >> >> > >> >> >> >> This one should not happen, 108 rate should get recognized. > >> >> >> >> I will try to reproduce it on CURRENT. > >> >> >> >> > >> >> >> >> To OP, could you try 7 STABLE after 31 Jan? I guess it should not > >> >> >> >> change anything but you never know. > >> >> >> > > >> >> >> > Sorry, I must have copied and pasted the uname output from the > >> >> >> > wrong > >> >> >> > machine. This is actually FreeBSD 7.1-STABLE #4: Mon Feb 16 > >> >> >> > 16:37:18 > >> >> >> > EST 2009 :-) > >> >> >> > >> >> >> miniport dump NDIS_STATUS_UNSUPPORTED_MEDIA for error in > >> >> >> ndis_setstate() for setting OID_802_11_CONFIGURATION. > >> >> > > >> >> > Sorry if I seem slow, but are you asking me to check something there, > >> >> > or > >> >> > just > >> >> > stating what you think the problem is? :-) > >> >> > >> >> You can add printf() before "ndis_set_info(sc, > >> >> OID_802_11_CONFIGURATION, &config, &len);" in ndis_setstate_80211() to > >> >> check what value for config.nc_dsconfig is by default. > >> > > >> > I'll try that shortly. > >> > > >> >> Also try changing "sysctl debug.ndis=1" and post console debug ouput > >> >> again. > >> > > >> > This was strange. If I boot up and enable debugging before I try to > >> > run '/etc/rc.d/netif start ndis0' everything works just fine. I get an > >> > IP address and stay connected (at least under a light load). This is > >> > the output: > >> > > >> > ndis_newstate: INIT -> INIT > >> > ndis0: NDIS ERROR: c00013a7 (unknown error) > >> > ndis0: NDIS ERROR: c0001392 (unknown error) > >> > >> these two errors means: > >> > >> EVENT_NDIS_ADAPTER_CHECK_ERROR > >> EVENT_NDIS_INVALID_VALUE_FROM_ADAPTER > >> > >> Looks like minport driver doesnt like your card. > >> Are you absolutly sure that you are using right miniport driver? > > > > Frankly, no. This laptop came with a broadcom minipci card. I > > replaced it with the intel one that I'm now using since intel network > > cards have native drivers under FreeBSD :-) I've downloaded the latest > > drivers from the intel website > > ( > > http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&Inst=Yes&ProductID=1637&DwnldID=17228&strOSs=45&OSFullName=Windows*%20XP%20Home%20Edition&lang=eng > > ) > > and used them to generate the driver with ndisgen. Is there a > > recommended windows driver to use with ndis for this intel network card? > > > >> > Setting BSSID to ff:ff:ff:ff:ff:ff > >> > Setting ESSID to "" > >> > ndis0: no matching rate for: 108 > >> > ndis_newstate: INIT -> RUN > >> > ndis0: link state changed to UP > >> > ndis_newstate: RUN -> INIT > >> > Setting channel to 2412000kHz > >> > ndis0: couldn't change DS config to 2412000kHz: 19 > >> > Setting BSSID to ff:ff:ff:ff:ff:ff > >> > Setting ESSID to "Mckella280Front" > >> > ndis0: link state changed to DOWN > >> > ndis0: no matching rate for: 108 > >> > ndis_newstate: INIT -> RUN > >> > ndis0: link state changed to UP > >> > > >> > If I then stop the network on that device, disable debug, and try to > >> > start it up again, I get the same problem as before: > >> > > >> > ndis0: couldn't change DS config to 2412000kHz: 19 > >> > ndis0: link state changed to DOWN > >> > ndis0: no matching rate for: 108 > >> > ndis0: link state changed to UP > >> > ndis0: couldn't change DS config to 2412000kHz: 19 > >> > ndis0: link state changed to DOWN > >> > ndis0: no matching rate for: 108 > >> > ndis0: link state changed to UP > >> > ndis0: link state changed to DOWN > >> > > >> > If I then stop the network, enable debugging, and start up the network, > >> > the problem persists. > >> > > >> > >> You are starting ndis0 in same way in both cases? > > > > Yes. I booted up with the ifconfig_ndis0 line commented out > > in /etc/rc.conf. I then uncommented the line, enabled debugging, and > > started the network with '/etc/rc.d/netif start ndis0'. I then brought > > the network down, disabled debugging, and started the network with the > > same command. After stopping the interface, and re-enabling > > networking, I started the interface with the same command the third > > time. > > > > Adam > > > > -- > > This message has been scanned for viruses and > > dangerous content by MailScanner, and is > > believed to be clean. > > > > > > Did you copied whole ndis relevant debug output? > scan results are missing. > Are you using wpa_supplicant? Yes, I am using wpa_supplicant... I have ifconfig_ndis0="DHCP WPA" in my /etc/rc.conf file and the wpa_supplicant.conf file is presumably configured correctly as I am connecting. I'm pretty sure I copied every line that contained ndis, but I'll double check shortly. Adam -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-net@FreeBSD.ORG Wed Feb 18 19:10: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 2DEFA106566B for ; Wed, 18 Feb 2009 19:10:45 +0000 (UTC) (envelope-from nex84@vtr.net) Received: from vtr.net (mail-vtr.cgp.vtr.net [200.83.2.210]) by mx1.freebsd.org (Postfix) with ESMTP id 9C5178FC0A for ; Wed, 18 Feb 2009 19:10:44 +0000 (UTC) (envelope-from nex84@vtr.net) Received: from [192.168.5.3] (HELO av2.vtr.cl) by fe3.vtr.net (CommuniGate Pro SMTP 5.1.16) with ESMTP id 465714436 for freebsd-net@freebsd.org; Wed, 18 Feb 2009 15:10:41 -0300 X-ASG-Debug-ID: 1234980641-578601d70004-QdxwpM X-Barracuda-URL: http://192.168.5.3:8000/cgi-bin/mark.cgi Received: from vtr.net (localhost [127.0.0.1]) by av2.vtr.cl (Spam Firewall) with ESMTP id 2121AD21BC1 for ; Wed, 18 Feb 2009 15:10:41 -0300 (CLST) Received: from vtr.net (mxfe1.cgp.vtr.net [192.168.6.2]) by av2.vtr.cl with ESMTP id AVcGPqDurY0a6cpA for ; Wed, 18 Feb 2009 15:10:41 -0300 (CLST) Received: by fe1.vtr.net (CommuniGate Pro PIPE 5.1.16) with PIPE id 463092943; Wed, 18 Feb 2009 15:09:41 -0300 X-NHContentFiltered: yes Received: from [200.104.153.96] (account nex84@vtr.net HELO [192.168.1.109]) by fe1.vtr.net (CommuniGate Pro SMTP 5.1.16) with ESMTPA id 463092919 for freebsd-net@freebsd.org; Wed, 18 Feb 2009 15:09:40 -0300 Message-ID: <499C4ECC.8050109@vtr.net> Date: Wed, 18 Feb 2009 15:09:16 -0300 From: Felipe Jara Saba User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: freebsd-net@freebsd.org X-ASG-Orig-Subj: differentiated statistics for ipv4/ipv6 traffica? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Barracuda-Connect: mxfe1.cgp.vtr.net[192.168.6.2] X-Barracuda-Start-Time: 1234980641 X-Barracuda-Virus-Scanned: by Barracuda2 at vtr.cl X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=6.7 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.18191 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- Subject: differentiated statistics for ipv4/ipv6 traffica? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Feb 2009 19:10:45 -0000 Hello: Has anyone tried to get differentiated statistics for ipv4/ipv6 traffic in a FreeBSD server?. I was hoping that I could retrieve that information through SNMP (I`m running net-snmp on a freebsd 7.1 box), but even though there is a IPv6-MIB.txt in the /usr/local/share/snmp/mibs dir, it seems it only shows the ipv4/ipv6 traffic combined into the same counters. Greetings -- Felipe Jara S. Estudiante Ingenieria Civil Telematica UTFSM http://www.telematica.utfsm.cl From owner-freebsd-net@FreeBSD.ORG Wed Feb 18 19:34: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 391351065694 for ; Wed, 18 Feb 2009 19:34:05 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from spamfish.visualtech.com (h-67-102-187-40.phlapafg.covad.net [67.102.187.40]) by mx1.freebsd.org (Postfix) with ESMTP id 65DF68FC21 for ; Wed, 18 Feb 2009 19:34:04 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from mailstore.visualtech.com (unknown [67.102.187.41]) by spamfish.visualtech.com (Postfix) with ESMTPS id E72561F45CF; Wed, 18 Feb 2009 14:22:13 -0500 (EST) Received: from memory.visualtech.com (h-67-103-204-242.phlapafg.covad.net [67.103.204.242]) by mailstore.visualtech.com (Postfix) with ESMTP id ECB1DADC25F; Wed, 18 Feb 2009 14:37:06 -0500 (EST) Date: Wed, 18 Feb 2009 14:26:59 -0500 From: Adam K Kirchhoff To: "Paul B. Mahol" Message-ID: <20090218142659.135a73bc@memory.visualtech.com> In-Reply-To: <20090218134935.14f0a8c2@memory.visualtech.com> References: <200902171720.n1HHKkIf071491@freefall.freebsd.org> <20090217133404.22275b25@memory.visualtech.com> <3a142e750902171414p438d184bl54a1569e27490634@mail.gmail.com> <200902171727.53156.adamk@voicenet.com> <3a142e750902180306x390fd549led076474f4fae06b@mail.gmail.com> <20090218080420.681788d2@memory.visualtech.com> <3a142e750902180733o679b050ck8d9287f0bdd860e7@mail.gmail.com> <20090218111223.4483b923@memory.visualtech.com> <3a142e750902181027q25863f39ycc342d6506949eb9@mail.gmail.com> <20090218134935.14f0a8c2@memory.visualtech.com> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; i386-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-visualtech-MailScanner: Found to be clean Cc: freebsd-net@freebsd.org Subject: Re: kern/131781: [ndis] ndis keeps dropping the link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Feb 2009 19:34:05 -0000 On Wed, 18 Feb 2009 13:49:35 -0500 Adam K Kirchhoff wrote: > On Wed, 18 Feb 2009 19:27:36 +0100 > "Paul B. Mahol" wrote: > > > On 2/18/09, Adam K Kirchhoff wrote: > > > On Wed, 18 Feb 2009 16:33:56 +0100 > > > "Paul B. Mahol" wrote: > > > > > >> On 2/18/09, Adam K Kirchhoff wrote: > > >> > On Wed, 18 Feb 2009 12:06:21 +0100 > > >> > "Paul B. Mahol" wrote: > > >> > > > >> >> On 2/17/09, Adam K Kirchhoff wrote: > > >> >> > On Tuesday 17 February 2009 17:14:07 Paul B. Mahol wrote: > > >> >> >> On 2/17/09, Adam K Kirchhoff wrote: > > >> >> >> > On Tue, 17 Feb 2009 19:22:22 +0100 > > >> >> >> > > > >> >> >> > "Paul B. Mahol" wrote: > > >> >> >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=131781 > > >> >> >> >> > > >> >> >> >> This one should not happen, 108 rate should get recognized. > > >> >> >> >> I will try to reproduce it on CURRENT. > > >> >> >> >> > > >> >> >> >> To OP, could you try 7 STABLE after 31 Jan? I guess it should not > > >> >> >> >> change anything but you never know. > > >> >> >> > > > >> >> >> > Sorry, I must have copied and pasted the uname output from the > > >> >> >> > wrong > > >> >> >> > machine. This is actually FreeBSD 7.1-STABLE #4: Mon Feb 16 > > >> >> >> > 16:37:18 > > >> >> >> > EST 2009 :-) > > >> >> >> > > >> >> >> miniport dump NDIS_STATUS_UNSUPPORTED_MEDIA for error in > > >> >> >> ndis_setstate() for setting OID_802_11_CONFIGURATION. > > >> >> > > > >> >> > Sorry if I seem slow, but are you asking me to check something there, > > >> >> > or > > >> >> > just > > >> >> > stating what you think the problem is? :-) > > >> >> > > >> >> You can add printf() before "ndis_set_info(sc, > > >> >> OID_802_11_CONFIGURATION, &config, &len);" in ndis_setstate_80211() to > > >> >> check what value for config.nc_dsconfig is by default. > > >> > > > >> > I'll try that shortly. > > >> > > > >> >> Also try changing "sysctl debug.ndis=1" and post console debug ouput > > >> >> again. > > >> > > > >> > This was strange. If I boot up and enable debugging before I try to > > >> > run '/etc/rc.d/netif start ndis0' everything works just fine. I get an > > >> > IP address and stay connected (at least under a light load). This is > > >> > the output: > > >> > > > >> > ndis_newstate: INIT -> INIT > > >> > ndis0: NDIS ERROR: c00013a7 (unknown error) > > >> > ndis0: NDIS ERROR: c0001392 (unknown error) > > >> > > >> these two errors means: > > >> > > >> EVENT_NDIS_ADAPTER_CHECK_ERROR > > >> EVENT_NDIS_INVALID_VALUE_FROM_ADAPTER > > >> > > >> Looks like minport driver doesnt like your card. > > >> Are you absolutly sure that you are using right miniport driver? > > > > > > Frankly, no. This laptop came with a broadcom minipci card. I > > > replaced it with the intel one that I'm now using since intel network > > > cards have native drivers under FreeBSD :-) I've downloaded the latest > > > drivers from the intel website > > > ( > > > http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&Inst=Yes&ProductID=1637&DwnldID=17228&strOSs=45&OSFullName=Windows*%20XP%20Home%20Edition&lang=eng > > > ) > > > and used them to generate the driver with ndisgen. Is there a > > > recommended windows driver to use with ndis for this intel network card? > > > > > >> > Setting BSSID to ff:ff:ff:ff:ff:ff > > >> > Setting ESSID to "" > > >> > ndis0: no matching rate for: 108 > > >> > ndis_newstate: INIT -> RUN > > >> > ndis0: link state changed to UP > > >> > ndis_newstate: RUN -> INIT > > >> > Setting channel to 2412000kHz > > >> > ndis0: couldn't change DS config to 2412000kHz: 19 > > >> > Setting BSSID to ff:ff:ff:ff:ff:ff > > >> > Setting ESSID to "Mckella280Front" > > >> > ndis0: link state changed to DOWN > > >> > ndis0: no matching rate for: 108 > > >> > ndis_newstate: INIT -> RUN > > >> > ndis0: link state changed to UP > > >> > > > >> > If I then stop the network on that device, disable debug, and try to > > >> > start it up again, I get the same problem as before: > > >> > > > >> > ndis0: couldn't change DS config to 2412000kHz: 19 > > >> > ndis0: link state changed to DOWN > > >> > ndis0: no matching rate for: 108 > > >> > ndis0: link state changed to UP > > >> > ndis0: couldn't change DS config to 2412000kHz: 19 > > >> > ndis0: link state changed to DOWN > > >> > ndis0: no matching rate for: 108 > > >> > ndis0: link state changed to UP > > >> > ndis0: link state changed to DOWN > > >> > > > >> > If I then stop the network, enable debugging, and start up the network, > > >> > the problem persists. > > >> > > > >> > > >> You are starting ndis0 in same way in both cases? > > > > > > Yes. I booted up with the ifconfig_ndis0 line commented out > > > in /etc/rc.conf. I then uncommented the line, enabled debugging, and > > > started the network with '/etc/rc.d/netif start ndis0'. I then brought > > > the network down, disabled debugging, and started the network with the > > > same command. After stopping the interface, and re-enabling > > > networking, I started the interface with the same command the third > > > time. > > > > > > Adam > > > > > > -- > > > This message has been scanned for viruses and > > > dangerous content by MailScanner, and is > > > believed to be clean. > > > > > > > > > > Did you copied whole ndis relevant debug output? > > scan results are missing. > > Are you using wpa_supplicant? > > Yes, I am using wpa_supplicant... I have ifconfig_ndis0="DHCP WPA" in > my /etc/rc.conf file and the wpa_supplicant.conf file is presumably > configured correctly as I am connecting. > > I'm pretty sure I copied every line that contained ndis, but I'll > double check shortly. Alright, here's the full 'dmesg' output from when I loaded the kernel module: ndis0: mem 0xdfcff000-0xdfcfffff irq 17 at device 3.0 on pci3 ndis0: [ITHREAD] ndis0: NDIS API version: 5.0 ndis0: WARNING: using obsoleted if_watchdog interface ndis0: Ethernet address: 00:13:ce:a8:10:ea fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 ndis_newstate: INIT -> INIT ndis0: couldn't change Testing config.nc_dsconfig: 0 Setting BSSID to ff:ff:ff:ff:ff:ff Setting ESSID to "" ndis0: no matching rate for: 108 ndis_newstate: INIT -> RUN ndis0: link state changed to UP ndis_newstate: RUN -> INIT ndis0: couldn't change Testing config.nc_dsconfig: 0 Setting channel to 2412000kHz ndis0: couldn't change DS config to 2412000kHz: 19 Setting BSSID to ff:ff:ff:ff:ff:ff Setting ESSID to "Mckella280Front" ndis0: link state changed to DOWN ndis0: no matching rate for: 108 ndis_newstate: INIT -> RUN ndis0: link state changed to UP ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS ERROR: c00013a7 (unknown error) ndis_newstate: RUN -> SCAN ndis0: link state changed to DOWN ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS ERROR: c00013a7 (unknown error) As soon as those NDIS ERRORs start, the connection seems to die. I think I edited if_ndis.c in the correct place and had it output what I think you wanted to see... Here's the diff, so please let me know if I grabbed the wrong information, or did it at the wrong place. If I did it correctly, it looks like config.nc_dsconfig is 0. --- if_ndis.c 2009-01-31 00:22:11.000000000 -0500 +++ if_ndis.c.orig 2009-02-18 14:03:30.000000000 -0500 @@ -2459,6 +2459,11 @@ bzero((char *)&config, len); config.nc_length = len; config.nc_fhconfig.ncf_length = sizeof(ndis_80211_config_fh); + + device_printf(sc->ndis_dev, "couldn't change " + "Testing config.nc_dsconfig: %u \n", + config.nc_dsconfig); + rval = ndis_get_info(sc, OID_802_11_CONFIGURATION, &config, &len); -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-net@FreeBSD.ORG Wed Feb 18 22:25:52 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D82E81065677 for ; Wed, 18 Feb 2009 22:25:52 +0000 (UTC) (envelope-from info@ekipate.es) Received: from vds-790543.amen-pro.com (vds-790543.amen-pro.com [62.193.199.169]) by mx1.freebsd.org (Postfix) with ESMTP id 284E08FC1E for ; Wed, 18 Feb 2009 22:25:51 +0000 (UTC) (envelope-from info@ekipate.es) Received: (qmail 38699 invoked from network); 17 Feb 2009 19:32:35 +0100 Received: from localhost (HELO www.ekipate.es) (127.0.0.1) by localhost with SMTP; 17 Feb 2009 19:32:35 +0100 Recieved: Date: Tue, 17 Feb 2009 19:32:35 +0100 To: freebsd-net@freebsd.org From: admin Message-ID: <909542d4da6f965360c1cf612684174c@www.ekipate.es> X-Priority: 3 X-Mailer: PHPMailer [version 1.73] X-Mailer: phplist v2.10.9 X-MessageID: 19 X-ListMember: freebsd-net@freebsd.org Precedence: bulk Errors-To: info@ekipate.es MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="UTF-8" Subject: MEETING X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2009 22:25:54 -0000 Estas buscando pareja. -- To unsubscribe from this list visit http://www.ekipate.es/lists/lt.php?id=YR5QBw0OUwAYCFpMAQ4FVAA%3D To update your preferences visit http://www.ekipate.es/lists/lt.php?id=YR5QBw0OUwEYCFpMAQ4FVAA%3D -- Powered by PHPlist, www.phplist.com -- From owner-freebsd-net@FreeBSD.ORG Wed Feb 18 22:28:27 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 21646106571B; Wed, 18 Feb 2009 22:28:27 +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 DD7108FC16; Wed, 18 Feb 2009 22:28:26 +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 n1IMSQVQ038962; Wed, 18 Feb 2009 22:28:26 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1IMSQce038958; Wed, 18 Feb 2009 22:28:26 GMT (envelope-from gavin) Date: Wed, 18 Feb 2009 22:28:26 GMT Message-Id: <200902182228.n1IMSQce038958@freefall.freebsd.org> To: gavin@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-net@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: kern/131776: [wi] driver fails to init X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Feb 2009 22:28:28 -0000 Old Synopsis: wi driver fails to init New Synopsis: [wi] driver fails to init Responsible-Changed-From-To: freebsd-i386->freebsd-net Responsible-Changed-By: gavin Responsible-Changed-When: Wed Feb 18 22:25:55 UTC 2009 Responsible-Changed-Why: Over to maintainer(s) http://www.freebsd.org/cgi/query-pr.cgi?pr=131776 From owner-freebsd-net@FreeBSD.ORG Thu Feb 19 00:10:10 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 110571065679 for ; Thu, 19 Feb 2009 00:10:10 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id 6683A8FC29 for ; Thu, 19 Feb 2009 00:10:09 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by ewy14 with SMTP id 14so153800ewy.19 for ; Wed, 18 Feb 2009 16:10:08 -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 :content-transfer-encoding; bh=uyqKSVJq+5u5pad6AoDHw87mo5uftGkmRn3YrcFi2Pk=; b=Fki8FLelhs8vDuH/MdYCXVtu2nFDI0rI6Xlb4ncuAnGj/2G0sNLkZh7lRvEBBYLjCW gXsBBJOlzto8BIVF6W6cor+6m5+XE2HCOso8hq2qpsfgpkoXeEcGVy79O0AwIY72gUcm Y6Qck0QHKipi9DVdv/yzFdETwSMpzpHk219E0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=BOyNri2Q/f/IHilzKoQfk7x2+iUg2Rxb65ZWxExMFb1wqX94hkbNMFGD9vGcNEf8hP tRgxUs0EhCzAP8KdIt8xHyu7GprxBFo7GYR/RNMxIwn657XmWgXShV3/GBQ0mNlJ2gq/ XiOS2wspZUXgVRJQSRXsFueqg5jNr8aaGMA9E= MIME-Version: 1.0 Received: by 10.210.59.3 with SMTP id h3mr4986215eba.106.1235002208446; Wed, 18 Feb 2009 16:10:08 -0800 (PST) In-Reply-To: <20090218142659.135a73bc@memory.visualtech.com> References: <200902171720.n1HHKkIf071491@freefall.freebsd.org> <3a142e750902171414p438d184bl54a1569e27490634@mail.gmail.com> <200902171727.53156.adamk@voicenet.com> <3a142e750902180306x390fd549led076474f4fae06b@mail.gmail.com> <20090218080420.681788d2@memory.visualtech.com> <3a142e750902180733o679b050ck8d9287f0bdd860e7@mail.gmail.com> <20090218111223.4483b923@memory.visualtech.com> <3a142e750902181027q25863f39ycc342d6506949eb9@mail.gmail.com> <20090218134935.14f0a8c2@memory.visualtech.com> <20090218142659.135a73bc@memory.visualtech.com> Date: Thu, 19 Feb 2009 01:10:08 +0100 Message-ID: <3a142e750902181610h65f23d13vfeb20cc19ea0944a@mail.gmail.com> From: "Paul B. Mahol" To: Adam K Kirchhoff Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: kern/131781: [ndis] ndis keeps dropping the link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2009 00:10:10 -0000 On 2/18/09, Adam K Kirchhoff wrote: > --- if_ndis.c 2009-01-31 00:22:11.000000000 -0500 > +++ if_ndis.c.orig 2009-02-18 14:03:30.000000000 -0500 > @@ -2459,6 +2459,11 @@ > bzero((char *)&config, len); > config.nc_length = len; > config.nc_fhconfig.ncf_length = sizeof(ndis_80211_config_fh); > + > + device_printf(sc->ndis_dev, "couldn't change " > + "Testing config.nc_dsconfig: %u \n", > + config.nc_dsconfig); > + > rval = ndis_get_info(sc, OID_802_11_CONFIGURATION, &config, &len); printf should be bellow ndis_get_info() and above ndis_set_info(). Does same problem happens when not using WPA eg. wpa_supplicant? -- Paul From owner-freebsd-net@FreeBSD.ORG Thu Feb 19 00:48: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 21981106567C for ; Thu, 19 Feb 2009 00:48:37 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from spamfish.visualtech.com (h-67-102-187-40.phlapafg.covad.net [67.102.187.40]) by mx1.freebsd.org (Postfix) with ESMTP id C9A928FC14 for ; Thu, 19 Feb 2009 00:48:36 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from mailstore.visualtech.com (unknown [67.102.187.41]) by spamfish.visualtech.com (Postfix) with ESMTPS id 6ADE01F458D; Wed, 18 Feb 2009 19:43:24 -0500 (EST) Received: from sorrow.ashke.com (c-68-45-151-98.hsd1.nj.comcast.net [68.45.151.98]) by mailstore.visualtech.com (Postfix) with ESMTP id 66454ADC25B; Wed, 18 Feb 2009 19:58:21 -0500 (EST) Date: Wed, 18 Feb 2009 19:48:10 -0500 From: Adam K Kirchhoff To: "Paul B. Mahol" Message-ID: <20090218194810.075e0c7c@sorrow.ashke.com> In-Reply-To: <3a142e750902181610h65f23d13vfeb20cc19ea0944a@mail.gmail.com> References: <200902171720.n1HHKkIf071491@freefall.freebsd.org> <3a142e750902171414p438d184bl54a1569e27490634@mail.gmail.com> <200902171727.53156.adamk@voicenet.com> <3a142e750902180306x390fd549led076474f4fae06b@mail.gmail.com> <20090218080420.681788d2@memory.visualtech.com> <3a142e750902180733o679b050ck8d9287f0bdd860e7@mail.gmail.com> <20090218111223.4483b923@memory.visualtech.com> <3a142e750902181027q25863f39ycc342d6506949eb9@mail.gmail.com> <20090218134935.14f0a8c2@memory.visualtech.com> <20090218142659.135a73bc@memory.visualtech.com> <3a142e750902181610h65f23d13vfeb20cc19ea0944a@mail.gmail.com> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; i386-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-visualtech-MailScanner: Found to be clean Cc: freebsd-net@freebsd.org Subject: Re: kern/131781: [ndis] ndis keeps dropping the link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2009 00:48:37 -0000 On Thu, 19 Feb 2009 01:10:08 +0100 "Paul B. Mahol" wrote: > On 2/18/09, Adam K Kirchhoff wrote: > > --- if_ndis.c 2009-01-31 00:22:11.000000000 -0500 > > +++ if_ndis.c.orig 2009-02-18 14:03:30.000000000 -0500 > > @@ -2459,6 +2459,11 @@ > > bzero((char *)&config, len); > > config.nc_length = len; > > config.nc_fhconfig.ncf_length = sizeof(ndis_80211_config_fh); > > + > > + device_printf(sc->ndis_dev, "couldn't change " > > + "Testing config.nc_dsconfig: %u \n", > > + config.nc_dsconfig); > > + > > rval = ndis_get_info(sc, OID_802_11_CONFIGURATION, &config, &len); > > printf should be bellow ndis_get_info() and above ndis_set_info(). Alright, I've moved the printf down a few lines and recompiled. > Does same problem happens when not using WPA eg. wpa_supplicant? It's actually been running just fine since I got home. I'm still using wpa_supplicant, but with WEP instead of WPA. This has been about four hours. Not much network traffic, but certainly more than what causes the problem at work. I'm going to let it continue to run through the night. I have a cron job setup to transfer several 800 meg files to this laptop via scp, so it'll be interesting to see if that works over this driver. Tomorrow morning, when I get into work, I'll grab the debug output again, this time with the printf (hopefully) in the correct place. Adam -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-net@FreeBSD.ORG Thu Feb 19 05:30: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 A52FD106566B for ; Thu, 19 Feb 2009 05:30:39 +0000 (UTC) (envelope-from info@ekipate.es) Received: from vds-790543.amen-pro.com (vds-790543.amen-pro.com [62.193.199.169]) by mx1.freebsd.org (Postfix) with ESMTP id 1F7BE8FC1C for ; Thu, 19 Feb 2009 05:30:38 +0000 (UTC) (envelope-from info@ekipate.es) Received: (qmail 30338 invoked from network); 18 Feb 2009 09:59:08 +0100 Received: from localhost (HELO www.ekipate.es) (127.0.0.1) by localhost with SMTP; 18 Feb 2009 09:59:08 +0100 Recieved: Date: Wed, 18 Feb 2009 09:59:08 +0100 To: freebsd-net@freebsd.org From: admin Message-ID: <497f630791c64ec0904ce1d9492c2543@www.ekipate.es> X-Priority: 3 X-Mailer: PHPMailer [version 1.73] X-Mailer: phplist v2.10.9 X-MessageID: 23 X-ListMember: freebsd-net@freebsd.org Precedence: bulk Errors-To: info@ekipate.es MIME-Version: 1.0 Content-Type: text/plain; charset = "UTF-8" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Publicidad X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2009 05:30:39 -0000 Clic aqui si no ves la imagen -- To unsubscribe from this list visit http://www.ekipate.es/lists/lt.php?id=YR5SBAwKVAIYC1BMAQ4FVAA%3D To update your preferences visit http://www.ekipate.es/lists/lt.php?id=YR5SBAwKVAMYC1BMAQ4FVAA%3D -- Powered by PHPlist, www.phplist.com -- From owner-freebsd-net@FreeBSD.ORG Thu Feb 19 10:51:03 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 7588F10656CA for ; Thu, 19 Feb 2009 10:51:03 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from spamfish.visualtech.com (h-67-102-187-40.phlapafg.covad.net [67.102.187.40]) by mx1.freebsd.org (Postfix) with ESMTP id 203218FC1C for ; Thu, 19 Feb 2009 10:51:02 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from mailstore.visualtech.com (unknown [67.102.187.41]) by spamfish.visualtech.com (Postfix) with ESMTPS id 339851F450A; Thu, 19 Feb 2009 05:45:44 -0500 (EST) Received: from memory.visualtech.com (h-67-103-204-242.phlapafg.covad.net [67.103.204.242]) by mailstore.visualtech.com (Postfix) with ESMTP id 86E26ADC25E; Thu, 19 Feb 2009 06:00:46 -0500 (EST) Date: Thu, 19 Feb 2009 05:50:35 -0500 From: Adam K Kirchhoff To: "Paul B. Mahol" Message-ID: <20090219055035.1ff55f19@memory.visualtech.com> In-Reply-To: <20090218194810.075e0c7c@sorrow.ashke.com> References: <200902171720.n1HHKkIf071491@freefall.freebsd.org> <3a142e750902171414p438d184bl54a1569e27490634@mail.gmail.com> <200902171727.53156.adamk@voicenet.com> <3a142e750902180306x390fd549led076474f4fae06b@mail.gmail.com> <20090218080420.681788d2@memory.visualtech.com> <3a142e750902180733o679b050ck8d9287f0bdd860e7@mail.gmail.com> <20090218111223.4483b923@memory.visualtech.com> <3a142e750902181027q25863f39ycc342d6506949eb9@mail.gmail.com> <20090218134935.14f0a8c2@memory.visualtech.com> <20090218142659.135a73bc@memory.visualtech.com> <3a142e750902181610h65f23d13vfeb20cc19ea0944a@mail.gmail.com> <20090218194810.075e0c7c@sorrow.ashke.com> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; i386-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-visualtech-MailScanner: Found to be clean Cc: freebsd-net@freebsd.org Subject: Re: kern/131781: [ndis] ndis keeps dropping the link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2009 10:51:04 -0000 On Wed, 18 Feb 2009 19:48:10 -0500 Adam K Kirchhoff wrote: > On Thu, 19 Feb 2009 01:10:08 +0100 > "Paul B. Mahol" wrote: > > > On 2/18/09, Adam K Kirchhoff wrote: > > > --- if_ndis.c 2009-01-31 00:22:11.000000000 -0500 > > > +++ if_ndis.c.orig 2009-02-18 14:03:30.000000000 -0500 > > > @@ -2459,6 +2459,11 @@ > > > bzero((char *)&config, len); > > > config.nc_length = len; > > > config.nc_fhconfig.ncf_length = sizeof(ndis_80211_config_fh); > > > + > > > + device_printf(sc->ndis_dev, "couldn't change " > > > + "Testing config.nc_dsconfig: %u \n", > > > + config.nc_dsconfig); > > > + > > > rval = ndis_get_info(sc, OID_802_11_CONFIGURATION, &config, &len); > > > > printf should be bellow ndis_get_info() and above ndis_set_info(). > > Alright, I've moved the printf down a few lines and recompiled. > > > Does same problem happens when not using WPA eg. wpa_supplicant? > > It's actually been running just fine since I got home. I'm still using > wpa_supplicant, but with WEP instead of WPA. This has been about four > hours. Not much network traffic, but certainly more than what causes > the problem at work. > > I'm going to let it continue to run through the night. I have a cron > job setup to transfer several 800 meg files to this laptop via scp, so > it'll be interesting to see if that works over this driver. > > Tomorrow morning, when I get into work, I'll grab the debug output > again, this time with the printf (hopefully) in the correct place. Looks like config.nc_dsconfig is 2462000 The wireless connection stayed up all night, even while transferring over 2 gigs of data via scp. The problem appears to be specific to this AP using WPA. I can try WPA on my home network in about 10 hours to see if the same happens there. Adam -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-net@FreeBSD.ORG Thu Feb 19 10:57: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 94FDE1065670 for ; Thu, 19 Feb 2009 10:57:46 +0000 (UTC) (envelope-from tamaru@myn.rcast.u-tokyo.ac.jp) Received: from mail4.ecc.u-tokyo.ac.jp (mail3.ecc.u-tokyo.ac.jp [133.11.205.99]) by mx1.freebsd.org (Postfix) with ESMTP id 3E1F08FC20 for ; Thu, 19 Feb 2009 10:57:46 +0000 (UTC) (envelope-from tamaru@myn.rcast.u-tokyo.ac.jp) Received: from mail0.ecc.u-tokyo.ac.jp (mail0.ecc.u-tokyo.ac.jp [133.11.45.132]) by mail4.ecc.u-tokyo.ac.jp (Postfix) with ESMTP id D37A05B12B0 for ; Thu, 19 Feb 2009 19:24:22 +0900 (JST) Received: from mhs002.ecc.u-tokyo.ac.jp (mhs002.ecc.u-tokyo.ac.jp [133.11.70.162]) by mail0.ecc.u-tokyo.ac.jp (Postfix) with ESMTP id 1A9B71BE8015 for ; Thu, 19 Feb 2009 19:24:21 +0900 (JST) Received: from amulet.amuletic.net (124.155.55.252 [124.155.55.252]) by mhs002.ecc.u-tokyo.ac.jp (SpamBlock.pstn.b 3.4.102) with ESMTP id for ; Thu, 19 Feb 2009 19:24:07 +0900 Date: Thu, 19 Feb 2009 19:24:07 +0900 Message-ID: From: Hiroharu Tamaru To: freebsd-net@freebsd.org User-Agent: User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-IP: 124.155.55.252 X-FROM-DOMAIN: myn.rcast.u-tokyo.ac.jp X-FROM-EMAIL: tamaru@myn.rcast.u-tokyo.ac.jp Subject: Can ASPM be disabled on 82573 to allow Jumbo Frames with em(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: Thu, 19 Feb 2009 10:57:46 -0000 Hi I am not sure if I am understanding things right, but is it possible to forcibly disable ASPM in em(4) for 82573 devices? What I wanted to do is to use Jumbo Frames for these NICs and I saw in sys/dev/e1000/if_em.c that says: | static int | em_ioctl(struct ifnet *ifp, u_long command, caddr_t data) | { (snip) | case SIOCSIFMTU: (snip) | case e1000_82573: | /* | * 82573 only supports jumbo frames | * if ASPM is disabled. | */ | e1000_read_nvm(&adapter->hw, | NVM_INIT_3GIO_3, 1, &eeprom_data); | if (eeprom_data & NVM_WORD1A_ASPM_MASK) { | max_frame_size = ETHER_MAX_LEN; | break; | } | /* Allow Jumbo frames - fall thru */ | case e1000_82571: I also found that in Linux, they seem to disable ASPM for certain cases: http://kerneltrap.org/mailarchive/linux-netdev/2007/10/31/374573 So I started to wonder if there is a knob already in FreeBSD to disable ASPM for 82573 and (as a side effect?) allows one to use Jumbo Frames with this device, or I such can be introduced easily. It would be nice to be able to enable Jumbo Frames if the power consumption is not of a problem.. Thanks. Hiroharu From owner-freebsd-net@FreeBSD.ORG Thu Feb 19 21:19: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 E6C6E106566C for ; Thu, 19 Feb 2009 21:19:56 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from spamfish.visualtech.com (h-67-102-187-40.phlapafg.covad.net [67.102.187.40]) by mx1.freebsd.org (Postfix) with ESMTP id 9788F8FC1E for ; Thu, 19 Feb 2009 21:19:56 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from mailstore.visualtech.com (unknown [67.102.187.41]) by spamfish.visualtech.com (Postfix) with ESMTPS id 565ED1F44E6; Thu, 19 Feb 2009 16:13:48 -0500 (EST) Received: from thorn.ashke.com (c-68-45-151-98.hsd1.nj.comcast.net [68.45.151.98]) by mailstore.visualtech.com (Postfix) with ESMTP id 16E21ADC25E; Thu, 19 Feb 2009 16:28:57 -0500 (EST) Date: Thu, 19 Feb 2009 16:18:07 -0500 From: Adam K Kirchhoff To: "Paul B. Mahol" Message-ID: <20090219161807.63efaaa5@thorn.ashke.com> In-Reply-To: <20090219055035.1ff55f19@memory.visualtech.com> References: <200902171720.n1HHKkIf071491@freefall.freebsd.org> <3a142e750902171414p438d184bl54a1569e27490634@mail.gmail.com> <200902171727.53156.adamk@voicenet.com> <3a142e750902180306x390fd549led076474f4fae06b@mail.gmail.com> <20090218080420.681788d2@memory.visualtech.com> <3a142e750902180733o679b050ck8d9287f0bdd860e7@mail.gmail.com> <20090218111223.4483b923@memory.visualtech.com> <3a142e750902181027q25863f39ycc342d6506949eb9@mail.gmail.com> <20090218134935.14f0a8c2@memory.visualtech.com> <20090218142659.135a73bc@memory.visualtech.com> <3a142e750902181610h65f23d13vfeb20cc19ea0944a@mail.gmail.com> <20090218194810.075e0c7c@sorrow.ashke.com> <20090219055035.1ff55f19@memory.visualtech.com> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.14.4; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-visualtech-MailScanner: Found to be clean Cc: freebsd-net@freebsd.org Subject: Re: kern/131781: [ndis] ndis keeps dropping the link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2009 21:19:57 -0000 On Thu, 19 Feb 2009 05:50:35 -0500 Adam K Kirchhoff wrote: > On Wed, 18 Feb 2009 19:48:10 -0500 > Adam K Kirchhoff wrote: > > > On Thu, 19 Feb 2009 01:10:08 +0100 > > "Paul B. Mahol" wrote: > > > > > On 2/18/09, Adam K Kirchhoff wrote: > > > > --- if_ndis.c 2009-01-31 00:22:11.000000000 -0500 > > > > +++ if_ndis.c.orig 2009-02-18 14:03:30.000000000 -0500 > > > > @@ -2459,6 +2459,11 @@ > > > > bzero((char *)&config, len); > > > > config.nc_length = len; > > > > config.nc_fhconfig.ncf_length = sizeof(ndis_80211_config_fh); > > > > + > > > > + device_printf(sc->ndis_dev, "couldn't change " > > > > + "Testing config.nc_dsconfig: %u \n", > > > > + config.nc_dsconfig); > > > > + > > > > rval = ndis_get_info(sc, OID_802_11_CONFIGURATION, &config, &len); > > > > > > printf should be bellow ndis_get_info() and above ndis_set_info(). > > > > Alright, I've moved the printf down a few lines and recompiled. > > > > > Does same problem happens when not using WPA eg. wpa_supplicant? > > > > It's actually been running just fine since I got home. I'm still using > > wpa_supplicant, but with WEP instead of WPA. This has been about four > > hours. Not much network traffic, but certainly more than what causes > > the problem at work. > > > > I'm going to let it continue to run through the night. I have a cron > > job setup to transfer several 800 meg files to this laptop via scp, so > > it'll be interesting to see if that works over this driver. > > > > Tomorrow morning, when I get into work, I'll grab the debug output > > again, this time with the printf (hopefully) in the correct place. > > Looks like config.nc_dsconfig is 2462000 > > The wireless connection stayed up all night, even while transferring > over 2 gigs of data via scp. The problem appears to be specific to > this AP using WPA. I can try WPA on my home network in about 10 hours > to see if the same happens there. When I switched my home network to use WPA I started to have the same problems as with the WPA network at work. config.nc_dsconfig still reads 246200. Adam -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-net@FreeBSD.ORG Thu Feb 19 21:38: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 1DF1E106566B for ; Thu, 19 Feb 2009 21:38:18 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id 77E7E8FC1B for ; Thu, 19 Feb 2009 21:38:17 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by ewy14 with SMTP id 14so632271ewy.19 for ; Thu, 19 Feb 2009 13:38:16 -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 :content-transfer-encoding; bh=L6aHRrAb1CTidLJrq9f5wptFGLqYwUX2c5b4wbpnAXQ=; b=DD9d+2v+Eb4scTac3Icink3rOcXs9i8RRu9JH+7Sko7Ckak39BWYZjiK4DvNmEjV3D NifFQWRN/w2XglzdbfcMI53Sx9QfcCxoPsUSpatU0g4O+lBIMsJmIF6aWzWCkYqjwhYz 3BOLY/WlJZ34cRbmlhTVVIak9kHKxTUWZq/hc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=NPwaM95Jiul8QwK3Gr++RA8ov2tG397S29DFVeTsTK4NMUsOlnZrDGKkcZE+eDZ4y0 x4v0XXivx43zp8H+Um5ZbsCdUPVa90zuAe+dx/LbPfGisX8uNG5cKrRAIZZnZApdp9Sf Tyym1lUwD6XEVYl/Hxq8WZ5Qjnhv/MuPRmYFo= MIME-Version: 1.0 Received: by 10.210.43.10 with SMTP id q10mr26791ebq.58.1235079496459; Thu, 19 Feb 2009 13:38:16 -0800 (PST) In-Reply-To: <20090219161807.63efaaa5@thorn.ashke.com> References: <200902171720.n1HHKkIf071491@freefall.freebsd.org> <3a142e750902180733o679b050ck8d9287f0bdd860e7@mail.gmail.com> <20090218111223.4483b923@memory.visualtech.com> <3a142e750902181027q25863f39ycc342d6506949eb9@mail.gmail.com> <20090218134935.14f0a8c2@memory.visualtech.com> <20090218142659.135a73bc@memory.visualtech.com> <3a142e750902181610h65f23d13vfeb20cc19ea0944a@mail.gmail.com> <20090218194810.075e0c7c@sorrow.ashke.com> <20090219055035.1ff55f19@memory.visualtech.com> <20090219161807.63efaaa5@thorn.ashke.com> Date: Thu, 19 Feb 2009 22:38:16 +0100 Message-ID: <3a142e750902191338v7e2f3e9fna3b4ac77f0cbe612@mail.gmail.com> From: "Paul B. Mahol" To: Adam K Kirchhoff Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: kern/131781: [ndis] ndis keeps dropping the link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2009 21:38:18 -0000 On 2/19/09, Adam K Kirchhoff wrote: > On Thu, 19 Feb 2009 05:50:35 -0500 > Adam K Kirchhoff wrote: > >> On Wed, 18 Feb 2009 19:48:10 -0500 >> Adam K Kirchhoff wrote: >> >> > On Thu, 19 Feb 2009 01:10:08 +0100 >> > "Paul B. Mahol" wrote: >> > >> > > On 2/18/09, Adam K Kirchhoff wrote: >> > > > --- if_ndis.c 2009-01-31 00:22:11.000000000 -0500 >> > > > +++ if_ndis.c.orig 2009-02-18 14:03:30.000000000 -0500 >> > > > @@ -2459,6 +2459,11 @@ >> > > > bzero((char *)&config, len); >> > > > config.nc_length = len; >> > > > config.nc_fhconfig.ncf_length = sizeof(ndis_80211_config_fh); >> > > > + >> > > > + device_printf(sc->ndis_dev, "couldn't change " >> > > > + "Testing config.nc_dsconfig: %u \n", >> > > > + config.nc_dsconfig); >> > > > + >> > > > rval = ndis_get_info(sc, OID_802_11_CONFIGURATION, &config, &len); >> > > >> > > printf should be bellow ndis_get_info() and above ndis_set_info(). >> > >> > Alright, I've moved the printf down a few lines and recompiled. >> > >> > > Does same problem happens when not using WPA eg. wpa_supplicant? >> > >> > It's actually been running just fine since I got home. I'm still using >> > wpa_supplicant, but with WEP instead of WPA. This has been about four >> > hours. Not much network traffic, but certainly more than what causes >> > the problem at work. >> > >> > I'm going to let it continue to run through the night. I have a cron >> > job setup to transfer several 800 meg files to this laptop via scp, so >> > it'll be interesting to see if that works over this driver. >> > >> > Tomorrow morning, when I get into work, I'll grab the debug output >> > again, this time with the printf (hopefully) in the correct place. >> >> Looks like config.nc_dsconfig is 2462000 >> >> The wireless connection stayed up all night, even while transferring >> over 2 gigs of data via scp. The problem appears to be specific to >> this AP using WPA. I can try WPA on my home network in about 10 hours >> to see if the same happens there. > > When I switched my home network to use WPA I started to have the same > problems as with the WPA network at work. config.nc_dsconfig still > reads 246200. Enable wpa_supplicant debugging and try find something interesting. I still cant understant why enabling debug.ndis hides problem. -- Paul From owner-freebsd-net@FreeBSD.ORG Thu Feb 19 22:26: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 DD661106568B for ; Thu, 19 Feb 2009 22:26:45 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3A36D8FC1C for ; Thu, 19 Feb 2009 22:26:45 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from vhoffman-macbook.local ([IPv6:2001:470:9099:0:214:51ff:feed:712d]) (authenticated bits=0) by unsane.co.uk (8.14.3/8.14.0) with ESMTP id n1JMRYKp024595 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 19 Feb 2009 22:27:35 GMT (envelope-from vince@unsane.co.uk) Message-ID: <499DDCA2.5050108@unsane.co.uk> Date: Thu, 19 Feb 2009 22:26:42 +0000 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-GB; rv:1.9.1b3pre) Gecko/20081204 Thunderbird/3.0b1 MIME-Version: 1.0 To: Felipe Jara Saba References: <499C4ECC.8050109@vtr.net> In-Reply-To: <499C4ECC.8050109@vtr.net> X-Enigmail-Version: 0.96a Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: differentiated statistics for ipv4/ipv6 traffica? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2009 22:26:46 -0000 On 18/2/09 18:09, Felipe Jara Saba wrote: > Hello: > > Has anyone tried to get differentiated statistics for ipv4/ipv6 > traffic in a FreeBSD server?. I was hoping that I could retrieve that > information through SNMP (I`m running net-snmp on a freebsd 7.1 box), > but even though there is a IPv6-MIB.txt in the > /usr/local/share/snmp/mibs dir, it seems it only shows the ipv4/ipv6 > traffic combined into the same counters. > > Greetings > > Best I can think of is netstat. Should be enough info using the -i or -I arguments with -b (-h optional.) (22:20:27 <~>) 0 # netstat -i -bh -f inet6 Name Mtu Network Address Ipkts Ierrs Ibytes Opkts Oerrs Obytes Coll bge0 1500 fe80:1::2e0:8 fe80:1::2e0:81ff: 5.0K - 335K 5.0K - 340K - bge0 1500 2001:470:1f09 2001:470:1f09:110 1.6M - 291M 2.4M - 3.0G - em1 1500 fe80:3::207:e fe80:3::207:e9ff: 0 - 0 4 - 288 - lo0 16384 localhost ::1 637 - 74K 642 - 75K - lo0 16384 fe80:7::1 fe80:7::1 0 - 0 0 - 0 - root@crab (22:18:17 <~>) 0 # netstat -I bge0 -bh -f inet6 Name Mtu Network Address Ipkts Ierrs Ibytes Opkts Oerrs Obytes Coll bge0 1500 fe80:1::2e0:8 fe80:1::2e0:81ff: 4.9K - 334K 5.0K - 339K - bge0 1500 2001:470:1f09 2001:470:1f09:110 1.6M - 291M 2.4M - 3.0G - Hope that helps, Vince From owner-freebsd-net@FreeBSD.ORG Thu Feb 19 23:41:06 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C57BA1065674 for ; Thu, 19 Feb 2009 23:41:06 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id 97F618FC13 for ; Thu, 19 Feb 2009 23:41:06 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LaICu-00028g-3D for freebsd-net@freebsd.org; Thu, 19 Feb 2009 15:21:28 -0800 Message-ID: <22111802.post@talk.nabble.com> Date: Thu, 19 Feb 2009 15:21:28 -0800 (PST) From: new2FreeBSD To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: laks_guy@yahoo.com Subject: Plz help: Configuring routing protocols on Freebsd router X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Feb 2009 23:41:07 -0000 Dear guys, I am new to FreeBSD and to this forum as well. Please help me as I am in middle of a project. My question is, can I configure the following routing protocols on a freebsd router, if so, how can I configure it. - Ad hoc on-demand distance vector routing protocol (AODV) - Optimized link state routing protocol (OLSR) - Dynamic source routing protocol (DSR) Thanks in advance. Regards, Simon -- View this message in context: http://www.nabble.com/Plz-help%3A-Configuring-routing-protocols-on-Freebsd-router-tp22111802p22111802.html Sent from the freebsd-net mailing list archive at Nabble.com. From owner-freebsd-net@FreeBSD.ORG Fri Feb 20 00:18: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 66C41106566C for ; Fri, 20 Feb 2009 00:18:11 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from cohiba.eagle.ca (cohiba.eagle.ca [208.70.104.203]) by mx1.freebsd.org (Postfix) with ESMTP id EA6C98FC16 for ; Fri, 20 Feb 2009 00:18:10 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 71188 invoked by uid 89); 19 Feb 2009 23:51:28 -0000 Received: from unknown (HELO ?192.168.1.114?) (steveb@eagle.ca@208.70.104.100) by cohiba.eagle.ca with ESMTPA; 19 Feb 2009 23:51:28 -0000 Message-ID: <499DF077.20409@ibctech.ca> Date: Thu, 19 Feb 2009 18:51:19 -0500 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: new2FreeBSD References: <22111802.post@talk.nabble.com> In-Reply-To: <22111802.post@talk.nabble.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Plz help: Configuring routing protocols on Freebsd router X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Feb 2009 00:18:11 -0000 new2FreeBSD wrote: > Dear guys, > > I am new to FreeBSD and to this forum as well. Please help me as I am in > middle of a project. My question is, can I configure the following routing > protocols on a freebsd router, if so, how can I configure it. I could only find one. The rest may require some crafty Googling. > - Optimized link state routing protocol (OLSR) /usr/ports/net/olsrd Steve From owner-freebsd-net@FreeBSD.ORG Fri Feb 20 04:17: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 E8FDB106566C for ; Fri, 20 Feb 2009 04:17:11 +0000 (UTC) (envelope-from pgnet.trash@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.188]) by mx1.freebsd.org (Postfix) with ESMTP id 6DAF98FC08 for ; Fri, 20 Feb 2009 04:17:11 +0000 (UTC) (envelope-from pgnet.trash@gmail.com) Received: by mu-out-0910.google.com with SMTP id w1so546364mue.3 for ; Thu, 19 Feb 2009 20:17:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=idc2Mr2RVpJB3dfXT3/hlDlkwowETIrU18hBqRdNhyI=; b=WZ1YUIKNdVBoyK+AuTI4ZWZdatoVz8MPXzFQkNibfF/PoreIcorMfJNgW4DrsPQZm/ BH/3i5Xi63QZMPeXv/IFaROEHMC7pDsL/6a7GAW4Sgd44VoUoff0eP0+54hLdMSjXR08 Fnznd+oDQpG0uvbCIDUeh/lkwgUtCF2z3uWrA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; b=JeUb0hbkCof+L5S56rHXU3exZ+jqXsp8vPSNdYaQQ71Pm02atIIIIFgHiJnv1v0Jk1 i2Cuc9/bmKZpEsWNaPkGKycGSnnwttZrVrQBDtH9pySiiUXTHo2+2kfzBAqJEL929HeX YCbcE7eHyjk+y2HEL2BSbdiNZDDLpxw6fqBm4= MIME-Version: 1.0 Sender: pgnet.trash@gmail.com Received: by 10.102.219.8 with SMTP id r8mr1259217mug.10.1235102074971; Thu, 19 Feb 2009 19:54:34 -0800 (PST) Date: Thu, 19 Feb 2009 19:54:34 -0800 X-Google-Sender-Auth: dcdae24d0d7b6d3f Message-ID: From: PGNet To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: openvpn "HMAC auth" and TLS errors @ client connect? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Feb 2009 04:17:12 -0000 i'm taking a stab at setup of, openvpn --version OpenVPN 2.0.6 i386-portbld-freebsd6.3 [SSL] [LZO] built on Jul 18 2008 on a client's (read: i don't want to fubar this box!) headless router/firewall (running fbsd pf) box, uname -r 6.3-RELEASE-p3 i've setup, rc.conf openvpn_enable="YES" openvpn_configfile="/usr/local/etc/openvpn/openvpn.conf" openvpn_if="tun" @ server, "/usr/local/etc/openvpn/openvpn.conf" -------- server 172.30.7.0 255.255.255.0 dev tun1 proto udp port 22222 dh /usr/local/etc/openvpn/dh2048.pem ca /usr/local/etc/openvpn/mydomain.com.CA.cert.rsa.pem cert /usr/local/etc/openvpn/server.cert.rsa.pem key /usr/local/etc/openvpn/server.key.rsa.pem tls-auth /usr/local/etc/openvpn/ta.key 0 client-config-dir /usr/local/etc/openvpn/ccd ccd-exclusive max-clients 2 max-routes-per-client 128 connect-freq 3 60 cipher AES-256-CBC client-to-client comp-lzo keepalive 15 120 persist-key persist-tun status openvpn-status.log verb 4 -------- @ client, ".../openvpn.conf" -------- tls-client tls-remote ho3.mydomain.com remote 99.xx.xx.xx 22222 dev tun proto udp resolv-retry infinite keepalive 15 120 nobind persist-key persist-tun ca /usr/local/etc/openvpn/mydomain.com.CA.cert.rsa.pem cert /usr/local/etc/openvpn/client.cert.rsa.pem key /usr/local/etc/openvpn/client.key.rsa.pem tls-auth /usr/local/etc/openvpn/ta.key 1 ns-cert-type server cipher AES-256-CBC comp-lzo verb 4 pull -------- @ server, /usr/local/etc/rc.d/openvpn start Starting openvpn. add net 172.30.7.0: gateway 172.30.7.2 @ client connect, client logs show, ... Thu 02/19/09 07:28 PM: Control Channel Authentication: using '/usr/local/etc/openvpn/ta.key' as a OpenVPN static key file Thu 02/19/09 07:28 PM: Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Thu 02/19/09 07:28 PM: Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Thu 02/19/09 07:28 PM: LZO compression initialized Thu 02/19/09 07:28 PM: Control Channel MTU parms [ L:1542 D:166 EF:66 EB:0 ET:0 EL:0 ] Thu 02/19/09 07:28 PM: Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ] Thu 02/19/09 07:28 PM: tls-client' Thu 02/19/09 07:28 PM: tls-server' Thu 02/19/09 07:28 PM: Local Options hash (VER=V4): '504e774e' Thu 02/19/09 07:28 PM: Expected Remote Options hash (VER=V4): '14168603' Thu 02/19/09 07:28 PM: Socket Buffers: R=[42080->65536] S=[9216->65536] Thu 02/19/09 07:28 PM: UDPv4 link local: [undef] Thu 02/19/09 07:28 PM: UDPv4 link remote: 99.xx.xx.xx:22222 Thu 02/19/09 07:28 PM: @ server syslog, Feb 19 19:28:21 server openvpn[3947]: Authenticate/Decrypt packet error: packet HMAC authentication failed Feb 19 19:28:21 server openvpn[3947]: TLS Error: incoming packet authentication failed from 192.168.1.6:51365 i tried to follow what online help i could find, but have clearly missed something. any suggestions as to what to fix? not sure what info to provide; happy to provide what's needed. thanks. From owner-freebsd-net@FreeBSD.ORG Fri Feb 20 06:18:28 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 752491065670 for ; Fri, 20 Feb 2009 06:18:28 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from mail.bitblocks.com (bitblocks.com [64.142.15.60]) by mx1.freebsd.org (Postfix) with ESMTP id 62A0B8FC13 for ; Fri, 20 Feb 2009 06:18:28 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost.bitblocks.com [127.0.0.1]) by mail.bitblocks.com (Postfix) with ESMTP id 035255B1B for ; Thu, 19 Feb 2009 21:59:36 -0800 (PST) To: net@freebsd.org Date: Thu, 19 Feb 2009 21:59:35 -0800 From: Bakul Shah Message-Id: <20090220055936.035255B1B@mail.bitblocks.com> Cc: Subject: A more pliable firewall X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Feb 2009 06:18:28 -0000 I am wondering if there is a more dynamic and scriptable firewall program. The idea is to send it alerts (with sender host address) whenever a dns probe fails or ssh login fails or smtpd finds it has been fed spam or your website is fed bad urls. This program will then update the firewall after a certain number of attempts have been made from a host within a given period. Right now, when I find bad guys blasting packets at me, I add a rule to pf.conf to drop all packets from these hosts but all this manual editing is getting old and the internet is getting more and more like the Wild West crossed with the Attack of the Zombies. From owner-freebsd-net@FreeBSD.ORG Fri Feb 20 08:27:15 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 163131065670 for ; Fri, 20 Feb 2009 08:27:15 +0000 (UTC) (envelope-from lstewart@room52.net) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id 9E0FB8FC08 for ; Fri, 20 Feb 2009 08:27:14 +0000 (UTC) (envelope-from lstewart@room52.net) Received: from lstewart.caia.swin.edu.au (lstewart.caia.swin.edu.au [136.186.229.95]) (authenticated bits=0) by lauren.room52.net (8.14.3/8.14.3) with ESMTP id n1K84oZL035494 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Feb 2009 19:04:56 +1100 (EST) (envelope-from lstewart@room52.net) Message-ID: <499E641D.1060605@room52.net> Date: Fri, 20 Feb 2009 19:04:45 +1100 From: Lawrence Stewart User-Agent: Thunderbird 2.0.0.19 (X11/20090213) MIME-Version: 1.0 To: Bakul Shah References: <20090220055936.035255B1B@mail.bitblocks.com> In-Reply-To: <20090220055936.035255B1B@mail.bitblocks.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL autolearn=disabled version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on lauren.room52.net Cc: net@freebsd.org Subject: Re: A more pliable firewall X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Feb 2009 08:27:15 -0000 Bakul Shah wrote: > I am wondering if there is a more dynamic and scriptable > firewall program. The idea is to send it alerts (with sender > host address) whenever a dns probe fails or ssh login fails > or smtpd finds it has been fed spam or your website is fed > bad urls. This program will then update the firewall after a > certain number of attempts have been made from a host within > a given period. > > Right now, when I find bad guys blasting packets at me, I add > a rule to pf.conf to drop all packets from these hosts but > all this manual editing is getting old and the internet is > getting more and more like the Wild West crossed with the > Attack of the Zombies. It's a fairly crude solution and doesn't address a lot of the features you mention, but I do this with PF on many of my FreeBSD machines (tuning the various timeout and connection rates as appropriate): # Drop packets from hosts trying to spam us with connections. # We rehabilitate this list by calling # "pfctl -t bad_hosts -T expire 600" from cron every few mins block drop in quick on $wan_if from # Allow TCP connections from the outside world to: # ssh (port 22) # https (port 443) # Attempting to connect more than 5 times in 30 seconds # will put you in the bad books for a while pass in quick on $wan_if inet proto tcp from any to ($wan_if) port { 22, 443 } keep state (max-src-conn-rate 5/30, overload flush global) It does a surprisingly good job at stopping a majority of cruft ending up in my security logs, and the rehabilitation via cron ensures any false positives don't require manual intervention to remove the offending IP(s) from the black list. There are also of course many options in ports, some of which are very sophisticated (e.g. snort, bro). Cheers, Lawrence From owner-freebsd-net@FreeBSD.ORG Fri Feb 20 09:03:24 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 CB76B106564A for ; Fri, 20 Feb 2009 09:03:24 +0000 (UTC) (envelope-from artem@aws-net.org.ua) Received: from alf.aws-net.org.ua (alf.aws-net.org.ua [85.90.196.192]) by mx1.freebsd.org (Postfix) with ESMTP id 24DB98FC14 for ; Fri, 20 Feb 2009 09:03:23 +0000 (UTC) (envelope-from artem@aws-net.org.ua) Received: from alf.aws-net.org.ua (alf.aws-net.org.ua [192.168.32.61]) by alf.aws-net.org.ua (8.14.3/8.14.3) with ESMTP id n1K8SsJt018789 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Feb 2009 10:28:55 +0200 (EET) (envelope-from artem@aws-net.org.ua) Date: Fri, 20 Feb 2009 10:28:49 +0200 (EET) From: Artyom Viklenko To: Bakul Shah In-Reply-To: <20090220055936.035255B1B@mail.bitblocks.com> Message-ID: References: <20090220055936.035255B1B@mail.bitblocks.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (alf.aws-net.org.ua [192.168.32.61]); Fri, 20 Feb 2009 10:28:55 +0200 (EET) X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on alf.aws-net.org.ua X-Virus-Status: Clean Cc: net@freebsd.org Subject: Re: A more pliable firewall X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Feb 2009 09:03:25 -0000 On Thu, 19 Feb 2009, Bakul Shah wrote: > I am wondering if there is a more dynamic and scriptable > firewall program. The idea is to send it alerts (with sender > host address) whenever a dns probe fails or ssh login fails > or smtpd finds it has been fed spam or your website is fed > bad urls. This program will then update the firewall after a > certain number of attempts have been made from a host within > a given period. > > Right now, when I find bad guys blasting packets at me, I add > a rule to pf.conf to drop all packets from these hosts but Actually, you can use tables and add these ip-s to tables while leave pf.conf untouchable. The only thing to resolv is to write some daemon which will receive notifyes and update pf tables. It should be not so hard to write such piece of software. > all this manual editing is getting old and the internet is > getting more and more like the Wild West crossed with the > Attack of the Zombies. > _______________________________________________ > 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" > -- Sincerely yours, Artyom Viklenko. ------------------------------------------------------- artem@aws-net.org.ua | http://www.aws-net.org.ua/~artem FreeBSD: The Power to Serve - http://www.freebsd.org From owner-freebsd-net@FreeBSD.ORG Fri Feb 20 12:51: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 199F21065678 for ; Fri, 20 Feb 2009 12:51:40 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from spamfish.visualtech.com (h-67-102-187-40.phlapafg.covad.net [67.102.187.40]) by mx1.freebsd.org (Postfix) with ESMTP id BED568FC1C for ; Fri, 20 Feb 2009 12:51:39 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from mailstore.visualtech.com (unknown [67.102.187.41]) by spamfish.visualtech.com (Postfix) with ESMTPS id 4BDC11F45EF; Fri, 20 Feb 2009 07:35:22 -0500 (EST) Received: from localhost (h-67-103-204-242.phlapafg.covad.net [67.103.204.242]) by mailstore.visualtech.com (Postfix) with ESMTP id 9ED94ADC25B; Fri, 20 Feb 2009 07:50:40 -0500 (EST) Date: Fri, 20 Feb 2009 07:39:02 -0500 From: Adam K Kirchhoff To: "Paul B. Mahol" Message-ID: <20090220073902.193c929d@voicenet.com> In-Reply-To: <3a142e750902191338v7e2f3e9fna3b4ac77f0cbe612@mail.gmail.com> References: <200902171720.n1HHKkIf071491@freefall.freebsd.org> <3a142e750902180733o679b050ck8d9287f0bdd860e7@mail.gmail.com> <20090218111223.4483b923@memory.visualtech.com> <3a142e750902181027q25863f39ycc342d6506949eb9@mail.gmail.com> <20090218134935.14f0a8c2@memory.visualtech.com> <20090218142659.135a73bc@memory.visualtech.com> <3a142e750902181610h65f23d13vfeb20cc19ea0944a@mail.gmail.com> <20090218194810.075e0c7c@sorrow.ashke.com> <20090219055035.1ff55f19@memory.visualtech.com> <20090219161807.63efaaa5@thorn.ashke.com> <3a142e750902191338v7e2f3e9fna3b4ac77f0cbe612@mail.gmail.com> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; i386-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-visualtech-MailScanner: Found to be clean Cc: freebsd-net@freebsd.org Subject: Re: kern/131781: [ndis] ndis keeps dropping the link X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Feb 2009 12:51:40 -0000 On Thu, 19 Feb 2009 22:38:16 +0100 "Paul B. Mahol" wrote: > On 2/19/09, Adam K Kirchhoff wrote: > > On Thu, 19 Feb 2009 05:50:35 -0500 > > Adam K Kirchhoff wrote: > > > >> On Wed, 18 Feb 2009 19:48:10 -0500 > >> Adam K Kirchhoff wrote: > >> > >> > On Thu, 19 Feb 2009 01:10:08 +0100 > >> > "Paul B. Mahol" wrote: > >> > > >> > > On 2/18/09, Adam K Kirchhoff wrote: > >> > > > --- if_ndis.c 2009-01-31 00:22:11.000000000 -0500 > >> > > > +++ if_ndis.c.orig 2009-02-18 14:03:30.000000000 -0500 > >> > > > @@ -2459,6 +2459,11 @@ > >> > > > bzero((char *)&config, len); > >> > > > config.nc_length = len; > >> > > > config.nc_fhconfig.ncf_length = sizeof(ndis_80211_config_fh); > >> > > > + > >> > > > + device_printf(sc->ndis_dev, "couldn't change " > >> > > > + "Testing config.nc_dsconfig: %u \n", > >> > > > + config.nc_dsconfig); > >> > > > + > >> > > > rval = ndis_get_info(sc, OID_802_11_CONFIGURATION, &config, &len); > >> > > > >> > > printf should be bellow ndis_get_info() and above ndis_set_info(). > >> > > >> > Alright, I've moved the printf down a few lines and recompiled. > >> > > >> > > Does same problem happens when not using WPA eg. wpa_supplicant? > >> > > >> > It's actually been running just fine since I got home. I'm still using > >> > wpa_supplicant, but with WEP instead of WPA. This has been about four > >> > hours. Not much network traffic, but certainly more than what causes > >> > the problem at work. > >> > > >> > I'm going to let it continue to run through the night. I have a cron > >> > job setup to transfer several 800 meg files to this laptop via scp, so > >> > it'll be interesting to see if that works over this driver. > >> > > >> > Tomorrow morning, when I get into work, I'll grab the debug output > >> > again, this time with the printf (hopefully) in the correct place. > >> > >> Looks like config.nc_dsconfig is 2462000 > >> > >> The wireless connection stayed up all night, even while transferring > >> over 2 gigs of data via scp. The problem appears to be specific to > >> this AP using WPA. I can try WPA on my home network in about 10 hours > >> to see if the same happens there. > > > > When I switched my home network to use WPA I started to have the same > > problems as with the WPA network at work. config.nc_dsconfig still > > reads 246200. > > Enable wpa_supplicant debugging and try find something interesting. > I still cant understant why enabling debug.ndis hides problem. Well, one mystery hopefully solved. It looks like it has nothing to do with enabling debug.ndis. Instead, it seems related to the fact that it connects the first time I bring up the interface, whether debug.ndis is enabled or not. Of course, all my attempts at running wpa_supplicant directly from a terminal, with debugging enabled, has resulted in a working connection. I'll have to do more testing to see if I can find some consistency in this problem. Adam -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-net@FreeBSD.ORG Fri Feb 20 13:30: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 487741065672 for ; Fri, 20 Feb 2009 13:30:15 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by mx1.freebsd.org (Postfix) with ESMTP id CF5CE8FC13 for ; Fri, 20 Feb 2009 13:30:14 +0000 (UTC) (envelope-from max@love2party.net) Received: from vampire.homelinux.org (dslb-088-064-183-077.pools.arcor-ip.net [88.64.183.77]) by mrelayeu.kundenserver.de (node=mrelayeu4) with ESMTP (Nemesis) id 0ML21M-1LaVSH0sFf-0005pR; Fri, 20 Feb 2009 14:30:13 +0100 Received: (qmail 99266 invoked from network); 20 Feb 2009 13:30:12 -0000 Received: from fbsd8.laiers.local (192.168.4.200) by router.laiers.local with SMTP; 20 Feb 2009 13:30:12 -0000 From: Max Laier Organization: FreeBSD To: freebsd-net@freebsd.org Date: Fri, 20 Feb 2009 14:30:11 +0100 User-Agent: KMail/1.11.0 (FreeBSD/8.0-CURRENT; KDE/4.2.0; i386; ; ) References: <20090220055936.035255B1B@mail.bitblocks.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902201430.12311.max@love2party.net> X-Provags-ID: V01U2FsdGVkX1+VhL2kGZ04vhUx1B7+XWogwveuNMx0YQuw8m2 wHdqE/XhgdzufhRyUk9FKHsH69L+/4KhmUcoBg4i/lFo34MFoT qThiffyA9YsuKOd9PPcPA== Cc: Bakul Shah , Artyom Viklenko Subject: Re: A more pliable firewall X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Feb 2009 13:30:15 -0000 On Friday 20 February 2009 09:28:49 Artyom Viklenko wrote: > On Thu, 19 Feb 2009, Bakul Shah wrote: > > I am wondering if there is a more dynamic and scriptable > > firewall program. The idea is to send it alerts (with sender > > host address) whenever a dns probe fails or ssh login fails > > or smtpd finds it has been fed spam or your website is fed > > bad urls. This program will then update the firewall after a > > certain number of attempts have been made from a host within > > a given period. > > > > Right now, when I find bad guys blasting packets at me, I add > > a rule to pf.conf to drop all packets from these hosts but > > Actually, you can use tables and add these ip-s to tables > while leave pf.conf untouchable. The only thing to resolv > is to write some daemon which will receive notifyes and update > pf tables. It should be not so hard to write such piece > of software. /usr/ports/net-mgmt/pftabled]> cat pkg-descr The pftabled daemon is a small helper to make your pf tables reachable from other hosts. You can add/delete/flush IP addresses to/from a remote table with a single UDP datagram. A simple client program is included to do this from the command line. WWW: http://wolfermann.org/pftabled.html > > all this manual editing is getting old and the internet is > > getting more and more like the Wild West crossed with the > > Attack of the Zombies. > > _______________________________________________ > > 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, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News From owner-freebsd-net@FreeBSD.ORG Fri Feb 20 13:43:07 2009 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 175AB1065672 for ; Fri, 20 Feb 2009 13:43:07 +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 69A2F8FC08 for ; Fri, 20 Feb 2009 13:43:06 +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 n1KDU2CB055872; Sat, 21 Feb 2009 00:30:03 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sat, 21 Feb 2009 00:30:02 +1100 (EST) From: Ian Smith To: Artyom Viklenko In-Reply-To: Message-ID: <20090220235840.I46613@sola.nimnet.asn.au> References: <20090220055936.035255B1B@mail.bitblocks.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Bakul Shah , net@freebsd.org Subject: Re: A more pliable firewall X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Feb 2009 13:43:07 -0000 On Fri, 20 Feb 2009, Artyom Viklenko wrote: > On Thu, 19 Feb 2009, Bakul Shah wrote: > > > I am wondering if there is a more dynamic and scriptable > > firewall program. The idea is to send it alerts (with sender > > host address) whenever a dns probe fails or ssh login fails > > or smtpd finds it has been fed spam or your website is fed > > bad urls. This program will then update the firewall after a > > certain number of attempts have been made from a host within > > a given period. > > > > Right now, when I find bad guys blasting packets at me, I add > > a rule to pf.conf to drop all packets from these hosts but > > > Actually, you can use tables and add these ip-s to tables > while leave pf.conf untouchable. The only thing to resolv > is to write some daemon which will receive notifyes and update > pf tables. It should be not so hard to write such piece > of software. /usr/ports/security/fwlogwatch DESCRIPTION fwlogwatch produces Linux ipchains, Linux netfilter/iptables, Solaris/BSD/Irix/HP-UX ipfilter, ipfw, Cisco IOS, Cisco PIX, NetScreen, Windows XP firewall, Elsa Lancom router and Snort IDS log summary reports in plain text and HTML form and has a lot of options to analyze and display relevant patterns. It can produce customizable incident reports and send them to abuse contacts at offending sites or CERTs. Finally, it can also run as daemon (with web interface) doing realtime log monitoring and reporting anomalies or starting attack countermea- sures. I notice it doesn't mention pf, but it might be worth checking out; it calls your scripts on detection by various rules and looks customisable. Thanks to Michael Butler, who pointed out how to add table entries with it, with a timestamp value allowing removal of 'stale' entries by cron. > > all this manual editing is getting old and the internet is > > getting more and more like the Wild West crossed with the > > Attack of the Zombies. Indeed. Having lots of fun with ipfw tables here, most lately detecting and so ceasing participation in forged-source DNS amplification attacks. cheers, Ian From owner-freebsd-net@FreeBSD.ORG Fri Feb 20 17:24: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 D4F5B1065670 for ; Fri, 20 Feb 2009 17:24:17 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.234]) by mx1.freebsd.org (Postfix) with ESMTP id A820D8FC0C for ; Fri, 20 Feb 2009 17:24:17 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by rv-out-0506.google.com with SMTP id g9so935359rvb.3 for ; Fri, 20 Feb 2009 09:24:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=T8oOforc5GypdWxyMP+cy577OiMJ/RFF1P122Ji2lSI=; b=UJhsYRICvtvKD+1R+rZqrS7MUrllJuQZjWXLSXjtuQzIH3OEgkguHVHPZDAt+vo58L 4pFcXslaf2PvrByYL9Nsbk7x+LZ+YxWgMYapGleEDeIW/KlnvJYGOVDeazcKtFO+fobS 8IDDM8Ogvpu0gJ6+lcVUYxpqROZm8NJkrHnBw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=ZDdZRQb0EUimYuzTllMdwCobuwKaUxJdME759r2mMo0Da3ZtHgZUdGomGnsUlopkJK KGqi6t472bMs/pthlrC3UZ1ggPtBESf9Wgwv3E8GDHLiLE424DcfZW80wpG8TP7ZirvN oMKWxjtdMQemFhZp+2/9crApdMoyWb4ulFyyE= MIME-Version: 1.0 Sender: mat.macy@gmail.com Received: by 10.141.20.7 with SMTP id x7mr523050rvi.85.1235150657378; Fri, 20 Feb 2009 09:24:17 -0800 (PST) In-Reply-To: <910e60e80902180150n41a592ffyb62ea53beb24f1ef@mail.gmail.com> References: <910e60e80902180150n41a592ffyb62ea53beb24f1ef@mail.gmail.com> Date: Fri, 20 Feb 2009 09:24:17 -0800 X-Google-Sender-Auth: c7bc3bb50bc9773a Message-ID: <3c1674c90902200924p79d8d66dg9584182a1e662047@mail.gmail.com> From: Kip Macy To: dikshie Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: panic: _rw_wlock_hard X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Feb 2009 17:24:18 -0000 Known issue. I haven't been around to fix. Cheers, Kip On Wed, Feb 18, 2009 at 1:50 AM, dikshie wrote: > Hi, > does anyone see this panic on -HEAD: > > panic: _rw_wlock_hard: recursing but non-recursive rw radix node head > @ /usr/src/sys/net/route.c:831 > > kdb_enter() at kdb_enter+0x3a > panic() at panic+0x136 > _rw_wlock_hard() at _rw_wlock_hard+0x66 > _rw_wlock() at _rw_wlock+0xae > rtquest1_fib() at rtquest1_fib+0x95 > rtquest_fib() at rtquest_fib+0x5e > in_rtquest() at in_rtquest+0x3b > in_rtqkill() at in_rtqkill+0x7f > rn_walktree() at rn_walktree+0x65 > in_rtqtimo() at in_rtqtimo+0xb0 > softclock() at softclock+0x24a > intr_event_execute_handlers() at intr_event_execute_handlers+0x125 > ithread_loop() at ithread_loop+0x9f > fork_exit() at fork_exit+0xb8 > fork_trampoline() at fork_trampoline+0x8 > > -HEAD built on Feb 16 14:26:25 JST. > > > > > > -- > -dikshie- > _______________________________________________ > 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 Feb 20 19:50:03 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC2A9106566C for ; Fri, 20 Feb 2009 19:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 992388FC13 for ; Fri, 20 Feb 2009 19:50: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 n1KJo3XU060052 for ; Fri, 20 Feb 2009 19:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1KJo3Wk060047; Fri, 20 Feb 2009 19:50:03 GMT (envelope-from gnats) Date: Fri, 20 Feb 2009 19:50:03 GMT Message-Id: <200902201950.n1KJo3Wk060047@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Joseph Lee Cc: Subject: Re: kern/124753: [ieee80211] net80211 discards power-save queue packets early X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joseph Lee List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Feb 2009 19:50:04 -0000 The following reply was made to PR kern/124753; it has been noted by GNATS. From: Joseph Lee To: bug-followup@FreeBSD.org, nugundam@nugundam.best.vwh.net Cc: Subject: Re: kern/124753: [ieee80211] net80211 discards power-save queue packets early Date: Fri, 20 Feb 2009 11:12:16 -0800 ath0: flags=8943 metric 0 mtu 2290 ether 00:11:95:8d:17:89 inet6 fe80::211:95ff:fe8d:1789%ath0 prefixlen 64 scopeid 0x2 inet 192.168.5.1 netmask 0xffffff00 broadcast 192.168.5.255 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect ) status: associated ssid AP channel 1 (2412 Mhz 11g) bssid 00:11:95:8d:17:89 authmode WPA privacy MIXED deftxkey 2 TKIP 2:128-bit TKIP 3:128-bit txpower 31.5 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11g 7 roam:rate11g 5 protmode CTS wme burst hidessid dtimperiod 1 I've noticed with tcpdump that every time the mobile station queries for power-saved packets, there's a couple of arp who-has packets sent out: 10:30:59.744056 arp who-has AP tell mobile 10:30:59.744104 arp who-has AP tell mobile Also, packet requests never make it up to the tcpdump level. Setting bintval to 25 (instead of the default 100), allows packets to be queued longer but still not passed on: Here's a debug dump from exactly when the WiFi is turned on, on the mobile device with bintval @ 25: Feb 20 10:37:01 AP kernel: ath0: [00:18:41:c0:06:54] power save mode on, 1 sta's in ps mode Feb 20 10:37:01 AP kernel: ath0: [00:18:41:c0:06:54] save frame with age 0, 1 now queued Feb 20 10:37:01 AP kernel: ath0: [00:18:41:c0:06:54] save frame with age 0, 2 now queued Feb 20 10:37:01 AP kernel: ath0: [00:18:41:c0:06:54] power save mode off, 0 sta's in ps mode Feb 20 10:37:01 AP kernel: ath0: [00:18:41:c0:06:54] flush ps queue, 2 packets queue Feb 20 10:37:01 AP kernel: ath0: [00:18:41:c0:06:54] power save mode on, 1 sta's in ps mode Feb 20 10:37:01 AP kernel: ath0: [00:18:41:c0:06:54] save frame with age 0, 1 now queued Feb 20 10:37:06 AP kernel: ath0: [00:18:41:c0:06:54] save frame with age 0, 2 now queued Feb 20 10:37:06 AP kernel: ath0: [00:18:41:c0:06:54] discard frame, age 0 Feb 20 10:37:06 AP kernel: ath0: [00:18:41:c0:06:54] discard frame, age 0 Feb 20 10:37:06 AP kernel: ath0: [00:18:41:c0:06:54] discard 2 frames for age Feb 20 10:37:07 AP kernel: ath0: [00:18:41:c0:06:54] save frame with age 0, 1 now queued Feb 20 10:37:16 AP kernel: ath0: [00:18:41:c0:06:54] save frame with age 0, 2 now queued Feb 20 10:37:21 AP kernel: ath0: [00:18:41:c0:06:54] discard frame, age 0 Feb 20 10:37:21 AP kernel: ath0: [00:18:41:c0:06:54] discard frame, age 0 Feb 20 10:37:21 AP kernel: ath0: [00:18:41:c0:06:54] discard 2 frames for age Feb 20 10:37:22 AP kernel: ath0: [00:18:41:c0:06:54] save frame with age 0, 1 now queued Feb 20 10:37:25 AP kernel: ath0: [00:18:41:c0:06:54] save frame with age 0, 2 now queued Feb 20 10:37:31 AP kernel: ath0: [00:18:41:c0:06:54] save frame with age 0, 3 now queued Feb 20 10:37:36 AP kernel: ath0: [00:18:41:c0:06:54] discard frame, age 0 Feb 20 10:37:36 AP last message repeated 2 times Feb 20 10:37:36 AP kernel: ath0: [00:18:41:c0:06:54] discard 3 frames for age Feb 20 10:37:39 AP kernel: ath0: [00:18:41:c0:06:54] save frame with age 0, 1 now queued Feb 20 10:37:45 AP kernel: ath0: [00:18:41:c0:06:54] save frame with age 0, 2 now queued Feb 20 10:37:51 AP kernel: ath0: [00:18:41:c0:06:54] discard frame, age 0 Feb 20 10:37:51 AP kernel: ath0: [00:18:41:c0:06:54] discard frame, age 0 Feb 20 10:37:51 AP kernel: ath0: [00:18:41:c0:06:54] discard 2 frames for age I do not what the meaning of the arp requests are for. Thanks. Joseph From owner-freebsd-net@FreeBSD.ORG Fri Feb 20 20:45: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 A450F106564A for ; Fri, 20 Feb 2009 20:45:19 +0000 (UTC) (envelope-from artem@aws-net.org.ua) Received: from alf.aws-net.org.ua (alf.aws-net.org.ua [85.90.196.192]) by mx1.freebsd.org (Postfix) with ESMTP id 4D9298FC18 for ; Fri, 20 Feb 2009 20:45:18 +0000 (UTC) (envelope-from artem@aws-net.org.ua) Received: from aviko (aviko.aws-net.org.ua [192.168.32.4]) (authenticated bits=0) by alf.aws-net.org.ua (8.14.3/8.14.3) with ESMTP id n1KK7TfS058940 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Feb 2009 22:07:29 +0200 (EET) (envelope-from artem@aws-net.org.ua) From: Artyom Viklenko Organization: Arto&Co. To: Max Laier Date: Fri, 20 Feb 2009 22:07:29 +0200 User-Agent: KMail/1.9.10 References: <20090220055936.035255B1B@mail.bitblocks.com> <200902201430.12311.max@love2party.net> In-Reply-To: <200902201430.12311.max@love2party.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200902202207.29379.artem@aws-net.org.ua> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (alf.aws-net.org.ua [192.168.32.61]); Fri, 20 Feb 2009 22:07:29 +0200 (EET) X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on alf.aws-net.org.ua X-Virus-Status: Clean Cc: Bakul Shah , freebsd-net@freebsd.org Subject: Re: A more pliable firewall X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Feb 2009 20:45:20 -0000 On Friday 20 February 2009 15:30:11 Max Laier wrote: > On Friday 20 February 2009 09:28:49 Artyom Viklenko wrote: > > On Thu, 19 Feb 2009, Bakul Shah wrote: > > > I am wondering if there is a more dynamic and scriptable > > > firewall program. The idea is to send it alerts (with sender > > > host address) whenever a dns probe fails or ssh login fails > > > or smtpd finds it has been fed spam or your website is fed > > > bad urls. This program will then update the firewall after a > > > certain number of attempts have been made from a host within > > > a given period. > > > > > > Right now, when I find bad guys blasting packets at me, I add > > > a rule to pf.conf to drop all packets from these hosts but > > > > Actually, you can use tables and add these ip-s to tables > > while leave pf.conf untouchable. The only thing to resolv > > is to write some daemon which will receive notifyes and update > > pf tables. It should be not so hard to write such piece > > of software. > > /usr/ports/net-mgmt/pftabled]> cat pkg-descr > The pftabled daemon is a small helper to make your pf > tables reachable from other hosts. You can add/delete/flush > IP addresses to/from a remote table with a single UDP > datagram. A simple client program is included to do this > from the command line. > > WWW: http://wolfermann.org/pftabled.html > Wonderful! Thanks a lot! :) > > > all this manual editing is getting old and the internet is > > > getting more and more like the Wild West crossed with the > > > Attack of the Zombies. > > > _______________________________________________ > > > 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" --             Sincerely yours,                              Artyom Viklenko. ------------------------------------------------------- artem@aws-net.org.ua | http://www.aws-net.org.ua/~artem artem@viklenko.net   | ================================ FreeBSD: The Power to Serve   -  http://www.freebsd.org From owner-freebsd-net@FreeBSD.ORG Fri Feb 20 20:50:04 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 87B9D1065686 for ; Fri, 20 Feb 2009 20:50:04 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from mail.bitblocks.com (bitblocks.com [64.142.15.60]) by mx1.freebsd.org (Postfix) with ESMTP id 6C0C18FC13 for ; Fri, 20 Feb 2009 20:50:04 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost.bitblocks.com [127.0.0.1]) by mail.bitblocks.com (Postfix) with ESMTP id 301AB5B3E for ; Fri, 20 Feb 2009 12:50:02 -0800 (PST) To: net@freebsd.org In-reply-to: Your message of "Sat, 21 Feb 2009 00:30:02 +1100." <20090220235840.I46613@sola.nimnet.asn.au> References: <20090220055936.035255B1B@mail.bitblocks.com> <20090220235840.I46613@sola.nimnet.asn.au> Date: Fri, 20 Feb 2009 12:50:02 -0800 From: Bakul Shah Message-Id: <20090220205003.301AB5B3E@mail.bitblocks.com> Cc: Subject: Re: A more pliable firewall X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Feb 2009 20:50:05 -0000 Thanks to everyone who responded. Looks like all the pieces to do this exist. All I have to do is to package it all in one program "sheriff" that watches various log files and pulls the trigger on the bad guy(s) at appropriate time. I think I will add a program to keep running stats on *all* the tcp/udp senders to find all those annoyingly pesky repeat senders who have no business talking to my network. What would be nice is a standard interface to report suspicious failures (sort of like syslog). If the same guy sends N DNS requests for the same thing and every request fails, chances are he is a bad guy (or a zombie acting on behalf of one). Perhaps some day a trusted network of such daemons can be used to "back pressure" the closest ISP to the sender -- who can then shut him down for a while. From owner-freebsd-net@FreeBSD.ORG Sat Feb 21 00:17:00 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 6CAE7106568F for ; Sat, 21 Feb 2009 00:17:00 +0000 (UTC) (envelope-from lwindschuh@googlemail.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 3F2648FC1D for ; Sat, 21 Feb 2009 00:17:00 +0000 (UTC) (envelope-from lwindschuh@googlemail.com) Received: by rv-out-0506.google.com with SMTP id g9so1084144rvb.3 for ; Fri, 20 Feb 2009 16:16:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=/bh9UPESinsfOPyB01waA68o+Z3Z9WkcEuow4J+gYmQ=; b=TNX8NIbrW1cBddrWJPNoFkHUm5LwelHS0vQU0+i9TJjiSq6gdttD/jFu/f8DOTgWrk 2j+5UbO8Ct4Y/wjQZv5StDOfqB7ZS4YxeNkq1MPL2rCb+q78BM5ZtZW+AIsDQZPuOp9M ZQGahmHwgCxfnKE0LoKGV7AK2PgdSQ2mdUXok= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=kjJv5MI4BOOiH9zHUTzbjRf38CWSIchMPZkJOVfuDUPyKtrX/gzZ7VOtkxAp9Pw+FY YXdhFEgMbyXKZgl1p9sIPZUMKGYU8MbkfDK1Z6C6EzLG+T+S3Ow42fa/h9BgwvVHumJf dnC/Wcryi5b9tZgDUgCkk/Je5QIqzyQpBPEjY= MIME-Version: 1.0 Received: by 10.141.62.9 with SMTP id p9mr657701rvk.80.1235173815028; Fri, 20 Feb 2009 15:50:15 -0800 (PST) Date: Sat, 21 Feb 2009 00:50:15 +0100 Message-ID: <90a5caac0902201550l4bf5878x17fd77c9c188a4ec@mail.gmail.com> From: Lucius Windschuh To: net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: ifconfig tun0 destroy: panic: Bad link elm ... prev->next != elm X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Feb 2009 00:17:01 -0000 Hi guys. This is a kind of follow-up to PR kern/116837 (please mark as solved?). The described issue is solved, but now we have this issue. The following simple steps lead to a kernel panic on my system (i386, SMP, CURRENT from Feb. 18th): -->8-- cat < /dev/tun0 > /dev/tun0 & ifconfig tun0 up ifconfig tun0 destroy & ifconfig tun0 destroy --8<-- Panic string: Bad link elm 0xc6437c00 prev->next != elm Responsible backtraces: Tracing pid 1610 tid 100114 td 0xc686f240 kdb_enter(c090abd7,c090abd7,c08e2418,eaefeb6c,0,...) at kdb_enter+0x3a panic(c08e2418,c6437c00,c091867f,d3,2d,...) at panic+0x136 if_clone_destroyif(c0976300,c6437c00,c091867f,bf,0,...) at if_clone_destroyif+0x8a if_clone_destroy(c724f320,19c,eaefebd4,c0604976,c1494788,...) at if_clone_destroy+0xa2 ifioctl(c7077dc8,80206979,c724f320,c686f240,80206979,...) at ifioctl+0x116 soo_ioctl(c71deaf0,80206979,c724f320,c722a000,c686f240,...) at soo_ioctl+0x397 kern_ioctl(c686f240,3,80206979,c724f320,64c3c0,...) at kern_ioctl+0x1dd ioctl(c686f240,eaefecf8,c,c,c09644b0,...) at ioctl+0x134 syscall(eaefed38) at syscall+0x2a3 Xint0x80_syscall() at Xint0x80_syscall+0x20 Tracing command ifconfig pid 1611 tid 100194 td 0xc6c9b000 sched_switch(c6c9b000,0,104,18d,5796c911,...) at sched_switch+0x437 mi_switch(104,0,c090edc3,1d2,0,...) at mi_switch+0x200 sleepq_switch(c6c9b000,0,c090edc3,247,c6c9b000,...) at sleepq_switch+0x15f sleepq_wait(c69aa850,0,c0918d9f,1,0,...) at sleepq_wait+0x63 _cv_wait_unlock(c69aa850,c69aa83c,c0918d76,102,c69aa800,...) at _cv_wait_unlock+0x1d4 tun_destroy(c09ca0d8,0,c0918d76,11c) at tun_destroy+0x49 tun_clone_destroy(c6437c00,c6437c00,c6437c00,c0976300,eb04eb88,...) at tun_clone_destroy+0xb8 ifc_simple_destroy(c0976300,c6437c00,c091867f,d5,2d,...) at ifc_simple_destroy+0x27 if_clone_destroyif(c0976300,c6437c00,c091867f,bf,0,...) at if_clone_destroyif+0xe1 if_clone_destroy(c677cb20,19c,eb04ebd4,c0604976,c1494788,...) at if_clone_destroy+0xa2 ifioctl(c7257620,80206979,c677cb20,c6c9b000,80206979,...) at ifioctl+0x116 soo_ioctl(c7285bd0,80206979,c677cb20,c722a000,c6c9b000,...) at soo_ioctl+0x397 kern_ioctl(c6c9b000,3,80206979,c677cb20,64c3c0,...) at kern_ioctl+0x1dd ioctl(c6c9b000,eb04ecf8,c,c,c09644b0,...) at ioctl+0x134 syscall(eb04ed38) at syscall+0x2a3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x281b4b83, esp = 0xbfbfe47c, ebp = 0xbfbfe498 --- OK, it's odd to destroy an interface two times in parallel. But it shouldn't crash the kernel. ;-) This panic is triggered reliably. To rule out side effects of my kernel config, I ran the same test with the GENERIC config and got the same result: panic. The textdump is available here: http://sites.google.com/site/lwfreebsd/Home/files/tun0-double-destroy.zip?attredirects=0 I can supply more information if needed. Kind regards, Lucius From owner-freebsd-net@FreeBSD.ORG Sat Feb 21 01:56:07 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 9CE0F106564A for ; Sat, 21 Feb 2009 01:56:07 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (v6.ibctech.ca [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id 32D108FC15 for ; Sat, 21 Feb 2009 01:56:07 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 82052 invoked by uid 89); 21 Feb 2009 01:58:01 -0000 Received: from unknown (HELO ?192.168.1.114?) (steve@ibctech.ca@::ffff:208.70.104.100) by pearl.ibctech.ca with ESMTPA; 21 Feb 2009 01:58:01 -0000 Message-ID: <499F5F30.3010503@ibctech.ca> Date: Fri, 20 Feb 2009 20:56:00 -0500 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: FreeBSD Net X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: VLAN access and sub-int X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Feb 2009 01:56:07 -0000 Hi all, I'm in a bit of a pinch. I need to set up a VLAN from a FreeBSD box to a Cisco catalyst switch, but I am not in a position to test this in a lab before I deploy it. Currently, I've got em5 to a catalyst switch. There are no vlans in place on this switch at this point (other than native 1). What I'd like to do, is configure an em5.107 sub-int, and configure the physically connected switch port as a trunk, carrying the native vlan (1) as well as vlan 107. I've already got the em5.107 interface created. I'm just worried about changing the switch port to trunk mode remotely. The switch is in an odd location in the network, and I need this vlan lit up as a temporary hack until I can physically get to the location to move some cabling. What I'm asking is if I change the switchport mode on the physically connected switch port to trunk, will the native em5 interface deal with the untagged traffic by default? FWIW, I do have access via SSH to a device that has a console cable via cuad0 directly connected to the switch, if the worst should happen. Steve From owner-freebsd-net@FreeBSD.ORG Sat Feb 21 02:48:02 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B00D5106576B for ; Sat, 21 Feb 2009 02:48:02 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (v6.ibctech.ca [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id E59238FC19 for ; Sat, 21 Feb 2009 02:48:01 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 87240 invoked by uid 89); 21 Feb 2009 02:49:56 -0000 Received: from unknown (HELO ?192.168.1.114?) (steve@ibctech.ca@::ffff:208.70.104.100) by pearl.ibctech.ca with ESMTPA; 21 Feb 2009 02:49:56 -0000 Message-ID: <499F6B5A.4090300@ibctech.ca> Date: Fri, 20 Feb 2009 21:47:54 -0500 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: FreeBSD Net References: <499F5F30.3010503@ibctech.ca> In-Reply-To: <499F5F30.3010503@ibctech.ca> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: VLAN access and sub-int X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Feb 2009 02:48:03 -0000 Steve Bertrand wrote: > What I'm asking is if I change the switchport mode on the physically > connected switch port to trunk, will the native em5 interface deal with > the untagged traffic by default? ...upon 'testing' on production gear, it works just fine. em5 continues to pick up the untagged traffic, and em5.107 properly handles the vlan 107 traffic. Steve From owner-freebsd-net@FreeBSD.ORG Sat Feb 21 04:09:45 2009 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 11BFE106566B for ; Sat, 21 Feb 2009 04:09:45 +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 62BF38FC0A for ; Sat, 21 Feb 2009 04:09:44 +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 n1L49alN087476; Sat, 21 Feb 2009 15:09:37 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sat, 21 Feb 2009 15:09:36 +1100 (EST) From: Ian Smith To: Bakul Shah In-Reply-To: <20090220205003.301AB5B3E@mail.bitblocks.com> Message-ID: <20090221135053.J46613@sola.nimnet.asn.au> References: <20090220055936.035255B1B@mail.bitblocks.com> <20090220235840.I46613@sola.nimnet.asn.au> <20090220205003.301AB5B3E@mail.bitblocks.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: net@freebsd.org Subject: Re: A more pliable firewall X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Feb 2009 04:09:45 -0000 On Fri, 20 Feb 2009, Bakul Shah wrote: > Thanks to everyone who responded. Looks like all the pieces > to do this exist. All I have to do is to package it all in > one program "sheriff" that watches various log files and > pulls the trigger on the bad guy(s) at appropriate time. Wild West imagery indeed :) > I think I will add a program to keep running stats on *all* > the tcp/udp senders to find all those annoyingly pesky repeat > senders who have no business talking to my network. Be prepared for a very, very large list! Maybe needing some sort of tree/trie or hashing algorithm to handle quickly as it grows. You'll also need some expiry mechanism after a period, as many if not most of these are transient scans from infected 'doze boxes, trojans du jour. And that after you've ignored the near-constant 'background radiation' from 'doze boxes to eg TCP dst-ports 135,139,445,1433 and others, and UDP dst-ports 135,137,138,1433,1434,1900 etc; no use chasing such more or less constant misconfigs, they'll only mask more interesting stuff. > What would be nice is a standard interface to report > suspicious failures (sort of like syslog). If the same guy > sends N DNS requests for the same thing and every request > fails, chances are he is a bad guy (or a zombie acting on > behalf of one). Perhaps some day a trusted network of such > daemons can be used to "back pressure" the closest ISP to the > sender -- who can then shut him down for a while. One note of caution: TCP is straightforward enough, the three-way handshake verifying the source address (if it proceeds to connection). However it's trivial to forge UDP source addresses, as the recent DNS amplification attacks I mentioned amply demonstrate. In such cases, the address appearing to be sending DNS requests logged as, say, "address#port query (cache) './NS/IN' denied" is the *victim* of such attacks, and blocking all access to/from such addresses, often nameservers of large ISPs, amounts to shooting yourself in the foot as well as further punishing the victim - the unknown attacker's intention! In that case it's sufficient to block 'from $victim to $me 53', still allowing $me to query their nameservers, eg to send them some mail :) good luck, Ian From owner-freebsd-net@FreeBSD.ORG Sat Feb 21 14:10: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 5B769106564A for ; Sat, 21 Feb 2009 14:10:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3E5788FC15 for ; Sat, 21 Feb 2009 14:10:02 +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 n1LEA24l029104 for ; Sat, 21 Feb 2009 14: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 n1LEA2Lu029103; Sat, 21 Feb 2009 14:10:02 GMT (envelope-from gnats) Date: Sat, 21 Feb 2009 14:10:02 GMT Message-Id: <200902211410.n1LEA2Lu029103@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Lucius Windschuh Cc: Subject: Re: kern/116837: [tun] [panic] [patch] ifconfig tunX destroy: panic X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Lucius Windschuh List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2009 14:10:02 -0000 The following reply was made to PR kern/116837; it has been noted by GNATS. From: Lucius Windschuh To: bug-followup@freebsd.org Cc: Subject: Re: kern/116837: [tun] [panic] [patch] ifconfig tunX destroy: panic Date: Sat, 21 Feb 2009 14:27:45 +0100 This is a follow-up to PR kern/116837. The described issue is solved, but now we have this issue. The following simple steps lead to a kernel panic on my system (i386, SMP, 8-CURRENT from Feb. 18th): -->8-- cat < /dev/tun0 > /dev/tun0 & ifconfig tun0 up ifconfig tun0 destroy & ifconfig tun0 destroy --8<-- Panic string: Bad link elm 0xc6437c00 prev->next != elm Responsible backtraces: Tracing pid 1610 tid 100114 td 0xc686f240 kdb_enter(c090abd7,c090abd7,c08e2418,eaefeb6c,0,...) at kdb_enter+0x3a panic(c08e2418,c6437c00,c091867f,d3,2d,...) at panic+0x136 if_clone_destroyif(c0976300,c6437c00,c091867f,bf,0,...) at if_clone_destroyif+0x8a if_clone_destroy(c724f320,19c,eaefebd4,c0604976,c1494788,...) at if_clone_destroy+0xa2 ifioctl(c7077dc8,80206979,c724f320,c686f240,80206979,...) at ifioctl+0x116 soo_ioctl(c71deaf0,80206979,c724f320,c722a000,c686f240,...) at soo_ioctl+0x397 kern_ioctl(c686f240,3,80206979,c724f320,64c3c0,...) at kern_ioctl+0x1dd ioctl(c686f240,eaefecf8,c,c,c09644b0,...) at ioctl+0x134 syscall(eaefed38) at syscall+0x2a3 Xint0x80_syscall() at Xint0x80_syscall+0x20 Tracing command ifconfig pid 1611 tid 100194 td 0xc6c9b000 sched_switch(c6c9b000,0,104,18d,5796c911,...) at sched_switch+0x437 mi_switch(104,0,c090edc3,1d2,0,...) at mi_switch+0x200 sleepq_switch(c6c9b000,0,c090edc3,247,c6c9b000,...) at sleepq_switch+0x15f sleepq_wait(c69aa850,0,c0918d9f,1,0,...) at sleepq_wait+0x63 _cv_wait_unlock(c69aa850,c69aa83c,c0918d76,102,c69aa800,...) at _cv_wait_unlock+0x1d4 tun_destroy(c09ca0d8,0,c0918d76,11c) at tun_destroy+0x49 tun_clone_destroy(c6437c00,c6437c00,c6437c00,c0976300,eb04eb88,...) at tun_clone_destroy+0xb8 ifc_simple_destroy(c0976300,c6437c00,c091867f,d5,2d,...) at ifc_simple_destroy+0x27 if_clone_destroyif(c0976300,c6437c00,c091867f,bf,0,...) at if_clone_destroyif+0xe1 if_clone_destroy(c677cb20,19c,eb04ebd4,c0604976,c1494788,...) at if_clone_destroy+0xa2 ifioctl(c7257620,80206979,c677cb20,c6c9b000,80206979,...) at ifioctl+0x116 soo_ioctl(c7285bd0,80206979,c677cb20,c722a000,c6c9b000,...) at soo_ioctl+0x397 kern_ioctl(c6c9b000,3,80206979,c677cb20,64c3c0,...) at kern_ioctl+0x1dd ioctl(c6c9b000,eb04ecf8,c,c,c09644b0,...) at ioctl+0x134 syscall(eb04ed38) at syscall+0x2a3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x281b4b83, esp = 0xbfbfe47c, ebp = 0xbfbfe498 --- OK, it's odd to destroy an interface two times in parallel. But it shouldn't crash the kernel. ;-) This panic is triggered reliably. To rule out side effects of my kernel config, I ran the same test with the GENERIC config and got the same result: panic. The textdump is available here: http://sites.google.com/site/lwfreebsd/Home/files/tun0-double-destroy.zip?attredirects=0 I can supply more information if needed. Kind regards, Lucius From owner-freebsd-net@FreeBSD.ORG Sat Feb 21 14:50: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 F3BFD1065670 for ; Sat, 21 Feb 2009 14:50:31 +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 CE0D08FC12 for ; Sat, 21 Feb 2009 14:50:31 +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 67BEC46B51; Sat, 21 Feb 2009 09:50:31 -0500 (EST) Date: Sat, 21 Feb 2009 14:50:31 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: dikshie In-Reply-To: <910e60e80902180150n41a592ffyb62ea53beb24f1ef@mail.gmail.com> Message-ID: References: <910e60e80902180150n41a592ffyb62ea53beb24f1ef@mail.gmail.com> 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: panic: _rw_wlock_hard X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Feb 2009 14:50:32 -0000 On Wed, 18 Feb 2009, dikshie wrote: > does anyone see this panic on -HEAD: > > panic: _rw_wlock_hard: recursing but non-recursive rw radix node head @ > /usr/src/sys/net/route.c:831 > > kdb_enter() at kdb_enter+0x3a > panic() at panic+0x136 > _rw_wlock_hard() at _rw_wlock_hard+0x66 > _rw_wlock() at _rw_wlock+0xae > rtquest1_fib() at rtquest1_fib+0x95 > rtquest_fib() at rtquest_fib+0x5e > in_rtquest() at in_rtquest+0x3b > in_rtqkill() at in_rtqkill+0x7f > rn_walktree() at rn_walktree+0x65 > in_rtqtimo() at in_rtqtimo+0xb0 > softclock() at softclock+0x24a > intr_event_execute_handlers() at intr_event_execute_handlers+0x125 > ithread_loop() at ithread_loop+0x9f > fork_exit() at fork_exit+0xb8 > fork_trampoline() at fork_trampoline+0x8 > > -HEAD built on Feb 16 14:26:25 JST. Something like the following may help -- build-tested but not not run-time tested: Index: in_rmx.c =================================================================== --- in_rmx.c (revision 186118) +++ in_rmx.c (working copy) @@ -230,6 +230,8 @@ struct rtentry *rt = (struct rtentry *)rn; int err; + RADIX_NODE_HEAD_WLOCK_ASSERT(ap->rnh); + if (rt->rt_flags & RTPRF_OURS) { ap->found++; @@ -240,7 +242,8 @@ err = in_rtrequest(RTM_DELETE, (struct sockaddr *)rt_key(rt), rt->rt_gateway, rt_mask(rt), - rt->rt_flags, 0, rt->rt_fibnum); + rt->rt_flags | RTF_RNH_LOCKED, 0, + rt->rt_fibnum); if (err) { log(LOG_WARNING, "in_rtqkill: error %d\n", err); } else { From owner-freebsd-net@FreeBSD.ORG Sat Feb 21 15:23:52 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 4F4231065688; Sat, 21 Feb 2009 15:23:52 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 24C068FC23; Sat, 21 Feb 2009 15:23:52 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from freefall.freebsd.org (rwatson@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n1LFNqZB088774; Sat, 21 Feb 2009 15:23:52 GMT (envelope-from rwatson@freefall.freebsd.org) Received: (from rwatson@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1LFNqtb088770; Sat, 21 Feb 2009 15:23:52 GMT (envelope-from rwatson) Date: Sat, 21 Feb 2009 15:23:52 GMT Message-Id: <200902211523.n1LFNqtb088770@freefall.freebsd.org> To: rwatson@FreeBSD.org, freebsd-net@FreeBSD.org, rwatson@FreeBSD.org From: rwatson@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, 21 Feb 2009 15:23:52 -0000 Synopsis: [kernel] [patch] Possible deadlock in rt_check() (sys/net/route.c) Responsible-Changed-From-To: freebsd-net->rwatson Responsible-Changed-By: rwatson Responsible-Changed-When: Sat Feb 21 15:22:13 UTC 2009 Responsible-Changed-Why: Grab ownership of this PR since I'm taking a look at deadlocks relating to routing in 7.x currently. http://www.freebsd.org/cgi/query-pr.cgi?pr=130652