From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 29 05:56:28 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 62E223BA for ; Mon, 29 Jul 2013 05:56:28 +0000 (UTC) (envelope-from cochard@gmail.com) Received: from mail-ve0-x22d.google.com (mail-ve0-x22d.google.com [IPv6:2607:f8b0:400c:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 24CBC2CA5 for ; Mon, 29 Jul 2013 05:56:28 +0000 (UTC) Received: by mail-ve0-f173.google.com with SMTP id jw11so2609093veb.18 for ; Sun, 28 Jul 2013 22:56:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; bh=999tQQa61GB1DveTJshL3NParfkxHhzE7Hl7m8ZTNH4=; b=SmJ5V4U5uZwaRYdK5KZq/XgggTYwexKwaWkIjCNTo1jEFg7K9JyqFgVs2ki3wLVRGL Oa+Wk/nYsEPI+A31xFFvkNoscFP8vdzD8iA9cmaUUoZ7fiGjJrA8V6mUnKu9/6/77AKm KQL8EV9EXBKj/LVcZXOxRyaUVeBhjlQiBZ+JFKy1xthsacB1vC6NzHrapHBsyt53L9yK GvImYLIK6xIiXJNm7EMQrvqQdDhAnzykNH3RIQChQDTW9NVdqfCdtXomHVeJrihKDh1z O7KfdKfYFlo7Pwu7c9KUCt3/KqqGAk9kxbXcoSzjUXs7h414qW6yeDg0Gn7CIm0PIc8W rNpQ== X-Received: by 10.58.207.195 with SMTP id ly3mr25101886vec.77.1375077386720; Sun, 28 Jul 2013 22:56:26 -0700 (PDT) MIME-Version: 1.0 Sender: cochard@gmail.com Received: by 10.58.145.101 with HTTP; Sun, 28 Jul 2013 22:56:06 -0700 (PDT) From: =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?= Date: Mon, 29 Jul 2013 07:56:06 +0200 X-Google-Sender-Auth: K_5leEpHm6mJTeWjwp-Ooqd0-EU Message-ID: Subject: How to display 256 colors on the vga console shell ? To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jul 2013 05:56:28 -0000 Hi, I'm trying to display 256 colors on my vga console but didn't reach to display more than 16 colors. I'm using this perl script for my test: http://www.robmeerman.co.uk/_media/unix/256colors2.pl I'm using -current (r253755) with the default xterm for all ttyv. I've tried different vidcontrol mode (MODE_280, MODE 279, MODE_261) but still 16 colors for each try. The splash screen and the screen saver (rain_saver.ko) are able to display more than 16 colors on my laptop but why not the console ? Thanks, Olivier From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 29 10:45:32 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id AAC619E0 for ; Mon, 29 Jul 2013 10:45:32 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 732702C98 for ; Mon, 29 Jul 2013 10:45:32 +0000 (UTC) Received: from Mail-PC.tdx.co.uk (storm.tdx.co.uk [62.13.130.251]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id r6TAjPTp095469 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 29 Jul 2013 11:45:25 +0100 (BST) Date: Mon, 29 Jul 2013 11:45:26 +0100 From: Karl Pielorz To: freebsd-hackers@freebsd.org Subject: kldload ipfw, with IPFIREWALL_DEFAULT_TO_ACCEPT Message-ID: <1D6BF13DFC536AFC94EC6D64@Mail-PC.tdx.co.uk> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jul 2013 10:45:32 -0000 Hi, I've got a number of 9.1 boxes, where we need to enable ipfw (by kldload'ing it). I'm sure I saw a while ago a sysctl that would change the default ipfw config from 'deny all' to 'allow all' - even for a kldload? But I can't find it now. The boxes have a number of CARP interfaces on them - and I don't want them getting blocked during the firewall load - as there's a chance they'll flip to MASTER etc. [as well as cutting everyone on, and going through the box off - even if only momentarily]. So if there's a sysctl for changing the default ipfw behaviour on loading, or someway of getting the ethernet interfaces to 'opt out' of ipfw (until I've added the 'allow all from any to any' rule) - that'd be great, Thanks, -Karl From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 29 11:02:46 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id AEBD6D8B for ; Mon, 29 Jul 2013 11:02:46 +0000 (UTC) (envelope-from se@freebsd.org) Received: from nm5-vm0.bullet.mail.ird.yahoo.com (nm5-vm0.bullet.mail.ird.yahoo.com [77.238.189.207]) by mx1.freebsd.org (Postfix) with SMTP id 0A48D2D30 for ; Mon, 29 Jul 2013 11:02:45 +0000 (UTC) Received: from [77.238.189.237] by nm5.bullet.mail.ird.yahoo.com with NNFMP; 29 Jul 2013 11:02:39 -0000 Received: from [46.228.39.94] by tm18.bullet.mail.ird.yahoo.com with NNFMP; 29 Jul 2013 11:02:39 -0000 Received: from [127.0.0.1] by smtp131.mail.ir2.yahoo.com with NNFMP; 29 Jul 2013 11:02:39 -0000 X-Yahoo-Newman-Id: 93061.76163.bm@smtp131.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: vvUxnK0VM1m8xM4l_SQFzpgNovnciYlXawMPk5bMRdOTcxe okdSXD7AEHOR2YWZZRWC6uYBdLLDE8vRBljddAXrXjnORBUac91jDIr2F_WI isPSC2f98T1W.ihv9ObdtuHITubFPID1EedgIaoGXKYUfG467KYyh.vdPDa4 58ryefg0wumY8dBITcmYSRT7DDmnBsZ5a_BdrHUbo.IdMfpQXfz4vE6c5dWA IgYr1Lc1uF_w2V7FtkveIrUnv2Rbp745dwBkzNulg4ZKZkXNgsahMri1yxOO XL6.cKLNYbVeb2_2vBgFYoNuvJRD36sxAkvXZgvkPA4QU45h3bxJyoU9zofa F1Xr9u7mmwo6fxggFAxAjGP1mTBipILZ1bhx19hCyTycfKbdpbpRFEOuWNku fG7I8xrS_s4DVvKj5E_z0g8xQKvAEmCJ4r_jXyUpVwqrvTSNQeVYWxCGZdbJ AMpTKzfZ6sd2PvyenJ7W83REBNwFfZeSR.y.Fg7L195DKQDztVERT39s_XMN fd9Bn.JVl.JLl X-Yahoo-SMTP: iDf2N9.swBDAhYEh7VHfpgq0lnq. X-Rocket-Received: from [192.168.0.17] (se@85.199.71.72 with ) by smtp131.mail.ir2.yahoo.com with SMTP; 29 Jul 2013 11:02:38 +0000 UTC Message-ID: <51F64BCC.9000301@freebsd.org> Date: Mon, 29 Jul 2013 13:02:36 +0200 From: Stefan Esser User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, kpielorz_lst@tdx.co.uk Subject: Re: kldload ipfw, with IPFIREWALL_DEFAULT_TO_ACCEPT References: <1D6BF13DFC536AFC94EC6D64@Mail-PC.tdx.co.uk> In-Reply-To: <1D6BF13DFC536AFC94EC6D64@Mail-PC.tdx.co.uk> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jul 2013 11:02:46 -0000 Am 29.07.2013 12:45, schrieb Karl Pielorz: > I've got a number of 9.1 boxes, where we need to enable ipfw (by > kldload'ing it). > > I'm sure I saw a while ago a sysctl that would change the default ipfw > config from 'deny all' to 'allow all' - even for a kldload? But I can't > find it now. I guess you were looking for: net.inet.ip.fw.default_to_accept="1" which is a tunable to be set in /boot/loader.conf ... Regards, STefan From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 29 11:27:39 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 25372FA9; Mon, 29 Jul 2013 11:27:39 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id E09B72055; Mon, 29 Jul 2013 11:27:38 +0000 (UTC) Received: from Mail-PC.tdx.co.uk (storm.tdx.co.uk [62.13.130.251]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id r6TBRabe098683 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Jul 2013 12:27:37 +0100 (BST) Date: Mon, 29 Jul 2013 12:27:40 +0100 From: Karl Pielorz To: Stefan Esser , freebsd-hackers@freebsd.org Subject: Re: kldload ipfw, with IPFIREWALL_DEFAULT_TO_ACCEPT Message-ID: In-Reply-To: <51F64BCC.9000301@freebsd.org> References: <1D6BF13DFC536AFC94EC6D64@Mail-PC.tdx.co.uk> <51F64BCC.9000301@freebsd.org> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jul 2013 11:27:39 -0000 --On 29 July 2013 13:02 +0200 Stefan Esser wrote: > I guess you were looking for: > > net.inet.ip.fw.default_to_accept="1" > > which is a tunable to be set in /boot/loader.conf ... Very probably - but that's at boot time :( - Is there nothing I can do at kldload time to have the initial kldload give me a 'allow ip from any to any' rule as it loads? (thus not affecting traffic on the machine, or more importantly the CARP interfaces)? -Karl From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 29 11:31:01 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3AF9047F for ; Mon, 29 Jul 2013 11:31:01 +0000 (UTC) (envelope-from simond@irrelevant.org) Received: from mail-ve0-x236.google.com (mail-ve0-x236.google.com [IPv6:2607:f8b0:400c:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E9A45209D for ; Mon, 29 Jul 2013 11:31:00 +0000 (UTC) Received: by mail-ve0-f182.google.com with SMTP id m1so2406234ves.13 for ; Mon, 29 Jul 2013 04:31:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=irrelevant.org; s=irrelevant; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=wmfK2xcxHBhVOXh53pjQUfwjeOrcep0oPY2xMS01YzM=; b=HZsw1UpPq+H2aU8iM/C2fK6C+jxnD4SG8BikRGI1W3X2d3c+rP3kLP/q+a1BN7E2pR nTAHhagpkFQAQvKhnlhqGGONRR4cBFVfi1ijDe9dLY+R1ohkmbt1Gz7p8/KEI9r+kGtN R3p8yH4UuzY68lUDi8hYZb7wSUGXghUfKAEK4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=wmfK2xcxHBhVOXh53pjQUfwjeOrcep0oPY2xMS01YzM=; b=HQj2nz5CoBJsZbc7S/9/ZbTtNjEmXOyNdwOIg5uHCe5tBBn7C8uky6cuxLhhHk8x4G k2AiKQ4x1qpoG8a+XS1+zRYaDd4f7KXlzRF9/33x+pSKTvf68jwAjYnFN9xAPKhbGqMy 3JtrEsuSPC7+VesYCjobjAVbnvUxvgKeVdPHKg3W/7T42bpKcaGyxd6FhmTG533yVSxC MTJQd0Li+dumSLpw1xZQ0OtFrPB1AlI9O/hq/LXmV8u/7xmVzEVsgRtmJJK006p8B9lL PoTC3jqbdeAbm/zB6Zwu9UKEubRXLAahwV/gHNgMSLWUz734EOE3xoJyfbTy/QEO83z/ bVYg== MIME-Version: 1.0 X-Received: by 10.220.159.208 with SMTP id k16mr8500321vcx.92.1375097460032; Mon, 29 Jul 2013 04:31:00 -0700 (PDT) Received: by 10.221.48.131 with HTTP; Mon, 29 Jul 2013 04:30:59 -0700 (PDT) X-Originating-IP: [94.31.26.5] In-Reply-To: References: <1D6BF13DFC536AFC94EC6D64@Mail-PC.tdx.co.uk> <51F64BCC.9000301@freebsd.org> Date: Mon, 29 Jul 2013 12:30:59 +0100 Message-ID: Subject: Re: kldload ipfw, with IPFIREWALL_DEFAULT_TO_ACCEPT From: Simon Dick To: Karl Pielorz X-Gm-Message-State: ALoCoQkKKooEJp/Ojy0OTw8N356OIsnWhUKWvNtPTRgy2MDZItpSJ0ecGom1Tv5aQ45eAteo0n9+ Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jul 2013 11:31:01 -0000 On 29 July 2013 12:27, Karl Pielorz wrote: > > > --On 29 July 2013 13:02 +0200 Stefan Esser wrote: > > I guess you were looking for: >> >> net.inet.ip.fw.default_to_**accept="1" >> >> which is a tunable to be set in /boot/loader.conf ... >> > > Very probably - but that's at boot time :( - Is there nothing I can do at > kldload time to have the initial kldload give me a 'allow ip from any to > any' rule as it loads? (thus not affecting traffic on the machine, or more > importantly the CARP interfaces)? > > My normal way is to run the kldload in screen and manually run an allow all right afterwards e.g. kldload ipfw && ipfw ... :) From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 29 09:07:00 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D3F05102 for ; Mon, 29 Jul 2013 09:07:00 +0000 (UTC) (envelope-from pragmb@gmail.com) Received: from mail-ve0-x22f.google.com (mail-ve0-x22f.google.com [IPv6:2607:f8b0:400c:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 991B8284F for ; Mon, 29 Jul 2013 09:07:00 +0000 (UTC) Received: by mail-ve0-f175.google.com with SMTP id da11so2692321veb.20 for ; Mon, 29 Jul 2013 02:06:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=z1mibiIc8spEE+OAxU2z3H4mgeN6B5MkjB9buyxgx5U=; b=BerwzVsDvYI9KrTi1A1xFdKjgQQfnefvHyXnAxwsKMetFzIp2bFP26T8Dvm9E2hlA9 PcVsUxfmfrh5qIu8g9htLuhRYSqBDsQ5YuG3MzELZ1XI5vcfzikLoCI4/qQWF91ll/+A ncRUVXv6o1nEzkEN8iq7gGW09b6wx5eomNcpoQ6gNi24qE4uzgZYufvvhQyfMZiefcea 70LWMjq1jBX14chcljUfgw+QESO+dD0ZpJcj+hwblOMOAOg/sqHtJ4mM3pU4VXdPrOv1 OiXHzpsG1f44OwdVvVspifcQ/w1p7ZYckpUPQKgLBMgQYrnDkaIThLEb82KL+DCxCnQv FGag== MIME-Version: 1.0 X-Received: by 10.58.97.138 with SMTP id ea10mr24941217veb.38.1375088819643; Mon, 29 Jul 2013 02:06:59 -0700 (PDT) Received: by 10.220.203.7 with HTTP; Mon, 29 Jul 2013 02:06:59 -0700 (PDT) Date: Mon, 29 Jul 2013 11:06:59 +0200 Message-ID: Subject: Can't override function keys in kbdcontrol From: Pragm B To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Mailman-Approved-At: Mon, 29 Jul 2013 11:34:27 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jul 2013 09:07:00 -0000 Hello everyone, I have problems overriding the functions keys of my keyboard in FreeBSD 9.1 The kbdcontrol utility can be used to define specific values for the function keys. See here: http://www.freebsd.org/cgi/man.cgi?query=atkbd&apropos=0&sektion=0&manpath=FreeBSD+9.1-RELEASE&arch=default&format=html It is stated that the function keys can be overridden using kbdcontrol -f # s where '#' is a number from 1 to 96 and 's' is a string that will be outputted. When '#' is between 65 and 96 (unassigned functions), this works. However, this does not work for functions keys between 1 and 64! Any insight is much appreciated :) Cheers, Pragmb From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 29 12:23:36 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id DAA80512; Mon, 29 Jul 2013 12:23:36 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 9FF6E2357; Mon, 29 Jul 2013 12:23:36 +0000 (UTC) Received: from Mail-PC.tdx.co.uk (storm.tdx.co.uk [62.13.130.251]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id r6TCNYqQ003679 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Jul 2013 13:23:35 +0100 (BST) Date: Mon, 29 Jul 2013 13:23:34 +0100 From: Karl Pielorz To: Simon Dick Subject: Re: kldload ipfw, with IPFIREWALL_DEFAULT_TO_ACCEPT Message-ID: <67FACFDFDA838E0B60BBDDF4@Mail-PC.tdx.co.uk> In-Reply-To: References: <1D6BF13DFC536AFC94EC6D64@Mail-PC.tdx.co.uk> <51F64BCC.9000301@freebsd.org> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jul 2013 12:23:36 -0000 --On 29 July 2013 12:30 +0100 Simon Dick wrote: > My normal way is to run the kldload in screen and manually run an allow > all right afterwards > e.g. > > kldload ipfw && ipfw ... :) Yeah, that would probably work - I'm more concerned what impact it would have on the CARP interfaces on the box - i.e. if they get 'cut off' even for a fractional period, they may decide they are the new master (or worse, other boxes may decide they need to become the new master). If there's no way of getting a 'default allow' on kldload (other than the workaround kind of way) it looks like I'll just have to plan for a cut off of things like CARP, and design around it :( Cheers, -Karl From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 29 14:04:47 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8DCFBC79; Mon, 29 Jul 2013 14:04:47 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F25F0283F; Mon, 29 Jul 2013 14:04:46 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.7/8.14.7) with ESMTP id r6TE4exJ013281; Mon, 29 Jul 2013 17:04:40 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.3 kib.kiev.ua r6TE4exJ013281 Received: (from kostik@localhost) by tom.home (8.14.7/8.14.7/Submit) id r6TE4ens013280; Mon, 29 Jul 2013 17:04:40 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 29 Jul 2013 17:04:40 +0300 From: Konstantin Belousov To: Karl Pielorz Subject: Re: kldload ipfw, with IPFIREWALL_DEFAULT_TO_ACCEPT Message-ID: <20130729140440.GN4972@kib.kiev.ua> References: <1D6BF13DFC536AFC94EC6D64@Mail-PC.tdx.co.uk> <51F64BCC.9000301@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dzI2QqkSBOAresgT" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jul 2013 14:04:47 -0000 --dzI2QqkSBOAresgT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 29, 2013 at 12:27:40PM +0100, Karl Pielorz wrote: >=20 >=20 > --On 29 July 2013 13:02 +0200 Stefan Esser wrote: >=20 > > I guess you were looking for: > > > > net.inet.ip.fw.default_to_accept=3D"1" > > > > which is a tunable to be set in /boot/loader.conf ... >=20 > Very probably - but that's at boot time :( - Is there nothing I can do at= =20 > kldload time to have the initial kldload give me a 'allow ip from any to= =20 > any' rule as it loads? (thus not affecting traffic on the machine, or mor= e=20 > importantly the CARP interfaces)? kenv net.inet.ip.fw.default_to_accept=3D1 should have the same effect after the usermode is booted. Kenv must be set before the module is loaded. --dzI2QqkSBOAresgT Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQIcBAEBAgAGBQJR9nZ3AAoJEJDCuSvBvK1BVsgP/1cq8116/8Rqq4ZIFovVsLyf CxNw6mHAMwdiImaDIauokGXPnKMKaJmxMr9HEe8TKVNsiTqiiz9+IIhZZzhNHxpa 9cnxJHif2mLnJNBe/OEjcqR/nz2BVa/B3z/e0/2qulfdhn0CqSiA3w0SZa2Jseaj oojcbtwo5IDH78kM/DufuDnuvGHWcPyeL1BSNTai4nZaIeddgS2vmtpo7qubeKco 9uGM0LZ/W2APxYRf5pvzULDcbuOmx0bN60GBTGhdGU54paLRuPV6TFTBvG3FjVQG GuAurggqkRdQpDBqlINg64wmeIa5HgM4khqArqVD21u+1vDD9y1yPg5Mq8fK1dpd 2muJ0pC8abkUYxWeh93yhnHtbw5xwJ5IYub8+sDg3ORgvH1rKadvb/JAaqzhSHDx EB0FPzUwTdz3bhUhucVwTUFFTMekajX82FNjsRJu4KqpeUon5vWYvHubVJVaGTkf vhg+qbmoFXUOzMhfVI+Njg7T6IeeL/MKV9FgdH042Y4jKerSugo7J72pAt+JyqgA usQPQEdUR5vdpOQo4OiPb0Lg/oHpBcwcHwBGeoWCwvUk8j3TKe3lvrgIEKrU7Fxh XQadT3HvPQhgxz6JfR32HGeBCwNb0p+gg915CXEDVMZ8vlLxrQx0ZPFn1GhmSeKE BvHM/yrViI7xURpFTnI0 =kgPp -----END PGP SIGNATURE----- --dzI2QqkSBOAresgT-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 29 14:52:09 2013 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0280D92A for ; Mon, 29 Jul 2013 14:52:09 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CC18F2BD7 for ; Mon, 29 Jul 2013 14:52:08 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1V3onu-000378-Mv; Mon, 29 Jul 2013 14:52:06 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r6TEq3Zi017251; Mon, 29 Jul 2013 08:52:03 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/KY1AomXHkZhZNJO9mp8sH Subject: Re: BUS_PROBE_NOWILDCARD behaviour doesn't seem to match DEVICE_PROBE(9) From: Ian Lepore To: Ryan Stone In-Reply-To: References: Content-Type: text/plain; charset="us-ascii" Date: Mon, 29 Jul 2013 08:52:03 -0600 Message-ID: <1375109523.45247.32.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jul 2013 14:52:09 -0000 On Thu, 2013-06-20 at 10:54 -0400, Ryan Stone wrote: > http://www.freebsd.org/cgi/man.cgi?query=DEVICE_PROBE&apropos=0&sektion=0&manpath=FreeBSD%208.2-RELEASE&format=html > > DEVICE_PROBE(9) has this to say about BUS_PROBE_NOWILDCARD: > > The driver expects its parent to tell it which children to manage and no > probing is really done. The device only matches if its parent bus > specifically said to use this driver. > > > I interpreted this as meaning that if BUS_ADD_CHILD() is called with the > name parameter specifying a driver then if that driver's probe method > returns BUS_PROBE_NOWILDCARD the driver will match that device. However > the logic in subr_bus.c is more strict; it will only match if the unit > number if also specified. This seems overly strict to me, and there > appears to be at least one case in-tree where a driver will never match due > to this behaviour: > > http://svnweb.freebsd.org/base/head/sys/dev/iicbus/iicsmb.c?revision=227843&view=markup > > The iicsmb driver calls BUS_ADD_CHILD() from its identify method with a > wildcarded unit number (-1) but the driver specified. It then returns > BUS_PROBE_NOWILDCARD from its attach method(intending that it only claim > the device created in the identify method), but that won't match. > > I want to use the exact same pattern in a new driver. The following patch > allows this to work: > > diff --git a/sys/kern/subr_bus.c b/sys/kern/subr_bus.c > index 1f3d4e8..7e48b0e 100644 > --- a/sys/kern/subr_bus.c > +++ b/sys/kern/subr_bus.c > @@ -2015,7 +2015,7 @@ device_probe_child(device_t dev, device_t child) > * in stone by the parent bus. > */ > if (result <= BUS_PROBE_NOWILDCARD && > - child->flags & DF_WILDCARD) > + !(child->flags & DF_FIXEDCLASS)) > continue; > best = dl; > pri = result; > > This should be safe to do, as all devices that specified a unit number must > have specified a driver, so this can't cause any devices to suddenly fail > to match. I supposed that it theoretically could cause a driver to match a > device that previously it wouldn't have, but I'm having trouble seeing how > somebody could add a device of type "foo" and not expect the "foo" driver > to attach. > > Any objections if I commit this? I know this is pretty long after the fact, but it looks like this never got committed. I recently had to port some drivers written for freebsd 4 and 6 to 8.2, and some of them have no real probe mechanism and attached themselves to, like, *everything* (serial and parallel ports and so on). They're instantiated based on hints that are definitive, so I switched to returning BUS_PROBE_NOWILDCARD and sanity returned. Then I remembered this email, so I applied your patch and re-tested and everything still worked perfectly. Not exactly an exhaustive test, but at least a positive datapoint. -- Ian From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 29 15:10:02 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7EDAAF1E for ; Mon, 29 Jul 2013 15:10:02 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EFB722CBC for ; Mon, 29 Jul 2013 15:10:01 +0000 (UTC) Received: by mail-wi0-f180.google.com with SMTP id f14so996195wiw.7 for ; Mon, 29 Jul 2013 08:10:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WabRBjs0o4RbA5mDuHhQSnj0vt8I11I8zcSl/kXo3C0=; b=1BIGaHqqSOwbYDo5SXmDSSVcuXZ/IGx0aXTsnSkUIC4yANiolne+T6pUxIMQIkv3gA 2FC88YMCfhgF6t6nJopP6TIZLVQyissGaZ0XAdXE/5qTrpOa7j5N5Y2DFKKul65t9PqE yzp1bMv4PaWO2JEMXJ8AG15ITmHnr8Enxiuu/5R+UKi+Wf3CsH91RgcBYY8w44BJkYPY Cb2ef9qDDdNcVYZUhsMzxOKlkRvTxMoFMJL7ZLPg6lSz/1V5z4XE0IDdObavxUMxyWDa yUYmwrD+DbsjkyyLw0ufgxmEUu6YnG2p0lWSVj3lRZKYBQcJ6asIW029M1DKESlTrQIL Wx+g== MIME-Version: 1.0 X-Received: by 10.180.79.161 with SMTP id k1mr7339826wix.36.1375110600119; Mon, 29 Jul 2013 08:10:00 -0700 (PDT) Received: by 10.180.187.162 with HTTP; Mon, 29 Jul 2013 08:09:59 -0700 (PDT) In-Reply-To: References: Date: Mon, 29 Jul 2013 17:09:59 +0200 Message-ID: Subject: Re: Can't override function keys in kbdcontrol From: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= To: Pragm B Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jul 2013 15:10:02 -0000 On Mon, Jul 29, 2013 at 11:06 AM, Pragm B wrote: > Hello everyone, > > I have problems overriding the functions keys of my keyboard in FreeBSD 9.1 > > The kbdcontrol utility can be used to define specific values for the > function keys. See here: > > http://www.freebsd.org/cgi/man.cgi?query=atkbd&apropos=0&sektion=0&manpath=FreeBSD+9.1-RELEASE&arch=default&format=html > > It is stated that the function keys can be overridden using > kbdcontrol -f # s > > where '#' is a number from 1 to 96 and 's' is a string that will be > outputted. > > When '#' is between 65 and 96 (unassigned functions), this works. > However, this does not work for functions keys between 1 and 64! > What do you mean by "does not work"? Do you get any errors? I'm on 9.1-RELEASE-p3 $ kbdcontrol -f 37 "hello" Here I type Ctrl-Shift-F1 and get: $hello > > Any insight is much appreciated :) > > Cheers, > Pragmb > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 29 15:42:19 2013 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2F8F546E for ; Mon, 29 Jul 2013 15:42:19 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E7CE12E0F for ; Mon, 29 Jul 2013 15:42:18 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1V3paT-000DE3-Pe; Mon, 29 Jul 2013 15:42:17 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r6TFgDGj017280; Mon, 29 Jul 2013 09:42:14 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX19In0IkB0W0kaQZgjFpnEo6 Subject: Re: bin/176713: [patch] nc(1) closes network socket too soon From: Ian Lepore To: "Ronald F. Guilmette" In-Reply-To: <11109.1374623313@server1.tristatelogic.com> References: <11109.1374623313@server1.tristatelogic.com> Content-Type: text/plain; charset="us-ascii" Date: Mon, 29 Jul 2013 09:42:13 -0600 Message-ID: <1375112533.45247.43.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jul 2013 15:42:19 -0000 On Tue, 2013-07-23 at 16:48 -0700, Ronald F. Guilmette wrote: > In message > Adrian Chadd wrote: > > >Right, and your patch just stops the shutdown(), right? > > The shutdown that occurs when EOF is encountered on stdin, yes. > > >Rather than > >teaching nc to correctly check BOTH socket states before deciding to > >close things. > > In effect, nc *is* currently "checking both sockets" and that is exactly > the problem. It terminates (prematurely in some cases) whenever it sees > an EOF _either_ from the remote host _or_ from stdin. > > My patch casuses nc to wait for EOF from the remote server before exiting, > EVEN IF prior to the time it sees that EOF from the remote server it sees > an EOF (first) on stdin. > > This code change demonstratably makes the functionality of nc better and > more pragmatically useful in typical use cases. > > You appear to be proposing something else, but I'm sorry to say that > I cannot decypher what, exactly you are attempting to propose. > > I have proposed specific code changes. If you have some different ones > that you would like to propose, then I feel sure that everyone on the > hackers list, including myself, would be interested to take a look at > what you have in mind, and also what problem you are solving. > > >I'd personally rather see nc taught to check to see whether it can > >possibly make ANY more progress before deciding to shut things down. > > I believe that that is exactly what the patch that I proposed does. > I'm not sure why you feel otherwise. > > Look, there are only two scenarios... either (a) EOF arrives from stdin > first or else (b) EOF arrives from the remote server first. > I don't think this accurately summarizes things. The view of the remote server isn't just "EOF arrives" it's "can't read anymore" and "can't write anymore" which have to be handled separately. > My patch causes nc to continue gathering data from the remote server > (and copying it all to stdout) in case (a). > > In case (b) there is no point in nc continuing to run (and/or continuing > to read from stdin) if the remote server has shut down the connection. > In this case, the data that nc might yet gather from its stdin channel > has noplace to go! So whenever nc has sensed an EOF from the remote > server it can (and should) immediately shut down... and that is exactly > what it is _already_ programmed to do. > Here you seem to be talking about the inability to send more data to the remote side. If you exit immediately when that happens, even if you could still read from the remote side, then you may miss the incoming data that would tell you why you can't send anymore. In this case the thing to do would be to stop reading stdin, but continue to read the remote side and copy it to stdout until you get EOF reading the remote side. Conversely, you can't exit immediately when the remote side has no more to send you and shuts down that half of the connection, you still have to read from stdin and send it to the remote until EOF on stdin or the remote shuts down that half of the connection. How all this applies to netcat's ability to do connectionless (UDP) stuff probably makes the whole thing that much more interesting. BTW, earlier in the thread you asserted more or less that telnet is for interactive and nc for scripting. I virtually never use nc in any way except interactively, and I use it that way every day, all day long. -- Ian > So, what problem do you want to solve that is not solved by the patch > that I already proposed? > > Also, with respect, if you think there really is some other problem, > then proposing actual concrete patches to solve that other problem > would perhaps allow folks, including myself, to better understand what > it is that you are driving at. > > > Regards, > rfg > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 29 14:17:31 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6CBC662C; Mon, 29 Jul 2013 14:17:31 +0000 (UTC) (envelope-from kpielorz@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 3212C2924; Mon, 29 Jul 2013 14:17:30 +0000 (UTC) Received: from Mail-PC.tdx.co.uk (storm.tdx.co.uk [62.13.130.251]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id r6TEHTG4012317 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Jul 2013 15:17:29 +0100 (BST) Date: Mon, 29 Jul 2013 15:17:33 +0100 From: Karl Pielorz To: Konstantin Belousov Subject: Re: kldload ipfw, with IPFIREWALL_DEFAULT_TO_ACCEPT Message-ID: In-Reply-To: <20130729140440.GN4972@kib.kiev.ua> References: <1D6BF13DFC536AFC94EC6D64@Mail-PC.tdx.co.uk> <51F64BCC.9000301@freebsd.org> <20130729140440.GN4972@kib.kiev.ua> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Mailman-Approved-At: Mon, 29 Jul 2013 17:39:47 +0000 Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jul 2013 14:17:31 -0000 --On 29 July 2013 17:04 +0300 Konstantin Belousov wrote: > kenv net.inet.ip.fw.default_to_accept=1 > should have the same effect after the usermode is booted. Kenv must > be set before the module is loaded. Great - thanks! - I'll give that a go in the test environment, Thanks, -Karl From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 30 01:54:43 2013 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5851DE5A for ; Tue, 30 Jul 2013 01:54:43 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 3A5B12C07 for ; Tue, 30 Jul 2013 01:54:42 +0000 (UTC) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 26FE23B615 for ; Mon, 29 Jul 2013 18:54:30 -0700 (PDT) From: "Ronald F. Guilmette" To: freebsd-hackers@FreeBSD.org Subject: Re: bin/176713: [patch] nc(1) closes network socket too soon In-Reply-To: <1375112533.45247.43.camel@revolution.hippie.lan> Date: Mon, 29 Jul 2013 18:54:30 -0700 Message-ID: <79871.1375149270@server1.tristatelogic.com> X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jul 2013 01:54:43 -0000 In message <1375112533.45247.43.camel@revolution.hippie.lan>, Ian Lepore wrote: >I don't think this accurately summarizes things... Everyone is entitled to her or her own opinion. Unfortunately, due to other pressing matters I will no longer be able to be an active participant in this debate. I'm very sorry. I'm sure that you all eill be able to carry on just fine without me, and vise versa. Regards, rfg From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 30 07:56:06 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 67EA5A74 for ; Tue, 30 Jul 2013 07:56:06 +0000 (UTC) (envelope-from shrikanth07@gmail.com) Received: from mail-vb0-x22d.google.com (mail-vb0-x22d.google.com [IPv6:2607:f8b0:400c:c02::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2C4E72AA5 for ; Tue, 30 Jul 2013 07:56:06 +0000 (UTC) Received: by mail-vb0-f45.google.com with SMTP id p14so3539401vbm.32 for ; Tue, 30 Jul 2013 00:56:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=IgW2y3ZuK7H2Gr26taRMXZoSyR3ItGldSdV20X0YWa0=; b=i2LGaNmwC9TuVrM9j4s5VdvWIH9SxBD9pK6lPFuSKEXKbiSnUZkoLxY7UONZeDidyi IIBNwWtS2ltPv1yzZBKwdrQpiVR52GRPfOc61FjWg1aI6Mpu2jzQH6vWn+D2rYNW6aq5 iEN+EwdL5N/tjke1CrhSMmv7PAD7OF5cWYeXIcburC/ThI8S2XEn6e5aSHAtCI1KWV9D mQQcrQv0+MIGUCrolN7LINchYIrfxdiAVj6abPmBnuL4fVDdt1bB/Dg8rh/1p6wZ1W2C jaSK8UV5EUKShKZqF5H+E1hxswTVJCt4DTsEg6wXC4PNJWwYHBQcOodqtaorvPNIb+qF gZyw== MIME-Version: 1.0 X-Received: by 10.220.173.195 with SMTP id q3mr9455404vcz.86.1375170964719; Tue, 30 Jul 2013 00:56:04 -0700 (PDT) Received: by 10.58.232.41 with HTTP; Tue, 30 Jul 2013 00:56:04 -0700 (PDT) Date: Tue, 30 Jul 2013 00:56:04 -0700 Message-ID: Subject: Symbols in symtab reordered between module.kld and module.ko? From: Shrikanth Kamath To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jul 2013 07:56:06 -0000 I am comparing the readelf -s snapshot from module.kld and module.ko for a module build in a cross compiler FreeBSD 10 environment, Do the symbols in symtab get reordered between module.kld and module.ko, as an example readelf -s module.kld we pick 2 symbols 2651: 000b8230 74 FUNC GLOBAL DEFAULT 1 prison_equal_ip6 2652: 00030140 3318 FUNC GLOBAL DEFAULT 1 ip_output Compare them with readelf -s from module.ko 2558: 0007a6d0 3318 FUNC GLOBAL DEFAULT 5 ip_output 2559: 001027c0 74 FUNC GLOBAL DEFAULT 5 prison_equal_ip6 So the symbol ip_output appears after prison_equal_ip6 in module.kld but appears before it in module.ko. The problem is this is affecting the DTrace FBT probing, running FBT probe of ip_output shows as having arguments of prison_equal_ip6. The way module.ko is being derived from module.kld is ld -m elf_i386 -Bshareable --verbose -o module.ko.debug module.kld How can I suppress this re-ordering? From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 31 09:37:34 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id ED55614D for ; Wed, 31 Jul 2013 09:37:34 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id B63BC264F for ; Wed, 31 Jul 2013 09:37:34 +0000 (UTC) Received: from Mail-PC.tdx.co.uk (storm.tdx.co.uk [62.13.130.251]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id r6V9bXwS017758 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 31 Jul 2013 10:37:33 +0100 (BST) Date: Wed, 31 Jul 2013 10:37:35 +0100 From: Karl Pielorz To: freebsd-hackers@freebsd.org Subject: Stacking lots of IP's on a single box - any 'gotchas'? Message-ID: <34C668004A0D654205D0516B@Mail-PC.tdx.co.uk> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jul 2013 09:37:35 -0000 Hi, We've got a number of boxes we'd like to consolidate - this could mean upward of 1,500 IP's on a single box (9.1 amd64). Last time we did anything like this we hit at issue at around 900 (ntpd 'binds' by default to all available IP's - I think we had a workaround for that). But is there any hard limit we're likely to encounter putting so many IP's on a single machine? - Are there any limits that would likely need tuning to support that many IP's? Thanks, -Karl From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 31 17:23:58 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2D4B6A3E for ; Wed, 31 Jul 2013 17:23:58 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 00A032E6F for ; Wed, 31 Jul 2013 17:23:57 +0000 (UTC) Received: from Julian-MBP3.local (etroy.elischer.org [121.45.226.51]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.6) with ESMTP id r6VHNpW9034901 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 31 Jul 2013 10:23:55 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <51F94822.4020005@freebsd.org> Date: Thu, 01 Aug 2013 01:23:46 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Karl Pielorz Subject: Re: Stacking lots of IP's on a single box - any 'gotchas'? References: <34C668004A0D654205D0516B@Mail-PC.tdx.co.uk> In-Reply-To: <34C668004A0D654205D0516B@Mail-PC.tdx.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jul 2013 17:23:58 -0000 On 7/31/13 5:37 PM, Karl Pielorz wrote: > > Hi, > > We've got a number of boxes we'd like to consolidate - this could > mean upward of 1,500 IP's on a single box (9.1 amd64). > > Last time we did anything like this we hit at issue at around 900 > (ntpd 'binds' by default to all available IP's - I think we had a > workaround for that). > > But is there any hard limit we're likely to encounter putting so > many IP's on a single machine? - Are there any limits that would > likely need tuning to support that many IP's? all on one interface? do you really need so many addresses? what are you trying to achieve? you can make a machine accept work for many addresses without actually assigning those addresses to any interface on the machine (see ipfw fwd) > > Thanks, > > -Karl > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to > "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 31 19:47:04 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 98B74A3A for ; Wed, 31 Jul 2013 19:47:04 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2D7E424B5 for ; Wed, 31 Jul 2013 19:47:04 +0000 (UTC) Received: by mail-we0-f180.google.com with SMTP id p61so969718wes.25 for ; Wed, 31 Jul 2013 12:47:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yjkqPXpcA6Yz8ZHuIzPpuBYDI2xpJHVxBR39yfPLLzk=; b=Dpm0Zqc3nAaUt7zajLafwqczyCdlCUTk6xojcM9H4XfAj2sGbHzGI7JHxjrq0YiASu sUkU0kUNuBRykBxrBOzrbEdgfxqF/yUr9HvAiZwqUPJG/+/sluAu5EsLnA3vWOlFHSTl 9MO1xL5Vp+jAjFC77KswlpqzgnxEdZJyC4YgUx4sOFmHIWh03vWotNdHAkZd19bvrPED 3R0qaVa7VMsfKOcObDlGNwBmmTlQumWgo5P/wNOozkgSlp55lTcXFoXUyjjEfuePFi9T KsB01Vgfk5LNvoXVsW1Te4h2mYGA2MZC5KMIt81WNf+firXvSqTmJpDDxYrPIZHwcXR+ kB9A== MIME-Version: 1.0 X-Received: by 10.180.11.146 with SMTP id q18mr5368172wib.50.1375300022225; Wed, 31 Jul 2013 12:47:02 -0700 (PDT) Received: by 10.216.82.70 with HTTP; Wed, 31 Jul 2013 12:47:02 -0700 (PDT) In-Reply-To: <34C668004A0D654205D0516B@Mail-PC.tdx.co.uk> References: <34C668004A0D654205D0516B@Mail-PC.tdx.co.uk> Date: Wed, 31 Jul 2013 23:47:02 +0400 Message-ID: Subject: Re: Stacking lots of IP's on a single box - any 'gotchas'? From: Sergey Kandaurov To: Karl Pielorz Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jul 2013 19:47:04 -0000 On 31 July 2013 13:37, Karl Pielorz wrote: > > Hi, > > We've got a number of boxes we'd like to consolidate - this could mean > upward of 1,500 IP's on a single box (9.1 amd64). > > Last time we did anything like this we hit at issue at around 900 (ntpd > 'binds' by default to all available IP's - I think we had a workaround for > that). > This is because select() has a limit on FD_SETSIZE (1024). If it tries to select > 1024 fds, bad things could happen. Newer ntpd (not in base) has a feature to bind only to the specific interface; this was used to run ntpd on boxes with > 1200 IPs on 1 i/face. > But is there any hard limit we're likely to encounter putting so many IP's > on a single machine? - Are there any limits that would likely need tuning to > support that many IP's? > Unlikely, besides those unrelated things like ntpd+select() et.al. -- wbr, pluknet From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 31 20:27:41 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8DA4C2BC for ; Wed, 31 Jul 2013 20:27:41 +0000 (UTC) (envelope-from db@db.net) Received: from diana.db.net (diana.db.net [66.113.102.10]) by mx1.freebsd.org (Postfix) with ESMTP id 763092640 for ; Wed, 31 Jul 2013 20:27:41 +0000 (UTC) Received: from night.db.net (localhost [127.0.0.1]) by diana.db.net (Postfix) with ESMTP id 357E42AA4BD; Wed, 31 Jul 2013 14:27:32 -0600 (MDT) Received: by night.db.net (Postfix, from userid 1000) id 28C311CC0E; Wed, 31 Jul 2013 15:27:22 -0500 (EST) Date: Wed, 31 Jul 2013 15:27:22 -0500 From: Diane Bruce To: Sergey Kandaurov Subject: Re: Stacking lots of IP's on a single box - any 'gotchas'? Message-ID: <20130731202722.GA11852@night.db.net> References: <34C668004A0D654205D0516B@Mail-PC.tdx.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-hackers@freebsd.org, Karl Pielorz X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jul 2013 20:27:41 -0000 On Wed, Jul 31, 2013 at 11:47:02PM +0400, Sergey Kandaurov wrote: > On 31 July 2013 13:37, Karl Pielorz wrote: > > > > Hi, > > > > We've got a number of boxes we'd like to consolidate - this could mean > > upward of 1,500 IP's on a single box (9.1 amd64). > > > > Last time we did anything like this we hit at issue at around 900 (ntpd > > 'binds' by default to all available IP's - I think we had a workaround for > > that). > > > > This is because select() has a limit on FD_SETSIZE (1024). > If it tries to select > 1024 fds, bad things could happen. > Newer ntpd (not in base) has a feature to bind only to the specific > interface; this was used to run ntpd on boxes with > 1200 IPs on 1 i/face. I can tell you from experience that FreeBSD has no problems at all selecting on more than 1024 fds. In fact, this is what I would suggest you do. Your limit then is going to be the number of anonymous ports on each IP. Figure 32000 or so to be conservative that's more than what you need. > > But is there any hard limit we're likely to encounter putting so many IP's > > on a single machine? - Are there any limits that would likely need tuning to > > support that many IP's? > > > > Unlikely, besides those unrelated things like ntpd+select() et.al. > > -- > wbr, > pluknet - Diane -- - db@FreeBSD.org db@db.net http://www.db.net/~db From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 1 03:59:21 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4482C247 for ; Thu, 1 Aug 2013 03:59:21 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 17B5725E5 for ; Thu, 1 Aug 2013 03:59:20 +0000 (UTC) Received: from jre-mbp.elischer.org (etroy.elischer.org [121.45.226.51]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.6) with ESMTP id r713xGNh036514 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Wed, 31 Jul 2013 20:59:19 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <51F9DD11.1020606@freebsd.org> Date: Thu, 01 Aug 2013 11:59:13 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: Stacking lots of IP's on a single box - any 'gotchas'? References: <34C668004A0D654205D0516B@Mail-PC.tdx.co.uk> <20130731202722.GA11852@night.db.net> In-Reply-To: <20130731202722.GA11852@night.db.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Aug 2013 03:59:21 -0000 On 8/1/13 4:27 AM, Diane Bruce wrote: > On Wed, Jul 31, 2013 at 11:47:02PM +0400, Sergey Kandaurov wrote: >> On 31 July 2013 13:37, Karl Pielorz wrote: >>> Hi, >>> >>> We've got a number of boxes we'd like to consolidate - this could mean >>> upward of 1,500 IP's on a single box (9.1 amd64). >>> >>> Last time we did anything like this we hit at issue at around 900 (ntpd >>> 'binds' by default to all available IP's - I think we had a workaround for >>> that). >>> >> This is because select() has a limit on FD_SETSIZE (1024). >> If it tries to select > 1024 fds, bad things could happen. >> Newer ntpd (not in base) has a feature to bind only to the specific >> interface; this was used to run ntpd on boxes with > 1200 IPs on 1 i/face. > I can tell you from experience that FreeBSD has no problems at all selecting > on more than 1024 fds. In fact, this is what I would suggest you do. > Your limit then is going to be the number of anonymous ports on each > IP. Figure 32000 or so to be conservative that's more than what you need. Once again. I ask: Why do you want to do this? if you just want to respond to a small number of ports on multiple addresses there are easier ways to do this with a single socket. > > >>> But is there any hard limit we're likely to encounter putting so many IP's >>> on a single machine? - Are there any limits that would likely need tuning to >>> support that many IP's? >>> >> Unlikely, besides those unrelated things like ntpd+select() et.al. >> >> -- >> wbr, >> pluknet > - Diane From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 1 08:16:56 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 89A4A225 for ; Thu, 1 Aug 2013 08:16:56 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 50C872135 for ; Thu, 1 Aug 2013 08:16:56 +0000 (UTC) Received: from Mail-PC.tdx.co.uk (storm.tdx.co.uk [62.13.130.251]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id r718Gq4n025931 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Aug 2013 09:16:53 +0100 (BST) Date: Thu, 01 Aug 2013 09:16:54 +0100 From: Karl Pielorz To: Sergey Kandaurov Subject: Re: Stacking lots of IP's on a single box - any 'gotchas'? Message-ID: <35E6DA11BCAC68653E699E83@Mail-PC.tdx.co.uk> In-Reply-To: References: <34C668004A0D654205D0516B@Mail-PC.tdx.co.uk> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Aug 2013 08:16:56 -0000 --On 31 July 2013 23:47 +0400 Sergey Kandaurov wrote: >> But is there any hard limit we're likely to encounter putting so many >> IP's on a single machine? - Are there any limits that would likely need >> tuning to support that many IP's? >> > > Unlikely, besides those unrelated things like ntpd+select() et.al. As far as I know they already split the software handling the IP's between multiple instances (some kind of VPN end points outward facing) - so as long as we say, avoid anything that's going to try and 'select' on all of them - and keep an eye on other things (like mbufs/clusters/fd's etc.) this should work... Thanks for the replies... -Kp From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 1 19:18:09 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7FDC7506 for ; Thu, 1 Aug 2013 19:18:09 +0000 (UTC) (envelope-from rnewpol@panasas.com) Received: from natasha.panasas.com (natasha.panasas.com [67.152.220.90]) by mx1.freebsd.org (Postfix) with ESMTP id 45B1325A7 for ; Thu, 1 Aug 2013 19:18:08 +0000 (UTC) Received: from zenyatta.panasas.com (zenyatta.int.panasas.com [172.17.28.63]) by natasha.panasas.com (8.13.1/8.13.1) with ESMTP id r71JI8B6012858 for ; Thu, 1 Aug 2013 15:18:08 -0400 Received: from ZENYATTA.int.panasas.com ([fe80::44ca:f0e1:b97e:bf79]) by zenyatta.int.panasas.com ([fe80::44ca:f0e1:b97e:bf79%15]) with mapi id 14.01.0438.000; Thu, 1 Aug 2013 15:18:08 -0400 From: "Newpol, Richard" To: "freebsd-hackers@freebsd.org" Subject: Problem with lagg driver? Thread-Topic: Problem with lagg driver? Thread-Index: Ac6O69rfRbIh7q8wTF+L0UnmsLA63Q== Date: Thu, 1 Aug 2013 19:18:08 +0000 Message-ID: <1A778AD3F807B340B7EB1BD1B9C196773D6560C0@zenyatta.int.panasas.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.17.28.30] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Aug 2013 19:18:09 -0000 All, We seem to have discovered a problem that occurs when adding an address (or= alias) to a DOWNed lagg interface. After adding an address, when you try t= o bring the interface UP it can't reach the desired networks. Turns out that the problem occurs because the lagg driver silently passes t= he SIOCSIFADDR ioctl to the "ether_ioctl" handler, which in turn always set= s the IFF_UP flag. While this is usually ok (since ifconfig
implies UP with the= first assigned address anyway), the lagg driver does not have the proper h= andling to actually change state to UP on the first address, so it ends up = in an inconsistent state. Then, when the user eventually does an "ifconfig = lagg up" the default subnet routes are not added (because the "interface up= " code sees that IFF_UP is already set). So my first question - is this a known problem, or has it been addressed in= some other way? Secondly, I can think of two ways to fix this, and was wondering what are t= he implications. The first way would be for the lagg driver to correctly br= ing itself up when the first address is added to it. The second way would b= e for the lagg driver to preserve the state of IFF_FLAG when handling SIOCS= IFADDR. I like the second way because it is less of an overall behaviour ch= ange from the current, but the first way seems more correct. Rich Newpol Panasas From owner-freebsd-hackers@FreeBSD.ORG Sat Aug 3 02:37:58 2013 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6B343BA8 for ; Sat, 3 Aug 2013 02:37:58 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 3E038239C for ; Sat, 3 Aug 2013 02:37:57 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id r732AgTK038326 for ; Fri, 2 Aug 2013 19:10:43 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <51FC65DF.2090606@rawbw.com> Date: Fri, 02 Aug 2013 19:07:27 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130628 Thunderbird/17.0.7 MIME-Version: 1.0 To: FreeBSD Hackers Subject: After the FreeBSD VM crash, file system in VM got rolled back to some old previous state causing data loss Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Aug 2013 02:37:58 -0000 I hit this unexpected problem: my host had an ungraceful shutdown while FreeBSD 9.1 STABLE was running in the VirtualBox VM. After reboot of the host and VM, local ufs file system was missing all recent updates for at least 20 hours (!!!) My question is, how is this possible? Is this related to journaled soft-updates which were enabled in VM? Losing data looks like a critical issue. I had a backup outside VM so no real data loss for me, but this is bad. Fedora VM, that was shut down in the same way didn't suffer from the same issue (local ext4). Host shutdown was caused by the frozen Xorg, I had to kill it and reboot. VirtualBox processes got killed in the process. Yuri From owner-freebsd-hackers@FreeBSD.ORG Sat Aug 3 10:14:27 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6DD0F9F1 for ; Sat, 3 Aug 2013 10:14:27 +0000 (UTC) (envelope-from aamitr4@gmail.com) Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EB3F52E0D for ; Sat, 3 Aug 2013 10:14:26 +0000 (UTC) Received: by mail-lb0-f179.google.com with SMTP id v1so1012468lbd.24 for ; Sat, 03 Aug 2013 03:14:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=MkisG85mfZovoylID0FuATLEwtYkXdXzRad+u2EpHCY=; b=gMzcTnE0yEzSoEXBktB0AQAArceIqmlmqq3ybxeRNsMbYMZHAzx+2IVEEXa4OHm8wy V69Nmqs6GNTyM9TGDoYrqf3uK/0ZbtOiUWVxyveEXZB+kVk74ubQZ1qk8t0pj+uOGl0I 5uLdyU7XQ0mi0a8C4aaSwohsAbIB23i320kyXf1gVWE0fblgn9E2Po1D3nQkMxi567pF U1CmV/FsbtkEc5hZxxSNA/lLJkHe/REulZ/CcocDvcvhjwxjevwRw7szaDH0C/jFVq98 vWQY1npz+28nKonzUWsTfGXFwA74ysHHu7Nc/gvWfT+HolU1+eQNvU3ZOU7uL+GSOTLS 79kg== MIME-Version: 1.0 X-Received: by 10.152.29.103 with SMTP id j7mr4594570lah.7.1375524864741; Sat, 03 Aug 2013 03:14:24 -0700 (PDT) Received: by 10.152.45.178 with HTTP; Sat, 3 Aug 2013 03:14:24 -0700 (PDT) Date: Sat, 3 Aug 2013 10:14:24 +0000 Message-ID: Subject: I am frustrated From: Amit Rawat To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Aug 2013 10:14:27 -0000 Hi, I am Amit Rawat. Here is the link to my two proposal which I submitted in two consecutive year 1. https://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/amitrawat10/1#c8001 2. https://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/amitrawat10/12001 But I didn't get selected. I posted the mail in freebsd hackers as per the instruction http://lists.freebsd.org/pipermail/freebsd-hackers/2013-April/042411.html and what I propose is based on the fact given by the people of freebsd. I spent one year on working in freebsd. I remain most of the time in the irc channel #freebsd-soc and #bsdmisp. I maintain the blog https://amit10rawat.wordpress.com/ as per suggested by the google. I follow all the mailing list. Now I don't know why I didn't get selected and How many times I need to apply to get selected. Now I am confused what to do to get selected to freebsd.. It is total waste of time and energy and every time they give lame excuses to me. I tried hard to attach to this community but it is really disappointing and frustrating. When I see the result I found that some of them never came to IRC or even tried to post anything on freebsd mailing list. I am questioning the selection procedure of freebsd. I have no faith in it. I have few questions 1. FreeBSD FUSE* *has been allotted two slots before and third this time. One project with three slot. 2. Port GlusterFS to FreeBSD how it can be completed since it depends on FUSE as written by the project submitter. But FUSE is still not ported. 3. What is the relation b/w capsicum and FreeBSD ? and Why capsicum project are put in freebsd slots ? The management of project is disaster. If my project is not so worth people should have said it before. I would have applied to some other community which care about the people who want to join the community. Regards, Amit Rawat From owner-freebsd-hackers@FreeBSD.ORG Sat Aug 3 12:55:56 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 10D7C5B1 for ; Sat, 3 Aug 2013 12:55:56 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-oa0-x232.google.com (mail-oa0-x232.google.com [IPv6:2607:f8b0:4003:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CF40A21FE for ; Sat, 3 Aug 2013 12:55:55 +0000 (UTC) Received: by mail-oa0-f50.google.com with SMTP id i4so3371611oah.9 for ; Sat, 03 Aug 2013 05:55:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6jUByXzEKsP542MfOuYYnW8vkasZf5vgnIlBySy1y+U=; b=Uou9xigWp70/QRmCqt+fcYi9OOvp86+CZQcgcARbIRIkA8CaW79ZdDNRrC0dFtWdRM 5exzZkzKst6bKyksd4vZVKoD75IZ4mhCqgKD6VcoTRLGodC0eif4iKRwPH2PnWXjayR6 9phvnCd3pYmye9xIdZq5DY0l6SD/L5JHZMdlX6tmy750s66lGDjuC5WyVg2UBdoPJks5 +hx/bSshuF3bb9W4srW5KxXNfCSvX18C996AG1c3et7FrrMPYfwWylmPOrBQn/h82IA5 5YbI3i5GT8nMS/boxL1LnIapE261qlpfgMpqYU1CH7mS5c2sCVnxM6UrXC8HoyOViOfl hOBQ== MIME-Version: 1.0 X-Received: by 10.182.88.202 with SMTP id bi10mr8669124obb.91.1375534555171; Sat, 03 Aug 2013 05:55:55 -0700 (PDT) Received: by 10.182.115.194 with HTTP; Sat, 3 Aug 2013 05:55:55 -0700 (PDT) In-Reply-To: References: Date: Sat, 3 Aug 2013 08:55:55 -0400 Message-ID: Subject: Re: I am frustrated From: Super Bisquit To: Amit Rawat Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Aug 2013 12:55:56 -0000 Calm down for a minute. There are people who work with embedded systems on the different mailing lists. Think about things first. You were given some suggestions in that thread. The problem is convincing the embedded market and not those who maintain FreeBSD. You need the hardware along with the software to do your project. What systems and architectures will be your focus? The other projects started with someone who took time and tried. If you start on what you want while allowing others to be able to join in, you may get more help. Adrian mentioned the MIPS kernel to you in that thread. The raspberry Pi /ARM port could use some help. Even the PPC and standard ports could use that help; but, you need to test what you build. Amit, the project takes a lot of people who work constantly on making the system stable. Making an ultimatum will not have the effect that you so desire. Have you asked if anyone is willing to teach you more about the kernel internals? Have you looked at all of the code? Take a breath and start over. On Sat, Aug 3, 2013 at 6:14 AM, Amit Rawat wrote: > Hi, > > I am Amit Rawat. Here is the link to my two proposal which I submitted in > two consecutive year > 1. > > https://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/amitrawat10/1#c8001 > > 2. > > https://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/amitrawat10/12001 > > But I didn't get selected. I posted the mail in freebsd hackers as per the > instruction > > http://lists.freebsd.org/pipermail/freebsd-hackers/2013-April/042411.html > > and what I propose is based on the fact given by the people of freebsd. I > spent one year on working in freebsd. I remain most of the time in the irc > channel #freebsd-soc and #bsdmisp. I maintain the blog > > https://amit10rawat.wordpress.com/ > > as per suggested by the google. I follow all the mailing list. > > Now I don't know why I didn't get selected and How many times I need to > apply to get selected. Now I am confused what to do to get selected to > freebsd.. It is total waste of time and energy and every time they give > lame excuses to me. I tried hard to attach to this community but it is > really disappointing and frustrating. When I see the result I found that > some of them never came to IRC or even tried to post anything on freebsd > mailing list. I am questioning the selection procedure of freebsd. I have > no faith in it. > > I have few questions > > 1. FreeBSD FUSE* *has been allotted two slots before and third this time. > One project with three slot. > > > 2. Port GlusterFS to FreeBSD how it can be completed since it depends on > FUSE as written by the project submitter. But FUSE is still not ported. > > 3. What is the relation b/w capsicum and FreeBSD ? and Why capsicum project > are put in freebsd slots ? > > The management of project is disaster. If my project is not so worth people > should have said it before. I would have applied to some other community > which care about the people who want to join the community. > > Regards, > > Amit Rawat > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >