<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    
    <title>blog.crox.net (Entries tagged as wlan)</title>
    <link>https://blog.crox.net/</link>
    <description></description>
    <dc:language>en</dc:language>
    <generator>Serendipity 2.5.0 - http://www.s9y.org/</generator>
    <pubDate>Fri, 15 Aug 2025 22:48:00 GMT</pubDate>

    <image>
    <url>https://blog.crox.net/templates/2k11/img/s9y_banner_small.png</url>
    <title>RSS: blog.crox.net - </title>
    <link>https://blog.crox.net/</link>
    <width>100</width>
    <height>21</height>
</image>

<item>
    <title>Disable WiFi Power Management on Raspbian 12 (Network Manager)</title>
    <link>https://blog.crox.net/archives/129-Disable-WiFi-Power-Management-on-Raspbian-12-Network-Manager.html</link>
    
    <comments>https://blog.crox.net/archives/129-Disable-WiFi-Power-Management-on-Raspbian-12-Network-Manager.html#comments</comments>
    <wfw:comment>https://blog.crox.net/wfwcomment.php?cid=129</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>https://blog.crox.net/rss.php?version=2.0&amp;type=comments&amp;cid=129</wfw:commentRss>
    

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    &lt;a href=&quot;https://blog.crox.net/archives/106-How-to-solve-Edimax-EW-7612UAn-v2-73927822-power-management-issues-on-Raspberry-Pi-Raspbian-WiFi-disconnect.html&quot; title=&quot;How to solve Edimax EW-7612UAn v2 (7392:7822) power management issues on Raspberry Pi (Raspbian WiFi disconnect)&quot;&gt;8 years later&lt;/a&gt; there are still issues on Raspberry Pi / Raspbian with WiFi power management causing disconnects and generally bad performance.&lt;br /&gt;
&lt;br /&gt;
I&#039;ve found a reliable method to disable WiFi Power Management for the on-board WiFi chip (brcmfmac) here: &lt;a href=&quot;https://gist.github.com/jcberthon/ea8cfe278998968ba7c5a95344bc8b55&quot; title=&quot;NetworkManager WiFi Power Saving&quot;&gt;NetworkManager WiFi Power Saving&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Fri, 15 Aug 2025 22:48:00 +0000</pubDate>
    <guid isPermaLink="false">https://blog.crox.net/archives/129-guid.html</guid>
    <category>debian</category>
<category>linux</category>
<category>raspberry pi</category>
<category>wlan</category>

</item>
<item>
    <title>How to solve Edimax EW-7612UAn v2 (7392:7822) power management issues on Raspberry Pi (Raspbian WiFi disconnect)</title>
    <link>https://blog.crox.net/archives/106-How-to-solve-Edimax-EW-7612UAn-v2-73927822-power-management-issues-on-Raspberry-Pi-Raspbian-WiFi-disconnect.html</link>
    
    <comments>https://blog.crox.net/archives/106-How-to-solve-Edimax-EW-7612UAn-v2-73927822-power-management-issues-on-Raspberry-Pi-Raspbian-WiFi-disconnect.html#comments</comments>
    <wfw:comment>https://blog.crox.net/wfwcomment.php?cid=106</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>https://blog.crox.net/rss.php?version=2.0&amp;type=comments&amp;cid=106</wfw:commentRss>
    

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    &lt;ul&gt;&lt;li&gt;On Raspbian, you don&#039;t need to install the 8192cu driver manually, as it comes with the distribution&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;To avoid disconnection issues, you need however to disable power management. This needs to be done in two places. First, this is what I have in /etc/modprobe.d/8192cu.conf:&lt;pre&gt;options 8192cu rtw_power_mgnt=0 rtw_enusbss=0&lt;/pre&gt;&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;This alone did not prevent the issue. I also had to add this entry to /etc/network/interfaces:&lt;pre&gt;auto wlan0&lt;br /&gt;allow-hotplug wlan0&lt;br /&gt;iface wlan0 inet dhcp&lt;br /&gt;wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf&lt;br /&gt;&lt;b&gt;wireless-power off&lt;/b&gt;&lt;br /&gt;iface default inet dhcp&lt;/pre&gt;&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;
&lt;br /&gt;
Sources: &lt;a href=&quot;https://github.com/xbianonpi/xbian/issues/217&quot;&gt;https://github.com/xbianonpi/xbian/issues/217&lt;/a&gt;, &lt;a href=&quot;https://www.kuerbis.org/2016/03/raspberry-pi-3-kurztipps-wlan-sleep-mode-verhindern/&quot;&gt;https://www.kuerbis.org/2016/03/raspberry-pi-3-kurztipps-wlan-sleep-mode-verhindern/&lt;/a&gt; 
    </content:encoded>

    <pubDate>Sun, 12 Nov 2017 19:04:00 +0000</pubDate>
    <guid isPermaLink="false">https://blog.crox.net/archives/106-guid.html</guid>
    <category>debian</category>
<category>linux</category>
<category>raspberry pi</category>
<category>wlan</category>

</item>
<item>
    <title>Recovering an unmanageable WRT54GL (OpenWRT lost password)</title>
    <link>https://blog.crox.net/archives/53-Recovering-an-unmanageable-WRT54GL-OpenWRT-lost-password.html</link>
    
    <comments>https://blog.crox.net/archives/53-Recovering-an-unmanageable-WRT54GL-OpenWRT-lost-password.html#comments</comments>
    <wfw:comment>https://blog.crox.net/wfwcomment.php?cid=53</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>https://blog.crox.net/rss.php?version=2.0&amp;type=comments&amp;cid=53</wfw:commentRss>
    

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    A friend recently brought us a &lt;a href=&quot;http://en.wikipedia.org/wiki/Linksys_WRT54G_series&quot; &gt;Linksys WRT54GL&lt;/a&gt; which had been laying around for a while and whose password was not available anymore.&lt;br /&gt;
&lt;br /&gt;
None of the &quot;easy&quot; password recovery methods seemed to work (like holding the reset button, power-cycling etc.) - possibly because the corresponding options had been previously disabled.&lt;br /&gt;
&lt;br /&gt;
In the end, I used the TFTP method described here: &lt;a href=&quot;http://oldwiki.openwrt.org/OpenWrtDocs(2f)Installing(2f)TFTP.html&quot;  title=&quot;Installing OpenWrt via TFTP&quot;&gt;http://oldwiki.openwrt.org/OpenWrtDocs(2f)Installing(2f)TFTP.html&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
However, it didn&#039;t work until all these conditions were met:&lt;br /&gt;
&lt;br /&gt;
- the laptop with the firmware image and the tftp client had to be connected to the WRT through an external switch&lt;br /&gt;
&lt;br /&gt;
- the switch had to be unplugged from the LAN&lt;br /&gt;
&lt;br /&gt;
- I had to lauch a &quot;ping -f 192.168.1.1&quot; in a different terminal before powering on the WRT in order for the tftp transfer to start&lt;br /&gt;
&lt;br /&gt;
- before and after the flashing I followed the &lt;a href=&quot;http://www.dd-wrt.com/wiki/index.php/Hard_reset_or_30/30/30&quot;  title=&quot;Hard reset or 30/30/30&quot;&gt;30/30/30&lt;/a&gt; procedure (not sure if that one is mandatory but it is recommended)&lt;br /&gt;
&lt;br /&gt;
To make sure the hardware was working I installed the latest firmware from the Linksys website (WRT54GL_v4.30.11_012_ETSI_EN_code.bin), but now I&#039;ll likely reflash it with &lt;a href=&quot;http://openwrt.org/&quot; &gt;OpenWRT&lt;/a&gt; - this time from the web interface :o) 
    </content:encoded>

    <pubDate>Fri, 19 Jun 2009 18:53:30 +0000</pubDate>
    <guid isPermaLink="false">https://blog.crox.net/archives/53-guid.html</guid>
    <category>linksys</category>
<category>wlan</category>

</item>
<item>
    <title>Linksys WAG200G-EU stops routing UDP after a while (scripted reboot how-to)</title>
    <link>https://blog.crox.net/archives/31-Linksys-WAG200G-EU-stops-routing-UDP-after-a-while-scripted-reboot-how-to.html</link>
    
    <comments>https://blog.crox.net/archives/31-Linksys-WAG200G-EU-stops-routing-UDP-after-a-while-scripted-reboot-how-to.html#comments</comments>
    <wfw:comment>https://blog.crox.net/wfwcomment.php?cid=31</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>https://blog.crox.net/rss.php?version=2.0&amp;type=comments&amp;cid=31</wfw:commentRss>
    

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    It seems that after having been up for a couple of days, the WAG200G starts having issues routing UDP packets properly. This particularly affects VoIP traffic (here IAX2 on port 4569). The symptoms are that &quot;regular surfing&quot; works flawlessly, but the registration with the asterisk server fails. &lt;a href=&quot;http://en.wikipedia.org/wiki/Tcpdump&quot;  title=&quot;tcpdump&quot;&gt;tcpdump&lt;/a&gt; shows no traffic on the server side. Restarting the WAG200G immediately solves the problem.&lt;br /&gt;
&lt;br /&gt;
Here is how I restarted the router from the command line:&lt;br /&gt;
&lt;pre&gt;wget --http-user=admin --http-password=pa55w0rd \&lt;br /&gt;     --post-data=&#039;reboot=1&amp;save=Enregistrer+les+param%E8tres&amp;todo=reboot&amp;h_reboot=1&amp;this_file=Reboot.htm&amp;next_file=index.htm&amp;message=&#039; \&lt;br /&gt;     http://192.168.0.1/setup.cgi&lt;/pre&gt;&lt;br /&gt;
(replace password and IP address as appropriate)&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Fri, 07 Mar 2008 10:04:25 +0000</pubDate>
    <guid isPermaLink="false">https://blog.crox.net/archives/31-guid.html</guid>
    <category>adsl</category>
<category>linksys</category>
<category>network</category>
<category>wlan</category>

</item>

</channel>
</rss>
