From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id 3CB5521F1C9 for ; Sun, 20 Oct 2013 09:26:01 -0700 (PDT) Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 50A9B20C27; Sun, 20 Oct 2013 12:26:00 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute5.internal (MEProxy); Sun, 20 Oct 2013 12:26:00 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=imap.cc; h= message-id:date:from:mime-version:to:subject:references :in-reply-to:content-type; s=mesmtp; bh=AEEEAKsmUUcEJ9RqVbCRa40U ZZk=; b=KB+Ag6loCFPN4ydxW9jg9X914qBaVWzyO1QRRdwlO4AMJn5Dp/FFoTBA pY/9KtV9zkI4wKbQsXnghq+tmSPVsnhCGVPEmA803kPhpfBBsoC2PQepKSJvMhxl ea50gnm2cwMfRkQOEQ2yVii9KdlhxzEejUiSJoFPS3CtP7uRPtg= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type; s=smtpout; bh=AEEE AKsmUUcEJ9RqVbCRa40UZZk=; b=Y6yYlp3Zjh0n+6XEvIGhcwzqfefqM+x7R5Ab yMqmWTmI+pY00Mos5ojhkg7l6ztDTGRMbvLqHJmh7lYTLE0aUIN/LWegWmxvHT7t ciD5yW1WUzXKCt29EbJcbDlAr/H0V+JnlNwitVjMSF+P+W4hS7CtlARomrk55J2M io4rHvI= X-Sasl-enc: xOGTGrnfvt1fBCSC7T0m7NzH2ZCGacHfAV4LLhrCfdx6 1382286359 Received: from [172.30.42.8] (unknown [2.96.14.206]) by mail.messagingengine.com (Postfix) with ESMTPA id AC65CC00E87 for ; Sun, 20 Oct 2013 12:25:59 -0400 (EDT) Message-ID: <52640416.6010906@imap.cc> Date: Sun, 20 Oct 2013 17:25:58 +0100 From: Fred Stratton User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: cerowrt-devel@lists.bufferbloat.net References: <5264020C.2030203@imap.cc> In-Reply-To: <5264020C.2030203@imap.cc> X-Forwarded-Message-Id: <5264020C.2030203@imap.cc> Content-Type: multipart/alternative; boundary="------------000706030307000701030406" Subject: Re: [Cerowrt-devel] development build 3.10.17-1 released X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Oct 2013 16:26:01 -0000 This is a multi-part message in MIME format. --------------000706030307000701030406 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Well, I have never before seen such a clear explanation of router firmware configuration. I had expected the script to be launched from rc, not rc.local. The latter, however, might be regarded as good practice, and, if rc is derived unchanged from OpenWrt, might make code maintenance much easier. I reinstated the script in rc.local to launch /etc/fixdaemons, overwritten as you say by the /overlay/etc/rc.local I had introduced, and all wireless connected machines have reacquired ipv4 DHCP addresses, in addition to the ipv6 addresses they possessed. Thank you. On 20/10/13 14:55, David Personette wrote: > The actual CeroWRT is a RO filesystem, with modifications stored in an > overlay. you can see the original file with no customizations in /rom. > /overlay is mounted "over" the ROM. If nothing has been changed the > /rom file is read, if you have made a change, then it's read from the > overlay. A change that you can make is deleting a file that exists on > the /rom image, and that can be stored on the overlay as well (the > file will be not be visible in the merged /). You can purge changes > that you have made by removing the corresponding file(s) and/or > directory(s) in the /overlay filesystem. > > -- > David P. > > > On Sun, Oct 20, 2013 at 9:41 AM, Fred Stratton > wrote: > > What do you mean by 'overlay/etc/rc.local'? > > I have used 2 backup configurations, one with iptables rules in > rc.local, and one with no uncommented text, other than 'exit 0'. > > Both show the same problem. > > I have previously operated this Mac with a wired connection. I was > thinking this was a 10.8.5 problem prior to your comment. > > > > On 20/10/13 14:17, David Personette wrote: >> I have a laptop running 10.8.5 that's working. I had to remove >> the /overlay/etc/rc.local file and reboot before Dave's >> /etc/fixdaemons would show up. My saved configuration was >> stopping it from working. >> >> -- >> David P. >> >> >> On Sun, Oct 20, 2013 at 9:12 AM, Fred Stratton >> > wrote: >> >> Spoke too soon . Machine running OS X 10.8.5 cannot obtain >> wireless DHCP lease. Machine running 10.7.5 has no problem. >> >> >> On 20/10/13 06:41, Dave Taht wrote: >> >> + sync with openwrt >> + dnsmasq 2.67rc4 >> + get_cycles() and /dev/random fixes >> + mild firewall changes >> + actually sort of tested >> - sysupgrade still busted >> - didn't package the jitter rng >> >> The simple expedient of putting a script in /etc/rc.local >> to restart >> pimd, minissdpd, and dnsmasq 60 seconds after boot >> appears to get us a >> working dhcp/dns on the wifi interfaces once again. >> >> dnsmasq wasn't busted, it was how it interfaces to >> netifd. the march >> down to something deployable resumes with rc4. >> >> This is the first test that I know of, of some of the RNG >> fixes >> upstream, notably the mips code does the right thing with >> a highly >> optimized "get_cycles()". >> >> There are two changes to the firewall code >> >> 1) There has been a long-standing error in not blocking >> port 161 >> (snmp) from the outside world. It is now blocked by default. >> >> Although I am not aware of any exploits of this (besides the >> information leakage) I would recommend blocking this port >> by default >> on your existing builds, also, or disabling the snmp >> daemon entirely >> if you do not use it. >> >> 2) Usage of the "pattern matching syntax" on various >> firewall rules. >> >> Instead of 3 rules for se00,sw00,sw10, and 4 for >> gw00,gw10,gw01,gw11 >> there are now 1 rule for s+ and one rule for gw+ >> >> This does not show up in the web interface correctly. I'd >> also like to >> get to a more efficient rule set for the blocked ports, >> perhaps with >> ipset... >> >> ... >> >> It's sort of my hope that with these fixes that the march >> towards a >> stable release can resume, and we get some fresh shiny >> new bugs out of >> this. >> >> Upcoming next are a revised version of pie, more random >> number fixes, >> and I forget what else. >> >> >> 3) >> >> >> _______________________________________________ >> Cerowrt-devel mailing list >> Cerowrt-devel@lists.bufferbloat.net >> >> https://lists.bufferbloat.net/listinfo/cerowrt-devel >> >> > > > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > > https://lists.bufferbloat.net/listinfo/cerowrt-devel > > --------------000706030307000701030406 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
Well, I have never before seen such a clear explanation of router firmware configuration. I had expected the script to be launched from rc, not rc.local. The latter, however, might be regarded as good practice, and, if rc is derived unchanged from OpenWrt, might make code maintenance much easier.

I reinstated the script in rc.local to launch /etc/fixdaemons, overwritten as you say by the /overlay/etc/rc.local I had introduced, and all wireless connected machines have reacquired ipv4 DHCP addresses, in addition to the ipv6 addresses they possessed.

Thank you.


On 20/10/13 14:55, David Personette wrote:
The actual CeroWRT is a RO filesystem, with modifications stored in an overlay. you can see the original file with no customizations in /rom. /overlay is mounted "over" the ROM. If nothing has been changed the /rom file is read, if you have made a change, then it's read from the overlay. A change that you can make is deleting a file that exists on the /rom image, and that can be stored on the overlay as well (the file will be not be visible in the merged /). You can purge changes that you have made by removing the corresponding file(s) and/or directory(s) in the /overlay filesystem.

-- 
David P.


On Sun, Oct 20, 2013 at 9:41 AM, Fred Stratton <fredstratton@imap.cc> wrote:
What do you mean by 'overlay/etc/rc.local'?

I have used 2 backup configurations, one with iptables rules in rc.local, and one with no uncommented text, other than 'exit 0'.

Both show the same problem.

I have previously operated this Mac with a wired connection. I was thinking this was a 10.8.5 problem prior to your comment.



On 20/10/13 14:17, David Personette wrote:
I have a laptop running 10.8.5 that's working. I had to remove the /overlay/etc/rc.local file and reboot before Dave's /etc/fixdaemons would show up. My saved configuration was stopping it from working.

--
David P.


On Sun, Oct 20, 2013 at 9:12 AM, Fred Stratton <fredstratton@imap.cc> wrote:
Spoke too soon . Machine running OS X 10.8.5 cannot obtain wireless DHCP lease. Machine running 10.7.5 has no problem.


On 20/10/13 06:41, Dave Taht wrote:
+ sync with openwrt
+ dnsmasq 2.67rc4
+ get_cycles() and /dev/random fixes
+ mild firewall changes
+ actually sort of tested
-  sysupgrade still busted
- didn't package the jitter rng

The simple expedient of putting a script in /etc/rc.local to restart
pimd, minissdpd, and dnsmasq 60 seconds after boot appears to get us a
working dhcp/dns on the wifi interfaces once again.

dnsmasq wasn't busted, it was how it interfaces to netifd. the march
down to something deployable resumes with rc4.

This is the first test that I know of, of some of the RNG fixes
upstream, notably the mips code does the right thing with a highly
optimized "get_cycles()".

There are two changes to the firewall code

1) There has been a long-standing error in not blocking port 161
(snmp) from the outside world. It is now blocked by default.

Although I am not aware of any exploits of this (besides the
information leakage) I would recommend blocking this port by default
on your existing builds, also, or disabling the snmp daemon entirely
if you do not use it.

2) Usage of the "pattern matching syntax" on various firewall rules.

Instead of 3 rules for se00,sw00,sw10, and 4 for gw00,gw10,gw01,gw11
there are now 1 rule for s+ and one rule for gw+

This does not show up in the web interface correctly. I'd also like to
get to a more efficient rule set for the blocked ports, perhaps with
ipset...

...

It's sort of my hope that with these fixes that the march towards a
stable release can resume, and we get some fresh shiny new bugs out of
this.

Upcoming next are a revised version of pie, more random number fixes,
and I forget what else.


3)


_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel



_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel





--------------000706030307000701030406--