1 Apr
2022
1 Apr
'22
2:38 a.m.
the front door computer is unreachable, because some network switch between
it and the server is not working right i guess... either one of the switches
upstairs (in the "public computer lab") or something in the network cage.
I had to leave before i was able to figure out what was wrong and I can't
access the front door computer from theh network, so I don't know whether card
access will work although now that i think about it, it probably does work.
the wifi was being really really really slow tonight (thursday night) and
Arthur and I were trying to figure out what was wrong, and Yar and Marc helped
remotely, but we never figured out where the problem was, and I didn't realize
until i had to leave that the front door computer is entirely inaccessible.
$ ping 100.64.64.11
"No route to host"
even though i power cycled it and it's getting a link light. I don't actually
know where the other end of its ethernet cable is but since the front door
computer is important to security and accessibility, this worries me.
Can someone who understands the building's network please try to fix this ASAP?
-jake
1 Apr
1 Apr
2:53 a.m.
New subject: [sudo-discuss] help! network is down at Omni!
We ran some tests and it seems like there is very high latency (around 200
ms) and packet loss (18% was the lowest I saw) on the wifi.
This is based on flood pinging a wifi-connected laptop from the gateway
(saros).
There appeared to be no such issues going from saros over ethernet to a
laptop or from saros over ethernet to the wifi access points.
This is very confusing because even though the APs have a central
controller, the traffic from the AP's clients does not flow through the
controller so something would have to be wrong with multiple APs at the
same time. Jake tested from both ends of the building to ensure it wasn't
just one AP.
Unless there is massive wifi interference at Omni or a malicious wifi
device, I can't think of what it could be.
Then of course there is the issue of the unreachable ethernet-connected
door computer. No idea there. More debugging needed to get to the bottom of
this.
On Fri, Apr 1, 2022 at 9:39 AM Jake via sudo-discuss <
sudo-discuss(a)sudoroom.org> wrote:
the front door computer is unreachable, because some
network switch between
it and the server is not working right i guess... either one of the
switches
upstairs (in the "public computer lab") or something in the network cage.
I had to leave before i was able to figure out what was wrong and I can't
access the front door computer from theh network, so I don't know whether
card
access will work although now that i think about it, it probably does work.
the wifi was being really really really slow tonight (thursday night) and
Arthur and I were trying to figure out what was wrong, and Yar and Marc
helped
remotely, but we never figured out where the problem was, and I didn't
realize
until i had to leave that the front door computer is entirely inaccessible.
$ ping 100.64.64.11
"No route to host"
even though i power cycled it and it's getting a link light. I don't
actually
know where the other end of its ethernet cable is but since the front door
computer is important to security and accessibility, this worries me.
Can someone who understands the building's network please try to fix this
ASAP?
-jake
_______________________________________________
sudo-discuss mailing list -- sudo-discuss(a)sudoroom.org
To unsubscribe send an email to sudo-discuss-leave(a)sudoroom.org
More options at
https://sudoroom.org/lists/postorius/lists/sudo-discuss.sudoroom.org/
2:24 p.m.
New subject: [sudo-discuss] Re: help! network is down at Omni!
What is the consequence until this is resolved? Is the local WiFi usable?
Jake, did you say the access system is still functional?
*Andrew R Gross, (he/him)*
412.657.5332 - shrad.org <http://www.shrad.org>
On Fri, Apr 1, 2022 at 2:53 AM Marc Juul via sudo-discuss <
sudo-discuss(a)sudoroom.org> wrote:
We ran some tests and it seems like there is very high
latency (around 200
ms) and packet loss (18% was the lowest I saw) on the wifi.
This is based on flood pinging a wifi-connected laptop from the gateway
(saros).
There appeared to be no such issues going from saros over ethernet to a
laptop or from saros over ethernet to the wifi access points.
This is very confusing because even though the APs have a central
controller, the traffic from the AP's clients does not flow through the
controller so something would have to be wrong with multiple APs at the
same time. Jake tested from both ends of the building to ensure it wasn't
just one AP.
Unless there is massive wifi interference at Omni or a malicious wifi
device, I can't think of what it could be.
Then of course there is the issue of the unreachable ethernet-connected
door computer. No idea there. More debugging needed to get to the bottom of
this.
On Fri, Apr 1, 2022 at 9:39 AM Jake via sudo-discuss <
sudo-discuss(a)sudoroom.org> wrote:
the front door computer is unreachable, because
some network switch
between
it and the server is not working right i guess... either one of the
switches
upstairs (in the "public computer lab") or something in the network cage.
I had to leave before i was able to figure out what was wrong and I can't
access the front door computer from theh network, so I don't know whether
card
access will work although now that i think about it, it probably does
work.
the wifi was being really really really slow tonight (thursday night) and
Arthur and I were trying to figure out what was wrong, and Yar and Marc
helped
remotely, but we never figured out where the problem was, and I didn't
realize
until i had to leave that the front door computer is entirely
inaccessible.
$ ping 100.64.64.11
"No route to host"
even though i power cycled it and it's getting a link light. I don't
actually
know where the other end of its ethernet cable is but since the front door
computer is important to security and accessibility, this worries me.
Can someone who understands the building's network please try to fix this
ASAP?
-jake
_______________________________________________
sudo-discuss mailing list -- sudo-discuss(a)sudoroom.org
To unsubscribe send an email to sudo-discuss-leave(a)sudoroom.org
More options at
https://sudoroom.org/lists/postorius/lists/sudo-discuss.sudoroom.org/
_______________________________________________
sudo-discuss mailing list -- sudo-discuss(a)sudoroom.org
To unsubscribe send an email to sudo-discuss-leave(a)sudoroom.org
More options at
https://sudoroom.org/lists/postorius/lists/sudo-discuss.sudoroom.org/
847
days inactive
847
days old
2 comments
3 participants
participants (3)
-
Andrew R Gross -
Jake -
Marc Juul