Hi all,
Does anyone object to me re-purposing two of the picam raspis for use with the two big TVs around?
Not sure what to display on them yet, but I'd rather use a pi than a desktop PC for sure.
Ideas?
R
Hokay! No sweat. I know others found them useful as well.
N/m :)
R
--
You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hacksp...@googlegroups.com.
There's always the fireplace channel, that's pretty awesome in winter.
Plus, I'm guessing by the fact that at least one of the TVs has fans in it, there would be realistic warmth as well :)
R
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
Do we have any numbers on maximum concurrent viewers to help with building v2?
What did folks use them for? Pure occupancy detection or seeing specifically who's around?
I too miss the cameras for all the above reasons.
Used to access them at least once per day.
Richard
Easy enough to fix apparently just put it behind a password.
There has already been extensive discussion about it and I don't want to revisit it, I just want to reinstate it in a compliant way that is also useful.
Also, considering how much bandwidth live video takes it's important to try to figure out some usage patterns. If we only need to serve (say maybe) 5 concurrent users, that would be easier than 100. (I dunno, I like proper live video, maybe not for the lost and found, but for general areas...)
R
I suppose it depends on what’s involved, but think there are security benefits of having a more continuous stream.
Sent from my Windows 10 phone
From: Ian Petrie
Sent: 07 September 2016 15:57
To: Reading Hackspace
Subject: Re: [RDG-Hack] Re: Picams
I was happy enough with regular picture updates. No need for video - though I appreciated video for the outside camera.
Considering bandwidth only, from a few angles:
Important to consider the different use cases per camera for bandwidth. I think a camera on the 3 week shelves (and even on other storage areas) would be worth having, long term – especially given the level of debate around this. However a snapshot per hour would be plenty to make this as useful as it can be in my opinion. So the bandwidth cost is negligible, we’ve already sunk the cost of the software stack from the other cameras, so when considering if it’s worth having, it’s versus just the cost of a pi and a little more of the same maintenance.
I assume we can set the broadcast framerate independently of the capture to disk storage?
It should be possible for each pi to throttle its frequency of frames broadcast and/or captured if the measured amount of movement in front of the camera is below a set threshold indicating no people are present. Doing this may allow us to more freely ramp up the frame rate when things get interesting, within the same bandwidth budget.
Similarly, especially if we have access controlled via password, we can do useful things to control bandwidth usage – no point broadcasting at high bandwidth if zero people are watching.
Finally, if the bandwidth cost of having the kind of live video framerate that gives a sense of ‘being there’ is hugely higher than the cost of providing snapshots, we could implement micropayment to fund it directly (paypal donate button honesty box is a minimum viable product suggestion).
From: reading-...@googlegroups.com [mailto:reading-...@googlegroups.com] On Behalf Of Ryan .
Sent: 07 September 2016 15:07
To: reading-...@googlegroups.com
Subject: Re: [RDG-Hack] Re: Picams
Easy enough to fix apparently just put it behind a password.
Yep, all that is possible, and along the lines of what I was thinking.
Cool, let's make it go! 99% of the infra is already there, methinks management via puppet/ansible and proper dns/firewall/ip config is needed, plus the actual video bits.
R
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
Best way to prevent it phoning home is to set its default gateway to NULL and/or block its MAC on the firewall.
Oh, and not allowing it access to a speak-and-spell, rotary phone, turntable, sawblade and an umbrella of course.
Please bare in mind: http://securityaffairs.co/wordpress/51726/cyber-crime/ovh-hit-botnet-iot.html
😊
Sent from my Windows 10 phone
From: Laurence Rochfort
Sent: 29 September 2016 07:16
To: Reading Hackspace
Subject: Re: [RDG-Hack] Re: Picams
Best way to prevent it phoning home is to set its default gateway to NULL and/or block its MAC on the firewall.
umbrella?
Oh bog - ignore that, I recognised the reference as soon as I had
pressed send..
Please bare in mind: http://securityaffairs.co/wordpress/51726/cyber-crime/ovh-hit-botnet-iot.html
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hacksp...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
> > email to reading-hackspace+unsubscribe@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
> >
>
> --
> You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
> To unsubscribe from this group and stop receiving emails from it, send an email to reading-hacksp...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hacksp...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hacksp...@googlegroups.com.
Im not at all convinced that when IPv6 is the norm that all IPs will be public facing.
Even if you trust your firewall config you increase your attack surface by exposing your IPs and information associated with them.
NAT and the obfuscation it provides isn't security by itself but it is abstraction and there are admin and security advantages to that.
Also it makes for an admin headache when you get beyond Tonka Toy SME scale setups.
Besides if you take away all the unnecessary complexity how will people justify their pointless overpriced Cisco qualifications?!
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
I think i probably wasn't that clear. I'm watching Breaking Bad and typing :)
I completely agree that NAT isn't security but I do think that even with IPv6 its still a useful admin tool and component in a larger security setup.
It won't help my device on a public network, but on the other side of the coin if Im running a large network then its still useful.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
I believe the point of giving out public facing IPs is that eventually whenever the mainstream finally get shoved onto IPv6 all IPs will be public facing, there won't be any NAT, so use this to get used to it.
Ted,
This is fantastic.
Preliminary testing shows automatic kmalloc alignment changes according to ccNUMA context.
In particular, this reduces the likelihood page allocation starvation (not failure) on very high order NUMA systems thanks to more accurate page size resolution.
However, on SPARC64 I'm seeing a bug where the mobo DRAM boundary is being applied to the CPU card DRAM *only after* the first NUMA boundary interrogation occurs for mobo DRAM. The boundary is correctly applied to CPU DRAM up until this point.
I noticed two things.
__asm_numa_ctx is no longer reentrant.
The above is now used instead of the get_numa_env macro, which of course makes sense.
I can only trigger this on our boxes with 128 CPU threads and 512GB RAM or less. I don't run into it on our M8000 or M9000. I don't have an M7 based system to test against. The entry level M7 super has 1024 CPU threads and 4TB RAM.
We need to come up with a stress test for those.
Would you please try to reproduce on an M7 super and pull my branch to test my asm patch?
Ta!
Ted,
This is fantastic.
Preliminary testing shows automatic kmalloc alignment changes according to ccNUMA context.
In particular, this reduces the likelihood page allocation starvation (not failure) on very high order NUMA systems thanks to more accurate page size resolution.
However, on SPARC64 I'm seeing a bug where the mobo DRAM boundary is being applied to the CPU card DRAM *only after* the first NUMA boundary interrogation occurs for mobo DRAM. The boundary is correctly applied to CPU DRAM up until this point.
I noticed two things.
__asm_numa_ctx is no longer reentrant.
The above is now used instead of the get_numa_env macro, which of course makes sense.
I can only trigger this on our boxes with 128 CPU threads and 512GB RAM or less. I don't run into it on our M8000 or M9000. I don't have an M7 based system to test against. The entry level M7 super has 1024 CPU threads and 4TB RAM.
We need to come up with a stress test for those.
Would you please try to reproduce on an M7 super and pull my branch to test my asm patch?
Ta!
Dude, who's Ted, wtf is numa and where TF do I get a M7?!?!!!??
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
Hmmm.
I should stop reading the forum at work I guess? Its just more interesting than work email.....
Bright? Kinda. That's the great thing about kernel stuff it makes you sound like a wizard :) I couldnt build a decent website if my life depended on it though!!!
Ryan, the power consumption of one of our M7 systems would make Stan look positively frugal!
Stan takes up to 30 kW, you serious?
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
Aaaaah, Stan wins!
A nominal load out for an M9000 is 14kw, but we just moved all our new M7 engineered systems over to PCIe NVME cards so removing all the those rotational HDDs should drop that a lot.
Toby is exactly correct about NUMA. Its all to do with managing different memory speeds, bucket sizes and physical distances from tje CPU.
In the case of SPARC you often have several gigs of dedicated DRAM directly on a Pentium II CPU card. This us much more than intel and managing this stuff for multiple architectures is proving hard.
Anyhoo, Ill stop hijacking this thread.....
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hacksp...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hacksp...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hacksp...@googlegroups.com.
Pentium II?
Computers are complicated.
As for picams, let's hack all the things when I'm back from Rome :)
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hackspace+unsubscribe@googlegroups.com.
Pentium II style card :)
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hacksp...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hacksp...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hacksp...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hacksp...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Reading Hackspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reading-hacksp...@googlegroups.com.