<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
>

<channel>
	<title>Cyconet Blog &#187; WLan</title>
	<atom:link href="http://blog.waja.info/tag/wlan/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.waja.info</link>
	<description>Just a place to be!</description>
	<lastBuildDate>Wed, 28 Apr 2010 08:22:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/</creativeCommons:license>
		<item>
		<title>Ignoring security (usability)</title>
		<link>http://blog.waja.info/2007/07/07/ignoring-security-usability/</link>
		<comments>http://blog.waja.info/2007/07/07/ignoring-security-usability/#comments</comments>
		<pubDate>Fri, 06 Jul 2007 23:39:18 +0000</pubDate>
		<dc:creator>cyco</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[planet]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[WLan]]></category>

		<guid isPermaLink="false">http://blog.waja.info/2007/07/07/ignoring-security-usability/</guid>
		<description><![CDATA[Since some time, Deutsche Bahn rolled public wireless lan called &#8220;WLAN am Bahnhof&#8221; out at 25 railroad stations, you can choose between 4 providers. Sounds really nice, but beside the economical conditions, there is also at least one security issue. Connecting to the network and opening your favorite browser redirects you to a encrypted portal. [...]]]></description>
			<content:encoded><![CDATA[<p>Since some time, <a target="new" href="http://www.db.de">Deutsche Bahn</a> rolled public wireless lan called &#8220;WLAN am Bahnhof&#8221; out at 25 railroad stations, you can choose between 4 providers. Sounds really nice, but beside the economical conditions, there is also at least one security issue.<br />
Connecting to the network and opening your favorite browser redirects you to a encrypted portal. So far, so good &#8230; the really bad news is, that the certificate expired over 6 years ago.<br />
<img src="http://blog.waja.info/wp-content/photos/zertifikat.png" alt="Broken certificate" /><br />
This seems to be a normal behavior, since it happens often, that invalid certificates are used. This leeds to blunted users, which aren&#8217;t verifying such certificates anymore, even when it&#8217;s important.<br />
Does anybody know a reasonable way to notify anybody who can solve the problem there beside the normal contact forms?</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.waja.info/2007/07/07/ignoring-security-usability/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>Wireless Bridge and WPA(2) on Linksys Router &#8230; or how to look for a needle in a haystack</title>
		<link>http://blog.waja.info/2006/07/02/wireless-bridge-and-wpa2-on-linksys-router/</link>
		<comments>http://blog.waja.info/2006/07/02/wireless-bridge-and-wpa2-on-linksys-router/#comments</comments>
		<pubDate>Sun, 02 Jul 2006 19:56:44 +0000</pubDate>
		<dc:creator>cyco</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[OpenSource]]></category>
		<category><![CDATA[OpenWRT]]></category>
		<category><![CDATA[WLan]]></category>
		<category><![CDATA[linksys]]></category>

		<guid isPermaLink="false">http://blog.waja.info/2006/07/02/wireless-bridge-and-wpa2-on-linksys-router-or-how-to-look-for-a-needle-in-a-haystack/</guid>
		<description><![CDATA[I was searching half a night and 2 hours today to get a Linksys Router working a wireless bridge with WPA(2) encryption. I tried Openwrt White Russian RC5 and DD-Wrt V23 SP1 and many combinations of WPA, WPA2, TKIP, AES. The bridge works well with WEP and without any encryption&#8230;. So &#8230; after more than [...]]]></description>
			<content:encoded><![CDATA[<p>I was searching half a night and 2 hours today to get a Linksys Router working a wireless bridge with WPA(2) encryption. I tried <a href="http://openwrt.org">Openwrt</a> White Russian RC5 and <a href="http://www.dd-wrt.com">DD-Wrt</a> V23 SP1 and many combinations of WPA, WPA2, TKIP, AES. The bridge works well with WEP and without any encryption&#8230;.</p>
<p><span id="more-89"></span></p>
<p>So &#8230; after more than one hour googling I found the following in the broadcom kernel module source:</p>
<blockquote><p>
<code>if (val &#038;&#038; strstr(v, "psk")) {<br />
    val = (strstr(v, "psk2") ? 0x84 : 0x4);<br />
    v = nvram_safe_get(wl_var("wpa_psk"));<br />
    if ((strlen(v) >= 8) &#038;&#038; (strlen(v) < 63)) {</p>
<p>        bcom_ioctl(skfd, ifname, WLC_SET_WPA_AUTH, &#038;val, sizeof(val));</p>
<p>        if (nvram_match(wl_var("mode"), "wet")) {<br />
            /* Enable in-driver WPA supplicant */<br />
            wsec_pmk_t pmk;</p>
<p>            pmk.key_len = (unsigned short) strlen(v);<br />
            pmk.flags = WSEC_PASSPHRASE;<br />
            strcpy(pmk.key, v);<br />
            bcom_ioctl(skfd, ifname, WLC_SET_WSEC_PMK, &#038;pmk, sizeof(pmk));<br />
            bcom_set_int(skfd, ifname, "sup_wpa", 1);<br />
        }<br />
    }<br />
}</code></code></p></blockquote>
<p>So &#8230; this means, that the WPA-PSK length has to be >= 8 and < 63, mine was 65. This wasnÃƒâ€šÃ‚Â´t a problem yet, cause I used the routers only in AP mode, where this restriction doesn't effect. Shorting the WPA-PSK length 62 did the trick!</p></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.waja.info/2006/07/02/wireless-bridge-and-wpa2-on-linksys-router/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>WRTSL54GS debridged</title>
		<link>http://blog.waja.info/2006/06/28/wrtsl54gs-debridged/</link>
		<comments>http://blog.waja.info/2006/06/28/wrtsl54gs-debridged/#comments</comments>
		<pubDate>Wed, 28 Jun 2006 08:47:27 +0000</pubDate>
		<dc:creator>cyco</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[OpenSource]]></category>
		<category><![CDATA[OpenWRT]]></category>
		<category><![CDATA[WLan]]></category>
		<category><![CDATA[hacking]]></category>
		<category><![CDATA[linksys]]></category>

		<guid isPermaLink="false">http://blog.waja.info/2006/06/28/wrtsl54gs-debridged/</guid>
		<description><![CDATA[Okay &#8230; we got the serial port running (same like WRT54GS), so we could be more risky. After some tries I decided to work analog the WRT54G models. Successfull was the following modifications to factory (linksys) defaults: nvram set vlan0ports=&#8221;0 1 2 5*&#8221; nvram set vlan1ports=&#8221;4 5*&#8221; nvram set vlan0hwname=&#8221;et0&#8243; nvram set vlan2ports=&#8221;3 5&#8243; nvram [...]]]></description>
			<content:encoded><![CDATA[<p>Okay &#8230; we got the serial port running (same like WRT54GS), so we could be more risky. After some tries I decided to work analog the WRT54G models.</p>
<p><span id="more-87"></span></p>
<p>Successfull was the following modifications to factory (linksys) defaults:
</p>
<p class="code">nvram set vlan0ports=&#8221;0 1 2 5*&#8221;<br />
nvram set vlan1ports=&#8221;4 5*&#8221;<br />
nvram set vlan0hwname=&#8221;et0&#8243;<br />
nvram set vlan2ports=&#8221;3 5&#8243;<br />
nvram set vlan2hwname=&#8221;et0&#8243;<br />
nvram set dmz_ifname=&#8221;vlan2&#8243;<br />
nvram set lan_ifname=&#8221;br0&#8243;<br />
nvram set lan_ifnames=&#8221;vlan0&#8243;<br />
nvram set wan_ifname=&#8221;ppp0&#8243;</p>
<p>Now the door is open to extend the functionality of the openwrt router</p>
<p class="code"># df<br />
Filesystem           1k-blocks      Used Available Use% Mounted on<br />
/dev/root                 7296      3420      3876  47% /<br />
none                     15276        36     15240   0% /tmp</p>
<p>Hrhrhrhr &#8230; :-) Disassemble photos can be found <a href="http://gallery.cyconet.org/v/wrtsl54gs1/">here</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.waja.info/2006/06/28/wrtsl54gs-debridged/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>We got some Linksys WRTSL54GS imported from US</title>
		<link>http://blog.waja.info/2006/06/27/we-got-some-linksys-wrtsl54gs-imported-from-us/</link>
		<comments>http://blog.waja.info/2006/06/27/we-got-some-linksys-wrtsl54gs-imported-from-us/#comments</comments>
		<pubDate>Tue, 27 Jun 2006 11:14:43 +0000</pubDate>
		<dc:creator>cyco</dc:creator>
				<category><![CDATA[Networking]]></category>
		<category><![CDATA[OpenWRT]]></category>
		<category><![CDATA[WLan]]></category>
		<category><![CDATA[hardware-hacking]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[OpenSource]]></category>

		<guid isPermaLink="false">http://blog.waja.info/2006/06/27/we-got-some-linksys-wrtsl54gs-imported-from-us/</guid>
		<description><![CDATA[DonÃƒâ€šÃ‚Â´t ask how, but we got some units to europe. The first thing we does, was to install openwrt and to try debridge the switch to have multiple interfaces instead. We was able to remove ports from the switch, but cant create additional working vlans like on WRT54G. So at this point its useless for [...]]]></description>
			<content:encoded><![CDATA[<p><img align="left" alt="Linksys WRTSL54GS" title="Linksys WRTSL54GS" style="margin: 0pt 6px 2px 0pt; padding: 3px; display: inline; float: left" src="http://blog.waja.info/wp-content/photos/wrtsl54gs.jpeg" /></p>
<p>DonÃƒâ€šÃ‚Â´t ask how, but we got some units to europe. </p>
<p>The first thing we does, was to install <a href="http://www.openwrt.org">openwrt</a> and to try debridge the switch to have multiple interfaces instead. We was able to remove ports from the switch, but cant create additional working vlans like on <a href="http://blog.waja.info/2005/11/23/break-the-switch-into-separated-ethernet-ports-vlans/">WRT54G</a>. So at this point its useless for our purpose. But we will start exploring as son as possible we have a running serial console.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.waja.info/2006/06/27/we-got-some-linksys-wrtsl54gs-imported-from-us/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>Break the Switch into separated ethernet ports / VLANs</title>
		<link>http://blog.waja.info/2005/11/23/break-the-switch-into-separated-ethernet-ports-vlans/</link>
		<comments>http://blog.waja.info/2005/11/23/break-the-switch-into-separated-ethernet-ports-vlans/#comments</comments>
		<pubDate>Wed, 23 Nov 2005 12:30:24 +0000</pubDate>
		<dc:creator>cyco</dc:creator>
				<category><![CDATA[OpenWRT]]></category>
		<category><![CDATA[WLan]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[OpenSource]]></category>

		<guid isPermaLink="false">http://blog.waja.info/2005/11/23/break-the-switch-into-separated-ethernet-ports-vlans/</guid>
		<description><![CDATA[At first &#8230; I&#8217;m not responsible, if you brick your router by using this documention. If your fear it would be possible, stop HERE! The following NVRAM-Settings need to take place: #!/bin/sh #Port 0 into WAN, 5 Router themselv nvram set vlan1hwname=et0 nvram set vlan1ports="0 5" #Port 2, 3 and 4 into LAN, 5 Router [...]]]></description>
			<content:encoded><![CDATA[<p>At first &#8230; I&#8217;m not responsible, if you brick your router by using this documention. If your fear it would be possible, stop HERE!</p>
<p>The following NVRAM-Settings need to take place:</p>
<blockquote><pre>#!/bin/sh
#Port 0 into WAN, 5 Router themselv
nvram set vlan1hwname=et0
nvram set vlan1ports="0 5"
#Port 2, 3 and 4 into LAN, 5 Router themselv
nvram set vlan0hwname=et0
nvram set vlan0ports="2 3 4 5*"
# Port 1 into DMZ, 5 Router themselv
nvram set vlan2hwname=et0
nvram set vlan2ports="1 5*"
# Static IP-Address for DMZ-IF
nvram set dmz_ifname=vlan2
nvram set dmz_proto=static
nvram set dmz_ipaddr=172.18.20.5
nvram set dmz_netmask=255.255.255.0
# save all the stuff
nvram commit</pre>
</blockquote>
<p>To bring automaticaly up the dmz-if, you need to add &#8220;ifup dmz&#8221; with:</p>
<p class="code"># sed &#8220;s/ifup lan/ifup lan@    ifup dmz/&#8221; &#92<br />
/etc/init.d/S40network | tr &#8216;@&#8217; &#8216;n&#8217; > /etc/init.d/S40network</p>
<p>To allow traffic forwarded by the new if, you will maybe add for example the following into &#8220;/etc/firewall.users&#8221;:</p>
<blockquote><pre>#!/bin/sh
DMZ=$(nvram get dmz_ifname)
#Allow Forward from DMZ into WAN
iptables -A FORWARD -i $DMZ -o $WAN -j ACCEPT
#Allow Forward from DMZ into LAN
iptables -A FORWARD -i $DMZ -o $LAN -j ACCEPT
#Allow Forward from LAN into DMZ
iptables -A FORWARD -i $LAN -o $DMZ -j ACCEPT</pre>
</blockquote>
<p>But it will be better to specify exactly, what services are allowed from and into DMZ!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.waja.info/2005/11/23/break-the-switch-into-separated-ethernet-ports-vlans/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>Other resources</title>
		<link>http://blog.waja.info/2004/10/19/other-resources/</link>
		<comments>http://blog.waja.info/2004/10/19/other-resources/#comments</comments>
		<pubDate>Tue, 19 Oct 2004 20:00:18 +0000</pubDate>
		<dc:creator>cyco</dc:creator>
				<category><![CDATA[OpenWRT]]></category>
		<category><![CDATA[WLan]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[OpenSource]]></category>

		<guid isPermaLink="false">http://blog.waja.info/?p=13</guid>
		<description><![CDATA[Seattle Wireless &#8211; LinksysWrt54g Wrt54gTools Snort on the WRT54G Linux on the WRT54G Linksys WRT54 Hardware Versions Under the Knife-the definitive guide How-To: recover from a bad firmware flash DD-WRT &#8211; this firmware based on Alchemy 6RC5a Openwrt howto german OpenWRT Website Journal of TheIndividual Hardware supported by OpenWRT Memoryupgrade for some Wrt54G V2 and [...]]]></description>
			<content:encoded><![CDATA[<p><a target="_blank" href="http://www.seattlewireless.net/index.cgi/LinksysWrt54g">Seattle Wireless &#8211; LinksysWrt54g</a><br />
<a href="http://www.seattlewireless.net/index.cgi/Wrt54gTools">Wrt54gTools</a><br />
<a target="_blank" href="http://www.batbox.org/wrt54g.html">Snort on the WRT54G</a><br />
<a target="_blank" href="http://www.batbox.org/wrt54g-linux.html">Linux on the WRT54G</a><br />
<a target="new" href="http://www.linksysinfo.org/modules.php?name=Content&#038;pa=showpage&#038;pid=6#table">Linksys WRT54 Hardware Versions Under the Knife-the definitive guide</a><br />
<a target="new" href="http://forum.bsr-clan.de/viewtopic.php?t=593">How-To: recover from a bad firmware flash</a><br />
<a target="new" href="http://sf01_32.ipx10813.ipxserver.de/dd-wrt/index.html">DD-WRT &#8211; this firmware based on Alchemy 6RC5a</a><br />
<a target="new" href="http://www.syslinx.org/wiki/index.php/Openwrt_howto_german">Openwrt howto german</a><br />
<a target="new" href="http://openwrt.org/">OpenWRT Website</a><br />
<a target="new" href="http://slashdot.org/~TheIndividual/journal/">Journal of TheIndividual</a><br />
<a target="new" href="http://openwrt.org/OpenWrtDocs/Hardware">Hardware supported by OpenWRT</a><br />
<a target="new" href="http://forum.bsr-clan.de/viewtopic.php?t=583&#038;postdays=0&#038;postorder=asc&#038;start=30">Memoryupgrade for some Wrt54G V2 and for V2.2?!?</a><br />
<a target="new" href="http://spacetoad.com/tmp/hairydairymaid_debrickv22.zip">JTAG access to WRT flash</a><br />
<a target="new" href="http://forum.bsr-clan.de/viewtopic.php?t=604&#038;highlight=jtag">Need JTAG help!</a><br />
<a target="new" href="http://forum.bsr-clan.de/viewtopic.php?t=556&#038;highlight=jtag">Bricked (?) WRT54G v1.0 gives odd ping times</a><br />
<a target="new" href="http://www.rwhitby.net/wrt54gs/serial.html">Linksys WRT54G/WRT54GS Dual Serial Port Mod</a><br />
<a target="new" href="http://jdc.parodius.com/wrt54g/serial.html">WRT54G: Single-port Serial Modification</a><br />
<a target="new" href="http://hamburg.freifunk.net/twiki/bin/view/Technisches/WRT54gSerielleSchnittstelle">Linksys WRT54G/WRT54GS RS232 Dual Serial Port / Console Mod</a><br />
<a target="new" href="http://www.yokoy.de/sonstiges-bauanleitungen.html">Bauanleitungen</a><br />
<a target="new" href="http://www.foken.de/alexander/?projekte/elektronik/wrt54g-v2-console.html">KonsolenanschluÃƒÆ’Ã…Â¸ fÃƒÆ’Ã‚Â¼r Linksys WRT54G Version 2</a><br />
<a target="new" href="http://hans.liss.pp.se/work/wrt54gs_serial.html">A serial port adapter for the Linksys WRT54G/WRT54GS router</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.waja.info/2004/10/19/other-resources/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>lspci</title>
		<link>http://blog.waja.info/2004/10/19/lspci/</link>
		<comments>http://blog.waja.info/2004/10/19/lspci/#comments</comments>
		<pubDate>Tue, 19 Oct 2004 19:58:34 +0000</pubDate>
		<dc:creator>cyco</dc:creator>
				<category><![CDATA[OpenWRT]]></category>
		<category><![CDATA[WLan]]></category>
		<category><![CDATA[linksys]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[OpenSource]]></category>

		<guid isPermaLink="false">http://blog.waja.info/?p=14</guid>
		<description><![CDATA[00:00.0 RAM memory: Broadcom Corporation: Unknown device 0803 00:01.0 Ethernet controller: Broadcom Corporation: Unknown device 4711 00:02.0 Ethernet controller: Broadcom Corporation: Unknown device 4713 00:03.0 Modem: Broadcom Corporation: Unknown device 4712 00:04.0 USB Controller: Broadcom Corporation: Unknown device 4715 00:05.0 PCI bridge: Broadcom Corporation: Unknown device 0804 00:06.0 MIPS: Broadcom Corporation: Unknown device 0805 00:07.0 [...]]]></description>
			<content:encoded><![CDATA[<pre>00:00.0 RAM memory: Broadcom Corporation: Unknown device 0803
00:01.0 Ethernet controller: Broadcom Corporation: Unknown device 4711
00:02.0 Ethernet controller: Broadcom Corporation: Unknown device 4713
00:03.0 Modem: Broadcom Corporation: Unknown device 4712
00:04.0 USB Controller: Broadcom Corporation: Unknown device 4715
00:05.0 PCI bridge: Broadcom Corporation: Unknown device 0804
00:06.0 MIPS: Broadcom Corporation: Unknown device 0805
00:07.0 FLASH memory: Broadcom Corporation: Unknown device 0811
00:08.0 Ethernet controller: Broadcom Corporation: Unknown device 4713
01:00.0 Host bridge: Broadcom Corporation: Unknown device 4710 (rev 01)
01:08.0 Network controller: Broadcom Corporation BCM94306 802.11g (rev 02)</pre>
]]></content:encoded>
			<wfw:commentRss>http://blog.waja.info/2004/10/19/lspci/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>Boot messages</title>
		<link>http://blog.waja.info/2004/10/19/boot-messages/</link>
		<comments>http://blog.waja.info/2004/10/19/boot-messages/#comments</comments>
		<pubDate>Tue, 19 Oct 2004 19:55:57 +0000</pubDate>
		<dc:creator>cyco</dc:creator>
				<category><![CDATA[OpenWRT]]></category>
		<category><![CDATA[WLan]]></category>
		<category><![CDATA[linksys]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[OpenSource]]></category>

		<guid isPermaLink="false">http://blog.waja.info/?p=15</guid>
		<description><![CDATA[CPU revision is: 00024000 Loading BCM4710 MMU routines. Primary instruction cache 8kb, linesize 16 bytes (2 ways) Primary data cache 4kb, linesize 16 bytes (2 ways) Linux version 2.4.20 (bdferris@localhost.localdomain) (gcc version 3.0 20010422 (prerelease) with bcm4710a0 modifications) #55 Sat Nov 15 12:23:00 EST 2003 Determined physical RAM map: memory: 01000000 @ 00000000 (usable) On [...]]]></description>
			<content:encoded><![CDATA[<pre>CPU revision is: 00024000
Loading BCM4710 MMU routines.
Primary instruction cache 8kb, linesize 16 bytes (2 ways)
Primary data cache 4kb, linesize 16 bytes (2 ways)
Linux version 2.4.20 (bdferris@localhost.localdomain) (gcc version 3.0 20010422 (prerelease) with bcm4710a0 modifications) #55 Sat Nov 15 12:23:00 EST 2003
Determined physical RAM map:
memory: 01000000 @ 00000000 (usable)
On node 0 totalpages: 4096
zone(0): 4096 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/mtdblock2 noinitrd console=ttyS0,115200
CPU: BCM4710 rev 0 at 125 MHz
!unable to setup serial console!
Calibrating delay loop... 82.94 BogoMIPS
Memory: 14540k/16384k available (1239k kernel code, 1844k reserved, 108k data, 64k init, 0k highmem)
Dentry cache hash table entries: 2048 (order: 2, 16384 bytes)
Inode cache hash table entries: 1024 (order: 1, 8192 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
Checking for 'wait' instruction... unavailable.
POSIX conformance testing by UNIFIX
PCI: Fixing up bus 0
PCI: Fixing up bridge
PCI: Fixing up bus 1
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
PPP generic driver version 2.4.2
Amd/Fujitsu Extended Query Table v1.1 at 0x0040
number of CFI chips: 1
flash device: 400000 at 1fc00000
Physically mapped flash: cramfs filesystem found at block 863
Creating 4 MTD partitions on "Physically mapped flash":
0x00000000-0x00040000 : "pmon"
0x00040000-0x003f0000 : "linux"
0x000d7e24-0x003f0000 : "rootfs"
mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only
0x003f0000-0x00400000 : "nvram"
sflash: chipcommon not found
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 1024 bind 2048)
ip_conntrack version 2.1 (128 buckets, 1024 max) - 344 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
ipt_time loading
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NET4: Ethernet Bridge 008 for NET4.0
VFS: Mounted root (cramfs filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 64k freed
Warning: unable to open an initial console.
eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.31.16.0
eth1: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.31.16.0
PCI: Enabling device 01:08.0 (0004 -> 0006)
eth2: Broadcom BCM43XX 802.11 Wireless Controller 3.31.16.0 (Compiled in . at 18:49:17 on Aug 6 2003)
flag=[get_flash] offset=[0] string=[ULL>]
Write mac init
mac_init()
location = [1]
The mac[1] is available, address=[2012]!
cmd(90,ffffffff)
^Iflashutl_cmd->need_unlock=[1]
flash_reset
^Iflashutl_cmd->clear_csr=[0] flashutl_cmd->read_array=[f0]
scmd(f0,0)
Set flash_type=AMD 29lv320DB 2Mx16 BotB
exit
Algorithmics/MIPS FPU Emulator v1.5
bug: kernel timer added twice at c0017d40.
device eth0 entered promiscuous mode
device eth2 entered promiscuous mode
br0: port 2(eth2) entering learning state
br0: port 1(eth0) entering learning state
br0: port 2(eth2) entering forwarding state
br0: topology change detected, propagating
br0: port 1(eth0) entering forwarding state
br0: topology change detected, propagating
diag_loop: Reset LED.
bug: kernel timer added twice at c0017d40.</pre>
]]></content:encoded>
			<wfw:commentRss>http://blog.waja.info/2004/10/19/boot-messages/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>Wlan Links</title>
		<link>http://blog.waja.info/2004/10/19/wlan-links/</link>
		<comments>http://blog.waja.info/2004/10/19/wlan-links/#comments</comments>
		<pubDate>Tue, 19 Oct 2004 19:53:21 +0000</pubDate>
		<dc:creator>cyco</dc:creator>
				<category><![CDATA[WLan]]></category>
		<category><![CDATA[war-driving]]></category>

		<guid isPermaLink="false">http://blog.waja.info/?p=3</guid>
		<description><![CDATA[Wiki WirelessLan wardriving.com Kismet &#8211; an 802.11 wireless network sniffer Wellenreiter &#8211; WaveLAN hacking THC RELEASES WEPCrack &#8211; An 802.11 key breaker German Wireless LAN HotSpots Wireless Lan Technical Informations and Software Wireless Honeypot Trickery m0n0wall]]></description>
			<content:encoded><![CDATA[<p><a target="_blank" href="http://adenin.rz.uni-konstanz.de/wiki/bin/search/Wireless/?search=WirelessLan&#038;scope=text&#038;ignorecase=on">Wiki WirelessLan</a><br />
<a target="_blank" href="http://www.wardriving.com/">wardriving.com</a><br />
<a target="_blank" href="http://kismetwireless.net/">Kismet &#8211; an 802.11 wireless network sniffer</a><br />
<a target="_blank" href="http://www.remote-exploit.org/">Wellenreiter &#8211; WaveLAN hacking</a><br />
<a target="_blank" href="http://www.thc.org/releases.php">THC RELEASES</a><br />
<a target="_blank" href="http://wepcrack.sourceforge.net/">WEPCrack &#8211; An 802.11 key breaker</a><br />
<a target="_blank" href="http://mobileaccess.de/wlan/">German Wireless LAN HotSpots</a><br />
<a target="_blank" href="http://www.monolith81.de/">Wireless Lan Technical Informations and Software</a><br />
<a target="_blank" href="http://securityfocus.com/infocus/1761">Wireless Honeypot Trickery</a><br />
<a target="_blank" href="http://m0n0.ch/wall/">m0n0wall</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.waja.info/2004/10/19/wlan-links/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>Access Points with Intersil Prism Cards and *nix</title>
		<link>http://blog.waja.info/2004/10/19/access-points-with-intersil-prism-cards-and-nix/</link>
		<comments>http://blog.waja.info/2004/10/19/access-points-with-intersil-prism-cards-and-nix/#comments</comments>
		<pubDate>Tue, 19 Oct 2004 19:52:50 +0000</pubDate>
		<dc:creator>cyco</dc:creator>
				<category><![CDATA[WLan]]></category>

		<guid isPermaLink="false">http://blog.waja.info/?p=4</guid>
		<description><![CDATA[Prism II Access Point Mini-Howto Host AP driver for Intersil Prism2/2.5/3 OpenAP project Running Linux on the Apple Airport Base Station Fake AP Informations about Prism2 a public access point using a striped down version of debian gnu/linux Building a wireless access point on Linux Pebble Linux]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.cafwap.net/prism2ap/" target="_blank">Prism II Access Point Mini-Howto</a><br />
<a href="http://hostap.epitest.fi/" target="_blank">Host AP driver for Intersil Prism2/2.5/3</a><br />
<a href="http://opensource.instant802.com/home.php" target="_blank">OpenAP project</a><br />
<a href="http://www-hft.ee.tu-berlin.de/~strauman/airport/airport.html" target="_blank">Running Linux on the Apple Airport Base Station</a><br />
<a href="http://www.blackalchemy.to/project/fakeap/" target="_blank">Fake AP</a><br />
<a href="http://team.vantronix.net/reyk/prism2/" target="_blank">Informations about Prism2</a><br />
<a href="http://linuxjournal.com/article.php?sid=6897"target="_blank">a public access point using a striped down version of debian gnu/linux</a><br />
<a href="http://www-106.ibm.com/developerworks/library/l-wap.html?ca=dnt-429" target="_blank">Building a wireless access point on Linux</a><br />
<a href="http://www.nycwireless.net/pebble/" target="_blank">Pebble Linux</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.waja.info/2004/10/19/access-points-with-intersil-prism-cards-and-nix/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/</creativeCommons:license>
	</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->