<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Wireless on Nico Maas</title>
        <link>https://www.nico-maas.de/tags/wireless/</link>
        <description>Recent content in Wireless on Nico Maas</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en-us</language>
        <lastBuildDate>Tue, 26 Jul 2011 11:14:48 +0000</lastBuildDate><atom:link href="https://www.nico-maas.de/tags/wireless/index.xml" rel="self" type="application/rss+xml" /><item>
            <title>Netgear WNCE2001 Notes</title>
            <link>https://www.nico-maas.de/posts/2011-07-26-netgear-wnce2001-notes/</link>
            <pubDate>Tue, 26 Jul 2011 11:14:48 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2011-07-26-netgear-wnce2001-notes/</guid>
            <description>&lt;p&gt;We just got an Netgear WNCE2001 - and the need to support it.&lt;br&gt;&#xA;Basically, its an Wireless -&amp;gt; Ethernet Converter which does bridge an WIFI Network to an LAN / Ethernet Connector.&lt;br&gt;&#xA;You need to install it via WDS System or - plug it into an PC / Laptop, DHCP Client on and configure it via Webbrowser before using it on an &amp;ldquo;dump&amp;rdquo; ethernet-only device. Problem: The device itself asks for an IP Adress (to be configured after inital stage) and the connected Ethernet Client does ask itself again - some DHCP Servers don&amp;rsquo;t like that behavior, as far as it seems. So, our workaround was following: Giving the WNCE2001 an static assigned IP by the DHCP Server and &amp;ldquo;blocking&amp;rdquo; another IP for the Client. The Client has been configured statically and does now work as it was intended to be.&lt;/p&gt;</description>
        </item></channel>
</rss>
