From owner-freebsd-net@FreeBSD.ORG Sun Jan 28 02:23:55 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A2AAC16A403 for ; Sun, 28 Jan 2007 02:23:55 +0000 (UTC) (envelope-from antinvidia@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.177]) by mx1.freebsd.org (Postfix) with ESMTP id 6241B13C49D for ; Sun, 28 Jan 2007 02:23:55 +0000 (UTC) (envelope-from antinvidia@gmail.com) Received: by py-out-1112.google.com with SMTP id f47so571621pye for ; Sat, 27 Jan 2007 18:23:52 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=m9DT7NdpmOLrjcZ5VLrMD8tpVxJX+GcYDyQNPx62ZlZCXldL6CU9XYSuo2nJkivYogeEhPnI0efc02cTgexwHhPWNcL0sVtiWr52JvGN7/eBT8quIylzpmejfHGh7IJP6PL2jkwTBf09g6HdyaQBTtJA4GKnafHkt2KeLVFjpLA= Received: by 10.35.74.1 with SMTP id b1mr9848911pyl.1169951032702; Sat, 27 Jan 2007 18:23:52 -0800 (PST) Received: by 10.35.58.13 with HTTP; Sat, 27 Jan 2007 18:23:52 -0800 (PST) Message-ID: Date: Sun, 28 Jan 2007 02:23:52 +0000 From: MQ To: Wishmaster In-Reply-To: <194684269.20070127175157@velnet.ru> MIME-Version: 1.0 References: <1458229821.20070120234257@velnet.ru> <45B28F37.7040100@delphij.net> <1651695163.20070122010957@velnet.ru> <45B4BE90.20602@qwirky.net> <1582899958.20070126014728@velnet.ru> <194684269.20070127175157@velnet.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re: Re[4]: reproducible watchdog timeout in bge X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Jan 2007 02:23:55 -0000 2007/1/27, Wishmaster : > > Hello MQ, > > Saturday, January 27, 2007, 5:31:49 PM, you wrote: > > M> I have two boxes with onboard bge, one using 5780, the other > M> 5701. Neither of them has your problem. I think there may be some > M> problems with your software or hardware configuration. > > > I don't think so. I have two different motherboards and two > different freebsd distributions on them (6.1/amd64 and 6.2/i386). On both > motherboards there > are bcm5721 onboard network chips and both configurations have the > same issue. > > Can you tell me do you have smp kernel? > > p.s. On both machines I have clear installation of freebsd. i.e. > there is nothing except SMP in my kernel. > -- > Best regards, > Wishmaster mailto:wishmaster@velnet.ru > > > _______________________________________________ > 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" > One of my boxes is dual Opteron 250 with dual 5780 onboard, SMP kernel. The other is HP NC6000 with 5701, GENERIC kernel. Perhaps 5721 has some big differences from other chips. From owner-freebsd-net@FreeBSD.ORG Mon Jan 29 10:40:26 2007 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B354316A400 for ; Mon, 29 Jan 2007 10:40:26 +0000 (UTC) (envelope-from nvass@teledomenet.gr) Received: from arwen.teledomenet.gr (arwen.teledomenet.gr [213.142.128.58]) by mx1.freebsd.org (Postfix) with ESMTP id 3E45A13C471 for ; Mon, 29 Jan 2007 10:40:25 +0000 (UTC) (envelope-from nvass@teledomenet.gr) Received: from iris ([192.168.1.71]) by arwen.teledomenet.gr (8.12.10/8.12.10) with ESMTP id l0TAeJm1008498; Mon, 29 Jan 2007 12:40:19 +0200 From: Nikos Vassiliadis To: Alexander Motin Date: Mon, 29 Jan 2007 12:43:35 +0200 User-Agent: KMail/1.9.1 References: <1169850194.00677461.1169839202@10.7.7.3> <45BABDE2.4010503@alkar.net> In-Reply-To: <45BABDE2.4010503@alkar.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200701291243.36380.nvass@teledomenet.gr> Cc: net@freebsd.org Subject: Re: ng_pptpgre problems: tcp connections reset unexpectedly X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Jan 2007 10:40:26 -0000 On Saturday 27 January 2007 04:50, Alexander Motin wrote: > Hi. > > Nikos Vassiliadis wrote: > > It seems that tcp connections over pptp reset unexpectedly. I have > > tried several things such as connecting from a FBSD-4 to a FBSD-6, > > connecting from a FBSD-[46] to a Cisco router(*). There are times which > > the client box gets from the other peer an echo-request msg, which is > > not supposed to happen while downloading. Perhaps it's relevant to > > this: > > > > (*) the result is always the same. > > > > What i have not tried, is a newer mpd, Alexander Motin seems to > > maintain mpd very actively, he sends a patch every 5 minutes or so:) > > I am using at the moment 6.2-PRE, just a few days before RELEASE, > > and mpd-3.18_4. > > Actually I have spent so much time working on mpd4 that I dont like to > even hear about some problems in ancient mpd3. :) There so much work was > done in mpd4 that it is mostly pointless to debug something in mpd3. Perfect points, it would be very unfair to ask you such a thing. I use mpd3 cause it's what was available in ports at the time of the installation. I already have an mpd4 installation working, but had some problems using pptp with it. I will try again with the RC you just released. > > > Could you please help? any workarounds, tunables, suggestions? > > It's my connection to the internet and from time to time I need > > to download something bigger than a few megs... > > I do not use pptp actively, to say for sure, but you can try to play > with such pptp options like delayed-ack, always-ack and windowing. 1) > delayed-ack enable > always-ack disable > windowing enable failed 2) > delayed-ack enable > always-ack enable > windowing enable failed 3) > delayed-ack disable > always-ack enable > windowing enable failed 4) > delayed-ack disable > always-ack enable > windowing disable seem to work, sometimes it's not that easy to reproduce the problem. > > > Thanks in advance, Nikos > > > > root:2:~/tst1# fetch ftp://ftp2.de.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/6.2/6.2-RELEASE-i386-disc1.iso; date > > 6.2-RELEASE-i386-disc1.iso 3% of 573 MB 185 kBps 50m56s > > fetch: transfer timed out > > fetch: 6.2-RELEASE-i386-disc1.iso appears to be truncated: 20702208/601229312 bytes > > Fri Jan 26 11:31:40 EET 2007 > > > tcpdump.ng0: > > 11:31:40.797285 IP 134.76.12.3.56123 > 213.142.137.253.64016: . 20695333:20696745(1412) ack 1 win 5792 > > 11:31:40.797294 IP 213.142.137.253.64016 > 134.76.12.3.56123: . ack 20696745 win 32476 > > 11:31:40.797697 IP 134.76.12.3.56123 > 213.142.137.253.64016: . 20696745:20698157(1412) ack 1 win 5792 > > 11:31:40.797780 IP 213.142.137.253.64016 > 134.76.12.3.56123: . ack 20698157 win 33182 > > 11:31:40.798589 IP 134.76.12.3.56123 > 213.142.137.253.64016: . 20698157:20699569(1412) ack 1 win 5792 > > 11:31:40.798739 IP 134.76.12.3.56123 > 213.142.137.253.64016: . 20699569:20700981(1412) ack 1 win 5792 > > 11:31:40.798748 IP 213.142.137.253.64016 > 134.76.12.3.56123: . ack 20700981 win 32476 > > 11:31:40.798877 IP 134.76.12.3.56123 > 213.142.137.253.64016: . 20700981:20702393(1412) ack 1 win 5792 > > 11:31:40.798924 IP 213.142.137.253.64016 > 134.76.12.3.56123: . ack 20702393 win 33182 > > 11:31:40.859025 IP 213.142.137.253.64016 > 134.76.12.3.56123: R 1:1(0) ack 20702393 win 33182 > > 11:31:40.887739 IP 134.76.12.3.56123 > 213.142.137.253.64016: . 20702393:20703805(1412) ack 1 win 5792 > > 11:31:40.887859 IP 134.76.12.3.56123 > 213.142.137.253.64016: P 20703805:20705217(1412) ack 1 win 5792 > > 11:31:40.888005 IP 134.76.12.3.56123 > 213.142.137.253.64016: . 20705217:20706629(1412) ack 1 win 5792 > > Looking here I can see that it is your local machine (213.142.137.253) > sent "R" - Reset request just after normal acknowledge packet. I don't > see the reason for such it's behaviour. To complicate things a bit more sftp over the same the link works reliably (different sockopts?). http fails, ftp fails but sftp works as usual. Eventually a read(2) fails: 1794 fetch CALL read(0x3,0x8057730,0xd0) 1794 fetch RET read -1 errno 60 Operation timed out > Is it the same machine where fetch and tcpdump running? Yes. > Wasn't there some kind of time synchronization or NAT restart or some other external event? There is no NAT involved. But i had the feeling that routers load is relevant. That's because there was no problem when some of the clients where moved to a second router and the router I am conne- cting to became less loaded. I also have to add that the router is two hops away, and I think the reliability of the link is quite good. It seems to work with disabled windowing. If you are interested in tracking down this, I would be glad to help. Thanks, Nikos From owner-freebsd-net@FreeBSD.ORG Mon Jan 29 11:08:39 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B3EC016A568 for ; Mon, 29 Jan 2007 11:08:39 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id A27A813C4A7 for ; Mon, 29 Jan 2007 11:08:39 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l0TB8dkp042124 for ; Mon, 29 Jan 2007 11:08:39 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l0TB8cu9042120 for freebsd-net@FreeBSD.org; Mon, 29 Jan 2007 11:08:38 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 29 Jan 2007 11:08:38 GMT Message-Id: <200701291108.l0TB8cu9042120@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Jan 2007 11:08:39 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- a kern/38554 net changing interface ipaddress doesn't seem to work s kern/39937 net ipstealth issue o kern/92552 net A serious bug in most network drivers from 5.X to 6.X s kern/95665 net [if_tun] "ping: sendto: No buffer space available" wit o kern/106722 net [net] [patch] ifconfig may not connect an interface to 5 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s kern/19875 net A new protocol family, PF_IPOPTION, to handle IP optio o conf/23063 net [PATCH] for static ARP tables in rc.network s bin/41647 net ifconfig(8) doesn't accept lladdr along with inet addr o kern/54383 net [nfs] [patch] NFS root configurations without dynamic s kern/60293 net FreeBSD arp poison patch o kern/95267 net packet drops periodically appear f kern/95277 net [netinet] IP Encapsulation mask_match() returns wrong o kern/102035 net [plip] plip networking disables parallel port printing o conf/102502 net [patch] ifconfig name does't rename netgraph node in n o kern/106999 net [netgraph] [patch] ng_ksocket fails to clear multicast 10 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Jan 29 05:36:04 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8A23D16A400 for ; Mon, 29 Jan 2007 05:36:04 +0000 (UTC) (envelope-from aronesimi@yahoo.com) Received: from web58605.mail.re3.yahoo.com (web58605.mail.re3.yahoo.com [68.142.236.203]) by mx1.freebsd.org (Postfix) with SMTP id 50CE513C442 for ; Mon, 29 Jan 2007 05:36:04 +0000 (UTC) (envelope-from aronesimi@yahoo.com) Received: (qmail 66545 invoked by uid 60001); 29 Jan 2007 05:09:22 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=vduOhf/SImFOcPKt0o3l9ePlOA9ABG8pjnMukDnOLkh/UecCEb24B9GIuqIlhwWtur18GBn2gh1/7Q7pJcAvTSRDr+vgC/mj647fcneTMIZ35CIQg5UC2n4FiuAVA7gUCeN1zgL3vKtTKYQy2ZBY4AbZc4/dI1BiiQRWns/xqRU=; Received: from [75.72.230.91] by web58605.mail.re3.yahoo.com via HTTP; Sun, 28 Jan 2007 21:09:22 PST Date: Sun, 28 Jan 2007 21:09:22 -0800 (PST) From: Arone Silimantia To: freebsd-net@freebsd.org MIME-Version: 1.0 Message-ID: <464814.62688.qm@web58605.mail.re3.yahoo.com> X-Mailman-Approved-At: Mon, 29 Jan 2007 12:26:33 +0000 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ipfw pipe show ... help with output is needed, please. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Jan 2007 05:36:04 -0000 I set up a dummynet pipe with this sequence of commands: sysctl -w net.inet.ip.fw.one_pass=0 ipfw pipe 1 config bw 16Mbit/s ipfw add 10000 pipe 1 all from any to any So far so good. Works great. However, when I look at the pipe itself, with this command: ipfw pipe show 1 I see this: # ipfw pipe show 1 00001: 16.000 Mbit/s 0 ms 50 sl. 1 queues (1 buckets) droptail mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000 BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes Pkt/Byte Drp 0 tcp 1.2.3.4/22 1.2.3.4/4333 2970975653 2649647615805 2 2992 10414733 I would like to clarify a few things... First, the ipfw pipe creation command I ran is not (as far as I can tell) TCP specific, and further, my ipfw rule says "any to any" - but when I look at the pipe, it has a protocol specified (TCP) and further, has a port number (22). I want to throttle ALL IP traffic, not just TCP, and certainly not just port 22. What am I doing wrong ? Second, there are seven headings (from BKT at the left to Drp on the right) but underneath those seven headings are _9_ values. What I really want to know is how many packets I am droppinig ... but I can't tell which of the fields are the "dropped" - I assume it is the final number .. if so, what is that measured in ? Packets ? Finally, why am I dropping any packets ? My total traffic is 5-7 Mbits/s on average ... I don't see why I would be dropping any packets at all ... are they being dropped because the system can't keep up, or are they being dropped because I am hitting the throttle limit and it drops everything above that ? Many thanks. --------------------------------- Finding fabulous fares is fun. Let Yahoo! FareChase search your favorite travel sites to find flight and hotel bargains. --------------------------------- Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out. From owner-freebsd-net@FreeBSD.ORG Mon Jan 29 13:18:07 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9C6B616A404 for ; Mon, 29 Jan 2007 13:18:07 +0000 (UTC) (envelope-from spadge@fromley.net) Received: from queue02-winn.ispmail.ntl.com (queue02-winn.ispmail.ntl.com [81.103.221.56]) by mx1.freebsd.org (Postfix) with ESMTP id 077A113C478 for ; Mon, 29 Jan 2007 13:18:02 +0000 (UTC) (envelope-from spadge@fromley.net) Received: from aamtaout04-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout03-winn.ispmail.ntl.com with ESMTP id <20070129125536.RRWA1865.mtaout03-winn.ispmail.ntl.com@aamtaout04-winn.ispmail.ntl.com>; Mon, 29 Jan 2007 12:55:36 +0000 Received: from tobermory.home ([86.0.163.117]) by aamtaout04-winn.ispmail.ntl.com with ESMTP id <20070129125536.NNRM29112.aamtaout04-winn.ispmail.ntl.com@tobermory.home>; Mon, 29 Jan 2007 12:55:36 +0000 Received: from webmail.fromley.net (localhost.home [127.0.0.1]) by tobermory.home (Postfix) with ESMTP id C10C1A6CDD; Mon, 29 Jan 2007 12:55:29 +0000 (GMT) Received: from 213.123.179.188 (SquirrelMail authenticated user spadge) by webmail.fromley.net with HTTP; Mon, 29 Jan 2007 12:55:29 -0000 (UTC) Message-ID: <33457.213.123.179.188.1170075329.squirrel@webmail.fromley.net> In-Reply-To: <464814.62688.qm@web58605.mail.re3.yahoo.com> References: <464814.62688.qm@web58605.mail.re3.yahoo.com> Date: Mon, 29 Jan 2007 12:55:29 -0000 (UTC) From: "Spadge Fromley" To: "Arone Silimantia" User-Agent: SquirrelMail/1.4.9a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-net@freebsd.org Subject: Re: ipfw pipe show ... help with output is needed, please. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Jan 2007 13:18:07 -0000 > > I see this: > > # ipfw pipe show 1 > 00001: 16.000 Mbit/s 0 ms 50 sl. 1 queues (1 buckets) droptail > mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000 > BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes > Pkt/Byte Drp > 0 tcp 1.2.3.4/22 1.2.3.4/4333 2970975653 2649647615805 2 > 2992 10414733 > Second, there are seven headings (from BKT at the left to Drp on the > right) but underneath those seven headings are _9_ values. What I really > want to know is how many packets I am droppinig ... but I can't tell which > of the fields are the "dropped" - I assume it is the final number .. if > so, what is that measured in ? Packets ? I can't help you with the rest of it, as I am frequently just as baffled by ipfw/dummynet as the next man .. But the 7/9 thing I can explain. Tot_pkt: 2970975653 bytes: 2649647615805 Pkt: 2 Byte: 2992 Ideally, there'd be a '/' between pkts and bytes, like there is in the headers. Does it make a difference if you set up the ipfw rule before the dummynet one? Here's how I have mine: root@tobermory# ipfw list | grep pipe 01400 pipe 101 ip from any to any uid DLMonkey via fxp0 in 01500 pipe 102 ip from any to any uid DLMonkey via fxp0 out taken from: root@tobermory# grep pipe /etc/rc.firewall /sbin/ipfw -f pipe flush /sbin/ipfw add pipe 101 ip from any to any uid DLMonkey via $WAN in /sbin/ipfw add pipe 102 ip from any to any uid DLMonkey via $WAN out /sbin/ipfw pipe 101 config delay 100ms /sbin/ipfw pipe 102 config delay 100ms Gives the following info: root@tobermory# ipfw pipe list 00102: unlimited 100 ms 50 sl. 1 queues (1 buckets) droptail mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000 BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes Pkt/Byte Drp 0 tcp {my.ip.address}/61676 59.127.165.138/4662 6557083 758428752 0 0 0 00101: unlimited 100 ms 50 sl. 1 queues (1 buckets) droptail mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000 BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes Pkt/Byte Drp 0 udp 67.163.25.202/7871 {my.ip.address}/14298 8466595 1174764649 0 0 0 Trust me: there will be a lot more connections set up in those pipes than that. I think it's just showing a snapshot. Or I have got it all completely wrong and it's not actually working at all like I thought it ought. Who knows? :) -- Spadge 'Intoccabile' From owner-freebsd-net@FreeBSD.ORG Mon Jan 29 13:33:34 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2CE6716A406; Mon, 29 Jan 2007 13:33:34 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from av8-1-sn3.vrr.skanova.net (av8-1-sn3.vrr.skanova.net [81.228.9.183]) by mx1.freebsd.org (Postfix) with ESMTP id AD58A13C4C3; Mon, 29 Jan 2007 13:33:33 +0000 (UTC) (envelope-from johan@stromnet.se) Received: by av8-1-sn3.vrr.skanova.net (Postfix, from userid 502) id BC65D38049; Mon, 29 Jan 2007 14:00:44 +0100 (CET) Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net [81.228.9.101]) by av8-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 92B1837FDF; Mon, 29 Jan 2007 14:00:44 +0100 (CET) Received: from elfi.stromnet.se (90-224-172-102-no129.tbcn.telia.com [90.224.172.102]) by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 7055937E47; Mon, 29 Jan 2007 14:00:44 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by elfi.stromnet.se (Postfix) with ESMTP id E3C9A61E49; Mon, 29 Jan 2007 14:00:43 +0100 (CET) X-Virus-Scanned: amavisd-new at stromnet.se Received: from elfi.stromnet.se ([127.0.0.1]) by localhost (elfi.stromnet.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cy-4uthEzEqm; Mon, 29 Jan 2007 14:00:43 +0100 (CET) Received: from [IPv6:2001:16d8:ff20:1:217:f2ff:fef0:d6b7] (unknown [IPv6:2001:16d8:ff20:1:217:f2ff:fef0:d6b7]) by elfi.stromnet.se (Postfix) with ESMTP id 5E49061E48; Mon, 29 Jan 2007 14:00:43 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <16425E76-4111-4DE3-970D-A5E1E29EA194@stromnet.se> Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?Johan_Str=F6m?= Date: Mon, 29 Jan 2007 14:00:06 +0100 To: freebsd-net@freebsd.org, freebsd-hardware@freebsd.org X-Mailer: Apple Mail (2.752.3) Cc: wpaul@freebsd.org Subject: Support for 3C996-SX? Or 3C985(b)-SX? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Jan 2007 13:33:34 -0000 Hi I'm about to buy a PCI 1000-SX network card, looking on eBay I've =20 found both 3C996-SX and 3C985(b)-SX cards. Looking at http://www.freebsd.org/releases/6.2R/hardware-=20 i386.html#ETHERNET I can find "3Com 3c996-T (10/100/1000baseTX)", but =20= not the SX? However, on http://www.freebsd.org/releases/5.0R/hardware-=20 i386.html#ETHERNET I can see "3Com 3c996-SX, 3c996-T". So, has the -SX support been removed or something? =46rom the if_bge.c changelog (http://www.freebsd.org/cgi/cvsweb.cgi/=20= src/sys/dev/bge/if_bge.c) I found this: Commit message by wpaul > Lastly, teach the driver how to recognize a 3c996B-SX by checking > the hardware config word in the EEPROM in order to detect the media. > We attach 5701 fiber cards correctly now, but I haven't verified that > they send/receive packets yet since I don't have a second fiber > interface at home. (I know that fiber 5700 cards work, so I'm > keeping my fingers crossed.) But this is from 4 years ago so.. not pretty recent and no followup =20 in the log. So, is it supported or not? :) Also i found some 3c985(b) cards on eBay, a bit more expensive ($10 =20 or so..), but this uses the ti driver instead of bge. And from what I =20= can see this driver does not support ALTQ. However, im not quite sure =20= i will need it anyway, since I will runt VLAN interface ontop of the =20 device (and both bge and ti supports vlan), and vlan does not support =20= altq anyway (which is kind of boring, any plans for it?) So, any suggestions? Which card should I choose? Or some other =20 popular card in the same price range (ebay price range that is..)? Thanks! Johan Str=F6m Stromnet johan@stromnet.se http://www.stromnet.se/ From owner-freebsd-net@FreeBSD.ORG Mon Jan 29 15:35:58 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B1E7216A405 for ; Mon, 29 Jan 2007 15:35:58 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.freebsd.org (Postfix) with ESMTP id 2262513C49D for ; Mon, 29 Jan 2007 15:35:57 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.4/8.13.3) with ESMTP id l0TF2teH038733 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Jan 2007 18:02:56 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.4/8.13.1/Submit) id l0TF2tuX038732; Mon, 29 Jan 2007 18:02:55 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Mon, 29 Jan 2007 18:02:55 +0300 From: Gleb Smirnoff To: Ask Bj?rn Hansen Message-ID: <20070129150255.GU7922@FreeBSD.org> Mail-Followup-To: Gleb Smirnoff , Ask Bj?rn Hansen , freebsd-net@freebsd.org, freebsd-stable@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Cc: freebsd-net@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: CARP + VLAN = kernel dump X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Jan 2007 15:35:58 -0000 On Thu, Dec 14, 2006 at 07:05:04PM -0800, Ask Bj?rn Hansen wrote: A> Hi, A> A> If I enable carp on a vlan interface in rc.conf the kernel goes A> boom. This is 6.2-RC from a couple of weeks ago. (IIRC then I had A> the same problem setting up carp on a bridge'd interface). A> A> I'm configuring it like this: A> A> ifconfig_vlan2="inet 10.50.0.3/24 vlan 202 vlandev sis2" A> ifconfig_carp2="vhid 3 advskew 200 pass awe4jkfha4jkfha4f 10.50.0.1" A> A> cloned_interfaces="... carp2 ... vlan2" A> A> However, if I do the carp2 setup "manually" after the system is A> booted, it is working fine. A> A> ifconfig carp2 vhid 3 advskew 200 pass hjarefhakjewfha 10.50.0.1 A> A> Any ideas? A> A> (kernel dump below) A> A> - ask A> A> A> fault virtual address = 0x100005c A> fault code = supervisor read, page not present A> instruction pointer = 0x20:0xc05ba533 A> stack pointer = 0x28:0xc7975c30 A> frame pointer = 0x28:0xc7975c90 A> code segment = base 0x0, limit 0xfffff, type 0x1b A> = DPL 0, pres 1, def32 1, gran 1 A> processor eflags = interrupt enabled, resume, IOPL = 0 A> current process = 13 (swi1: net) A> trap number = 12 A> panic: page fault A> Uptime: 17s A> Cannot dump. No dump device defined. Can you please configure dump device, obtain kernel dump, and print the backtrace from it? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-net@FreeBSD.ORG Mon Jan 29 17:26:41 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A095816A400 for ; Mon, 29 Jan 2007 17:26:41 +0000 (UTC) (envelope-from mav@alkar.net) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 2C7F513C48D for ; Mon, 29 Jan 2007 17:26:40 +0000 (UTC) (envelope-from mav@alkar.net) Received: from [212.86.226.11] (account mav@alkar.net [212.86.226.11] verified) by cmail.optima.ua (CommuniGate Pro SMTP 5.0.11) with ESMTPA id 20270231; Mon, 29 Jan 2007 18:26:39 +0200 Message-ID: <45BE203E.3070409@alkar.net> Date: Mon, 29 Jan 2007 18:26:38 +0200 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8b) Gecko/20051108 MIME-Version: 1.0 To: FreeBSD Net , mpd-users@lists.sourceforge.net Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: mpd-4.0rc1 released X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Jan 2007 17:26:41 -0000 Hi. After long period of development I am glad to present you a first candidate to the long waited and at last coming soon release of Mpd-4.0! Next 2-3 weeks will be spent for testing and bug fixing, to make first release of new brunch production stable in all possible ways. We will be graceful for any bug reports you can submit. Most significant features added in a last few months: - complete IPv6 support, - L2TP, TCP and UDP link types (re)implemented, - NAT, - WEB interface, - Deflate and Predictor-1 traffic compression, - DES traffic encryption, - HUGE amount of bug fixes, refactoring cases and performance optimizations. Complete change log of MPD4 branch you can find here: http://mpd.sourceforge.net/doc/mpd5.html You can download mpd in source form here: http://sourceforge.net/project/showfiles.php?group_id=14145 , or install it via FreeBSD ports system. To get all new features proposed by this release it is recommended to upgrade your system to the FreeBSD 6.2-STABLE after 2007-01-28. -- Alexander Motin mav@alkar.net Optima Telecom From owner-freebsd-net@FreeBSD.ORG Mon Jan 29 18:25:30 2007 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F3C9316A401 for ; Mon, 29 Jan 2007 18:25:29 +0000 (UTC) (envelope-from mav@alkar.net) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 7C3EF13C461 for ; Mon, 29 Jan 2007 18:25:29 +0000 (UTC) (envelope-from mav@alkar.net) Received: from [195.248.178.122] (account mav@alkar.net HELO [192.168.3.2]) by cmail.optima.ua (CommuniGate Pro SMTP 5.0.11) with ESMTPA id 20273000; Mon, 29 Jan 2007 20:25:28 +0200 Message-ID: <45BE3C17.3070606@alkar.net> Date: Mon, 29 Jan 2007 20:25:27 +0200 From: Alexander Motin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nikos Vassiliadis References: <1169850194.00677461.1169839202@10.7.7.3> <1169882591.00677647.1169870401@10.7.7.3> <1170080583.00678976.1170067803@10.7.7.3> In-Reply-To: <1170080583.00678976.1170067803@10.7.7.3> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: net@freebsd.org Subject: Re: ng_pptpgre problems: tcp connections reset unexpectedly X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Jan 2007 18:25:30 -0000 Nikos Vassiliadis wrote: > I already have an mpd4 installation working, > but had some problems using pptp with it. I will try again with > the RC you just released. It is released now. And if you will have there any problems, they must be fixed before next release. So inform me. >>I do not use pptp actively, to say for sure, but you can try to play >>with such pptp options like delayed-ack, always-ack and windowing. > 4) >> delayed-ack disable >> always-ack enable >> windowing disable > > seem to work, sometimes it's not that easy to > reproduce the problem. >>Looking here I can see that it is your local machine (213.142.137.253) >>sent "R" - Reset request just after normal acknowledge packet. I don't >>see the reason for such it's behaviour. > > To complicate things a bit more sftp over the same the link works reliably > (different sockopts?). http fails, ftp fails but sftp works as usual. > > Eventually a read(2) fails: > 1794 fetch CALL read(0x3,0x8057730,0xd0) > 1794 fetch RET read -1 errno 60 Operation timed out Strange result IMHO for reading from TCP socket. I will try to investigate this. > It seems to work with disabled windowing. If you are interested in > tracking down this, I would be glad to help. I will try to look into it. If you will have some more interesting results send them to me. -- Alexander Motin mav@alkar.net Optima Telecom From owner-freebsd-net@FreeBSD.ORG Mon Jan 29 18:30:07 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5589616A407 for ; Mon, 29 Jan 2007 18:30:07 +0000 (UTC) (envelope-from victorloureirolima@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.248]) by mx1.freebsd.org (Postfix) with ESMTP id EFD2613C4B2 for ; Mon, 29 Jan 2007 18:30:06 +0000 (UTC) (envelope-from victorloureirolima@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so558570ana for ; Mon, 29 Jan 2007 10:30:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=t1PJfbf356da8do/csBo+Vz/DtUN70IekRGE5ZO0lK4pLGkfxUlZONwYFqSRBUvpT9NgPcm1tqhWP7SjEvzEPnnmcVXhQeqlQM31e6YwDXtwg/Q9xqRXMRfsoxdvmueWhXkcvp8FUfU5+3P90kRlIjO8lJLWB6c2Bie0sdhhkbo= Received: by 10.115.89.1 with SMTP id r1mr288691wal.1170093876148; Mon, 29 Jan 2007 10:04:36 -0800 (PST) Received: by 10.114.177.20 with HTTP; Mon, 29 Jan 2007 10:04:35 -0800 (PST) Message-ID: Date: Mon, 29 Jan 2007 16:04:35 -0200 From: "Victor Loureiro Lima" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Interface security considerations X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Jan 2007 18:30:07 -0000 Hello -net@, A question came into my mind a few days ago while I was coding some application using libpcap on freebsd: - Whats the best way to determine if an application is listening on an interface and sniffing packets that goes through it? I've seen that a couple of process that are using libpcap can be traced back to open file descriptors to /dev/bpfX files using fstat(1), even with sockstat(1) I can figure out that a certain process has an open "something" and further investigate it, but I was wondering whats the common practice for freebsd users finding out this sort of thing? - While I was trying to figure out which process was listening on a certain interfaces an idea for a patch in sys/net/bpf.c functions bpf_open() and bpf_close() that would simply printf(9) the PID (d->bd_pid = td->td_proc->p_pid;) of a process that was trying to open the BPF device, while it was a simple patch, I am not sure if using the BPF device is the only possible way to sniff the packets from an interface, I know that linux implement sock_packet, and some systems have DLPI, just to get things straight, If an application wants to be able to sniff packets on a interface the only possible way (without messing with kernel at all) is using the BPF interface or are there other ways (even if they are not portable out of FreeBSD at all) of doing this? - Is "device bpf" enabled by default on GENERIC kernel? Thanks in advance, Victor Loureiro Lima From owner-freebsd-net@FreeBSD.ORG Mon Jan 29 19:21:34 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7199916A406 for ; Mon, 29 Jan 2007 19:21:34 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.232]) by mx1.freebsd.org (Postfix) with ESMTP id 237FB13C4A3 for ; Mon, 29 Jan 2007 19:21:34 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by wr-out-0506.google.com with SMTP id 68so1010127wri for ; Mon, 29 Jan 2007 11:21:33 -0800 (PST) Received: by 10.90.115.9 with SMTP id n9mr7170461agc.1170096911076; Mon, 29 Jan 2007 10:55:11 -0800 (PST) Received: by 10.90.29.8 with HTTP; Mon, 29 Jan 2007 10:55:11 -0800 (PST) Message-ID: Date: Mon, 29 Jan 2007 20:55:11 +0200 From: "Vlad GALU" To: "Victor Loureiro Lima" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-net@freebsd.org Subject: Re: Interface security considerations X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Jan 2007 19:21:34 -0000 On 1/29/07, Victor Loureiro Lima wrote: > Hello -net@, > > A question came into my mind a few days > ago while I was coding some application using > libpcap on freebsd: > - Whats the best way to determine if an application > is listening on an interface and sniffing packets that > goes through it? I've seen that a couple of process > that are using libpcap can be traced back to open file > descriptors to /dev/bpfX files using fstat(1), even with > sockstat(1) I can figure out that a certain process has > an open "something" and further investigate it, but I was > wondering whats the common practice for freebsd users > finding out this sort of thing? See ports/net/bpfstat. BPF already exposes that info to the userspace programs. > - While I was trying to figure out which process was > listening on a certain interfaces an idea for a patch in > sys/net/bpf.c functions bpf_open() and bpf_close() that > would simply printf(9) the PID (d->bd_pid = td->td_proc->p_pid;) > of a process that was trying to open the BPF device, while > it was a simple patch, I am not sure if using the BPF device > is the only possible way to sniff the packets from an > interface, I know that linux implement sock_packet, and > some systems have DLPI, just to get things straight, > If an application wants to be able to sniff packets on a interface > the only possible way (without messing with kernel at all) is > using the BPF interface or are there other ways (even if they > are not portable out of FreeBSD at all) of doing this? No, there aren't any other interfaces. Unless you modify the ether_input() routine. And BPF is the most portable method in use nowadays. > - Is "device bpf" enabled by default on GENERIC kernel? Yes. > Thanks in advance, > Victor Loureiro Lima > _______________________________________________ > 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" > -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. From owner-freebsd-net@FreeBSD.ORG Mon Jan 29 22:59:07 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A72E816A400; Mon, 29 Jan 2007 22:59:07 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id 7BAAD13C471; Mon, 29 Jan 2007 22:59:07 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id C2CB899B50; Mon, 29 Jan 2007 17:59:06 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Mon, 29 Jan 2007 17:59:06 -0500 X-Sasl-enc: LdP54oHACuM6rw/0zmkD3N9Fs8BhnZDCJNt9AywR//fc 1170111546 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id C42991A180; Mon, 29 Jan 2007 17:59:05 -0500 (EST) Message-ID: <45BE7C37.20903@FreeBSD.org> Date: Mon, 29 Jan 2007 22:59:03 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: Gleb Smirnoff References: <20070125162422.GA7922@bestcom.ru> <45B8EB23.705@FreeBSD.org> <20070125183720.GB7922@cell.sick.ru> <20070125203807.S13293@fledge.watson.org> <20070125212310.GG7922@cell.sick.ru> <20070125214956.J13293@fledge.watson.org> <20070126114449.GM7922@cell.sick.ru> In-Reply-To: <20070126114449.GM7922@cell.sick.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Robert Watson , net@FreeBSD.org Subject: Re: rev. 1.94 of netinet/in.c broke CARP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Jan 2007 22:59:07 -0000 Hello, I've had a chance to read ip_carp.c in more detail now, so... Gleb Smirnoff wrote: > Is adding a generic GC function a correct way or was it better to just fix > the buggy layer, that forgot about its multicast memberships? > In the bigger picture: The real fix for netinet is to do what netinet6 does; that is, refcount the memberships and keep them in a list, rather than a vector. This would have been my preferred fix. However, this breaks the ABI for drivers, and is a larger change. The less intrusive, non-ABI-breaking change (discussed with Robert at the time) was to convert a statically allocated array to a lazy-reallocated vector. This was considered acceptable for the upcoming 6.2 release at that point in time. Unfortunately, due to how CARP works, two bugs were fixed at the expense of introducing another. > ATM, I can fix the CARP in the following way: > > 1) Call multicast cleanup, if we are destroying carp interface itself. > 2) Don't call multicast cleanup, if we are called through EVENTHANDLER(9) > since parent is detaching. > > Would this fix be ok? > Yes. In fact I would go so far as to say that it is the correct behaviour for CARP. Resource allocation and free for CARP runs along two separate paths; the case where a member interface is detached cannot be considered the same as when CARP itself is detaching, they are two distinct paths. imo_membership 'belongs to' netinet attached to an ifnet. CARP merely borrows it. Regards, BMS From owner-freebsd-net@FreeBSD.ORG Tue Jan 30 00:35:30 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0D71716A402 for ; Tue, 30 Jan 2007 00:35:30 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.183]) by mx1.freebsd.org (Postfix) with ESMTP id BF30013C467 for ; Tue, 30 Jan 2007 00:35:29 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by py-out-1112.google.com with SMTP id f47so856878pye for ; Mon, 29 Jan 2007 16:35:29 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=K9qB6F28+9ThKxGA1rx3OhxGSLLeZJbOdnl9wzNPRL7lqzLk6pKUKTKoS853xoWkdFKPJa7vdSCggP8mnOe49QmwcQpC8516YjRJxdAMnQvOSQzbP8eEsiOWV+kk9sI9qmTDSHOh3cJNs0EVo+m14b9eurIU382XD+CXxVpOXVQ= Received: by 10.35.64.8 with SMTP id r8mr14031260pyk.1170117328270; Mon, 29 Jan 2007 16:35:28 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id a70sm6868598pye.2007.01.29.16.35.25; Mon, 29 Jan 2007 16:35:27 -0800 (PST) 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 l0U0YLvI005341 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Jan 2007 09:34:21 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l0U0YJM3005340; Tue, 30 Jan 2007 09:34:19 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 30 Jan 2007 09:34:19 +0900 From: Pyun YongHyeon To: Johan Str?m Message-ID: <20070130003419.GA5092@cdnetworks.co.kr> References: <16425E76-4111-4DE3-970D-A5E1E29EA194@stromnet.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16425E76-4111-4DE3-970D-A5E1E29EA194@stromnet.se> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org, wpaul@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Support for 3C996-SX? Or 3C985(b)-SX? 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, 30 Jan 2007 00:35:30 -0000 On Mon, Jan 29, 2007 at 02:00:06PM +0100, Johan Str?m wrote: > Hi > > I'm about to buy a PCI 1000-SX network card, looking on eBay I've > found both 3C996-SX and 3C985(b)-SX cards. > Looking at http://www.freebsd.org/releases/6.2R/hardware- > i386.html#ETHERNET I can find "3Com 3c996-T (10/100/1000baseTX)", but > not the SX? > However, on http://www.freebsd.org/releases/5.0R/hardware- > i386.html#ETHERNET I can see "3Com 3c996-SX, 3c996-T". > So, has the -SX support been removed or something? > From the if_bge.c changelog (http://www.freebsd.org/cgi/cvsweb.cgi/ > src/sys/dev/bge/if_bge.c) I found this: > If my memory serve me right bge(4) supports 3Com 996SX. I think I've used the 996SX to make bge(4) work on sparc64. > Commit message by wpaul > > Lastly, teach the driver how to recognize a 3c996B-SX by checking > > the hardware config word in the EEPROM in order to detect the media. > > We attach 5701 fiber cards correctly now, but I haven't verified that > > they send/receive packets yet since I don't have a second fiber > > interface at home. (I know that fiber 5700 cards work, so I'm > > keeping my fingers crossed.) > > But this is from 4 years ago so.. not pretty recent and no followup > in the log. > > So, is it supported or not? :) > > Also i found some 3c985(b) cards on eBay, a bit more expensive ($10 > or so..), but this uses the ti driver instead of bge. And from what I > can see this driver does not support ALTQ. However, im not quite sure I'm not sure Max Laier(mlaier@) already made a ALTQ patch for ti(4). If you can test ti(4) on your box I can write a ALTQ patch for ti(4). > i will need it anyway, since I will runt VLAN interface ontop of the > device (and both bge and ti supports vlan), and vlan does not support > altq anyway (which is kind of boring, any plans for it?) > > So, any suggestions? Which card should I choose? Or some other > popular card in the same price range (ebay price range that is..)? > > Thanks! > > Johan Str?m > Stromnet > johan@stromnet.se > http://www.stromnet.se/ -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Tue Jan 30 09:35:04 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BCACF16A400; Tue, 30 Jan 2007 09:35:04 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from av12-1-sn2.hy.skanova.net (av12-1-sn2.hy.skanova.net [81.228.8.185]) by mx1.freebsd.org (Postfix) with ESMTP id 3D8E213C428; Tue, 30 Jan 2007 09:35:04 +0000 (UTC) (envelope-from johan@stromnet.se) Received: by av12-1-sn2.hy.skanova.net (Postfix, from userid 502) id EE34538245; Tue, 30 Jan 2007 10:10:01 +0100 (CET) Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net [81.228.8.93]) by av12-1-sn2.hy.skanova.net (Postfix) with ESMTP id DA0DC380AD; Tue, 30 Jan 2007 10:10:01 +0100 (CET) Received: from elfi.stromnet.se (90-224-172-102-no129.tbcn.telia.com [90.224.172.102]) by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id C721C37E49; Tue, 30 Jan 2007 10:10:01 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by elfi.stromnet.se (Postfix) with ESMTP id 13AEF61E48; Tue, 30 Jan 2007 10:10:01 +0100 (CET) X-Virus-Scanned: amavisd-new at stromnet.se Received: from elfi.stromnet.se ([127.0.0.1]) by localhost (elfi.stromnet.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8kFD-I6Bfyds; Tue, 30 Jan 2007 10:09:55 +0100 (CET) Received: from [129.16.46.255] (dynamic-46-255.chl.chalmers.se [129.16.46.255]) by elfi.stromnet.se (Postfix) with ESMTP id C82C661E49; Tue, 30 Jan 2007 10:09:55 +0100 (CET) In-Reply-To: <20070130003419.GA5092@cdnetworks.co.kr> References: <16425E76-4111-4DE3-970D-A5E1E29EA194@stromnet.se> <20070130003419.GA5092@cdnetworks.co.kr> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <6934F894-BDD2-4185-9245-8B53407C3903@stromnet.se> Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?Johan_Str=F6m?= Date: Tue, 30 Jan 2007 10:09:15 +0100 To: pyunyh@gmail.com X-Mailer: Apple Mail (2.752.3) Cc: freebsd-net@freebsd.org, wpaul@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Support for 3C996-SX? Or 3C985(b)-SX? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Jan 2007 09:35:04 -0000 On Jan 30, 2007, at 01:34 , Pyun YongHyeon wrote: > On Mon, Jan 29, 2007 at 02:00:06PM +0100, Johan Str?m wrote: >> Hi >> >> I'm about to buy a PCI 1000-SX network card, looking on eBay I've >> found both 3C996-SX and 3C985(b)-SX cards. >> Looking at http://www.freebsd.org/releases/6.2R/hardware- >> i386.html#ETHERNET I can find "3Com 3c996-T (10/100/1000baseTX)", but >> not the SX? >> However, on http://www.freebsd.org/releases/5.0R/hardware- >> i386.html#ETHERNET I can see "3Com 3c996-SX, 3c996-T". >> So, has the -SX support been removed or something? >> =46rom the if_bge.c changelog (http://www.freebsd.org/cgi/cvsweb.cgi/ >> src/sys/dev/bge/if_bge.c) I found this: >> > > If my memory serve me right bge(4) supports 3Com 996SX. > I think I've used the 996SX to make bge(4) work on sparc64. Goodie :) I got a private mail from wpaul too confirming this. > >> Commit message by wpaul >>> Lastly, teach the driver how to recognize a 3c996B-SX by checking >>> the hardware config word in the EEPROM in order to detect the media. >>> We attach 5701 fiber cards correctly now, but I haven't verified =20 >>> that >>> they send/receive packets yet since I don't have a second fiber >>> interface at home. (I know that fiber 5700 cards work, so I'm >>> keeping my fingers crossed.) >> >> But this is from 4 years ago so.. not pretty recent and no followup >> in the log. >> >> So, is it supported or not? :) >> >> Also i found some 3c985(b) cards on eBay, a bit more expensive ($10 >> or so..), but this uses the ti driver instead of bge. And from what I >> can see this driver does not support ALTQ. However, im not quite sure > > I'm not sure Max Laier(mlaier@) already made a ALTQ patch for ti(4). > If you can test ti(4) on your box I can write a ALTQ patch for ti(4). Okay :) I'll see what card I get, but as I understand it it shouldnt =20 make much difference.. Thanks for your help! :) Johan Str=F6m Stromnet johan@stromnet.se http://www.stromnet.se/ From owner-freebsd-net@FreeBSD.ORG Tue Jan 30 09:48:54 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DF36B16A403 for ; Tue, 30 Jan 2007 09:48:54 +0000 (UTC) (envelope-from chris@hitnet.RWTH-Aachen.DE) Received: from mta-1.ms.rz.rwth-aachen.de (mta-1.ms.rz.RWTH-Aachen.DE [134.130.7.72]) by mx1.freebsd.org (Postfix) with ESMTP id 8E36113C48D for ; Tue, 30 Jan 2007 09:48:54 +0000 (UTC) (envelope-from chris@hitnet.RWTH-Aachen.DE) Received: from circe ([134.130.3.36]) by mta-1.ms.rz.RWTH-Aachen.de (Sun Java System Messaging Server 6.2-7.05 (built Sep 5 2006)) with ESMTP id <0JCO00J7WDXHNVC0@mta-1.ms.rz.RWTH-Aachen.de>; Tue, 30 Jan 2007 10:48:53 +0100 (CET) Received: from talos.rz.RWTH-Aachen.DE ([134.130.3.22]) by circe (MailMonitor for SMTP v1.2.2 ) ; Tue, 30 Jan 2007 10:48:52 +0100 (MET) Received: from bigboss.hitnet.rwth-aachen.de (bigspace.hitnet.RWTH-Aachen.DE [137.226.181.2]) by smarthost.rwth-aachen.de (8.13.8/8.13.1/1) with ESMTP id l0U9mqwG012105; Tue, 30 Jan 2007 10:48:52 +0100 Received: from haakonia.hitnet.rwth-aachen.de ([137.226.181.92]) by bigboss.hitnet.rwth-aachen.de with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1HBpbg-0005rZ-7t; Tue, 30 Jan 2007 10:48:52 +0100 Received: by haakonia.hitnet.rwth-aachen.de (Postfix, from userid 1001) id B6A3A3F41E; Tue, 30 Jan 2007 10:48:51 +0100 (CET) Date: Tue, 30 Jan 2007 10:48:51 +0100 From: Christian Brueffer In-reply-to: <6934F894-BDD2-4185-9245-8B53407C3903@stromnet.se> To: Johan =?iso-8859-1?Q?Str=F6m?= Message-id: <20070130094851.GB2019@haakonia.hitnet.RWTH-Aachen.DE> MIME-version: 1.0 Content-type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary=TakKZr9L6Hm6aLOc Content-disposition: inline X-Operating-System: FreeBSD 6.2-STABLE X-PGP-Key: http://people.FreeBSD.org/~brueffer/brueffer.key.asc X-PGP-Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D References: <16425E76-4111-4DE3-970D-A5E1E29EA194@stromnet.se> <20070130003419.GA5092@cdnetworks.co.kr> <6934F894-BDD2-4185-9245-8B53407C3903@stromnet.se> User-Agent: Mutt/1.5.11 Cc: pyunyh@gmail.com, freebsd-net@freebsd.org, freebsd-hardware@freebsd.org, wpaul@freebsd.org Subject: Re: Support for 3C996-SX? Or 3C985(b)-SX? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Jan 2007 09:48:55 -0000 --TakKZr9L6Hm6aLOc Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 30, 2007 at 10:09:15AM +0100, Johan Str=F6m wrote: >=20 > On Jan 30, 2007, at 01:34 , Pyun YongHyeon wrote: >=20 > >On Mon, Jan 29, 2007 at 02:00:06PM +0100, Johan Str?m wrote: > >>Hi > >> > >>I'm about to buy a PCI 1000-SX network card, looking on eBay I've > >>found both 3C996-SX and 3C985(b)-SX cards. > >>Looking at http://www.freebsd.org/releases/6.2R/hardware- > >>i386.html#ETHERNET I can find "3Com 3c996-T (10/100/1000baseTX)", but > >>not the SX? > >>However, on http://www.freebsd.org/releases/5.0R/hardware- > >>i386.html#ETHERNET I can see "3Com 3c996-SX, 3c996-T". > >>So, has the -SX support been removed or something? > >>From the if_bge.c changelog (http://www.freebsd.org/cgi/cvsweb.cgi/ > >>src/sys/dev/bge/if_bge.c) I found this: > >> > > > >If my memory serve me right bge(4) supports 3Com 996SX. > >I think I've used the 996SX to make bge(4) work on sparc64. >=20 > Goodie :) I got a private mail from wpaul too confirming this. >=20 Thanks, I have added this card to the bge(4) hardware list, so it'll show up as supported for the next release. - Christian --=20 Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D --TakKZr9L6Hm6aLOc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFvxSDbHYXjKDtmC0RAqHSAJ9GZfFPedGcCRhZ8pvxf9+AhUYh9gCffQVx gWKQJcUZbCRGZaZ50alLxFw= =M6rC -----END PGP SIGNATURE----- --TakKZr9L6Hm6aLOc-- From owner-freebsd-net@FreeBSD.ORG Tue Jan 30 10:23:27 2007 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9369F16A401 for ; Tue, 30 Jan 2007 10:23:27 +0000 (UTC) (envelope-from nvass@teledomenet.gr) Received: from arwen.teledomenet.gr (arwen.teledomenet.gr [213.142.128.58]) by mx1.freebsd.org (Postfix) with ESMTP id 181F313C442 for ; Tue, 30 Jan 2007 10:23:26 +0000 (UTC) (envelope-from nvass@teledomenet.gr) Received: from iris ([192.168.1.71]) by arwen.teledomenet.gr (8.12.10/8.12.10) with ESMTP id l0UANMm1004920; Tue, 30 Jan 2007 12:23:22 +0200 From: Nikos Vassiliadis To: Alexander Motin Date: Tue, 30 Jan 2007 12:26:35 +0200 User-Agent: KMail/1.9.1 References: <1169850194.00677461.1169839202@10.7.7.3> <1170080583.00678976.1170067803@10.7.7.3> <45BE3C17.3070606@alkar.net> In-Reply-To: <45BE3C17.3070606@alkar.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701301226.35612.nvass@teledomenet.gr> Cc: net@freebsd.org Subject: Re: ng_pptpgre problems: tcp connections reset unexpectedly X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Jan 2007 10:23:27 -0000 On Monday 29 January 2007 20:25, Alexander Motin wrote: > It is released now. And if you will have there any problems, they must > be fixed before next release. So inform me. The problem I had is gone. mpd4 cannot be compared to mpd3. It is by far superior, both usability-wise and networking-ability-wise. thanks. > > To complicate things a bit more sftp over the same the link works reliably > > (different sockopts?). http fails, ftp fails but sftp works as usual. > > > > Eventually a read(2) fails: > > 1794 fetch CALL read(0x3,0x8057730,0xd0) > > 1794 fetch RET read -1 errno 60 Operation timed out > > Strange result IMHO for reading from TCP socket. I will try to > investigate this. > > > It seems to work with disabled windowing. If you are interested in > > tracking down this, I would be glad to help. > > I will try to look into it. If you will have some more interesting > results send them to me. > I can provide you a pptp peer to connect to. I can reproduce it easily from home, I am opening a pptp tunnel over the pppoe connection and it happens frequently. Nikos From owner-freebsd-net@FreeBSD.ORG Tue Jan 30 13:16:37 2007 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 08B5216A4A7 for ; Tue, 30 Jan 2007 13:16:37 +0000 (UTC) (envelope-from mav@alkar.net) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 8340213C46B for ; Tue, 30 Jan 2007 13:16:36 +0000 (UTC) (envelope-from mav@alkar.net) Received: from [212.86.226.11] (account mav@alkar.net [212.86.226.11] verified) by cmail.optima.ua (CommuniGate Pro SMTP 5.0.11) with ESMTPA id 20298249; Tue, 30 Jan 2007 15:16:35 +0200 Message-ID: <45BF4532.7060203@alkar.net> Date: Tue, 30 Jan 2007 15:16:34 +0200 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8b) Gecko/20051108 MIME-Version: 1.0 To: Nikos Vassiliadis References: <1169850194.00677461.1169839202@10.7.7.3> <1170080583.00678976.1170067803@10.7.7.3> <45BE3C17.3070606@alkar.net> <200701301226.35612.nvass@teledomenet.gr> In-Reply-To: <200701301226.35612.nvass@teledomenet.gr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: net@freebsd.org Subject: Re: ng_pptpgre problems: tcp connections reset unexpectedly. TCP guru needed! X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Jan 2007 13:16:37 -0000 Nikos Vassiliadis wrote: >>>It seems to work with disabled windowing. If you are interested in >>>tracking down this, I would be glad to help. >> >>I will try to look into it. If you will have some more interesting >>results send them to me. > > I can provide you a pptp peer to connect to. I can reproduce it > easily from home, I am opening a pptp tunnel over the pppoe > connection and it happens frequently. Last night I was thinking of it and I was able to reproduce this sometimes, but it was not predictable. For this moment I have no idea about reason of this problem. There is one problem with windowing in ng_pptpgre and I am now working on it, but it can only results in packet losses, but not in connection reset. I think we need some TCP guru to understand this. -- Alexander Motin mav@alkar.net Optima Telecom From owner-freebsd-net@FreeBSD.ORG Tue Jan 30 13:33:07 2007 Return-Path: X-Original-To: freebsd-net@hub.freebsd.org Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7F25116A400; Tue, 30 Jan 2007 13:33:07 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 56D1913C467; Tue, 30 Jan 2007 13:33:07 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (remko@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l0UDX7RT068954; Tue, 30 Jan 2007 13:33:07 GMT (envelope-from remko@freefall.freebsd.org) Received: (from remko@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l0UDX7oD068950; Tue, 30 Jan 2007 13:33:07 GMT (envelope-from remko) Date: Tue, 30 Jan 2007 13:33:07 GMT From: Remko Lodder Message-Id: <200701301333.l0UDX7oD068950@freefall.freebsd.org> To: remko@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-net@FreeBSD.org Cc: Subject: Re: kern/108542: [bce]: Huge network latencies with 6.2-RELEASE / STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2007 13:33:07 -0000 Old Synopsis: Huge network latencies with 6.2-RELEASE / STABLE New Synopsis: [bce]: Huge network latencies with 6.2-RELEASE / STABLE Responsible-Changed-From-To: freebsd-i386->freebsd-net Responsible-Changed-By: remko Responsible-Changed-When: Tue Jan 30 13:32:00 UTC 2007 Responsible-Changed-Why: This seems like a networking issue, assign it to the networking team. Submitter: Please be informed that there had been discussion on the bce driver recently (I cannot recall whether that went about performance issues though), if you are not aware of that please review the mailinglist archives of -net (as far as i can recall) http://www.freebsd.org/cgi/query-pr.cgi?pr=108542 From owner-freebsd-net@FreeBSD.ORG Wed Jan 31 03:31:12 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7F1AD16A406 for ; Wed, 31 Jan 2007 03:31:12 +0000 (UTC) (envelope-from x86.nat@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.freebsd.org (Postfix) with ESMTP id 2022D13C46B for ; Wed, 31 Jan 2007 03:31:11 +0000 (UTC) (envelope-from x86.nat@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so63051uge for ; Tue, 30 Jan 2007 19:31:11 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=ZaHsxlB+xBE/TXGy8RXnCngUCOa76lYTn6Z0LsomIOFtJ2QHlE8XAD/4RUVoqEZyNQSfLM5hFWfyQJhdADhqFFc8JRjN1E8ZIuxbT8XaT0cezNDxdYmGRhEfo3jW/c/qNGOsTUOku6DE4nwW3jFjcHjaPG6pgOgseFCPPNO9FuA= Received: by 10.78.97.7 with SMTP id u7mr41263hub.1170212546115; Tue, 30 Jan 2007 19:02:26 -0800 (PST) Received: by 10.78.175.6 with HTTP; Tue, 30 Jan 2007 19:02:26 -0800 (PST) Message-ID: <491f5f5a0701301902k285bae45v2d362855e3148d22@mail.gmail.com> Date: Wed, 31 Jan 2007 11:02:26 +0800 From: MIN To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: s X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Jan 2007 03:31:12 -0000 -- from x86.natgmail.com Best regards, From owner-freebsd-net@FreeBSD.ORG Wed Jan 31 09:42:20 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CB8CA16A401 for ; Wed, 31 Jan 2007 09:42:20 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id A390613C4B3 for ; Wed, 31 Jan 2007 09:42:20 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id DF6994D83F; Wed, 31 Jan 2007 04:20:48 -0500 (EST) Date: Wed, 31 Jan 2007 09:20:45 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Victor Loureiro Lima In-Reply-To: Message-ID: <20070131091347.O58048@fledge.watson.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: Interface security considerations X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Jan 2007 09:42:20 -0000 On Mon, 29 Jan 2007, Victor Loureiro Lima wrote: > - While I was trying to figure out which process was listening on a certain > interfaces an idea for a patch in sys/net/bpf.c functions bpf_open() and > bpf_close() that would simply printf(9) the PID (d->bd_pid = > td->td_proc->p_pid;) of a process that was trying to open the BPF device, > while it was a simple patch, I am not sure if using the BPF device is the > only possible way to sniff the packets from an interface, I know that linux > implement sock_packet, and some systems have DLPI, just to get things > straight, If an application wants to be able to sniff packets on a interface > the only possible way (without messing with kernel at all) is using the BPF > interface or are there other ways (even if they are not portable out of > FreeBSD at all) of doing this? FYI, the semantics of bd_pid are potentially confusing: bd_pid is the process ID of the process that has most recently issued an operation on the BPF descriptor. Since more than one process at a time may have a reference to the same BPF descriptor (discouraged, but possible), bd_pid doesn't reflect all the processes that have in the past used the descriptor, or may even be using it when queried. fstat and other tools that derive consumer information from process and file descriptor tables are the only way to gather a full list of current consumers of a BPF descriptor. BPF is the only formal API for network interface-layer packet sniffing, but there are a variety of services that can be used in FreeBSD to sniff packets. For example, using the IPFW firewall, it is possible to tee the packet stream to a divert socket, which provides access to the active packet stream visible to IP. PF and ipfilter also offer similer facilities, which I believe are even directly supported by tcpdump. And, the administrator can always load custom kernel code to the same effect, as there are network interface programming hooks in netgraph that allow attaching to the packet stream. Compiling BPF out of the kernel will make it more complex to sniff packets. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-net@FreeBSD.ORG Wed Jan 31 12:07:00 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9163416A49C for ; Wed, 31 Jan 2007 12:07:00 +0000 (UTC) (envelope-from tarkhil@webmail.sub.ru) Received: from mail.sub.ru (host-205-2.netflow.ru [88.212.205.2]) by mx1.freebsd.org (Postfix) with SMTP id C41A213C4BF for ; Wed, 31 Jan 2007 12:06:57 +0000 (UTC) (envelope-from tarkhil@webmail.sub.ru) Received: (qmail 34522 invoked by uid 0); 31 Jan 2007 14:45:48 +0300 Received: from unknown (HELO localhost) (88.212.205.2) by techno.sub.ru with SMTP; 31 Jan 2007 11:45:48 -0000 X-Virus-Scanned: by amavisd-new at mail.sub.ru Received: from unknown ([88.212.205.2]) by localhost (mail-new.sub.ru [88.212.205.2]) (amavisd-new, port 10024) with SMTP id QdxTnUHR8sT4; Wed, 31 Jan 2007 14:45:44 +0300 (MSK) Received: from unknown (HELO ?192.168.139.47?) (tarkhil%sub.ru@213.247.139.99) by techno.sub.ru with SMTP; 31 Jan 2007 11:45:44 -0000 Message-ID: <45C08019.1030105@webmail.sub.ru> Date: Wed, 31 Jan 2007 14:40:09 +0300 From: Alex Povolotsky User-Agent: Thunderbird 1.5.0.9 (X11/20070104) MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-net@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: mpd locking system? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Jan 2007 12:07:00 -0000 Hello! for about 4-5 days, I'm expeirencing heavy troubles with my VPN (mpd) 6.1-RELEASE based server. After some time (minimum 2 seconds, maximum 12 hours) of running MPD with moderate load (about 100-200 clients, CPU not overused), system locks (even keyboard hangs) to reset. Nothing at all in logs. Patching kernel to 6.1p12 did not help. Attempt to add kern.ipc.nmbclusters="0" to /boot/loader.conf did not change anything. The box seems to be healthy (at least, CPU fan works ok, no symptoms of overheating at all). It has run under more load without a flaw. I hope someone can help. Alex. From owner-freebsd-net@FreeBSD.ORG Wed Jan 31 14:27:55 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 85FAB16A407 for ; Wed, 31 Jan 2007 14:27:55 +0000 (UTC) (envelope-from antinvidia@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.177]) by mx1.freebsd.org (Postfix) with ESMTP id 44CAC13C46B for ; Wed, 31 Jan 2007 14:27:55 +0000 (UTC) (envelope-from antinvidia@gmail.com) Received: by py-out-1112.google.com with SMTP id f47so106415pye for ; Wed, 31 Jan 2007 06:27:54 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=ljv1z3c9HzfpKwHWSdylSCvFYNUrq8wCPhkSzbdCpeVhnqbEkW2TkGue6u8qW7KDJ3WE9D5VMsJe+0cB0T9Y/trgw4dnWcjPU6FZ9DJ4xqLNq++4GeKC2ytvGs99QGfU8eVMtXM2lS5PfIy4iF+B5noEc/MOpdxyi5oWPPhRCuQ= Received: by 10.35.41.12 with SMTP id t12mr1624939pyj.1170253674583; Wed, 31 Jan 2007 06:27:54 -0800 (PST) Received: by 10.35.58.13 with HTTP; Wed, 31 Jan 2007 06:27:54 -0800 (PST) Message-ID: Date: Wed, 31 Jan 2007 22:27:54 +0800 From: MQ To: Wishmaster In-Reply-To: MIME-Version: 1.0 References: <1458229821.20070120234257@velnet.ru> <45B28F37.7040100@delphij.net> <1651695163.20070122010957@velnet.ru> <45B4BE90.20602@qwirky.net> <1582899958.20070126014728@velnet.ru> <194684269.20070127175157@velnet.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re: Re[4]: reproducible watchdog timeout in bge X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Jan 2007 14:27:55 -0000 2007/1/28, MQ : > > > > 2007/1/27, Wishmaster : > > > > Hello MQ, > > > > Saturday, January 27, 2007, 5:31:49 PM, you wrote: > > > > M> I have two boxes with onboard bge, one using 5780, the other > > M> 5701. Neither of them has your problem. I think there may be some > > M> problems with your software or hardware configuration. > > > > > > I don't think so. I have two different motherboards and two > > different freebsd distributions on them (6.1/amd64 and 6.2/i386). On > > both motherboards there > > are bcm5721 onboard network chips and both configurations have the > > same issue. > > > > Can you tell me do you have smp kernel? > > > > p.s. On both machines I have clear installation of freebsd. i.e. > > there is nothing except SMP in my kernel. > > -- > > Best regards, > > Wishmaster mailto: wishmaster@velnet.ru > > > > > > _______________________________________________ > > 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" > > > > > One of my boxes is dual Opteron 250 with dual 5780 onboard, SMP kernel. > The other is HP NC6000 with 5701, GENERIC kernel. Perhaps 5721 has some big > differences from other chips. > Today, I got a mainboard manufactured by Tyan with onboard 5721. I got into a situation even stranger than yours, the NIC was identified as 5750, and printed RX CPU self-diagnostics failed! It's so strange, I'll go deeper into this problem when I get time. From owner-freebsd-net@FreeBSD.ORG Wed Jan 31 15:06:20 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 850B216A403 for ; Wed, 31 Jan 2007 15:06:20 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id 48A2113C494 for ; Wed, 31 Jan 2007 15:06:20 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id EE5EC9E0AD for ; Wed, 31 Jan 2007 09:39:43 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Wed, 31 Jan 2007 09:39:43 -0500 X-Sasl-enc: MPmIVxSNIi3oitGSsqu5qAxTI+3OMl/i7ME4mMrQB5b5 1170254383 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 814252D0D2 for ; Wed, 31 Jan 2007 09:39:43 -0500 (EST) Message-ID: <45C0AA2E.30803@incunabulum.net> Date: Wed, 31 Jan 2007 14:39:42 +0000 From: Bruce M Simpson User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: net@FreeBSD.org Content-Type: multipart/mixed; boundary="------------010605080409020901020105" Cc: Subject: [PATCH] Broadcast 169.254.0.0/16 ARP replies for RFC 3927 (Zeroconf) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Jan 2007 15:06:20 -0000 This is a multi-part message in MIME format. --------------010605080409020901020105 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I will hold off on committing this pending further feedback. Regards, BMS --------------010605080409020901020105 Content-Type: text/x-patch; name="zeroconf-arp.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="zeroconf-arp.diff" This patch forces the FreeBSD IPv4 ARP code to broadcast ARP replies for IPv4 link-local addresses, as required by RFC 3927, if and only if the request was destined for the local machine (ie not proxied). The code does not set ar_tha by itself; it relies on the AF_ARP handler in net/if_ethersubr.c to set it to if_broadaddr for us. Delta 1.97-1.98 of netinet/in.h is required for the IN_LINKLOCAL() macro. Index: if_ether.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/if_ether.c,v retrieving revision 1.158 diff -u -p -r1.158 if_ether.c --- if_ether.c 14 Jan 2007 18:44:17 -0000 1.158 +++ if_ether.c 31 Jan 2007 14:35:48 -0000 @@ -885,11 +885,23 @@ reply: } } + if (itaddr.s_addr == myaddr.s_addr && + IN_LINKLOCAL(ntohl(itaddr.s_addr))) { + /* RFC 3927 link-local IPv4; always reply by broadcast. */ +#ifdef DEBUG_LINKLOCAL + printf("arp: sending reply for link-local addr %s\n", + inet_ntoa(itaddr)); +#endif + m->m_flags |= M_BCAST; + m->m_flags &= ~M_MCAST; + } else { + /* default behaviour; never reply by broadcast. */ + m->m_flags &= ~(M_BCAST|M_MCAST); + } (void)memcpy(ar_tpa(ah), ar_spa(ah), ah->ar_pln); (void)memcpy(ar_spa(ah), &itaddr, ah->ar_pln); ah->ar_op = htons(ARPOP_REPLY); ah->ar_pro = htons(ETHERTYPE_IP); /* let's be sure! */ - m->m_flags &= ~(M_BCAST|M_MCAST); /* never reply by broadcast */ m->m_len = sizeof(*ah) + (2 * ah->ar_pln) + (2 * ah->ar_hln); m->m_pkthdr.len = m->m_len; sa.sa_family = AF_ARP; --------------010605080409020901020105-- From owner-freebsd-net@FreeBSD.ORG Wed Jan 31 16:56:18 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A6A0616A401 for ; Wed, 31 Jan 2007 16:56:18 +0000 (UTC) (envelope-from slawek.zak@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.237]) by mx1.freebsd.org (Postfix) with ESMTP id 6D29C13C4B2 for ; Wed, 31 Jan 2007 16:56:18 +0000 (UTC) (envelope-from slawek.zak@gmail.com) Received: by wr-out-0506.google.com with SMTP id 71so256225wri for ; Wed, 31 Jan 2007 08:56:17 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=oiBIkzpfKh7HX97SV9tD/6FWifHfaCtdgBgeKu0+puRKsreeHk/FunhcXHMVCgt4RNdyii9hhDrwcsimKVcJOXND5YIxm01wUhEcE0y39PEGqb6yO7Paderje3+f7pJzN3YUE/0GpUdo7yFhSjcFx1VCg/hEXLFPokYpBe98l8o= Received: by 10.90.65.11 with SMTP id n11mr1465560aga.1170260870650; Wed, 31 Jan 2007 08:27:50 -0800 (PST) Received: by 10.90.65.6 with HTTP; Wed, 31 Jan 2007 08:27:50 -0800 (PST) Message-ID: <787bbe1c0701310827o9b84b33q1322007bf68f4f8a@mail.gmail.com> Date: Wed, 31 Jan 2007 17:27:50 +0100 From: "Slawek Zak" To: freebsd-net@freebsd.org, freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Forcing 1000FD for bce X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Jan 2007 16:56:18 -0000 Hi, First of all thanks to Doug White for committing SerDes support for bce. I have a question for someone familiar with this driver. I must enforce Gb/Full-duplex before the end of boot. I have IBM BladeCenter chassis which internally uses Nortel 2-3 switches which in turn do not allow for autonegotiation of internal interfaces. I want to run a diskless configuration so changing the bits with ifconfig is not an option. Tweaking settings in PXE boot agent doesn't help - the link preference is not preserved after kernel starts booting. Thus the last resort remains I guess - fiddling with the source. Help anyone TIA, /S From owner-freebsd-net@FreeBSD.ORG Wed Jan 31 16:57:03 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EE8A116A403 for ; Wed, 31 Jan 2007 16:57:03 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id B06D213C49D for ; Wed, 31 Jan 2007 16:57:03 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 22E949E0A9 for ; Wed, 31 Jan 2007 11:57:03 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Wed, 31 Jan 2007 11:57:03 -0500 X-Sasl-enc: jaoTba1GJVw94X55UUYCl4NQZAlWbxrLJeYtdIjm46bZ 1170262622 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 78F7711BF for ; Wed, 31 Jan 2007 11:57:02 -0500 (EST) Message-ID: <45C0CA5D.5090903@incunabulum.net> Date: Wed, 31 Jan 2007 16:57:01 +0000 From: Bruce M Simpson User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: net@FreeBSD.org Content-Type: multipart/mixed; boundary="------------010507050407010806050504" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: [TEST ATTACHED] Inconsistencies with IP_ONESBCAST and/or IP_SENDSRCADDR X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Jan 2007 16:57:04 -0000 This is a multi-part message in MIME format. --------------010507050407010806050504 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hello, In preparation for tightening up our handling of INADDR_BROADCAST sends, I ran some brief tests today on the network stack with the attached test code. I found some inconsistencies when run against 6.2-RELEASE; 1. IP_ONESBCAST breaks if SO_DONTROUTE is specified. One thing appears to be consistent about the failure mode: bad UDP checksums. dc(4) is being used on the destination end of the test network, so checksum offloading should not be an issue. I am also seeing the wrong destination address being used in most cases. This is intermittent regardless of whether the socket is bound or unbound. 2. IP_SENDSRCADDR has some other inconsistencies. a. The option is always rejected if the socket is not bound. I find this behaviour suspect; the whole point of the option is to specify, for SOCK_DGRAM and SOCK_RAW, the source address of a packet. b. 0.0.0.0 is always accepted. A regular interface lookup is used based on destination if this is specified. This appears suspect to me because such an option is redundant. In theory a developer should be able to write code which uses SO_DONTROUTE and IP_SENDSRCADDR to bypass the routing table lookup when sending to 255.255.255.255. Currently this doesn't appear to be the case, though IP_SENDSRCADDR is a separate issue from IP_ONESBCAST. Regards, BMS --------------010507050407010806050504-- From owner-freebsd-net@FreeBSD.ORG Wed Jan 31 17:28:49 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6EBF316A400 for ; Wed, 31 Jan 2007 17:28:49 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id 315A113C478 for ; Wed, 31 Jan 2007 17:28:49 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 6AC009E0A9 for ; Wed, 31 Jan 2007 12:28:48 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Wed, 31 Jan 2007 12:28:48 -0500 X-Sasl-enc: G8sA44hXB7shrX6lFFqAtuzXO3X5qSx2jyxF5kToS+ET 1170264527 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 62AB522F4C for ; Wed, 31 Jan 2007 12:28:46 -0500 (EST) Message-ID: <45C0D1CD.8040107@FreeBSD.org> Date: Wed, 31 Jan 2007 17:28:45 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: net@FreeBSD.org References: <45C0CA5D.5090903@incunabulum.net> In-Reply-To: <45C0CA5D.5090903@incunabulum.net> Content-Type: multipart/mixed; boundary="------------050203030607070005000502" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: [TEST ATTACHED] Inconsistencies with IP_ONESBCAST and/or IP_SENDSRCADDR X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Jan 2007 17:28:49 -0000 This is a multi-part message in MIME format. --------------050203030607070005000502 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Thunderbird ate my homework. Reposting. --------------050203030607070005000502-- From owner-freebsd-net@FreeBSD.ORG Wed Jan 31 17:37:20 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 25E9A16A403 for ; Wed, 31 Jan 2007 17:37:20 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id F377513C494 for ; Wed, 31 Jan 2007 17:37:19 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 6EC289C9BA for ; Wed, 31 Jan 2007 12:37:19 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Wed, 31 Jan 2007 12:37:19 -0500 X-Sasl-enc: BVsO7c06P7IQ/YNYK6TlmHKBmMme8EIVSDzmcLov73og 1170265039 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 1610610595 for ; Wed, 31 Jan 2007 12:37:18 -0500 (EST) Message-ID: <45C0D3CD.5010701@FreeBSD.org> Date: Wed, 31 Jan 2007 17:37:17 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: net@FreeBSD.org References: <45C0CA5D.5090903@incunabulum.net> <45C0D1CD.8040107@FreeBSD.org> In-Reply-To: <45C0D1CD.8040107@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: [TEST ATTACHED] Inconsistencies with IP_ONESBCAST and/or IP_SENDSRCADDR X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Jan 2007 17:37:20 -0000 Bruce M. Simpson wrote: > Thunderbird ate my homework. Reposting. The FreeBSD mailing list server seems to drop my attachments, so I've uploaded it here: http://people.freebsd.org/~bms/dump/broadtest.c Regards, BMS From owner-freebsd-net@FreeBSD.ORG Wed Jan 31 20:40:22 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 831A816A401; Wed, 31 Jan 2007 20:40:22 +0000 (UTC) (envelope-from wollman@khavrinen.csail.mit.edu) Received: from khavrinen.csail.mit.edu (khavrinen.csail.mit.edu [128.30.28.20]) by mx1.freebsd.org (Postfix) with ESMTP id 1217D13C461; Wed, 31 Jan 2007 20:40:21 +0000 (UTC) (envelope-from wollman@khavrinen.csail.mit.edu) Received: from khavrinen.csail.mit.edu (localhost.csail.mit.edu [127.0.0.1]) by khavrinen.csail.mit.edu (8.13.6/8.13.6) with ESMTP id l0VK4vhk066310 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK CN=khavrinen.csail.mit.edu issuer=Client+20CA); Wed, 31 Jan 2007 15:04:58 -0500 (EST) (envelope-from wollman@khavrinen.csail.mit.edu) Received: (from wollman@localhost) by khavrinen.csail.mit.edu (8.13.6/8.13.6/Submit) id l0VK4vXC066309; Wed, 31 Jan 2007 15:04:57 -0500 (EST) (envelope-from wollman) Date: Wed, 31 Jan 2007 15:04:57 -0500 (EST) From: Garrett Wollman Message-Id: <200701312004.l0VK4vXC066309@khavrinen.csail.mit.edu> To: freebsd@j-davis.com In-Reply-To: <1170269163.22436.71.camel@dogma.v10.wvs> Organization: MIT Computer Science & Artificial Intelligence Laboratory X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-3.0 (khavrinen.csail.mit.edu [127.0.0.1]); Wed, 31 Jan 2007 15:04:58 -0500 (EST) Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: send() returns error even though data is sent, TCP connection still alive X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Jan 2007 20:40:22 -0000 In article <1170269163.22436.71.camel@dogma.v10.wvs>, Jeff Davis wrote: >You should see something like "write failed: host is down" and the >session will terminate. Of course, when ssh exits, the TCP connection >closes. The only way to see that it's still open and active is by >writing (or using) an application that ignores EHOSTDOWN errors from >write(). I agree that it's a bug. The only time write() on a stream socket should return the asynchronous error[1] is when the connection has been (or is in the process of being) torn down as a result of a subsequent timeout. POSIX says "may fail" for these errors write() and send() on sockets -GAWollman [1] There are two kinds of error returns in the socket model: synchronous errors, like synchronous signals, are attributed to the result of a specific system call, detected prior to syscall return, and usually represent programming or user error (e.g., attempting to connect() on an fd that is not a socket). Asynchronous errors are detected asynchronously, and merely posted to the socket without being delivered; they may be delivered on the next socket operation. See XSH 2.10.10, "Pending Error". From owner-freebsd-net@FreeBSD.ORG Wed Jan 31 21:11:32 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7D36216A402; Wed, 31 Jan 2007 21:11:32 +0000 (UTC) (envelope-from cedric@decemplex.net) Received: from mail.decemplex.net (mail.decemplex.net [80.237.247.202]) by mx1.freebsd.org (Postfix) with ESMTP id 3C19713C491; Wed, 31 Jan 2007 21:11:32 +0000 (UTC) (envelope-from cedric@decemplex.net) Received: from localhost (mail.decemplex.net [80.237.247.202]) by mail.decemplex.net (Postfix) with ESMTP id 0FA3C7D1649; Wed, 31 Jan 2007 21:47:15 +0100 (CET) X-Virus-Scanned: amavisd-new at decemplex.net Received: from mail.decemplex.net ([80.237.247.202]) by localhost (mail.decemplex.net [80.237.247.202]) (amavisd-new, port 10024) with LMTP id LiO7LEWQv003; Wed, 31 Jan 2007 21:47:14 +0100 (CET) Received: from decemplex.loc (83-178-112-217.dyn.adsl.belcenter.be [217.112.178.83]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.decemplex.net (Postfix) with ESMTP id 6C7B47D13E0; Wed, 31 Jan 2007 21:47:14 +0100 (CET) Date: Wed, 31 Jan 2007 21:47:05 +0100 From: =?ISO-8859-1?Q?C=E9dric?= Jonas To: freebsd-net@freebsd.org Message-ID: <20070131214705.0ee0ba67@ganymed> X-Mailer: Claws Mail 2.7.1 (GTK+ 2.10.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_GiTGV60xmr1k/UmjqFIRHoW"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-current@freebsd.org Subject: fxp(4) checksum (offloading?) errors X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2007 21:11:32 -0000 --Sig_GiTGV60xmr1k/UmjqFIRHoW Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, I get TCP/UDP checksum errors with fxp(4). I noticed it after using Wireshark today: Checksum: 0xac18 [incorrect, should be 0xfbc7 (maybe caused by checksum offloading?)] for example. If I understand it more or less correctly, checksum offloading is performed by or with help of the NIC - only for TCP and UDP, where the checksum fails exactly... I didn't found a way to disable it, so I assume it's a bug in the driver... I don't know exactly which infos I must provide additionally to the following, so don't hesitate to ask more :) Used NIC: fxp0: port 0xa400-0xa43f mem 0xfb030000-0xfb030fff,0xfb000000-0xfb01ffff irq 16 at device 7.0 on pci2 Used system: FreeBSD ganymed 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Sun Jan 21 16:07:51 CET 2007 root@ganymed:/usr/obj/usr/src/sys/GANYMED i386 --=20 C=E9dric Jonas cedric@decemplex.net GPG ID: 30CCFE8D GPG Key: http://box.decemplex.net/~cedric/cedric.key.asc GPG Fingerprint: CF03 E1FD 9428 1B6B E971 B107 9044 AA99 30CC FE8D Jabber-ID: cedric@decemplex.net --Sig_GiTGV60xmr1k/UmjqFIRHoW Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFwQBQkESqmTDM/o0RAkDdAKCCMGwdc+EMl/hhXTIOwW46w+zPBACfZrG+ 8zc1WUK4mH6T/gJR4yfetm0= =W8o8 -----END PGP SIGNATURE----- --Sig_GiTGV60xmr1k/UmjqFIRHoW-- From owner-freebsd-net@FreeBSD.ORG Wed Jan 31 21:40:58 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2914516A401 for ; Wed, 31 Jan 2007 21:40:58 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net [80.76.149.212]) by mx1.freebsd.org (Postfix) with ESMTP id AC5D513C491 for ; Wed, 31 Jan 2007 21:40:57 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from c83-253-29-241.bredband.comhem.se ([83.253.29.241]:51173 helo=falcon.midgard.homeip.net) by ch-smtp01.sth.basefarm.net with smtp (Exim 4.63) (envelope-from ) id 1HCMwA-0004wB-5J for freebsd-net@freebsd.org; Wed, 31 Jan 2007 22:24:14 +0100 Received: (qmail 29819 invoked from network); 31 Jan 2007 22:24:11 +0100 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with SMTP; 31 Jan 2007 22:24:11 +0100 Received: (qmail 86304 invoked by uid 1001); 31 Jan 2007 22:24:11 +0100 Date: Wed, 31 Jan 2007 22:24:11 +0100 From: Erik Trulsson To: =?iso-8859-1?Q?C=E9dric?= Jonas Message-ID: <20070131212411.GA86267@owl.midgard.homeip.net> Mail-Followup-To: =?iso-8859-1?Q?C=E9dric?= Jonas , freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <20070131214705.0ee0ba67@ganymed> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <20070131214705.0ee0ba67@ganymed> User-Agent: Mutt/1.5.13 (2006-08-11) X-Scan-Result: No virus found in message 1HCMwA-0004wB-5J. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1HCMwA-0004wB-5J 8edeaa7eda6f7ef52c92be5dcce43b71 Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: Re: fxp(4) checksum (offloading?) errors X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2007 21:40:58 -0000 On Wed, Jan 31, 2007 at 09:47:05PM +0100, C=E9dric Jonas wrote: > Hi, >=20 > I get TCP/UDP checksum errors with fxp(4). I noticed it after using > Wireshark today: >=20 > Checksum: 0xac18 [incorrect, should be 0xfbc7 (maybe caused by > checksum offloading?)] >=20 > for example. Is that for incoming or outgoing packets? If it is for outgoing it is perfectly normal and nothing to be worried about (assuming that your NIC does checksum offloading.) If it is for incoming packets it could be a real problem. >=20 > If I understand it more or less correctly, checksum offloading is > performed by or with help of the NIC - only for TCP and UDP, where the > checksum fails exactly... Checksum offloading means that the calculation of the checksum is done by the NIC instead of by the main CPU. For outgoing packets this means that wireshark or tcpdump and all similar programs see the packets before they have been handed over to the NIC, which means that the correct checksum has not yet been calculated and probably contains garbage. > I didn't found a way to disable it, so I assume it's a bug in the > driver... I don't know exactly which infos I must provide additionally > to the following, so don't hesitate to ask more :) >=20 > Used NIC: >=20 > fxp0: port 0xa400-0xa43f mem > 0xfb030000-0xfb030fff,0xfb000000-0xfb01ffff irq 16 at device > 7.0 on pci2 >=20 > Used system: >=20 > FreeBSD ganymed 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Sun Jan 21 > 16:07:51 CET 2007 > root@ganymed:/usr/obj/usr/src/sys/GANYMED i386 >=20 --=20 Erik Trulsson ertr1013@student.uu.se From owner-freebsd-net@FreeBSD.ORG Wed Jan 31 21:54:47 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7B95016A401; Wed, 31 Jan 2007 21:54:47 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: from syn.atarininja.org (syn.csh.rit.edu [129.21.60.158]) by mx1.freebsd.org (Postfix) with ESMTP id 5782513C471; Wed, 31 Jan 2007 21:54:47 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: by syn.atarininja.org (Postfix, from userid 1001) id 354F25C2E; Wed, 31 Jan 2007 16:25:34 -0500 (EST) Date: Wed, 31 Jan 2007 16:25:34 -0500 From: Wesley Shields To: C?dric Jonas Message-ID: <20070131212534.GC58404@atarininja.org> References: <20070131214705.0ee0ba67@ganymed> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070131214705.0ee0ba67@ganymed> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: Re: fxp(4) checksum (offloading?) errors X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2007 21:54:47 -0000 On Wed, Jan 31, 2007 at 09:47:05PM +0100, C?dric Jonas wrote: > Hi, > > I get TCP/UDP checksum errors with fxp(4). I noticed it after using > Wireshark today: > > Checksum: 0xac18 [incorrect, should be 0xfbc7 (maybe caused by > checksum offloading?)] > > for example. > > If I understand it more or less correctly, checksum offloading is > performed by or with help of the NIC - only for TCP and UDP, where the > checksum fails exactly... Yes, the checksums are offloaded to the card. Maybe I missed it, but you were not very clear on where you were seeing the invalid checksums. In the case of wireshark running on the machine which is doing the offloading then this makes sense as the checksums are computed AFTER wireshark sees them. The best way to know for sure if the checksums were computed correctly is to check them on the destination or somewhere along the wire to the destination. > I didn't found a way to disable it, so I assume it's a bug in the > driver... I don't know exactly which infos I must provide additionally > to the following, so don't hesitate to ask more :) According to ifconfig(8) they can be toggled using -rxcsum and -txcsum, but it is dependent upon the NIC/driver in use. A quick glance through fxp(4) indicates that it doesn't do checksum offloading. I'm sure someone will correct me if I am wrong. :) -- WXS From owner-freebsd-net@FreeBSD.ORG Wed Jan 31 22:00:19 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 24AAA16A400 for ; Wed, 31 Jan 2007 22:00:18 +0000 (UTC) (envelope-from freebsd@j-davis.com) Received: from servata.com (ip-216-152-249-241.servata.com [216.152.249.241]) by mx1.freebsd.org (Postfix) with ESMTP id D42F313C47E for ; Wed, 31 Jan 2007 22:00:16 +0000 (UTC) (envelope-from freebsd@j-davis.com) Received: from [209.162.219.253] (helo=dogma.v10.wvs) by servata.com with esmtpsa (TLS-1.0:RSA_ARCFOUR_MD5:16) (Exim 4.50) id 1HCNBS-00039C-Ti; Wed, 31 Jan 2007 13:40:03 -0800 From: Jeff Davis To: Garrett Wollman In-Reply-To: <200701312004.l0VK4vXC066309@khavrinen.csail.mit.edu> References: <200701312004.l0VK4vXC066309@khavrinen.csail.mit.edu> Content-Type: text/plain Date: Wed, 31 Jan 2007 13:40:04 -0800 Message-Id: <1170279604.22436.81.camel@dogma.v10.wvs> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: send() returns error even though data is sent, TCP connection still alive X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Jan 2007 22:00:19 -0000 On Wed, 2007-01-31 at 15:04 -0500, Garrett Wollman wrote: > In article <1170269163.22436.71.camel@dogma.v10.wvs>, > Jeff Davis wrote: > > >You should see something like "write failed: host is down" and the > >session will terminate. Of course, when ssh exits, the TCP connection > >closes. The only way to see that it's still open and active is by > >writing (or using) an application that ignores EHOSTDOWN errors from > >write(). > > I agree that it's a bug. The only time write() on a stream socket > should return the asynchronous error[1] is when the connection has > been (or is in the process of being) torn down as a result of a > subsequent timeout. POSIX says "may fail" for these errors write() > and send() on sockets > As far as I'm concerned, a fix for this bug is critical. We have had to move production apps off some of our freebsd servers. Regards, Jeff Davis From owner-freebsd-net@FreeBSD.ORG Wed Jan 31 22:06:11 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E716E16A408; Wed, 31 Jan 2007 22:06:11 +0000 (UTC) (envelope-from cedric@decemplex.net) Received: from mail.decemplex.net (mail.decemplex.net [80.237.247.202]) by mx1.freebsd.org (Postfix) with ESMTP id 78A3C13C4C3; Wed, 31 Jan 2007 22:06:11 +0000 (UTC) (envelope-from cedric@decemplex.net) Received: from localhost (mail.decemplex.net [80.237.247.202]) by mail.decemplex.net (Postfix) with ESMTP id 9D90D7D1962; Wed, 31 Jan 2007 23:06:10 +0100 (CET) X-Virus-Scanned: amavisd-new at decemplex.net Received: from mail.decemplex.net ([80.237.247.202]) by localhost (mail.decemplex.net [80.237.247.202]) (amavisd-new, port 10024) with LMTP id C-6nNJmYmV-1; Wed, 31 Jan 2007 23:06:10 +0100 (CET) Received: from decemplex.loc (83-178-112-217.dyn.adsl.belcenter.be [217.112.178.83]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.decemplex.net (Postfix) with ESMTP id DA21A7D193C; Wed, 31 Jan 2007 23:06:09 +0100 (CET) Date: Wed, 31 Jan 2007 23:05:40 +0100 From: =?ISO-8859-1?Q?C=E9dric?= Jonas To: Erik Trulsson Message-ID: <20070131230540.2141488e@ganymed> In-Reply-To: <20070131212411.GA86267@owl.midgard.homeip.net> References: <20070131214705.0ee0ba67@ganymed> <20070131212411.GA86267@owl.midgard.homeip.net> X-Mailer: Claws Mail 2.7.1 (GTK+ 2.10.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_s.kHoGYz7ohP5cloys5DPiM; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: Re: fxp(4) checksum (offloading?) errors X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2007 22:06:12 -0000 --Sig_s.kHoGYz7ohP5cloys5DPiM Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Wed, 31 Jan 2007 22:24:11 +0100 Erik Trulsson wrote: > On Wed, Jan 31, 2007 at 09:47:05PM +0100, C=E9dric Jonas wrote: > > Hi, > >=20 > > I get TCP/UDP checksum errors with fxp(4). I noticed it after using > > Wireshark today: > >=20 > > Checksum: 0xac18 [incorrect, should be 0xfbc7 (maybe caused > > by checksum offloading?)] > >=20 > > for example. >=20 > Is that for incoming or outgoing packets? If it is for outgoing it is > perfectly normal and nothing to be worried about (assuming that your > NIC does checksum offloading.) Arghs, shame on me. You are fully right... I needed to know it, my first mail contains quasi the reason of the "bug" :)=20 However, thank you! >=20 > If it is for incoming packets it could be a real problem. >=20 >=20 > >=20 > > If I understand it more or less correctly, checksum offloading is > > performed by or with help of the NIC - only for TCP and UDP, where > > the checksum fails exactly... >=20 > Checksum offloading means that the calculation of the checksum is > done by the NIC instead of by the main CPU. For outgoing packets > this means that wireshark or tcpdump and all similar programs see the > packets before they have been handed over to the NIC, which means > that the correct checksum has not yet been calculated and probably > contains garbage. >=20 >=20 > > I didn't found a way to disable it, so I assume it's a bug in the > > driver... I don't know exactly which infos I must provide > > additionally to the following, so don't hesitate to ask more :) > >=20 > > Used NIC: > >=20 > > fxp0: port 0xa400-0xa43f mem > > 0xfb030000-0xfb030fff,0xfb000000-0xfb01ffff irq 16 at device > > 7.0 on pci2 > >=20 > > Used system: > >=20 > > FreeBSD ganymed 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Sun Jan > > 21 16:07:51 CET 2007 > > root@ganymed:/usr/obj/usr/src/sys/GANYMED i386 > >=20 >=20 >=20 >=20 >=20 --=20 C=E9dric Jonas cedric@decemplex.net Mobile Phone: (32-494) 08 92 64 GPG ID: 30CCFE8D GPG Key: http://box.decemplex.net/~cedric/cedric.key.asc GPG Fingerprint: CF03 E1FD 9428 1B6B E971 B107 9044 AA99 30CC FE8D Jabber-ID: cedric@decemplex.net --Sig_s.kHoGYz7ohP5cloys5DPiM Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFwRLQkESqmTDM/o0RAg/EAJ9oqW84KKbOWTfp36blRvvBl1PESwCdFeqE 5DGJU9ooRX5ChM6R0AW9P3I= =nBDS -----END PGP SIGNATURE----- --Sig_s.kHoGYz7ohP5cloys5DPiM-- From owner-freebsd-net@FreeBSD.ORG Wed Jan 31 22:48:53 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 311DE16A403 for ; Wed, 31 Jan 2007 22:48:53 +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 B5F1313C46B for ; Wed, 31 Jan 2007 22:48:52 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from c83-253-29-241.bredband.comhem.se ([83.253.29.241]:56778 helo=falcon.midgard.homeip.net) by ch-smtp02.sth.basefarm.net with smtp (Exim 4.63) (envelope-from ) id 1HCOG3-0002Vs-8s for freebsd-net@freebsd.org; Wed, 31 Jan 2007 23:48:51 +0100 Received: (qmail 30419 invoked from network); 31 Jan 2007 23:48:49 +0100 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with SMTP; 31 Jan 2007 23:48:49 +0100 Received: (qmail 86910 invoked by uid 1001); 31 Jan 2007 23:48:49 +0100 Date: Wed, 31 Jan 2007 23:48:49 +0100 From: Erik Trulsson To: Wesley Shields Message-ID: <20070131224849.GA86858@owl.midgard.homeip.net> Mail-Followup-To: Wesley Shields , C?dric Jonas , freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <20070131214705.0ee0ba67@ganymed> <20070131212534.GC58404@atarininja.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070131212534.GC58404@atarininja.org> User-Agent: Mutt/1.5.13 (2006-08-11) X-Scan-Result: No virus found in message 1HCOG3-0002Vs-8s. X-Scan-Signature: ch-smtp02.sth.basefarm.net 1HCOG3-0002Vs-8s 24e988f5f4e6b1ae9e28fba7c066a46b Cc: C?dric Jonas , freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: Re: fxp(4) checksum (offloading?) errors X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2007 22:48:53 -0000 On Wed, Jan 31, 2007 at 04:25:34PM -0500, Wesley Shields wrote: > On Wed, Jan 31, 2007 at 09:47:05PM +0100, C?dric Jonas wrote: > > Hi, > > > > I get TCP/UDP checksum errors with fxp(4). I noticed it after using > > Wireshark today: > > > > Checksum: 0xac18 [incorrect, should be 0xfbc7 (maybe caused by > > checksum offloading?)] > > > > for example. > > > > If I understand it more or less correctly, checksum offloading is > > performed by or with help of the NIC - only for TCP and UDP, where the > > checksum fails exactly... > > Yes, the checksums are offloaded to the card. Maybe I missed it, but > you were not very clear on where you were seeing the invalid checksums. > In the case of wireshark running on the machine which is doing the > offloading then this makes sense as the checksums are computed AFTER > wireshark sees them. The best way to know for sure if the checksums > were computed correctly is to check them on the destination or somewhere > along the wire to the destination. > > > I didn't found a way to disable it, so I assume it's a bug in the > > driver... I don't know exactly which infos I must provide additionally > > to the following, so don't hesitate to ask more :) > > According to ifconfig(8) they can be toggled using -rxcsum and -txcsum, > but it is dependent upon the NIC/driver in use. A quick glance through > fxp(4) indicates that it doesn't do checksum offloading. I'm sure > someone will correct me if I am wrong. :) Some fxp(4) NICs support checksum offloading, but most don't. The fairly common 82559 controller chip does not support checksum offloading. The 82550 (which can be found on the Intel PRO/100 S cards) does support checksum offloading. -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-net@FreeBSD.ORG Wed Jan 31 22:59:07 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C3D7816A402; Wed, 31 Jan 2007 22:59:07 +0000 (UTC) (envelope-from flz@FreeBSD.org) Received: from postfix1-g20.free.fr (postfix1-g20.free.fr [212.27.60.42]) by mx1.freebsd.org (Postfix) with ESMTP id 4F3A713C491; Wed, 31 Jan 2007 22:59:07 +0000 (UTC) (envelope-from flz@FreeBSD.org) Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by postfix1-g20.free.fr (Postfix) with ESMTP id 6E7658C86BE; Wed, 31 Jan 2007 23:35:57 +0100 (CET) Received: from smtp.xbsd.org (unknown [82.233.2.192]) by smtp3-g19.free.fr (Postfix) with ESMTP id A5AD34A250; Wed, 31 Jan 2007 23:35:55 +0100 (CET) Received: from localhost (localhost.xbsd.org [127.0.0.1]) by smtp.xbsd.org (Postfix) with ESMTP id E4B9211806; Wed, 31 Jan 2007 23:35:54 +0100 (CET) X-Virus-Scanned: amavisd-new at xbsd.org Received: from smtp.xbsd.org ([127.0.0.1]) by localhost (srv1.xbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R1mLQNpX1JgJ; Wed, 31 Jan 2007 23:35:49 +0100 (CET) Received: from [193.120.13.130] (cream.xbsd.org [193.120.13.130]) by smtp.xbsd.org (Postfix) with ESMTP id 9E9A81164F; Wed, 31 Jan 2007 23:35:48 +0100 (CET) Message-ID: <45C118FB.6070208@FreeBSD.org> Date: Wed, 31 Jan 2007 22:32:27 +0000 From: Florent Thoumie User-Agent: Thunderbird 1.5.0.9 (X11/20070122) MIME-Version: 1.0 To: freebsd-pf@FreeBSD.org X-Enigmail-Version: 0.94.1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enigE96306D3B08E091DD9728ADA" Cc: freebsd-net@FreeBSD.org, Roman Divacky , freebsd-ports@FreeBSD.org Subject: RFC: net/hoststated port - Host status for server load-balancing X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 31 Jan 2007 22:59:07 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE96306D3B08E091DD9728ADA Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I took a few minutes to make a port of it after Roman Divacky sent me an initial patchset for it. I made sure that it compiled/installed fine but don't have the chance to test it now. For those who don't know yet about hoststated: hoststated is the host status daemon for server load balancing. Its main purpose is to keep pf(4) tables up to date as well as any related pf rdr rules. To communicate with pf, hoststated uses the anchor facility. To enable hoststated to install rulesets through the anchor, the following line is required in the NAT section of pf.conf(5). It is written by Pierre-Yves Ritschard and it has been recently added (and linked to the build) in the OpenBSD source tree. You can find the port here (both extracted and in shell archive format): http://people.freebsd.org/~flz/local/ports/ PS: Apologies to those who will receive more than once this email due to cross-mailing. --=20 Florent Thoumie flz@FreeBSD.org FreeBSD Committer --------------enigE96306D3B08E091DD9728ADA 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.5 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFwRkAMxEkbVFH3PQRCl1yAJ43bbKvjYj4uR0zjB/ZwOt25lopTQCdFbNh pzzaTjwo++1ZJP/Sbhz5jH0= =dexH -----END PGP SIGNATURE----- --------------enigE96306D3B08E091DD9728ADA-- From owner-freebsd-net@FreeBSD.ORG Thu Feb 1 01:32:59 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 65C0B16A400 for ; Thu, 1 Feb 2007 01:32:59 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id 41AC313C47E for ; Thu, 1 Feb 2007 01:32:54 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 6D30B9DD7D for ; Wed, 31 Jan 2007 20:32:53 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Wed, 31 Jan 2007 20:32:53 -0500 X-Sasl-enc: sZ6mbNxgzDU/I+gT5XC4rKdXax1wVpuHa0Wiwtt1n3Kc 1170293573 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 0E7B010541 for ; Wed, 31 Jan 2007 20:32:52 -0500 (EST) Message-ID: <45C14343.3020401@incunabulum.net> Date: Thu, 01 Feb 2007 01:32:51 +0000 From: Bruce M Simpson User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: net@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: [PATCH] Zeroconf: avahi-autoipd support for FreeBSD X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Feb 2007 01:32:59 -0000 Hello, As you probably all know, I have been endeavouring to do something about the lack of Zeroconf support. Today, I've spent a while hacking out a diff to get Avahi's autoipd to run on FreeBSD: http://people.freebsd.org/~bms/dump/avahi-autoipd.diff Comments and feedback, particularly more in-depth testing by another contributor, are very welcome. I have tested this on my local 802.11 wireless segment with ath(4). Before this can be committed to ports or pushed upstream, it is missing an rc script. Regards, BMS From owner-freebsd-net@FreeBSD.ORG Thu Feb 1 15:56:06 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 37EE616A406 for ; Thu, 1 Feb 2007 15:56:06 +0000 (UTC) (envelope-from wishmaster@velnet.ru) Received: from mail.velnet.ru (mail.velnet.ru [88.210.53.179]) by mx1.freebsd.org (Postfix) with ESMTP id EE67713C478 for ; Thu, 1 Feb 2007 15:56:05 +0000 (UTC) (envelope-from wishmaster@velnet.ru) Received: from [212.30.154.174] (helo=localhost) by mail.velnet.ru with esmtp (Exim 4.30; FreeBSD) id 1HCeN7-000F3p-Dj; Thu, 01 Feb 2007 19:01:13 +0300 Date: Thu, 1 Feb 2007 18:57:59 +0300 From: Wishmaster X-Mailer: The Bat! (v2.12.00) X-Priority: 3 (Normal) Message-ID: <1174639496.20070201185759@velnet.ru> To: Alex Povolotsky In-Reply-To: <45C08019.1030105@webmail.sub.ru> References: <45C08019.1030105@webmail.sub.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: mpd locking system? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Wishmaster List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2007 15:56:06 -0000 Hello Alex, Wednesday, January 31, 2007, 2:40:09 PM, you wrote: AP> Hello! AP> for about 4-5 days, I'm expeirencing heavy troubles with my VPN (mpd) AP> 6.1-RELEASE based server. AP> After some time (minimum 2 seconds, maximum 12 hours) of running MPD AP> with moderate load (about 100-200 clients, CPU not overused), system AP> locks (even keyboard hangs) to reset. Nothing at all in logs. AP> Patching kernel to 6.1p12 did not help. AP> Attempt to add kern.ipc.nmbclusters="0" to /boot/loader.conf did not AP> change anything. AP> The box seems to be healthy (at least, CPU fan works ok, no symptoms of AP> overheating at all). It has run under more load without a flaw. AP> I hope someone can help. AP> Alex. AP> _______________________________________________ AP> freebsd-net@freebsd.org mailing list AP> http://lists.freebsd.org/mailman/listinfo/freebsd-net AP> To unsubscribe, send any mail to AP> "freebsd-net-unsubscribe@freebsd.org" What freebsd distribution and mpd release you are using? Do you have SMP kernel ? So, uname -a && mpd -v (or mpd4 -v) I have freebsd 6.1R/amd64 +mpd4 x900 tunnels. Uptime more then 6 month. i.e. no problems. -- Best regards, Wishmaster mailto:wishmaster@velnet.ru From owner-freebsd-net@FreeBSD.ORG Thu Feb 1 16:48:02 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3DB7016A401 for ; Thu, 1 Feb 2007 16:48:02 +0000 (UTC) (envelope-from ericx@vineyard.net) Received: from smtp1.vineyard.net (a1.vineyard.net [204.17.195.95]) by mx1.freebsd.org (Postfix) with ESMTP id 0914E13C494 for ; Thu, 1 Feb 2007 16:48:01 +0000 (UTC) (envelope-from ericx@vineyard.net) Received: from localhost (loopback [127.0.0.1]) by smtp1.vineyard.net (Postfix) with ESMTP id 250EB158180B; Thu, 1 Feb 2007 11:48:01 -0500 (EST) Received: from smtp1.vineyard.net ([127.0.0.1]) by localhost (ace1.vineyard.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 47831-01-2; Thu, 1 Feb 2007 11:47:54 -0500 (EST) Received: from [204.17.195.104] (fortiva.vineyard.net [204.17.195.104]) by smtp1.vineyard.net (Postfix) with ESMTP id 04384158189A; Thu, 1 Feb 2007 11:47:14 -0500 (EST) Message-ID: <45C21979.2080002@vineyard.net> Date: Thu, 01 Feb 2007 11:46:49 -0500 From: "Eric W. Bates" User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: ashoke saha References: <816104.21070.qm@web51907.mail.yahoo.com> In-Reply-To: <816104.21070.qm@web51907.mail.yahoo.com> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS-ace1 at Vineyard.NET Cc: freebsd-net@freebsd.org Subject: Re: About NAT Traversal X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Feb 2007 16:48:02 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ashoke saha wrote: > basic kame (racoon) as NAT_T for IKE. It did not have > kernel support till 6.0. you can take the patch from > there. > also NAT_T has moved from draft to RFC and do google > for NAT_T to get get the RFC's and also read the code > in the kernel patch and racoon. Thank you. I have installed the patch; but I suspect that deciphering the code is beyond my skill level. RFC 3948 is mentioned. I will start there. > assuming you are talking about ipsec NAT_T. Yes, we want to implement end-to-end esp rather than > ashoke. > > --- Darren Pilgrim wrote: > >> Eric W. Bates wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> Can someone please refer me to some documentation >> describing how to >>> implement NAT Traversal? >> In what context? The methods required to traverse a >> NAT are highly >> protocol-specific. >> >> -- >> Darren Pilgrim >> _______________________________________________ >> 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" >> > > > > > ____________________________________________________________________________________ > Be a PS3 game guru. > Get your game face on with the latest PS3 news and previews at Yahoo! Games. > http://videogames.yahoo.com/platform?platform=120121 > > - -- Eric W. Bates ericx@vineyard.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFwhl5D1roJTQ4LlERAsxrAJ9eNB6ZgR8tbAb1Iq+oIDpusX07SgCfZSY9 zaOJ0A+hBpNRaQt10TAUJ3k= =h3AY -----END PGP SIGNATURE----- From owner-freebsd-net@FreeBSD.ORG Thu Feb 1 16:57:58 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 08B4E16A400 for ; Thu, 1 Feb 2007 16:57:58 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from smtp.zeninc.net (reverse-25.fdn.fr [80.67.176.25]) by mx1.freebsd.org (Postfix) with ESMTP id C530E13C4A7 for ; Thu, 1 Feb 2007 16:57:57 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: by smtp.zeninc.net (smtpd, from userid 1000) id 0546E3F17; Thu, 1 Feb 2007 17:57:55 +0100 (CET) Date: Thu, 1 Feb 2007 17:57:55 +0100 From: VANHULLEBUS Yvan To: freebsd-net@freebsd.org Message-ID: <20070201165755.GC14658@zen.inc> References: <816104.21070.qm@web51907.mail.yahoo.com> <45C21979.2080002@vineyard.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45C21979.2080002@vineyard.net> User-Agent: All mail clients suck. This one just sucks less. Subject: Re: About NAT Traversal X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Feb 2007 16:57:58 -0000 On Thu, Feb 01, 2007 at 11:46:49AM -0500, Eric W. Bates wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > ashoke saha wrote: > > basic kame (racoon) as NAT_T for IKE. It did not have > > kernel support till 6.0. you can take the patch from > > there. > > also NAT_T has moved from draft to RFC and do google > > for NAT_T to get get the RFC's and also read the code > > in the kernel patch and racoon. > > Thank you. I have installed the patch; but I suspect that deciphering > the code is beyond my skill level. RFC 3948 is mentioned. I will start > there. Hi. You probably don't really need to "decipher" that code, you'll just need the skill level required to apply a patch to the kernel sources and recompile your kernel (and recompiling your world is also probably a good idea), then install the new headers (mainly /usr/include/net/pfkeyv2.h). Then you'll just have to recompile/reinstall ipsec-tools port, which will autodetect NAT-T support (to be more exact, which will detect that your /usr/include/net/pfkeyv2.h has the required structs for NAT-T support) and which will be recompiled with such support. Yvan. -- NETASQ http://www.netasq.com From owner-freebsd-net@FreeBSD.ORG Thu Feb 1 14:58:49 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 583C616A402 for ; Thu, 1 Feb 2007 14:58:49 +0000 (UTC) (envelope-from aronesimi@yahoo.com) Received: from web58602.mail.re3.yahoo.com (web58602.mail.re3.yahoo.com [68.142.236.200]) by mx1.freebsd.org (Postfix) with SMTP id 0E5DB13C48E for ; Thu, 1 Feb 2007 14:58:48 +0000 (UTC) (envelope-from aronesimi@yahoo.com) Received: (qmail 63780 invoked by uid 60001); 1 Feb 2007 14:58:46 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=b3kRjal/3FvT2sUEUJwgCmD9jSsILtZHiCmqkiaYzlwGZGZPnou2B4FjzxLV8p3iPAZQo7g3+pv6OlIjMphqepsM8cUaWV+IX+kVvr2Vhhmq7WAdoqRnZ2UgQvucqSXGTIxRiA93p5dCr4c3Vy6wALi6ZHbCR7E0ju1Em68i2gc=; X-YMail-OSG: 3ODQmw8VM1lT9m1hS7_G1zaAnzizD1iDmgmIU4Jp7_InYVHqQVR_abvzVumhet8mA5K7xaptBQi4BTfCzyuvq1Mp1xgftpanPcsxrpufJCG4GgaBXjDplc3hmR_DJpjl Received: from [75.72.230.91] by web58602.mail.re3.yahoo.com via HTTP; Thu, 01 Feb 2007 06:58:46 PST Date: Thu, 1 Feb 2007 06:58:46 -0800 (PST) From: Arone Silimantia To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <265849.63502.qm@web58602.mail.re3.yahoo.com> X-Mailman-Approved-At: Thu, 01 Feb 2007 19:09:41 +0000 Subject: Re: ipfw pipe show ... help with output is needed, please. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Feb 2007 14:58:49 -0000 > > Second, there are seven headings (from BKT at the left to Drp on the > > right) but underneath those seven headings are _9_ values. What I really > > want to know is how many packets I am droppinig ... but I can't tell which > > of the fields are the "dropped" - I assume it is the final number .. if > > so, what is that measured in ? Packets ? > > I can't help you with the rest of it, as I am frequently just as baffled > by ipfw/dummynet as the next man .. > > But the 7/9 thing I can explain. > > Tot_pkt: 2970975653 > bytes: 2649647615805 > > Pkt: 2 > Byte: 2992 Ok, thank you - and then the final number in the output is the number of dropped _packets_, right ? (snip 'ipfw pipe list' paste) > Trust me: there will be a lot more connections set up in those pipes than > that. I think it's just showing a snapshot. Or I have got it all > completely wrong and it's not actually working at all like I thought it > ought. > > Who knows? Can anyone clarify this ? Is 'ipfw pipe list' just showing a snapshot, and when I see it listing a "protocol", and port numbers, etc., it is still applying to _all_ IP traffic, as I have my ipfw rule phrased: "from any to any" ? Because I really want this dummynet pipe to throttle _all_ traffic, and I only ever see it listing a "tcp" protocol, and showing a tcp port number... My second question was: - what happens to the packets that show up in the "Drp" column ? Am I losing connections/data/traffic, or do those just get resent/reworked and nobody really notices ? ____________________________________________________________________________________ Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com From owner-freebsd-net@FreeBSD.ORG Thu Feb 1 19:12:56 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0E8BD16A400 for ; Thu, 1 Feb 2007 19:12:56 +0000 (UTC) (envelope-from ericx@vineyard.net) Received: from smtp1.vineyard.net (a1.vineyard.net [204.17.195.95]) by mx1.freebsd.org (Postfix) with ESMTP id D733013C4BA for ; Thu, 1 Feb 2007 19:12:55 +0000 (UTC) (envelope-from ericx@vineyard.net) Received: from localhost (loopback [127.0.0.1]) by smtp1.vineyard.net (Postfix) with ESMTP id 519C71581846; Thu, 1 Feb 2007 14:12:55 -0500 (EST) Received: from smtp1.vineyard.net ([127.0.0.1]) by localhost (ace1.vineyard.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 57832-04-6; Thu, 1 Feb 2007 14:12:50 -0500 (EST) Received: from [204.17.195.104] (fortiva.vineyard.net [204.17.195.104]) by smtp1.vineyard.net (Postfix) with ESMTP id 9F179158186A; Thu, 1 Feb 2007 14:12:47 -0500 (EST) Message-ID: <45C23B97.8050402@vineyard.net> Date: Thu, 01 Feb 2007 14:12:23 -0500 From: "Eric W. Bates" User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: VANHULLEBUS Yvan References: <816104.21070.qm@web51907.mail.yahoo.com> <45C21979.2080002@vineyard.net> <20070201165755.GC14658@zen.inc> In-Reply-To: <20070201165755.GC14658@zen.inc> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS-ace1 at Vineyard.NET Cc: freebsd-net@freebsd.org Subject: Re: About NAT Traversal X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Feb 2007 19:12:56 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 VANHULLEBUS Yvan wrote: > On Thu, Feb 01, 2007 at 11:46:49AM -0500, Eric W. Bates wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> ashoke saha wrote: >>> basic kame (racoon) as NAT_T for IKE. It did not have >>> kernel support till 6.0. you can take the patch from >>> there. >>> also NAT_T has moved from draft to RFC and do google >>> for NAT_T to get get the RFC's and also read the code >>> in the kernel patch and racoon. >> Thank you. I have installed the patch; but I suspect that deciphering >> the code is beyond my skill level. RFC 3948 is mentioned. I will start >> there. > > Hi. > > You probably don't really need to "decipher" that code, you'll just > need the skill level required to apply a patch to the kernel sources > and recompile your kernel (and recompiling your world is also probably > a good idea), then install the new headers (mainly > /usr/include/net/pfkeyv2.h). > > > Then you'll just have to recompile/reinstall ipsec-tools port, which > will autodetect NAT-T support (to be more exact, which will detect > that your /usr/include/net/pfkeyv2.h has the required structs for > NAT-T support) and which will be recompiled with such support. Great. thanks. I've already got the new kernel; but I neglected to rebuild racoon. I will try that. > > Yvan. > - -- Eric W. Bates ericx@vineyard.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFwjuWD1roJTQ4LlERAv8DAKCYom6NqQaYoASRpXdDjVeNHXVUugCfSKzD SAXJ9YEoiPG0ZZvRxsrLxHY= =NV9F -----END PGP SIGNATURE----- From owner-freebsd-net@FreeBSD.ORG Thu Feb 1 21:36:10 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8724316A400 for ; Thu, 1 Feb 2007 21:36:10 +0000 (UTC) (envelope-from wishmaster@velnet.ru) Received: from mail.velnet.ru (mail.velnet.ru [88.210.53.179]) by mx1.freebsd.org (Postfix) with ESMTP id 4BE8C13C48D for ; Thu, 1 Feb 2007 21:36:10 +0000 (UTC) (envelope-from wishmaster@velnet.ru) Received: from [212.30.154.174] (helo=localhost) by mail.velnet.ru with esmtp (Exim 4.30; FreeBSD) id 1HCjgJ-000IMN-1v; Fri, 02 Feb 2007 00:41:23 +0300 Date: Fri, 2 Feb 2007 00:38:08 +0300 From: Wishmaster X-Mailer: The Bat! (v2.12.00) X-Priority: 3 (Normal) Message-ID: <572119228.20070202003808@velnet.ru> To: freebsd-net@freebsd.org In-Reply-To: <45C08019.1030105@webmail.sub.ru> References: <45C08019.1030105@webmail.sub.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Alex Povolotsky Subject: Re: mpd locking system? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Wishmaster List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2007 21:36:10 -0000 Hello Alex, Wednesday, January 31, 2007, 2:40:09 PM, you wrote: AP> Hello! AP> for about 4-5 days, I'm expeirencing heavy troubles with my VPN (mpd) AP> 6.1-RELEASE based server. AP> After some time (minimum 2 seconds, maximum 12 hours) of running MPD AP> with moderate load (about 100-200 clients, CPU not overused), system AP> locks (even keyboard hangs) to reset. Nothing at all in logs. AP> Patching kernel to 6.1p12 did not help. AP> Attempt to add kern.ipc.nmbclusters="0" to /boot/loader.conf did not AP> change anything. AP> The box seems to be healthy (at least, CPU fan works ok, no symptoms of AP> overheating at all). It has run under more load without a flaw. AP> I hope someone can help. AP> Alex. AP> _______________________________________________ AP> freebsd-net@freebsd.org mailing list AP> http://lists.freebsd.org/mailman/listinfo/freebsd-net AP> To unsubscribe, send any mail to AP> "freebsd-net-unsubscribe@freebsd.org" What freebsd distribution and mpd release you are using? Do you have SMP kernel ? So, uname -a && mpd -v (or mpd4 -v) I have freebsd 6.1R/amd64 +mpd4 x900 tunnels. Uptime more then 6 month. i.e. no problems. -- Best regards, Wishmaster mailto:wishmaster@velnet.ru From owner-freebsd-net@FreeBSD.ORG Thu Feb 1 23:53:31 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 49ECC16A401 for ; Thu, 1 Feb 2007 23:53:31 +0000 (UTC) (envelope-from david.baukus@us.fujitsu.com) Received: from fujitsu0.fujitsu.com (fujitsu0.fujitsu.com [192.240.0.5]) by mx1.freebsd.org (Postfix) with ESMTP id 2BE9213C494 for ; Thu, 1 Feb 2007 23:53:31 +0000 (UTC) (envelope-from david.baukus@us.fujitsu.com) Received: from fujitsu0.fujitsu.com (localhost [127.0.0.1]) by fujitsu0.fujitsu.com (8.13.7/8.13.7) with ESMTP id l11NOlF5005214 for ; Thu, 1 Feb 2007 15:24:47 -0800 (PST) Received: from fujitsu7i.fnanic.fujitsu.com ([133.164.253.7]) by fujitsu0.fujitsu.com (8.13.7/8.13.7) with ESMTP id l11NOkec005206 for ; Thu, 1 Feb 2007 15:24:46 -0800 (PST) Received: from fncnmp01.fnc.fujitsu.com (localhost [127.0.0.1]) by fujitsu7i.fnanic.fujitsu.com (8.13.7/8.13.7) with ESMTP id l11NOaoC026372 for ; Thu, 1 Feb 2007 15:24:45 -0800 (PST) Received: from unknown (HELO equinox.tx.fnc.fujitsu.com) ([167.254.252.122]) by fncnmp01.fnc.fujitsu.com with ESMTP; 01 Feb 2007 17:23:13 -0600 X-IronPort-AV: i="4.13,269,1167631200"; d="scan'208"; a="88965383:sNHT121823284" Received: from nomad.tx.fnc.fujitsu.com (localhost [127.0.0.1]) by equinox.tx.fnc.fujitsu.com (8.13.7+Sun/8.13.7) with ESMTP id l11NNDGU001231; Thu, 1 Feb 2007 17:23:13 -0600 (CST) Received: from tdd2172.tddeng00.fnts.com (tdd2172.tddeng00.fnts.com [167.254.250.128]) by nomad.tx.fnc.fujitsu.com (8.13.7+Sun/8.13.7) with ESMTP id l11NN8NT017423; Thu, 1 Feb 2007 17:23:08 -0600 (CST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by tdd2172.tddeng00.fnts.com (8.11.7p3+Sun/8.11.7) with ESMTP id l11NN8G09935; Thu, 1 Feb 2007 17:23:08 -0600 (CST) Message-ID: <45C2765C.7010708@us.fujitsu.com> Date: Thu, 01 Feb 2007 17:23:08 -0600 From: Dave Baukus User-Agent: Mozilla Thunderbird 1.0 (X11/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Baukus, David" Subject: ETIMEDOUT bug X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Feb 2007 23:53:31 -0000 There is a bug tcp_output() for at least freeBSD6.1 that causes a perfectly good TCP to be dropped by its retransmit timer; the application receives ETIMEDOUT. Consider a TCP that never transmits (the receive end of the ttcp utility is an example), while the TCP is established snd_max == snd_una == snd_nxt == (isr + 1) and the retransmit timer should never be started. If the retransmit timer is started then it is never stopped by tcp_input/tcp_out because snd_max == snd_una == snd_nxt (always). Once started the timer continues its count up till tp->t_rxtshift == 12 and the connection that never transmitted gets falsely killed. The bug is to blindly rely on the return value of ip_output(). If ip_output() returns ENOBUFS then the retransmit timer is activated: From the end of tcp_output(): out: SOCKBUF_UNLOCK_ASSERT(&so->so_snd); /* Check gotos. */ if (error == ENOBUFS) { if (!callout_active(tp->tt_rexmt) && !callout_active(tp->tt_persist)) callout_reset(tp->tt_rexmt, tp->t_rxtcur, tcp_timer_rexmt, tp); tp->snd_cwnd = tp->t_maxseg; return (0); } My simple minded fix would be not to start the retransmit timer; if tcp_output() wanted to time this transmit it would have started the timer up above. This ETIMEDOUT problem is easily recreated on any old machine using a single slow ethernet device and the ttcp test utility. First, fire up a couple ttcp receivers. Second, flood the same interface with enough ttcp transmitters to cause the driver's transmit ring and interface queue to back up. Eventually, one of the ttcp receives will get ENOBUFS from ip_output() and the retransmit timer will be wrongly activated for a pure ACK segment. I was able to do it w/ the following on freeBSD6.1: box1: ttcp -s -l 16384 -p 9444 -v -b 128000 -r ttcp -s -l 16384 -p 9445 -v -b 128000 -r ttcp -s -n 6553600 -l 4096 -p 9446 -v -b 128000 -t 192.168.222.13 ttcp -s -n 9999999 -l 333 -p 9447 -v -b 128000 -t 192.168.222.13 ttcp -s -n 9999999 -l 8192 -p 9448 -v -b 128000 -t 192.168.222.13 ttcp -s -n 9999999 -l 333 -p 9449 -v -b 128000 -t 192.168.222.13 ttcp -s -n 9999999 -l 8192 -p 9450 -v -b 128000 -t 192.168.222.13 box2: ttcp -s -n 6553600 -l 8192 -p 9444 -v -b 128000 -t 192.168.222.222 ttcp -s -n 9999999 -l 128 -p 9445 -v -b 128000 -t 192.168.222.222 ttcp -s -l 16384 -p 9446 -v -b 128000 -r ttcp -s -l 16384 -p 9447 -v -b 128000 -r ttcp -s -l 16384 -p 9448 -v -b 128000 -r ttcp -s -l 16384 -p 9449 -v -b 128000 -r ttcp -s -l 16384 -p 9450 -v -b 128000 -r -- Dave Baukus david.baukus@us.fujitsu.com Fujitsu Network Communications Richardson, Texas USA From owner-freebsd-net@FreeBSD.ORG Fri Feb 2 02:59:11 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7FFC116A402 for ; Fri, 2 Feb 2007 02:59:11 +0000 (UTC) (envelope-from ml@t-b-o-h.net) Received: from vjofn.tucs-beachin-obx-house.com (vjofn.tucs-beachin-obx-house.com [204.107.90.128]) by mx1.freebsd.org (Postfix) with ESMTP id 3F2AC13C48D for ; Fri, 2 Feb 2007 02:59:11 +0000 (UTC) (envelope-from ml@t-b-o-h.net) Received: from himinbjorg.tucs-beachin-obx-house.com (cpe-72-225-142-211.hvc.res.rr.com [72.225.142.211]) (authenticated bits=0) by vjofn.tucs-beachin-obx-house.com (8.12.9/8.12.9) with ESMTP id l122eSQe072180 for ; Thu, 1 Feb 2007 21:40:28 -0500 (EST) Received: from himinbjorg.tucs-beachin-obx-house.com (localhost.tucs-beachin-obx-house.com [127.0.0.1]) by himinbjorg.tucs-beachin-obx-house.com (8.13.8/8.13.6) with ESMTP id l122eNrK031917 for ; Thu, 1 Feb 2007 21:40:23 -0500 (EST) (envelope-from ml@t-b-o-h.net) Received: (from tbohml@localhost) by himinbjorg.tucs-beachin-obx-house.com (8.13.8/8.13.6/Submit) id l122eMtv031916 for freebsd-net@freebsd.org; Thu, 1 Feb 2007 21:40:22 -0500 (EST) (envelope-from tbohml) From: "Tuc at T-B-O-H.NET" Message-Id: <200702020240.l122eMtv031916@himinbjorg.tucs-beachin-obx-house.com> To: freebsd-net@freebsd.org Date: Thu, 1 Feb 2007 21:40:22 -0500 (EST) X-Mailer: ELM [version 2.5 PL8] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Converting Cisco shorthand to route statement X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Feb 2007 02:59:11 -0000 Hi, I have a line on my router : ip route 172.16.3.0 255.255.255.0 Tunnel0 I'd like to change it to something that doesn't use the "Tunnel0" as a destination, that could be used in a "route" statement. Thanks, Tuc From owner-freebsd-net@FreeBSD.ORG Fri Feb 2 03:43:51 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 23C0216A400 for ; Fri, 2 Feb 2007 03:43:51 +0000 (UTC) (envelope-from joe@joeholden.co.uk) Received: from satriani.as6911.net (satriani.as6911.net [62.84.160.9]) by mx1.freebsd.org (Postfix) with ESMTP id 9BA1413C4A8 for ; Fri, 2 Feb 2007 03:43:50 +0000 (UTC) (envelope-from joe@joeholden.co.uk) Received: from [192.168.10.199] (dsl172-67.as6911.net [62.84.172.67]) by satriani.as6911.net (8.13.6/8.13.6) with ESMTP id l1234dfG089280; Fri, 2 Feb 2007 03:04:39 GMT (envelope-from joe@joeholden.co.uk) Message-ID: <45C2AA4D.6070702@joeholden.co.uk> Date: Fri, 02 Feb 2007 03:04:45 +0000 From: Joe Holden User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: "Tuc at T-B-O-H.NET" References: <200702020240.l122eMtv031916@himinbjorg.tucs-beachin-obx-house.com> In-Reply-To: <200702020240.l122eMtv031916@himinbjorg.tucs-beachin-obx-house.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Converting Cisco shorthand to route statement X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Feb 2007 03:43:51 -0000 Tuc at T-B-O-H.NET wrote: > Hi, > > I have a line on my router : > > ip route 172.16.3.0 255.255.255.0 Tunnel0 > > > I'd like to change it to something that > doesn't use the "Tunnel0" as a destination, that > could be used in a "route" statement. > > Thanks, Tuc Err, I am going to assume you want to transfer it to a fbsd machine, in which case, it would be (tun0|tap0), if not, this is certainly the wrong list. Thanks, -- Joe Holden Telephone: +44 (0) 207 100 9593 Email: joe@joeholden.co.uk Website: http://www.joeholden.co.uk IRC: raindance@Quakenet/#FreeBSD From owner-freebsd-net@FreeBSD.ORG Fri Feb 2 03:26:05 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9C94316A402 for ; Fri, 2 Feb 2007 03:26:05 +0000 (UTC) (envelope-from ml@t-b-o-h.net) Received: from vjofn.tucs-beachin-obx-house.com (vjofn.tucs-beachin-obx-house.com [204.107.90.128]) by mx1.freebsd.org (Postfix) with ESMTP id 59D8F13C471 for ; Fri, 2 Feb 2007 03:26:05 +0000 (UTC) (envelope-from ml@t-b-o-h.net) Received: from himinbjorg.tucs-beachin-obx-house.com (cpe-72-225-142-211.hvc.res.rr.com [72.225.142.211]) (authenticated bits=0) by vjofn.tucs-beachin-obx-house.com (8.12.9/8.12.9) with ESMTP id l123Q3Qe073879 for ; Thu, 1 Feb 2007 22:26:04 -0500 (EST) Received: from himinbjorg.tucs-beachin-obx-house.com (localhost.tucs-beachin-obx-house.com [127.0.0.1]) by himinbjorg.tucs-beachin-obx-house.com (8.13.8/8.13.6) with ESMTP id l123Pwtn033339 for ; Thu, 1 Feb 2007 22:25:58 -0500 (EST) (envelope-from ml@t-b-o-h.net) Received: (from tbohml@localhost) by himinbjorg.tucs-beachin-obx-house.com (8.13.8/8.13.6/Submit) id l123Pw8P033338 for freebsd-net@freebsd.org; Thu, 1 Feb 2007 22:25:58 -0500 (EST) (envelope-from tbohml) From: "Tuc at T-B-O-H.NET" Message-Id: <200702020325.l123Pw8P033338@himinbjorg.tucs-beachin-obx-house.com> To: joe@joeholden.co.uk (Joe Holden) Date: Thu, 1 Feb 2007 22:25:17 -0500 (EST) In-Reply-To: <45C2AA4D.6070702@joeholden.co.uk> X-Mailer: ELM [version 2.5 PL8] Sender: ml@t-b-o-h.net X-Mailman-Approved-At: Fri, 02 Feb 2007 04:37:39 +0000 Cc: Subject: Re: Converting Cisco shorthand to route statement X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Feb 2007 03:26:05 -0000 > > Tuc at T-B-O-H.NET wrote: > > Hi, > > > > I have a line on my router : > > > > ip route 172.16.3.0 255.255.255.0 Tunnel0 > > > > > > I'd like to change it to something that > > doesn't use the "Tunnel0" as a destination, that > > could be used in a "route" statement. > > > > Thanks, Tuc > > Err, I am going to assume you want to transfer it to a fbsd machine, in > which case, it would be (tun0|tap0), if not, this is certainly the wrong > list. > The tunnel is going to be an IPSEC-TOOLS GRE/Tunnel on FreeBSD. (5.X probably) So I'm not sure it has a device name to associate it with. Tuc From owner-freebsd-net@FreeBSD.ORG Fri Feb 2 09:32:54 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 257AE16A4EB for ; Fri, 2 Feb 2007 09:32:54 +0000 (UTC) (envelope-from robert@mpe.mpg.de) Received: from mpemail.mpe.mpg.de (mpemail.mpe-garching.mpg.de [130.183.137.110]) by mx1.freebsd.org (Postfix) with ESMTP id B392213C491 for ; Fri, 2 Feb 2007 09:32:53 +0000 (UTC) (envelope-from robert@mpe.mpg.de) Received: from robert3.mpe-garching.mpg.de ([130.183.136.84]) by mpemail.mpe.mpg.de with esmtpa (Exim 4.50) id 1HCtw3-0004u3-SF for freebsd-net@freebsd.org; Fri, 02 Feb 2007 09:38:19 +0100 Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: 7bit Message-Id: <3FB96681-41F5-49A1-AB61-F18B99E46A7E@mpe.mpg.de> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-net@freebsd.org From: Klaus Robert Suetterlin Date: Fri, 2 Feb 2007 09:38:12 +0100 X-Mailer: Apple Mail (2.752.3) X-Authenticated-Id: robert Subject: GigE Vision standard frame grabber for FreeBSD X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Feb 2007 09:32:54 -0000 Hi all, has anyone experience with using GigE vision standard based cameras and using them under FreeBSD? I am glad for any and all pointers and especially if there was someone with first hand experience. Thanks, --Robert S. From owner-freebsd-net@FreeBSD.ORG Fri Feb 2 14:15:56 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D88BF16A401 for ; Fri, 2 Feb 2007 14:15:56 +0000 (UTC) (envelope-from david.baukus@us.fujitsu.com) Received: from fujitsu0.fujitsu.com (fujitsu0.fujitsu.com [192.240.0.5]) by mx1.freebsd.org (Postfix) with ESMTP id B13F413C481 for ; Fri, 2 Feb 2007 14:15:56 +0000 (UTC) (envelope-from david.baukus@us.fujitsu.com) Received: from fujitsu0.fujitsu.com (localhost [127.0.0.1]) by fujitsu0.fujitsu.com (8.13.7/8.13.7) with ESMTP id l12EFtWh007807 for ; Fri, 2 Feb 2007 06:15:55 -0800 (PST) Received: from fujitsu7i.fnanic.fujitsu.com ([133.164.253.7]) by fujitsu0.fujitsu.com (8.13.7/8.13.7) with ESMTP id l12EFsL4007804 for ; Fri, 2 Feb 2007 06:15:55 -0800 (PST) Received: from fncnmp02.fnc.fujitsu.com (localhost [127.0.0.1]) by fujitsu7i.fnanic.fujitsu.com (8.13.7/8.13.7) with ESMTP id l12EFsxL003456 for ; Fri, 2 Feb 2007 06:15:54 -0800 (PST) Received: from unknown (HELO nova.tx.fnc.fujitsu.com) ([167.254.252.121]) by fncnmp02.fnc.fujitsu.com with ESMTP; 02 Feb 2007 08:12:43 -0600 X-IronPort-AV: i="4.13,273,1167631200"; d="scan'208"; a="59645204:sNHT19537812" Received: from miranda.tx.fnc.fujitsu.com (localhost [127.0.0.1]) by nova.tx.fnc.fujitsu.com (8.13.7+Sun/8.13.7) with ESMTP id l12ECirc020952; Fri, 2 Feb 2007 08:12:44 -0600 (CST) Received: from tdd2172.tddeng00.fnts.com (tdd2172.tddeng00.fnts.com [167.254.250.128]) by miranda.tx.fnc.fujitsu.com (8.13.7+Sun/8.13.7) with ESMTP id l12ECfir004304; Fri, 2 Feb 2007 08:12:41 -0600 (CST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by tdd2172.tddeng00.fnts.com (8.11.7p3+Sun/8.11.7) with ESMTP id l12ECfG13320; Fri, 2 Feb 2007 08:12:41 -0600 (CST) Message-ID: <45C346D7.4090305@us.fujitsu.com> Date: Fri, 02 Feb 2007 08:12:39 -0600 From: Dave Baukus User-Agent: Mozilla Thunderbird 1.0 (X11/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <45C2765C.7010708@us.fujitsu.com> In-Reply-To: <45C2765C.7010708@us.fujitsu.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Dave Baukus Subject: Re: ETIMEDOUT bug X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Feb 2007 14:15:57 -0000 I realized, late last night, that I was wrong on a few details concerning this bug: 1.) The retransmit timer does not keep popping on without being restarted. 2.) ip_output() must return ENOBUFS (TCP_MAXRXTSHIFT + 1) times to the same, non-transmitting TCP. 3.) Given a TCP as described below, when tcp_output() uses ENOBUFS to blindly start the retransmit timer then tp->t_rxtshift will be falsely incremented and never cleared. Thus the bug manifests itself because it appears for a TCP that never transmits nobody ever clears clears tp->t_rxtshift; this allows tp->t_rxtshift to slowly count up to TCP_MAXRXTSHIFT; once TCP_MAXRXTSHIFT is exceeded tcp_timer_rexmt() will kill the poor innocent TCP. On 02/01/07 17:23, Dave Baukus wrote: > There is a bug tcp_output() for at least freeBSD6.1 > that causes a perfectly good TCP to be dropped by its > retransmit timer; the application receives ETIMEDOUT. > > Consider a TCP that never transmits (the receive end of the ttcp > utility is an example), while the TCP is established > snd_max == snd_una == snd_nxt == (isr + 1) and the retransmit > timer should never be started. If the retransmit timer is started > then it is never stopped by tcp_input/tcp_out because > snd_max == snd_una == snd_nxt (always). Once started the > timer continues its count up till tp->t_rxtshift == 12 and > the connection that never transmitted gets falsely killed. > > The bug is to blindly rely on the return value of ip_output(). > If ip_output() returns ENOBUFS then the retransmit timer is > activated: > > From the end of tcp_output(): > out: > SOCKBUF_UNLOCK_ASSERT(&so->so_snd); /* Check gotos. */ > if (error == ENOBUFS) { > if (!callout_active(tp->tt_rexmt) && > !callout_active(tp->tt_persist)) > callout_reset(tp->tt_rexmt, tp->t_rxtcur, > tcp_timer_rexmt, tp); > tp->snd_cwnd = tp->t_maxseg; > return (0); > } > > My simple minded fix would be not to start the retransmit timer; > if tcp_output() wanted to time this transmit it would have started > the timer up above. > > This ETIMEDOUT problem is easily recreated on any old machine > using a single slow ethernet device and the ttcp test utility. > First, fire up a couple ttcp receivers. Second, flood the same > interface with enough ttcp transmitters to cause the driver's transmit > ring and interface queue to back up. Eventually, one of the ttcp > receives will get ENOBUFS from ip_output() and the retransmit > timer will be wrongly activated for a pure ACK segment. > > I was able to do it w/ the following on freeBSD6.1: > > box1: > ttcp -s -l 16384 -p 9444 -v -b 128000 -r > ttcp -s -l 16384 -p 9445 -v -b 128000 -r > ttcp -s -n 6553600 -l 4096 -p 9446 -v -b 128000 -t 192.168.222.13 > ttcp -s -n 9999999 -l 333 -p 9447 -v -b 128000 -t 192.168.222.13 > ttcp -s -n 9999999 -l 8192 -p 9448 -v -b 128000 -t 192.168.222.13 > ttcp -s -n 9999999 -l 333 -p 9449 -v -b 128000 -t 192.168.222.13 > ttcp -s -n 9999999 -l 8192 -p 9450 -v -b 128000 -t 192.168.222.13 > > box2: > ttcp -s -n 6553600 -l 8192 -p 9444 -v -b 128000 -t 192.168.222.222 > ttcp -s -n 9999999 -l 128 -p 9445 -v -b 128000 -t 192.168.222.222 > ttcp -s -l 16384 -p 9446 -v -b 128000 -r > ttcp -s -l 16384 -p 9447 -v -b 128000 -r > ttcp -s -l 16384 -p 9448 -v -b 128000 -r > ttcp -s -l 16384 -p 9449 -v -b 128000 -r > ttcp -s -l 16384 -p 9450 -v -b 128000 -r > -- Dave Baukus david.baukus@us.fujitsu.com 972-479-2491 Fujitsu Network Communications Richardson, Texas USA From owner-freebsd-net@FreeBSD.ORG Fri Feb 2 15:01:11 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0A7B916A40A for ; Fri, 2 Feb 2007 15:01:11 +0000 (UTC) (envelope-from mav@alkar.net) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 85C5C13C491 for ; Fri, 2 Feb 2007 15:01:08 +0000 (UTC) (envelope-from mav@alkar.net) Received: from [212.86.226.11] (account mav@alkar.net [212.86.226.11] verified) by cmail.optima.ua (CommuniGate Pro SMTP 5.0.11) with ESMTPA id 20413501; Fri, 02 Feb 2007 17:01:07 +0200 Message-ID: <45C35232.6010002@alkar.net> Date: Fri, 02 Feb 2007 17:01:06 +0200 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8b) Gecko/20051108 MIME-Version: 1.0 To: Dave Baukus References: <1170386588.00681186.1170374401@10.7.7.3> In-Reply-To: <1170386588.00681186.1170374401@10.7.7.3> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, nvass@teledomenet.gr Subject: Re: ETIMEDOUT bug X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Feb 2007 15:01:11 -0000 Dave Baukus wrote: > There is a bug tcp_output() for at least freeBSD6.1 > that causes a perfectly good TCP to be dropped by its > retransmit timer; the application receives ETIMEDOUT. > This ETIMEDOUT problem is easily recreated on any old machine > using a single slow ethernet device and the ttcp test utility. The same problem is noticed on PPTP links in discussion "ng_pptpgre problems: tcp connections reset unexpectedly". There ENOBUFS is initiated by congestion control of ng_pptpgre node. Other symptoms are the same. -- Alexander Motin mav@alkar.net Optima Telecom From owner-freebsd-net@FreeBSD.ORG Fri Feb 2 16:17:29 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AFFB616A400 for ; Fri, 2 Feb 2007 16:17:29 +0000 (UTC) (envelope-from minotaur@padonki.org.ua) Received: from crow.padonki.org.ua (crow.padonki.org.ua [213.186.192.71]) by mx1.freebsd.org (Postfix) with ESMTP id 64F9B13C4B8 for ; Fri, 2 Feb 2007 16:17:29 +0000 (UTC) (envelope-from minotaur@padonki.org.ua) Received: from minotaur by crow.padonki.org.ua with local (Exim 4.66 (FreeBSD)) (envelope-from ) id 1HD0Xw-000CJd-CX; Fri, 02 Feb 2007 17:41:52 +0200 Date: Fri, 2 Feb 2007 17:41:51 +0200 From: Alexander Shikoff To: freebsd-net@freebsd.org Message-ID: <20070202154150.GA47220@crete.org.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-u Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) Sender: Alexander Shikoff Subject: Attansic L1 Ethernet X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-net@freebsd.org List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2007 16:17:29 -0000 Hello, I have an Asus motherboard with integrated Attansic L1 1Gbit Ethernet. As written at http://lists.freebsd.org/pipermail/freebsd-net/2007-January/013009.html there is no driver for that device at this moment. Would anybody be so kind to tell is in near future a chance to get this adapter working with -STABLE? Thanks in advance. -- Kind Regards, Alexander Shikoff minotaur@crete.org.ua From owner-freebsd-net@FreeBSD.ORG Fri Feb 2 20:19:14 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E2E2D16A403 for ; Fri, 2 Feb 2007 20:19:14 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id BD72C13C491 for ; Fri, 2 Feb 2007 20:19:14 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 50D459DD4D for ; Fri, 2 Feb 2007 15:19:13 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Fri, 02 Feb 2007 15:19:13 -0500 X-Sasl-enc: +2QiA+MEPj+9l8c7XvK0jFFtW/AsozzZd7DVlC5PFmes 1170447553 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id EDF3E1B074 for ; Fri, 2 Feb 2007 15:19:12 -0500 (EST) Message-ID: <45C39CBF.7010105@incunabulum.net> Date: Fri, 02 Feb 2007 20:19:11 +0000 From: Bruce M Simpson User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: net@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Proposal: remove encap from MROUTING X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Feb 2007 20:19:15 -0000 How would you all feel about removing the old encapsulation methods from IPv4 multicast routing as OpenBSD has done? http://www.openbsd.org/cgi-bin/cvsweb/src/sys/netinet/ip_mroute.c.diff?r1=1.42&r2=1.43 The last time I deployed any such infrastructure, I had to use gif(4); in a NATted world, the encap stuff has never worked cleanly for me or been worth the additional effort in deployment. Regards, BMS From owner-freebsd-net@FreeBSD.ORG Fri Feb 2 22:20:43 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F015A16A403 for ; Fri, 2 Feb 2007 22:20:43 +0000 (UTC) (envelope-from gizmen@blurp.pl) Received: from mail.azs.pwr.wroc.pl (albion.azs.pwr.wroc.pl [156.17.17.145]) by mx1.freebsd.org (Postfix) with ESMTP id B4C4813C491 for ; Fri, 2 Feb 2007 22:20:43 +0000 (UTC) (envelope-from gizmen@blurp.pl) Received: from gizmen (blurp.t2.ds.pwr.wroc.pl [156.17.224.5]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.azs.pwr.wroc.pl (Postfix) with ESMTP id 465EE11481 for ; Fri, 2 Feb 2007 23:03:31 +0100 (CET) Date: Fri, 2 Feb 2007 23:03:26 +0100 From: Bartosz Giza X-Mailer: The Bat! (v3.85.03) Professional X-Priority: 3 (Normal) Message-ID: <458982175.20070202230326@blurp.pl> To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: if_bridge and ip alias problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bartosz Giza List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2007 22:20:44 -0000 Hi, recently i have set up bridge based on if_bridge implementation. I have IP address assigned to bridge0 iface and no addresses assigned to members of bridge0. Basicly i am configuring bridge0 in rc.conf: cloned_interfaces="bridge0" autobridge_interfaces="bridge0" autobridge_bridge0="rl0 rl1 em0" ifconfig_bridge0="inet 10.1.1.1 netmask 255.255.255.0" ifconfig_bridge0_alias0="inet 10.1.1.2 netmask 255.255.255.255" ifconfig_rl0="up" ifconfig_rl1="up" ifconfig_em0="up" The problem is with my first alias(10.1.1.2) after system reboot this alias is not visible over network. I can ping this ip on bridge box but no other host can ping this address. When i delete this alias from iface with: ifconfig bridge0 delete 10.1.1.2 and again add on running system ifconfig bridge0 add 10.1.1.2/32 everything starts to work. I can ping this alias from other hosts and i can establish connection with this alias. But if i reboot system ip alias is added to bridge0 but again i can't use this alias. And i have to manualy delete and add alias to be seen over network. Can anybody tell me what can be wrong ? Is this bug or normal behavior? I am using pf for filtering. I have this sysctls: net.link.bridge.ipfw: 0 net.link.bridge.log_stp: 0 net.link.bridge.pfil_member: 0 net.link.bridge.pfil_bridge: 1 net.link.bridge.ipfw_arp: 0 net.link.bridge.pfil_onlyip: 1 I tryied to turn off pf and again turn on, i was watching logs on pflog. I noticed that pf blocks packets on bridge0 comming out to 10.1.1.2 ip address. What is strage it blocks packets comming out not comming in to this ip. But even if trun off pf nothing changes :( So right now i can't use ip aliasing on bridge0 iface. uname -a FreeBSD albion 6.2-STABLE FreeBSD 6.2-STABLE #2: Wed Jan 31 19:16:11 CET 2007 amd64 Any help or advice wanted :) -- Pozdrawiam, Bartosz Giza From owner-freebsd-net@FreeBSD.ORG Sat Feb 3 00:06:59 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 205B516A402 for ; Sat, 3 Feb 2007 00:06:59 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id 9F97C13C47E for ; Sat, 3 Feb 2007 00:05:17 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 7A3A89E6CC for ; Fri, 2 Feb 2007 18:35:52 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Fri, 02 Feb 2007 18:35:52 -0500 X-Sasl-enc: ps5MBianexi468ilEBVpgVvzzwKDBssFcT/6iifl9U2i 1170459352 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 1C9252676B for ; Fri, 2 Feb 2007 18:35:52 -0500 (EST) Message-ID: <45C3CAD7.8040704@incunabulum.net> Date: Fri, 02 Feb 2007 23:35:51 +0000 From: Bruce M Simpson User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: multipart/mixed; boundary="------------030709000202000402000806" Subject: [PATCH] tun(4) does not clean up after itself X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Feb 2007 00:06:59 -0000 This is a multi-part message in MIME format. --------------030709000202000402000806 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, I just saw this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/100080 This patch appears to fix the problem. Any obvious glaring errors? Testers please? Regards, BMS --------------030709000202000402000806 Content-Type: text/x-patch; name="tun-cleanup.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="tun-cleanup.diff" Index: if_tun.c =================================================================== RCS file: /home/ncvs/src/sys/net/if_tun.c,v retrieving revision 1.161 diff -u -p -r1.161 if_tun.c --- if_tun.c 6 Nov 2006 13:42:02 -0000 1.161 +++ if_tun.c 2 Feb 2007 23:30:04 -0000 @@ -388,16 +388,21 @@ tunclose(struct cdev *dev, int foo, int splx(s); } + /* Delete all addresses and routes which reference this interface. */ if (ifp->if_drv_flags & IFF_DRV_RUNNING) { struct ifaddr *ifa; s = splimp(); - /* find internet addresses and delete routes */ - TAILQ_FOREACH(ifa, &ifp->if_addrhead, ifa_link) - if (ifa->ifa_addr->sa_family == AF_INET) - /* Unlocked read. */ + TAILQ_FOREACH(ifa, &ifp->if_addrhead, ifa_link) { + /* deal w/IPv4 PtP destination; unlocked read */ + if (ifa->ifa_addr->sa_family == AF_INET) { rtinit(ifa, (int)RTM_DELETE, tp->tun_flags & TUN_DSTADDR ? RTF_HOST : 0); + } else { + rtinit(ifa, (int)RTM_DELETE, 0); + } + } + if_purgeaddrs(ifp); ifp->if_drv_flags &= ~IFF_DRV_RUNNING; splx(s); } --------------030709000202000402000806-- From owner-freebsd-net@FreeBSD.ORG Sat Feb 3 00:10:41 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C0BB716A400 for ; Sat, 3 Feb 2007 00:10:41 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id 96AA213C481 for ; Sat, 3 Feb 2007 00:10:41 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id CC7E79E441 for ; Fri, 2 Feb 2007 19:10:40 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Fri, 02 Feb 2007 19:10:40 -0500 X-Sasl-enc: 2smEFJYhLV73f9tGXIIUlfN7GsgnYNXdLaywbrNR8b9v 1170461440 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 5D5A3AE94; Fri, 2 Feb 2007 19:10:40 -0500 (EST) Message-ID: <45C3D2FF.5010908@FreeBSD.org> Date: Sat, 03 Feb 2007 00:10:39 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: Bruce M Simpson References: <45C0AA2E.30803@incunabulum.net> In-Reply-To: <45C0AA2E.30803@incunabulum.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: net@FreeBSD.org Subject: Re: [PATCH] Broadcast 169.254.0.0/16 ARP replies for RFC 3927 (Zeroconf) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Feb 2007 00:10:41 -0000 This has now been committed. Thanks to all who responded. From owner-freebsd-net@FreeBSD.ORG Sat Feb 3 00:56:42 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F0BB016A401 for ; Sat, 3 Feb 2007 00:56:42 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id C75D913C4A8 for ; Sat, 3 Feb 2007 00:56:42 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 075D19DE07; Fri, 2 Feb 2007 19:56:42 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Fri, 02 Feb 2007 19:56:42 -0500 X-Sasl-enc: wMY0YYcbxuwywwQOtBup+pqcrKyrJo+P8hFwsthBBM5n 1170464201 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 88B87DF7; Fri, 2 Feb 2007 19:56:41 -0500 (EST) Message-ID: <45C3DDC8.6070109@FreeBSD.org> Date: Sat, 03 Feb 2007 00:56:40 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: Landon Fuller References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: [patch] tun(4) and tap(4) if_clone support. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Feb 2007 00:56:43 -0000 Hi, I have cleaned up the style/mdoc bugs in the original patch, and cut a new one against bleeding edge HEAD (we just took the kern_conf.c fix in too):- http://people.freebsd.org/~bms/dump/new-landon-tuntap.diff PRs potentially resolved by this patch: http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/90413 http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/105570 Regards, BMS From owner-freebsd-net@FreeBSD.ORG Sat Feb 3 06:18:12 2007 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A301416A403 for ; Sat, 3 Feb 2007 06:18:12 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id 66F7313C4A6 for ; Sat, 3 Feb 2007 06:18:12 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 6AA15E0771 for ; Sat, 3 Feb 2007 01:16:56 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Sat, 03 Feb 2007 01:16:56 -0500 X-Sasl-enc: bUwdwVdShk4BUWLozoRBKPyN0E4HX5SXLp0zk08cFdbt 1170483415 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id C78EE447B for ; Sat, 3 Feb 2007 01:16:55 -0500 (EST) Message-ID: <45C428D7.20900@incunabulum.net> Date: Sat, 03 Feb 2007 06:16:55 +0000 From: Bruce M Simpson User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: net@FreeBSD.org Content-Type: multipart/mixed; boundary="------------070806030404070403060507" Cc: Subject: [PATCH] ip_fastfwd forwards directed broadcasts X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Feb 2007 06:18:12 -0000 This is a multi-part message in MIME format. --------------070806030404070403060507 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, Attached is a patch which tells our IPv4 fast-forwarding path to drop directed broadcast packets. The checks originally put in ip_fastfwd.c can deal only with undirected broadcasts. Whilst this patch doesn't mitigate the resulting CPU consumption, it does the right thing by letting the FIB deal with the hard work of determining whether or not a given destination address is for a broadcast destination. Normally, RTF_BROADCAST is set on routes which were added as a result of a call to arpresolve() to resolve the broadcast address, and thus in_addroute(). This is fine and covers the case where the directed broadcast address is known to the router -- which is what we want 99% of the time. The fix in PR 98799 is not the right fix: in_broadcast() can potentially return an IPv4 destination address as not being a broadcast address, because it only walks the address list hung off the single ifnet pointer provided. We perform a route lookup anyway, so let the FIB do the work. To detect directed broadcasts being propagated beyond a single hop would require cooperation from a routing daemon which is smart enough to set RTF_BROADCAST on the routes which it pushes to the kernel FIB for the network prefixes it learns; the router has to have topology information before it can do anything, otherwise, it's just another IPv4 address. Regards, BMS --------------070806030404070403060507 Content-Type: text/x-patch; name="dropbroadcasts.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dropbroadcasts.diff" Index: ip_fastfwd.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/ip_fastfwd.c,v retrieving revision 1.37 diff -u -p -r1.37 ip_fastfwd.c --- ip_fastfwd.c 17 Aug 2006 00:37:03 -0000 1.37 +++ ip_fastfwd.c 3 Feb 2007 06:11:08 -0000 @@ -418,9 +418,11 @@ passin: ifp = ro.ro_rt->rt_ifp; /* - * Immediately drop blackholed traffic. + * Immediately drop blackholed traffic, and directed broadcasts + * for either the all-ones or all-zero subnet addresses on + * locally attached networks. */ - if (ro.ro_rt->rt_flags & RTF_BLACKHOLE) + if ((ro.ro_rt->rt_flags & (RTF_BLACKHOLE|RTF_BROADCAST)) != 0) goto drop; /* --------------070806030404070403060507-- From owner-freebsd-net@FreeBSD.ORG Sat Feb 3 10:20:06 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 792A816A402 for ; Sat, 3 Feb 2007 10:20:06 +0000 (UTC) (envelope-from wschnr@googlemail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.226]) by mx1.freebsd.org (Postfix) with ESMTP id 27A3813C461 for ; Sat, 3 Feb 2007 10:20:05 +0000 (UTC) (envelope-from wschnr@googlemail.com) Received: by wx-out-0506.google.com with SMTP id s18so1056607wxc for ; Sat, 03 Feb 2007 02:20:05 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=iKR1kuI1F1qbGJcwF2UMZFKc6AuhGDesvfNR0LgMEGwML/25DGxiEuCMkiyLnkjLfuLJxMGqzIHjB+kNqxXx0nPTHnZjSIGuw2YZpqr5XsHB+KG1MhXMxXCTxDMwVq77B32QuG4tbrr9mpFSGpcgMovC8SUeGauivwiAHxmKzQw= Received: by 10.90.55.19 with SMTP id d19mr6297053aga.1170496256797; Sat, 03 Feb 2007 01:50:56 -0800 (PST) Received: by 10.90.68.6 with HTTP; Sat, 3 Feb 2007 01:50:56 -0800 (PST) Message-ID: Date: Sat, 3 Feb 2007 10:50:56 +0100 From: "Wolfram Schneider" Sender: wschnr@googlemail.com To: "Sasha Usov" In-Reply-To: <657795279.20070202192828@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <657795279.20070202192828@gmail.com> X-Google-Sender-Auth: 19c007d7ec9d4583 Cc: freebsd-net@freebsd.org Subject: Re: ALTQ with bce interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2007 10:20:06 -0000 Hi Sasha, I forwared your mail to the freebsd-net mailing list. -Wolfram On 2/2/07, Sasha Usov wrote: > > Hello! > > Can I use ALTQ with onboard interface bce (Broadcom Communication)? > > As per man, They have been applied to the following > hardware drivers: an(4), ath(4), awi(4), bfe(4), bge(4), dc(4), de(4), > ed(4), em(4), fxp(4), hme(4), le(4), lnc(4), my(4), nve(4), re(4), rl(4), > sf(4), sis(4), sk(4), ste(4), stge(4), vr(4), wi(4), and xl(4). > > > -- > Sasha Usov > blessendor@gmail.com > > -- Wolfram Schneider http://wolfram.schneider.org From owner-freebsd-net@FreeBSD.ORG Sat Feb 3 13:04:40 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 18B1F16A40E; Sat, 3 Feb 2007 13:04:40 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.179]) by mx1.freebsd.org (Postfix) with ESMTP id A241713C4AA; Sat, 3 Feb 2007 13:04:39 +0000 (UTC) (envelope-from max@love2party.net) Received: from [88.64.189.250] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu3) with ESMTP (Nemesis), id 0MKxQS-1HDKZJ0rlb-00044y; Sat, 03 Feb 2007 14:04:37 +0100 From: Max Laier Organization: FreeBSD To: freebsd-net@freebsd.org Date: Sat, 3 Feb 2007 14:06:31 +0100 User-Agent: KMail/1.9.5 References: <657795279.20070202192828@gmail.com> In-Reply-To: X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3354870.5mt9p5dlnG"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200702031406.38102.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 X-Provags-ID2: V01U2FsdGVkX1+LlmW4cHYwWY13IOYjQqjsvn5kUC3WauHjqBmM0aLifyfszv9/qZxYj++p0mtY55/69Pe7QEU9bPKNQYj9h9urQD191EDUkSU75VjmwOyUbg== Cc: Sasha Usov , Wolfram Schneider Subject: Re: ALTQ with bce interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2007 13:04:40 -0000 --nextPart3354870.5mt9p5dlnG Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 03 February 2007 10:50, Wolfram Schneider wrote: > Hi Sasha, > > I forwared your mail to the freebsd-net mailing list. > > -Wolfram > > On 2/2/07, Sasha Usov wrote: > > Hello! > > > > Can I use ALTQ with onboard interface bce (Broadcom Communication)? It seems that bce(4) supported ALTQ from revision 1.1 - I will add it to=20 the man page. > > > > As per man, They have been applied to the following > > hardware drivers: an(4), ath(4), awi(4), bfe(4), bge(4), dc(4), > > de(4), ed(4), em(4), fxp(4), hme(4), le(4), lnc(4), my(4), nve(4), > > re(4), rl(4), sf(4), sis(4), sk(4), ste(4), stge(4), vr(4), wi(4), > > and xl(4). > > > > > > -- > > Sasha Usov > > blessendor@gmail.com =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart3354870.5mt9p5dlnG Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQBFxIjeXyyEoT62BG0RAnRYAJwO8C81cad1UouZxFtiX/uc3Yv46gCbBwG2 bojCW27RQObU9AhvJDjob70= =qR8p -----END PGP SIGNATURE----- --nextPart3354870.5mt9p5dlnG-- From owner-freebsd-net@FreeBSD.ORG Sat Feb 3 17:27:40 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1BCEB16A402 for ; Sat, 3 Feb 2007 17:27:40 +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 CAE7313C428 for ; Sat, 3 Feb 2007 17:27:39 +0000 (UTC) (envelope-from freebsd-net@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HDOfl-0007iQ-Ev for freebsd-net@freebsd.org; Sat, 03 Feb 2007 18:27:33 +0100 Received: from 89-172-45-56.adsl.net.t-com.hr ([89.172.45.56]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 03 Feb 2007 18:27:33 +0100 Received: from ivoras by 89-172-45-56.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 03 Feb 2007 18:27:33 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-net@freebsd.org From: Ivan Voras Date: Sat, 03 Feb 2007 18:27:04 +0100 Lines: 26 Message-ID: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig7B51C010F7AB858589644BA4" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 89-172-45-56.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) X-Enigmail-Version: 0.94.1.2 Sender: news Subject: SIMPLEX network device? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 03 Feb 2007 17:27:40 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig7B51C010F7AB858589644BA4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I've noticed in ifconfig report for a gigabit NIC based on Realtek 8169S chip that it has the SIMPLEX flag set. What does it mean in practice, considering the media type is (correctly) autonegotiated for 1000baseTX full-duplex? --------------enig7B51C010F7AB858589644BA4 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.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFxMXuldnAQVacBcgRAivyAJ9wHJQvsgm3AEniLf1U8z07kKYuxQCeODhb AdcGF9TcKovsX5y5dsf60og= =s2ur -----END PGP SIGNATURE----- --------------enig7B51C010F7AB858589644BA4-- From owner-freebsd-net@FreeBSD.ORG Sat Feb 3 20:03:40 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 780F916A400 for ; Sat, 3 Feb 2007 20:03:40 +0000 (UTC) (envelope-from thompsa@freebsd.org) Received: from heff.fud.org.nz (203-109-251-39.static.bliink.ihug.co.nz [203.109.251.39]) by mx1.freebsd.org (Postfix) with ESMTP id 1A53D13C481 for ; Sat, 3 Feb 2007 20:03:40 +0000 (UTC) (envelope-from thompsa@freebsd.org) Received: by heff.fud.org.nz (Postfix, from userid 1001) id 88DE51CC51; Sun, 4 Feb 2007 09:03:38 +1300 (NZDT) Date: Sun, 4 Feb 2007 09:03:38 +1300 From: Andrew Thompson To: Bartosz Giza Message-ID: <20070203200338.GA95102@heff.fud.org.nz> References: <458982175.20070202230326@blurp.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <458982175.20070202230326@blurp.pl> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-net@freebsd.org Subject: Re: if_bridge and ip alias 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: Sat, 03 Feb 2007 20:03:40 -0000 On Fri, Feb 02, 2007 at 11:03:26PM +0100, Bartosz Giza wrote: > Hi, > > recently i have set up bridge based on if_bridge implementation. > I have IP address assigned to bridge0 iface and no addresses assigned > to members of bridge0. > Basicly i am configuring bridge0 in rc.conf: > > cloned_interfaces="bridge0" > autobridge_interfaces="bridge0" > autobridge_bridge0="rl0 rl1 em0" > ifconfig_bridge0="inet 10.1.1.1 netmask 255.255.255.0" > ifconfig_bridge0_alias0="inet 10.1.1.2 netmask 255.255.255.255" > ifconfig_rl0="up" > ifconfig_rl1="up" > ifconfig_em0="up" > > The problem is with my first alias(10.1.1.2) after system reboot this > alias is not visible over network. I can ping this ip on bridge box > but no other host can ping this address. > When i delete this alias from iface with: > ifconfig bridge0 delete 10.1.1.2 > and again add on running system > ifconfig bridge0 add 10.1.1.2/32 Do you see if the address is arped correctly from the other host? you can use tcpdump to view this or just add it statically to see if this resolves the problem. When you re-add the alias it will send out a gratuitous arp which suggests this is the problem. cheers, Andrew