<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Trier on Nico Maas</title>
        <link>https://www.nico-maas.de/tags/trier/</link>
        <description>Recent content in Trier on Nico Maas</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en-us</language>
        <lastBuildDate>Fri, 01 Sep 2017 13:50:41 +0000</lastBuildDate><atom:link href="https://www.nico-maas.de/tags/trier/index.xml" rel="self" type="application/rss+xml" /><item>
            <title>[Freifunk] Upgrade Virtual Freifunk Router on VMWare ESXi 6.5</title>
            <link>https://www.nico-maas.de/posts/2017-09-01-freifunk-upgrade-virtual-freifunk-router-on-vmware-esxi-6-5/</link>
            <pubDate>Fri, 01 Sep 2017 13:50:41 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2017-09-01-freifunk-upgrade-virtual-freifunk-router-on-vmware-esxi-6-5/</guid>
            <description>&lt;p&gt;As I mentioned &lt;a class=&#34;link&#34; href=&#34;https://www.nico-maas.de/posts/2016-10-03-freifunk-virtual-freifunk-router-on-vmware-esxi-4-1/&#34; &gt;earlier&lt;/a&gt;, I use a virtual Freifunk Router as part of my mobile Infrastructure / Server. With this little VM, I can actually run a big-area Freifunk Network with lots of users without having to invest in new TP-Link accesspoints: I am running the VM, outputing the Freifunk LAN to a designated VLAN and use old spare Accesspoints as dumb &amp;ldquo;Media-Converters&amp;rdquo; (LAN to WIFI ;)).&lt;/p&gt;&#xA;&lt;p&gt;But, as I only use this appliance every now and then for different kind of conventions and conferences, I need to upgrade that Appliance manually, to get it straight to the latest version without waiting or reinstalling (and droping the VPN key&amp;hellip;).&lt;/p&gt;</description>
        </item><item>
            <title>[Freifunk] Virtual Freifunk Router on VMWare ESXi 4.1</title>
            <link>https://www.nico-maas.de/posts/2016-10-03-freifunk-virtual-freifunk-router-on-vmware-esxi-4-1/</link>
            <pubDate>Mon, 03 Oct 2016 19:44:33 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2016-10-03-freifunk-virtual-freifunk-router-on-vmware-esxi-4-1/</guid>
            <description>&lt;p&gt;This post was planed a LONG TIME, however - due to the fact that I could not get it working back in 2015 (See: &lt;a class=&#34;link&#34; href=&#34;https://github.com/freifunk-gluon/gluon/issues/496&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;https://github.com/freifunk-gluon/gluon/issues/496&lt;/a&gt;) it had been delayed. However, as I have the need to get Freifunk working as VM on a central ESXi Server - I tried it again - and it worked! Basic instruction to get it working can be found here in german: &lt;a class=&#34;link&#34; href=&#34;https://www.it-kl.eu/2015/08/gluon-x86-unter-vmware/&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;https://www.it-kl.eu/2015/08/gluon-x86-unter-vmware/&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;I got following equipment: ESXi 4.1 Server with multiple NICs.&lt;br&gt;&#xA;Start up with getting the right image from your Freifunk Team. I got the gluon-fftr-0.8.4-x86-vmware.vmdk from the Firmware Store of my trusted guys from FFTR (&lt;a class=&#34;link&#34; href=&#34;https://github.com/freifunktrier/firmware_store/tree/master/firmware/stable/factory&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;https://github.com/freifunktrier/firmware_store/tree/master/firmware/stable/factory&lt;/a&gt; [ Trier 0.8.4 is gluon 2016.1.6-3-g9300421, it&amp;rsquo;s just 2016.1.6 + ee597c6 + Webinterface-color-patches ] )&lt;br&gt;&#xA;After that, create a new VM on your VMWare ESXi Server. Choose an user definied configuration, &amp;ldquo;Other&amp;rdquo; OS and &amp;ldquo;Other (32-Bit)&amp;rdquo; Version. I gave the VM a 1 vCPU and 512 MB of RAM - but you can chose as you like. After that, you need to create two Network Devices / NICs. I chose two E1000 ones, and gave the first Interface the Freifunk LAN and added the second Interface to my common WAN (IMPORTANT!). After that, you&amp;rsquo;re not going to create an HDD.&lt;br&gt;&#xA;After the creation of the VM, upload your vmdk file to the folder, edit the VM and chose the downloaded VMDK as Harddrive.&lt;/p&gt;</description>
        </item><item>
            <title>Raspberry Pi Con &#34;Pi and More&#34;</title>
            <link>https://www.nico-maas.de/posts/2012-11-14-raspberry-pi-con-pi-and-more/</link>
            <pubDate>Wed, 14 Nov 2012 18:17:32 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2012-11-14-raspberry-pi-con-pi-and-more/</guid>
            <description>&lt;p&gt;At the 23. of August 2012, the University of Trier held the first Raspberry Pi Convention in Germany. It was a little, but awesome gig with about 30 IT Students and other interested people.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img class=&#34;gallery-image&#34; data-flex-basis=&#34;321px&#34; data-flex-grow=&#34;133&#34; height=&#34;1936&#34; loading=&#34;lazy&#34; sizes=&#34;(max-width: 767px) calc(100vw - 30px), (max-width: 1023px) 700px, (max-width: 1279px) 950px, 1232px&#34; src=&#34;https://www.nico-maas.de/posts/2012-11-14-raspberry-pi-con-pi-and-more/IMG_20120823_200012__1349.jpg&#34; srcset=&#34;https://www.nico-maas.de/posts/2012-11-14-raspberry-pi-con-pi-and-more/IMG_20120823_200012__1349_hu_15340cdbf52a535f.jpg 800w, https://www.nico-maas.de/posts/2012-11-14-raspberry-pi-con-pi-and-more/IMG_20120823_200012__1349_hu_6e0d0018bc0735ed.jpg 1600w, https://www.nico-maas.de/posts/2012-11-14-raspberry-pi-con-pi-and-more/IMG_20120823_200012__1349_hu_e16be2cf7367d00a.jpg 2400w, https://www.nico-maas.de/posts/2012-11-14-raspberry-pi-con-pi-and-more/IMG_20120823_200012__1349.jpg 2592w&#34; width=&#34;2592&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;The main idea was to rise the awareness for the new microcomputer, called &amp;ldquo;Raspberry Pi&amp;rdquo; which combines an 700 MHz ARM Processor, 512 MB of RAM, Full HDMI Output, Audio, Ethernet and USB into an very small and affordable package (about 35 US Dollar). With this microcomputer, and its General Purpose Input and Outputs (GPIO), pupils can actually have a &amp;ldquo;hands-on&amp;rdquo; (in) physical computing. That means: Connecting software (i.e. Python, Perl, C programs) with the real world. For example: Controlling LEDs, driving motors or even react on buttons, attached to the GPIO port. Combining these possibilities into a small and affordable package started a big hype about this little computer, long before it was even available to the public.&lt;/p&gt;</description>
        </item></channel>
</rss>
