Labels

Showing posts with label Edgerouter-12. Show all posts
Showing posts with label Edgerouter-12. Show all posts

Tuesday, July 22, 2025

Added Some Collections to the FLINT 2 Router

I decided to add a way to gather statistics on the wireless connection to Connect in my apartment.  I found that luci-app-statistics uses collectd to gather system statistics and uses rrdtool to display them.  I installed luci-app-statistics and collectd on the FLINT2 Router.  Since I have an MQTT server running on port 1883 of the EXP-PiHole RPi, I decided to open up icmp to WAN (port 10) and WAN2 (port 9) on Edgerouter-12.  I then added passthrough of MQTT (1883) to WAN (port 10) on Edgerouter-12 to EXP-PiHole.  I am not sure if WAN2 will pick up the same passthrough message to port 1883; that I will have to test separately. I also installed the following packages on FLINT2: collectd-mod-cpu, collectd-mod-ethstat, collectd-mod-interface, collectd-mod-ipstatistics, collectd-mod-iwinfo, collectd-mod-load, collectd-mod-memory, collectd-mod-mqtt, collectd-mod-network, collectd-mod-rrdtool, collectd-mod-thermal, collectd-mod-uptime, and collectd-mod-wireless.

Update: I have removed the collectd items from FLINT2 because it appeared that it was slowing down the download/upload throughput.

Friday, April 11, 2025

Project #33 - Moving the DHCP and DNS over to PiHole

This is one project that has stuck in my craw for a number of years.  I am now in a situation where I am about to change out my network to be in two pieces.  I have enough computers to think about a centralized DHCP/DNS server for the network.  I have used PiHole in the past but now I want to make that the default for all of the routers in my network.  The rub is, I have all of these vlans that need attention when I am giving out IP addresses.  This will be an effort to consolidate the IP gathering and DNS entries into one location that is easier to control.  Some specifics of what I want to do are:

  • setup my Netgear switches to force certain IP ranges to certain vlans
  • use PiHole to issue DHCP IP addresses tied to their MAC addresses
  • if the MAC address is unknown, push it to a guest network
  • include both the FLINT1 and FLINT2 routers in the mix
  • modify my FLINT2 setup to have one guest network vlan that is passthrough

Monday, November 27, 2023

I have re-arranged the HomeLab rack to allow for four different systems

 I decided to change out the HomeLab rack and concentrate on four sub-systems: (1) Experiment Pod; (2) Proxmox; (3) Edgerouter-12/M4100-26g; and (4) Monitor sub-system.  Each one of these sub-systems can now be independently booted up and used.

I added a GS108Tv3 managed switch to the top of the rack so that I could change out the cables going from the HomeLab rack to only need one connection to the external GS108Tv2 switch behind the rack.  This frees up some of the ports on that switch to be used for experiments on the table.  The ExPod is now behind an Edgerouter-X connected to that top switch, with all components able to be turned off at the same time from a single switch on the power switch panel.  The Proxmox server is also connected to that top switch for all of its external ports and is powered through a single switch on the power switch panel.  The Edgerouter-12/M4100-26g combination is powered down from a single switch on the same power switch panel; external connections go through the top switch.  The monitor sub-system is also turned on and off through a single switch on the power switch panel and is behind an Edgerouter-X connected to the top switch.

I also added an RGB led lighting on the sides of the HomeLab rack.

Issue: the vlans for server admin and servers still require the Edgerouter-12 to be running since the DHCP servers are on that device.  This will need to be dealt with int the future.