<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OpenWRT on nagg.eu</title><link>https://nagg.eu/tags/openwrt/</link><description>Recent content in OpenWRT on nagg.eu</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 25 Jul 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://nagg.eu/tags/openwrt/index.xml" rel="self" type="application/rss+xml"/><item><title>Debian QEMU/KVM bridged networking and VLAN</title><link>https://nagg.eu/debian-qemu-kvm-bridged-networking-and-vlan/</link><pubDate>Sun, 25 Jul 2021 00:00:00 +0000</pubDate><guid>https://nagg.eu/debian-qemu-kvm-bridged-networking-and-vlan/</guid><description>&lt;p&gt;By default on every Linux distro after installing &lt;code&gt;QEMU&lt;/code&gt; and &lt;code&gt;libvirt&lt;/code&gt; two
kinds of networking are available:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;NAT: VM sits behind a NAT.&lt;/li&gt;
&lt;li&gt;MACVTAP: without going into much details it acts more or less like a
bridged network, except not really. One of the most annoying limitations is
that host to guest communication and vice versa are not really working well.
Other important things might be broken as well, like for example VRRP.
This mode is good for quick and dirty testing but not really for a stable
environment.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;BRIDGED networking is also supported by &lt;code&gt;libvirt&lt;/code&gt; but requires some manual
work.&lt;br&gt;
A possible networking schema could be the following:&lt;/p&gt;</description></item><item><title>OPENWRT first run configuration guide</title><link>https://nagg.eu/openwrt-first-run-configuration-guide/</link><pubDate>Sat, 12 Dec 2020 00:00:00 +0000</pubDate><guid>https://nagg.eu/openwrt-first-run-configuration-guide/</guid><description>&lt;p&gt;OpenWRT is a free open source Linux based operating system aimed at networking
hardware.&lt;br&gt;
Every time the system is upgraded to a newer version using the so called &lt;code&gt;Sysupgrade BIN&lt;/code&gt;
image every package the user manually installed gets lost; this makes the upgrade process
very tedious especially if one does not properly write down all the customization he has made.&lt;br&gt;
I don&amp;rsquo;t use many custom packages but QoS, DNS-over-HTTPS, USB support and vnstat are must have.&lt;/p&gt;</description></item><item><title>APC UPS and HP server gen8 not restarting automatically when power goes back online after shutdown procedure is already starded but not completed</title><link>https://nagg.eu/apc-ups-and-hp-server-gen8-not-restarting-automatically-when-power-goes-back-online-after-shutdown-procedure-is-already-starded-but-not-completed/</link><pubDate>Mon, 25 Jun 2018 17:35:54 +0000</pubDate><guid>https://nagg.eu/apc-ups-and-hp-server-gen8-not-restarting-automatically-when-power-goes-back-online-after-shutdown-procedure-is-already-starded-but-not-completed/</guid><description>&lt;p&gt;I have got my hands on an APC UPS and some HP gen8 server, installed apcupsd on CentOS 7, connected the USB cable and everything was working fine except for this very annoying issue I had: * power goes down (pull the UPS power cord).&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;after some minutes the UPS battery threshold is triggered and the server shutdown procedure is launched by apcupsd.&lt;/li&gt;
&lt;li&gt;power goes back up (plug in the power cord) while the server is already shutting down but the shutdown sequence is not yet completed.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;RESULT&lt;/strong&gt;: the server will not power itself up even if the correct setting is selected in BIOS (&lt;code&gt;last power state&lt;/code&gt; or &lt;code&gt;always on&lt;/code&gt;).&lt;br&gt;
If the power stays offline for enough time for the server to completely shutdown and for the UPS to also shutdown once the power goes back online the server starts up automatically like it is supposed to do.&lt;br&gt;
The only workaround I could think of to solve the issue is running a cron job on the router, which is running OpenWRT, to trigger wake-on-LAN for the server.&lt;br&gt;
I don&amp;rsquo;t really like this solution, it feels hackish but still I could not find a better way to make the damn server power on automatically all by himself.&lt;br&gt;
As for OpenWRT and wake-on-LAN, first of all install &lt;code&gt;etherwake&lt;/code&gt; from LuCI or opkg:&lt;/p&gt;</description></item><item><title>LEDE/OPENWRT first run configuration guide</title><link>https://nagg.eu/lede-first-run-configuration-guide/</link><pubDate>Sat, 04 Nov 2017 13:33:49 +0000</pubDate><guid>https://nagg.eu/lede-first-run-configuration-guide/</guid><description>&lt;p&gt;LEDE, formerly OpenWRT, is a free open source Linux based operating system aimed at networking hardware.&lt;br&gt;
Every time the system is upgraded to a newer version using the so called &lt;code&gt;Sysupgrade BIN&lt;/code&gt; image every package the user manually installed gets lost; this makes the upgrade process very tedious especially if one does not properly write down all the customization he has made.&lt;br&gt;
I don&amp;rsquo;t use many custom packages but QoS, USB support and vnstat are a must have.&lt;/p&gt;</description></item></channel></rss>