3:13 p.m.
On Tue, Oct 6, 2020 at 9:22 AM Charles E. Lehner <cel(a)celehner.com> wrote:
I'm unable to reach the room server. Is it down?
Historically we've had two subnets, 192.x and 100.x, served by
different switches. A couple weeks ago, the 192 switch died, and all
of its ethernet connections got (inadvisedly) moved up to the 100
switch. They still won't work without reassigning their IPs, but now
nobody is sure where all the cables go. The router (saros) and door
computer are still reachable because they had 100.x IPs.
I'm guessing you're trying to reach space.local which was
192.168.42.2. Someone needs to go log into its console, reassign it to
a 100.x IP, and update the port forwarding, but nobody's done that
yet. For the record, this machine is also wasting electricity (vastly
overprovisioned for what it does), running Ubuntu 14.04 (EOL April
2019), not hosting anything crucial to omni operations, and I
personally would prefer to replace it entirely, if someone else could
deal with finding the right hardware.
5:17 p.m.
Thanks for that info, Yar.
I maintained a SSB node on space.local: https://sudoroom.org/wiki/Secure_Scuttlebutt
If space.local is being decommissioned, I hope the SSB private key on it
(~ssb/.ssb/secret) will be securely deleted from the device. I have a backup copy of it,
which I can provide if/when we want to set up another SSB node.
About hardware:
When I was at Sudo Room last year, I saw a single-board computer in one of the bins - it
looked like a ODROID-MC1: https://www.hardkernel.com/shop/odroid-mc1-solo/
If that's still there, it could maybe be used for a server, running Armbian:
https://www.armbian.com/odroid-hc1/ It would need a microSD card, and a 5V barrel
connector.
On Tue, 6 Oct 2020 15:13:37 -0700
Yardena Cohen <yardenack(a)gmail.com> wrote:
8 Oct
8 Oct
4:58 p.m.
On Tue, Oct 6, 2020 at 5:17 PM Charles E. Lehner <cel(a)celehner.com> wrote:
Thanks. Next time I'm in sudo, I will try to change the IP address and
look for that odroid. But I'm probably not going to visit during the
pandemic just for that.
If we ever do replace it, I intend to copy all the homedirs, then
/usr/bin/shred the old disk.
18 Oct
18 Oct
4:01 p.m.
Hello,
Today I paid a quick visit to the sudomesh/server room area, and this is my
report back:
a) The paper with the description of each patch panel port is still pinned
to the wall. Image attached to this email.
b) I didn't touch anything, just took a quick visual check, and took a few
photos.
c) For the record I am typing those pp port descriptions here:
Lucent CAT5e Patch Panel
Por 1: Sudoroom Gateway Server NIC 2
Port 20: Mesh Built Server
Port 22: Sudoroom GW Server NIC 1
Port 26: Ballroom 1 (WAP)
Port 27: Ballroom 2 (WAP)
Port 32: 2nd Floor Switch (Switch - WAP)
Port 33: 3D Printing Area
Port 34: Basement (WAP)
Port 35: CCL (WAP)
Port 36: Disco Room (WAP)
Note the WAP Controller that is next to the patch panel needs to be in the
same Public VLAN with the WAPs. There are three white more cables
coming/going from LLens (basement as well), but those are not labeled.
*What is the solution?*
One could be to get a working PoE+ switch on the Public VLAN, and plug the
WAP, and the WAP Controller appliance runs into it. This would be the
easiest.
Second option: That someone configures the current HP switch to handle the
Private and Public VLANs, and carve some ports for each VLAN. This requires
a higher Kung Fu than I can provide.
Thank you,
Daniel
On Tue, Oct 13, 2020 at 7:31 PM Yardena Cohen <yardenack(a)gmail.com> wrote:
11 Oct
11 Oct
9:13 a.m.
On Thu, 8 Oct 2020 16:58:40 -0700
Yardena Cohen <yardenack(a)gmail.com> wrote:
If we ever do replace it, I intend to copy all the
homedirs, then
/usr/bin/shred the old disk.
Sounds good. It's possible the homedir of the ssb user may be outside /home, like in
/var/lib... I don't remember.
1642
days inactive
1654
days old
8 comments
4 participants
participants (4)
-
Charles E. Lehner -
danarauz＠gmail.com -
Marc Juul -
Yardena Cohen