From owner-freebsd-net@FreeBSD.ORG Sun Jan 4 01:30:27 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D3A3106566C; Sun, 4 Jan 2009 01:30:27 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 144F78FC08; Sun, 4 Jan 2009 01:30:27 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n041UQVk010502; Sun, 4 Jan 2009 01:30:26 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n041UQ35010492; Sun, 4 Jan 2009 01:30:26 GMT (envelope-from vwe) Date: Sun, 4 Jan 2009 01:30:26 GMT Message-Id: <200901040130.n041UQ35010492@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/80853: [ed] [patch] add support for Compex RL2000/ISA in PnP mode X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Jan 2009 01:30:28 -0000 Synopsis: [ed] [patch] add support for Compex RL2000/ISA in PnP mode Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Sun Jan 4 01:29:36 UTC 2009 Responsible-Changed-Why: the patch is still valid, device is still not supported by ed(4) reassign to the net team http://www.freebsd.org/cgi/query-pr.cgi?pr=80853 From owner-freebsd-net@FreeBSD.ORG Sun Jan 4 01:35:09 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE12D1065672; Sun, 4 Jan 2009 01:35:09 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 925278FC20; Sun, 4 Jan 2009 01:35:09 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n041Z9ph015997; Sun, 4 Jan 2009 01:35:09 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n041Z9YS015993; Sun, 4 Jan 2009 01:35:09 GMT (envelope-from vwe) Date: Sun, 4 Jan 2009 01:35:09 GMT Message-Id: <200901040135.n041Z9YS015993@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/84202: [ed] [patch] Holtek HT80232 PCI NIC recognition on FreeBSD 5.4-RELEASE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jan 2009 01:35:10 -0000 Synopsis: [ed] [patch] Holtek HT80232 PCI NIC recognition on FreeBSD 5.4-RELEASE Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Sun Jan 4 01:34:48 UTC 2009 Responsible-Changed-Why: the patch is still valid, device is still not supported by ed(4) reassign to the net team http://www.freebsd.org/cgi/query-pr.cgi?pr=84202 From owner-freebsd-net@FreeBSD.ORG Sun Jan 4 08:37:42 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22075106564A for ; Sun, 4 Jan 2009 08:37:42 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [220.233.188.227]) by mx1.freebsd.org (Postfix) with ESMTP id 455C28FC12 for ; Sun, 4 Jan 2009 08:37:40 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id n048bcc0019867; Sun, 4 Jan 2009 19:37:39 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sun, 4 Jan 2009 19:37:38 +1100 (EST) From: Ian Smith To: perryh@pluto.rain.com In-Reply-To: <495fd4f4.LnYmNJ/Km8Riy79x%perryh@pluto.rain.com> Message-ID: <20090104173927.R28770@sola.nimnet.asn.au> References: <495edc8b.yfwTDGtb9G/8NMur%perryh@pluto.rain.com> <20090103154232.P28770@sola.nimnet.asn.au> <495f15da.kLIW2g4L+3rMjCXS%perryh@pluto.rain.com> <20090103185837.K28770@sola.nimnet.asn.au> <495fd4f4.LnYmNJ/Km8Riy79x%perryh@pluto.rain.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-net@freebsd.org Subject: Re: tun0 not responding to ping X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Jan 2009 08:37:42 -0000 On Sat, 3 Jan 2009, perryh@pluto.rain.com wrote: > Ian Smith wrote: > > On Fri, 2 Jan 2009, perryh@pluto.rain.com wrote: > > > Ian Smith wrote: > > > > uucp .. how quaint :) > > Yep, but running over ssh since agora no longer has modems. > How's that for a mix of ancient and modern technology? :) I like it .. > > > http://www.cs.rpi.edu/~flemej/fbsd-cisco-vpn.pdf > > > > "You don't have permission to access /~flemej/fbsd-cisco-vpn.pdf > > That's odd. It worked from here as recently as 12/17. Thanks for mailing it. It's at http://smithi.id.au/fbsd-cisco-vpn.pdf (100K) for now, if anyone else is interested. > FreeBSD interoperability with Cisco VPN > Concentrator 3000 series > James Flemer > jflemer@alum.rpi.edu > October 10, 2002 > > and the relevant excerpt -- after it describes a setup involving > netgraph(4) and the mpd port -- is > > 3.4 Routing > Unfortunately, this does not work completely. It successfully > establishes the PPTP connection, but cannot send anything over > it. The problem is that the PPTP implementation for the > concentrator forces its end of the PPP link to have the same > IP as the address of its public interface (192.168.0.2 in this > network). This causes FreeBSD to have routing problems, because > the default gateway becomes 192.168.0.2 (via ng0), but in order > to use that tunnel it has to send GRE packets to 192.168.0.2. > > The solution to this is as follows. Once the PPTP link is up, > you need to re-address the ng0 interface and then change your > default route. In the example network, you have to execute the > following commands (assuming we are assigned 10.0.2.42 for our > side of the link): > > # ifconfig ng0 inet 10.0.2.42 10.0.0.2 netmask 0xffffffff > # route delete default > # route add default -interface ng0 > > What I see is a bit different -- both ends get the IP that's > supposed to have been assigned to my end, rather than the Cisco > end getting the Cisco's public IP -- but perhaps related. Had a quick look at http://www.unix-ag.uni-kl.de/~massar/vpnc/ but don't get whether it, or you, are configuring ppp? ie, does vpnc make or mess with /etc/ppp/ppp.conf? Or otherwise invoke ppp directly itself? You can do pretty much like the above by invoking an /etc/ppp/ppp.linkup script. Here you're not using the tunnel as your default route anyway, but you could perhaps fix the addressing with ifconfig, though a quick refresher skim through ppp(8) shows a way/s to force the remote ppp to supply its IP address if it's otherwise recalcitrant. Or if you know it, you can force it by an appropriate 'set if_addr' address/mask. Have you considered using mpd for this instead? It comes with PPTP example configs, and while some syntax has changed from then (2002, maybe mpd 3) to now (mpd 5 .. I'm still using 4.1) it might be more straightforward to setup, and mav@ is around here and ever helpful .. > > but as I said, I know next to nothing about VPN configuration anyway. > > I suspect this problem has more to do with PPP, tun(4), and routing > than with VPN's as such. vpnc does seem to be establishing the VPN > connection. > > > > * Supposing that tun0 does need to be readdressed as > > > > > > inet ZZZ.ZZZ.233.42 --> ZZZ.ZZZ.2.13 netmask 0xffffffff > > > > > > -- where ZZZ.ZZZ.2.13 is the address of the Cisco box on > > > ZZZ.ZZZ.0.0/16 -- I'm not at all clear on how a w/a should get > > > that internal address in the general case. (I got it by running > > > a traceroute from an inside machine to a working VPN-connected > > > Windows system, after not finding anything in the vpnc logs.) Have another dig through CONTROLLING IP ADDRESS in ppp(8) (set if_addr), which appears to include a case where remote is reluctant to supply its address. And then, it may not matter - as long as it's not the same as your end - if you're using 'route add -interface ppp0' but that's really in the realm of guesswork, treat with due suspicion .. > w/a = workaround. Ah! > > Usually you can ping either end; ping is the same as ping > > localhost > > That's what I expected. > > > ping is, well, that. With both the same, I'm not > > too surprised that ppp can't figure out which end you want to > > talk to? > > Maybe that's (part of?) the problem, although I would have thought > that the local side would immediately respond to its own address, > without even checking anything else. I don't know whether it would even get to ppp, past the routing; point to point without two points being a bit, er, pointless :) Also, any routes you add via that link specify the far (not near) end as gateway, with then a single host route for the far end via the near, as below. > > We ran ppp for 10 years on a dialup link but these days for pppoe > > using mpd, but the routing should come to about the same, given > > that here it's our default route. > > > > ng0: > > flags=88d1 mtu 1492 > > inet xxx.yyy.zzz.227 --> xxx.yyy.1.33 netmask 0xffffffff > > Hmm. Maybe tun0 needs NOARP and/or SIMPLEX (but, as with the remote > IP address, I'd have expected vpnc to configure the interface as > required rather than needing help). I've not seen ppp use those options, just mpd, but I dunno. Seems vpnc is generating your ppp.conf? I've no idea what it's doing here, sorry, nor whether such a VPN requires proxy ARP to work. If so, ppp can do. > > Destination Gateway Flags Refs Use Netif Expire > > default xxx.yyy.1.33 UGS 0 24390 ng0 > > [..] > > xxx.yyy.1.33 xxx.yyy.zzz.227 UH 1 0 ng0 > > xxx.yyy.zzz.227/32 lo0 US 0 2 lo0 > > > > This is a 5.5 system, in case different presentation might mislead. > > This one is not all that much newer (6.1). One thing I notice, > which seems odd, is the route to ng0's local IP address via lo0. > Shouldn't the stack be able to communicate directly with a local > ng (or tun) interface, just as it does with something like an xl0 > (or lo0, for that matter)? I wondered about that too, but that it works fine has been good enough. Perhaps it has something to do with the fact that ng0 is really working over another physical ethernet interface? (here, xe0 to an ADSL bridge) I'm out of ideas, so hopefully some of the Cogniscenti will chime in, if they're not all still sunning themselves in the Bahamas, or Cairns .. cheers, Ian From owner-freebsd-net@FreeBSD.ORG Sun Jan 4 09:48:08 2009 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F588106564A for ; Sun, 4 Jan 2009 09:48:08 +0000 (UTC) (envelope-from kes-kes@yandex.ru) Received: from forwards4.yandex.ru (forwards4.yandex.ru [77.88.32.20]) by mx1.freebsd.org (Postfix) with ESMTP id CC3D08FC13 for ; Sun, 4 Jan 2009 09:48:07 +0000 (UTC) (envelope-from kes-kes@yandex.ru) Received: from smtp5.yandex.ru (smtp5.yandex.ru [77.88.32.24]) by forwards4.yandex.ru (Yandex) with ESMTP id A134F4C5343; Sun, 4 Jan 2009 12:48:04 +0300 (MSK) Received: from 252-75-113-92.pool.ukrtel.net ([92.113.75.252]:64516 "EHLO HOMEUSER" smtp-auth: "kes-kes" TLS-CIPHER: TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S6144112AbZADJrz (ORCPT + 1 other); Sun, 4 Jan 2009 12:47:55 +0300 X-Yandex-Spam: 1 X-Yandex-Front: smtp5 X-Yandex-TimeMark: 1231062475 X-BornDate: 1149541200 X-Yandex-Karma: 0 X-Yandex-KarmaStatus: 0 X-MsgDayCount: 2 X-Comment: RFC 2476 MSA function at smtp5.yandex.ru logged sender identity as: kes-kes Date: Sun, 4 Jan 2009 11:47:54 +0200 From: KES X-Mailer: The Bat! (v4.0.24) Professional Organization: SaftTen X-Priority: 3 (Normal) Message-ID: <666141730.20090104114754@yandex.ru> To: vwe@FreeBSD.org In-Reply-To: <200901031502.n03F2KbP042269@freefall.freebsd.org> References: <200901031502.n03F2KbP042269@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 8bit Cc: freebsd-net@FreeBSD.org Subject: Re[2]: kern/129074: [ppp] [panic] kernel panic with pppoe_server X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: KES List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jan 2009 09:48:08 -0000 Çäðàâñòâóéòå, Vwe. Âû ïèñàëè 3 ÿíâàðÿ 2009 ã., 17:02:20: vFo> Synopsis: [ppp] [panic] kernel panic with pppoe_server vFo> State-Changed-From-To: feedback->closed vFo> State-Changed-By: vwe vFo> State-Changed-When: Sat Jan 3 15:01:30 UTC 2009 vFo> State-Changed-Why: vFo> We're sorry to not see any feedback received for quite some time. vFo> If you think this is still an issue that should be worked on, vFo> please provide the requested information and we'll be happy to vFo> re-open this ticket. vFo> Thank you for bringing this problem to attention! vFo> Responsible-Changed-From-To: freebsd-net->vwe vFo> Responsible-Changed-By: vwe vFo> Responsible-Changed-When: Sat Jan 3 15:01:30 UTC 2009 vFo> Responsible-Changed-Why: vFo> track vFo> http://www.freebsd.org/cgi/query-pr.cgi?pr=129074 Strange, I have replied to email and provide requested information... kes# pppd --version pppd version 2.3 patch level 5 /etc/ppp/ppp.conf default: set log Phase Chat LCP IPCP CCP tun command adsl: set log Phase LCP tun command set device PPPoE:rl0:ukrtelecom # enable lqr # enable dns disable ipv6cp set cd 10 set dial # set login set redial 0 0 set reconnect random 999 set mtu 1492 set mru 1492 set authname name set authkey password # add! default HISADD ppp[348]: tun0: Phase: Pap Input: FAILURE (insufficient resources available to authenticate user) or ppp[348]: tun0: Phase: Pap Output: ******** last message repeated 2 times ppp[348]: tun0: Phase: Auth: No response from server As you can see my ISP respond with error. After 10-15 trying to login to ISP my server will reboot with kernel panic. -- Ñ óâàæåíèåì, KES mailto:kes-kes@yandex.ru From owner-freebsd-net@FreeBSD.ORG Sun Jan 4 10:23:27 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFE2D1065670 for ; Sun, 4 Jan 2009 10:23:27 +0000 (UTC) (envelope-from nrml@att.net) Received: from web83802.mail.sp1.yahoo.com (web83802.mail.sp1.yahoo.com [69.147.85.67]) by mx1.freebsd.org (Postfix) with SMTP id AC8148FC18 for ; Sun, 4 Jan 2009 10:23:27 +0000 (UTC) (envelope-from nrml@att.net) Received: (qmail 9534 invoked by uid 60001); 4 Jan 2009 10:23:27 -0000 X-YMail-OSG: wbMY2eAVM1mj2e9_LlRo2bnhydykjiqLG91rCOSQOx3z0AOveUMvqYnFMcfL9rpQQqC8rDQ0FlDoIxhiPnXYp3TyGyrBMlerW2.5a2H65ukryyEbYoXevjVINWvjs367ang9hKzJV4S.KRecdM3l.KMQXZViK1iMY69OmvBDOpPS5ZD1LSEINezbAo_FwT58E1ofAos7ZOBTMEzEY4hgF17wYJzh Received: from [69.43.143.172] by web83802.mail.sp1.yahoo.com via HTTP; Sun, 04 Jan 2009 02:23:26 PST X-Mailer: YahooMailWebService/0.7.218.2 Date: Sun, 4 Jan 2009 02:23:26 -0800 (PST) From: Gabe To: "Bjoern A. Zeeb" In-Reply-To: <480896.12029.qm@web83811.mail.sp1.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <186728.8993.qm@web83802.mail.sp1.yahoo.com> Cc: freebsd-net@freebsd.org Subject: Re: +ipsec_common_input: no key association found for SA X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: nrml@att.net List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jan 2009 10:23:28 -0000 > From: Gabe > Subject: Re: +ipsec_common_input: no key association found for SA > To: "Bjoern A. Zeeb" > Cc: freebsd-net@freebsd.org > Date: Tuesday, December 30, 2008, 11:56 PM > > From: Bjoern A. Zeeb > > > Subject: Re: +ipsec_common_input: no key association > found for SA > > To: "Gabe" > > Cc: freebsd-net@freebsd.org > > Date: Tuesday, December 30, 2008, 6:24 AM > > On Tue, 30 Dec 2008, Gabe wrote: > > > > >> One more thing; if you are comparing SPIs > from the > > log with setkey, > > >> you can also run > > >> tcpdump -s 0 -vv -ln proto 50 > > >> and it will show you something like > > >> ... ESP(spi=0x12345678,seq=0x..), > > >> so you could as well compare what you receive > on > > the wire with what > > >> you get in the log. This would help to > eliminiate > > the case of a > > >> promblematic patch. > > > > > > However I still get the ipsec_common message > albeit > > not as often, it > > > appears to only be when I restart racoon now. I > also > > tried matching the > > > SPIs but the SPIs given by setkey -Da did not > match > > the ones on the log. > > > > Ok, can you try running the following script and see > if the > > output > > times match your racoon restarts or the log entries? > > > > You need to set your interface and the tunnel endpoint > IPs > > (as in box/box2). > > > > /bz > > I restarted racoon and cleared out the keys then I ran the > script which returned: > > on BOX: > tcpdump: verbose output suppressed, use -v or -vv for full > protocol decode > listening on em1, link-type EN10MB (Ethernet), capture size > 65535 bytes > 23:51:13.032336 SPI changed uninitialized -> 0x0878469a > 23:51:13.063318 SPI changed 0x0878469a -> 0x091b7ada > ^C1154 packets captured > 1597 packets received by filter > 0 packets dropped by kernel > > on BOX2: > tcpdump: verbose output suppressed, use -v or -vv for full > protocol decode > listening on em1, link-type EN10MB (Ethernet), capture size > 65535 bytes > 23:53:43.594785 SPI changed uninitialized -> 0x01d66237 > ^C2404 packets captured > 9701 packets received by filter > 0 packets dropped by kernel > > box and box2 are the local and end point respectively. > > /gabe I'm still unable to find the cause for this. Does anyone know what the above output is referring to? Thanks, /gabe From owner-freebsd-net@FreeBSD.ORG Sun Jan 4 11:25:12 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E32D106566B for ; Sun, 4 Jan 2009 11:25:12 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id 36D438FC14 for ; Sun, 4 Jan 2009 11:25:12 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (amavis.str.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 261F041C62D; Sun, 4 Jan 2009 12:25:11 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([62.111.66.27]) by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id kWrAWi-84CyF; Sun, 4 Jan 2009 12:25:10 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id B6C9B41C616; Sun, 4 Jan 2009 12:25:10 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 5DA934448DD; Sun, 4 Jan 2009 11:24:59 +0000 (UTC) Date: Sun, 4 Jan 2009 11:24:58 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Gabe In-Reply-To: <186728.8993.qm@web83802.mail.sp1.yahoo.com> Message-ID: <20090104110430.I45399@maildrop.int.zabbadoz.net> References: <186728.8993.qm@web83802.mail.sp1.yahoo.com> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: +ipsec_common_input: no key association found for SA X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Jan 2009 11:25:12 -0000 On Sun, 4 Jan 2009, Gabe wrote: Hi, >>> Ok, can you try running the following script and see >> if the >>> output >>> times match your racoon restarts or the log entries? You hadn't answered that question to correlate the tcpdump with racoon restarts and kernel log entries. If you do that, you may want to run the script for two hours or four to actually see more changes than just the initial one. Check the syslog timestamps in the logfile where your kernel messages go to (might be /var/log/messages) for the ipsec_common_input lines. Perhaps grep upfront before startung the script to be sure that they are there. > I'm still unable to find the cause for this. Does anyone know what the above output is referring to? I think David DeSimone had last explained it to you: http://lists.freebsd.org/pipermail/freebsd-net/2008-December/020611.html Maybe it would be time to read the RFC now; I'll try it in my own words again and shorter. Your IPsec Policy makes your racoons negotiate a Security Assosiaction for some parameters (keys, lieftime, ..). There will be one for each direction. One thing negotiated is the security policy index, the number we are tracing. This 'number' is put into each packet one of the boxes send encrypted to the other for the given direction. What your kernel tells you is that the number in the packet received does not make sense to the box receiving it. Let's say the SPI received in the packet from the other box is unknown on the receiver side. That's why the kernel complains. Without the proper SPI the kernel will not be able to find the proper other parameters for this packet, and thus will not be able to decrypt the packet. What we are trying to find out at the moment is to identify where exactly the wrong SPI is coming from. This could be: - whatever the boxes negotiated gets out of sync - a patch like the NAT-T patch could corrupt the packet - a software bug in where the kernel or racoon - ... To narrow this down from "everywhere" to "here" it is important to see where the values match, where not and when they do not match - thus correlating information from the time racoon gets restarted, the kernel prints the log message and what tcpdump is showing. It's important to get all this information for the same problematic moment, timestamped. If one is missing it's like a 1000 pieces puzzle with only 600 pieces included. One more question that hadn't been asked so far - what architectures (i386, amd64, sparc, arm, ..) are box and box2 and which version of freebsd are they running; I assume they are both on freebsd? /bz -- Bjoern A. Zeeb The greatest risk is not taking one. From owner-freebsd-net@FreeBSD.ORG Sun Jan 4 11:50:57 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F9C5106566C for ; Sun, 4 Jan 2009 11:50:57 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [199.26.172.34]) by mx1.freebsd.org (Postfix) with ESMTP id DFF518FC0C for ; Sun, 4 Jan 2009 11:50:56 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id n04Botj8017388 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 4 Jan 2009 03:50:56 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id n04Bota9017387; Sun, 4 Jan 2009 03:50:55 -0800 (PST) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA08299; Sun, 4 Jan 09 03:32:20 PST Date: Sun, 04 Jan 2009 03:34:43 -0800 From: perryh@pluto.rain.com To: smithi@nimnet.asn.au Message-Id: <49609ed3.pm0Bis/9ZOFmjtVw%perryh@pluto.rain.com> References: <495edc8b.yfwTDGtb9G/8NMur%perryh@pluto.rain.com> <20090103154232.P28770@sola.nimnet.asn.au> <495f15da.kLIW2g4L+3rMjCXS%perryh@pluto.rain.com> <20090103185837.K28770@sola.nimnet.asn.au> <495fd4f4.LnYmNJ/Km8Riy79x%perryh@pluto.rain.com> <20090104173927.R28770@sola.nimnet.asn.au> In-Reply-To: <20090104173927.R28770@sola.nimnet.asn.au> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: tun0 not responding to ping X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Jan 2009 11:50:57 -0000 > Had a quick look at http://www.unix-ag.uni-kl.de/~massar/vpnc/ but > don't get whether it, or you, are configuring ppp? ie, does vpnc > make or mess with /etc/ppp/ppp.conf? Or otherwise invoke ppp > directly itself? Neither, I suspect. Looking at the ppp(8) manpage, it looks as if both vpnc and (user-mode) ppp use tun(4) rather than vpnc invoking ppp. There's no mention of ppp in the vpnc README or manpage, although the manpage does mention ip(8), ifconfig(8), and route(1). My /etc/ppp/ppp.conf is dated in 2006, so I guess it it "as delivered". It appears to be a template for connecting to an ISP via dialup or PAP/CHAP. > You can do pretty much like the above by invoking an > /etc/ppp/ppp.linkup script. Provided it could (somehow) be made to handle the VPN encryption and logon credentials, including RSA SecureNet one-time passwords, which vpnc seems to take care of. > Here you're not using the tunnel as your default route anyway, > but you could perhaps fix the addressing with ifconfig ... That seems to be Flemer's approach, and it may be as good a thing as any to try first. > Have you considered using mpd for this instead? That would be Flemer's setup. I got the impression from his paper that it might not handle the RSA one-time passwords very well, if at all, although it might work well enough in a shop that does not use dynamic passwords. (I suspect no one would have taken the trouble to write vpnc, or at least to port it from Linux to FreeBSD, had mpd been an altogether satisfactory solution :) From owner-freebsd-net@FreeBSD.ORG Sun Jan 4 12:11:28 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6936C1065678 for ; Sun, 4 Jan 2009 12:11:28 +0000 (UTC) (envelope-from nrml@att.net) Received: from web83809.mail.sp1.yahoo.com (web83809.mail.sp1.yahoo.com [69.147.85.81]) by mx1.freebsd.org (Postfix) with SMTP id 55EA78FC16 for ; Sun, 4 Jan 2009 12:11:28 +0000 (UTC) (envelope-from nrml@att.net) Received: (qmail 90290 invoked by uid 60001); 4 Jan 2009 12:11:27 -0000 X-YMail-OSG: Yoe5rjcVM1lF5oOTJhSf.S2iWmG4ziiZ.jcGGoQXt6Y7oKjgc4lleoIsnyAzydMlj2FrU6LUtotnzn1mkG5FMgZv7wF_P_NPktRKXMxW6cJpsYxQY0AUTvin.7PuccQpoI5o3qMQZWmIMWfDu2viO8kRSesLASc.4XEOJdmdKXZof9igfhyQ2w9br0R7rtQATrKzUEpnt99pBXSyM_emeyRDYOkW Received: from [69.43.143.172] by web83809.mail.sp1.yahoo.com via HTTP; Sun, 04 Jan 2009 04:11:27 PST X-Mailer: YahooMailWebService/0.7.218.2 Date: Sun, 4 Jan 2009 04:11:27 -0800 (PST) From: Gabe To: "Bjoern A. Zeeb" In-Reply-To: <20090104110430.I45399@maildrop.int.zabbadoz.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <881287.90275.qm@web83809.mail.sp1.yahoo.com> Cc: freebsd-net@freebsd.org Subject: Re: +ipsec_common_input: no key association found for SA X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: nrml@att.net List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jan 2009 12:11:28 -0000 > From: Bjoern A. Zeeb > Subject: Re: +ipsec_common_input: no key association found for SA > To: "Gabe" > Cc: freebsd-net@freebsd.org > Date: Sunday, January 4, 2009, 3:24 AM > On Sun, 4 Jan 2009, Gabe wrote: > > Hi, > > >>> Ok, can you try running the following script > and see > >> if the > >>> output > >>> times match your racoon restarts or the log > entries? > > You hadn't answered that question to correlate the > tcpdump with racoon > restarts and kernel log entries. > > If you do that, you may want to run the script for two > hours or four > to actually see more changes than just the initial one. > > Check the syslog timestamps in the logfile where your > kernel messages > go to (might be /var/log/messages) for the > ipsec_common_input lines. > Perhaps grep upfront before startung the script to be sure > that they > are there. > I understand. I'm having to rebuild "box" (unrelated) so this will have to wait, I will definitely do it as mentioned above. > > I'm still unable to find the cause for this. Does > anyone know what the above output is referring to? > > I think David DeSimone had last explained it to you: > http://lists.freebsd.org/pipermail/freebsd-net/2008-December/020611.html > > Maybe it would be time to read the RFC now; I'll try it > in my own > words again and shorter. > > Your IPsec Policy makes your racoons negotiate a Security > Assosiaction > for some parameters (keys, lieftime, ..). There will be one > for each > direction. One thing negotiated is the security policy > index, the > number we are tracing. This 'number' is put into > each packet one of the > boxes send encrypted to the other for the given direction. > > What your kernel tells you is that the number in the packet > received > does not make sense to the box receiving it. Let's say > the SPI received in > the packet from the other box is unknown on the receiver > side. That's > why the kernel complains. > Without the proper SPI the kernel will not be able to find > the proper > other parameters for this packet, and thus will not be able > to decrypt > the packet. > > > What we are trying to find out at the moment is to identify > where > exactly the wrong SPI is coming from. This could be: > - whatever the boxes negotiated gets out of sync > - a patch like the NAT-T patch could corrupt the packet > - a software bug in where the kernel or racoon > - ... > > To narrow this down from "everywhere" to > "here" it is important to see > where the values match, where not and when they do not > match - thus > correlating information from the time racoon gets > restarted, the > kernel prints the log message and what tcpdump is showing. > It's > important to get all this information for the same > problematic moment, > timestamped. If one is missing it's like a 1000 pieces > puzzle with > only 600 pieces included. > > One more question that hadn't been asked so far - what > architectures > (i386, amd64, sparc, arm, ..) are box and box2 and which > version of > freebsd are they running; I assume they are both on > freebsd? > They're i386. This is uname -a on "box": FreeBSD box.domain.tld 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Fri Dec 12 07:11:30 PST 2008 root@box.domain.tld:/usr/obj/usr/src/sys/KERNEL i386 This is uname -a on "box2": FreeBSD box2.domain.tld 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #5: Fri Dec 26 01:48:31 PST 2008 root@box2.domain.tld:/usr/obj/usr/src/sys/KERNEL i386 One thing I found to be interesting is that "box2" no longer spews out the ipsec_common_input message after I corrected the 'spdadd' lines. So perhaps this is related to the different kernel sources version. Either way I'll report back once I'm finished rebuilding "box" From owner-freebsd-net@FreeBSD.ORG Sun Jan 4 12:29:04 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31484106566B for ; Sun, 4 Jan 2009 12:29:04 +0000 (UTC) (envelope-from vwe@freebsd.org) Received: from frontmail.ipactive.de (frontmail.maindns.de [85.214.95.103]) by mx1.freebsd.org (Postfix) with ESMTP id B25738FC12 for ; Sun, 4 Jan 2009 12:29:03 +0000 (UTC) (envelope-from vwe@freebsd.org) Received: from mail.vtec.ipme.de (Q7c0c.q.ppp-pool.de [89.53.124.12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id 4C313128844; Sun, 4 Jan 2009 12:56:31 +0100 (CET) Received: from [192.168.16.4] (dardanos.sz.vwsoft.com [192.168.16.4]) by mail.vtec.ipme.de (Postfix) with ESMTP id 799EC2E916; Sun, 4 Jan 2009 12:56:22 +0100 (CET) Message-ID: <4960A3E5.7000906@freebsd.org> Date: Sun, 04 Jan 2009 12:56:21 +0100 From: Volker Werth User-Agent: Thunderbird 2.0.0.18 (X11/20081203) MIME-Version: 1.0 To: KES References: <200901031502.n03F2KbP042269@freefall.freebsd.org> <666141730.20090104114754@yandex.ru> In-Reply-To: <666141730.20090104114754@yandex.ru> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit MailScanner-NULL-Check: 1231674986.9266@bgEs2BWAQjq4auAJwoalyw X-MailScanner-ID: 799EC2E916.3E381 X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: vwe@freebsd.org X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: vwe@freebsd.org Cc: freebsd-net@FreeBSD.org Subject: Re: kern/129074: [ppp] [panic] kernel panic with pppoe_server X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Jan 2009 12:29:04 -0000 On 01/04/09 10:47, KES wrote: > Çäðàâñòâóéòå, Vwe. > > Âû ïèñàëè 3 ÿíâàðÿ 2009 ã., 17:02:20: > > vFo> Synopsis: [ppp] [panic] kernel panic with pppoe_server > > vFo> State-Changed-From-To: feedback->closed > Eugene, > Strange, I have replied to email and provide requested information... sorry, but we can't guess where to look for any postings when working on a PR. Please understand we cannot use google for an hour just to check if somebody has sent an email to the pope or anybody else anywhere in the world. We need relevant information being ATTACHED TO THE PR! > > kes# pppd --version > pppd version 2.3 patch level 5 > > > /etc/ppp/ppp.conf > default: > set log Phase Chat LCP IPCP CCP tun command > > adsl: > set log Phase LCP tun command > set device PPPoE:rl0:ukrtelecom > # enable lqr > # enable dns > disable ipv6cp > set cd 10 > set dial > # set login > set redial 0 0 > set reconnect random 999 > set mtu 1492 > set mru 1492 > set authname name > set authkey password > # add! default HISADD > > ppp[348]: tun0: Phase: Pap Input: FAILURE (insufficient resources available to authenticate user) > or > ppp[348]: tun0: Phase: Pap Output: ******** > last message repeated 2 times > ppp[348]: tun0: Phase: Auth: No response from server > > As you can see my ISP respond with error. After 10-15 trying to login > to ISP my server will reboot with kernel panic. > Ok, I don't care if your ISP has resources or not to serve it's customers but I would be interested in the actual kernel panic. Better, please give us the full backtrace and everything else to investigate this. Thank you for your understanding. Volker From owner-freebsd-net@FreeBSD.ORG Sun Jan 4 14:09:47 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0898106566C; Sun, 4 Jan 2009 14:09:47 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B79998FC17; Sun, 4 Jan 2009 14:09:47 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n04E9l8u018204; Sun, 4 Jan 2009 14:09:47 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n04E9lBa018200; Sun, 4 Jan 2009 14:09:47 GMT (envelope-from vwe) Date: Sun, 4 Jan 2009 14:09:47 GMT Message-Id: <200901041409.n04E9lBa018200@freefall.freebsd.org> To: vwe@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/96030: [bfe] [patch] Install hangs with Broadcomm 440x NIC installed X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Jan 2009 14:09:48 -0000 Synopsis: [bfe] [patch] Install hangs with Broadcomm 440x NIC installed Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: vwe Responsible-Changed-When: Sun Jan 4 14:07:38 UTC 2009 Responsible-Changed-Why: reassign to net team There hasn't been any feedback for 2.5 years whether this issue is still true or the attached patch solves it. By checking recent sources, it looks like the patch is outdated. Leaving it to the net team for a decision what to do about the patch. http://www.freebsd.org/cgi/query-pr.cgi?pr=96030 From owner-freebsd-net@FreeBSD.ORG Sun Jan 4 15:26:31 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8B29A1065676; Sun, 4 Jan 2009 15:26:31 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 625748FC0C; Sun, 4 Jan 2009 15:26:31 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n04FQVtk078303; Sun, 4 Jan 2009 15:26:31 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n04FQV8W078299; Sun, 4 Jan 2009 15:26:31 GMT (envelope-from linimon) Date: Sun, 4 Jan 2009 15:26:31 GMT Message-Id: <200901041526.n04FQV8W078299@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: bin/130159: [patch] ppp(8) fails to correctly set routes X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Jan 2009 15:26:32 -0000 Old Synopsis: [patch] ppp fail to correctly set routes New Synopsis: [patch] ppp(8) fails to correctly set routes Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sun Jan 4 15:25:14 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=130159 From owner-freebsd-net@FreeBSD.ORG Sun Jan 4 15:46:42 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 069A1106566C; Sun, 4 Jan 2009 15:46:42 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D157C8FC14; Sun, 4 Jan 2009 15:46:41 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n04FkfSK094038; Sun, 4 Jan 2009 15:46:41 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n04Fkfx0094034; Sun, 4 Jan 2009 15:46:41 GMT (envelope-from vwe) Date: Sun, 4 Jan 2009 15:46:41 GMT Message-Id: <200901041546.n04Fkfx0094034@freefall.freebsd.org> To: aragon@phat.za.net, vwe@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/125079: [ppp] host routes added by ppp with gateway flag (regression) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jan 2009 15:46:42 -0000 Synopsis: [ppp] host routes added by ppp with gateway flag (regression) State-Changed-From-To: open->closed State-Changed-By: vwe State-Changed-When: Sun Jan 4 15:45:32 UTC 2009 State-Changed-Why: closing this PR in favour of bin/130159 (seems to be the same issue) which contains a patch http://www.freebsd.org/cgi/query-pr.cgi?pr=125079 From owner-freebsd-net@FreeBSD.ORG Sun Jan 4 15:47:03 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D0791065673; Sun, 4 Jan 2009 15:47:03 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 14CDC8FC1A; Sun, 4 Jan 2009 15:47:03 +0000 (UTC) (envelope-from vwe@FreeBSD.org) Received: from freefall.freebsd.org (vwe@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n04Fl2On094078; Sun, 4 Jan 2009 15:47:02 GMT (envelope-from vwe@freefall.freebsd.org) Received: (from vwe@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n04Fl2iC094074; Sun, 4 Jan 2009 15:47:02 GMT (envelope-from vwe) Date: Sun, 4 Jan 2009 15:47:02 GMT Message-Id: <200901041547.n04Fl2iC094074@freefall.freebsd.org> To: tcs@kitty.2y.idv.tw, vwe@FreeBSD.org, freebsd-net@FreeBSD.org From: vwe@FreeBSD.org Cc: Subject: Re: kern/122068: [ppp] ppp can not set the correct interface with pptpd X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 04 Jan 2009 15:47:03 -0000 Synopsis: [ppp] ppp can not set the correct interface with pptpd State-Changed-From-To: open->closed State-Changed-By: vwe State-Changed-When: Sun Jan 4 15:46:55 UTC 2009 State-Changed-Why: closing this PR in favour of bin/130159 (seems to be the same issue) which contains a patch http://www.freebsd.org/cgi/query-pr.cgi?pr=122068 From owner-freebsd-net@FreeBSD.ORG Mon Jan 5 03:00:54 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86B32106564A for ; Mon, 5 Jan 2009 03:00:54 +0000 (UTC) (envelope-from freebsd@chrisbuechler.com) Received: from mail.livebsd.com (mail.livebsd.com [69.64.6.14]) by mx1.freebsd.org (Postfix) with SMTP id 2F2B18FC2A for ; Mon, 5 Jan 2009 03:00:53 +0000 (UTC) (envelope-from freebsd@chrisbuechler.com) Received: (qmail 19133 invoked by uid 89); 5 Jan 2009 02:34:12 -0000 Received: from unknown (HELO ?10.0.64.15?) (96.28.38.25) by 172.29.29.14 with SMTP; 5 Jan 2009 02:34:12 -0000 Message-ID: <496171A3.8030000@chrisbuechler.com> Date: Sun, 04 Jan 2009 21:34:11 -0500 From: Chris Buechler User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Blackberry Bold on FreeBSD ath AP not working X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jan 2009 03:00:54 -0000 Has anyone ever tried connecting a Blackberry Bold to a FreeBSD access point using an Atheros card? The card is an Atheros 5212, using FreeBSD 7.0. Every other wireless device that has been tried on this network works fine, but this Blackberry connects, gets a DHCP lease, and then sends ARP requests that get no reply. It behaves the same with the wireless open and using WPA or WPA2. The ath card is bridged to an Ethernet interface with if_bridge, which works flawlessly for everything but this Blackberry. The Blackberry works fine on several other wireless networks it has been tried on. capture of the Blackberry's ARP requests here: http://chrisbuechler.com/temp/bb-arp.pcap They're a bit different from the ARP requests of every other wireless device tried on this AP (i.e. the ones that work), in that they aren't padded to 60 byte frames, but I don't think that should be a problem. Anyone ever tried this, or have any idea what might be going on here? thanks, Chris From owner-freebsd-net@FreeBSD.ORG Mon Jan 5 04:14:25 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A23D1106566C for ; Mon, 5 Jan 2009 04:14:25 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [199.26.172.34]) by mx1.freebsd.org (Postfix) with ESMTP id 7FB9C8FC08 for ; Mon, 5 Jan 2009 04:14:25 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id n054EPlc048913 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sun, 4 Jan 2009 20:14:25 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id n054EPRI048912 for freebsd-net@freebsd.org; Sun, 4 Jan 2009 20:14:25 -0800 (PST) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA10835; Sun, 4 Jan 09 20:13:09 PST Date: Sun, 04 Jan 2009 20:15:30 -0800 From: perryh@pluto.rain.com To: freebsd-net@freebsd.org Message-Id: <49618962.WvA2bFthdzGdSO/b%perryh@pluto.rain.com> References: <495edc8b.yfwTDGtb9G/8NMur%perryh@pluto.rain.com> <20090103154232.P28770@sola.nimnet.asn.au> In-Reply-To: <20090103154232.P28770@sola.nimnet.asn.au> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: (partly) SOLVED: tun0 not responding to ping X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Jan 2009 04:14:25 -0000 Ian Smith wrote: > On Fri, 2 Jan 2009, perryh@pluto.rain.com wrote: > > > Why would a local interface, reported as up in ifconfig, not respond > > to a ping of its own IP address? The tun0 reported below doesn't, ... > > $ ifconfig -a ... > > tun0: flags=8051 mtu 1412 > > inet6 fe80::2b0:d0ff:fe28:ad4f%tun0 prefixlen 64 scopeid 0x4 > > inet ZZZ.ZZZ.233.42 --> ZZZ.ZZZ.233.42 netmask 0xffffffff > > Opened by PID 24635 > > I don't know if this is relevant or not, but I've never seen a point to > point interface use the same IP address on both ends of its link before. It turns out to be normal -- or at least tolerable -- for a tun(4) interface used by vpnc to have the same IP address at both ends. It started working when I added NAT Traversal Mode cisco-udp to vpnc.conf. (Presumably not all configurations of the Cisco 3000 will need that, else it would be the default, but it seems to be correct for the one involved here.) I never did figure out why that kept the interface from responding to a ping of its own address :( From owner-freebsd-net@FreeBSD.ORG Mon Jan 5 07:09:44 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 342B71065672 for ; Mon, 5 Jan 2009 07:09:44 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outO.internet-mail-service.net (outo.internet-mail-service.net [216.240.47.238]) by mx1.freebsd.org (Postfix) with ESMTP id 1A14E8FC0C for ; Mon, 5 Jan 2009 07:09:44 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 6B2E0234B for ; Sun, 4 Jan 2009 23:09:44 -0800 (PST) X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id 5BADD2D6023 for ; Sun, 4 Jan 2009 23:09:43 -0800 (PST) Message-ID: <4961B236.8040607@elischer.org> Date: Sun, 04 Jan 2009 23:09:42 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105) MIME-Version: 1.0 To: FreeBSD Net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Request for assitance: VIMAGE performance testing X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Jan 2009 07:09:44 -0000 The current state of vimage in -current is such that we can do some performance testing. Unfortunatly I don't have a test plan in place.. The aim is to run some tests on systems with VIMAGE_GLOBALS defined and not defined and see if there are any detectable differences. Firstly I have done some simple tests myself (e.g. scps, pings, ftps) but it would be very helpful if people coudl compile up an alternative kernel with VIMAGE_GLOBALS defined and see if their everyday workloads show any noticeable differences. nothing special.. just time a few things you often do that may be special to you and are network intensive, and then switch to the other kernel and try it again. Then put the results in ministat (saying whether bigger is better or worse) Ok do it several times for statistical purposes, reply to me (and the list) and let us know if you are seeing differences anywhere.. regards.. Julian (p.s. I will put numbers up too when I get some more) From owner-freebsd-net@FreeBSD.ORG Mon Jan 5 10:13:31 2009 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5782B1065687 for ; Mon, 5 Jan 2009 10:13:31 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.229]) by mx1.freebsd.org (Postfix) with ESMTP id 165D68FC19 for ; Mon, 5 Jan 2009 10:13:30 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id f9so6348350rvb.2 for ; Mon, 05 Jan 2009 02:13:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=MZwlTRPAxWlBwwwESdLw03YUABiNhL/m7unvBEoiL8w=; b=OKckEC3/E9UQ2L2ro9YEcc510FvtdvWPmIcA0PwXHJUncKv6q2cIR5GwXQKTT9eaVY nU8h41fp5GwtuzrWGvB1AFePZ3r+6XEuOvGEMYUGecEm8uBT2vDzJdAn/Q0cd0ar9XtU 068Jmk/6Yx3kC35RkO1o3jubcM0m7PGcKZePg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=M3lByq82bfEhe6up53/jIm17Ugjr7VsclrHSOojVfavj/8Ji8OQu8kzdT4fgVxgQ09 Gx7xRQ+LJ641CR+Zlo4ZUZ5ppACv6PrOjr5PBtOf752UhAL11Lgo5L0+lw+Zr0gX/Lw1 eRKzISHOKyfaqnO2s9JIviyPZV521g9e6ZrPo= Received: by 10.140.188.19 with SMTP id l19mr10316547rvf.51.1231149103433; Mon, 05 Jan 2009 01:51:43 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id g22sm32714964rvb.1.2009.01.05.01.51.39 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 05 Jan 2009 01:51:42 -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 n059pa4o003542 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Jan 2009 18:51:36 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id n059pZZd003541; Mon, 5 Jan 2009 18:51:35 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 5 Jan 2009 18:51:35 +0900 From: Pyun YongHyeon To: Garrett Cooper Message-ID: <20090105095135.GH1842@cdnetworks.co.kr> References: <20081224021016.GF95088@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: net@freebsd.org Subject: Re: Annoyance with msk(4) going up and down when initializing interface 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: Mon, 05 Jan 2009 10:13:37 -0000 On Fri, Jan 02, 2009 at 03:31:33PM -0800, Garrett Cooper wrote: > Hi Pyun, > I've noticed an issue for a while now with my chipset (I think that > this is post an MFC between 7.0 and 7.1, but I could be wrong). > Basically, each CPU (with the ULE scheduler) grabs the task to check > for media status, goes out and attempts to get an IP, and if the > timing of the status modifications is just right, one of the CPU's > will mark the link up and others will mark it down, and it will stay > down. No, the link state change event is protected by driver lock. > Same thing occurs when trying to get a DHCP request -- there will > typically be multiple requests and ACK's for any given requests. > This occurs with my onboard NICs on my P5K-e motherboards on 7.1- > rc[12], and also 8-CURRENT. If you're referring to multiple link UP/DOWN messages when dhclient(8) trying to get an IP address via DHCP it's normal for drivers that rely on mii(4) state change event. Technically it's not normal but it's the way how it was implemented on most drivers. Ideally drivers should not need to reset controllers when it's not absolutely required to reset hardwares but most drivers blindly reset hardware which in turn results in link renegotiation. You can see similiar behavour when alias addresseses are added to the interface. Because controllers that have complex firmware/embedded OS will take time to complete the reset operation, the reset operation would be pain to these controllers. Long time ago I added a hack to em(4) to mitigate the issue but I don't think it's way to go. NetBSD seems to have right fix in ioctl handler. However the approach will require careful checking of multicasting code of all drivers. I don't have all hardwares to test this and I don't know hardware internals of all drivers. -- Regards, Pyun YongHyeon From owner-freebsd-net@FreeBSD.ORG Mon Jan 5 11:06:56 2009 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64327106564A for ; Mon, 5 Jan 2009 11:06:56 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 51A468FC1D for ; Mon, 5 Jan 2009 11:06:56 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n05B6uJj002864 for ; Mon, 5 Jan 2009 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n05B6tH1002860 for freebsd-net@FreeBSD.org; Mon, 5 Jan 2009 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 5 Jan 2009 11:06:55 GMT Message-Id: <200901051106.n05B6tH1002860@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-net@FreeBSD.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jan 2009 11:06:56 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o bin/130159 net [patch] ppp(8) fails to correctly set routes o kern/130109 net [ipfw] Can not set fib for packets originated from loc f kern/130059 net [panic] Leaking 50k mbufs/hour o kern/129846 net [panic] /usr/sbin/ppp causes panic "Sleeping thread ow o kern/129793 net [ip6] [patch] Locking related leaks in the kernel (rou o kern/129750 net [ath] Atheros AR5006 exits on "cannot map register spa o kern/129719 net [tcp] [panic] Panic during shutdown, tcp_ctloutput: in o kern/129580 net [ndis] Netgear WG311v3 (ndis) causes kenel trap at boo o kern/129517 net [ipsec] [panic] double fault / stack overflow o kern/129508 net [panic] Kernel panic with EtherIP (may be related to S o kern/129352 net [xl] [patch] xl0 watchdog timeout o kern/129219 net [ppp] Kernel panic when using kernel mode ppp o kern/129135 net [vge] vge driver on a VIA mini-ITX not working o kern/128917 net [wpi] [panic] if_wpi and wpa+tkip causing kernel panic o kern/128884 net [msk] if_msk page fault while in kernel mode o kern/128840 net [igb] page fault under load with igb/LRO o bin/128602 net [an] wpa_supplicant(8) crashes with an(4) o kern/128598 net [bluetooth] WARNING: attempt to net_add_domain(bluetoo o kern/128448 net [nfs] 6.4-RC1 Boot Fails if NFS Hostname cannot be res o conf/128334 net [request] use wpa_cli in the "WPA DHCP" situation o bin/128295 net [patch] ifconfig(8) does not print TOE4 or TOE6 capabi o kern/128247 net [ip6] [panic] Fatal Trap 12 in ip6_forward = o conf/128030 net [request] Isn't it time to enable IPsec in GENERIC? o bin/128001 net wpa_supplicant(8), wlan(4), and wi(4) issues o kern/127928 net [tcp] [patch] TCP bandwidth gets squeezed every time t o kern/127834 net [ixgbe] [patch] wrong error counting o kern/127826 net [iwi] iwi0 driver has reduced performance and connecti o kern/127815 net [gif] [patch] if_gif does not set vlan attributes from o kern/127724 net [rtalloc] rtfree: 0xc5a8f870 has 1 refs f bin/127719 net arp: Segmentation fault (core dumped) s kern/127587 net [bge] [request] if_bge(4) doesn't support BCM576X fami f kern/127528 net [icmp]: icmp socket receives icmp replies not owned by o bin/127192 net routed(8) removes the secondary alias IP of interface f kern/127145 net [wi]: prism (wi) driver crash at bigger traffic o kern/127102 net [wpi] Intel 3945ABG low throughput o kern/127057 net [udp] Unable to send UDP packet via IPv6 socket to IPv o kern/127050 net [carp] ipv6 does not work on carp interfaces [regressi o kern/126945 net [carp] CARP interface destruction with ifconfig destro o kern/126924 net [an] [patch] printf -> device_printf and simplify prob o kern/126895 net [patch] [ral] Add antenna selection (marked as TBD) o kern/126874 net [vlan]: Zebra problem if ifconfig vlanX destroy o bin/126822 net wpa_supplicant(8): WPA PSK does not work in adhoc mode o kern/126714 net [carp] CARP interface renaming makes system no longer o kern/126695 net rtfree messages and network disruption upon use of if_ o kern/126688 net [ixgbe] [patch] 1.4.7 ixgbe driver panic with 4GB and f kern/126564 net [ath] doesn't work with my PCI-E X1 wireless network a o kern/126561 net [nlm] [patch] NLM (rpclockd) RPC UNLOCK failure (stall o kern/126475 net [ath] [panic] ath pcmcia card inevitably panics under o kern/126469 net [fxp] [panic] fxp(4) related kernel panic o kern/126339 net [ipw] ipw driver drops the connection o kern/126214 net [ath] txpower problem with Atheros wifi card o kern/126075 net [in] Network: internet control accesses beyond end of o bin/125922 net [patch] Deadlock in arp(8) o kern/125920 net [arp] Kernel Routing Table loses Ethernet Link status o kern/125845 net [netinet] [patch] tcp_lro_rx() should make use of hard o kern/125816 net [carp] [if_bridge] carp stuck in init when using bridg f kern/125502 net [ral] ifconfig ral0 scan produces no output unless in o kern/125258 net [socket] socket's SO_REUSEADDR option does not work o kern/125239 net [gre] kernel crash when using gre f kern/125195 net [fxp] fxp(4) driver failed to initialize device Intel o kern/124904 net [fxp] EEPROM corruption with Compaq NC3163 NIC o kern/124767 net [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 net [ieee80211] net80211 discards power-save queue packets o kern/124341 net [ral] promiscuous mode for wireless device ral0 looses o kern/124160 net [libc] connect(2) function loops indefinitely o kern/124127 net [msk] watchdog timeout (missed Tx interrupts) -- recov o kern/124021 net [ip6] [panic] page fault in nd6_output() o kern/123968 net [rum] [panic] rum driver causes kernel panic with WPA. p kern/123961 net [vr] [patch] Allow vr interface to handle vlans o kern/123892 net [tap] [patch] No buffer space available o kern/123881 net [tcp] Turning on TCP blackholing causes slow localhost o kern/123858 net [stf] [patch] stf not usable behind a NAT o kern/123796 net [ipf] FreeBSD 6.1+VPN+ipnat+ipf: port mapping does not o bin/123633 net ifconfig(8) doesn't set inet and ether address in one o kern/123617 net [tcp] breaking connection when client downloading file o kern/123603 net [tcp] tcp_do_segment and Received duplicate SYN o kern/123559 net [iwi] iwi periodically disassociates/associates [regre o bin/123465 net [ip6] route(8): route add -inet6 -interfac o kern/123463 net [ipsec] [panic] repeatable crash related to ipsec-tool o kern/123429 net [nfe] [hang] "ifconfig nfe up" causes a hard system lo o kern/123347 net [bge] bge1: watchdog timeout -- linkstate changed to D o conf/123330 net [nsswitch.conf] Enabling samba wins in nsswitch.conf c o kern/123256 net [wpi] panic: blockable sleep lock with wpi(4) f kern/123200 net [netgraph] Server failure due to netgraph mpd and dhcp f kern/123172 net [bce] Watchdog timeout problems with if_bce o kern/123160 net [ip] Panic and reboot at sysctl kern.polling.enable=0 o kern/123066 net [ipsec] [panic] kernel trap with ipsec o kern/122989 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/122954 net [lagg] IPv6 EUI64 incorrectly chosen for lagg devices o kern/122928 net [em] interface watchdog timeouts and stops receiving p f kern/122839 net [multicast] FreeBSD 7 multicast routing problem p kern/122794 net [lagg] Kernel panic after brings lagg(8) up if NICs ar o kern/122780 net [lagg] tcpdump on lagg interface during high pps wedge o kern/122772 net [em] em0 taskq panic, tcp reassembly bug causes radix o kern/122743 net [panic] vm_page_unwire: invalid wire count: 0 o kern/122697 net [ath] Atheros card is not well supported o kern/122685 net It is not visible passing packets in tcpdump(1) o kern/122551 net [bge] Broadcom 5715S no carrier on HP BL460c blade usi o kern/122427 net [apm] [panic] apm and mDNSResponder cause panic during o kern/122319 net [wi] imposible to enable ad-hoc demo mode with Orinoco o kern/122290 net [netgraph] [panic] Netgraph related "kmem_map too smal f kern/122252 net [ipmi] [bge] IPMI problem with BCM5704 (does not work o kern/122195 net [ed] Alignment problems in if_ed o kern/122058 net [em] [panic] Panic on em1: taskq o kern/122033 net [ral] [lor] Lock order reversal in ral0 at bootup [reg o kern/121983 net [fxp] fxp0 MBUF and PAE o kern/121872 net [wpi] driver fails to attach on a fujitsu-siemens s711 s kern/121774 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/121706 net [netinet] [patch] "rtfree: 0xc4383870 has 1 refs" emit o kern/121624 net [em] [regression] Intel em WOL fails after upgrade to o kern/121555 net [panic] Fatal trap 12: current process = 12 (swi1: net o kern/121443 net [gif] LOR icmp6_input/nd6_lookup o kern/121437 net [vlan] Routing to layer-2 address does not work on VLA o kern/121298 net [em] [panic] Fatal trap 12: page fault while in kernel o kern/121257 net [tcp] TSO + natd -> slow outgoing tcp traffic o kern/121181 net [panic] Fatal trap 3: breakpoint instruction fault whi o kern/121080 net [bge] IPv6 NUD problem on multi address config on bge0 o kern/120966 net [rum] kernel panic with if_rum and WPA encryption p docs/120945 net [patch] ip6(4) man page lacks documentation for TCLASS o kern/120566 net [request]: ifconfig(8) make order of arguments more fr o kern/120304 net [netgraph] [patch] netgraph source assumes 32-bit time o kern/120266 net [panic] gnugk causes kernel panic when closing UDP soc o kern/120232 net [nfe] [patch] Bring in nfe(4) to RELENG_6 o kern/120130 net [carp] [panic] carp causes kernel panics in any conste o kern/119945 net [rum] [panic] rum device in hostap mode, cause kernel o kern/119791 net [nfs] UDP NFS mount of aliased IP addresses from a Sol o kern/119617 net [nfs] nfs error on wpa network when reseting/shutdown f kern/119516 net [ip6] [panic] _mtx_lock_sleep: recursed on non-recursi o kern/119432 net [arp] route add -host -iface causes arp e o kern/119361 net [bge] bge(4) transmit performance problem o kern/119345 net [ath] Unsuported Atheros 5424/2424 and CPU speedstep n o kern/119225 net [wi] 7.0-RC1 no carrier with Prism 2.5 wifi card [regr o bin/118987 net ifconfig(8): ifconfig -l (address_family) does not wor o kern/118880 net [ip6] IP_RECVDSTADDR & IP_SENDSRCADDR not implemented a kern/118879 net [bge] [patch] bge has checksum problems on the 5703 ch o kern/118727 net [netgraph] [patch] [request] add new ng_pf module o kern/117448 net [carp] 6.2 kernel crash [regression] o kern/117423 net [vlan] Duplicate IP on different interfaces o bin/117339 net [patch] route(8): loading routing management commands o kern/117271 net [tap] OpenVPN TAP uses 99% CPU on releng_6 when if_tap o kern/117043 net [em] Intel PWLA8492MT Dual-Port Network adapter EEPROM o kern/116837 net [tun] [panic] [patch] ifconfig tunX destroy: panic o kern/116747 net [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile o bin/116643 net [patch] [request] fstat(1): add INET/INET6 socket deta o kern/116328 net [bge]: Solid hang with bge interface o kern/116185 net [iwi] if_iwi driver leads system to reboot o kern/116077 net [ip] [patch] 6.2-STABLE panic during use of multi-cast o kern/115239 net [ipnat] panic with 'kmem_map too small' using ipnat o kern/114915 net [patch] [pcn] pcn (sys/pci/if_pcn.c) ethernet driver f o kern/114839 net [fxp] fxp looses ability to speak with traffic o kern/114714 net [gre][patch] gre(4) is not MPSAFE and does not support o kern/113842 net [ip6] PF_INET6 proto domain state can't be cleared wit o kern/112722 net [udp] IP v4 udp fragmented packet reject o kern/112686 net [patm] patm driver freezes System (FreeBSD 6.2-p4) i38 o bin/112557 net [patch] ppp(8) lock file should not use symlink name o kern/112528 net [nfs] NFS over TCP under load hangs with "impossible p o kern/109733 net [bge] bge link state issues [regression] o kern/109470 net [wi] Orinoco Classic Gold PC Card Can't Channel Hop o kern/109308 net [pppd] [panic] Multiple panics kernel ppp suspected [r o bin/108895 net pppd(8): PPPoE dead connections on 6.2 [regression] o kern/108542 net [bce]: Huge network latencies with 6.2-RELEASE / STABL o kern/107944 net [wi] [patch] Forget to unlock mutex-locks o conf/107035 net [patch] bridge interface given in rc.conf not taking a o kern/106438 net [ipf] ipfilter: keep state does not seem to allow repl o kern/106316 net [dummynet] dummynet with multipass ipfw drops packets s kern/105943 net Network stack may modify read-only mbuf chain copies o bin/105925 net problems with ifconfig(8) and vlan(4) [regression] o conf/102502 net [patch] ifconfig name does't rename netgraph node in n o kern/102035 net [plip] plip networking disables parallel port printing o kern/101948 net [ipf] [panic] Kernel Panic Trap No 12 Page Fault - cau o kern/100519 net [netisr] suggestion to fix suboptimal network polling o kern/98978 net [ipf] [patch] ipfilter drops OOW packets under 6.1-Rel o kern/96030 net [bfe] [patch] Install hangs with Broadcomm 440x NIC in o kern/95288 net [pppd] [tty] [panic] if_ppp panic in sys/kern/tty_subr o kern/95277 net [netinet] [patch] IP Encapsulation mask_match() return o kern/95267 net packet drops periodically appear o kern/93378 net [tcp] Slow data transfer in Postfix and Cyrus IMAP (wo f kern/92552 net A serious bug in most network drivers from 5.X to 6.X o kern/92090 net [bge] bge0: watchdog timeout -- resetting s kern/91777 net [ipf] [patch] wrong behaviour with skip rule inside an o kern/91594 net [em] FreeBSD > 5.4 w/ACPI fails to detect Intel Pro/10 o kern/87521 net [ipf] [panic] using ipfilter "auth" keyword leads to k s kern/86920 net [ndis] ifconfig: SIOCS80211: Invalid argument [regress o kern/86103 net [ipf] Illegal NAT Traversal in IPFilter o kern/84202 net [ed] [patch] Holtek HT80232 PCI NIC recognition on Fre s kern/81147 net [net] [patch] em0 reinitialization while adding aliase o kern/80853 net [ed] [patch] add support for Compex RL2000/ISA in PnP o kern/79895 net [ipf] 5.4-RC2 breaks ipfilter NAT when using netgraph o bin/79228 net [patch] extend arp(8) to be able to create blackhole r o kern/78090 net [ipf] ipf filtering on bridged packets doesn't work if p kern/77913 net [wi] [patch] Add the APDL-325 WLAN pccard to wi(4) o kern/77273 net [ipf] ipfilter breaks ipv6 statefull filtering on 5.3 s kern/77195 net [ipf] [patch] ipfilter ioctl SIOCGNATL does not match o kern/70904 net [ipf] ipfilter ipnat problem with h323 proxy support o kern/64556 net [sis] if_sis short cable fix problems with NetGear FA3 s kern/60293 net FreeBSD arp poison patch o kern/54383 net [nfs] [patch] NFS root configurations without dynamic s bin/41647 net ifconfig(8) doesn't accept lladdr along with inet addr s kern/39937 net ipstealth issue a kern/38554 net [patch] changing interface ipaddress doesn't seem to w o kern/35442 net [sis] [patch] Problem transmitting runts in if_sis dri o kern/34665 net [ipf] [hang] ipfilter rcmd proxy "hangs". o kern/27474 net [ipf] [ppp] Interactive use of user PPP and ipfilter c o conf/23063 net [patch] for static ARP tables in rc.network 204 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Jan 5 11:07:52 2009 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65CEE106566C for ; Mon, 5 Jan 2009 11:07:52 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3AD788FC24 for ; Mon, 5 Jan 2009 11:07:52 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n05B7qga003942 for ; Mon, 5 Jan 2009 11:07:52 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n05B7paH003938 for net@FreeBSD.org; Mon, 5 Jan 2009 11:07:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 5 Jan 2009 11:07:51 GMT Message-Id: <200901051107.n05B7paH003938@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: net@FreeBSD.org Cc: Subject: Current problem reports assigned to net@FreeBSD.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jan 2009 11:07:52 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- s kern/117717 net [panic] Kernel panic with Bittorrent client. 1 problem total. From owner-freebsd-net@FreeBSD.ORG Mon Jan 5 13:13:25 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 393CB106566B; Mon, 5 Jan 2009 13:13:25 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 141F78FC19; Mon, 5 Jan 2009 13:13:25 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 9ED7546B2C; Mon, 5 Jan 2009 08:13:24 -0500 (EST) Date: Mon, 5 Jan 2009 13:13:24 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Lin Jui-Nan Eric In-Reply-To: <47713ee10901012249w65c659bbp3366e4d8ef25c59d@mail.gmail.com> Message-ID: References: <47713ee10812301206j12b35264o715976c154080a1b@mail.gmail.com> <47713ee10901012147k1f25c31bn512dd29b2b294ad5@mail.gmail.com> <47713ee10901012249w65c659bbp3366e4d8ef25c59d@mail.gmail.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, stable@freebsd.org Subject: Re: TCP packet out-of-order problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jan 2009 13:13:25 -0000 On Fri, 2 Jan 2009, Lin Jui-Nan Eric wrote: > After running "netstat -s -p tcp", we found that lots of packets are > discarded due to memory problems. We googled for it, and found that sysctl > oid "net.inet.tcp.reass.maxsegments" became 0, therefore packets never > reassembled. > > Then we checked our /boot/loader.conf and /etc/sysctl.conf, and found that > setting kern.ipc.nmbclusters="0" makes net.inet.tcp.reass.maxsegments=0. > After setting net.inet.tcp.reass.maxsegments="1600" in /boot/loader.conf, > the network works perfectly now. Was it set to 0 through a configuration error, or did the system auto-tune improperly? Robert N M Watson Computer Laboratory University of Cambridge > > Thank you all for the help! > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Mon Jan 5 15:24:54 2009 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 61B021065675 for ; Mon, 5 Jan 2009 15:24:54 +0000 (UTC) (envelope-from edwin@mavetju.org) Received: from k7.mavetju.org (ppp121-44-155-248.lns10.syd7.internode.on.net [121.44.155.248]) by mx1.freebsd.org (Postfix) with ESMTP id 0AA9E8FC23 for ; Mon, 5 Jan 2009 15:24:53 +0000 (UTC) (envelope-from edwin@mavetju.org) Received: by k7.mavetju.org (Postfix, from userid 1001) id 621574505A; Mon, 5 Jan 2009 21:43:25 +1100 (EST) Date: Mon, 5 Jan 2009 21:43:25 +1100 From: Edwin Groothuis To: Pyun YongHyeon Message-ID: <20090105104325.GA70686@mavetju.org> References: <20081224021016.GF95088@cdnetworks.co.kr> <20090105095135.GH1842@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090105095135.GH1842@cdnetworks.co.kr> User-Agent: Mutt/1.4.2.3i Cc: Garrett Cooper , net@freebsd.org Subject: Re: Annoyance with msk(4) going up and down when initializing 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: Mon, 05 Jan 2009 15:24:54 -0000 On Mon, Jan 05, 2009 at 06:51:35PM +0900, Pyun YongHyeon wrote: > On Fri, Jan 02, 2009 at 03:31:33PM -0800, Garrett Cooper wrote: > > Hi Pyun, > > I've noticed an issue for a while now with my chipset (I think that > > this is post an MFC between 7.0 and 7.1, but I could be wrong). > > Basically, each CPU (with the ULE scheduler) grabs the task to check > > for media status, goes out and attempts to get an IP, and if the > > timing of the status modifications is just right, one of the CPU's > > will mark the link up and others will mark it down, and it will stay > > down. > > No, the link state change event is protected by driver lock. > > > Same thing occurs when trying to get a DHCP request -- there will > > typically be multiple requests and ACK's for any given requests. > > This occurs with my onboard NICs on my P5K-e motherboards on 7.1- > > rc[12], and also 8-CURRENT. > > If you're referring to multiple link UP/DOWN messages when > dhclient(8) trying to get an IP address via DHCP it's normal for > drivers that rely on mii(4) state change event. Technically it's > not normal but it's the way how it was implemented on most drivers. > Ideally drivers should not need to reset controllers when it's not > absolutely required to reset hardwares but most drivers blindly > reset hardware which in turn results in link renegotiation. You can > see similiar behavour when alias addresseses are added to the > interface. Because controllers that have complex firmware/embedded > OS will take time to complete the reset operation, the reset > operation would be pain to these controllers. Long time ago I added > a hack to em(4) to mitigate the issue but I don't think it's way to > go. > NetBSD seems to have right fix in ioctl handler. However the > approach will require careful checking of multicasting code of all > drivers. I don't have all hardwares to test this and I don't know > hardware internals of all drivers. When booting diskless via PXE I sometimes run into this problem too: machine boots via NFS, NIC gets down and up and oh, it doesn't work anymore. Edwin -- Edwin Groothuis Website: http://www.mavetju.org/ edwin@mavetju.org Weblog: http://www.mavetju.org/weblog/ From owner-freebsd-net@FreeBSD.ORG Mon Jan 5 16:39:30 2009 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A27F11065673; Mon, 5 Jan 2009 16:39:30 +0000 (UTC) (envelope-from kes-kes@yandex.ru) Received: from forwards4.yandex.ru (forwards4.yandex.ru [77.88.32.20]) by mx1.freebsd.org (Postfix) with ESMTP id 21C988FC1A; Mon, 5 Jan 2009 16:39:30 +0000 (UTC) (envelope-from kes-kes@yandex.ru) Received: from smtp15.yandex.ru (smtp15.yandex.ru [77.88.32.85]) by forwards4.yandex.ru (Yandex) with ESMTP id 1E2DA4C5642; Mon, 5 Jan 2009 19:39:29 +0300 (MSK) Received: from 38-83-113-92.pool.ukrtel.net ([92.113.83.38]:43012 "EHLO HOMEUSER" smtp-auth: "kes-kes" TLS-CIPHER: TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S4866255AbZAEQjX (ORCPT + 1 other); Mon, 5 Jan 2009 19:39:23 +0300 X-Yandex-Spam: 1 X-Yandex-Front: smtp15 X-Yandex-TimeMark: 1231173563 X-BornDate: 1149541200 X-Yandex-Karma: 0 X-Yandex-KarmaStatus: 0 X-MsgDayCount: 3 X-Comment: RFC 2476 MSA function at smtp15.yandex.ru logged sender identity as: kes-kes Date: Mon, 5 Jan 2009 18:39:22 +0200 From: KES X-Mailer: The Bat! (v4.0.24) Professional Organization: SaftTen X-Priority: 3 (Normal) Message-ID: <1652352570.20090105183922@yandex.ru> To: Volker Werth In-Reply-To: <4960A3E5.7000906@freebsd.org> References: <200901031502.n03F2KbP042269@freefall.freebsd.org> <666141730.20090104114754@yandex.ru> <4960A3E5.7000906@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: freebsd-net@FreeBSD.org Subject: Re[2]: kern/129074: [ppp] [panic] kernel panic with pppoe_server X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: KES List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jan 2009 16:39:30 -0000 ЗдравÑтвуйте, Volker. Ð’Ñ‹ пиÑали 4 ÑÐ½Ð²Ð°Ñ€Ñ 2009 г., 13:56:21: VW> On 01/04/09 10:47, KES wrote: >> Çäðàâñòâóéòå, Vwe. >> >> Âû ïèñàëè 3 ÿíâàðÿ 2009 ã., 17:02:20: >> >> vFo> Synopsis: [ppp] [panic] kernel panic with pppoe_server >> >> vFo> State-Changed-From-To: feedback->closed >> VW> Eugene, >> Strange, I have replied to email and provide requested information... VW> sorry, but we can't guess where to look for any postings when working on VW> a PR. Please understand we cannot use google for an hour just to check VW> if somebody has sent an email to the pope or anybody else anywhere in VW> the world. We need relevant information being ATTACHED TO THE PR! I had reply as usually. Mybe my letter was droped somewhere... =( >> >> kes# pppd --version >> pppd version 2.3 patch level 5 >> >> >> /etc/ppp/ppp.conf >> default: >> set log Phase Chat LCP IPCP CCP tun command >> >> adsl: >> set log Phase LCP tun command >> set device PPPoE:rl0:ukrtelecom >> # enable lqr >> # enable dns >> disable ipv6cp >> set cd 10 >> set dial >> # set login >> set redial 0 0 >> set reconnect random 999 >> set mtu 1492 >> set mru 1492 >> set authname name >> set authkey password >> # add! default HISADD >> >> ppp[348]: tun0: Phase: Pap Input: FAILURE (insufficient resources available to authenticate user) >> or >> ppp[348]: tun0: Phase: Pap Output: ******** >> last message repeated 2 times >> ppp[348]: tun0: Phase: Auth: No response from server >> >> As you can see my ISP respond with error. After 10-15 trying to login >> to ISP my server will reboot with kernel panic. >> VW> Ok, I don't care if your ISP has resources or not to serve it's VW> customers but I would be interested in the actual kernel panic. VW> Better, please give us the full backtrace and everything else to VW> investigate this. VW> Thank you for your understanding. VW> Volker There were some problem with server of my ISP. Now they fix their server. So now pppd works fine. If problem will repeat I will send tcpdump of PPPoE traffic. -- С уважением, KES mailto:kes-kes@yandex.ru From owner-freebsd-net@FreeBSD.ORG Mon Jan 5 21:46:53 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF78D106564A for ; Mon, 5 Jan 2009 21:46:53 +0000 (UTC) (envelope-from vwe@freebsd.org) Received: from frontmail.ipactive.de (frontmail.maindns.de [85.214.95.103]) by mx1.freebsd.org (Postfix) with ESMTP id 59A508FC12 for ; Mon, 5 Jan 2009 21:46:53 +0000 (UTC) (envelope-from vwe@freebsd.org) Received: from mail.vtec.ipme.de (Q7d36.q.ppp-pool.de [89.53.125.54]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id 3D32812883F; Mon, 5 Jan 2009 22:46:43 +0100 (CET) Received: from [192.168.16.4] (dardanos.sz.vwsoft.com [192.168.16.4]) by mail.vtec.ipme.de (Postfix) with ESMTP id A60382E916; Mon, 5 Jan 2009 22:46:23 +0100 (CET) From: vwe To: KES In-Reply-To: <1652352570.20090105183922@yandex.ru> References: <200901031502.n03F2KbP042269@freefall.freebsd.org> <666141730.20090104114754@yandex.ru> <4960A3E5.7000906@freebsd.org> <1652352570.20090105183922@yandex.ru> Content-Type: text/plain; charset=iso-2022-jp Date: Mon, 05 Jan 2009 22:45:06 +0100 Message-Id: <1231191906.16660.1.camel@dardanos.sz.vwsoft.com> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit MailScanner-NULL-Check: 1231796797.39343@7cBuyBQxp29WfSAGIvHJGw X-MailScanner-ID: A60382E916.A8F82 X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: vwe@freebsd.org X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: vwe@freebsd.org Cc: freebsd-net@FreeBSD.org Subject: Re: Re[2]: kern/129074: [ppp] [panic] kernel panic with pppoe_server X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Jan 2009 21:46:54 -0000 On Mon, 2009-01-05 at 18:39 +0200, KES wrote: > $B')'U'b'Q'S'c'd'S'e'['d'V(B, Volker. > > $B'#'m(B $B'a'Z'c'Q']'Z(B 4 $B'q'_'S'Q'b'q(B 2009 $B'T(B., 13:56:21: > > VW> On 01/04/09 10:47, KES wrote: > >> , Vwe. > >> > >> 3 2009 ., 17:02:20: > >> > >> vFo> Synopsis: [ppp] [panic] kernel panic with pppoe_server > >> > >> vFo> State-Changed-From-To: feedback->closed > >> > > VW> Eugene, > > >> Strange, I have replied to email and provide requested information... > > VW> sorry, but we can't guess where to look for any postings when working on > VW> a PR. Please understand we cannot use google for an hour just to check > VW> if somebody has sent an email to the pope or anybody else anywhere in > VW> the world. We need relevant information being ATTACHED TO THE PR! > > I had reply as usually. Mybe my letter was droped somewhere... =( > > >> > >> kes# pppd --version > >> pppd version 2.3 patch level 5 > >> > >> > >> /etc/ppp/ppp.conf > >> default: > >> set log Phase Chat LCP IPCP CCP tun command > >> > >> adsl: > >> set log Phase LCP tun command > >> set device PPPoE:rl0:ukrtelecom > >> # enable lqr > >> # enable dns > >> disable ipv6cp > >> set cd 10 > >> set dial > >> # set login > >> set redial 0 0 > >> set reconnect random 999 > >> set mtu 1492 > >> set mru 1492 > >> set authname name > >> set authkey password > >> # add! default HISADD > >> > >> ppp[348]: tun0: Phase: Pap Input: FAILURE (insufficient resources available to authenticate user) > >> or > >> ppp[348]: tun0: Phase: Pap Output: ******** > >> last message repeated 2 times > >> ppp[348]: tun0: Phase: Auth: No response from server > >> > >> As you can see my ISP respond with error. After 10-15 trying to login > >> to ISP my server will reboot with kernel panic. > >> > > VW> Ok, I don't care if your ISP has resources or not to serve it's > VW> customers but I would be interested in the actual kernel panic. > > VW> Better, please give us the full backtrace and everything else to > VW> investigate this. > > VW> Thank you for your understanding. > > VW> Volker > > > There were some problem with server of my ISP. Now they fix their > server. So now pppd works fine. > If problem will repeat I will send tcpdump of PPPoE traffic. > Eugene, if you should find a coredump for analysis or if your server will ever experience the same panic again, please drop us a note (cc bug-followup@ to have the information attached to the GNATS PR) and we'll reopen this ticket. Thank you for providing feedback! Volker From owner-freebsd-net@FreeBSD.ORG Tue Jan 6 04:25:09 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40FA21065672; Tue, 6 Jan 2009 04:25:09 +0000 (UTC) (envelope-from ericlin@tamama.org) Received: from mail-gx0-f18.google.com (mail-gx0-f18.google.com [209.85.217.18]) by mx1.freebsd.org (Postfix) with ESMTP id CB3A48FC18; Tue, 6 Jan 2009 04:25:08 +0000 (UTC) (envelope-from ericlin@tamama.org) Received: by gxk11 with SMTP id 11so192815gxk.19 for ; Mon, 05 Jan 2009 20:25:08 -0800 (PST) Received: by 10.151.156.6 with SMTP id i6mr24362823ybo.150.1231215907903; Mon, 05 Jan 2009 20:25:07 -0800 (PST) Received: by 10.151.68.13 with HTTP; Mon, 5 Jan 2009 20:25:07 -0800 (PST) Message-ID: <47713ee10901052025y26d342f6me0aea946a49b6f0a@mail.gmail.com> Date: Tue, 6 Jan 2009 12:25:07 +0800 From: "Lin Jui-Nan Eric" To: "Robert Watson" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47713ee10812301206j12b35264o715976c154080a1b@mail.gmail.com> <47713ee10901012147k1f25c31bn512dd29b2b294ad5@mail.gmail.com> <47713ee10901012249w65c659bbp3366e4d8ef25c59d@mail.gmail.com> Cc: freebsd-net@freebsd.org, stable@freebsd.org Subject: Re: TCP packet out-of-order 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: Tue, 06 Jan 2009 04:25:09 -0000 Hi Robert, I thought that the system auto-tune improperly in this case. On Mon, Jan 5, 2009 at 9:13 PM, Robert Watson wrote: > On Fri, 2 Jan 2009, Lin Jui-Nan Eric wrote: > >> After running "netstat -s -p tcp", we found that lots of packets are >> discarded due to memory problems. We googled for it, and found that sysctl >> oid "net.inet.tcp.reass.maxsegments" became 0, therefore packets never >> reassembled. >> >> Then we checked our /boot/loader.conf and /etc/sysctl.conf, and found that >> setting kern.ipc.nmbclusters="0" makes net.inet.tcp.reass.maxsegments=0. >> After setting net.inet.tcp.reass.maxsegments="1600" in /boot/loader.conf, >> the network works perfectly now. > > Was it set to 0 through a configuration error, or did the system auto-tune > improperly? > > Robert N M Watson > Computer Laboratory > University of Cambridge > >> >> Thank you all for the help! >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> > From owner-freebsd-net@FreeBSD.ORG Tue Jan 6 07:21:50 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26D301065670 for ; Tue, 6 Jan 2009 07:21:50 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from arcturus.maxiscale.com (arcturus.maxiscale.com [76.231.178.136]) by mx1.freebsd.org (Postfix) with ESMTP id 01DF18FC18 for ; Tue, 6 Jan 2009 07:21:49 +0000 (UTC) (envelope-from psteele@maxiscale.com) X-ASG-Debug-ID: 1231225420-5c3d00020000-QdxwpM X-Barracuda-URL: http://10.100.1.25:8000/cgi-bin/mark.cgi Received: from polaris.maxiscale.com (localhost [127.0.0.1]) by arcturus.maxiscale.com (Spam Firewall) with ESMTP id B0F9335BB0 for ; Mon, 5 Jan 2009 23:03:40 -0800 (PST) Received: from polaris.maxiscale.com (polaris.maxiscale.com [10.100.1.24]) by arcturus.maxiscale.com with ESMTP id FuaflQ2zUim3acA4 for ; Mon, 05 Jan 2009 23:03:40 -0800 (PST) X-ASG-Whitelist: Client X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 X-ASG-Orig-Subj: Having problems with limited broadcast Date: Mon, 5 Jan 2009 23:03:36 -0800 Message-ID: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DE9@polaris.maxiscale.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Having problems with limited broadcast Thread-Index: AclvzOTbUmAfkqTlT6uY4+WyfRVk+A== From: "Peter Steele" To: X-Barracuda-Connect: polaris.maxiscale.com[10.100.1.24] X-Barracuda-Start-Time: 1231225422 X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at maxiscale.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Jan 2009 07:21:50 -0000 We have a Python app that implements a DHCP-like protocol using limited broadcast using address 255.255.255.255. Our code works fine on Linux and FreeBSD but we cannot seem to get broadcast to work on FreeBSD. We've tried both Python and C under FreeBSD 7.0. =20 I've found a lengthy discussion of this problem here: =20 http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/99558 =20 It appears some work has been done to correct this problem but if I understand the discussion correctly it still is not resolved, at least as of the timeframe of this thread.=20 =20 In our case, we have systems with no IP identity of any kind--no IP address and no gateway, and they are connected only by switches. There is no router in the network. They receive IP addresses through a special service that we've written that runs on one of the systems, in response to address request queries sent out by the systems. All communication is done through limited broadcast. As I said, this works fine one our Linux and Windows boxes but not FreeBSD. =20 Based on the discussion in the link above, it doesn't seem like the problem was entirely resolved by the patches mentioned in this thread. Has anything been done since this discussion took place. Surely there must be a way to get limited broadcast to work under FreeBSD. =20 From owner-freebsd-net@FreeBSD.ORG Tue Jan 6 08:16:02 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 638F7106566B; Tue, 6 Jan 2009 08:16:02 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 3D46F8FC17; Tue, 6 Jan 2009 08:16:02 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id CEE6846B0C; Tue, 6 Jan 2009 03:16:01 -0500 (EST) Date: Tue, 6 Jan 2009 08:16:01 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Lin Jui-Nan Eric In-Reply-To: <47713ee10901052025y26d342f6me0aea946a49b6f0a@mail.gmail.com> Message-ID: References: <47713ee10812301206j12b35264o715976c154080a1b@mail.gmail.com> <47713ee10901012147k1f25c31bn512dd29b2b294ad5@mail.gmail.com> <47713ee10901012249w65c659bbp3366e4d8ef25c59d@mail.gmail.com> <47713ee10901052025y26d342f6me0aea946a49b6f0a@mail.gmail.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, stable@freebsd.org Subject: Re: TCP packet out-of-order 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: Tue, 06 Jan 2009 08:16:02 -0000 On Tue, 6 Jan 2009, Lin Jui-Nan Eric wrote: > I thought that the system auto-tune improperly in this case. Hmm. Do you have a custom setting for kern.ipc.nmbclusters in loader.conf or sysctl.conf? What does kern.ipc.nmbclusters configure itself to on your system? Also, could you send me the output of uname -a on the system? Thanks, Robert N M Watson Computer Laboratory University of Cambridge > On Mon, Jan 5, 2009 at 9:13 PM, Robert Watson wrote: >> On Fri, 2 Jan 2009, Lin Jui-Nan Eric wrote: >> >>> After running "netstat -s -p tcp", we found that lots of packets are >>> discarded due to memory problems. We googled for it, and found that sysctl >>> oid "net.inet.tcp.reass.maxsegments" became 0, therefore packets never >>> reassembled. >>> >>> Then we checked our /boot/loader.conf and /etc/sysctl.conf, and found that >>> setting kern.ipc.nmbclusters="0" makes net.inet.tcp.reass.maxsegments=0. >>> After setting net.inet.tcp.reass.maxsegments="1600" in /boot/loader.conf, >>> the network works perfectly now. >> >> Was it set to 0 through a configuration error, or did the system auto-tune >> improperly? >> >> Robert N M Watson >> Computer Laboratory >> University of Cambridge >> >>> >>> Thank you all for the help! >>> _______________________________________________ >>> freebsd-stable@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >>> >> > From owner-freebsd-net@FreeBSD.ORG Tue Jan 6 15:12:17 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C3A31065678; Tue, 6 Jan 2009 15:12:17 +0000 (UTC) (envelope-from ericlin@tamama.org) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by mx1.freebsd.org (Postfix) with ESMTP id 3AA888FC1A; Tue, 6 Jan 2009 15:12:17 +0000 (UTC) (envelope-from ericlin@tamama.org) Received: by yx-out-2324.google.com with SMTP id 8so3400179yxb.13 for ; Tue, 06 Jan 2009 07:12:16 -0800 (PST) Received: by 10.151.111.1 with SMTP id o1mr970543ybm.88.1231254736021; Tue, 06 Jan 2009 07:12:16 -0800 (PST) Received: by 10.151.68.13 with HTTP; Tue, 6 Jan 2009 07:12:15 -0800 (PST) Message-ID: <47713ee10901060712g7b4a204fq73cabb99c7070929@mail.gmail.com> Date: Tue, 6 Jan 2009 23:12:15 +0800 From: "Lin Jui-Nan Eric" To: "Robert Watson" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47713ee10812301206j12b35264o715976c154080a1b@mail.gmail.com> <47713ee10901012147k1f25c31bn512dd29b2b294ad5@mail.gmail.com> <47713ee10901012249w65c659bbp3366e4d8ef25c59d@mail.gmail.com> <47713ee10901052025y26d342f6me0aea946a49b6f0a@mail.gmail.com> Cc: freebsd-net@freebsd.org, stable@freebsd.org Subject: Re: TCP packet out-of-order 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: Tue, 06 Jan 2009 15:12:18 -0000 Oops, we surely have kern.ipc.nmbclusters="0" in loader.conf, but I think that should not modify net.inet.tcp.reass.maxsegments to "0" since we wish unlimited nmbclusters but not zero TCP reassembly segments. On Tue, Jan 6, 2009 at 4:16 PM, Robert Watson wrote: > > On Tue, 6 Jan 2009, Lin Jui-Nan Eric wrote: > >> I thought that the system auto-tune improperly in this case. > > Hmm. Do you have a custom setting for kern.ipc.nmbclusters in loader.conf > or sysctl.conf? What does kern.ipc.nmbclusters configure itself to on your > system? Also, could you send me the output of uname -a on the system? > > Thanks, > > Robert N M Watson > Computer Laboratory > University of Cambridge > >> On Mon, Jan 5, 2009 at 9:13 PM, Robert Watson wrote: >>> >>> On Fri, 2 Jan 2009, Lin Jui-Nan Eric wrote: >>> >>>> After running "netstat -s -p tcp", we found that lots of packets are >>>> discarded due to memory problems. We googled for it, and found that >>>> sysctl >>>> oid "net.inet.tcp.reass.maxsegments" became 0, therefore packets never >>>> reassembled. >>>> >>>> Then we checked our /boot/loader.conf and /etc/sysctl.conf, and found >>>> that >>>> setting kern.ipc.nmbclusters="0" makes net.inet.tcp.reass.maxsegments=0. >>>> After setting net.inet.tcp.reass.maxsegments="1600" in >>>> /boot/loader.conf, >>>> the network works perfectly now. >>> >>> Was it set to 0 through a configuration error, or did the system >>> auto-tune >>> improperly? >>> >>> Robert N M Watson >>> Computer Laboratory >>> University of Cambridge >>> >>>> >>>> Thank you all for the help! >>>> _______________________________________________ >>>> freebsd-stable@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>>> To unsubscribe, send any mail to >>>> "freebsd-stable-unsubscribe@freebsd.org" >>>> >>> >> > From owner-freebsd-net@FreeBSD.ORG Tue Jan 6 16:41:05 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A93751065670 for ; Tue, 6 Jan 2009 16:41:05 +0000 (UTC) (envelope-from leeygang@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.189]) by mx1.freebsd.org (Postfix) with ESMTP id 396278FC16 for ; Tue, 6 Jan 2009 16:41:05 +0000 (UTC) (envelope-from leeygang@gmail.com) Received: by fk-out-0910.google.com with SMTP id k31so5358664fkk.11 for ; Tue, 06 Jan 2009 08:41:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=5r9SSeoWvCYmcSry9vupSiXd4hYZvjk0ivDr6+WGeWQ=; b=JsKAhIZrsNP83YEkM0TMyjOlGib12SKzjwVO+AkG5c/qX5As6Q0c2AUaAoBqMCkCje 6TT9NRpP3J6+mIGDKFqAB48IUGiQVxM0BgYJJKSgicZKKLQJpoecWAUxSIe9U3XgeL1H LonaUCrRrN35SVzNuB1/IOmfqmDCznP7pJ9F8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=wePpPOeAjCB2oIS+hiBJGnHVrZDTAE/+U9K/9T3kmmfgRwD67E634cLzQWqT2vDnW0 Nflkt9ZLkdWYCaVPXNZ4NTo9WEq3Fz2vwwUBiKAF+IGYCL2Fc6vlSwiWdJKGB5i71MSO lvBXDyRTA91tch59ZoqIFoXIXtlEAYvy2zWXw= Received: by 10.103.217.5 with SMTP id u5mr3866019muq.118.1231258366356; Tue, 06 Jan 2009 08:12:46 -0800 (PST) Received: by 10.103.95.8 with HTTP; Tue, 6 Jan 2009 08:12:46 -0800 (PST) Message-ID: <6742fb710901060812u5f1b749cubec97c8adbbe3384@mail.gmail.com> Date: Tue, 6 Jan 2009 16:12:46 +0000 From: "Li yonggang" To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: the BACKWARD COMPTIBLITY code for the input for netstat leads to a crash X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Jan 2009 16:41:06 -0000 Hi, I use FreeBSD 7.0-Release and find if a mistake input for -m can make netstat crash. such as: netstat -m xxx After simple investigation, I found it is caused by the code in main.c :456 #define BACKWARD_COMPATIBILITY #ifdef BACKWARD_COMPATIBILITY if (*argv) { if (isdigit(**argv)) { interval = atoi(*argv); if (interval <= 0) usage(); ++argv; iflag = 1; } if (*argv) { nlistf = *argv; if (*++argv) memf = *argv; } } #endif if the input is incorrect, this piece of code will set nlistf as a incorrect string, this will make the live var set incorrectly. so I think there are 2 ways to resolve: 1. add input check code in case -m of switch. 2. or delete backward comptiblity code. Is my understanding correct? Thanks, Yong-gang Li. From owner-freebsd-net@FreeBSD.ORG Tue Jan 6 16:46:19 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A49A106566B for ; Tue, 6 Jan 2009 16:46:19 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from arcturus.maxiscale.com (arcturus.maxiscale.com [76.231.178.136]) by mx1.freebsd.org (Postfix) with ESMTP id D8E068FC12 for ; Tue, 6 Jan 2009 16:46:18 +0000 (UTC) (envelope-from psteele@maxiscale.com) X-ASG-Debug-ID: 1231260327-374800000000-QdxwpM X-Barracuda-URL: http://10.100.1.25:8000/cgi-bin/mark.cgi Received: from polaris.maxiscale.com (localhost [127.0.0.1]) by arcturus.maxiscale.com (Spam Firewall) with ESMTP id B1CC335C6C for ; Tue, 6 Jan 2009 08:45:28 -0800 (PST) Received: from polaris.maxiscale.com (polaris.maxiscale.com [10.100.1.24]) by arcturus.maxiscale.com with ESMTP id Uad68AAzmm7gfsvs for ; Tue, 06 Jan 2009 08:45:27 -0800 (PST) X-ASG-Whitelist: Client X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 X-ASG-Orig-Subj: Having problems with limited broadcast Date: Tue, 6 Jan 2009 08:45:10 -0800 Message-ID: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Having problems with limited broadcast Thread-Index: AclvzOTbUmAfkqTlT6uY4+WyfRVk+A== From: "Peter Steele" To: X-Barracuda-Connect: polaris.maxiscale.com[10.100.1.24] X-Barracuda-Start-Time: 1231260331 X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at maxiscale.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 06 Jan 2009 16:46:19 -0000 We have a Python app that implements a DHCP-like protocol using limited broadcast using address 255.255.255.255. Our code works fine on Linux and FreeBSD but we cannot seem to get broadcast to work on FreeBSD. We've tried both Python and C under FreeBSD 7.0. =20 I've found a lengthy discussion of this problem here: =20 http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/99558 =20 It appears some work has been done to correct this problem but if I understand the discussion correctly it still is not resolved, at least as of the timeframe of this thread.=20 =20 In our case, we have systems with no IP identity of any kind--no IP address and no gateway, and they are connected only by switches. There is no router in the network. They receive IP addresses through a special service that we've written that runs on one of the systems, in response to address request queries sent out by the systems. All communication is done through limited broadcast. As I said, this works fine one our Linux and Windows boxes but not FreeBSD. =20 Based on the discussion in the link above, it doesn't seem like the problem was entirely resolved by the patches mentioned in this thread. Has anything been done since this discussion took place. Surely there must be a way to get limited broadcast to work under FreeBSD. =20 From owner-freebsd-net@FreeBSD.ORG Wed Jan 7 04:15:05 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23317106564A for ; Wed, 7 Jan 2009 04:15:05 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [220.233.188.227]) by mx1.freebsd.org (Postfix) with ESMTP id 965938FC17 for ; Wed, 7 Jan 2009 04:15:04 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id n074F2gW053506; Wed, 7 Jan 2009 15:15:02 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Wed, 7 Jan 2009 15:15:02 +1100 (EST) From: Ian Smith To: perryh@pluto.rain.com In-Reply-To: <49618962.WvA2bFthdzGdSO/b%perryh@pluto.rain.com> Message-ID: <20090107150633.S28770@sola.nimnet.asn.au> References: <495edc8b.yfwTDGtb9G/8NMur%perryh@pluto.rain.com> <20090103154232.P28770@sola.nimnet.asn.au> <49618962.WvA2bFthdzGdSO/b%perryh@pluto.rain.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-net@freebsd.org Subject: Re: (partly) SOLVED: tun0 not responding to ping X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Jan 2009 04:15:05 -0000 On Sun, 4 Jan 2009, perryh@pluto.rain.com wrote: > Ian Smith wrote: > > On Fri, 2 Jan 2009, perryh@pluto.rain.com wrote: > > > > > Why would a local interface, reported as up in ifconfig, not respond > > > to a ping of its own IP address? The tun0 reported below doesn't, > ... > > > $ ifconfig -a > ... > > > tun0: flags=8051 mtu 1412 > > > inet6 fe80::2b0:d0ff:fe28:ad4f%tun0 prefixlen 64 scopeid 0x4 > > > inet ZZZ.ZZZ.233.42 --> ZZZ.ZZZ.233.42 netmask 0xffffffff > > > Opened by PID 24635 > > > > I don't know if this is relevant or not, but I've never seen a point to > > point interface use the same IP address on both ends of its link before. .. at least, not when using ppp(8) That's what I get for ASSuming :) > It turns out to be normal -- or at least tolerable -- for a tun(4) > interface used by vpnc to have the same IP address at both ends. > It started working when I added > > NAT Traversal Mode cisco-udp > > to vpnc.conf. (Presumably not all configurations of the Cisco 3000 > will need that, else it would be the default, but it seems to be > correct for the one involved here.) > > I never did figure out why that kept the interface from responding > to a ping of its own address :( Glad to hear it's working anyway, on getting back from a few days away. cheers, Ian From owner-freebsd-net@FreeBSD.ORG Wed Jan 7 08:50:03 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 824351065670 for ; Wed, 7 Jan 2009 08:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6F53D8FC1B for ; Wed, 7 Jan 2009 08:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n078o2cG041103 for ; Wed, 7 Jan 2009 08:50:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n078o2Gh041102; Wed, 7 Jan 2009 08:50:02 GMT (envelope-from gnats) Date: Wed, 7 Jan 2009 08:50:02 GMT Message-Id: <200901070850.n078o2Gh041102@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: =?iso-8859-1?Q?=22Stefan_Kr=FCger=22?= Cc: Subject: Re: kern/106438: [ipf] ipfilter: keep state does not seem to allow replies in on spar64 (and maybe others) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?iso-8859-1?Q?=22Stefan_Kr=FCger=22?= List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jan 2009 08:50:03 -0000 The following reply was made to PR kern/106438; it has been noted by GNATS. From: =?iso-8859-1?Q?=22Stefan_Kr=FCger=22?= To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/106438: [ipf] ipfilter: keep state does not seem to allow replies in on spar64 (and maybe others) Date: Wed, 07 Jan 2009 09:16:57 +0100 I can confirm that ipf's keep state still doesn't work on FreeBSD 7.1-RELEASE :( Machine used for testing was a Sun Fire v120 (i.e. sparc64), NIC was Sun Eri (= gem driver) -- Sensationsangebot verlängert: GMX FreeDSL - Telefonanschluss + DSL für nur 16,37 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K1308T4569a From owner-freebsd-net@FreeBSD.ORG Wed Jan 7 09:12:43 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 730DD106566B for ; Wed, 7 Jan 2009 09:12:43 +0000 (UTC) (envelope-from kayvey@gmail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id 8A0168FC21 for ; Wed, 7 Jan 2009 09:12:42 +0000 (UTC) (envelope-from kayvey@gmail.com) Received: by ewy14 with SMTP id 14so9933288ewy.19 for ; Wed, 07 Jan 2009 01:12:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=sIFVZKcIjor2zbrIgI2NMJfNT2eWVfGyNz6RcKbK2pI=; b=qukeho7e6MRM3BYv4xY+ZVPtIHvT3aECseCzEbTu0nMr5MA4Mf1Wc4UI17S68Hyk59 irO8oWrmtGJ1QHmRzpk0LimfjCzkHtPikrh+pnkn6ArA1hQXhh7pRapyanh2Wa/ph9yN 52GvhAB9ckDOkhSZFx5n1XmTW6Tzcsq2tDAwY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=bxn90GSGCOQdy30ZD2BGYRLyOw5l7Fuz2YMOXr5QeqqnjtILepMK3lOs1n1QCLUeuV YJQWl/XJMIZUcMVjxpZcyjvvEuj2slHJhm+Tg3rwtfCSQWsP21oPOFxr0e3/GfzkpoYs TSBHnw4WnEYMSgcqViH5Rg770kKAtZhX9UU/M= Received: by 10.210.42.13 with SMTP id p13mr3443643ebp.183.1231317597556; Wed, 07 Jan 2009 00:39:57 -0800 (PST) Received: by 10.210.38.6 with HTTP; Wed, 7 Jan 2009 00:39:57 -0800 (PST) Message-ID: <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> Date: Wed, 7 Jan 2009 00:39:57 -0800 From: "Kayven Riese" To: "Peter Steele" In-Reply-To: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> MIME-Version: 1.0 References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Jan 2009 09:12:43 -0000 On Tue, Jan 6, 2009 at 8:45 AM, Peter Steele wrote: > We have a Python app that implements a DHCP-like protocol using limited > broadcast using address 255.255.255.255. Our code works fine on Linux > and FreeBSD but we cannot seem to get broadcast to work on FreeBSD. > We've tried both Python and C under FreeBSD 7.0. > > > > I've found a lengthy discussion of this problem here: > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/99558 > More reaently, ------------------------------ >Message: 22 >Date: Tue, 6 Jan 2009 13:29:04 -0800 >From: "Peter Steele" >Subject: RE: Do UDP broadcasts work in FreeBSD? >To: >Message-ID: > <2ACA3DE8F9758A48B8BE2C7A847F91F2479E3F@polaris.maxiscale.com> >Content-Type: text/plain; charset="us-ascii" > >> What you're trying to do with sending to the all-ones broadcast >> address is known as sending a "link-local" packet. On some systems, >> sending a UDP packet to 255.255.255.255 will actually cause a packet >> with that destination to be generated from all network interfaces >> which are "UP". That seems to be the behavior you are expecting. > >Yes it is. This is the behavior I've seen on every system I've used for >20+ years, except for FreeBSD. > I've only been a UNIX luser since 1985 when I thought I learned "EVAX" at the University of Wisconsin-Milwaukee. I have done other things than sysadmin since then, so if anyone has a better source for an EVAX operating system (if I am not confusing it with something else) I would appreciate it. >> On FreeBSD, IIRC, the behavior you get is that it will send to the >> local network broadcast address for each interface [1] using the >> network broadcast address (ie, if an interface is configured for >> 10.1.1.1 with /16 netmask, the packet will have destination >> 10.1.255.255). If an interface is UP but not configured with an IP >> +netmask, I don't believe a packet will be sent. (In fact, it might >> depend upon whether the BROADCAST flag is enabled, which gets set when > >> an inet-enabled interface is setup with a netmask...) At the risk of digressing and in hopes that there is truly "no stupid question that is at least on topic", I want to say that I was some amount through the book "TCP/IP Network Administration" by Hunt published by O'Reilly, when I picked up "Writing a UNIX Device Driver" by Egan and Teixeira (I note its regrettable emphasis on System V, though it mentiones "Berkeley Systems") because I was really hoping to get up to speed to contribute vis a vis Wireless USB adapters by Belkin that do not seem to have a driver in FreeBSD (is this a bug?). If anybody has any further suggestions for further reading, it would be appreciated. I already had the TCP/IP Hunt book but hadn't picked it up when I picked up a book by the name of "TCP/IP Illustrated Volume 2." Getting a bit into that, and cogniscient of the fact that it was "Volume 2" I decided to put it down and pick up Hunt, feeling like a TCP/IP newbie (at least a developer level newbie fo'sho'). Anyway.. back to the topic. I have also been exposed to TCP/IP recently in UC-Berkeley's undergraduate operating systems course (CS 162) where they discussed the fact that not all IP addresses are created equal. I missed some points on a test question claiming that "There are 2^32 IP adddresses" or some such, since e.g. 0.0.0.0 and 255.255.255.255 and 127.0.0.1, right? are not really legal addresses. I don't remember off the top of my head the exact IP numbers involved with this, but I vaguely recall that in addition to having IPs with "special meaning" i.e. do not exactly "point" to any "node" on the "internet," there ARE a set of IPs that are specifically designed for use in LANs (is that what we are talking about with a "set of computers" that have "no IP," right?) > >In our case our systems have no IP identity of any kind, and we don't >want to have to rely on whether or not our customers have a DHCP server >available. So we've come up with our own "light" DHCP. It works fine for >Linux and Windows. Not FreeBSD though. > >> Arguably, this is a bug in FreeBSD > >I don't think there is any doubt about that. And from what I understand >it even used to work under FreeBSD a few years ago. Okay, I jumped the gun. Is this a bug to be absolutely ignorant of the existance of an IP system that .. am I wrong in saying this?.. MANDATES that every computer has an IP even if it is just in a LAN, and acutally tries to claim it is not a part of the "internet," and, indeed, the IP system provides for this by having a set of IPs (was it 10.0.0.0/8 and 192.168.0.0/16 ?..I am professing absolute ignorance here, but hoping that I am not mistaken). We ARE talking about "just a LAN" here, right? Also, these computers are "not on the internet?" They have absolutely no connectivity? (Unlikely). I apologize for being incredibly stupid, and not having the time to "thoroughly" (umm.. well..I .. yeah. I feel that maybe the amount of background reading to really get up to speed before this thread wistfully drifts into the internet archives might be prohibitive).. research the background here, but feel at least if I am OT on freebsd-net (I would have replied to -questions, but I am set up for this "daily digest" and fear that totally destroys these neato email threads that have my name being a horses patoot all over the internet). > >> but you can work around it by >> using the BPF interface to send the traffic directly rather than using > >> the network stack via socket()+send()/write(). I believe the ISC DHCP > >> server software provides examples of how to do this, as dhclient is >> commonly used to send DHCP requests to the all-ones broadcast addr, >> without needing an interface being configured with an IP.... > >I've already looked at the ISC DHCP source code. They use raw sockets to >send their broadcasts, which seems to us to be a convoluted way of >sending a simple broadcast. I've seen examples of DHCP client/server >code written in Java using standard UDP. Unfortunately, our own system >is already largely implemented in Java/Python, so we'll need to provide >a JNI interface to support raw sockets. Alternatively we may patch the >kernel to fix the bug at its source. > After having looked closely at this question, and feeling "the guantlet has been tossed," I tossed an turned and suddenly knew I had to rise and confront this assertion on the matter of "bug versus feature." In my voluminous ignorance, I offer a simple question. I have an intuition that somebody really smart _just might_ jump in and having something really interesting to say on this matter if (despite the fact??) I do. It defintely sounds like this "feature" (I am hearby casting my pathetic carcass into the line of fire in my assertion that his is not a "bug," but a "feature.") is giving a certain Peter Steele more irritations in the form of required configuration issues than he would otherwise like. My very simple (but at the same time perhaps profoundly complex) question is, "What are the security implications of pretending there is no such thing as IP addresses that are designated for LANs that are isolated from TCP/IP of the WAN as servers, while perhaps acting as clients?" In case I am actually clueless, I also offer a potentially synonymic question, "What is the 'infinite wisdom' (note to any--feel free to replace with 'absolute folly' if you are so inclined) behind the design of FreeBSD in contrast to Penguinware and Uncle Bill's Windoze that is leading to the "feature"that is making a certain Peter Steele's life so difficult? > > It appears some work has been done to correct this problem but if I > understand the discussion correctly it still is not resolved, at least > as of the timeframe of this thread. > > > > In our case, we have systems with no IP identity of any kind--no IP > address and no gateway, and they are connected only by switches. There > is no router in the network. They receive IP addresses through a special > service that we've written that runs on one of the systems, in response > to address request queries sent out by the systems. All communication is > done through limited broadcast. As I said, this works fine one our Linux > and Windows boxes but not FreeBSD. > > > > Based on the discussion in the link above, it doesn't seem like the > problem was entirely resolved by the patches mentioned in this thread. > Has anything been done since this discussion took place. Surely there > must be a way to get limited broadcast to work under FreeBSD. > > > > _______________________________________________ > 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" > -- *----------------------------------------------------------* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *----------------------------------------------------------* From owner-freebsd-net@FreeBSD.ORG Wed Jan 7 09:13:51 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B0241065674 for ; Wed, 7 Jan 2009 09:13:51 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.freebsd.org (Postfix) with ESMTP id A8E758FC08 for ; Wed, 7 Jan 2009 09:13:50 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: by ug-out-1314.google.com with SMTP id 30so1387129ugs.39 for ; Wed, 07 Jan 2009 01:13:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:subject:date :message-id:mime-version:content-type:x-mailer:thread-index :x-mimeole; bh=i7U63l7EsUJ044nd6UG0AIbBmnXttRuESwtnoeQWy0I=; b=TxF8LagY/gkI5lzrb2AoQ/dgQPMidzRk+NMo4VYrFqOcKeKjgBmuLl6ZNxsNRpQoGo M1sFmuB1A0WtiQogNI5OofrfQBSTmzMwPNz2iWRjVEqUape0jIB4tldOOFfLH0YXATRH UFXJAr3eaC4Wj4iTZWpat6SyZlTooBNDw8/6M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:x-mimeole; b=YWOqBjFTpMjIyWrf5q63jNN7vjuZK8RgeF9rucITnZN4r9gCYnb/GItpssBwQ6IW58 NPUn2MjZBpGwhCyuZyLIrQyo9W1DoIZyyK7UVdzp6jUN3y2oKX25Tg0KanfsBDw2KZOR G0JodeJ8Kr0KpsrUFGtJei4YA3e9wQN3BCVYc= Received: by 10.67.115.14 with SMTP id s14mr13762333ugm.57.1231319629614; Wed, 07 Jan 2009 01:13:49 -0800 (PST) Received: from mtllpt03 (DSL212-235-20-133.bb.netvision.net.il [212.235.20.133]) by mx.google.com with ESMTPS id 20sm27224007uga.49.2009.01.07.01.13.46 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 07 Jan 2009 01:13:48 -0800 (PST) From: "Yony Yossef" To: Date: Wed, 7 Jan 2009 11:13:44 +0200 Message-ID: <000001c970a8$3fa45240$220f000a@mtl.com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 Thread-Index: Aclwp9zO1uF1JxH1QhGuS7LAW0yevQ== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Eitan Shefi Subject: VLAN interface management - unloading carrying driver hangs the machine X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Jan 2009 09:13:51 -0000 Hi All, I'm having a problem on FreeBSD 6.3 and 7.0 with VLAN management. After loading my 10GigE driver I'm creating a vlan interface: /sbin/ifconfig vlan3653 create /sbin/ifconfig vlan3653 vlan 3653 vlandev mynic0 Then I'm unloading the driver and everything is fine, the driver interface remains with a NULL parent. Problem is when I assign an IP to the vlan interface. In that case, unloading the driver results in hanging the host. Does it sound familiar to anybody? Thanks, Yony From owner-freebsd-net@FreeBSD.ORG Wed Jan 7 14:13:46 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 96D1E106566B for ; Wed, 7 Jan 2009 14:13:46 +0000 (UTC) (envelope-from nrml@att.net) Received: from web83803.mail.sp1.yahoo.com (web83803.mail.sp1.yahoo.com [69.147.85.69]) by mx1.freebsd.org (Postfix) with SMTP id 7A2808FC0C for ; Wed, 7 Jan 2009 14:13:46 +0000 (UTC) (envelope-from nrml@att.net) Received: (qmail 31385 invoked by uid 60001); 7 Jan 2009 14:13:46 -0000 Received: from [69.43.143.172] by web83803.mail.sp1.yahoo.com via HTTP; Wed, 07 Jan 2009 06:13:45 PST X-Mailer: YahooMailWebService/0.7.218.2 Date: Wed, 7 Jan 2009 06:13:45 -0800 (PST) From: Gabe To: "Bjoern A. Zeeb" In-Reply-To: <881287.90275.qm@web83809.mail.sp1.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <227893.30747.qm@web83803.mail.sp1.yahoo.com> Cc: freebsd-net@freebsd.org Subject: Re: +ipsec_common_input: no key association found for SA X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: nrml@att.net List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jan 2009 14:13:47 -0000 > From: Gabe > Subject: Re: +ipsec_common_input: no key association found for SA > To: "Bjoern A. Zeeb" > Cc: freebsd-net@freebsd.org > Date: Sunday, January 4, 2009, 4:11 AM > > From: Bjoern A. Zeeb > > > Subject: Re: +ipsec_common_input: no key association > found for SA > > To: "Gabe" > > Cc: freebsd-net@freebsd.org > > Date: Sunday, January 4, 2009, 3:24 AM > > On Sun, 4 Jan 2009, Gabe wrote: > > > > Hi, > > > > >>> Ok, can you try running the following > script > > and see > > >> if the > > >>> output > > >>> times match your racoon restarts or the > log > > entries? > > > > You hadn't answered that question to correlate the > > tcpdump with racoon > > restarts and kernel log entries. > > > > If you do that, you may want to run the script for two > > hours or four > > to actually see more changes than just the initial > one. > > > > Check the syslog timestamps in the logfile where your > > kernel messages > > go to (might be /var/log/messages) for the > > ipsec_common_input lines. > > Perhaps grep upfront before startung the script to be > sure > > that they > > are there. > > > > I understand. I'm having to rebuild "box" > (unrelated) so this will have to wait, I will definitely do > it as mentioned above. > > > > I'm still unable to find the cause for this. > Does > > anyone know what the above output is referring to? > > > > I think David DeSimone had last explained it to you: > > > http://lists.freebsd.org/pipermail/freebsd-net/2008-December/020611.html > > > > Maybe it would be time to read the RFC now; I'll > try it > > in my own > > words again and shorter. > > > > Your IPsec Policy makes your racoons negotiate a > Security > > Assosiaction > > for some parameters (keys, lieftime, ..). There will > be one > > for each > > direction. One thing negotiated is the security policy > > index, the > > number we are tracing. This 'number' is put > into > > each packet one of the > > boxes send encrypted to the other for the given > direction. > > > > What your kernel tells you is that the number in the > packet > > received > > does not make sense to the box receiving it. Let's > say > > the SPI received in > > the packet from the other box is unknown on the > receiver > > side. That's > > why the kernel complains. > > Without the proper SPI the kernel will not be able to > find > > the proper > > other parameters for this packet, and thus will not be > able > > to decrypt > > the packet. > > > > > > What we are trying to find out at the moment is to > identify > > where > > exactly the wrong SPI is coming from. This could be: > > - whatever the boxes negotiated gets out of sync > > - a patch like the NAT-T patch could corrupt the > packet > > - a software bug in where the kernel or racoon > > - ... > > > > To narrow this down from "everywhere" to > > "here" it is important to see > > where the values match, where not and when they do not > > match - thus > > correlating information from the time racoon gets > > restarted, the > > kernel prints the log message and what tcpdump is > showing. > > It's > > important to get all this information for the same > > problematic moment, > > timestamped. If one is missing it's like a 1000 > pieces > > puzzle with > > only 600 pieces included. > > > > One more question that hadn't been asked so far - > what > > architectures > > (i386, amd64, sparc, arm, ..) are box and box2 and > which > > version of > > freebsd are they running; I assume they are both on > > freebsd? > > > > They're i386. > > This is uname -a on "box": > > FreeBSD box.domain.tld 7.1-PRERELEASE FreeBSD > 7.1-PRERELEASE #0: Fri Dec 12 07:11:30 PST 2008 > root@box.domain.tld:/usr/obj/usr/src/sys/KERNEL i386 > > This is uname -a on "box2": > > FreeBSD box2.domain.tld 7.1-PRERELEASE FreeBSD > 7.1-PRERELEASE #5: Fri Dec 26 01:48:31 PST 2008 > root@box2.domain.tld:/usr/obj/usr/src/sys/KERNEL i386 > > One thing I found to be interesting is that > "box2" no longer spews out the ipsec_common_input > message after I corrected the 'spdadd' lines. So > perhaps this is related to the different kernel sources > version. > > Either way I'll report back once I'm finished > rebuilding "box" Well, I can't continue to try and figure this out. The boxes where this is occurring are live production boxes and well I need to figure out a better solution that's a little more intuitive. So it seems that just like many other freebsd users out there with IPSec and the NAT-T patch this will remain unanswered. Thanks Bjoern and everyone who answered. Cheers /gabe From owner-freebsd-net@FreeBSD.ORG Wed Jan 7 14:38:27 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3324A1065670 for ; Wed, 7 Jan 2009 14:38:27 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from arcturus.maxiscale.com (arcturus.maxiscale.com [76.231.178.136]) by mx1.freebsd.org (Postfix) with ESMTP id 09C218FC16 for ; Wed, 7 Jan 2009 14:38:24 +0000 (UTC) (envelope-from psteele@maxiscale.com) X-ASG-Debug-ID: 1231339087-49c500000000-QdxwpM X-Barracuda-URL: http://10.100.1.25:8000/cgi-bin/mark.cgi Received: from polaris.maxiscale.com (localhost [127.0.0.1]) by arcturus.maxiscale.com (Spam Firewall) with ESMTP id 39C47360AB for ; Wed, 7 Jan 2009 06:38:07 -0800 (PST) Received: from polaris.maxiscale.com (polaris.maxiscale.com [10.100.1.24]) by arcturus.maxiscale.com with ESMTP id 2JjDLHQpdql6L565 for ; Wed, 07 Jan 2009 06:38:07 -0800 (PST) X-ASG-Whitelist: Client X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 X-ASG-Orig-Subj: RE: Having problems with limited broadcast Date: Wed, 7 Jan 2009 06:38:05 -0800 Message-ID: <2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com> In-Reply-To: <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Having problems with limited broadcast Thread-Index: Aclwo7FvMTQm45SXQwiffk2PQhMrnQALokpA References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> From: "Peter Steele" To: X-Barracuda-Connect: polaris.maxiscale.com[10.100.1.24] X-Barracuda-Start-Time: 1231339093 X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at maxiscale.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: RE: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Jan 2009 14:38:27 -0000 >We ARE talking about "just a LAN" here, right? Also, these computers >are "not on the internet?" They have absolutely no connectivity? >(Unlikely). When our boxes are initially deployed, they have no IP addresses assigned to them. Their ifconfig entry looks like this: ifconfig_lagg0=3D"laggproto failover laggport nfe0 laggport nfe1" With this config, no IP is assigned to the lagg0 device, so the only way to access the boxes is via a serial console. From there we give one system a static IP, and then proceed to configure our "light DHCP" service on this box via a web app. After this is done, the remaining systems start communicating with this box via a broadcast protocol to obtain their IPs. These will be assigned statically to these boxes, and from there they can get on with launching their applications (JBOSS, etc). And I'll leave it at that. I am quite ready to give this one to Kayven Riese. He clearly knows a lot more about the subject than I do, and I apologize for the testiness of my posting (deadline pressures). We are proceeding with using raw sockets to implement our broadcast based light DHCP service. =20 From owner-freebsd-net@FreeBSD.ORG Wed Jan 7 15:04:45 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3CA001065670 for ; Wed, 7 Jan 2009 15:04:45 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by mx1.freebsd.org (Postfix) with ESMTP id BAE788FC0C for ; Wed, 7 Jan 2009 15:04:44 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: by ug-out-1314.google.com with SMTP id 30so1406277ugs.39 for ; Wed, 07 Jan 2009 07:04:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references:subject :date:message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:in-reply-to:x-mimeole; bh=YEQkDhtjL4ZUXe+7Y/aUsCD4GgtUv4wlUyN7R+08xxk=; b=fU9rifv/d/ozxqgjVFFc0BgNfla2tXwlAN+DhPOrz1f7iGof1w2z5VHC50YOvejnQD VI3SbbZ81zt8MWH1oQ1ngmKDNkOW34yQlNi67WlHWJpyPeX2qhX3VyyiCXfsOvDUiQyO P+LrbHNSkPYRdwTwz/LslZOAFf8HQY6Pf0iyc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :in-reply-to:x-mimeole; b=ocKLaZxyGruTZYh1E1gksBtV7HVMGVT/5S5UvRIyMvfqpk2YC+SfAa4lLdZru16VCM /6K34/sp5naBmajxlrhekA3ZRrRPknxgw4eVRrCCAKD7n11S2zZ6xlODmDEvYQFOUVCK P3nYTwiTefjoUuVKtdDfFta69gP5bBQ/fBFPM= Received: by 10.67.92.10 with SMTP id u10mr13978881ugl.21.1231340683636; Wed, 07 Jan 2009 07:04:43 -0800 (PST) Received: from mtllpt03 (DSL212-235-20-133.bb.netvision.net.il [212.235.20.133]) by mx.google.com with ESMTPS id j4sm27397855ugf.16.2009.01.07.07.04.41 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 07 Jan 2009 07:04:42 -0800 (PST) From: "Yony Yossef" To: "'Angelo Turetta'" , "Yony Yossef" References: <000001c970a8$3fa45240$220f000a@mtl.com> <4964C2E9.1060301@bestunion.it> Date: Wed, 7 Jan 2009 17:04:37 +0200 Message-ID: <000001c970d9$4403e590$220f000a@mtl.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: Aclw2Fh+aQAyCrQETpy8Fc7S/9oNEgAAMY2A In-Reply-To: <4964C2E9.1060301@bestunion.it> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 Cc: Eitan Shefi , freebsd-net@freebsd.org Subject: RE: VLAN interface management - unloading carrying driver hangs the machine X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Jan 2009 15:04:45 -0000 > Yony Yossef wrote: > > /sbin/ifconfig vlan3653 create > > > > Problem is when I assign an IP to the vlan interface. > > In that case, unloading the driver results in hanging the host. > > > > Does it sound familiar to anybody? > > Well, surely I'd expect problems by doing so. > The correct way is to > > /sbin/ifconfig vlan3653 destroy > > before unloading the driver. > > Angelo. Thanks, I didn't know freebsd does not allow it. Yony From owner-freebsd-net@FreeBSD.ORG Wed Jan 7 15:23:37 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2EC4F106566B for ; Wed, 7 Jan 2009 15:23:37 +0000 (UTC) (envelope-from aturetta@bestunion.it) Received: from mail.bestunion.it (mail.bestunion.it [85.18.201.87]) by mx1.freebsd.org (Postfix) with ESMTP id 7E4038FC13 for ; Wed, 7 Jan 2009 15:23:36 +0000 (UTC) (envelope-from aturetta@bestunion.it) Received: from [192.168.43.66] ([151.65.157.161]) (authenticated bits=0) by mail.bestunion.it (8.14.3/8.14.3) with ESMTP id n07EvpMs044852 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Jan 2009 15:57:57 +0100 (CET) (envelope-from aturetta@bestunion.it) Message-ID: <4964C2E9.1060301@bestunion.it> Date: Wed, 07 Jan 2009 15:57:45 +0100 From: Angelo Turetta User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Yony Yossef References: <000001c970a8$3fa45240$220f000a@mtl.com> In-Reply-To: <000001c970a8$3fa45240$220f000a@mtl.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on mail.bestunion.it X-Virus-Status: Clean Cc: Eitan Shefi , freebsd-net@freebsd.org Subject: Re: VLAN interface management - unloading carrying driver hangs the machine X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Jan 2009 15:23:37 -0000 Yony Yossef wrote: > /sbin/ifconfig vlan3653 create > > Problem is when I assign an IP to the vlan interface. > In that case, unloading the driver results in hanging the host. > > Does it sound familiar to anybody? Well, surely I'd expect problems by doing so. The correct way is to /sbin/ifconfig vlan3653 destroy before unloading the driver. Angelo. From owner-freebsd-net@FreeBSD.ORG Wed Jan 7 15:26:21 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04B4F10656C7 for ; Wed, 7 Jan 2009 15:26:21 +0000 (UTC) (envelope-from vladislav.yasevich@hp.com) Received: from g5t0006.atlanta.hp.com (g5t0006.atlanta.hp.com [15.192.0.43]) by mx1.freebsd.org (Postfix) with ESMTP id A5E148FC13 for ; Wed, 7 Jan 2009 15:26:20 +0000 (UTC) (envelope-from vladislav.yasevich@hp.com) Received: from g5t0012.atlanta.hp.com (g5t0012.atlanta.hp.com [15.192.0.49]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by g5t0006.atlanta.hp.com (Postfix) with ESMTPS id 062D2C592; Wed, 7 Jan 2009 15:09:18 +0000 (UTC) Received: from [192.168.98.100] (pool-71-255-130-196.cncdnh.east.verizon.net [71.255.130.196]) by g5t0012.atlanta.hp.com (Postfix) with ESMTPSA id 1DB5A10004; Wed, 7 Jan 2009 15:09:17 +0000 (UTC) Message-ID: <4964C59B.7050106@hp.com> Date: Wed, 07 Jan 2009 10:09:15 -0500 From: Vlad Yasevich User-Agent: Thunderbird 2.0.0.4 (X11/20070604) MIME-Version: 1.0 To: "" References: <3418F3471F1CA4409901547349FFAE2E0910679F@ftrdmel2> <2C67145C-C26B-4666-B7A5-6EC1C4ABA1E5@lurchi.franken.de> <3418F3471F1CA4409901547349FFAE2E091067B8@ftrdmel2> <2C477D99-DB2F-4EDB-950F-23856B58ACAB@lurchi.franken.de> <3418F3471F1CA4409901547349FFAE2E091067E9@ftrdmel2> <835C2156-9DE3-4C96-94F0-C7E3AF63A1BD@lurchi.franken.de> <3418F3471F1CA4409901547349FFAE2E09106883@ftrdmel2> In-Reply-To: X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: Michael Tuexen , khadija.daoud@orange-ftgroup.com, Randall Stewart , freebsd-net Subject: Re: SCTP : problems in sending ASCONF chunks X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Jan 2009 15:26:22 -0000 Randall Stewart wrote: > Aman: > > You may also want to contact Vlad (copied above) who is responsible > for the lk-sctp implementation.. he may be able to direct you to > the one that will have all his latest fixes.. > > Regards To turn on support of ASCONF, you need to turn on at least 2 sysctl variables: net.sctp.auth_enable net.sctp.addip_enable If one of your systems does not support AUTH extension, then you need to turn on: net.sctp.addip_noauth_enable There were issues in older kernels. I'd advise using at least a 2.6.25 kernel from kernel.org. -vlad > > R > On Dec 30, 2008, at 10:59 AM, > wrote: > >> >> Hello M.Tüxen, >> >> Today I switched T (the machine I use for testing, and that sends data >> to my PC) to FreeBSD 7.0. And I was very glad to see that my SCTP hard >> handover tests went through successfully :-) >> >> I am very grateful to you, for pointing out that I should check the >> INIT - INIT-ACK exchange, because so far I really didn't understand >> why my tests failed all the time. >> >> About lksctp : up until now, my problems were due to the fact that the >> CN was running under Linux, with the lksctp implementation, and that >> it didn't indicate in the INIT-ACK that it supports ASCONF, ASCONF-ACK >> and AUTH chunks at least, even if we have set the parameter >> net.sctp.addip_enable to 1. These are required for Dynamic Address >> Reconfiguration according to the RFC and very likely in FreeBSD >> implementation for sending ASCONF. >> >> I will perform tests between my PC running under FreeBSD and T running >> on Fedora Core 9 to see if I have better results than what I've had so >> far (since I was using Fedora Core 7). I will keep you updated :-) >> >> Again, thanks a LOT for the help you provided, I'm truly thankful for >> this. >> >> >> Aman Jassal >> >> >> >> -----Message d'origine----- >> De : Michael Tüxen [mailto:Michael.Tuexen@lurchi.franken.de] >> Envoyé : lundi 29 décembre 2008 19:00 >> À : zze-Abac JASSAL A ext RD-RESA-ISS >> Cc : freebsd-net@freebsd.org; DAOUD TRIKI Khadija RD-RESA-ISS >> Objet : Re: SCTP : problems in sending ASCONF chunks >> >> Hi Aman, >> >> comments in-line. >> >> Best regards >> Michael >> >> On Dec 29, 2008, at 6:12 PM, >> wrote: >> >>> >>> Hello M.Tüxen, >>> >>> I performed a quick test and at the INIT/INIT-ACK exchange, I noticed >>> the following : >>> >>> - In the INIT chunk, the Supported Extensions Parameter field >>> indicates that ASCONF, ASCONF-ACK, FORWARD-TSN, PKTDROP, STREAM_RESET >>> and AUTH are supported >> OK. That is the FreeBSD box. >>> >>> - In the INIT-ACK chunk, there is no field indicating that any of >>> the chunks listed above are supported... >> So it does not support ASCONF and AUTH. >> At least on a Fedora 9 box you need to enable ADD-IP by setting the >> sysctl variable >> net.sctp.addip_enable >> to 1. >> To enable SCTP-AUTH you need to set the sysctl variable >> net.sctp.auth_enable >> to 1. >> I'm not sure whether the Linux box support SCTP-AUTH or not... So the >> second step might not work. If this is the case you can disable the >> AUTH requirement for ASCONF chunks by setting on the FreeBSD box the >> sysctl >> variable >> net.inet.sctp.asconf_auth_nochk >> to 1 >> >> Let me know if this works... >>> >>> >>> I didn't think about looking in this before >_< >>> >>> Since there is no indication given to my PC, perhaps my PC assumes >>> that T doesn't support ASCONF, ASCONF-ACK, FORWARD-TSN, PKTDROP, >>> STREAM_RESET and AUTH. >> Correct. At least some of the extension are not enabled. >>> >>> >>> Could it be that, because it doesn't see any Supported Extensions >>> Parameter field in the INIT-ACK, my PC doesn't try to send any >>> ASCONF chunk ?? Do we absolutely need to have the ASCONF, ASCONF-ACK >>> and AUTH parameters in the Supported Extensions Parameter, in both >>> the INIT and the INIT-ACK chunks, to have the possibility of sending >>> an ASCONF chunk ? >> In principle, yes! You can work around the AUTH chunks as indicated >> above, but this >> violates the specification and is only supported to interwork with >> legacy implementations. >>> >>> >>> >>> Kind regards >>> >>> >>> Aman Jassal >>> >>> >>> -----Message d'origine----- >>> De : Michael Tüxen [mailto:Michael.Tuexen@lurchi.franken.de] >>> Envoyé : lundi 29 décembre 2008 16:49 >>> À : zze-Abac JASSAL A ext RD-RESA-ISS >>> Cc : freebsd-net@freebsd.org; DAOUD TRIKI Khadija RD-RESA-ISS >>> Objet : Re: SCTP : problems in sending ASCONF chunks >>> >>> Hi Aman, >>> >>> I'm not that familiar with the Linux box configuration. If you look >>> at the INIT/INIT-ACK exchange, does the Linux box support ASCONF and >>> the SCTP-AUTH extension? Both are required... >>> >>> Best regards >>> Michael >>> On Dec 29, 2008, at 2:36 PM, >>> >>> wrote: >>> >>>> >>>> Hello M.Tüxen, >>>> >>>> No, only the PC is running under FreeBSD 7.0. T is running under >>>> Linux >>>> (kernel version is 2.6.21 and the distribution used is Fedora Core >>>> 7). >>>> SCTP is running on T thanks to the lksctp implementation, we loaded >>>> the sctp module on it and made the necessary configurations so that >>>> it >>>> is loaded at boot time. >>>> >>>> Also, I enable net.sctp.addip_enable=1 on T, just in case, I'm not >>>> exactly sure if it has an effect on my tests. >>>> >>>> Kind regards >>>> >>>> >>>> Aman Jassal >>>> >>>> -----Message d'origine----- >>>> De : Michael Tüxen [mailto:Michael.Tuexen@lurchi.franken.de] >>>> Envoyé : lundi 29 décembre 2008 14:09 >>>> À : zze-Abac JASSAL A ext RD-RESA-ISS >>>> Cc : freebsd-net@freebsd.org; DAOUD TRIKI Khadija RD-RESA-ISS Objet : >>>> Re: SCTP : problems in sending ASCONF chunks >>>> >>>> Hi, >>>> >>>> are both machines (T and you PC) running FreeBSD? >>>> >>>> Best regards >>>> Michael >>>> >>>> On Dec 29, 2008, at 12:33 PM, >>>> >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> I have been working with SCTP and more specifically with the >>>>> mobility >>>>> features of SCTP at my work. Basically, I have been trying to use >>>>> SCTP to perform handover tests between 2 separate Wifi networks. I >>>>> use >>>>> IPv6 >>>>> for all my tests. >>>>> >>>>> I have a local LAN (wired-network), on which I have 3 machines, one >>>>> of them is the machine I use to communicate with for the tests (I'll >>>>> call it T to make things simple), and the other two are used as Wifi >>>>> Access Points (say Wifi1 and Wifi2 respectively). Since I work with >>>>> IPv6, I set up both Access Points to send Router Advertisement >>>>> messages periodically (minimum of 3 seconds, maximum of 4 seconds). >>>>> That way I can have automatic address reconfiguration when I connect >>>>> to either of the access points. >>>>> >>>>> The aim of my tests is to use a PC, connect to Wifi1 (for example), >>>>> launch an SCTP association with T (T sends data to my PC), and then >>>>> perform a handover on Wifi2. I do make address reconfiguration >>>>> during >>>>> the handover process. The important point is that I work with only >>>>> ONE address on my network interface. Before I start my tests, I set >>>>> the following sysctl parameters : >>>>> >>>>> # sysctl -w net.inet.sctp.mobility_base=1 # sysctl -w >>>>> net.inet.sctp.mobility_fasthandoff=1 >>>>> # sysctl -w net.inet.sctp.debug=0x00f301f0 (that is to dump >>>>> messages in /var/log/messages) >>>>> >>>>> net.inet.sctp.auto_asconf is set to 1 by default. >>>>> >>>>> I use FreeBSD 7.0 on my PC, I don't know if that is extremely useful >>>>> but I'm trying to be thorough. This is the script I use to perform >>>>> handover >>>>> : >>>>> >>>>> ifconfig rum0 inet6 delete ifconfig rum0 ssid >>>> target access point> route del -inet6 default rtsol >>>>> rum0 >>>>> >>>>> If I'm not mistaken, the PC should have sent an ASCONF chunk to >>>>> perform dynamic address reconfiguration. However what I observed is >>>>> that nothing happens. No ASCONF chunks are sent, and therefore, T >>>>> doesn't ever know that it should send data on the PC's newly >>>>> acquired >>>>> address. >>>>> >>>>> I tried to investigate the problem myself, by adding some debug logs >>>>> in the sctp source code (to see which functions are called during >>>>> the >>>>> handover process), and it seems as if the kernel doesn't ever add an >>>>> ASCONF chunk to send in its queue... But that's just my >>>>> understanding >>>>> of the problem... >>>>> >>>>> I looked up in the CVS repository for answers, and to see the >>>>> various >>>>> changes that were gradually brought on the code. There, I noticed >>>>> that on the revision dating 24th July 2007, changes were made for >>>>> dynamic address reconfiguration : "Change behaviour so that when the >>>>> last address is deleted (auto-asconf on a boudall endpoint) no >>>>> action >>>>> is taken until an address is added ; at that time an ASCONF >>>>> add+delete is sent (if the asoc is still up)" >>>>> >>>>> In my humble opinion, this is exactly the case that corresponds to >>>>> my >>>>> handover scenario. But I just haven't been able to successfully >>>>> perform it because I don't seem to send any ASCONF chunk. I'm >>>>> struggling to understand why I do not see any ASCONF chunk sent. >>>>> >>>>> If it can help, I'm also attaching links to the kind of debug logs I >>>>> got when performing a handover test. This is the kind of debug logs >>>>> that I got : >>>>> >>>>> http://www.divshare.com/download/6200509-560 >>>>> >>>>> This is another debug logfile, but with my own debug logs added in >>>>> the sctp source code : >>>>> >>>>> http://www.divshare.com/download/6200504-2e9 >>>>> >>>>> >>>>> Many thanks for your work, and I hope someone will be able to help >>>>> and shed some light on this problem :-) >>>>> >>>>> >>>>> Aman Jassal >>>>> >>>>> _______________________________________________ >>>>> 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" >>>>> >>>> >>>> >>> >>> >> >> _______________________________________________ >> 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" >> > > ------------------------------ > Randall Stewart > 803-317-4952 (cell) > 803-345-0391(direct) > From owner-freebsd-net@FreeBSD.ORG Wed Jan 7 15:52:43 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB59A1065670 for ; Wed, 7 Jan 2009 15:52:43 +0000 (UTC) (envelope-from bmw@wezel.com) Received: from toq8-srv.bellnexxia.net (bc.sympatico.ca [209.226.175.204]) by mx1.freebsd.org (Postfix) with ESMTP id 6266E8FC1B for ; Wed, 7 Jan 2009 15:52:43 +0000 (UTC) (envelope-from bmw@wezel.com) Received: from toip4.srvr.bell.ca ([209.226.175.87]) by tomts36-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20090107152849.HRKN1669.tomts36-srv.bellnexxia.net@toip4.srvr.bell.ca> for ; Wed, 7 Jan 2009 10:28:49 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AlwFALBTZElBX3e3/2dsb2JhbACBbM4zhXU Received: from bas2-toronto63-1096775607.dsl.bell.ca (HELO mg-i1200.home.wezel.com) ([65.95.119.183]) by toip4.srvr.bell.ca with ESMTP; 07 Jan 2009 10:38:02 -0500 Message-ID: <4964CA2E.5090708@wezel.com> Date: Wed, 07 Jan 2009 10:28:46 -0500 From: Bruce Walker User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: Peter Steele References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com> In-Reply-To: <2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Jan 2009 15:52:44 -0000 Peter Steele wrote: > When our boxes are initially deployed, they have no IP addresses > assigned to them. Their ifconfig entry looks like this: > > ifconfig_lagg0="laggproto failover laggport nfe0 laggport nfe1" > > With this config, no IP is assigned to the lagg0 device, so the only way > to access the boxes is via a serial console. Peter, leaving aside the issue of FreeBSD limited broadcast, have you considered ZeroConf, and in particular the IPv4 Link-Level Addressing portion of it to meet your basic "get the boxes addressed" requirement? http://www.zeroconf.org/ http://files.zeroconf.org/rfc3927.txt I don't have any experience with the lagg device yet, so I don't know if that presents specific issues wrt ipv4ll code. -bmw From owner-freebsd-net@FreeBSD.ORG Wed Jan 7 16:40:36 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB56310656D9 for ; Wed, 7 Jan 2009 16:40:36 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 801278FC55 for ; Wed, 7 Jan 2009 16:40:36 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 974E1202EEC; Wed, 7 Jan 2009 11:40:35 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 07 Jan 2009 11:40:35 -0500 X-Sasl-enc: 7UdjPUIfskWyL0wQ75U9V+/Ot4XY19kFAhjDDarYAaGR 1231346435 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id F250E1EDB3; Wed, 7 Jan 2009 11:40:34 -0500 (EST) Message-ID: <4964DB01.7000201@FreeBSD.org> Date: Wed, 07 Jan 2009 16:40:33 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.18 (X11/20081205) MIME-Version: 1.0 To: Peter Steele References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> In-Reply-To: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Jan 2009 16:40:51 -0000 Peter Steele wrote: > .. > > Based on the discussion in the link above, it doesn't seem like the > problem was entirely resolved by the patches mentioned in this thread. > Has anything been done since this discussion took place. Surely there > must be a way to get limited broadcast to work under FreeBSD. > You will need to go to the pcap layer to send limited broadcasts w/o any IPv4 addresses configured in a BSD stack for now. If you have an IP on the interface, you can just use IP_ONESBCAST. thanks BMS > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Wed Jan 7 17:54:44 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 316851065670 for ; Wed, 7 Jan 2009 17:54:44 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 084A48FC18 for ; Wed, 7 Jan 2009 17:54:43 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n07HsNft063782 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Jan 2009 09:54:28 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <4964EC4F.8030507@freebsd.org> Date: Wed, 07 Jan 2009 09:54:23 -0800 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081209) MIME-Version: 1.0 To: Yony Yossef References: <000001c970a8$3fa45240$220f000a@mtl.com> <4964C2E9.1060301@bestunion.it> <000001c970d9$4403e590$220f000a@mtl.com> In-Reply-To: <000001c970d9$4403e590$220f000a@mtl.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: Eitan Shefi , 'Angelo Turetta' , freebsd-net@freebsd.org Subject: Re: VLAN interface management - unloading carrying driver hangs the machine X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Jan 2009 17:54:44 -0000 Yony Yossef wrote: >> Yony Yossef wrote: >> >>> /sbin/ifconfig vlan3653 create >>> >>> Problem is when I assign an IP to the vlan interface. >>> In that case, unloading the driver results in hanging the host. >>> >>> Does it sound familiar to anybody? >>> >> Well, surely I'd expect problems by doing so. >> The correct way is to >> >> /sbin/ifconfig vlan3653 destroy >> >> before unloading the driver. >> >> Angelo. >> > > Thanks, I didn't know freebsd does not allow it. > > This seems wrong. Someone should disallow the driver detach/unload. Please file a PR about this so the issue is not lost. Sam From owner-freebsd-net@FreeBSD.ORG Wed Jan 7 18:37:16 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54F411065749 for ; Wed, 7 Jan 2009 18:37:16 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from arcturus.maxiscale.com (arcturus.maxiscale.com [76.231.178.136]) by mx1.freebsd.org (Postfix) with ESMTP id 2E6ED8FC1B for ; Wed, 7 Jan 2009 18:37:15 +0000 (UTC) (envelope-from psteele@maxiscale.com) X-ASG-Debug-ID: 1231353434-5b1200030000-QdxwpM X-Barracuda-URL: http://10.100.1.25:8000/cgi-bin/mark.cgi Received: from polaris.maxiscale.com (localhost [127.0.0.1]) by arcturus.maxiscale.com (Spam Firewall) with ESMTP id 33018361AB for ; Wed, 7 Jan 2009 10:37:15 -0800 (PST) Received: from polaris.maxiscale.com (polaris.maxiscale.com [10.100.1.24]) by arcturus.maxiscale.com with ESMTP id HPRGwiqN0p4SJFRE for ; Wed, 07 Jan 2009 10:37:15 -0800 (PST) X-ASG-Whitelist: Client X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-ASG-Orig-Subj: RE: Having problems with limited broadcast Date: Wed, 7 Jan 2009 10:37:13 -0800 Message-ID: <2ACA3DE8F9758A48B8BE2C7A847F91F2479ECA@polaris.maxiscale.com> In-Reply-To: <4964DB01.7000201@FreeBSD.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Having problems with limited broadcast Thread-Index: Aclw5rMxjxPRI+ikTMqGgs7j6gbFzgAD/N2Q References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> <4964DB01.7000201@FreeBSD.org> From: "Peter Steele" To: X-Barracuda-Connect: polaris.maxiscale.com[10.100.1.24] X-Barracuda-Start-Time: 1231353435 X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at maxiscale.com Subject: RE: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Jan 2009 18:37:16 -0000 > You will need to go to the pcap layer to send limited broadcasts w/o any=20 > IPv4 addresses configured in a BSD stack for now. If you have an IP on > the interface, you can just use IP_ONESBCAST. Yes, I can send broadcasts if my box has an IP. Since we are writing our own DHCP-like service though this isn't an option for us, so pcap seems to be the route to go... From owner-freebsd-net@FreeBSD.ORG Wed Jan 7 22:00:00 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E886D106582B for ; Wed, 7 Jan 2009 21:59:59 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by mx1.freebsd.org (Postfix) with ESMTP id AC6458FC18 for ; Wed, 7 Jan 2009 21:59:59 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wa-out-1112.google.com with SMTP id m34so4803301wag.27 for ; Wed, 07 Jan 2009 13:59:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=HY164/IR2hxD3At+4ZTmWjFl+sjqy4RumRjBsMg15O4=; b=M85CQv5v2/woNxxOTm9eqwzHYbJG+vwUgmV5geybkFoklATsESoXL0eAeidrynlb7t EqI4wNRMUec04m5Igt2UUdcXjkrwtrhQy1EuHUGKoUqrgZfxpMv9tep1Ym/4C3253grA l53jBFBhhoLoQEpV4GCrJKIUeTFBbSisfnVSE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=M2w5EWWoqi0Ak7OnfS3hlCqEAjQuY3COdPWzW239rlVOv6ucsIBsuwjAfKfS+qiMg7 bzVerBhyBTwF78R0VbIq2vmAl77ONwvfI3R7nE4qIuPeGPk53lkmsx+OHHDa1xGAxpCV oReXSOG3PtxQb7Lee7D65lIwkrLAk3SOyHenw= Received: by 10.114.111.1 with SMTP id j1mr1987941wac.153.1231365598724; Wed, 07 Jan 2009 13:59:58 -0800 (PST) Received: by 10.114.157.9 with HTTP; Wed, 7 Jan 2009 13:59:58 -0800 (PST) Message-ID: <2a41acea0901071359w3f41465ajb8206cdef5b7b680@mail.gmail.com> Date: Wed, 7 Jan 2009 13:59:58 -0800 From: "Jack Vogel" To: "Sam Leffler" In-Reply-To: <4964EC4F.8030507@freebsd.org> MIME-Version: 1.0 References: <000001c970a8$3fa45240$220f000a@mtl.com> <4964C2E9.1060301@bestunion.it> <000001c970d9$4403e590$220f000a@mtl.com> <4964EC4F.8030507@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Eitan Shefi , Angelo Turetta , Yony Yossef , freebsd-net@freebsd.org Subject: Re: VLAN interface management - unloading carrying driver hangs the machine X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Jan 2009 22:00:03 -0000 On Wed, Jan 7, 2009 at 9:54 AM, Sam Leffler wrote: > Yony Yossef wrote: > >> Yony Yossef wrote: >>> >>> >>>> /sbin/ifconfig vlan3653 create >>>> >>>> Problem is when I assign an IP to the vlan interface. >>>> In that case, unloading the driver results in hanging the host. >>>> Does it sound familiar to anybody? >>>> >>>> >>> Well, surely I'd expect problems by doing so. >>> The correct way is to >>> >>> /sbin/ifconfig vlan3653 destroy >>> >>> before unloading the driver. >>> >>> Angelo. >>> >>> >> >> Thanks, I didn't know freebsd does not allow it. >> >> >> > This seems wrong. Someone should disallow the driver detach/unload. Please > file a PR about this so the issue is not lost. > > Sam > In many drivers, ahem, like mine, there is a test at detach and it will not allow it if there is a non-NULL trunk. Sounds like a broken driver needs to be fixed is all... Jack From owner-freebsd-net@FreeBSD.ORG Wed Jan 7 22:35:32 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 607BF106587F for ; Wed, 7 Jan 2009 22:35:32 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 2E4898FC16 for ; Wed, 7 Jan 2009 22:35:31 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n07MZHob065362 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Jan 2009 14:35:17 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <49652E25.9030705@freebsd.org> Date: Wed, 07 Jan 2009 14:35:17 -0800 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081209) MIME-Version: 1.0 To: Jack Vogel References: <000001c970a8$3fa45240$220f000a@mtl.com> <4964C2E9.1060301@bestunion.it> <000001c970d9$4403e590$220f000a@mtl.com> <4964EC4F.8030507@freebsd.org> <2a41acea0901071359w3f41465ajb8206cdef5b7b680@mail.gmail.com> In-Reply-To: <2a41acea0901071359w3f41465ajb8206cdef5b7b680@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: Eitan Shefi , Angelo Turetta , Yony Yossef , freebsd-net@freebsd.org Subject: Re: VLAN interface management - unloading carrying driver hangs the machine X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Jan 2009 22:35:36 -0000 Jack Vogel wrote: > > > On Wed, Jan 7, 2009 at 9:54 AM, Sam Leffler > wrote: > > Yony Yossef wrote: > > Yony Yossef wrote: > > > /sbin/ifconfig vlan3653 create > > Problem is when I assign an IP to the vlan interface. > In that case, unloading the driver results in hanging > the host. > Does it sound familiar to anybody? > > > Well, surely I'd expect problems by doing so. > The correct way is to > > /sbin/ifconfig vlan3653 destroy > > before unloading the driver. > > Angelo. > > > > Thanks, I didn't know freebsd does not allow it. > > > > This seems wrong. Someone should disallow the driver > detach/unload. Please file a PR about this so the issue is not lost. > > Sam > > > In many drivers, ahem, like mine, there is a test at detach and it > will not allow it if there > is a non-NULL trunk. > > Sounds like a broken driver needs to be fixed is all... > I don't agree; drivers should not be required to deal with this. If someone files a PR and assigns it to me I'll look at it. Sam From owner-freebsd-net@FreeBSD.ORG Thu Jan 8 08:18:46 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01FA0106566B for ; Thu, 8 Jan 2009 08:18:46 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170]) by mx1.freebsd.org (Postfix) with ESMTP id 54E6A8FC1B for ; Thu, 8 Jan 2009 08:18:44 +0000 (UTC) (envelope-from yonyossef.lists@gmail.com) Received: by ug-out-1314.google.com with SMTP id 30so1458348ugs.39 for ; Thu, 08 Jan 2009 00:18:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references:subject :date:message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:in-reply-to:x-mimeole; bh=d/OESLjEMandt5w2NyqqU82yrvl/69jI7XoITwltzRk=; b=AHRq5pcuSjYabIYaKlTPiC/418fndwPEdSJFoDm6/iNLGSM4/t6DA4PgGXBgBvOvww sADaGF7Dc1bhXjPeef1p7xuwyzIMxAsq3xRcp6vH37i4TiGr2utfrMNmwhPo4qjfqdrH rU4Dks0G8gjQVY8TLXIEcPx6zDQmp1fSqLyQs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :in-reply-to:x-mimeole; b=gSIk5KxDjnumWRkhh7gu9hOXBoHFNSqvrUJh3sR1C/ALOiJsKbklj+qLZDrsp1EPbs UoGAaA4y2h8Ogz/UqIWDgrT+sHRBc3o6pcO6oqTAeC50O90+aed3m01Nb2a4fcjM4nMJ iCnwRNnx1XbIN3gjCpqxJPR+Fxbfsbyjw69uI= Received: by 10.67.40.6 with SMTP id s6mr3139494ugj.10.1231402724207; Thu, 08 Jan 2009 00:18:44 -0800 (PST) Received: from mtllpt03 (DSL212-235-20-133.bb.netvision.net.il [212.235.20.133]) by mx.google.com with ESMTPS id y6sm27996711uge.28.2009.01.08.00.18.42 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 08 Jan 2009 00:18:43 -0800 (PST) From: "Yony Yossef" To: "'Sam Leffler'" , "Jack Vogel" References: <000001c970a8$3fa45240$220f000a@mtl.com> <4964C2E9.1060301@bestunion.it> <000001c970d9$4403e590$220f000a@mtl.com> <4964EC4F.8030507@freebsd.org> <2a41acea0901071359w3f41465ajb8206cdef5b7b680@mail.gmail.com> <49652E25.9030705@freebsd.org> Date: Thu, 8 Jan 2009 10:18:40 +0200 Message-ID: <000601c97169$b85717b0$220f000a@mtl.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: AclxGEMroQ0DEzw2TpiyBNWaKlAhXAAUSMfw In-Reply-To: <49652E25.9030705@freebsd.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 Cc: Eitan Shefi , Angelo Turetta , Yony Yossef , freebsd-net@freebsd.org Subject: RE: VLAN interface management - unloading carrying driver hangs the machine X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Jan 2009 08:18:46 -0000 > Jack Vogel wrote: > > > > > > On Wed, Jan 7, 2009 at 9:54 AM, Sam Leffler > > wrote: > > > > Yony Yossef wrote: > > > > Yony Yossef wrote: > > > > > > /sbin/ifconfig vlan3653 create > > > > Problem is when I assign an IP to the vlan > interface. > > In that case, unloading the driver results > in hanging > > the host. > > Does it sound familiar to anybody? > > > > > > Well, surely I'd expect problems by doing so. > > The correct way is to > > > > /sbin/ifconfig vlan3653 destroy > > > > before unloading the driver. > > > > Angelo. > > > > > > > > Thanks, I didn't know freebsd does not allow it. > > > > > > > > This seems wrong. Someone should disallow the driver > > detach/unload. Please file a PR about this so the issue > is not lost. > > > > Sam > > > > > > In many drivers, ahem, like mine, there is a test at detach and it > > will not allow it if there is a non-NULL trunk. > > > > Sounds like a broken driver needs to be fixed is all... > > > I don't agree; drivers should not be required to deal with > this. If someone files a PR and assigns it to me I'll look at it. > > Sam > I agree with Sam. There's no reason to leave this check to the driver. Yony From owner-freebsd-net@FreeBSD.ORG Thu Jan 8 08:31:04 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B2ED10656CC; Thu, 8 Jan 2009 08:31:04 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 313C58FC0A; Thu, 8 Jan 2009 08:31:04 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n088V4qb082325; Thu, 8 Jan 2009 08:31:04 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n088V4Qa082321; Thu, 8 Jan 2009 08:31:04 GMT (envelope-from linimon) Date: Thu, 8 Jan 2009 08:31:04 GMT Message-Id: <200901080831.n088V4Qa082321@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/130189: [ndis] [patch] if_ndis typo 802.11 mode test X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Jan 2009 08:31:05 -0000 Old Synopsis: [patch] if_ndis typo 802.11 mode test New Synopsis: [ndis] [patch] if_ndis typo 802.11 mode test Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Thu Jan 8 08:30:39 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=130189 From owner-freebsd-net@FreeBSD.ORG Thu Jan 8 09:09:17 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 059F91065673; Thu, 8 Jan 2009 09:09:17 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by mx1.freebsd.org (Postfix) with ESMTP id BE8878FC27; Thu, 8 Jan 2009 09:09:16 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wa-out-1112.google.com with SMTP id m34so4931314wag.27 for ; Thu, 08 Jan 2009 01:09:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=fcMlNiuwheoD8gzXxX7BHQryUVdfiS1SuKGaVBJVTPs=; b=RrwcwC4OCMYHIcZFrNdZPuh2eC0/ag88qE8qAtZcTvCKyje2leFHH5NwMJ17JjeUxq Bf0mMs576f7xsBXw++pcRVjmSFla1ygJTR2QL/0jywz3g+S23WmQV6wXpV28y6yQaKad MFyV6nF2zHCVhX4RAK0JL+K0jxo4zzTFx0v+I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=a9UZ0c3jB0lCso2v0KZ/UzLQVI64FE7SgvjlONFmW160+fYCzZbdW7Axw6YFseTNas OlTdqQxwrjB/b9s063utykIhEQflPWXyIU1K9vFuPsb0+JhyRj9LRb3LlIPFQ211KmHO AOd6A8i25piOzLEfOrHeRicjkkKxQxKv570Bk= Received: by 10.115.92.2 with SMTP id u2mr15903142wal.228.1231405756193; Thu, 08 Jan 2009 01:09:16 -0800 (PST) Received: by 10.114.157.9 with HTTP; Thu, 8 Jan 2009 01:09:16 -0800 (PST) Message-ID: <2a41acea0901080109l6189b379q4a348cc80527e90e@mail.gmail.com> Date: Thu, 8 Jan 2009 01:09:16 -0800 From: "Jack Vogel" To: "Yony Yossef" In-Reply-To: <000601c97169$b85717b0$220f000a@mtl.com> MIME-Version: 1.0 References: <000001c970a8$3fa45240$220f000a@mtl.com> <4964C2E9.1060301@bestunion.it> <000001c970d9$4403e590$220f000a@mtl.com> <4964EC4F.8030507@freebsd.org> <2a41acea0901071359w3f41465ajb8206cdef5b7b680@mail.gmail.com> <49652E25.9030705@freebsd.org> <000601c97169$b85717b0$220f000a@mtl.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Eitan Shefi , Angelo Turetta , Sam Leffler , freebsd-net@freebsd.org Subject: Re: VLAN interface management - unloading carrying driver hangs the machine X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Jan 2009 09:09:17 -0000 Fine with me, go do it and I'll take the driver code out :) Jack On Thu, Jan 8, 2009 at 12:18 AM, Yony Yossef wrote: > > Jack Vogel wrote: > > > > > > > > > On Wed, Jan 7, 2009 at 9:54 AM, Sam Leffler > > > wrote: > > > > > > Yony Yossef wrote: > > > > > > Yony Yossef wrote: > > > > > > > > > /sbin/ifconfig vlan3653 create > > > > > > Problem is when I assign an IP to the vlan > > interface. > > > In that case, unloading the driver results > > in hanging > > > the host. > > > Does it sound familiar to anybody? > > > > > > > > > Well, surely I'd expect problems by doing so. > > > The correct way is to > > > > > > /sbin/ifconfig vlan3653 destroy > > > > > > before unloading the driver. > > > > > > Angelo. > > > > > > > > > > > > Thanks, I didn't know freebsd does not allow it. > > > > > > > > > > > > This seems wrong. Someone should disallow the driver > > > detach/unload. Please file a PR about this so the issue > > is not lost. > > > > > > Sam > > > > > > > > > In many drivers, ahem, like mine, there is a test at detach and it > > > will not allow it if there is a non-NULL trunk. > > > > > > Sounds like a broken driver needs to be fixed is all... > > > > > I don't agree; drivers should not be required to deal with > > this. If someone files a PR and assigns it to me I'll look at it. > > > > Sam > > > > I agree with Sam. There's no reason to leave this check to the driver. > > Yony > > From owner-freebsd-net@FreeBSD.ORG Thu Jan 8 19:16:50 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2DAA3106564A for ; Thu, 8 Jan 2009 19:16:50 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from arcturus.maxiscale.com (arcturus.maxiscale.com [76.231.178.136]) by mx1.freebsd.org (Postfix) with ESMTP id 0AFD08FC1E for ; Thu, 8 Jan 2009 19:16:49 +0000 (UTC) (envelope-from psteele@maxiscale.com) X-ASG-Debug-ID: 1231442208-5aff00040000-QdxwpM X-Barracuda-URL: http://10.100.1.25:8000/cgi-bin/mark.cgi Received: from polaris.maxiscale.com (localhost [127.0.0.1]) by arcturus.maxiscale.com (Spam Firewall) with ESMTP id BBFD4365C9 for ; Thu, 8 Jan 2009 11:16:48 -0800 (PST) Received: from polaris.maxiscale.com (polaris.maxiscale.com [10.100.1.24]) by arcturus.maxiscale.com with ESMTP id sEzavXtEQDlBVEVB for ; Thu, 08 Jan 2009 11:16:48 -0800 (PST) X-ASG-Whitelist: Client X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-ASG-Orig-Subj: RE: Having problems with limited broadcast Date: Thu, 8 Jan 2009 11:16:48 -0800 Message-ID: <2ACA3DE8F9758A48B8BE2C7A847F91F2479FB0@polaris.maxiscale.com> In-Reply-To: <4964CA2E.5090708@wezel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Having problems with limited broadcast Thread-Index: Aclw3KjZAd4JfFh4Rg2uRWJdMhlnTQA53dHA References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com> <4964CA2E.5090708@wezel.com> From: "Peter Steele" To: "Bruce Walker" X-Barracuda-Connect: polaris.maxiscale.com[10.100.1.24] X-Barracuda-Start-Time: 1231442208 X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at maxiscale.com Cc: freebsd-net@freebsd.org Subject: RE: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Jan 2009 19:16:50 -0000 >Peter, leaving aside the issue of FreeBSD limited broadcast, have you=20 >considered ZeroConf, and in particular the IPv4 Link-Level Addressing=20 >portion of it to meet your basic "get the boxes addressed" requirement? > >http://www.zeroconf.org/ >http://files.zeroconf.org/rfc3927.txt > >I don't have any experience with the lagg device yet, so I don't know if=20 >that presents specific issues wrt ipv4ll code. I just found your email in my junk email folder. For some reason my filter didn't like it. Thanks for the suggestion though. I'm not familiar with ZeroConf; I'll check it out. The lagg device should not be a problem. It appears as a normal Ethernet device as far as the OS is concerned. Peter From owner-freebsd-net@FreeBSD.ORG Thu Jan 8 20:14:37 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B42A8106566B for ; Thu, 8 Jan 2009 20:14:37 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.27]) by mx1.freebsd.org (Postfix) with ESMTP id 6E4F38FC0A for ; Thu, 8 Jan 2009 20:14:37 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by qw-out-2122.google.com with SMTP id 9so5311127qwb.7 for ; Thu, 08 Jan 2009 12:14:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:mime-version:content-type:content-transfer-encoding :content-disposition:x-google-sender-auth; bh=yuTjmU4mQyS1TrzcyZm70aDN87mRUjVOesk1NqHqupc=; b=CwyW6cLAoP+3wcjFCiuMV91SbUrIegyZDEuJUgFOrD6L76fxGT0zdoHV8otEa3WRJ0 uLn1GgBzJIGA+xUUPyI47jnG4A8+cuIOW+KJiboMChK6mw3A2HeMIPjlY1hl3Ti257Vq nKuSHIZza3uz2Ni5BW6qm0eN+JKTF6MhHtJEM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition:x-google-sender-auth; b=pTrTpAAHA66gtQCQHR+Oo7M0DL5GXnweRuGd5/7uHOaxuAx70L2fdmdllfGqJyeYL0 Pq15pBl1rYZd4oNnlYIRnEKELnq4dcrB8q+b156PU/Yknx/0LAD4gPIAfh64jDpwddxU eb/TIiNEqPqTH0Z7pj4Nk/IWDvZg1r2OdYt00= Received: by 10.215.12.4 with SMTP id p4mr7585089qai.154.1231443977389; Thu, 08 Jan 2009 11:46:17 -0800 (PST) Received: by 10.214.81.13 with HTTP; Thu, 8 Jan 2009 11:46:17 -0800 (PST) Message-ID: Date: Thu, 8 Jan 2009 14:46:17 -0500 From: "Adrian Chadd" Sender: adrian.chadd@gmail.com To: "FreeBSD Net" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Google-Sender-Auth: 3e631a1bc3194175 Subject: Julian's source IP address spoofing - code review requested X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Jan 2009 20:14:37 -0000 G'day all, I've finally gotten around to pulling apart some of Julian Elischer's work on the source IP address spoofing stuff and I've been testing it on my local squid-2 fork (cacheboy.) I'd appreciate some comments and review before I begin committing bits of it to freebsd-current. The work will be available here, including a brief description of what is going on: http://people.freebsd.org/~adrian/sys/spoof_bind/ I'd first like to commit the core changes which introduce a new compile option, sysctl and IP option to enable a non-local IP address in bind(). That in itself is enough to at least begin testing under -current and releng_7. The diff against -current for this first phase is available here: http://people.freebsd.org/~adrian/sys/spoof_bind/spoof_bind_sys.diff I'm currently running just this patch on a machine in the netperf cluster which is acting as a transparent HTTP interception thing. It seems to handle "moderate" request rates (~1500 socket creations a second, ~150mbit). This first patch is pretty straight forward and I'm reasonably confident that it won't break anything in -current or releng_7 which isn't already broken. There are other changes to IPFW and the bridging code which I'll ask to be reviewed separately. Thanks! Adrian From owner-freebsd-net@FreeBSD.ORG Thu Jan 8 20:55:24 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74D981065674; Thu, 8 Jan 2009 20:55:24 +0000 (UTC) (envelope-from prvs=julian=25242c0f6@elischer.org) Received: from smtp-outbound.ironport.com (smtp-outbound.ironport.com [63.251.108.112]) by mx1.freebsd.org (Postfix) with ESMTP id 5D5FC8FC08; Thu, 8 Jan 2009 20:55:24 +0000 (UTC) (envelope-from prvs=julian=25242c0f6@elischer.org) Received: from unknown (HELO julian-mac.elischer.org) ([10.251.60.63]) by smtp-outbound.ironport.com with ESMTP; 08 Jan 2009 12:26:50 -0800 Message-ID: <49666189.9010406@elischer.org> Date: Thu, 08 Jan 2009 12:26:49 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: Adrian Chadd References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Net Subject: Re: Julian's source IP address spoofing - code review requested X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Jan 2009 20:55:24 -0000 Adrian Chadd wrote: > G'day all, > > I've finally gotten around to pulling apart some of Julian Elischer's > work on the source IP address spoofing stuff and I've been testing it > on my local squid-2 fork (cacheboy.) > > I'd appreciate some comments and review before I begin committing bits > of it to freebsd-current. > > The work will be available here, including a brief description of what > is going on: > > http://people.freebsd.org/~adrian/sys/spoof_bind/ Well the for_me rule in ipfw may have similar problems that the uid rules had WRT Lock order. I notice you are using a read lock which may solve that problem. I see you always call ether_demux when a packet is moved up.. hopefully that will also work if an interface is NOT ethernet? hey I know I originally wrote this but it's been a while and I must say I was following tracks made by others, and we are using aonly a subset of possible hardware... > > I'd first like to commit the core changes which introduce a new > compile option, sysctl and IP option to enable a non-local IP address > in bind(). That in itself is enough to at least begin testing under > -current and releng_7. the logical equivalent of this code (not prettied up) has been in Ironport's FreeBSD since 4.x. The code in if_bridge is new as we used the old bridge code, but it 's logically similar. FYI we will probably switch to a single netgraph node that does bridging and filtering combined in 7.x :-) > > The diff against -current for this first phase is available here: > > http://people.freebsd.org/~adrian/sys/spoof_bind/spoof_bind_sys.diff > > I'm currently running just this patch on a machine in the netperf > cluster which is acting as a transparent HTTP interception thing. It > seems to handle "moderate" request rates (~1500 socket creations a > second, ~150mbit). This first patch is pretty straight forward and I'm > reasonably confident that it won't break anything in -current or > releng_7 which isn't already broken. > For others, this is a patch that allows the proxy to be a "bump on the wire" It is proxying between two segments of the same subnet, completely transparently (assuming you do server side spoofing too.) > There are other changes to IPFW and the bridging code which I'll ask > to be reviewed separately. > > Thanks! > > > > Adrian > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Thu Jan 8 21:21:47 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA54C106564A for ; Thu, 8 Jan 2009 21:21:47 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from arcturus.maxiscale.com (arcturus.maxiscale.com [76.231.178.136]) by mx1.freebsd.org (Postfix) with ESMTP id B74ED8FC19 for ; Thu, 8 Jan 2009 21:21:47 +0000 (UTC) (envelope-from psteele@maxiscale.com) X-ASG-Debug-ID: 1231449707-29ef00010000-QdxwpM X-Barracuda-URL: http://10.100.1.25:8000/cgi-bin/mark.cgi Received: from polaris.maxiscale.com (localhost [127.0.0.1]) by arcturus.maxiscale.com (Spam Firewall) with ESMTP id 32982366A8 for ; Thu, 8 Jan 2009 13:21:47 -0800 (PST) Received: from polaris.maxiscale.com (polaris.maxiscale.com [10.100.1.24]) by arcturus.maxiscale.com with ESMTP id V2l3stSxBYDMJ8uK for ; Thu, 08 Jan 2009 13:21:47 -0800 (PST) X-ASG-Whitelist: Client X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-ASG-Orig-Subj: RE: Having problems with limited broadcast Date: Thu, 8 Jan 2009 13:21:46 -0800 Message-ID: <2ACA3DE8F9758A48B8BE2C7A847F91F2479FCE@polaris.maxiscale.com> In-Reply-To: <2ACA3DE8F9758A48B8BE2C7A847F91F2479FB0@polaris.maxiscale.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Having problems with limited broadcast Thread-Index: Aclw3KjZAd4JfFh4Rg2uRWJdMhlnTQA53dHAAASqrpA= References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com><2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com><4964CA2E.5090708@wezel.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FB0@polaris.maxiscale.com> From: "Peter Steele" To: X-Barracuda-Connect: polaris.maxiscale.com[10.100.1.24] X-Barracuda-Start-Time: 1231449707 X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at maxiscale.com Subject: RE: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Jan 2009 21:21:48 -0000 > Thanks for the suggestion though. I'm not familiar with ZeroConf; I'll > check it out. ZeroConf is an interesting concept. Unfortunately it restricts IPs to the 169.254/16 range and it is very likely some of our customers will want to be able to configure our boxes to an IP range of their own choosing. That's the biggest concern we have with this facility. It's definitely attractive, but I don't think we can use unfortunately. From owner-freebsd-net@FreeBSD.ORG Thu Jan 8 21:41:10 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63B72106564A; Thu, 8 Jan 2009 21:41:10 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3A5058FC18; Thu, 8 Jan 2009 21:41:10 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n08LfANW082902; Thu, 8 Jan 2009 21:41:10 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n08LfAfV082898; Thu, 8 Jan 2009 21:41:10 GMT (envelope-from linimon) Date: Thu, 8 Jan 2009 21:41:10 GMT Message-Id: <200901082141.n08LfAfV082898@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/130311: [wlan_xauth] [panic] hostapd restart causing kernel panic X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2009 21:41:11 -0000 Old Synopsis: [wlan_xauth] hostapd restart causing kernel panic New Synopsis: [wlan_xauth] [panic] hostapd restart causing kernel panic Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Thu Jan 8 21:40:59 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=130311 From owner-freebsd-net@FreeBSD.ORG Thu Jan 8 22:11:40 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BCF9106566B for ; Thu, 8 Jan 2009 22:11:40 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gx0-f11.google.com (mail-gx0-f11.google.com [209.85.217.11]) by mx1.freebsd.org (Postfix) with ESMTP id BD7D38FC12 for ; Thu, 8 Jan 2009 22:11:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by gxk4 with SMTP id 4so1085822gxk.19 for ; Thu, 08 Jan 2009 14:11:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=9Eb7lSTKnvDFxGYKBSz+7FKNrq86258k2eOyljWdK3o=; b=XzBpv1A7D/L7AWFj+nerQvZUabP9EIghR8iFbOTZ/WDxzp7/PGWxQjtw1xOJpph4e3 /8YIQNw3/E4nxOwz5FJU5st8vFQmcwALq7sDxU5fNiEyncgcTKjJ1lWO9vqaR4uoedbo 9vqXyPfi/7aQJKndVm/tIv6KijqrMva5siXEE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=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=ch7o0wPsuOefkPHVu1lz0e1p+LWBNH0Q6+/y0WuvJayc3ooDxtr8VEOudIRuZiSvFx O8XttVQhm2Sr3isEpLgSnyuXPUsH5qQ5o/GS7eAO9xhEqiIIxiwUvwAGv9hr/ffhaau5 YEhc4Xju+WvvPT4ydmCU+9YJQM1JeUHNVm4Uk= Received: by 10.150.145.20 with SMTP id s20mr2767870ybd.97.1231452699214; Thu, 08 Jan 2009 14:11:39 -0800 (PST) Received: by 10.151.135.13 with HTTP; Thu, 8 Jan 2009 14:11:39 -0800 (PST) Message-ID: Date: Thu, 8 Jan 2009 17:11:39 -0500 From: "Adrian Chadd" Sender: adrian.chadd@gmail.com To: "Peter Steele" In-Reply-To: <2ACA3DE8F9758A48B8BE2C7A847F91F2479FCE@polaris.maxiscale.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com> <4964CA2E.5090708@wezel.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FB0@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FCE@polaris.maxiscale.com> X-Google-Sender-Auth: 74e25c22d68714bb Cc: freebsd-net@freebsd.org Subject: Re: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Jan 2009 22:11:40 -0000 If this is all going over an L2 LAN, why not do the initial discovery and general configuration exchange over IPv6? :P Link layer network-scope addresses to the rescue. (think: just like apple wireless base stations and MacOSX hosts doing configuration do..) Adrian 2009/1/8 Peter Steele : >> Thanks for the suggestion though. I'm not familiar with ZeroConf; I'll >> check it out. > > ZeroConf is an interesting concept. Unfortunately it restricts IPs to > the 169.254/16 range and it is very likely some of our customers will > want to be able to configure our boxes to an IP range of their own > choosing. That's the biggest concern we have with this facility. It's > definitely attractive, but I don't think we can use unfortunately. > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Thu Jan 8 22:18:16 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 370271065788 for ; Thu, 8 Jan 2009 22:18:16 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.29]) by mx1.freebsd.org (Postfix) with ESMTP id DC33A8FC35 for ; Thu, 8 Jan 2009 22:18:15 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so3879393yxb.13 for ; Thu, 08 Jan 2009 14:18:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=80Wo/mh/oq74xcDIv2CbsZyjzkY160ZJ1hImLQHiDN8=; b=et9oA1nF0Xt07lN8+5PEUMTLSz8SKvWfe3a3NxC1c2u+OgJsBNUPPfMKyUZ1y8ZbZ3 C6xpIsKpUfY7TuqCNM6+GZ66hE3Y4lTOf/ZMT5zE1BKVd/bZSD/1xg/gN6sQPwiKkpHd Itje0PRnZqNGkUjZuF4HWAZmM6SxcryS6naDo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=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=g4BxRg2oT2mrkSpAYgAOQFv7CPBjQf7W1FNVC26aVw91S55UmAdTvzJLH7a8euDFbR ysBlpiZsTrMUPTXEtKBL5qKszyf1dPr+sNUVB7uP7OuDoxXcfb6rvzkZiT5udHeMNZ+1 BIZgcfStJJIToVWadMHc84ca2APfqMGWiKLoI= Received: by 10.151.154.20 with SMTP id g20mr2838153ybo.8.1231453095180; Thu, 08 Jan 2009 14:18:15 -0800 (PST) Received: by 10.151.135.13 with HTTP; Thu, 8 Jan 2009 14:18:15 -0800 (PST) Message-ID: Date: Thu, 8 Jan 2009 17:18:15 -0500 From: "Adrian Chadd" Sender: adrian.chadd@gmail.com To: "Julian Elischer" In-Reply-To: <49666189.9010406@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <49666189.9010406@elischer.org> X-Google-Sender-Auth: 397d36f350beeccf Cc: FreeBSD Net Subject: Re: Julian's source IP address spoofing - code review requested X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Jan 2009 22:18:16 -0000 2009/1/8 Julian Elischer : > I see you always call ether_demux when a packet is moved up.. s/you/you/ :) This is all your stuff IIRC, I just ported and commented as required. > hopefully that will also work if an interface is NOT ethernet? this is why i left the ethernet bridge interception stuff out in a seperate diff. I'll commit it only once I've spoken to bridge-cluey people and have their blessing. > hey I know I originally wrote this but it's been a while and > I must say I was following tracks made by others, and we > are using aonly a subset of possible hardware... Well, its entirely possible this stuff will be deployed in two scenarios: * where its all done at the IP layer, eg policy routing, IPFW * where its being done as part of a transparent ethernet bridge > FYI we will probably switch to a single netgraph node that > does bridging and filtering combined in 7.x :-) That'd certainly be nicer. ;) About the only thing I'm looking to add to this later on is to flesh out IPv6 source address spoofing too, just in case V6 catches on. Adrian From owner-freebsd-net@FreeBSD.ORG Thu Jan 8 22:39:12 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0102D106570C for ; Thu, 8 Jan 2009 22:39:12 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from arcturus.maxiscale.com (arcturus.maxiscale.com [76.231.178.136]) by mx1.freebsd.org (Postfix) with ESMTP id D0D7F8FC2F for ; Thu, 8 Jan 2009 22:39:11 +0000 (UTC) (envelope-from psteele@maxiscale.com) X-ASG-Debug-ID: 1231454349-57d300010000-QdxwpM X-Barracuda-URL: http://10.100.1.25:8000/cgi-bin/mark.cgi Received: from polaris.maxiscale.com (localhost [127.0.0.1]) by arcturus.maxiscale.com (Spam Firewall) with ESMTP id 78424366C0; Thu, 8 Jan 2009 14:39:09 -0800 (PST) Received: from polaris.maxiscale.com (polaris.maxiscale.com [10.100.1.24]) by arcturus.maxiscale.com with ESMTP id XHExhZgw8FYpbsN9; Thu, 08 Jan 2009 14:39:09 -0800 (PST) X-ASG-Whitelist: Client X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-ASG-Orig-Subj: RE: Having problems with limited broadcast Date: Thu, 8 Jan 2009 14:39:07 -0800 Message-ID: <2ACA3DE8F9758A48B8BE2C7A847F91F2479FD9@polaris.maxiscale.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Having problems with limited broadcast Thread-Index: Aclx3hWiEudBfLJiRHilVcw/tD/C1gAAzApQ References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com> <4964CA2E.5090708@wezel.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FB0@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FCE@polaris.maxiscale.com> From: "Peter Steele" To: "Adrian Chadd" X-Barracuda-Connect: polaris.maxiscale.com[10.100.1.24] X-Barracuda-Start-Time: 1231454349 X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at maxiscale.com Cc: freebsd-net@freebsd.org Subject: RE: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Jan 2009 22:39:12 -0000 >If this is all going over an L2 LAN, why not do the initial discovery >and general configuration exchange over IPv6? :P Link layer >network-scope addresses to the rescue. > >(think: just like apple wireless base stations and MacOSX hosts doing >configuration do..) It's really a matter of time. We didn't anticipate limited broadcast being broken in FreeBSD and we're scrambling to come up with a solution. To be quite frank I haven't done anything with IPv6 before so it would be more research to get up to speed on this option. It seems our best option is scapy, which unfortunately I also haven't used before... From owner-freebsd-net@FreeBSD.ORG Thu Jan 8 23:29:56 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92ABB10657C8 for ; Thu, 8 Jan 2009 23:29:56 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 608748FC24 for ; Thu, 8 Jan 2009 23:29:56 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id D99C7204585; Thu, 8 Jan 2009 18:29:55 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 08 Jan 2009 18:29:55 -0500 X-Sasl-enc: +ysqJXadOrPL99N6CcLOOFxh6mbSmaHHustSwGrZoUIt 1231457395 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 471822046A; Thu, 8 Jan 2009 18:29:55 -0500 (EST) Message-ID: <49668C71.4090407@FreeBSD.org> Date: Thu, 08 Jan 2009 23:29:53 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.19 (X11/20090107) MIME-Version: 1.0 To: Peter Steele References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com> <4964CA2E.5090708@wezel.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FB0@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FCE@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FD9@polaris.maxiscale.com> In-Reply-To: <2ACA3DE8F9758A48B8BE2C7A847F91F2479FD9@polaris.maxiscale.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Adrian Chadd Subject: Re: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 08 Jan 2009 23:29:56 -0000 Peter Steele wrote: > ... > It's really a matter of time. We didn't anticipate limited broadcast > being broken in FreeBSD and we're scrambling to come up with a solution. > To be quite frank I haven't done anything with IPv6 before so it would > be more research to get up to speed on this option. It seems our best > option is scapy, which unfortunately I also haven't used before... > It's not broken -- it has always been this way in all BSD derived networking stacks. Limited broadcast addresses just don't contain any information about where the datagram should go, and this is the case in all other implementations. They are similar to multicast addresses in that regard. Linux has a knob SO_BINDTODEVICE which is partly there to workaround this problem, however it isn't the ideal semantic fit. The folk who point out that link-local addresses could be used, have an interesting suggestion which might work for you. thanks BMS From owner-freebsd-net@FreeBSD.ORG Fri Jan 9 00:50:44 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07F8210656C1 for ; Fri, 9 Jan 2009 00:50:44 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from arcturus.maxiscale.com (arcturus.maxiscale.com [76.231.178.136]) by mx1.freebsd.org (Postfix) with ESMTP id CE89B8FC1E for ; Fri, 9 Jan 2009 00:50:43 +0000 (UTC) (envelope-from psteele@maxiscale.com) X-ASG-Debug-ID: 1231462218-281a00030000-QdxwpM X-Barracuda-URL: http://10.100.1.25:8000/cgi-bin/mark.cgi Received: from polaris.maxiscale.com (localhost [127.0.0.1]) by arcturus.maxiscale.com (Spam Firewall) with ESMTP id 6834D36706; Thu, 8 Jan 2009 16:50:20 -0800 (PST) Received: from polaris.maxiscale.com (polaris.maxiscale.com [10.100.1.24]) by arcturus.maxiscale.com with ESMTP id w3zBdFR9GyaLFDIz; Thu, 08 Jan 2009 16:50:18 -0800 (PST) X-ASG-Whitelist: Client X-MimeOLE: Produced By Microsoft Exchange V6.5 x-cr-puzzleid: {3840D320-4CF9-4290-B431-D1ED4D99D21B} MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-class: urn:content-classes:message X-ASG-Orig-Subj: RE: Having problems with limited broadcast Date: Thu, 8 Jan 2009 16:50:01 -0800 Message-ID: <2ACA3DE8F9758A48B8BE2C7A847F91F2479FF9@polaris.maxiscale.com> In-Reply-To: <49668C71.4090407@FreeBSD.org> x-cr-hashedpuzzle: D59s KT72 LL8L LyLu OJHG RXpi Xv4C ZW4F cWk+ cYFG ctlI dLGH dRhv eR8z iAy5 ihff; 3; YQBkAHIAaQBhAG4AQABmAHIAZQBlAGIAcwBkAC4AbwByAGcAOwBiAG0AcwBAAGYAcgBlAGUAYgBzAGQALgBvAHIAZwA7AGYAcgBlAGUAYgBzAGQALQBuAGUAdABAAGYAcgBlAGUAYgBzAGQALgBvAHIAZwA=; Sosha1_v1; 7; {3840D320-4CF9-4290-B431-D1ED4D99D21B}; cABzAHQAZQBlAGwAZQBAAG0AYQB4AGkAcwBjAGEAbABlAC4AYwBvAG0A; Fri, 09 Jan 2009 00:50:01 GMT; UgBFADoAIABIAGEAdgBpAG4AZwAgAHAAcgBvAGIAbABlAG0AcwAgAHcAaQB0AGgAIABsAGkAbQBpAHQAZQBkACAAYgByAG8AYQBkAGMAYQBzAHQA X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Having problems with limited broadcast Thread-Index: Aclx6QVMvIJsjj3fQp2fnDUEhS5j+gACviJA References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com> <4964CA2E.5090708@wezel.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FB0@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FCE@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FD9@polaris.maxiscale.com> <49668C71.4090407@FreeBSD.org> From: "Peter Steele" To: "Bruce M. Simpson" X-Barracuda-Connect: polaris.maxiscale.com[10.100.1.24] X-Barracuda-Start-Time: 1231462222 X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at maxiscale.com Cc: freebsd-net@freebsd.org, Adrian Chadd Subject: RE: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Jan 2009 00:50:44 -0000 > The folk who point out that link-local addresses could be used, have an=20 > interesting suggestion which might work for you. It's definitely interesting, but it is very likely that some of our customers will want to be able to set their own IP ranges and not be limited to 169.254/16. So we need a more generic solution. From owner-freebsd-net@FreeBSD.ORG Fri Jan 9 01:04:21 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54829106566C for ; Fri, 9 Jan 2009 01:04:21 +0000 (UTC) (envelope-from bmw@wezel.com) Received: from tomts20-srv.bellnexxia.net (tomts20.bellnexxia.net [209.226.175.74]) by mx1.freebsd.org (Postfix) with ESMTP id 03C518FC1A for ; Fri, 9 Jan 2009 01:04:20 +0000 (UTC) (envelope-from bmw@wezel.com) Received: from toip4.srvr.bell.ca ([209.226.175.87]) by tomts20-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20090109010420.XCJV1552.tomts20-srv.bellnexxia.net@toip4.srvr.bell.ca> for ; Thu, 8 Jan 2009 20:04:20 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhUFAPMxZklBX3e3/2dsb2JhbACBbM1uhXU Received: from bas2-toronto63-1096775607.dsl.bell.ca (HELO mg-i1200.home.wezel.com) ([65.95.119.183]) by toip4.srvr.bell.ca with ESMTP; 08 Jan 2009 20:13:22 -0500 Message-ID: <4966A283.4070505@wezel.com> Date: Thu, 08 Jan 2009 20:04:03 -0500 From: Bruce Walker User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: Peter Steele References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com> <4964CA2E.5090708@wezel.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FB0@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FCE@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FD9@polaris.maxiscale.com> <49668C71.4090407@FreeBSD.org> In-Reply-To: <49668C71.4090407@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Jan 2009 01:04:21 -0000 Bruce M. Simpson wrote: > > The folk who point out that link-local addresses could be used, have > an interesting suggestion which might work for you. Peter, I understand your issue with the (apparent) restriction of the 169.254/16 range, though I'd point out that the IPv4-LL addressing scheme is considered a fall-back plan by most systems implementors. Your systems could look for DHCP first then failing that, drop back to IPv4-LL and get an address. The picky customers would simply be required to supply a DHCP server. Everyone else presumably doesn't care as long as the boxes can communicate. But there's another useful point to pickup from the ZeroConf stuff. I implemented a small standalone IPv4-LLA daemon using libevent, libnet and libpcap. IPv4-LLA needs to muck around with a completely unaddressed interface (like you are doing with your DHCP-lite), sending and listening-for broadcast and directed ARP packets, per RFC 3927. It was trivial to do this in a completely portable way using libpcap and libnet. I'd highly recommend to you that you link those libraries into your Python DHCP-lite app and you will be able to deploy relatively painlessly on any platform that those libraries are ported to. http://sourceforge.net/projects/pylibpcap/ http://pylibnet.sourceforge.net/ Cheers! -bmw From owner-freebsd-net@FreeBSD.ORG Fri Jan 9 01:08:54 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 15834106566B; Fri, 9 Jan 2009 01:08:54 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id D33E88FC12; Fri, 9 Jan 2009 01:08:53 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 629D7203176; Thu, 8 Jan 2009 20:08:52 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 08 Jan 2009 20:08:52 -0500 X-Sasl-enc: GDZP2x5q3YWdNyhGyCgjSWFGA+hsaCEb7h9iJyEWHMX1 1231463332 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 8FD2328323; Thu, 8 Jan 2009 20:08:51 -0500 (EST) Message-ID: <4966A3A2.7030001@FreeBSD.org> Date: Fri, 09 Jan 2009 01:08:50 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.19 (X11/20090107) MIME-Version: 1.0 To: Peter Steele References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com> <4964CA2E.5090708@wezel.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FB0@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FCE@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FD9@polaris.maxiscale.com> <49668C71.4090407@FreeBSD.org> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FF9@polaris.maxiscale.com> In-Reply-To: <2ACA3DE8F9758A48B8BE2C7A847F91F2479FF9@polaris.maxiscale.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Adrian Chadd , Peter Grehan , "George V. Neville-Neil" Subject: Re: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Jan 2009 01:08:54 -0000 Peter Steele wrote: >> The folk who point out that link-local addresses could be used, have >> > an > >> interesting suggestion which might work for you. >> > > It's definitely interesting, but it is very likely that some of our > customers will want to be able to set their own IP ranges and not be > limited to 169.254/16. So we need a more generic solution. Sounds like it's bpf/pcap city for you guys. A similar bump-in-the-stack to SO_BINDTODEVICE, e.g. let's call it IP_SENDIF has been on the drawing board, but it needs appropriate security screening -- the ability to bypass the forwarding tables, whilst specifying an interface e.g. by index or name, would be desirable only for certain privileged processes. BTW: If you guys are already looking at scapy, you may also wish to give pcs.sourceforge.net a look as an alternative. It is a Python project which I did some hacking on with George Neville-Neill who started it. It has BPF/PCAP support out of the box and has a number of powerful features, including a packet-level expect() facility, which works in a very similar manner to pexpect (Python expect for text streams). I added a scapy-like concatenation syntax ('/' operator) to it as that makes plugging packet chains together that much easier. I have the beginnings of an IGMPv3 test suite in my home repo written using PCS, it uses pcap capture. I imagine a DHCP like protocol could easily be implemented using PCS too. cheers BMS From owner-freebsd-net@FreeBSD.ORG Fri Jan 9 01:19:49 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C644F106564A; Fri, 9 Jan 2009 01:19:49 +0000 (UTC) (envelope-from weongyo@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9D8248FC16; Fri, 9 Jan 2009 01:19:49 +0000 (UTC) (envelope-from weongyo@FreeBSD.org) Received: from freefall.freebsd.org (weongyo@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n091Jnh4039662; Fri, 9 Jan 2009 01:19:49 GMT (envelope-from weongyo@freefall.freebsd.org) Received: (from weongyo@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n091JnYD039658; Fri, 9 Jan 2009 01:19:49 GMT (envelope-from weongyo) Date: Fri, 9 Jan 2009 01:19:49 GMT Message-Id: <200901090119.n091JnYD039658@freefall.freebsd.org> To: weongyo@FreeBSD.org, freebsd-net@FreeBSD.org, weongyo@FreeBSD.org From: weongyo@FreeBSD.org Cc: Subject: Re: kern/130189: [ndis] [patch] if_ndis typo 802.11 mode test X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Jan 2009 01:19:50 -0000 Synopsis: [ndis] [patch] if_ndis typo 802.11 mode test Responsible-Changed-From-To: freebsd-net->weongyo Responsible-Changed-By: weongyo Responsible-Changed-When: Fri Jan 9 01:19:18 UTC 2009 Responsible-Changed-Why: Grab it. http://www.freebsd.org/cgi/query-pr.cgi?pr=130189 From owner-freebsd-net@FreeBSD.ORG Fri Jan 9 01:25:06 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4DC3106566C for ; Fri, 9 Jan 2009 01:25:06 +0000 (UTC) (envelope-from bmw@wezel.com) Received: from tomts13-srv.bellnexxia.net (tomts13-srv.bellnexxia.net [209.226.175.34]) by mx1.freebsd.org (Postfix) with ESMTP id 550A78FC0A for ; Fri, 9 Jan 2009 01:25:06 +0000 (UTC) (envelope-from bmw@wezel.com) Received: from toip6.srvr.bell.ca ([209.226.175.125]) by tomts13-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20090109012505.QZNV1559.tomts13-srv.bellnexxia.net@toip6.srvr.bell.ca> for ; Thu, 8 Jan 2009 20:25:05 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhUFAHg2ZklBX3e3/2dsb2JhbACBbM1ghXU Received: from bas2-toronto63-1096775607.dsl.bell.ca (HELO mg-i1200.home.wezel.com) ([65.95.119.183]) by toip6.srvr.bell.ca with ESMTP; 08 Jan 2009 20:19:23 -0500 Message-ID: <4966A76A.5070409@wezel.com> Date: Thu, 08 Jan 2009 20:24:58 -0500 From: Bruce Walker User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: Peter Steele References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com> <4964CA2E.5090708@wezel.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FB0@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FCE@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FD9@polaris.maxiscale.com> <49668C71.4090407@FreeBSD.org> <4966A283.4070505@wezel.com> In-Reply-To: <4966A283.4070505@wezel.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Jan 2009 01:25:06 -0000 Bruce Walker wrote: > It was trivial to do this in a completely portable way using libpcap > and libnet. Sorry, typo: I actually meant to say libdnet -- a different but similar package. Also with Python bindings. http://libdnet.sourceforge.net/ -bmw From owner-freebsd-net@FreeBSD.ORG Fri Jan 9 04:50:26 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 51130106566C for ; Fri, 9 Jan 2009 04:50:26 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from arcturus.maxiscale.com (arcturus.maxiscale.com [76.231.178.136]) by mx1.freebsd.org (Postfix) with ESMTP id 249E98FC12 for ; Fri, 9 Jan 2009 04:50:25 +0000 (UTC) (envelope-from psteele@maxiscale.com) X-ASG-Debug-ID: 1231476577-383800000000-QdxwpM X-Barracuda-URL: http://10.100.1.25:8000/cgi-bin/mark.cgi Received: from polaris.maxiscale.com (localhost [127.0.0.1]) by arcturus.maxiscale.com (Spam Firewall) with ESMTP id 75F33367D9 for ; Thu, 8 Jan 2009 20:49:37 -0800 (PST) Received: from polaris.maxiscale.com (polaris.maxiscale.com [10.100.1.24]) by arcturus.maxiscale.com with ESMTP id aPGGOhFAwsp5wcG6 for ; Thu, 08 Jan 2009 20:49:37 -0800 (PST) X-ASG-Whitelist: Client X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-ASG-Orig-Subj: RE: Having problems with limited broadcast Date: Thu, 8 Jan 2009 20:49:32 -0800 Message-ID: <2ACA3DE8F9758A48B8BE2C7A847F91F247A00E@polaris.maxiscale.com> In-Reply-To: <4966A283.4070505@wezel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Having problems with limited broadcast Thread-Index: Aclx9oM20hj+ArP2TeaDrQcK2YMA/wAHZuEw References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com> <4964CA2E.5090708@wezel.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FB0@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FCE@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FD9@polaris.maxiscale.com><49668C71.4090407@FreeBSD.org> <4966A283.4070505@wezel.com> From: "Peter Steele" To: "Bruce Walker" X-Barracuda-Connect: polaris.maxiscale.com[10.100.1.24] X-Barracuda-Start-Time: 1231476578 X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at maxiscale.com Cc: freebsd-net@freebsd.org Subject: RE: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Jan 2009 04:50:26 -0000 >Peter, I understand your issue with the (apparent) restriction of the=20 >169.254/16 range, though I'd point out that the IPv4-LL addressing=20 >scheme is considered a fall-back plan by most systems implementors. =20 >Your systems could look for DHCP first then failing that, drop back to >IPv4-LL and get an address. The picky customers would simply be=20 >required to supply a DHCP server. Everyone else presumably doesn't care=20 >as long as the boxes can communicate. I personally like this idea, but I'm not sure I can sell it to the others. Are there any restrictions to these 169.254.x.y addresses? Although our boxes systems operate as a cluster, there do need to be externally addressable. If there are no restrictions in how these link local addresses appear in a company LAN, then I don't think there would be a problem. The question is, if a picky customer doesn't want to use this range, will they be agreeable to providing a DHCP server for our use? The customer often has a lot of leverage in these matters unfortunately. =20 >But there's another useful point to pickup from the ZeroConf stuff. I=20 >implemented a small standalone IPv4-LLA daemon using libevent, libnet=20 >and libpcap. IPv4-LLA needs to muck around with a completely=20 >unaddressed interface (like you are doing with your DHCP-lite), sending >and listening-for broadcast and directed ARP packets, per RFC 3927. It >was trivial to do this in a completely portable way using libpcap and=20 >libnet. I'd highly recommend to you that you link those libraries into >your Python DHCP-lite app and you will be able to deploy relatively=20 >painlessly on any platform that those libraries are ported to. We need broadcast support for both Java and Python and we're currently looking at a relatively simple solution using scapy. If that doesn't work out I'm sure we may have to delve into libnet/libpcap. Thanks for your feedback. Peter From owner-freebsd-net@FreeBSD.ORG Fri Jan 9 04:51:59 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42AAF106566B for ; Fri, 9 Jan 2009 04:51:59 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from arcturus.maxiscale.com (arcturus.maxiscale.com [76.231.178.136]) by mx1.freebsd.org (Postfix) with ESMTP id 1A3CD8FC18 for ; Fri, 9 Jan 2009 04:51:58 +0000 (UTC) (envelope-from psteele@maxiscale.com) X-ASG-Debug-ID: 1231476668-383a00010000-QdxwpM X-Barracuda-URL: http://10.100.1.25:8000/cgi-bin/mark.cgi Received: from polaris.maxiscale.com (localhost [127.0.0.1]) by arcturus.maxiscale.com (Spam Firewall) with ESMTP id AB835367EE; Thu, 8 Jan 2009 20:51:08 -0800 (PST) Received: from polaris.maxiscale.com (polaris.maxiscale.com [10.100.1.24]) by arcturus.maxiscale.com with ESMTP id fQOskRJbWRyoCFiT; Thu, 08 Jan 2009 20:51:08 -0800 (PST) X-ASG-Whitelist: Client X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-ASG-Orig-Subj: RE: Having problems with limited broadcast Date: Thu, 8 Jan 2009 20:51:06 -0800 Message-ID: <2ACA3DE8F9758A48B8BE2C7A847F91F247A00F@polaris.maxiscale.com> In-Reply-To: <4966A3A2.7030001@FreeBSD.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Having problems with limited broadcast Thread-Index: Aclx9uJwPQMj0OHfQYOhgrftiEtbwQAHtp0w References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com> <4964CA2E.5090708@wezel.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FB0@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FCE@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FD9@polaris.maxiscale.com> <49668C71.4090407@FreeBSD.org> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FF9@polaris.maxiscale.com> <4966A3A2.7030001@FreeBSD.org> From: "Peter Steele" To: "Bruce M. Simpson" X-Barracuda-Connect: polaris.maxiscale.com[10.100.1.24] X-Barracuda-Start-Time: 1231476672 X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at maxiscale.com Cc: freebsd-net@freebsd.org, Adrian Chadd , Peter Grehan , "George V. Neville-Neil" Subject: RE: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Jan 2009 04:51:59 -0000 > BTW: If you guys are already looking at scapy, you may also wish to give=20 > pcs.sourceforge.net a look as an alternative. I didn't come across that in my research. I'll have to check it out. Thanks. Peter From owner-freebsd-net@FreeBSD.ORG Fri Jan 9 06:09:54 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1AC99106564A for ; Fri, 9 Jan 2009 06:09:54 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id DD9AF8FC16 for ; Fri, 9 Jan 2009 06:09:53 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 6BEB7203704; Fri, 9 Jan 2009 01:09:53 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 09 Jan 2009 01:09:53 -0500 X-Sasl-enc: hvIwoIx3shC69L70BbrykTFimrkFyL+XcgQ/9g2tmiP1 1231481393 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id CD1379E42; Fri, 9 Jan 2009 01:09:52 -0500 (EST) Message-ID: <4966EA2F.5040603@FreeBSD.org> Date: Fri, 09 Jan 2009 06:09:51 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.19 (X11/20090107) MIME-Version: 1.0 To: Peter Steele References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com> <4964CA2E.5090708@wezel.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FB0@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FCE@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FD9@polaris.maxiscale.com><49668C71.4090407@FreeBSD.org> <4966A283.4070505@wezel.com> <2ACA3DE8F9758A48B8BE2C7A847F91F247A00E@polaris.maxiscale.com> In-Reply-To: <2ACA3DE8F9758A48B8BE2C7A847F91F247A00E@polaris.maxiscale.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Bruce Walker Subject: Re: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Jan 2009 06:09:54 -0000 Peter Steele wrote: > ... > I personally like this idea, but I'm not sure I can sell it to the > others. Are there any restrictions to these 169.254.x.y addresses? > 169.254.0.0/16 must never appear outside a link -- it is strictly scoped to that link. Currently the IPv4 BSD stack has no concept of link-scoped addresses, but IPv6 does. Link is a realized concept there because of KAME's support for the % syntax. Internally, interface indexes get used. In practice this shouldn't be an issue as long as you can guarantee different addresses are used for the 169.254.0.0/16 block on each interface, however, it would mean any app using sockets would need to explicitly bind to the local address to ensure the correct interface is used. Furthermore, we effectively need to be able to support multiple next-hops for the 169.254.0.0/16 prefix, otherwise we can support only one such interface w/o significant kernel code rewrites. So, really, LL may not buy you anything at all, and it's likely you need to go straight to pcap for your app. These restrictions have existed for years, and the fact that they haven't been addressed has largely been because there has been no community strategy to deal with it. I speculate some BSD-using organisations might have already solved these problems, however, without evidence (and code sharing), that's pure speculation. cheers BMS From owner-freebsd-net@FreeBSD.ORG Fri Jan 9 06:14:08 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98CA81065673 for ; Fri, 9 Jan 2009 06:14:08 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 67F1E8FC18 for ; Fri, 9 Jan 2009 06:14:08 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 0A507204AA1; Fri, 9 Jan 2009 01:14:08 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 09 Jan 2009 01:14:08 -0500 X-Sasl-enc: K+rRq60+02j+AtyIpjfolcx5TpA43mOFLHo5Jas4KDqN 1231481647 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 788573685E; Fri, 9 Jan 2009 01:14:07 -0500 (EST) Message-ID: <4966EB2E.7010301@FreeBSD.org> Date: Fri, 09 Jan 2009 06:14:06 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.19 (X11/20090107) MIME-Version: 1.0 To: Peter Steele References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com> <4964CA2E.5090708@wezel.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FB0@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FCE@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FD9@polaris.maxiscale.com><49668C71.4090407@FreeBSD.org> <4966A283.4070505@wezel.com> <2ACA3DE8F9758A48B8BE2C7A847F91F247A00E@polaris.maxiscale.com> <4966EA2F.5040603@FreeBSD.org> In-Reply-To: <4966EA2F.5040603@FreeBSD.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Bruce Walker Subject: Re: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Jan 2009 06:14:09 -0000 Bruce M. Simpson wrote: > Peter Steele wrote: >> ... >> I personally like this idea, but I'm not sure I can sell it to the >> others. Are there any restrictions to these 169.254.x.y addresses? >> > > 169.254.0.0/16 must never appear outside a link -- it is strictly > scoped to that link. P.S. I checked in a change to ip_forward() a while back which enforces this, as forwarding such traffic between interfaces without NATting it or otherwise proxying it is a really bad idea (and also breaks the IPv4 LL RFC). From owner-freebsd-net@FreeBSD.ORG Fri Jan 9 07:40:49 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 728561065670; Fri, 9 Jan 2009 07:40:49 +0000 (UTC) (envelope-from prvs=julian=25380973a@elischer.org) Received: from smtp-outbound.ironport.com (smtp-outbound.ironport.com [63.251.108.112]) by mx1.freebsd.org (Postfix) with ESMTP id 53D6A8FC17; Fri, 9 Jan 2009 07:40:49 +0000 (UTC) (envelope-from prvs=julian=25380973a@elischer.org) Received: from unknown (HELO julian-mac.elischer.org) ([10.251.60.63]) by smtp-outbound.ironport.com with ESMTP; 08 Jan 2009 23:12:41 -0800 Message-ID: <4966F8E9.90002@elischer.org> Date: Thu, 08 Jan 2009 23:12:41 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: "Bruce M. Simpson" References: <2ACA3DE8F9758A48B8BE2C7A847F91F2479DF2@polaris.maxiscale.com> <28b9b4180901070039x27a25bb4m6b50c8bfae63e0af@mail.gmail.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479E9A@polaris.maxiscale.com> <4964CA2E.5090708@wezel.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FB0@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FCE@polaris.maxiscale.com> <2ACA3DE8F9758A48B8BE2C7A847F91F2479FD9@polaris.maxiscale.com><49668C71.4090407@FreeBSD.org> <4966A283.4070505@wezel.com> <2ACA3DE8F9758A48B8BE2C7A847F91F247A00E@polaris.maxiscale.com> <4966EA2F.5040603@FreeBSD.org> In-Reply-To: <4966EA2F.5040603@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Peter Steele , Bruce Walker Subject: Re: Having problems with limited broadcast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Jan 2009 07:40:50 -0000 Bruce M. Simpson wrote: > Peter Steele wrote: >> ... >> I personally like this idea, but I'm not sure I can sell it to the >> others. Are there any restrictions to these 169.254.x.y addresses? >> > > 169.254.0.0/16 must never appear outside a link -- it is strictly scoped > to that link. > > Currently the IPv4 BSD stack has no concept of link-scoped addresses, > but IPv6 does. Link is a realized concept there because of KAME's > support for the % syntax. Internally, interface indexes get used. > > In practice this shouldn't be an issue as long as you can guarantee > different addresses are used for the 169.254.0.0/16 block on each > interface, however, it would mean any app using sockets would need to > explicitly bind to the local address to ensure the correct interface is > used. Furthermore, we effectively need to be able to support multiple > next-hops for the 169.254.0.0/16 prefix, otherwise we can support only > one such interface w/o significant kernel code rewrites. we now have multiple routing tables, multiple default routes, and per interface arp tables, so we can now do more of this than before. we can now support two interfaces with different instantiations of the same range by assigning them only in one routing table each. With Vimage you'll be able to do more.... > > So, really, LL may not buy you anything at all, and it's likely you need > to go straight to pcap for your app. These restrictions have existed for > years, and the fact that they haven't been addressed has largely been > because there has been no community strategy to deal with it. I > speculate some BSD-using organisations might have already solved these > problems, however, without evidence (and code sharing), that's pure > speculation. > > cheers > BMS > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Fri Jan 9 08:48:47 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84637106564A for ; Fri, 9 Jan 2009 08:48:47 +0000 (UTC) (envelope-from Matthias.Apitz@oclc.org) Received: from mail.pica.nl (mail.pica.nl [192.87.44.30]) by mx1.freebsd.org (Postfix) with ESMTP id 218838FC1D for ; Fri, 9 Jan 2009 08:48:46 +0000 (UTC) (envelope-from Matthias.Apitz@oclc.org) Received: from rebelion.Sisis.de ([10.0.1.29]) by mail.pica.nl with Microsoft SMTPSVC(6.0.3790.3959); Fri, 9 Jan 2009 09:36:43 +0100 Received: (from guru@localhost) by rebelion.Sisis.de (8.14.2/8.13.8/Submit) id n098agSL007779 for freebsd-net@freebsd.org; Fri, 9 Jan 2009 09:36:42 +0100 (CET) (envelope-from matthias.apitz@oclc.org) X-Authentication-Warning: rebelion.Sisis.de: guru set sender to matthias.apitz@oclc.org using -f Date: Fri, 9 Jan 2009 09:36:42 +0100 From: Matthias Apitz To: freebsd-net@freebsd.org Message-ID: <20090109083642.GA7507@rebelion.Sisis.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.0-STABLE (i386) X-OriginalArrivalTime: 09 Jan 2009 08:36:43.0849 (UTC) FILETIME=[66B12B90:01C97235] Subject: FreeBSD 7.0R && ADSL X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jan 2009 08:48:47 -0000 Hello, I've at home a connection of ISDN-BRI and ADSL to my phone/Internet provider; BRI and ADSL get splitted in a so called ISDN-splitter, from which a line goes to a DSL modem (Thomson speedTouch 536i) which is connected via Ethernet to a WLAN/WAN router (SMCWBR14-G2). Actually I have the problem that DSL is not connecting (while BRI is fine). The WLAN of the router is fine too, i.e. I can connect to the router management interface (HTTP), but this does not give much help on trouble-shooting. I have had this already sometimes in the past and I want to nail this down and kicking out the WLAN/WAN router, connecting my FreeBSD laptop directly to the DSL modem. The router has a configured PPPoE connection for the WAN interface. What kind of software I could use in FreeBSD? There is some port net/rp-pppoe but the man pages speaks about incoming connections? What else? I'm hoping that with better log files directly on the FreeBSD side I can figure out what's wrong with my DSL line/provider/modem? Thx matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ SPAMer of the year: Subject: Alle Software ist Deutsche Sprachen >From: -40 % die Neujahrsaktion From owner-freebsd-net@FreeBSD.ORG Fri Jan 9 09:27:31 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CB38106564A; Fri, 9 Jan 2009 09:27:31 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.131.111.2]) by mx1.freebsd.org (Postfix) with ESMTP id CB6038FC14; Fri, 9 Jan 2009 09:27:30 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from acrux.dbai.tuwien.ac.at (acrux [128.131.111.60]) by vexpert.dbai.tuwien.ac.at (Postfix) with ESMTP id 94FF13910A; Fri, 9 Jan 2009 10:27:28 +0100 (CET) Received: by acrux.dbai.tuwien.ac.at (Postfix, from userid 1203) id 09C5C10059; Fri, 9 Jan 2009 10:27:29 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by acrux.dbai.tuwien.ac.at (Postfix) with ESMTP id EB7F310054; Fri, 9 Jan 2009 10:27:29 +0100 (CET) Date: Fri, 9 Jan 2009 10:27:29 +0100 (CET) From: Gerald Pfeifer To: "Li, Qing" In-Reply-To: Message-ID: References: <20081227202117.F3B14341A3@cavin02.kulnet.kuleuven.ac.be><200812281613.49404.tijl@ulyssis.org> User-Agent: Alpine 1.99 (LSU 1142 2008-08-13) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Tijl Coosemans , freebsd-net@freebsd.org, freebsd-current@freebsd.org, Qing Li Subject: RE: HEADSUP: arp-v2 has been committed X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jan 2009 09:27:31 -0000 On Tue, 30 Dec 2008, Li, Qing wrote: > I don't think we can provide binary compatibility without putting > back RTF_LLINFO exactly as it was. My preference is to continue down > the new path without RTF_LLINFO. So, you are saying that applications built on FreeBSD 7 or earlier that use RTF_LLINFO will no longer work properly on FreeBSD 8 after your change? Ignoring everything else, that would be a killer and the one reason to definitely change the current situation. Otherwise, ISVs will need two builds, one for FreeBSD 7 and earlier and one for FreeBSD 8, and believe me, that is bad, bad, bad. Or rather: unlikely. (GNU/Linux distributions do provide this level of compatibility.) > We still have some time before the 8.0 release. It's straightforward > for me to retain some of the RTF_LLINFO support in the new kernel if > and when the situation becomes necessary. Sounds like that is the case? > Since the affected ports now have the conditional code around > RTF_LLINFO, the updates would allow these ports to compile in > both -current and in the previous releases. emulators/wine still is broken, and upstream Wine has not accepted the patch yet. I believe one reason likely is the above, and the fact that this may break commercial builds of Wine. How are you going to address this? Gerald -- Gerald (Jerry) Pfeifer gerald@pfeifer.com http://www.pfeifer.com/gerald/ From owner-freebsd-net@FreeBSD.ORG Fri Jan 9 19:59:36 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3FEA106566C; Fri, 9 Jan 2009 19:59:36 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 929068FC1B; Fri, 9 Jan 2009 19:59:36 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id E0714202CB9; Fri, 9 Jan 2009 14:59:35 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 09 Jan 2009 14:59:35 -0500 X-Sasl-enc: XYu0vKKq0mcv/M8jY01pTgWfONsqV96R9JRsGBaQX4Y4 1231531175 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id D66D62A0A0; Fri, 9 Jan 2009 14:59:34 -0500 (EST) Message-ID: <4967ACA5.6080502@incunabulum.net> Date: Fri, 09 Jan 2009 19:59:33 +0000 From: Bruce Simpson User-Agent: Thunderbird 2.0.0.19 (X11/20081209) MIME-Version: 1.0 To: Gerald Pfeifer References: <20081227202117.F3B14341A3@cavin02.kulnet.kuleuven.ac.be><200812281613.49404.tijl@ulyssis.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Tijl Coosemans , "Li, Qing" , freebsd-current@freebsd.org, Qing Li , freebsd-net@freebsd.org Subject: Re: HEADSUP: arp-v2 has been committed X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jan 2009 19:59:37 -0000 +1 for introducing RTF_LLINFO backwards compatibility. I had to sneak in a fix to XORP and pretty much broke release protocol to do so. From owner-freebsd-net@FreeBSD.ORG Sat Jan 10 08:57:43 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42997106566C for ; Sat, 10 Jan 2009 08:57:43 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from mail.giulioferro.it (mail.giulioferro.it [85.18.102.52]) by mx1.freebsd.org (Postfix) with ESMTP id 0102A8FC18 for ; Sat, 10 Jan 2009 08:57:42 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from localhost (localhost [127.0.0.1]) by mail.giulioferro.it (Postfix) with ESMTP id 80DE633C47 for ; Sat, 10 Jan 2009 09:41:43 +0100 (CET) X-Virus-Scanned: amavisd-new at giulioferro.it Received: from mail.giulioferro.it ([127.0.0.1]) by localhost (aurynwork1sv1.giulioferro.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 51IltldMeBOv for ; Sat, 10 Jan 2009 09:41:40 +0100 (CET) Received: from aurynmob2.giulioferro.it (mail.zirakzigil.org [82.63.178.63]) (Authenticated sender: gferro@giulioferro.it) by mail.giulioferro.it (Postfix) with ESMTP id DBFCE33C39 for ; Sat, 10 Jan 2009 09:41:40 +0100 (CET) Message-ID: <49685F15.7080605@zirakzigil.org> Date: Sat, 10 Jan 2009 09:40:53 +0100 From: Giulio Ferro User-Agent: Thunderbird 2.0.0.17 (X11/20081018) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: NATT patch on current X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jan 2009 08:57:43 -0000 I just wanted to report that the nat-traversal patch on HEAD 2008-03-19 fails to apply cleanly. The problem is in the file ipsec.c lines 1847, 1870 Any news for the natt integration in CURRENT? Thanks. From owner-freebsd-net@FreeBSD.ORG Sat Jan 10 09:13:47 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3DEBF1065670 for ; Sat, 10 Jan 2009 09:13:47 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id BEFFE8FC0C for ; Sat, 10 Jan 2009 09:13:46 +0000 (UTC) (envelope-from mav@FreeBSD.org) X-Spam-Flag: SKIP X-Spam-Yversion: Spamooborona-2.1.0 Received: from [212.86.226.226] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPSA id 231297544; Sat, 10 Jan 2009 11:13:45 +0200 Message-ID: <496866CE.7050707@FreeBSD.org> Date: Sat, 10 Jan 2009 11:13:50 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.17 (X11/20081029) MIME-Version: 1.0 To: Matthias Apitz References: <1231503783.00057946.1231491001@10.7.7.3> In-Reply-To: <1231503783.00057946.1231491001@10.7.7.3> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: FreeBSD 7.0R && ADSL X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jan 2009 09:13:47 -0000 Matthias Apitz wrote: > What kind of software I could use in FreeBSD? There is some port > net/rp-pppoe but the man pages speaks about incoming connections? > What else? net/mpd5 -- Alexander Motin From owner-freebsd-net@FreeBSD.ORG Sat Jan 10 10:04:00 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56B79106566C for ; Sat, 10 Jan 2009 10:04:00 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from smtp.zeninc.net (smtp.zeninc.net [80.67.176.25]) by mx1.freebsd.org (Postfix) with ESMTP id 1784C8FC18 for ; Sat, 10 Jan 2009 10:03:59 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from albator.zen.inc (albator.zen.inc [192.168.1.5]) by smtp.zeninc.net (smtpd) with ESMTP id B877E2798B8; Sat, 10 Jan 2009 11:03:57 +0100 (CET) Received: by albator.zen.inc (Postfix, from userid 1000) id A1FEB731C7; Sat, 10 Jan 2009 11:03:57 +0100 (CET) Date: Sat, 10 Jan 2009 11:03:57 +0100 From: VANHULLEBUS Yvan To: Giulio Ferro Message-ID: <20090110100357.GB2718@zeninc.net> References: <49685F15.7080605@zirakzigil.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49685F15.7080605@zirakzigil.org> User-Agent: All mail clients suck. This one just sucks less. Cc: freebsd-net@freebsd.org Subject: Re: NATT patch on current X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jan 2009 10:04:00 -0000 Hi. On Sat, Jan 10, 2009 at 09:40:53AM +0100, Giulio Ferro wrote: > I just wanted to report that the nat-traversal patch on HEAD 2008-03-19 > fails to apply cleanly. > The problem is in the file ipsec.c lines 1847, 1870 > > Any news for the natt integration in CURRENT? Thanks for the report. I'm currently working on cleaning the PFKey part of the patch (available on Perforce if you're interested, and I hope our tests to be ok in a few days, so I'll send kernel+userland patch for public test/review), so I don't use anymore the public version of the patch for TRUNK. I'll be mostly AFK for the next 2-3 days, but I'll try to find quickly some time to update the public patch soon. Yvan. From owner-freebsd-net@FreeBSD.ORG Sat Jan 10 10:25:07 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FAC5106566B for ; Sat, 10 Jan 2009 10:25:07 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id EA7D28FC12 for ; Sat, 10 Jan 2009 10:25:06 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (amavis.str.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 235DA41C670; Sat, 10 Jan 2009 11:25:06 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([62.111.66.27]) by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id VkwgntZv2llL; Sat, 10 Jan 2009 11:25:05 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id BF12241C667; Sat, 10 Jan 2009 11:25:05 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 1A48C4448D5; Sat, 10 Jan 2009 10:24:08 +0000 (UTC) Date: Sat, 10 Jan 2009 10:24:07 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: VANHULLEBUS Yvan In-Reply-To: <20090110100357.GB2718@zeninc.net> Message-ID: <20090110102213.Y45399@maildrop.int.zabbadoz.net> References: <49685F15.7080605@zirakzigil.org> <20090110100357.GB2718@zeninc.net> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, Giulio Ferro Subject: Re: NATT patch on current X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jan 2009 10:25:07 -0000 On Sat, 10 Jan 2009, VANHULLEBUS Yvan wrote: Hi, > On Sat, Jan 10, 2009 at 09:40:53AM +0100, Giulio Ferro wrote: >> I just wanted to report that the nat-traversal patch on HEAD 2008-03-19 >> fails to apply cleanly. >> The problem is in the file ipsec.c lines 1847, 1870 >> >> Any news for the natt integration in CURRENT? > > Thanks for the report. > I'm currently working on cleaning the PFKey part of the patch > (available on Perforce if you're interested, and I hope our tests to > be ok in a few days, so I'll send kernel+userland patch for public > test/review), so I don't use anymore the public version of the patch > for TRUNK. > > I'll be mostly AFK for the next 2-3 days, but I'll try to find quickly > some time to update the public patch soon. There is more to the patch and current: it failes in in_pcb.h now as well -- there is a 0x2000 (or 0x1000) that is officially used now. I wondered if rrs' generic udp tunnel hack would apply to this as well but I haven't looked at the code yet. /bz -- Bjoern A. Zeeb The greatest risk is not taking one. From owner-freebsd-net@FreeBSD.ORG Sat Jan 10 11:46:23 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 413101065695 for ; Sat, 10 Jan 2009 11:46:23 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from mail.giulioferro.it (mail.giulioferro.it [85.18.102.52]) by mx1.freebsd.org (Postfix) with ESMTP id EDFCD8FC0C for ; Sat, 10 Jan 2009 11:46:22 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from localhost (localhost [127.0.0.1]) by mail.giulioferro.it (Postfix) with ESMTP id 60A4E33C8E; Sat, 10 Jan 2009 12:47:06 +0100 (CET) X-Virus-Scanned: amavisd-new at giulioferro.it Received: from mail.giulioferro.it ([127.0.0.1]) by localhost (aurynwork1sv1.giulioferro.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n4sK2yINySlh; Sat, 10 Jan 2009 12:47:03 +0100 (CET) Received: from aurynmob2.giulioferro.it (mail.zirakzigil.org [82.63.178.63]) (Authenticated sender: gferro@giulioferro.it) by mail.giulioferro.it (Postfix) with ESMTP id 8848C33C18; Sat, 10 Jan 2009 12:47:03 +0100 (CET) Message-ID: <49688A88.4080503@zirakzigil.org> Date: Sat, 10 Jan 2009 12:46:16 +0100 From: Giulio Ferro User-Agent: Thunderbird 2.0.0.17 (X11/20081018) MIME-Version: 1.0 To: VANHULLEBUS Yvan References: <49685F15.7080605@zirakzigil.org> <20090110100357.GB2718@zeninc.net> In-Reply-To: <20090110100357.GB2718@zeninc.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: NATT patch on current X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jan 2009 11:46:23 -0000 VANHULLEBUS Yvan wrote: > Hi. > > On Sat, Jan 10, 2009 at 09:40:53AM +0100, Giulio Ferro wrote: > >> I just wanted to report that the nat-traversal patch on HEAD 2008-03-19 >> fails to apply cleanly. >> The problem is in the file ipsec.c lines 1847, 1870 >> >> Any news for the natt integration in CURRENT? >> > > Thanks for the report. > I'm currently working on cleaning the PFKey part of the patch > (available on Perforce if you're interested, and I hope our tests to > be ok in a few days, so I'll send kernel+userland patch for public > test/review), so I don't use anymore the public version of the patch > for TRUNK. > > I'll be mostly AFK for the next 2-3 days, but I'll try to find quickly > some time to update the public patch soon. > > Thanks, looking forward to it... :-) From owner-freebsd-net@FreeBSD.ORG Sat Jan 10 11:55:03 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 981981065675 for ; Sat, 10 Jan 2009 11:55:03 +0000 (UTC) (envelope-from skip@menantico.com) Received: from vms173007pub.verizon.net (vms173007pub.verizon.net [206.46.173.7]) by mx1.freebsd.org (Postfix) with ESMTP id E88288FC0C for ; Sat, 10 Jan 2009 11:55:02 +0000 (UTC) (envelope-from skip@menantico.com) Received: from mx.menantico.com ([96.235.133.57]) by vms173007.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0KD900HX34WYWMT7@vms173007.mailsrvcs.net> for freebsd-net@freebsd.org; Sat, 10 Jan 2009 04:53:27 -0600 (CST) Date: Sat, 10 Jan 2009 05:54:56 -0500 From: Skip Ford In-reply-to: <20090109083642.GA7507@rebelion.Sisis.de> To: Matthias Apitz Message-id: <20090110105455.GA932@menantico.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline References: <20090109083642.GA7507@rebelion.Sisis.de> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org Subject: Re: FreeBSD 7.0R && ADSL X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jan 2009 11:55:03 -0000 Matthias Apitz wrote: > What kind of software I could use in FreeBSD? There is some port > net/rp-pppoe but the man pages speaks about incoming connections? > What else? Are you having problems using ppp(8)? PPPoE has been just another dialup connection for years. Example configurations are available in /usr/share/examples/ppp. If you really want a port, net/mpd is the way to go. ppp(8) is userland while mpd is kernel. I wish it was in base. -- Skip From owner-freebsd-net@FreeBSD.ORG Sat Jan 10 15:35:43 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31BD6106566C for ; Sat, 10 Jan 2009 15:35:43 +0000 (UTC) (envelope-from matthias.apitz@oclc.org) Received: from hunter.Sisis.de (hunter.sisis.de [193.31.11.194]) by mx1.freebsd.org (Postfix) with ESMTP id 8E22A8FC14 for ; Sat, 10 Jan 2009 15:35:42 +0000 (UTC) (envelope-from matthias.apitz@oclc.org) Received: (from mail@localhost) by hunter.Sisis.de (8.8.8/8.8.8) id QAA13482; Sat, 10 Jan 2009 16:16:49 +0100 (CET) (envelope-from matthias.apitz@oclc.org) Received: from ppp-88-217-59-59.dynamic.mnet-online.de(88.217.59.59) by hunter.Sisis.de via smap (V2.1) id xma013442; Sat, 10 Jan 09 16:16:28 +0100 Received: (from guru@localhost) by rebelion.Sisis.de (8.14.2/8.13.8/Submit) id n0AFPVlw033291; Sat, 10 Jan 2009 16:25:31 +0100 (CET) (envelope-from matthias.apitz@oclc.org) X-Authentication-Warning: rebelion.Sisis.de: guru set sender to matthias.apitz@oclc.org using -f Date: Sat, 10 Jan 2009 16:25:31 +0100 From: Matthias Apitz To: Skip Ford Message-ID: <20090110152531.GA32657@rebelion.Sisis.de> References: <20090109083642.GA7507@rebelion.Sisis.de> <20090110105455.GA932@menantico.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20090110105455.GA932@menantico.com> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.0-STABLE (i386) Cc: freebsd-net@freebsd.org Subject: Re: FreeBSD 7.0R && ADSL X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jan 2009 15:35:43 -0000 El día Saturday, January 10, 2009 a las 05:54:56AM -0500, Skip Ford escribió: > Matthias Apitz wrote: > > What kind of software I could use in FreeBSD? There is some port > > net/rp-pppoe but the man pages speaks about incoming connections? > > What else? > > Are you having problems using ppp(8)? PPPoE has been just another > dialup connection for years. Example configurations are available in > /usr/share/examples/ppp. > > If you really want a port, net/mpd is the way to go. ppp(8) is userland > while mpd is kernel. I wish it was in base. Thanks for all the hints. The problem was that for many years I have only used 'normal' pppd connections (over modems, ISDN or UMTS), but never PPPoE. So I went to the ports and did search 'name=pppoe' and ended up in net/rp-pppoe and was confused. It seems that just ppp(8) is what I have to use. Thx again. matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ SPAMer of the year: Subject: Alle Software ist Deutsche Sprachen >From: -40 % die Neujahrsaktion From owner-freebsd-net@FreeBSD.ORG Sat Jan 10 21:15:26 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54BFA106566C for ; Sat, 10 Jan 2009 21:15:26 +0000 (UTC) (envelope-from skip@menantico.com) Received: from vms173003pub.verizon.net (vms173003pub.verizon.net [206.46.173.3]) by mx1.freebsd.org (Postfix) with ESMTP id 35FAD8FC14 for ; Sat, 10 Jan 2009 21:15:26 +0000 (UTC) (envelope-from skip@menantico.com) Received: from mx.menantico.com ([96.235.133.57]) by vms173003.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0KD90043FX4G3ACI@vms173003.mailsrvcs.net> for freebsd-net@freebsd.org; Sat, 10 Jan 2009 15:02:45 -0600 (CST) Date: Sat, 10 Jan 2009 16:02:50 -0500 From: Skip Ford In-reply-to: <20090110152531.GA32657@rebelion.Sisis.de> To: Matthias Apitz Message-id: <20090110210250.GA894@menantico.com> MIME-version: 1.0 Content-type: text/plain; charset=unknown-8bit Content-transfer-encoding: 8BIT Content-disposition: inline References: <20090109083642.GA7507@rebelion.Sisis.de> <20090110105455.GA932@menantico.com> <20090110152531.GA32657@rebelion.Sisis.de> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org Subject: Re: FreeBSD 7.0R && ADSL X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jan 2009 21:15:26 -0000 Matthias Apitz wrote: > El día Saturday, January 10, 2009 a las 05:54:56AM -0500, Skip Ford escribió: > > Matthias Apitz wrote: > > > What kind of software I could use in FreeBSD? There is some port > > > net/rp-pppoe but the man pages speaks about incoming connections? > > > What else? > > > > Are you having problems using ppp(8)? PPPoE has been just another > > dialup connection for years. Example configurations are available in > > /usr/share/examples/ppp. > > > > If you really want a port, net/mpd is the way to go. ppp(8) is userland > > while mpd is kernel. I wish it was in base. > > Thanks for all the hints. The problem was that for many years I have > only used 'normal' pppd connections (over modems, ISDN or UMTS), but > never PPPoE. So I went to the ports and did search 'name=pppoe' and > ended up in net/rp-pppoe and was confused. It seems that just ppp(8) is > what I have to use. Thx again. Yeah, pppd(8) doesn't do PPPoE AFAIK. In addition to the examples I already posted, there's a PPPoE section in the handbook which covers everything instead of just ppp.conf: http://www.freebsd.org/doc/en/books/handbook/pppoe.html Good luck. -- Skip