South Seattle College on HamWAN Map
Howdy HamWAN, About a week ago we repaired the client radios at South Seattle College ACS site. There are now two of them. One connected to Beacon S3 and the other connected to Capital Park S2. The HamWAN monitoring system has't picked them up as yet, so dropping this note to ask if someone might give Cacti and the map a nudge, Capital Hill Client: 44.25.131.204 Beacon Client: 44.25.131.233 Router: 44.25.128.113 These operate under the W7ACS call, and *should* have the correct identity and other network management settings. As a second step, we also wish to configure redundant routing of the the subnet at SSC via the router and these two client radios. I assume that to mean that OSPF or other routing protocol would run on the router and announced via the client radios to the network. Thanks Much, Randy, W3RWN Seattle ACS COMT
Randy, The map does not automatically add new nodes. It only updates link data for nodes it already knows about. We’ll take a look at updating the map to include the new link. RE the redundant routing for that subnet. We’ll take a look there and see how we want to get that accomplished and will reach out off list if there’s further questions. Thanks, Nigel
On Feb 16, 2018, at 18:23, Randy Neals <randy@neals.ca> wrote:
Howdy HamWAN,
About a week ago we repaired the client radios at South Seattle College ACS site. There are now two of them. One connected to Beacon S3 and the other connected to Capital Park S2.
The HamWAN monitoring system has't picked them up as yet, so dropping this note to ask if someone might give Cacti and the map a nudge,
Capital Hill Client: 44.25.131.204 Beacon Client: 44.25.131.233 Router: 44.25.128.113
These operate under the W7ACS call, and *should* have the correct identity and other network management settings.
As a second step, we also wish to configure redundant routing of the the subnet at SSC via the router and these two client radios. I assume that to mean that OSPF or other routing protocol would run on the router and announced via the client radios to the network.
Thanks Much, Randy, W3RWN Seattle ACS COMT _______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.net/mailman/listinfo/psdr
Thanks very much Nigel! -Randy On Fri, Feb 16, 2018 at 7:32 PM, Nigel Vander Houwen <nigel@nigelvh.com> wrote:
Randy,
The map does not automatically add new nodes. It only updates link data for nodes it already knows about. We’ll take a look at updating the map to include the new link.
RE the redundant routing for that subnet. We’ll take a look there and see how we want to get that accomplished and will reach out off list if there’s further questions.
Thanks, Nigel
On Feb 16, 2018, at 18:23, Randy Neals <randy@neals.ca> wrote:
Howdy HamWAN,
About a week ago we repaired the client radios at South Seattle College ACS site. There are now two of them. One connected to Beacon S3 and the other connected to Capital Park S2.
The HamWAN monitoring system has't picked them up as yet, so dropping this note to ask if someone might give Cacti and the map a nudge,
Capital Hill Client: 44.25.131.204 Beacon Client: 44.25.131.233 Router: 44.25.128.113
These operate under the W7ACS call, and *should* have the correct identity and other network management settings.
As a second step, we also wish to configure redundant routing of the the subnet at SSC via the router and these two client radios. I assume that to mean that OSPF or other routing protocol would run on the router and announced via the client radios to the network.
Thanks Much, Randy, W3RWN Seattle ACS COMT _______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.net/mailman/listinfo/psdr
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.net/mailman/listinfo/psdr
participants (2)
-
Nigel Vander Houwen -
Randy Neals