Labels

Thursday, August 10, 2023

Using pfSense as a Multi-WAN interface for Monitoring within the HomeLab

 I am back.  I started playing with pfSense in my Proxmox server in order to have a multi-headed connection into vlans within my network.  The purpose is to have an isolated vlan (isolated in the sense that the other vlans cannot get to it) to use as a monitoring point.  My thought is this: let pfSense become the DNS/DHCP source for a number of hardware and VM/LXC components to provide monitoring and automation activities.  I would eventually use Ansible to automate setups within the HomeLab and would use Observium/collectd to monitor the different HW components.  I could also use a component to provide CA capabilities.  The steps needed include:

  1. download a tar.gzip of pfSense Community Edition from the pfSense website
  2. create a VM of pfSense on the Proxmox server
  3. setup the VM to link to an existing vlan in the HomeLab on the WAN side and to an isolated vlan on the LAN side
  4. check the pfSense console to make sure that the ports are configured correctly
  5. add a Raspberry Pi w/SSD to the isolated vlan and bring it up; helps if it is already setup to integrate with the tailscale network
  6. check that the Raspberry Pi can communicate through pfSense to the WAN side and that it has an IP within the subnet of the LAN; this will become the seat of monitoring and automation for the HomeLab
  7. add XRDP to the Raspberry Pi so that I can access the GUI
  8. setup Putty on my Windows laptop as an SSH tunnel to the web interface to pfSense through the Raspberry Pi; repeat with other things that I wish to monitor
Seemed like a good idea at the time.  Not sure why this would be frowned upon security wise.  I just need to be sure that I am always aware of new and clever attacks that might be possible within the network.

I'm wondering if the same thing can be done with one of my spare Edgerouter-X routers.

Update: I was able to do the same thing with the Edgerouter-X router.  So in retrospect, I have spun down the Proxmox pfSense router for use later.  I don't think that I will be getting rid of it anytime soon.  It's nice to know that I now have the ability to change the different routers that I have to give a multi-head ability to my HomeLab.


Thursday, September 22, 2022

Ran Another Test by Connecting to a Different Room Power Outlet

 I ran a different test with the AV2 Powerlines.  This time I purposefully plugged a different AV2000 into my small bedroom outlet to see what the increase in bandwidth would be from the living room to the small bedroom.  Unfortunately, the increase was only about doubling the speed.  I was getting around 93 Mbit/sec throughput instead of 35 Mbit/sec.

The test was composed of putting a new Powerline adapter into the small bedroom, connecting the new Powerline adapter to my HomeLab switch, and running some iperf tests.  The small bedroom circuit breaker is on the opposite side of the breaker box from my large bedroom circuit breaker; and on the same side as the circuit breaker for the living room.  Again this is 25 year old wiring.  I guess in the grand scheme of things I could have an electrician move the wires between the two breakers to get the large bedroom circuit breaker on the same side of the breaker box as the living room circuit breaker.  But, is the increase in speed worth it?  It will cost me money but in the end I will have more bandwidth.

Update: I am now trying to see if there is a different way of putting my Travel Routers and arranging my network in the back bedroom that will increase my throughput to the HomeLab.

Wednesday, September 21, 2022

Added a new 802.11ax Router to the Apartment

So I have purchased a new router, the Gl-iNet FLINT (GL-AX1800).  The reason that I did this was to optimize the connection between my HomeLab equipment and the apartment WiFi end point.  The FLINT is located 17 and a half feet from the end point and has 4 external antenna.  In addition, the FLINT is based on OpenWRT, which the SLATE was also based on.  Right now, being a new product, the software load is not quite up to the current edition of OpenWRT, but the beta test versions are promising.  I have downloaded the latest Beta and will be updating this router prior to the full software release.  The reason is to be able to setup vlans so that I can also plug in my TV and DVD player without interfering with the HomeLab connection.

After setting up the router in the space in the living room, I am measuring a speed of 400Mbps/400Mbps to the end point when setup as a repeater.  This is the kind of speed gain that I am hoping for.  The WiFi connection is continuing to reset itself and I need to know why.  I have noticed that the main indication of failure is that the DNS is no longer able to work through the connection and that the Weather Station is no longer pushing out information.

Update: so now the FLINT router has crapped out, possibly because I did some setting I shouldn’t have.  I have updated to the latest v4.1.0 beta without any custom values and now it works.  Go figure.

Update2: the problem with the WiFi connection stopping appears to be related to a DNS issue.  I can still ping IPs but just can't use DNS names.  Is this some setting somewhere?

Thursday, September 8, 2022

There appears to be an issue with the WiFi in my apartment

I have discovered that the WiFi is now stopping on a regular basis in my apartment.  I have no control over it but I would like to set things up so that I don’t have as many issues in what is available.  I have moved the Tempest Weather Station to the Portal SSID so that it has the most connectivity that it can get without being connected to the equipment in my rack.  I am also going to take down the UniFi AP AC Pro so that it doesn’t add to the interference in the apartment.  Perhaps removing this source will help with the overall speed of the WiFi in my apartment.  The problem with this is that I am using the UniFi to connect to the Tasmota switches.  I need something to do this with.  It occurred to me that I might use one of the RPi Zero Ws that I have to make up an isolated network within the rack.  If I keep the power level low enough, I should not cause interference outside of the rack.  Note, I do not have control over what the WiFi does or does not do.

I am also setting up an active/passive WiFi checker within the apartment so that I can get some data with which to analyze what might the problem be.

Update:  I have found 25 APs for the complex included in 832 devices just in 45 minutes.  There is ample amount of WiFi packets that could potentially cause issues, especially if they are on the cusp of the signal.  Further research is warranted.

Sunday, August 28, 2022

There seems to be an issue with the Gateway input keeping the DNS server up

Now that I have the Tempest Weather Station online, albeit without pushing the data to an official source, it seems strange that I am constantly losing DNS resolving.  The retirement community network uses 1.1.1.1 and 1.0.0.1 as the DNS servers.  I seem to lose connection to the DNS servers after about a day and a half.  This could be due to several things like pushing too much information out over the resident vlan or not having sufficient TLS connection credentials.  I am not sure at this point.

The first item, pushing too much information out, might be the likely culprit since the network setup might think that this is a spamming engine.  I will likely have to call IT to find out.  This would involve some sort of QoS with the UDP output from the Tempest Hub.

The second item, not having sufficient TLS connection credentials, is quite possible since the 1.1.1.1 and 1.0.0.1 both require a DNSSec connection (I think).  I will have to investigate further.

Update: I have noticed that the TCL TV occasionally reconnects, so it appears that I have an issue with WiFi in general. I am now connecting the Tempest Weather Station to the apartment WiFi system without going through my rack.  I will rely on extracting information from it across the internet using API calls now.

Sunday, August 21, 2022

Experiments Show PowerLine Adapters Often Don’t Work Like You Think They Should

The IT department here in the Retirement Community keeps making changes to make things good.  So it occurred to me that maybe things might have changed in my back bedroom for the good.  So I set out to find out what kind of speeds that I was getting between my input setup and my back bedroom where my HomeLab rack resides.  So I set up some speed tests using iperf on opposite sides of the input flow.  Much to my surprise, I found out that I was only getting around 38 Mbps throughput.  I had thought I was getting closer to 1 Gbps, given the type of AV2 units that I was using.  I tried different things like getting the managed switches out of the way, but still was achieving only the 38 Mbps that I had first measured.  I also tried using Speedtest.net and found that this was the max speed that I could get.

I downloaded the TP-Link app so that I could tell what the system was saying that it was getting between units.  It was displaying around 100 Mbps speed between the units, so I started looking into what kind of speeds I could expect with different wall outlets.  I brought in a different unit and added it to the mix and started moving it about the apartment to see what I could find out.  When it was plugged into a circuit that was near one of the two AV2000 units, it would register a speed of 1300-1400 Mbps, but would still measure the 100 Mbps to the other AV2000 unit.  As I was swapping them around, I could see patterns that identified a good vs bad line.  The low bandwidth is probably due to the age of the wiring in this apartment and having to go through an old breaker box.  Nothing I can do about that right now.

I am still trying to find the “sweet” spot to have equipment in the living room, but so far have not found it.

Update: so I have discovered that there are three circuit breakers that the signal is probably passing through.  One for the living room, one for the small bedroom, and one for the large bedroom.  They also appear to be on opposite sides of the mains, so much for finding a "sweet" spot to use.  I am stuck with what I have then.

Tuesday, August 16, 2022

The New Input Architecture to my HomeLab

 I think I may have solved my problem with the WiFi system here at the Retirement Community.  As I said before, this is a WiFi only environment; I can run Ethernet but not through the walls and not connected to the WiFi equipment and I have no control over the WiFi system.  The WiFi equipment has two main SSIDs, SSID1 and SSID2 in the following diagram.

The Incoming WiFi Architecture

The Incoming WiFi Architecture

Notice that there are a number of additional elements to the architecture.  The main input to the MainRouter in my HomeLab is through the WiFi Bridge, a Gl-iNet SLATE router.  That in turn goes into a managed switch, RemoteSwitch, which has a trunk line to my MainSwitch through Two TP-Link AV2000s.  The MainSwitch in turn poses the flow as the [WAN] vlan to the WAN port of my MainRouter.  Having the trunk line between two managed switches gives me great flexibility in how I arrange items in my HomeLab.  In fact I can put part of my [SRV] vlan in the living room where the main input equipment goes.  The MainSwitch also connects to other equipment in my HomeLab as necessary.  Normally I have almost a 30 dBm signal drop between the WiFi Access Point in the living room and my large back bedroom.  This input architecture resolves that.

I have an RPiGateway which is being primed to host input ports into my HomeLab from the outside.  As it turns out I can access RPiGateway from anywhere on the Retirement community campus; I just can't access it from the outside (and I don't need to, I'm not working now).  

Over on the right of the diagram is a problem that was solved through the use of a simple switch.  I have a Sleep-Number bed and it requires a WPA/WPA2 shared key encryption setup on 2.6GHz.  It is also a bit fussy on the level of the signal that it connects to.  So in that respect I have a DIR-505L which is connected to the SSID1 and retransmits a WPA/WPA2 shared key setup to the Sleep-Number bed since WPA/WPA2 is not available from the main WiFi setup.

I have a Tempest Weather station on my balcony which has a hub that was not able to receive the WPA/WPA2 shared key setup from the small bedroom, so it is now connected to a NEWIOTSSID coming from my Unifi AP AC Pro access point.  I also have a SRVSSID broadcast from that access point that I can connect to with my personal laptop in order to perform admin functions on my HomeLab while on my balcony.

I am also using the NEWIOTSSID to connect to a series of Tasmota switches mounted in my HomeLab Rack for the purpose of controlling power to several devices, since I may only have need of a couple at a time.