<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://www.baszerr.eu/lib/exe/css.php?s=feed" type="text/css"?>
<rss version="2.0">
    <channel xmlns:g="http://base.google.com/ns/1.0">
        <title>BaSzErr - blog:2012:01:13</title>
        <description></description>
        <link>https://www.baszerr.eu/</link>
        <lastBuildDate>Wed, 06 May 2026 09:35:20 +0000</lastBuildDate>
        <generator>FeedCreator 1.8</generator>
        <image>
            <url>https://www.baszerr.eu/lib/exe/fetch.php?media=wiki:dokuwiki.svg</url>
            <title>BaSzErr</title>
            <link>https://www.baszerr.eu/</link>
        </image>
        <item>
            <title>1</title>
            <link>https://www.baszerr.eu/doku.php?id=blog:2012:01:13:1</link>
            <description>
&lt;h1 class=&quot;sectionedit1&quot; id=&quot;monitor_on_channel_-1&quot;&gt;2012.01.13 - monitor on channel -1&lt;/h1&gt;
&lt;div class=&quot;level1&quot;&gt;

&lt;p&gt;
since some time there was a but in driver for intel&amp;#039;s wireless chip, in linux kernel. when you setup monitor device (ex. mon0) on specific channel (say: N), when injecting it says:
&lt;/p&gt;
&lt;pre class=&quot;code&quot;&gt;mon0 is on channel -1, but the AP uses channel N.&lt;/pre&gt;

&lt;p&gt;
it didn&amp;#039;t bother to fix this any way, until one day… and it appeared that whole fix means just executing few commands. in case you spot the same problem, see this &lt;a href=&quot;http://linux-software-news-tutorials.blogspot.com/2011/06/solve-error-mon0-is-on-channel-1-but-ap.html&quot; class=&quot;urlextern&quot; title=&quot;http://linux-software-news-tutorials.blogspot.com/2011/06/solve-error-mon0-is-on-channel-1-but-ap.html&quot; rel=&quot;ugc nofollow&quot;&gt;fix description&lt;/a&gt; (or &lt;a href=&quot;http://aircrack-ng.org/doku.php?id=compat-wireless&quot; class=&quot;urlextern&quot; title=&quot;http://aircrack-ng.org/doku.php?id=compat-wireless&quot; rel=&quot;ugc nofollow&quot;&gt;this one&lt;/a&gt;). funny thing is that it boils down to applying 2 trivial patches on the kernel driver: &lt;a href=&quot;http://patches.aircrack-ng.org/channel-negative-one-maxim.patch&quot; class=&quot;urlextern&quot; title=&quot;http://patches.aircrack-ng.org/channel-negative-one-maxim.patch&quot; rel=&quot;ugc nofollow&quot;&gt;fixing &amp;#039;-1&amp;#039; channel issue&lt;/a&gt; and &lt;a href=&quot;http://patches.aircrack-ng.org/mac80211.compat08082009.wl_frag+ack_v1.patch&quot; class=&quot;urlextern&quot; title=&quot;http://patches.aircrack-ng.org/mac80211.compat08082009.wl_frag+ack_v1.patch&quot; rel=&quot;ugc nofollow&quot;&gt;one more&lt;/a&gt;.
&lt;/p&gt;

&lt;p&gt;
few weeks ago &lt;a href=&quot;http://www.wojek.net&quot; class=&quot;urlextern&quot; title=&quot;http://www.wojek.net&quot; rel=&quot;ugc nofollow&quot;&gt;wojek&lt;/a&gt; told me that the newest &lt;a href=&quot;http://www.ubuntu.com&quot; class=&quot;urlextern&quot; title=&quot;http://www.ubuntu.com&quot; rel=&quot;ugc nofollow&quot;&gt;Ubuntu&lt;/a&gt; release already has a patched kernel. what makes me sad, is that it took so so long to make it official, vanilla kernel part…
&lt;/p&gt;

&lt;/div&gt;
</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Tue, 15 Jun 2021 20:09:12 +0000</pubDate>
        </item>
    </channel>
</rss>
