<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Networking on Network Haven</title>
    <link>/tags/networking/</link>
    <description>Recent content in Networking on Network Haven</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 16 May 2026 12:00:00 +0200</lastBuildDate>
    <atom:link href="/tags/networking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Cisco ignore startup configuration</title>
      <link>/posts/2026/cisco-ignore-startup-configuration/</link>
      <pubDate>Sat, 16 May 2026 12:00:00 +0200</pubDate>
      <guid>/posts/2026/cisco-ignore-startup-configuration/</guid>
      <description>&lt;p&gt;The startup configuration can be bypassed by booting into ROMMON or during normal operation. In either case, a reboot is required.&lt;/p&gt;&#xA;&lt;p&gt;This is particularly useful, for example, if you need to perform a password recovery because you have forgotten your password, or for troubleshooting purposes.&lt;/p&gt;&#xA;&lt;h2 id=&#34;configuration-in-ios&#34;&gt;Configuration in IOS&lt;/h2&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;Switch# configure terminal&#xA;! to activate&#xA;Switch(config)# system ignore startup-config&#xA;&#xA;! to deactivate&#xA;Switch(config)# no system ignore startup-config&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;configuration-in-rommon&#34;&gt;Configuration in ROMMON&lt;/h2&gt;&#xA;&lt;p&gt;In the background, the IOS command simply sets the ROMMON variable SWITCH_IGNORE_STARTUP_CONFIG to 1 or 0 which we can also do manually.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Fixing SCEP Certificate Enrollment over HTTPS on eLux Thin Clients</title>
      <link>/posts/2026/fixing-scep-certificate-enrollement-over-https-on-elux-thin-clients/</link>
      <pubDate>Wed, 13 May 2026 12:00:00 +0200</pubDate>
      <guid>/posts/2026/fixing-scep-certificate-enrollement-over-https-on-elux-thin-clients/</guid>
      <description>&lt;p&gt;Currently we trying out eLux as an replacement of older thin clients with ThinOS or IgelOS. We tried to configure 802.1x authentication and the therefore needed certificate enrollment with our current SCEP/NDES server. We came across the issue that the scep client that eLux uses – &lt;a href=&#34;https://github.com/certnanny/sscep&#34;&gt;sscep&lt;/a&gt; – an open source “Simple SCEP client for Unix” &lt;strong&gt;doesn’t support certificates requests over HTTPS&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;When investigating the problem we found this GitHub issue which explains our problem. Our NDES server was only reachable over HTTPS – both on the administration page and most importantly also on the request web page (certsrv/mscep) where the client requests their certificates.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Issue detecting domain network on domain controller when using NIC teaming</title>
      <link>/posts/2026/issue-detecting-domain-network-on-domain-controller-when-using-nic-teaming/</link>
      <pubDate>Fri, 10 Apr 2026 23:10:03 +0200</pubDate>
      <guid>/posts/2026/issue-detecting-domain-network-on-domain-controller-when-using-nic-teaming/</guid>
      <description>&lt;p&gt;We had an issue where our domain controller lost its domain network profile after a reboot. When it came back up it was set to public instead of domain.&lt;/p&gt;&#xA;&lt;p&gt;The problem occurred only when Windows NIC teaming (switch-independent) was used in combination with two network adapters in the team. As soon as one network adapter was disabled from the team (while the other remained active), the network profile (domain) was recognized correctly.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SNMP monitoring with Grafana, Prometheus and snmp_exporter</title>
      <link>/posts/2026/snmp-monitoring-with-grafana-prometheus-and-snmp_exporter/</link>
      <pubDate>Sun, 22 Feb 2026 23:10:03 +0200</pubDate>
      <guid>/posts/2026/snmp-monitoring-with-grafana-prometheus-and-snmp_exporter/</guid>
      <description>&lt;p&gt;SNMP monitoring with grafana and prometheus can be done with the official &lt;a href=&#34;https://github.com/prometheus/snmp_exporter&#34;&gt;snmp_exporter&lt;/a&gt; from prometheus.&lt;br&gt;&#xA;Since I didn’t found any direct forward documentation, blog or any source of documentation in an ELI5 style how this will work, this is my try to document my findings and understanding on how this stuff works. To be honest I still don’t understand all stuff inside the generator configuration file but here is what I found out.&lt;/p&gt;</description>
    </item>
    <item>
      <title>MikroTik SFTP backup script</title>
      <link>/posts/2026/mikrotik-sftp-backup-script/</link>
      <pubDate>Sun, 04 Jan 2026 23:10:03 +0200</pubDate>
      <guid>/posts/2026/mikrotik-sftp-backup-script/</guid>
      <description>&lt;p&gt;Automated backups for MikroTik devices can be accomplished by running a scheduled script.&#xA;The following script can be run in the scheduler in order to automate the backups to an SFTP share. It was tested on a MiroTik hEX RB750Gr3 with RouterOS 7.20.1. Just make sure to adjust the first five variables to your needs.&#xA;This script is based on another script I found on the forum – &lt;a href=&#34;https://forum.mikrotik.com/t/sftp-upload-via-scripting-only-supports-hmac-md5-and-hmac-sha1/166228&#34;&gt;here&lt;/a&gt;. I adjusted the date settings in the filename since these weren’t working for me.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Configure OPNsense Bridge on a Sophos SG125 V2</title>
      <link>/posts/2025/configure-opnsense-bridge-on-a-sophos-sg125-v2/</link>
      <pubDate>Mon, 22 Dec 2025 23:10:03 +0200</pubDate>
      <guid>/posts/2025/configure-opnsense-bridge-on-a-sophos-sg125-v2/</guid>
      <description>&lt;p&gt;I recently purchased two Sophos SG 125 V2s with OPNsense. These have several physical (Layer 3) interfaces, which I would like to combine into a bridge. This allows multiple interfaces to be treated like a switch (Layer 2) and assigned to the same network without having to configure each interface individually.&lt;/p&gt;&#xA;&lt;p&gt;Sophos has a DMZ, a LAN, an HA, a WAN, and several normal Ethernet ports. I would like to set up the Ethernet ports together as a bridge.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
