<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: HOWTO: Upgrading the Firmware on your Nokia M1122 / MW1122</title>
	<atom:link href="http://rob-the.geek.nz/2005/03/howto-upgrading-the-firmware-on-your-nokia-m1122-mw1122.html/feed" rel="self" type="application/rss+xml" />
	<link>http://rob-the.geek.nz/2005/03/howto-upgrading-the-firmware-on-your-nokia-m1122-mw1122.html</link>
	<description>Technology, Open Thinking, Community &#38; Education...</description>
	<lastBuildDate>Wed, 21 Jul 2010 10:05:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: Rob</title>
		<link>http://rob-the.geek.nz/2005/03/howto-upgrading-the-firmware-on-your-nokia-m1122-mw1122.html/comment-page-1#comment-75</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Sun, 13 Mar 2005 21:31:55 +0000</pubDate>
		<guid isPermaLink="false">http://inskeep.sandpit.biz/inskeep.net/Rob/blog/?p=9#comment-75</guid>
		<description>Just to let anyone reading this know that, following the update I would get some weird timeouts on the MW1122 and the network would drop with the DHCP service failing to assign new addresses or route traffic, this was happenning around midnightish over Friday/Sat and it wasn&#039;t until Sunday that I found that the new firmware had introduced a new default of not bridging the traffic between the Ethernet and the Wireless interface. With this bridging turned on, all things seem to be working nice and stable once more.</description>
		<content:encoded><![CDATA[<p>Just to let anyone reading this know that, following the update I would get some weird timeouts on the MW1122 and the network would drop with the DHCP service failing to assign new addresses or route traffic, this was happenning around midnightish over Friday/Sat and it wasn&#8217;t until Sunday that I found that the new firmware had introduced a new default of not bridging the traffic between the Ethernet and the Wireless interface. With this bridging turned on, all things seem to be working nice and stable once more.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
