#arednmesh — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #arednmesh, aggregated by home.social.
-
@AJ9BM those "SDR" are a power supply line. We have 12, 24 and 48V on that rail ready to power APRS radio, and POE switches for #arednmesh :)
-
@AJ9BM those "SDR" are a power supply line. We have 12, 24 and 48V on that rail ready to power APRS radio, and POE switches for #arednmesh :)
-
@AJ9BM those "SDR" are a power supply line. We have 12, 24 and 48V on that rail ready to power APRS radio, and POE switches for #arednmesh :)
-
@AJ9BM those "SDR" are a power supply line. We have 12, 24 and 48V on that rail ready to power APRS radio, and POE switches for #arednmesh :)
-
@AJ9BM those "SDR" are a power supply line. We have 12, 24 and 48V on that rail ready to power APRS radio, and POE switches for #arednmesh :)
-
This week I'm combining data nerd homelab metrics with @grafana and #arednmesh #hamradio goodness, by setting up @Prometheus collection performance metrics of your AREDN node and displaying them in Grafana! Homelabbers and hams unite!
-
This week I'm combining data nerd homelab metrics with @grafana and #arednmesh #hamradio goodness, by setting up @Prometheus collection performance metrics of your AREDN node and displaying them in Grafana! Homelabbers and hams unite!
-
-
-
-
-
@T_X I still have my #arednmesh routers. You can make them play together if you change the #ssid of the #hsmmmesh routers
-
@T_X I still have my #arednmesh routers. You can make them play together if you change the #ssid of the #hsmmmesh routers
-
@T_X I still have my #arednmesh routers. You can make them play together if you change the #ssid of the #hsmmmesh routers
-
@T_X I still have my #arednmesh routers. You can make them play together if you change the #ssid of the #hsmmmesh routers
-
@lid So how is it going exploring the mesh ? :)
-
@lid So how is it going exploring the mesh ? :)
-
Ce matin c'est la grande journée des mises à jour de notre réseau. Il est possible que certains systèmes soient indisponibles quelques minutes lors des opérations de maintenance.
Firewall, routeur, switch, radios... Tout y passe!
#hamradio #radioamateur #mesh #aredn #arednmesh #maintenance #IT
-
I must admit that I've been "lazy" to learn #Ansible ...
I was maintaining 25 #AREDN mesh nodes all by hand even if I had previously made needed script to do everything. The script was working, but needed tweaking. Tonight I took a shot at tweaking it and make sure that only critical nodes are not updated automatically.
Result is 25nodes updated with only one password input in less than an hour! Not bad!
VE2ATU network is now fully updated to latest release.
-
I must admit that I've been "lazy" to learn #Ansible ...
I was maintaining 25 #AREDN mesh nodes all by hand even if I had previously made needed script to do everything. The script was working, but needed tweaking. Tonight I took a shot at tweaking it and make sure that only critical nodes are not updated automatically.
Result is 25nodes updated with only one password input in less than an hour! Not bad!
VE2ATU network is now fully updated to latest release.
-
I must admit that I've been "lazy" to learn #Ansible ...
I was maintaining 25 #AREDN mesh nodes all by hand even if I had previously made needed script to do everything. The script was working, but needed tweaking. Tonight I took a shot at tweaking it and make sure that only critical nodes are not updated automatically.
Result is 25nodes updated with only one password input in less than an hour! Not bad!
VE2ATU network is now fully updated to latest release.
-
Has anyone else ever setup an openstreetmap tile sever for #AREDN #AREDNMESH purposes? I tested with the northeast region of the US and was able to get it working in under a couple of hours, so I expanded to North America and I'm in about 12 hours already and its still working away. I hate to think how long it would take to render all the tiles on the globe on a raspberry pi. Good thing I'm on an SSD. #OSM
-
Has anyone else ever setup an openstreetmap tile sever for #AREDN #AREDNMESH purposes? I tested with the northeast region of the US and was able to get it working in under a couple of hours, so I expanded to North America and I'm in about 12 hours already and its still working away. I hate to think how long it would take to render all the tiles on the globe on a raspberry pi. Good thing I'm on an SSD. #OSM
-
Has anyone else ever setup an openstreetmap tile sever for #AREDN #AREDNMESH purposes? I tested with the northeast region of the US and was able to get it working in under a couple of hours, so I expanded to North America and I'm in about 12 hours already and its still working away. I hate to think how long it would take to render all the tiles on the globe on a raspberry pi. Good thing I'm on an SSD. #OSM
-
My PR to #arednmesh has been merged into the repository earlier this week as commit 74810d01b4a54bfc2809c97bda5ca048f9eb12fe.
It fixed a bug that was introduced during the code translation to LUA.
The bug: It was not possible anymore to open ports range from the GUI in the port forwarding area.
Reason 1: REGEX has hyphen not properly escaped.
Reason 2 : Port range validation logic was reversed. The code was validating a port range having an higher start point than the ending point.
Along those 2 fixes and some discussions with dev team, another tweak has been made in the GUI code to escape blank space if any in front of the port range so the value is properly reused later for internal uses.
This was my first code contribution to AREDN Mesh. I already look forward to help when my skills allows to.
-
My PR to #arednmesh has been merged into the repository earlier this week as commit 74810d01b4a54bfc2809c97bda5ca048f9eb12fe.
It fixed a bug that was introduced during the code translation to LUA.
The bug: It was not possible anymore to open ports range from the GUI in the port forwarding area.
Reason 1: REGEX has hyphen not properly escaped.
Reason 2 : Port range validation logic was reversed. The code was validating a port range having an higher start point than the ending point.
Along those 2 fixes and some discussions with dev team, another tweak has been made in the GUI code to escape blank space if any in front of the port range so the value is properly reused later for internal uses.
This was my first code contribution to AREDN Mesh. I already look forward to help when my skills allows to.
-
My PR to #arednmesh has been merged into the repository earlier this week as commit 74810d01b4a54bfc2809c97bda5ca048f9eb12fe.
It fixed a bug that was introduced during the code translation to LUA.
The bug: It was not possible anymore to open ports range from the GUI in the port forwarding area.
Reason 1: REGEX has hyphen not properly escaped.
Reason 2 : Port range validation logic was reversed. The code was validating a port range having an higher start point than the ending point.
Along those 2 fixes and some discussions with dev team, another tweak has been made in the GUI code to escape blank space if any in front of the port range so the value is properly reused later for internal uses.
This was my first code contribution to AREDN Mesh. I already look forward to help when my skills allows to.
-
My PR to #arednmesh has been merged into the repository earlier this week as commit 74810d01b4a54bfc2809c97bda5ca048f9eb12fe.
It fixed a bug that was introduced during the code translation to LUA.
The bug: It was not possible anymore to open ports range from the GUI in the port forwarding area.
Reason 1: REGEX has hyphen not properly escaped.
Reason 2 : Port range validation logic was reversed. The code was validating a port range having an higher start point than the ending point.
Along those 2 fixes and some discussions with dev team, another tweak has been made in the GUI code to escape blank space if any in front of the port range so the value is properly reused later for internal uses.
This was my first code contribution to AREDN Mesh. I already look forward to help when my skills allows to.
-
My PR to #arednmesh has been merged into the repository earlier this week as commit 74810d01b4a54bfc2809c97bda5ca048f9eb12fe.
It fixed a bug that was introduced during the code translation to LUA.
The bug: It was not possible anymore to open ports range from the GUI in the port forwarding area.
Reason 1: REGEX has hyphen not properly escaped.
Reason 2 : Port range validation logic was reversed. The code was validating a port range having an higher start point than the ending point.
Along those 2 fixes and some discussions with dev team, another tweak has been made in the GUI code to escape blank space if any in front of the port range so the value is properly reused later for internal uses.
This was my first code contribution to AREDN Mesh. I already look forward to help when my skills allows to.
-
A few weeks, I noticed a bug in AREDN mesh V3.22.6.0 when I wanted to change some settings from the "Port Forwarding, DHCP, and Services" section. Reverting to V3.22.1.0 made everything functional agin.
It took sometimes to figure out was exactly was the bug. When I narrowed it to the port ranges inside the port forwarding section, it has been indicated inside the original ticket.
Time past and it was causing more and more troubles to our setup. So this morning I took an hour to look at the code. Not being a LUA dev, I wanted this bug fixed and if I may be of any help, better help out!
Starting at V3.22.1.0 to understand the logic behind the scene, I found out how it works. I took time to concentrate on the
validate_port_rangefunction.Between V3.22.1.0 and V3.22.6.0, the code has been rewritten in LUA, so I got the intuition that this rewrite might a brought in some problems.
Moving to main branch (V3.22.12.0 (Latest)) , to ensure not working on obsolete code, I found out the
validate_port_rangefunction and read the code. So I found out a first mistake while evaluation if the range is properly indicated (ex: 1000-2000 = Valid / 2000-1000 = Invalid). Simple and easy to fix.Made the changes on my lab device and still no joy! So what is the worst thing (IMHO) to convert from one language to another... ? REGEX! So I made a quick search to 'learn' how REGEX are working in LUA to get some answer. Opened up a JDoodle tab and started to play with the REGEX line until the various tests with valid and invalid ranges returns proper results.
Pushed the new REGEX in the lab device and Bingo! It is now working properly.
Arranged a PR (First PR on the project), submitted it and now waiting for it to be reviewed and merged. In the hope I didn't break something else!
Once included into
nightly, our 2 gateways requiring port ranges will be back to normal operations and so will be our VoIP servers behind them!#AmateurRadio #AREDN #AREDNMesh #LUA #Bugs #VoIP #Scriptkiddy #OpenSource #FirstPullRequest
-
A few weeks, I noticed a bug in AREDN mesh V3.22.6.0 when I wanted to change some settings from the "Port Forwarding, DHCP, and Services" section. Reverting to V3.22.1.0 made everything functional agin.
It took sometimes to figure out was exactly was the bug. When I narrowed it to the port ranges inside the port forwarding section, it has been indicated inside the original ticket.
Time past and it was causing more and more troubles to our setup. So this morning I took an hour to look at the code. Not being a LUA dev, I wanted this bug fixed and if I may be of any help, better help out!
Starting at V3.22.1.0 to understand the logic behind the scene, I found out how it works. I took time to concentrate on the
validate_port_rangefunction.Between V3.22.1.0 and V3.22.6.0, the code has been rewritten in LUA, so I got the intuition that this rewrite might a brought in some problems.
Moving to main branch (V3.22.12.0 (Latest)) , to ensure not working on obsolete code, I found out the
validate_port_rangefunction and read the code. So I found out a first mistake while evaluation if the range is properly indicated (ex: 1000-2000 = Valid / 2000-1000 = Invalid). Simple and easy to fix.Made the changes on my lab device and still no joy! So what is the worst thing (IMHO) to convert from one language to another... ? REGEX! So I made a quick search to 'learn' how REGEX are working in LUA to get some answer. Opened up a JDoodle tab and started to play with the REGEX line until the various tests with valid and invalid ranges returns proper results.
Pushed the new REGEX in the lab device and Bingo! It is now working properly.
Arranged a PR (First PR on the project), submitted it and now waiting for it to be reviewed and merged. In the hope I didn't break something else!
Once included into
nightly, our 2 gateways requiring port ranges will be back to normal operations and so will be our VoIP servers behind them!#AmateurRadio #AREDN #AREDNMesh #LUA #Bugs #VoIP #Scriptkiddy #OpenSource #FirstPullRequest
-
A few weeks, I noticed a bug in AREDN mesh V3.22.6.0 when I wanted to change some settings from the "Port Forwarding, DHCP, and Services" section. Reverting to V3.22.1.0 made everything functional again.
It took sometimes to figure out was exactly was the bug. When I narrowed it to the port ranges inside the port forwarding section, it has been indicated inside the original ticket.
Time past and it was causing more and more troubles to our setup. So this morning I took an hour to look at the code. Not being a LUA dev, I wanted this bug fixed and if I may be of any help, better help out!
Starting at V3.22.1.0 to understand the logic behind the scene, I found out how it works. I took time to concentrate on the
validate_port_rangefunction.Between V3.22.1.0 and V3.22.6.0, the code has been rewritten in LUA, so I got the intuition that this rewrite might a brought in some problems.
Moving to main branch (V3.22.12.0 (Latest)) , to ensure not working on obsolete code, I found out the
validate_port_rangefunction and read the code. So I found out a first mistake while evaluation if the range is properly indicated (ex: 1000-2000 = Valid / 2000-1000 = Invalid). Simple and easy to fix.Made the changes on my lab device and still no joy! So what is the worst thing (IMHO) to convert from one language to another... ? REGEX! So I made a quick search to 'learn' how REGEX are working in LUA to get some answer. Opened up a JDoodle tab and started to play with the REGEX line until the various tests with valid and invalid ranges returns proper results.
Pushed the new REGEX in the lab device and Bingo! It is now working properly.
Arranged a PR (First PR on the project), submitted it and now waiting for it to be reviewed and merged. In the hope I didn't break something else!
Once included into
nightly, our 2 gateways requiring port ranges will be back to normal operations and so will be our VoIP servers behind them!#AmateurRadio #AREDN #AREDNMesh #LUA #Bugs #VoIP #Scriptkiddy #OpenSource #FirstPullRequest
-
Today has been not been as productive as I wanted, but it has been a good one!
2 years ago, I started a project called AEWS, to collect data from various public sources using #Python with the goal to retrieve power outages, road closures and weather. Once retrieve, the data is formatted into 2 formats. The report format is a text file using markdown format and there is also the #aprs format to send abnormalities over RF in a group messages for all #amateurradio around to get the information if they wished to.
The goal for that little piece of software is to automate sending important information to operators deployed in #emcomm operations.
Last year, I was looking at a way to get some helps on some coming projects from fellow hams that are not coders but know enough to give a hand. I then found #nodered . After a bit of testing, Node-Red has been adopted as the official way to make things happen at our association.
So since then, we are migrating everything possible to Node-Red. Few weeks ago, I started to migrate AEWS toward Node-Red and more urgent projects came in, so it has been set aside. Today I've been able to put a bit of work into AEWS.
Starting from scratch or almost, I've took care to make it modular and integrated it with our #mattermost and #zabbix instances running out off our #aredn mesh. We now can receive reports on MatterMost, on our web portal and receive abnormalities through RF on APRS and via review them through Zabbix dashboard. Also small part of the data are available through our #TAK server, more work is required for that part to bring full data into it.
Most part of the power outage system is done. Few tweaks and getting site specific status to be shown on all platform and it can be called done. Maybe it will be done by the week-end so another module can be attacked before end of the year!
Cheers to productive and unproductive days!
-
Today has been not been as productive as I wanted, but it has been a good one!
2 years ago, I started a project called AEWS, to collect data from various public sources using #Python with the goal to retrieve power outages, road closures and weather. Once retrieve, the data is formatted into 2 formats. The report format is a text file using markdown format and there is also the #aprs format to send abnormalities over RF in a group messages for all #amateurradio around to get the information if they wished to.
The goal for that little piece of software is to automate sending important information to operators deployed in #emcomm operations.
Last year, I was looking at a way to get some helps on some coming projects from fellow hams that are not coders but know enough to give a hand. I then found #nodered . After a bit of testing, Node-Red has been adopted as the official way to make things happen at our association.
So since then, we are migrating everything possible to Node-Red. Few weeks ago, I started to migrate AEWS toward Node-Red and more urgent projects came in, so it has been set aside. Today I've been able to put a bit of work into AEWS.
Starting from scratch or almost, I've took care to make it modular and integrated it with our #mattermost and #zabbix instances running out off our #aredn mesh. We now can receive reports on MatterMost, on our web portal and receive abnormalities through RF on APRS and via review them through Zabbix dashboard. Also small part of the data are available through our #TAK server, more work is required for that part to bring full data into it.
Most part of the power outage system is done. Few tweaks and getting site specific status to be shown on all platform and it can be called done. Maybe it will be done by the week-end so another module can be attacked before end of the year!
Cheers to productive and unproductive days!
-
Today has been not been as productive as I wanted, but it has been a good one!
2 years ago, I started a project called AEWS, to collect data from various public sources using #Python with the goal to retrieve power outages, road closures and weather. Once retrieve, the data is formatted into 2 formats. The report format is a text file using markdown format and there is also the #aprs format to send abnormalities over RF in a group messages for all #amateurradio around to get the information if they wished to.
The goal for that little piece of software is to automate sending important information to operators deployed in #emcomm operations.
Last year, I was looking at a way to get some helps on some coming projects from fellow hams that are not coders but know enough to give a hand. I then found #nodered . After a bit of testing, Node-Red has been adopted as the official way to make things happen at our association.
So since then, we are migrating everything possible to Node-Red. Few weeks ago, I started to migrate AEWS toward Node-Red and more urgent projects came in, so it has been set aside. Today I've been able to put a bit of work into AEWS.
Starting from scratch or almost, I've took care to make it modular and integrated it with our #mattermost and #zabbix instances running out off our #aredn mesh. We now can receive reports on MatterMost, on our web portal and receive abnormalities through RF on APRS and via review them through Zabbix dashboard. Also small part of the data are available through our #TAK server, more work is required for that part to bring full data into it.
Most part of the power outage system is done. Few tweaks and getting site specific status to be shown on all platform and it can be called done. Maybe it will be done by the week-end so another module can be attacked before end of the year!
Cheers to productive and unproductive days!
-
Today has been not been as productive as I wanted, but it has been a good one!
2 years ago, I started a project called AEWS, to collect data from various public sources using #Python with the goal to retrieve power outages, road closures and weather. Once retrieve, the data is formatted into 2 formats. The report format is a text file using markdown format and there is also the #aprs format to send abnormalities over RF in a group messages for all #amateurradio around to get the information if they wished to.
The goal for that little piece of software is to automate sending important information to operators deployed in #emcomm operations.
Last year, I was looking at a way to get some helps on some coming projects from fellow hams that are not coders but know enough to give a hand. I then found #nodered . After a bit of testing, Node-Red has been adopted as the official way to make things happen at our association.
So since then, we are migrating everything possible to Node-Red. Few weeks ago, I started to migrate AEWS toward Node-Red and more urgent projects came in, so it has been set aside. Today I've been able to put a bit of work into AEWS.
Starting from scratch or almost, I've took care to make it modular and integrated it with our #mattermost and #zabbix instances running out off our #aredn mesh. We now can receive reports on MatterMost, on our web portal and receive abnormalities through RF on APRS and via review them through Zabbix dashboard. Also small part of the data are available through our #TAK server, more work is required for that part to bring full data into it.
Most part of the power outage system is done. Few tweaks and getting site specific status to be shown on all platform and it can be called done. Maybe it will be done by the week-end so another module can be attacked before end of the year!
Cheers to productive and unproductive days!
-
Today has been not been as productive as I wanted, but it has been a good one!
2 years ago, I started a project called AEWS, to collect data from various public sources using #Python with the goal to retrieve power outages, road closures and weather. Once retrieve, the data is formatted into 2 formats. The report format is a text file using markdown format and there is also the #aprs format to send abnormalities over RF in a group messages for all #amateurradio around to get the information if they wished to.
The goal for that little piece of software is to automate sending important information to operators deployed in #emcomm operations.
Last year, I was looking at a way to get some helps on some coming projects from fellow hams that are not coders but know enough to give a hand. I then found #nodered . After a bit of testing, Node-Red has been adopted as the official way to make things happen at our association.
So since then, we are migrating everything possible to Node-Red. Few weeks ago, I started to migrate AEWS toward Node-Red and more urgent projects came in, so it has been set aside. Today I've been able to put a bit of work into AEWS.
Starting from scratch or almost, I've took care to make it modular and integrated it with our #mattermost and #zabbix instances running out off our #aredn mesh. We now can receive reports on MatterMost, on our web portal and receive abnormalities through RF on APRS and via review them through Zabbix dashboard. Also small part of the data are available through our #TAK server, more work is required for that part to bring full data into it.
Most part of the power outage system is done. Few tweaks and getting site specific status to be shown on all platform and it can be called done. Maybe it will be done by the week-end so another module can be attacked before end of the year!
Cheers to productive and unproductive days!
-
Tinkering together a mobile #arednmesh go box. Harbor Freight ammo box, cheap 6Ah LiFEPo4 battery, a $20 solar charge controller, a 12->24v converter, 4 port POE injector and some ethernet bulkhead connectors. Will add fuses, switches, buttons, a USB charger, and a hookup for solar panel (I have a small 10W and a larger 100W). Pictured with my budget TPLINK CPE210. #projects
-
Tinkering together a mobile #arednmesh go box. Harbor Freight ammo box, cheap 6Ah LiFEPo4 battery, a $20 solar charge controller, a 12->24v converter, 4 port POE injector and some ethernet bulkhead connectors. Will add fuses, switches, buttons, a USB charger, and a hookup for solar panel (I have a small 10W and a larger 100W). Pictured with my budget TPLINK CPE210. #projects
-
Tinkering together a mobile #arednmesh go box. Harbor Freight ammo box, cheap 6Ah LiFEPo4 battery, a $20 solar charge controller, a 12->24v converter, 4 port POE injector and some ethernet bulkhead connectors. Will add fuses, switches, buttons, a USB charger, and a hookup for solar panel (I have a small 10W and a larger 100W). Pictured with my budget TPLINK CPE210. #projects
