From owner-freebsd-net@FreeBSD.ORG Sun Oct 12 14:32:43 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5189D106568A for ; Sun, 12 Oct 2008 14:32:43 +0000 (UTC) (envelope-from free.dvig@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.237]) by mx1.freebsd.org (Postfix) with ESMTP id 279B48FC1F for ; Sun, 12 Oct 2008 14:32:42 +0000 (UTC) (envelope-from free.dvig@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1139805rvf.43 for ; Sun, 12 Oct 2008 07:32:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=jZOyyAQVyprTizmCTML8XJcCylymgqLAk/oAJdJj0Ng=; b=iTO2yyC3dp1+576iqV5cmr3+m1FaMSaaUWbWouu1723u1GzSyTU9T/4j4zeARxx5Ws fZuj4Kpd/sGDcOvZqAKJkUlpsUera5/QHZUmVcip8lNJ0hOn9LHKYkH09KFmf7ePQfW/ o2SbH90dzKhRMWReP5cuT83kGR5vm4MNxyLz8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=Rrx2HSPIc3NJii4NP0bL6x2cHKdGcOWoZVyW1wiwftlJgeSJry2orX/wFIyUMPHFGI qfdKm30n1CKoSm3Txn2ICS+v6c0Rap6GGsYXMH5adfhT3tOlKYLg35SQBrqCKp6ocP8C fW3mN9oPTd3zcFdCdB7u5gaWuzFbiwDQGUoKo= Received: by 10.115.19.19 with SMTP id w19mr4160571wai.195.1223820383718; Sun, 12 Oct 2008 07:06:23 -0700 (PDT) Received: by 10.115.22.19 with HTTP; Sun, 12 Oct 2008 07:06:23 -0700 (PDT) Message-ID: <65f70ae30810120706k3580141dof58b86b13136d5df@mail.gmail.com> Date: Sun, 12 Oct 2008 20:06:23 +0600 From: "Aleksandr Litvinov" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Realtek network driver X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Oct 2008 14:32:43 -0000 Hi, Let's ask. Why in cvsweb existing a two drivers for network interface realtek: rl & re? They can be united? What objective reasons prevent to make? -- -- Good Luck. -- Litvinov Alexandr. From owner-freebsd-net@FreeBSD.ORG Sun Oct 12 15:06:18 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB2601065688 for ; Sun, 12 Oct 2008 15:06:18 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp02.sth.basefarm.net (ch-smtp02.sth.basefarm.net [80.76.149.213]) by mx1.freebsd.org (Postfix) with ESMTP id 75AB98FC0A for ; Sun, 12 Oct 2008 15:06:18 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from c83-255-48-78.bredband.comhem.se ([83.255.48.78]:50902 helo=falcon.midgard.homeip.net) by ch-smtp02.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1Kp2HS-0005Lx-9X for freebsd-net@freebsd.org; Sun, 12 Oct 2008 16:50:55 +0200 Received: (qmail 8007 invoked from network); 12 Oct 2008 16:50:41 +0200 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 12 Oct 2008 16:50:41 +0200 Received: (qmail 99733 invoked by uid 1001); 12 Oct 2008 16:50:41 +0200 Date: Sun, 12 Oct 2008 16:50:41 +0200 From: Erik Trulsson To: Aleksandr Litvinov Message-ID: <20081012145041.GA99667@owl.midgard.homeip.net> References: <65f70ae30810120706k3580141dof58b86b13136d5df@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <65f70ae30810120706k3580141dof58b86b13136d5df@mail.gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-Originating-IP: 83.255.48.78 X-Scan-Result: No virus found in message 1Kp2HS-0005Lx-9X. X-Scan-Signature: ch-smtp02.sth.basefarm.net 1Kp2HS-0005Lx-9X 110634995203cb51ea543ab2cf675221 Cc: freebsd-net@freebsd.org Subject: Re: Realtek network driver X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Oct 2008 15:06:18 -0000 On Sun, Oct 12, 2008 at 08:06:23PM +0600, Aleksandr Litvinov wrote: > Hi, > Let's ask. Why in cvsweb existing a two drivers for network interface > realtek: rl & re? They can be united? What objective reasons prevent > to make? Realtek makes many different ethernet controllers. The rl(4) driver supports several of the older chips (10/100M capable) while re(4) supports most of the newer models (mostly gigabit capable.) These two groups of controllers are different enough to warrant different drivers. Of course one could, in theory, unite the rl and re drivers, but they do not have enough in common for this to be a good idea. -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-net@FreeBSD.ORG Mon Oct 13 11:06:53 2008 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DABCF1065689 for ; Mon, 13 Oct 2008 11:06:53 +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 C46D78FC12 for ; Mon, 13 Oct 2008 11:06:53 +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 m9DB6rYR029506 for ; Mon, 13 Oct 2008 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id m9DB6reJ029502 for freebsd-net@FreeBSD.org; Mon, 13 Oct 2008 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 13 Oct 2008 11:06:53 GMT Message-Id: <200810131106.m9DB6reJ029502@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, 13 Oct 2008 11:06:54 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- 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/126984 net [carp][patch] add carp userland notifications via devc o kern/126945 net [carp] CARP interface destruction with ifconfig destro o kern/126924 net [an] [patch] printf -> device_printf and simplify prob o kern/126895 net [patch] [ral] Add antenna selection (marked as TBD) o kern/126874 net [vlan]: Zebra problem if ifconfig vlanX destroy o bin/126822 net wpa_supplicant(8): WPA PSK does not work in adhoc mode o kern/126714 net [carp] CARP interface renaming makes system no longer o kern/126695 net rtfree messages and network disruption upon use of if_ o kern/126688 net [ixgbe] [patch] 1.4.7 ixgbe driver panic with 4GB and f kern/126564 net [ath] doesn't work with my PCI-E X1 wireless network a o kern/126561 net [nlm] [patch] NLM (rpclockd) RPC UNLOCK failure (stall o kern/126475 net [ath] [panic] ath pcmcia card inevitably panics under o kern/126469 net [fxp] [panic] fxp(4) related kernel panic o kern/126339 net [ipw] ipw driver drops the connection o kern/126214 net [ath] txpower problem with Atheros wifi card o kern/126075 net [in] Network: internet control accesses beyond end of o bin/125922 net [patch] Deadlock in arp(8) o kern/125920 net [arp] Kernel Routing Table loses Ethernet Link status o kern/125845 net [netinet] [patch] tcp_lro_rx() should make use of hard o kern/125816 net [carp] [if_bridge] carp stuck in init when using bridg f kern/125502 net [ral] ifconfig ral0 scan produces no output unless in o kern/125258 net [socket] socket's SO_REUSEADDR option does not work o kern/125239 net [gre] kernel crash when using gre f kern/125195 net [fxp] fxp(4) driver failed to initialize device Intel o kern/125181 net [ndis] [patch] with wep enters kdb.enter.unknown, pani o kern/125079 net [ppp] host routes added by ppp with gateway flag (regr 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/124609 net [ipsec] [panic] ipsec 'remainder too big' panic with p 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 bin/124004 net ifconfig(8): Cannot assign both an IP and a MAC addres o kern/123968 net [rum] [panic] rum driver causes kernel panic with WPA. p kern/123961 net [vr] [patch] Allow vr interface to handle vlans o kern/123892 net [tap] [patch] No buffer space available o kern/123881 net [tcp] Turning on TCP blackholing causes slow localhost o kern/123858 net [stf] [patch] stf not usable behind a NAT o kern/123796 net [ipf] FreeBSD 6.1+VPN+ipnat+ipf: port mapping does not o bin/123633 net ifconfig(8) doesn't set inet and ether address in one o kern/123617 net [tcp] breaking connection when client downloading file o kern/123603 net [tcp] tcp_do_segment and Received duplicate SYN o kern/123559 net [iwi] iwi periodically disassociates/associates [regre o bin/123465 net [ip6] route(8): route add -inet6 -interfac o kern/123463 net [ipsec] [panic] repeatable crash related to ipsec-tool o kern/123429 net [nfe] [hang] "ifconfig nfe up" causes a hard system lo o kern/123347 net [bge] bge1: watchdog timeout -- linkstate changed to D o conf/123330 net [nsswitch.conf] Enabling samba wins in nsswitch.conf c o kern/123256 net [wpi] panic: blockable sleep lock with wpi(4) f kern/123200 net [netgraph] Server failure due to netgraph mpd and dhcp f kern/123172 net [bce] Watchdog timeout problems with if_bce o kern/123160 net [ip] Panic and reboot at sysctl kern.polling.enable=0 o kern/123066 net [ipsec] [panic] kernel trap with ipsec o kern/122989 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/122954 net [lagg] IPv6 EUI64 incorrectly chosen for lagg devices o kern/122928 net [em] interface watchdog timeouts and stops receiving p f kern/122839 net [multicast] FreeBSD 7 multicast routing problem p kern/122794 net [lagg] Kernel panic after brings lagg(8) up if NICs ar o kern/122780 net [lagg] tcpdump on lagg interface during high pps wedge o kern/122772 net [em] em0 taskq panic, tcp reassembly bug causes radix o kern/122743 net [panic] vm_page_unwire: invalid wire count: 0 o kern/122697 net [ath] Atheros card is not well supported o kern/122685 net It is not visible passing packets in tcpdump(1) o kern/122551 net [bge] Broadcom 5715S no carrier on HP BL460c blade usi o kern/122427 net [apm] [panic] apm and mDNSResponder cause panic during o kern/122319 net [wi] imposible to enable ad-hoc demo mode with Orinoco o kern/122290 net [netgraph] [panic] Netgraph related "kmem_map too smal f kern/122252 net [ipmi] [bge] IPMI problem with BCM5704 (does not work o kern/122195 net [ed] Alignment problems in if_ed o kern/122082 net [in_pcb] NULL pointer dereference in in_pcbdrop o kern/122068 net [ppp] ppp can not set the correct interface with pptpd o kern/122058 net [em] [panic] Panic on em1: taskq o kern/122033 net [ral] [lor] Lock order reversal in ral0 at bootup [reg o kern/121983 net [fxp] fxp0 MBUF and PAE o kern/121872 net [wpi] driver fails to attach on a fujitsu-siemens s711 s kern/121774 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/121706 net [netinet] [patch] "rtfree: 0xc4383870 has 1 refs" emit o kern/121624 net [em] [regression] Intel em WOL fails after upgrade to o kern/121555 net [panic] Fatal trap 12: current process = 12 (swi1: net o kern/121443 net [gif] LOR icmp6_input/nd6_lookup o kern/121437 net [vlan] Routing to layer-2 address does not work on VLA o kern/121298 net [em] [panic] Fatal trap 12: page fault while in kernel o kern/121257 net [tcp] TSO + natd -> slow outgoing tcp traffic o kern/121181 net [panic] Fatal trap 3: breakpoint instruction fault whi o kern/121080 net [bge] IPv6 NUD problem on multi address config on bge0 o kern/120966 net [rum] kernel panic with if_rum and WPA encryption p docs/120945 net [PATCH] ip6(4) man page lacks documentation for TCLASS o kern/120566 net [request]: ifconfig(8) make order of arguments more fr o kern/120304 net [netgraph] [patch] netgraph source assumes 32-bit time o kern/120266 net [panic] gnugk causes kernel panic when closing UDP soc o kern/120232 net [nfe] [patch] Bring in nfe(4) to RELENG_6 o kern/120130 net [carp] [panic] carp causes kernel panics in any conste o kern/119945 net [rum] [panic] rum device in hostap mode, cause kernel o kern/119791 net [nfs] UDP NFS mount of aliased IP addresses from a Sol o kern/119617 net [nfs] nfs error on wpa network when reseting/shutdown f kern/119516 net [ip6] [panic] _mtx_lock_sleep: recursed on non-recursi o kern/119432 net [arp] route add -host -iface causes arp e o kern/119361 net [bge] bge(4) transmit performance problem o kern/119345 net [ath] Unsuported Atheros 5424/2424 and CPU speedstep n o kern/119225 net [wi] 7.0-RC1 no carrier with Prism 2.5 wifi card [regr o bin/118987 net ifconfig(8): ifconfig -l (address_family) does not wor o kern/118880 net [ip6] IP_RECVDSTADDR & IP_SENDSRCADDR not implemented a kern/118879 net [bge] [patch] bge has checksum problems on the 5703 ch o kern/118727 net [netgraph] [patch] [request] add new ng_pf module o kern/117448 net [carp] 6.2 kernel crash [regression] o kern/117423 net [vlan] Duplicate IP on different interfaces o bin/117339 net [patch] route(8): loading routing management commands o kern/117271 net [tap] OpenVPN TAP uses 99% CPU on releng_6 when if_tap o kern/117043 net [em] Intel PWLA8492MT Dual-Port Network adapter EEPROM o kern/116837 net [tun] [panic] [patch] ifconfig tunX destroy: panic o kern/116747 net [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile o bin/116643 net [patch] [request] fstat(1): add INET/INET6 socket deta o kern/116328 net [bge]: Solid hang with bge interface o kern/116185 net [iwi] if_iwi driver leads system to reboot o kern/116077 net [ip] [patch] 6.2-STABLE panic during use of multi-cast o kern/115239 net [ipnat] panic with 'kmem_map too small' using ipnat o kern/114915 net [patch] [pcn] pcn (sys/pci/if_pcn.c) ethernet driver f o kern/114839 net [fxp] fxp looses ability to speak with traffic o kern/114714 net [gre][patch] gre(4) is not MPSAFE and does not support o kern/113842 net [ip6] PF_INET6 proto domain state can't be cleared wit o kern/112722 net [udp] IP v4 udp fragmented packet reject o kern/112686 net [patm] patm driver freezes System (FreeBSD 6.2-p4) i38 o bin/112557 net [patch] ppp(8) lock file should not use symlink name o kern/112528 net [nfs] NFS over TCP under load hangs with "impossible p o kern/109733 net [bge] bge link state issues [regression] o kern/109470 net [wi] Orinoco Classic Gold PC Card Can't Channel Hop o kern/109308 net [pppd] [panic] Multiple panics kernel ppp suspected [r o bin/108895 net pppd(8): PPPoE dead connections on 6.2 [regression] o kern/108542 net [bce]: Huge network latencies with 6.2-RELEASE / STABL o kern/107944 net [wi] [patch] Forget to unlock mutex-locks o conf/107035 net [patch] bridge interface given in rc.conf not taking a o kern/106438 net [ipf] ipfilter: keep state does not seem to allow repl o kern/106316 net [dummynet] dummynet with multipass ipfw drops packets s kern/105943 net Network stack may modify read-only mbuf chain copies o bin/105925 net problems with ifconfig(8) and vlan(4) [regression] o conf/102502 net [patch] ifconfig name does't rename netgraph node in n o kern/102035 net [plip] plip networking disables parallel port printing o kern/101948 net [ipf] [panic] Kernel Panic Trap No 12 Page Fault - cau o kern/100519 net [netisr] suggestion to fix suboptimal network polling o kern/98978 net [ipf] [patch] ipfilter drops OOW packets under 6.1-Rel o kern/95288 net [pppd] [tty] [panic] if_ppp panic in sys/kern/tty_subr o kern/95277 net [netinet] [patch] IP Encapsulation mask_match() return o kern/95267 net packet drops periodically appear o kern/93378 net [tcp] Slow data transfer in Postfix and Cyrus IMAP (wo f kern/92552 net A serious bug in most network drivers from 5.X to 6.X o kern/92090 net [bge] bge0: watchdog timeout -- resetting s kern/91777 net [ipf] [patch] wrong behaviour with skip rule inside an o kern/91594 net [em] FreeBSD > 5.4 w/ACPI fails to detect Intel Pro/10 o kern/87521 net [ipf] [panic] using ipfilter "auth" keyword leads to k s kern/86920 net [ndis] ifconfig: SIOCS80211: Invalid argument [regress o kern/86103 net [ipf] Illegal NAT Traversal in IPFilter s kern/81147 net [net] [patch] em0 reinitialization while adding aliase o kern/79895 net [ipf] 5.4-RC2 breaks ipfilter NAT when using netgraph o bin/79228 net [patch] extend arp(8) to be able to create blackhole r o kern/78090 net [ipf] ipf filtering on bridged packets doesn't work if p kern/77913 net [wi] [patch] Add the APDL-325 WLAN pccard to wi(4) o kern/77273 net [ipf] ipfilter breaks ipv6 statefull filtering on 5.3 s kern/77195 net [ipf] [patch] ipfilter ioctl SIOCGNATL does not match o kern/70904 net [ipf] ipfilter ipnat problem with h323 proxy support o kern/64556 net [sis] if_sis short cable fix problems with NetGear FA3 s kern/60293 net FreeBSD arp poison patch o kern/54383 net [nfs] [patch] NFS root configurations without dynamic s bin/41647 net ifconfig(8) doesn't accept lladdr along with inet addr s kern/39937 net ipstealth issue a kern/38554 net [patch] changing interface ipaddress doesn't seem to w o kern/35442 net [sis] [patch] Problem transmitting runts in if_sis dri o kern/34665 net [ipf] [hang] ipfilter rcmd proxy "hangs". o kern/27474 net [ipf] [ppp] Interactive use of user PPP and ipfilter c o conf/23063 net [PATCH] for static ARP tables in rc.network 185 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Oct 13 15:25:21 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 11E6A1065693 for ; Mon, 13 Oct 2008 15:25:21 +0000 (UTC) (envelope-from freebsd-net@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id C09AA8FC25 for ; Mon, 13 Oct 2008 15:25:20 +0000 (UTC) (envelope-from freebsd-net@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KpPIN-000223-Mk for freebsd-net@freebsd.org; Mon, 13 Oct 2008 15:25:19 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 13 Oct 2008 15:25:19 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 13 Oct 2008 15:25:19 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-net@freebsd.org From: Ivan Voras Date: Mon, 13 Oct 2008 17:26:04 +0200 Lines: 46 Message-ID: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig53B232959B3629782EC19C8E" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.17 (X11/20080925) X-Enigmail-Version: 0.95.0 Sender: news Subject: VLANs and hardware options X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Oct 2008 15:25:21 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig53B232959B3629782EC19C8E Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I have the following situation: bce0: flags=3D8802 metric 0 mtu 1500 options=3D1bb ether 00:14:5e:6d:2d:74 media: Ethernet autoselect (1000baseSX ) status: active vlan0: flags=3D8843 metric 0 mtu = 1500 options=3D3 ether 00:14:5e:b3:2a:38 inet xx.xx.xx.xx netmask 0xffffff00 broadcast xx.xx.xx.255 media: Ethernet autoselect (1000baseSX ) status: active vlan: 250 parent interface: bce1 e.g. the network card is directly on a trunked network, and I have the vlan interface with actual IP address. My question is: since this setup mixes various network&protocol layers, are the TSO capabilities of the card used? I guess not and that only RXCSUM & TXCSUM are used (for IP-level packets). --------------enig53B232959B3629782EC19C8E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFI82iMldnAQVacBcgRAoL6AKCOKwwVot9/3t9kK9kQ/brkRGW1XwCfcmUx W41cE83f9iyD9cHLLHg+rAk= =+gVa -----END PGP SIGNATURE----- --------------enig53B232959B3629782EC19C8E-- From owner-freebsd-net@FreeBSD.ORG Mon Oct 13 17:28:46 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB4B7106568A for ; Mon, 13 Oct 2008 17:28:46 +0000 (UTC) (envelope-from wawa@yandex-team.ru) Received: from cavolo.yandex.ru (cavolo.yandex.ru [87.250.244.45]) by mx1.freebsd.org (Postfix) with ESMTP id 37F268FC26 for ; Mon, 13 Oct 2008 17:28:45 +0000 (UTC) (envelope-from wawa@yandex-team.ru) Received: from [87.250.250.162] (dhcp250-162.yandex.ru [87.250.250.162]) by cavolo.yandex.ru (8.14.2/8.14.2) with ESMTP id m9DHFk7W022471 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Oct 2008 21:15:47 +0400 (MSD) (envelope-from wawa@yandex-team.ru) Message-ID: <48F38242.8020109@yandex-team.ru> Date: Mon, 13 Oct 2008 21:15:46 +0400 From: Vladimir Ivanov Organization: Yandex LLC User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: Stefan Lambrev References: <46B07931.3080300@yandex-team.ru> <2a41acea0708010923m7b21095ajc2ee84c37e0d5354@mail.gmail.com> <470280F6.9070009@yandex-team.ru> <20071003111737.U14276@delplex.bde.org> <47037246.2070400@yandex-team.ru> <47040D83.9010706@delphij.net> <47200537.8070708@room52.net> <472028C0.4040004@delphij.net> <47220853.90206@yandex-team.ru> <20071214113434.GD63588@uafug.org.ua> <4762796B.3090608@yandex-team.ru> <479B5C27.2010201@moneybookers.com> <479BC043.8020007@yandex-team.ru> <479CAF1F.4010900@moneybookers.com> In-Reply-To: <479CAF1F.4010900@moneybookers.com> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 8bit X-Antivirus: Dr.Web (R) for Mail Servers on cavolo.yandex.ru host X-Antivirus-Code: 100000 Cc: "freebsd-net@freebsd.org" Subject: Re: SMPable version of EM driver X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Oct 2008 17:28:46 -0000 Stefan Lambrev пишет: > Hi Vladimir, > [skip] > I'm unable to get this driver working under releng_7_0. It builds > without problems but panic my machine when I load it. > May be I'll wait until you have "official" version for FreeBSD 7.0 or > changes get merged into Intel's driver :) > We've published RELENG_7 revision at http://people.yandex-team.ru/~wawa/em-6.9.5-RELENG7-yandex-1.36.2.5.tar.gz WBR, -- Vladimir Ivanov Network Operations Center OOO "Yandex" t: +7 495 739-7000 f: +7 495 739-7070 @: noc@yandex.net (corporate) wawa@yandex-team.ru (personal) www: www.yandex.ru -- From owner-freebsd-net@FreeBSD.ORG Tue Oct 14 00:22:40 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D00C1065686 for ; Tue, 14 Oct 2008 00:22:40 +0000 (UTC) (envelope-from glen.j.barber@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.190]) by mx1.freebsd.org (Postfix) with ESMTP id 19D4A8FC1B for ; Tue, 14 Oct 2008 00:22:39 +0000 (UTC) (envelope-from glen.j.barber@gmail.com) Received: by mu-out-0910.google.com with SMTP id i2so1897573mue.3 for ; Mon, 13 Oct 2008 17:22:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=pv5OHo8S8wF0Wi/yyiMNvoM6bIecFjw9GhjfICxwuHY=; b=NizZqkfi84F3yKa0jAVWF27nJ877iDGibRZ/o+H+GJoS09o0yZNlRwkJdmzF96GCxz 0wwsSyxMho9csSIEsZM3xc5N4RUAJdJZAOn5J4Hp0jcQggpVwt2CK7zmEP9J6PF1DO+P mpxJzGhoc7zIaAcIMnMNlEcoZAPNtKRDcTlv4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=OB8FeDgYrR0flt4qfZw9nJpUcwsdearRXp3+YXs/rrGsaraZJnKxnmmg5KplRhFdaa BgL6nD+HVpoy0xeuotO9Cb00Su6rz1xcqhAqoV+rZcn57oFp/NkUkrIRpmxc/zEqex9V 10SqvMj2fRREYjW04yYBTMSPBw4nVA3wsSCPg= Received: by 10.187.166.12 with SMTP id t12mr1205487fao.38.1223943757636; Mon, 13 Oct 2008 17:22:37 -0700 (PDT) Received: by 10.187.194.10 with HTTP; Mon, 13 Oct 2008 17:22:37 -0700 (PDT) Message-ID: <4ad871310810131722p5dec24bco148ed703ca0f8870@mail.gmail.com> Date: Mon, 13 Oct 2008 20:22:37 -0400 From: "Glen Barber" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: ifconfig, wpa_supplicant, and hidden SSIDs X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Oct 2008 00:22:40 -0000 Hi everyone. I'm having an odd problem with wpa_supplicant and a hidden, unauthenticated access point. If I do 'ifconfig ndis0 scan', it brings up BSSIDs, but hidden names. I have desktopbsd-tools installed, so I tried accessing the AP using that, which I had to manually tell dbsd-nettray the SSID name for the AP in question. After doing so, I get 'Failed to connect', but '/etc/rc.d/netif restart ndis0' brings the interface back up, and reconnects. Now, to my real question: Where does SSID and AP MAC addresses get stored in the system? If I can manually (or script) the SSID name to the file, associated my MAC address of the access point, I can set this up via rc.local, and not need to load the dbsd-tools applet, which I cannot use anyway because of WPA at home. Thanks in advance. -- Glen Barber From owner-freebsd-net@FreeBSD.ORG Tue Oct 14 06:37:06 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65BB3106569B for ; Tue, 14 Oct 2008 06:37:06 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.229]) by mx1.freebsd.org (Postfix) with ESMTP id 2EFC68FC0C for ; Tue, 14 Oct 2008 06:37:05 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1841810rvf.43 for ; Mon, 13 Oct 2008 23:37:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=yumrfzR8LQ2Cy2Os6p+PsAMKfbuGXg80qWzRDw4Xbq0=; b=ZJQA0dglYUY7u1HUbZaiCx8tuHDlmWz5pvFWyAFuCuaO7hPRguN7O9bk11ys12J/kj SWpWeEuvhJcH66iFmJQxVvkdZwSRUNk6ktTEat/flKLHWxK2rfsHdywDCousGnCicEBi kKjW65EHfBhuanR+pqTl+IsQKhup2NUtqt7q0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=W6P1dLRCyU6IQ+oZWYvOxouZEQ0l3dhWteWOUedNqztf1hVdCvFvVVWlk7wF/ACu6+ oJzV8/SJL/MGr2WaCw6XDXl2zypSj+1vRvq6xoLVyaSjt/uONhcuGCvwN9YlD3HX5JVI cDvmFQcaj24Z9qL3bkkrYjmhi43VpHwYGjkiQ= Received: by 10.141.71.14 with SMTP id y14mr4564342rvk.24.1223966225722; Mon, 13 Oct 2008 23:37:05 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id g31sm2578573rvb.7.2008.10.13.23.37.02 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 13 Oct 2008 23:37:04 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m9E6Z4sd015937 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Oct 2008 15:35:04 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m9E6Z4ci015936; Tue, 14 Oct 2008 15:35:04 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 14 Oct 2008 15:35:04 +0900 From: Pyun YongHyeon To: Ivan Voras Message-ID: <20081014063504.GD14769@cdnetworks.co.kr> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org Subject: Re: VLANs and hardware options X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Oct 2008 06:37:06 -0000 On Mon, Oct 13, 2008 at 05:26:04PM +0200, Ivan Voras wrote: > I have the following situation: > > bce0: flags=8802 metric 0 mtu 1500 > options=1bb > ether 00:14:5e:6d:2d:74 > media: Ethernet autoselect (1000baseSX ) > status: active > > vlan0: flags=8843 metric 0 mtu 1500 > options=3 > ether 00:14:5e:b3:2a:38 > inet xx.xx.xx.xx netmask 0xffffff00 broadcast xx.xx.xx.255 > media: Ethernet autoselect (1000baseSX ) > status: active > vlan: 250 parent interface: bce1 > > e.g. the network card is directly on a trunked network, and I have the > vlan interface with actual IP address. My question is: since this setup > mixes various network&protocol layers, are the TSO capabilities of the > card used? I guess not and that only RXCSUM & TXCSUM are used (for > IP-level packets). > Correct. I believe almost all gigabit controllers can handle TSO with VLAN tagging. Unfortunately there is no official way to inform TSO capability of parent interface to VLAN layer in FreeBSD. Just adding a new flag to if_capabilities and minor patch to vlan(4) would make TSO work on vlan interface. But I haven't had time to implement this as my working environment does not involve VLANs. -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Tue Oct 14 21:20:58 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC04610656C5; Tue, 14 Oct 2008 21:20:58 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 80D0C8FC19; Tue, 14 Oct 2008 21:20:58 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (remko@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id m9ELKwef060423; Tue, 14 Oct 2008 21:20:58 GMT (envelope-from remko@freefall.freebsd.org) Received: (from remko@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id m9ELKwtq060419; Tue, 14 Oct 2008 21:20:58 GMT (envelope-from remko) Date: Tue, 14 Oct 2008 21:20:58 GMT Message-Id: <200810142120.m9ELKwtq060419@freefall.freebsd.org> To: remko@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: remko@FreeBSD.org Cc: Subject: Re: misc/128103: SiS 190 NIC not supported X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Oct 2008 21:20:58 -0000 Synopsis: SiS 190 NIC not supported Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: remko Responsible-Changed-When: Tue Oct 14 21:20:58 UTC 2008 Responsible-Changed-Why: Over to maintainer. http://www.freebsd.org/cgi/query-pr.cgi?pr=128103 From owner-freebsd-net@FreeBSD.ORG Wed Oct 15 01:47:58 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5310C106568F for ; Wed, 15 Oct 2008 01:47:58 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: from mail-gx0-f16.google.com (mail-gx0-f16.google.com [209.85.217.16]) by mx1.freebsd.org (Postfix) with ESMTP id E871A8FC26 for ; Wed, 15 Oct 2008 01:47:57 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: by gxk9 with SMTP id 9so5272284gxk.19 for ; Tue, 14 Oct 2008 18:47:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=z0Zd3M79KJjPv1D9U/xRu39aN/UO5aKf63ZO8AvVVs0=; b=RyFx5/KlHnUkwTLP/wLlSFLn5TC9U3AxtgiE5ZFbtxTG6AtpDWMnry8JTDBGf8G4PX MfDKsrdfkdyJvdXjetNwxrxr7R87HiO0ST5w/iFSOFQ+B8KfiKf8Oi55B1isujFZmBDI me/zqLcjjCVbEGetit4si2SbIGMuyjelgjiHg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=XoR1qwVuPpzLEB5vyTmKu64Nk6nYIzFI6BGpGS4XTKOY/EKRcnq/CneFqjUBczinVd U5K5RH0pA8GDU0aCmdhi4pnrWyUyeWix2z9IfLK/PKiaLy2M8pyHJA4obzkvRMJOyi8S jEMZUJ/WkyFA5g9VeLG4eoTjuFbbehcSDEmdA= Received: by 10.150.220.19 with SMTP id s19mr884579ybg.101.1224035276802; Tue, 14 Oct 2008 18:47:56 -0700 (PDT) Received: by 10.150.191.3 with HTTP; Tue, 14 Oct 2008 18:47:56 -0700 (PDT) Message-ID: Date: Wed, 15 Oct 2008 09:47:56 +0800 From: "Sepherosa Ziehau" To: "Bruce M. Simpson" In-Reply-To: <48F067EF.7010901@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <48EBB3D6.600@incunabulum.net> <48F067EF.7010901@FreeBSD.org> Cc: "freebsd-net@freebsd.org" Subject: Re: How to support an Ethernet PHY without ID registers? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Oct 2008 01:47:58 -0000 On Sat, Oct 11, 2008 at 4:46 PM, Bruce M. Simpson wrote: > Sepherosa Ziehau wrote: >> >> Are you sure you could read from BMSR? Return invalid value from BMSR >> is the usual cause of miibus attaching/probing failure. For ID1/ID2 >> reading, you could just fake some values in npe(4)'s miibus_readreg >> implementation. >> > > Thanks for the tip (from you and Pyun). I had to spoof the BMSR read to get > npe(4) to attach just to begin with. For whatever reason the chip doesn't > seem to respond on any of the PHY IDs which the Linux folk are using (5 and > 4 for npe0 (-B) and npe1 (-C) respectively). > > I noticed the ucLinux folk needed a similar patch to force driver attach > under Linux w/the IXP: > http://mailman.uclinux.org/pipermail/uclinux-dev/2005-March/031419.html > > The switch pretty much disappears after npe(4) attaches, I don't see any > activity lights or link lights at that point. This seems to happen after any > mii register access. > > If I frob things to allow rlswitch to attach, by using hints and hacking > if_npe.c, I can get dumps of the PHY register space, but it's all ones, > suggesting that it failed at xScale register level -- that would suggest the > PHY IDs are *wrong*, or something else isn't right. > > Pyun also suggested trying to manually take the PHYs out of power-down mode. > I tried that with a code snippet I sent him, but still no dice. I can't even > be sure that the PHYs are being addressed right. Realtek's 8211[BC] PHY has a "page selector" register (0x1f), BMSR and other GMII standard registers are in page0. Does the PHY you are working with has something like the "page selector"? Best Regards, sephe -- Live Free or Die From owner-freebsd-net@FreeBSD.ORG Thu Oct 16 04:25:36 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E563106568B for ; Thu, 16 Oct 2008 04:25:36 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id 4F7B78FC28 for ; Thu, 16 Oct 2008 04:25:36 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Subject:Message-ID:MIME-Version:Content-Type:Content-Disposition:Sender; b=X4ytdbrWJrJxqPbOtvendrX/iVh3B3HiEd/LZFWWFaCMZC8uz97fdvln5DbkBYBamc6qYtI1TQI8g5UPhnAKnFSDnb4S7qOnxhM6p9w/DeKS3i/G6uSvrZJuKHmOOaJ3a2wqSKYoKVh/6yl5d5jyzI91m5ZesDb1V5qUy3nh7xE=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1KqKQZ-0005j2-AY; Thu, 16 Oct 2008 08:25:35 +0400 Date: Thu, 16 Oct 2008 08:25:34 +0400 From: Eygene Ryabinkin To: freebsd-net@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GinsN7d7xEiEJaaA" Content-Disposition: inline Sender: rea-fbsd@codelabs.ru Cc: thompsa@freebsd.org Subject: Bridge interface as the vlan(4) parent X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Oct 2008 04:25:36 -0000 --GinsN7d7xEiEJaaA Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Andrew, *, good day. I had just came across the following situation: I have two VLAN-tagged links that are coming to my machine from two switches. I am running RSTP on the switches and need the machine to participate in the spanning tree formation (one switch is the root, another is the backup). Since RSTP messages are coming untagged, I need to make bridge on my physical interfaces, to enable spanning tree formation. And the bridge should be the parent device for the vlan(4) interfaces that will untag the packets. It is not possible just now to have bridge interface to be parent of vlan interface for two reasons: 1. vlan(4) won't attach to IFT_BRIDGE; this is rather easy to fix; 2. there should be a hook on the bridge path that will call vlan_input/ vlan_output; this is the harder problem, but I think that it isn't so hard, at least I have such impression after glancing at the code. Questions: may be I don't understand something and there is another way to create RSTP-aware bridge that will handle vlans? If my swithes will speak PVST, this will be easy -- one bridge per vlan instance and vlan(4) interfaces will be bridged. But I need RSTP. The second question: does anyone sees any problems apart from the mentioned two? May be I am wrong about the complexity of the second problem? Thanks! --=20 Eygene _ ___ _.--. # \`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard / ' ` , __.--' # to read the on-line manual =20 )/' _/ \ `-_, / # while single-stepping the kernel. `-'" `"\_ ,_.-;_.-\_ ', fsc/as # _.-'_./ {_.' ; / # -- FreeBSD Developers handbook=20 {_.-``-' {_/ # --GinsN7d7xEiEJaaA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkj2wj4ACgkQthUKNsbL7Yiw6wCfcoIgNsePLyFShrs0o/1iRknF 6GkAoIiniM3e3//OHLhARup0t41rFt7q =rRUz -----END PGP SIGNATURE----- --GinsN7d7xEiEJaaA-- From owner-freebsd-net@FreeBSD.ORG Thu Oct 16 13:10:08 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 271AE1065690 for ; Thu, 16 Oct 2008 13:10:08 +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 D6AA88FC23 for ; Thu, 16 Oct 2008 13:10: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 D9E0C41C66F for ; Thu, 16 Oct 2008 15:10:05 +0200 (CEST) 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 sFGLt-mAxz+A for ; Thu, 16 Oct 2008 15:10:05 +0200 (CEST) Received: by mail.cksoft.de (Postfix, from userid 66) id 90EB441C667; Thu, 16 Oct 2008 15:10:05 +0200 (CEST) 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 DAAA84449BC for ; Thu, 16 Oct 2008 13:05:16 +0000 (UTC) Date: Thu, 16 Oct 2008 13:05:16 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: freebsd-net@freebsd.org Message-ID: <20081016130318.J2978@maildrop.int.zabbadoz.net> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: [patch] src port randomization for inet6 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Oct 2008 13:10:08 -0000 Hi, so since the very early day of src port randomization ipv6 was missing that part while inet had it. Find a patch below. Please test, review and report back... http://people.freebsd.org/~bz/20081004-07-ipv6-randomport.diff /bz -- Bjoern A. Zeeb Stop bit received. Insert coin for new game. From owner-freebsd-net@FreeBSD.ORG Fri Oct 17 02:59:36 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D75B106568E for ; Fri, 17 Oct 2008 02:59:36 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mx1.freebsd.org (Postfix) with ESMTP id 7E5958FC20 for ; Fri, 17 Oct 2008 02:59:35 +0000 (UTC) (envelope-from max@love2party.net) Received: from vampire.homelinux.org (dslb-088-064-184-198.pools.arcor-ip.net [88.64.184.198]) by mrelayeu.kundenserver.de (node=mrelayeu0) with ESMTP (Nemesis) id 0MKwh2-1KqfYs074b-0006X0; Fri, 17 Oct 2008 04:59:34 +0200 Received: (qmail 41102 invoked from network); 17 Oct 2008 02:59:33 -0000 Received: from fbsd8.laiers.local (192.168.4.151) by ns1.laiers.local with SMTP; 17 Oct 2008 02:59:33 -0000 From: Max Laier Organization: FreeBSD To: freebsd-net@freebsd.org Date: Fri, 17 Oct 2008 04:59:32 +0200 User-Agent: KMail/1.10.1 (FreeBSD/8.0-CURRENT; KDE/4.1.1; i386; ; ) References: <20081016130318.J2978@maildrop.int.zabbadoz.net> In-Reply-To: <20081016130318.J2978@maildrop.int.zabbadoz.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200810170459.32822.max@love2party.net> X-Provags-ID: V01U2FsdGVkX197EihulsRFJD3CO9HIZ98hZXm9K1Aw/+tgcmj UdMVmf734hwlQGLEAMEptcek4IVHHV9ISl9n2Xx2CR2h2n8m/D imbRPPuzyPs0ELJ8Ydh6w== Cc: "Bjoern A. Zeeb" Subject: Re: [patch] src port randomization for inet6 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Oct 2008 02:59:36 -0000 On Thursday 16 October 2008 15:05:16 Bjoern A. Zeeb wrote: > so since the very early day of src port randomization ipv6 was missing > that part while inet had it. Find a patch below. > Please test, review and report back... > > http://people.freebsd.org/~bz/20081004-07-ipv6-randomport.diff looks good from a casual review. Which is to say that it is in line with the in_pcb.c version. However, I find the comment: /* * Simple check to ensure all ports are not used up causing * a deadlock here. */ a bit dangling and not really in line with the actual code. The same is true for the v4 version. -- /"\ 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 Oct 17 09:33:32 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB9B31065688 for ; Fri, 17 Oct 2008 09:33:32 +0000 (UTC) (envelope-from tdcmystere@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.180]) by mx1.freebsd.org (Postfix) with ESMTP id B17478FC23 for ; Fri, 17 Oct 2008 09:33:32 +0000 (UTC) (envelope-from tdcmystere@gmail.com) Received: by wa-out-1112.google.com with SMTP id n4so306883wag.27 for ; Fri, 17 Oct 2008 02:33:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=nzdrFJ8zMUWA1wzj2bkgQVGUb5v9755bkJRQ6F3UsVQ=; b=sV5CS+TltIjjlgIIU4oayTKQPqjnQt6jw+HliBNl1VaK2N51aNzNaypVZ2ZVEgXjUQ PJ1nuZVzAQ9cdNtC9KlD1OPbwLKY7JkFM3H4pajplYMQDmjBMV+AjCDUJ+T1FjL1hD4e QQPYadyGTJX+/2147ucdoGDoMsbHAeyimnHEY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=BZym8lWrGEISNScAEOjZm4ofl7ncnm9SB1pX/E+vT98sREp959GP+ZsAcCnrTrOtzb 9LoT2Sye28517lG50ZdPK30/HqKRAHucR1EE/D1B9cksEN6TdDOoff9u1RABCzRjkE/z 2BYlO4NCRRQlCk9UrC9yBXINZI7OUJLS/GdhA= Received: by 10.114.72.1 with SMTP id u1mr3187911waa.159.1224234749827; Fri, 17 Oct 2008 02:12:29 -0700 (PDT) Received: by 10.114.102.12 with HTTP; Fri, 17 Oct 2008 02:12:29 -0700 (PDT) Message-ID: Date: Fri, 17 Oct 2008 11:12:29 +0200 From: "Antipov Dima" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Network configuration for KVM X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Oct 2008 09:33:32 -0000 *English* Hi all sorry for my english i have little problem whis a network configuration for my freebsd used whi= s KVM so my probleme is simple ip of my host 91.121.156.206 ip oh my guest 91.121.234.115 from Gust i can ping any ip's but no domaines i can not ping my Guest from anywhere esolv.conf nameserver 231.186.33.99 domaine ovh.net search ovh.net on my host i have network interface wmbr0 so i add ip route add 91.121.234.115 (ip of my gust) dev vmbr0 on my guest i add a default route ip route add default 91.121.234.115 Thank you for all *French* bonjour a tous voila j ai jamais utilis=E9 freebsd et la j en ais besoin mon soucis j arrive a pinguer depuis le guest l exterieur et l interieur depuis host impossible pourtant la route est bien mise puis depuis guest je sais pinguer que les ip pas de domaines dans mon resolv.conf nameserver 231.186.33.99 domaine ovh.net je sais que il faut rajouter search ovh.net ou remplacer domaine par searc= h faut il faire encore qqch? et que dois je faire sur le host pour pinguer le gust? Merci d'avance From owner-freebsd-net@FreeBSD.ORG Fri Oct 17 14:04:12 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 245DD1065693; Fri, 17 Oct 2008 14:04:12 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id EC1328FC1F; Fri, 17 Oct 2008 14:04:11 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from freefall.freebsd.org (bz@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id m9HE4BIM007390; Fri, 17 Oct 2008 14:04:11 GMT (envelope-from bz@freefall.freebsd.org) Received: (from bz@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id m9HE4AFL007386; Fri, 17 Oct 2008 14:04:10 GMT (envelope-from bz) Date: Fri, 17 Oct 2008 14:04:10 GMT Message-Id: <200810171404.m9HE4AFL007386@freefall.freebsd.org> To: jeremie@le-hen.org, bz@FreeBSD.org, freebsd-net@FreeBSD.org From: bz@FreeBSD.org Cc: Subject: Re: bin/116643: [patch] [request] fstat(1): add INET/INET6 socket details as in NetBSD and OpenBSD X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Oct 2008 14:04:12 -0000 Synopsis: [patch] [request] fstat(1): add INET/INET6 socket details as in NetBSD and OpenBSD State-Changed-From-To: open->feedback State-Changed-By: bz State-Changed-When: Fri Oct 17 14:03:39 UTC 2008 State-Changed-Why: See what the submitetr thinks on staying with fstat and using sockstat. http://www.freebsd.org/cgi/query-pr.cgi?pr=116643 From owner-freebsd-net@FreeBSD.ORG Fri Oct 17 14:05:02 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9631D1065692; Fri, 17 Oct 2008 14:05:02 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6A5328FC1E; Fri, 17 Oct 2008 14:05:02 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from freefall.freebsd.org (bz@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id m9HE52dd007479; Fri, 17 Oct 2008 14:05:02 GMT (envelope-from bz@freefall.freebsd.org) Received: (from bz@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id m9HE52Ce007475; Fri, 17 Oct 2008 14:05:02 GMT (envelope-from bz) Date: Fri, 17 Oct 2008 14:05:02 GMT Message-Id: <200810171405.m9HE52Ce007475@freefall.freebsd.org> To: bz@FreeBSD.org, freebsd-net@FreeBSD.org, bz@FreeBSD.org From: bz@FreeBSD.org Cc: Subject: Re: bin/116643: [patch] [request] fstat(1): add INET/INET6 socket details as in NetBSD and OpenBSD X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Oct 2008 14:05:02 -0000 Synopsis: [patch] [request] fstat(1): add INET/INET6 socket details as in NetBSD and OpenBSD Responsible-Changed-From-To: freebsd-net->bz Responsible-Changed-By: bz Responsible-Changed-When: Fri Oct 17 14:04:47 UTC 2008 Responsible-Changed-Why: Assign to me for the follow-up. http://www.freebsd.org/cgi/query-pr.cgi?pr=116643 From owner-freebsd-net@FreeBSD.ORG Fri Oct 17 14:19:28 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CBDA106568E; Fri, 17 Oct 2008 14:19:28 +0000 (UTC) (envelope-from brooks@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E4A858FC18; Fri, 17 Oct 2008 14:19:27 +0000 (UTC) (envelope-from brooks@FreeBSD.org) Received: from freefall.freebsd.org (brooks@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id m9HEJRCX009740; Fri, 17 Oct 2008 14:19:27 GMT (envelope-from brooks@freefall.freebsd.org) Received: (from brooks@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id m9HEJRvB009736; Fri, 17 Oct 2008 14:19:27 GMT (envelope-from brooks) Date: Fri, 17 Oct 2008 14:19:27 GMT Message-Id: <200810171419.m9HEJRvB009736@freefall.freebsd.org> To: brooks@FreeBSD.org, freebsd-net@FreeBSD.org, thompsa@FreeBSD.org From: brooks@FreeBSD.org Cc: Subject: Re: kern/125181: [ndis] [patch] with wep enters kdb.enter.unknown, panics X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Oct 2008 14:19:28 -0000 Synopsis: [ndis] [patch] with wep enters kdb.enter.unknown, panics Responsible-Changed-From-To: freebsd-net->thompsa Responsible-Changed-By: brooks Responsible-Changed-When: Fri Oct 17 14:17:37 UTC 2008 Responsible-Changed-Why: thompsa seems to have insight into this problem to assign it to him for now. http://www.freebsd.org/cgi/query-pr.cgi?pr=125181 From owner-freebsd-net@FreeBSD.ORG Fri Oct 17 14:30:23 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29C2110656AC; Fri, 17 Oct 2008 14:30:23 +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 F0F3C8FC3B; Fri, 17 Oct 2008 14:30:22 +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 m9HEUMKA011730; Fri, 17 Oct 2008 14:30:22 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id m9HEUMvj011726; Fri, 17 Oct 2008 14:30:22 GMT (envelope-from gavin) Date: Fri, 17 Oct 2008 14:30:22 GMT Message-Id: <200810171430.m9HEUMvj011726@freefall.freebsd.org> To: marcinkk@gmail.com, gavin@FreeBSD.org, gavin@FreeBSD.org, freebsd-net@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: kern/128143: [rl] NIC Realtek 8139 doesn't work with RAM higher than 4GB X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Oct 2008 14:30:23 -0000 Synopsis: [rl] NIC Realtek 8139 doesn't work with RAM higher than 4GB State-Changed-From-To: feedback->open State-Changed-By: gavin State-Changed-When: Fri Oct 17 14:29:23 UTC 2008 State-Changed-Why: Submitter has tested patch but it makes no difference. Responsible-Changed-From-To: gavin->freebsd-net Responsible-Changed-By: gavin Responsible-Changed-When: Fri Oct 17 14:29:23 UTC 2008 Responsible-Changed-Why: Over to maintainers http://www.freebsd.org/cgi/query-pr.cgi?pr=128143 From owner-freebsd-net@FreeBSD.ORG Fri Oct 17 16:18:13 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B09A1065689; Fri, 17 Oct 2008 16:18:13 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1F6FD8FC17; Fri, 17 Oct 2008 16:18:13 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id m9HGIDpZ021344; Fri, 17 Oct 2008 16:18:13 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id m9HGICrK021340; Fri, 17 Oct 2008 16:18:12 GMT (envelope-from vwe) Date: Fri, 17 Oct 2008 16:18:12 GMT Message-Id: <200810171618.m9HGICrK021340@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-net@FreeBSD.org, vwe@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/128103: [feature request] [patch] new SiS 190 NIC driver X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2008 16:18:13 -0000 Synopsis: [feature request] [patch] new SiS 190 NIC driver Responsible-Changed-From-To: freebsd-net->vwe Responsible-Changed-By: vwe Responsible-Changed-When: Fri Oct 17 16:17:38 UTC 2008 Responsible-Changed-Why: grab - will create a clean patchset as I think this shouldn't be a new driver at all. http://www.freebsd.org/cgi/query-pr.cgi?pr=128103 From owner-freebsd-net@FreeBSD.ORG Sat Oct 18 00:58:47 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 35FA71065688 for ; Sat, 18 Oct 2008 00:58:47 +0000 (UTC) (envelope-from gene@nttmcl.com) Received: from mx0.nttmcl.com (MX0.nttmcl.com [216.69.68.201]) by mx1.freebsd.org (Postfix) with ESMTP id 1FA4A8FC0A for ; Sat, 18 Oct 2008 00:58:47 +0000 (UTC) (envelope-from gene@nttmcl.com) Received: from localhost (localhost [127.0.0.1]) by mx0.nttmcl.com (Postfix) with ESMTP id 4E82C800411 for ; Fri, 17 Oct 2008 17:39:47 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at mx0.nttmcl.com Received: from mx0.nttmcl.com ([127.0.0.1]) by localhost (mx0.nttmcl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O+7tXKm1ynOA for ; Fri, 17 Oct 2008 17:39:47 -0700 (PDT) Received: from [216.69.69.190] (dhcp190.nttmcl.com [216.69.69.190]) by mx0.nttmcl.com (Postfix) with ESMTP id 37D7C80040A for ; Fri, 17 Oct 2008 17:39:47 -0700 (PDT) Message-ID: <48F93051.6040808@nttmcl.com> Date: Fri, 17 Oct 2008 17:39:45 -0700 From: "Eugene M. Kim" User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Closing connection from an accept_filter(9) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Oct 2008 00:58:47 -0000 Hello, Is it possible to close a connection from an accept filter, for example, in order to prevent an incoming connection with a malformed request body from ever reaching the userland? Cheers, Eugene From owner-freebsd-net@FreeBSD.ORG Sat Oct 18 01:22:21 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0DA8C1065687 for ; Sat, 18 Oct 2008 01:22:21 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id F31EC8FC14 for ; Sat, 18 Oct 2008 01:22:20 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id BF9C01A3C37; Fri, 17 Oct 2008 18:04:52 -0700 (PDT) Date: Fri, 17 Oct 2008 18:04:52 -0700 From: Alfred Perlstein To: "Eugene M. Kim" Message-ID: <20081018010452.GC5651@elvis.mu.org> References: <48F93051.6040808@nttmcl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48F93051.6040808@nttmcl.com> User-Agent: Mutt/1.4.2.3i Cc: net@freebsd.org Subject: Re: Closing connection from an accept_filter(9) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Oct 2008 01:22:21 -0000 * Eugene M. Kim [081017 17:58] wrote: > Hello, > > Is it possible to close a connection from an accept filter, for example, > in order to prevent an incoming connection with a malformed request body > from ever reaching the userland? Probably, look at what happens inside of syncache or syncookies to sockets that are on accept queue but not yet "accepted". -Alfred > > Cheers, > Eugene > > _______________________________________________ > 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" -- - Alfred Perlstein From owner-freebsd-net@FreeBSD.ORG Sat Oct 18 08:15:10 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CC4D106568E; Sat, 18 Oct 2008 08:15:10 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E71D48FC37; Sat, 18 Oct 2008 08:15:09 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (remko@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id m9I8F9uM038149; Sat, 18 Oct 2008 08:15:09 GMT (envelope-from remko@freefall.freebsd.org) Received: (from remko@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id m9I8F9h6038145; Sat, 18 Oct 2008 08:15:09 GMT (envelope-from remko) Date: Sat, 18 Oct 2008 08:15:09 GMT Message-Id: <200810180815.m9I8F9h6038145@freefall.freebsd.org> To: remko@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: remko@FreeBSD.org Cc: Subject: Re: kern/128181: [fxp]: Unread portion of the kernel message buffer X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Oct 2008 08:15:10 -0000 Old Synopsis: Unread portion of the kernel message buffer New Synopsis: [fxp]: Unread portion of the kernel message buffer Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: remko Responsible-Changed-When: Sat Oct 18 08:14:54 UTC 2008 Responsible-Changed-Why: reassign to -net http://www.freebsd.org/cgi/query-pr.cgi?pr=128181 From owner-freebsd-net@FreeBSD.ORG Sat Oct 18 09:25:46 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28A031065696 for ; Sat, 18 Oct 2008 09:25:46 +0000 (UTC) (envelope-from ddesimone@verio.net) Received: from relay2-bcrtfl2.verio.net (relay2-bcrtfl2.verio.net [131.103.218.177]) by mx1.freebsd.org (Postfix) with ESMTP id E6CDF8FC12 for ; Sat, 18 Oct 2008 09:25:45 +0000 (UTC) (envelope-from ddesimone@verio.net) Received: from iad-wprd-xchw01.corp.verio.net (iad-wprd-xchw01.corp.verio.net [198.87.7.164]) by relay2-bcrtfl2.verio.net (Postfix) with ESMTP id ABD651FF00F2 for ; Sat, 18 Oct 2008 05:03:57 -0400 (EDT) Thread-Index: AckxAHQR5UNtcApHTdqW7CwmC9qkhA== Received: from limbo.int.dllstx01.us.it.verio.net ([10.10.10.11]) by iad-wprd-xchw01.corp.verio.net with Microsoft SMTPSVC(6.0.3790.1830); Sat, 18 Oct 2008 05:03:57 -0400 Received: by limbo.int.dllstx01.us.it.verio.net (Postfix, from userid 1000) id A2E3D8E29B; Sat, 18 Oct 2008 04:03:51 -0500 (CDT) Date: Sat, 18 Oct 2008 04:03:51 -0500 From: "David DeSimone" To: Content-Transfer-Encoding: 7bit Message-ID: <20081018090351.GA29876@verio.net> Mail-Followup-To: freebsd-net@freebsd.org References: <48F93051.6040808@nttmcl.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline Content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.3168 Importance: normal Priority: normal In-Reply-To: <48F93051.6040808@nttmcl.com> Precedence: bulk User-Agent: Mutt/1.5.9i X-OriginalArrivalTime: 18 Oct 2008 09:03:57.0320 (UTC) FILETIME=[7407D080:01C93100] Subject: Re: Closing connection from an accept_filter(9) 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: Sat, 18 Oct 2008 09:25:46 -0000 Eugene M. Kim wrote: > > Is it possible to close a connection from an accept filter, for > example, in order to prevent an incoming connection with a malformed > request body from ever reaching the userland? How would you propose to find out what is in the request body without first accepting the connection? -- David DeSimone == Network Admin == fox@verio.net "I don't like spinach, and I'm glad I don't, because if I liked it I'd eat it, and I just hate it." -- Clarence Darrow This email message is intended for the use of the person to whom it has been sent, and may contain information that is confidential or legally protected. If you are not the intended recipient or have received this message in error, you are not authorized to copy, distribute, or otherwise use this message or its attachments. Please notify the sender immediately by return e-mail and permanently delete this message and any attachments. Verio, Inc. makes no warranty that this email is error or virus free. Thank you. From owner-freebsd-net@FreeBSD.ORG Sat Oct 18 09:51:40 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 217AF1065692 for ; Sat, 18 Oct 2008 09:51:40 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id 7774B8FC0A for ; Sat, 18 Oct 2008 09:51:38 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id m9I9O6LX093510 for ; Sat, 18 Oct 2008 17:24:06 +0800 (KRAST) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id m9I9O5A1093509 for net@freebsd.org; Sat, 18 Oct 2008 17:24:05 +0800 (KRAST) (envelope-from eugen) Date: Sat, 18 Oct 2008 17:24:05 +0800 From: Eugene Grosbein To: net@freebsd.org Message-ID: <20081018092405.GA91929@svzserv.kemerovo.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: SNMP High Capacity Counters X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Oct 2008 09:51:40 -0000 Hi! I've just found that ports/net-snmp (version 5.4) built WITH_MFD_REWRITES=yes supports IF-MIB, and in theory should show 64-bit ifHC* counters but it does not. It seems agent/mibgroup/if-mib/data_access/interface_sysctl.c that obtains interface statistics from the kernel. The function netsnmp_arch_interface_container_load() has the following code: /* get counters */ entry->stats.ibytes.low = ifp->ifm_data.ifi_ibytes; entry->stats.ibytes.high = 0; entry->stats.iucast.low = ifp->ifm_data.ifi_ipackets; entry->stats.iucast.high = 0; entry->stats.imcast.low = ifp->ifm_data.ifi_imcasts; entry->stats.imcast.high = 0; So, it always produce 32-bit quantities. My question is: does FreeBSD/i386 kernel maintain 64-bit counters for interface statictics these days? If yes, since what version? Eugene Grosbein From owner-freebsd-net@FreeBSD.ORG Sat Oct 18 16:55:59 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AFA171065695; Sat, 18 Oct 2008 16:55:59 +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 864358FC1E; Sat, 18 Oct 2008 16:55:59 +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 m9IGtxbm089121; Sat, 18 Oct 2008 16:55:59 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id m9IGtxWk089117; Sat, 18 Oct 2008 16:55:59 GMT (envelope-from gavin) Date: Sat, 18 Oct 2008 16:55:59 GMT Message-Id: <200810181655.m9IGtxWk089117@freefall.freebsd.org> To: gavin@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: conf/128030: [request] Isn't it time to enable IPsec in GENERIC? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Oct 2008 16:55:59 -0000 Synopsis: [request] Isn't it time to enable IPsec in GENERIC? Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: gavin Responsible-Changed-When: Sat Oct 18 16:55:14 UTC 2008 Responsible-Changed-Why: Over to maintainer(s) for consideration http://www.freebsd.org/cgi/query-pr.cgi?pr=128030 From owner-freebsd-net@FreeBSD.ORG Sat Oct 18 17:05:27 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E6A71065687 for ; Sat, 18 Oct 2008 17:05:27 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 6A5AE8FC0C for ; Sat, 18 Oct 2008 17:05:27 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m9IH5Rgb060040 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 18 Oct 2008 10:05:27 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <48FA1756.1080708@freebsd.org> Date: Sat, 18 Oct 2008 10:05:26 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <200810181655.m9IGtxWk089117@freefall.freebsd.org> In-Reply-To: <200810181655.m9IGtxWk089117@freefall.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Subject: Re: conf/128030: [request] Isn't it time to enable IPsec in GENERIC? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Oct 2008 17:05:27 -0000 gavin@freebsd.org wrote: > Synopsis: [request] Isn't it time to enable IPsec in GENERIC? > > Responsible-Changed-From-To: freebsd-bugs->freebsd-net > Responsible-Changed-By: gavin > Responsible-Changed-When: Sat Oct 18 16:55:14 UTC 2008 > Responsible-Changed-Why: > Over to maintainer(s) for consideration > > http://www.freebsd.org/cgi/query-pr.cgi?pr=128030 > Last I checked IPSEC added noticeable overhead. Before anyone does this you need to measure the cost of having it enabled but not used. Sam From owner-freebsd-net@FreeBSD.ORG Sat Oct 18 17:32:10 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 540451065686 for ; Sat, 18 Oct 2008 17:32:10 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from smtp-1.dlr.de (smtp-1.dlr.de [195.37.61.185]) by mx1.freebsd.org (Postfix) with ESMTP id E14AA8FC1B for ; Sat, 18 Oct 2008 17:32:09 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from [129.247.12.15] ([129.247.12.15]) by smtp-1.dlr.de with Microsoft SMTPSVC(6.0.3790.1830); Sat, 18 Oct 2008 19:18:51 +0200 Message-ID: <48FA1A7C.5060801@dlr.de> Date: Sat, 18 Oct 2008 19:18:52 +0200 From: Hartmut Brandt Organization: German Aerospace Center User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: Eugene Grosbein References: <20081018092405.GA91929@svzserv.kemerovo.su> In-Reply-To: <20081018092405.GA91929@svzserv.kemerovo.su> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 18 Oct 2008 17:18:51.0802 (UTC) FILETIME=[97522FA0:01C93145] Cc: net@freebsd.org Subject: Re: SNMP High Capacity Counters X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Oct 2008 17:32:10 -0000 Eugene Grosbein wrote: > Hi! > > I've just found that ports/net-snmp (version 5.4) built > WITH_MFD_REWRITES=yes supports IF-MIB, and in theory should show 64-bit > ifHC* counters but it does not. > > It seems agent/mibgroup/if-mib/data_access/interface_sysctl.c that obtains > interface statistics from the kernel. > The function netsnmp_arch_interface_container_load() has the following code: > > /* get counters */ > entry->stats.ibytes.low = ifp->ifm_data.ifi_ibytes; > entry->stats.ibytes.high = 0; > entry->stats.iucast.low = ifp->ifm_data.ifi_ipackets; > entry->stats.iucast.high = 0; > entry->stats.imcast.low = ifp->ifm_data.ifi_imcasts; > entry->stats.imcast.high = 0; > > So, it always produce 32-bit quantities. My question is: > does FreeBSD/i386 kernel maintain 64-bit counters for interface statictics > these days? If yes, since what version? It does not, because not all architectures have atomic 64-bit increments and adds. Implementing 64-bit counters on these architectures would require some kind of locking. This was discussed in the past. You might look at the IF-MIB implementation of bsnmp (it is in the base system). It uses periodic polling to detect wraps of the 32-bit counters. The poll interval is tuned to the fastest interface in the system (given that all interfaces reported the correct speed). Note, that the netsnmp implementation is plain wrong - if the daemon does not support the HC counters it should never pretend to do. This is explicitely stated somewhere in the RFCs. harti From owner-freebsd-net@FreeBSD.ORG Sat Oct 18 18:18:18 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22F9B1065691 for ; Sat, 18 Oct 2008 18:18:18 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mx1.freebsd.org (Postfix) with ESMTP id A62A08FC17 for ; Sat, 18 Oct 2008 18:18:17 +0000 (UTC) (envelope-from max@love2party.net) Received: from vampire.homelinux.org (dslb-088-066-023-129.pools.arcor-ip.net [88.66.23.129]) by mrelayeu.kundenserver.de (node=mrelayeu4) with ESMTP (Nemesis) id 0ML21M-1KrGNT1B9U-00021i; Sat, 18 Oct 2008 20:18:15 +0200 Received: (qmail 68792 invoked from network); 18 Oct 2008 18:18:14 -0000 Received: from fbsd8.laiers.local (192.168.4.151) by laiers.local with SMTP; 18 Oct 2008 18:18:14 -0000 From: Max Laier Organization: FreeBSD To: freebsd-net@freebsd.org Date: Sat, 18 Oct 2008 20:18:13 +0200 User-Agent: KMail/1.10.1 (FreeBSD/8.0-CURRENT; KDE/4.1.1; i386; ; ) References: <200810181655.m9IGtxWk089117@freefall.freebsd.org> <48FA1756.1080708@freebsd.org> In-Reply-To: <48FA1756.1080708@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200810182018.13757.max@love2party.net> X-Provags-ID: V01U2FsdGVkX18PTPgXQgrGIsmjQ1ikClmdrnZ9Uj6fUkTuzrU OdxzcF43Y49D/WCY57uJ5fSqXoBSBvj2tlTTeGRon8nQqUH760 KNNa78+YRSPewxJRIMc8g== Cc: freebsd-hackers@freebsd.org Subject: Re: conf/128030: [request] Isn't it time to enable IPsec in GENERIC? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Oct 2008 18:18:18 -0000 On Saturday 18 October 2008 19:05:26 Sam Leffler wrote: > gavin@freebsd.org wrote: > > Synopsis: [request] Isn't it time to enable IPsec in GENERIC? > > > > Responsible-Changed-From-To: freebsd-bugs->freebsd-net > > Responsible-Changed-By: gavin > > Responsible-Changed-When: Sat Oct 18 16:55:14 UTC 2008 > > Responsible-Changed-Why: > > Over to maintainer(s) for consideration > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=128030 > > Last I checked IPSEC added noticeable overhead. Before anyone does this > you need to measure the cost of having it enabled but not used. It should be possible to turn IPSEC into a module - maybe only loadable on boot to avoid locking issues. This would reduce the overhead to a handful of function pointer checks that should not impact performance (thanks to modern branch prediction and cache sizes). This would have to be measured as well, of course. Maybe this should go to the project page? It's a good junior kernel hacker project, I believe. -- /"\ 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 Sat Oct 18 18:41:49 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A84E1065690 for ; Sat, 18 Oct 2008 18:41:49 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id 847EE8FC17 for ; Sat, 18 Oct 2008 18:41:47 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id m9IIffsc073033; Sun, 19 Oct 2008 02:41:41 +0800 (KRAST) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id m9IIfees073032; Sun, 19 Oct 2008 02:41:40 +0800 (KRAST) (envelope-from eugen) Date: Sun, 19 Oct 2008 02:41:40 +0800 From: Eugene Grosbein To: Hartmut Brandt Message-ID: <20081018184140.GA71679@svzserv.kemerovo.su> References: <20081018092405.GA91929@svzserv.kemerovo.su> <48FA1A7C.5060801@dlr.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48FA1A7C.5060801@dlr.de> User-Agent: Mutt/1.4.2.3i Cc: net@freebsd.org Subject: Re: SNMP High Capacity Counters X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Oct 2008 18:41:49 -0000 On Sat, Oct 18, 2008 at 07:18:52PM +0200, Hartmut Brandt wrote: > >I've just found that ports/net-snmp (version 5.4) built > >WITH_MFD_REWRITES=yes supports IF-MIB, and in theory should show 64-bit > >ifHC* counters but it does not. > > > >It seems agent/mibgroup/if-mib/data_access/interface_sysctl.c that obtains > >interface statistics from the kernel. > >The function netsnmp_arch_interface_container_load() has the following > >code: > > > > /* get counters */ > > entry->stats.ibytes.low = ifp->ifm_data.ifi_ibytes; > > entry->stats.ibytes.high = 0; > > entry->stats.iucast.low = ifp->ifm_data.ifi_ipackets; > > entry->stats.iucast.high = 0; > > entry->stats.imcast.low = ifp->ifm_data.ifi_imcasts; > > entry->stats.imcast.high = 0; > > > >So, it always produce 32-bit quantities. My question is: > >does FreeBSD/i386 kernel maintain 64-bit counters for interface statictics > >these days? If yes, since what version? > It does not, because not all architectures have atomic 64-bit increments > and adds. Implementing 64-bit counters on these architectures would > require some kind of locking. This was discussed in the past. Yes, I've read archives and saw a discussion dated 2002 or 2003. Some time has passed since than, generic CPU horsepower has changed. And I'm sure IPFW maintains 64-bit counters for FreeBSD/i386 without a problem. Yes, IPFW is additional feature and needs to be enables explicitly. I run it since 2.2.8 in every kernel and had no problems with (lots of) its 64-bit counters. Would (optionally) having another pack of them hurt? I've read someone made a path for 64-bit statictics counters in 2002. > You might look at the IF-MIB implementation of bsnmp (it is in the base > system). It uses periodic polling to detect wraps of the 32-bit > counters. The poll interval is tuned to the fastest interface in the > system (given that all interfaces reported the correct speed). > > Note, that the netsnmp implementation is plain wrong - if the daemon > does not support the HC counters it should never pretend to do. This is > explicitely stated somewhere in the RFCs. It does really support them for Linux and Solaris. They seem to have solved this problem somehow. It would be very nice to have, say, kernel option to enable the support. Just like options IPFIREWALL. Eugene Grosbein From owner-freebsd-net@FreeBSD.ORG Sat Oct 18 20:25:24 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79C4A106568C for ; Sat, 18 Oct 2008 20:25:24 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 4DD2B8FC14 for ; Sat, 18 Oct 2008 20:25:24 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m9IKPNWE060744 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 18 Oct 2008 13:25:23 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <48FA4633.9090500@freebsd.org> Date: Sat, 18 Oct 2008 13:25:23 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: Max Laier References: <200810181655.m9IGtxWk089117@freefall.freebsd.org> <48FA1756.1080708@freebsd.org> <200810182018.13757.max@love2party.net> In-Reply-To: <200810182018.13757.max@love2party.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: freebsd-net@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: conf/128030: [request] Isn't it time to enable IPsec in GENERIC? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Oct 2008 20:25:24 -0000 Max Laier wrote: > On Saturday 18 October 2008 19:05:26 Sam Leffler wrote: > >> gavin@freebsd.org wrote: >> >>> Synopsis: [request] Isn't it time to enable IPsec in GENERIC? >>> >>> Responsible-Changed-From-To: freebsd-bugs->freebsd-net >>> Responsible-Changed-By: gavin >>> Responsible-Changed-When: Sat Oct 18 16:55:14 UTC 2008 >>> Responsible-Changed-Why: >>> Over to maintainer(s) for consideration >>> >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=128030 >>> >> Last I checked IPSEC added noticeable overhead. Before anyone does this >> you need to measure the cost of having it enabled but not used. >> > > It should be possible to turn IPSEC into a module - maybe only loadable on > boot to avoid locking issues. This would reduce the overhead to a handful of > function pointer checks that should not impact performance (thanks to modern > branch prediction and cache sizes). This would have to be measured as well, > of course. Maybe this should go to the project page? It's a good junior > kernel hacker project, I believe. > > I believe the most important issue are the SADB checks in the tx path. It used to be possible to do them cheaply by checking a single ptr value but now it's much more expensive. My memory is hazy as it's been a while. Sam From owner-freebsd-net@FreeBSD.ORG Sat Oct 18 22:38:05 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F082A106568C for ; Sat, 18 Oct 2008 22:38:05 +0000 (UTC) (envelope-from sandiegobiker@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.229]) by mx1.freebsd.org (Postfix) with ESMTP id C6A4B8FC18 for ; Sat, 18 Oct 2008 22:38:05 +0000 (UTC) (envelope-from sandiegobiker@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1032955rvf.43 for ; Sat, 18 Oct 2008 15:38:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=OmN92IPLSaKraSkwdk84BNm8vs4peCuwVWFpBE7vkNQ=; b=tsTKxDhpAKYIqI47gIV0yGxPsRMudoBtuPVFenXgxWnnPmg99e38ZiyQs9uGIEZZg7 ML8y2udPGqipwYmyLunPx/X4pIhkfqbHJz0Y1DGPYUaz+hflKySx5Hp9nycAI3T7ixab 7zIuW97HQcK0L6AgpeQpVpnoi7Bo9t8re3U5A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=EyqRVAfXydY8g/ZJJgv2GjfDXAGGYN+jndjX6jm1EJqtFLRh2vTH9fqzjvTuSlVyw4 y3BHydbPTsZaljxGiBakoEHUUeRxgZfb9eKFlqeM5jP7o3Z6Galrd9aMzUB1LcDn5/ET 61k8IUMTigf6ry3xlDmvbwTBBDMDNmmHG6ET8= Received: by 10.141.29.18 with SMTP id g18mr3566760rvj.298.1224367938363; Sat, 18 Oct 2008 15:12:18 -0700 (PDT) Received: by 10.141.37.19 with HTTP; Sat, 18 Oct 2008 15:12:18 -0700 (PDT) Message-ID: <27cb3ada0810181512qeab4020g912096848212ad86@mail.gmail.com> Date: Sat, 18 Oct 2008 15:12:18 -0700 From: "Len Gross" To: "freebsd-net@freebsd.org" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Timers in drivers vs userland X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Oct 2008 22:38:06 -0000 If I place a timer directly in a driver (like Ethernet) will it be subject to less jitter and more consistency than if it were in Userland? I know FreeBSD is not "real time," but I need to be able to run a polling algorithm with about 1 ms accuracy. Thanks in advance. (Please tell me if there is a better list for this question.) -- Len