Amateur Radio
DAPNET Status
Node Status
Echolink Status
Hotspot Status
×

DAPNET Node Status

Current Status

Icon Key
PersonalWide Area

×

Node STDVAZ:WY7EMT-7

tinystatus

Packet Services

  • BPQ AXIP
  • BPQ FBB
  • BPQ IP4 Gateway
  • BPQ Telnet
  • BPQ Web Server
  • VHF Port

Last check: 09/16/24 21:20 MST

Incidents

❗  ISSUE: INTERNET OUTAGE at 2024/05/18 18:11 UTC: Cox Internet connection issue in area. Cox claims full service by 1506 MST.

✅  RESOLVED: MANY LINKS DOWN at 2023/12/07 00:28 UTC by Whoever dug up the fiber optic lines.

❗  ISSUE: MANY LINKS DOWN at 2023/12/06 17:36 UTC: Many of our links are down because some genious with a backhoe dug up a fiber line east of here.

×

Brandmeister Hotspot

STATUSCONNECTED TALKGROUPS
Hotspot Online
Hotspot last seen 2024-09-17 04:19:08 UTC
Static: 3104 3156 3176 31566 310999

Dynamic:

Timed: NONE

Weather at WY7EMT
T: 72° F | H: 60% | B: 29.86 inHg | DP: 58° F | Feels: 72° F | Sun: 0.0 w/m2 | UVI: 0.0 | R: 0.0” (0.0 in/hr) | Wind: 113° at 0 MPH (G: 0 MPH) | Wind Chill: 72° F | Updated: 2024-09-16 21:14:29(GMT-0700)
BBS hardware move complete
Tags: hardware, swap, BBS

The hardware move was completed late yesterday afternoon and the node’s been running good for the past 24 hours (with the exception of changing a setting or two and having to restart today).

Bulletins are coming in fine and I haven’t had any issues with mail or node-node connections. I managed to track down the issue with the node losing connection with other nodes. It was, no surprise, the other nodes having dynamic IP addresses. I noticed that linbpq grabs and occassionally updates the AXIP cache with the IP address of the other node’s domain name.

I threw together a script that scrapes the IP address from that file every 5 minutes and places it in a location where my firewall has easy access to it. Every 15 minutes, my firewall re-reads that file and adjusts the firewall to allow traffic in from them.

If you lose connectivity with my node, check for an announcement here (could be that the node’s down for maintenance or a software update). If there’s nothing posted here, then just sit tight for about 15-20 minutes and the nodes should start sending routing requests back and forth again.

If it’s been > 20 minutes, either there’s a power outage or my ISP is having a hiccup.

 Return to Article List
📰 Subscribe via RSS