Re: [Cerowrt-devel] kleinrock's work on queue theory is out of print

2020-05-11 Thread Daniel Ezell
Thanks to Archive.org's National Emergency Library both volumes of Kleinrock are available for free with no queue. Volume 1 and Volume 2 On

Re: [Cerowrt-devel] expressobin

2018-07-31 Thread Daniel Ezell
$79 for another gig of RAM http://www.globalscaletechnologies.com/p-72-marvell-espressobin.aspx On Tue, Jul 31, 2018 at 7:54 PM, Dave Taht wrote: > 50 bucks. Dual core arm. 3 "real" ethernet ports? > > https://www.amazon.com/Globalscale-Technologies-Inc- > SBUD102-ESPRESSObin/dp/B06Y3V2FBK/ref=s

Re: [Cerowrt-devel] Copy of cerowrt 3.10.50-1

2015-10-22 Thread Daniel Ezell
If you have a copy of the 3800 build, I'd also appreciate it. On Oct 22, 2015 7:05 PM, "Rich Brown" wrote: > I have one. Let me set up a mirror. > > Rich > > > On Oct 22, 2015, at 6:58 PM, Richard Smith wrote: > > > > snapon doesn't seem to be responding. Does anyone have a copy of the > 7300v2

Re: [Cerowrt-devel] [Bug #442] status?

2014-08-16 Thread Daniel Ezell
No drops here since installing. Looks great to me. Daniel On Aug 16, 2014 11:23 AM, "Dave Taht" wrote: > I am told that several sites that had severe problems with wifi > hanging have now been up, > for over 2 weeks, without problems, with the 3.10.50-1 release of cerowrt. > > How is everyone els

Re: [Cerowrt-devel] going back to the default multicast rate on wifi

2014-02-10 Thread Daniel Ezell
Thanks for the Comcast release. It's nice having native ipv6. Strange though, I have business class and they say they don't yet support ipv6. I'm getting a /128 yet my connected devices all get addresses, too. Multicast has been seamless to me. The list includes a Macbook pro mid 2010, nexus 4, iP

Re: [Cerowrt-devel] atomic route updates?

2013-05-05 Thread Daniel Ezell
If minidlna will compile, and you have the time, could you include it in the next release? On May 5, 2013 6:28 AM, "Dave Taht" wrote: > On Thu, Apr 25, 2013 at 8:05 AM, Robert Bradley > wrote: > > On 24/04/13 16:46, Dave Taht wrote: > >> > >> There is a possibly related bug being discussed on th