<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel about="http://permalink.gmane.org/gmane.org.freifunk.wlanware">
    <title>gmane.org.freifunk.wlanware</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4856"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4855"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4854"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4853"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4852"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4851"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4850"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4849"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4848"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4847"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4844"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4843"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4842"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4841"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4839"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4838"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4837"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4836"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4834"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4833"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4856">
    <title>Re: [Wien] stream for tonight T.Clausen OLSRv2presentation &lt; at &gt;funkfeuer.at</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware/4856</link>
    <description>Hi!

Kaplan L. Aaron schrieb:
There´s a typo, it´s

http://sc.superbertram.com/archive/

Greetings Gregor

</description>
    <dc:creator>Gregor G.</dc:creator>
    <dc:date>2008-08-13T18:53:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4855">
    <title>dhcpsplash bug in blocked macs</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware/4855</link>
    <description>Hi all

There was a bug in dhcpsplash affecting the blocked mac list in
dhcpsplash. I introduced it myself back in January in the course of a
rewrite of the firewall rules.

The Bug is still present in Freifunk 1.6.30 but is fixed in CVS now.

Lorenz


revision 1.12
date: 2008/08/27 05:52:39;  author: lschori;  state: Exp;  lines: +1 -1
Fixed typo in iptables mac-filtering rule. Thanks to Jose Monteiro for
reporting this.

*** functions.sh    2008-08-27 04:49:47.000000000 +0100
--- functions-broken.sh    2008-08-27 04:50:27.000000000 +0100
***************
*** 166,172 ****
          while read mac hostname ; do
              test -z "$mac" &amp;&amp; continue
              splash_isknownmac "$mac" &amp;&amp; splash_removemac "$mac"
!             $IPTABLES -t filter -I splash_blocked -m mac --mac-source
"$mac" -j DROP &gt;/dev/null 2&gt;&amp;1
          done &lt; /etc/dhcpsplash/blocked
      fi
  }
--- 166,172 ----
          while read mac hostname ; do
              test -z "$mac" &amp;&amp; continue
              splash_isknownmac "$mac" &amp;&amp; sp</description>
    <dc:creator>Lorenz Schori</dc:creator>
    <dc:date>2008-08-27T06:04:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4854">
    <title>Re: Default Gate auswählen</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware/4854</link>
    <description>
Ihr wisst auch, dass man mittels NatThreshold  ein "sticky" gateway  
realisieren kann?

http://www.olsr.org/?q=sticky-gateway

Die route bleibt dann beim naechsten gw "kleben" bis das andere  
wirklich um eben obigen faktor besser geworden ist.

Waere interessiert an feedback. Kein feedback kann entweder heissen,  
dass alles super funktioniert oder dass es niemand wirklich  
verwendet :))

lg,
a.



On Aug 18, 2008, at 12:20 PM, Ufo wrote:


_______________________________________________
WLANware mailing list
WLANware-OytpCXbLH6/k1uMJSBkQmQ&lt; at &gt;public.gmane.org
Abonnement abbestellen? -&gt; https://freifunk.net/mailman/listinfo/wlanware

Weitere Infos zu den freifunk.net Mailinglisten und zur An- und Abmeldung unter http://freifunk.net/mailinglisten

</description>
    <dc:creator>Kaplan L. Aaron</dc:creator>
    <dc:date>2008-08-18T18:38:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4853">
    <title>Re: Default Gate verschlechtern</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware/4853</link>
    <description>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi.


Ich hatte einen Bug im Script gebaut, dort war ein /8 hart codiert.

Grüße,
JoW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIqYlBdputYINPTPMRApVjAJ9ZyKicrflfuQ/vHdeYrZ+GskQpbQCfX+g/
/PpLk8bPlNhfOQlHWbY3RoQ=
=Q5lO
-----END PGP SIGNATURE-----
_______________________________________________
WLANware mailing list
WLANware-OytpCXbLH6/k1uMJSBkQmQ&lt; at &gt;public.gmane.org
Abonnement abbestellen? -&gt; https://freifunk.net/mailman/listinfo/wlanware

Weitere Infos zu den freifunk.net Mailinglisten und zur An- und Abmeldung unter http://freifunk.net/mailinglisten

</description>
    <dc:creator>Jo-Philipp Wich</dc:creator>
    <dc:date>2008-08-18T14:37:53</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4852">
    <title>Re: Default Gate verschlechtern</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware/4852</link>
    <description>Äh, wenn mich meine Rechenkünste nicht täuschen ist 172.21.84.238 IN 
172.21.0.0/16 drinne. Mal eben Netzmaske angewendet: von 172.21.84.238 die 
ersten 16 Bit weg ergibt: 84.238 für den local-part und 172.21 für den 
network-part. Passt wunderbar, und alle haben sich lieb...

Gruß,
Florian
</description>
    <dc:creator>Florian Teply</dc:creator>
    <dc:date>2008-08-18T14:00:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4851">
    <title>Re: Default Gate verschlechtern</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware/4851</link>
    <description>Aloah.


Ich schaue nachher mal...



Grüße,
JoW
_______________________________________________
WLANware mailing list
WLANware-OytpCXbLH6/k1uMJSBkQmQ&lt; at &gt;public.gmane.org
Abonnement abbestellen? -&gt; https://freifunk.net/mailman/listinfo/wlanware

Weitere Infos zu den freifunk.net Mailinglisten und zur An- und Abmeldung unter http://freifunk.net/mailinglisten

</description>
    <dc:creator>Jo-Philipp Wich</dc:creator>
    <dc:date>2008-08-18T12:26:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4850">
    <title>Re: Default Gate verschlechtern</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware/4850</link>
    <description>
Danke.
Habe das Paket installiert und sieht wirklich gut aus. Einfach nutzbar.
Habe aber ein kleines Problem im Webinterface:
Verwaltung: Gateway-Tunnel
Die eingegebene Gateway-Adresse '172.21.84.238' liegt außerhalb des
eingestellten Freifunk-Netzbereiches 172.21.0.0/16! Bitte die
Einstellungen korrigieren. Zurück

Ich hoffe der Autor liest hier mit und könnte nen Fix bauen, ich blick den
Sinn des Codes in gwtun.html nicht wirklich.


ALBI...


_______________________________________________
WLANware mailing list
WLANware-OytpCXbLH6/k1uMJSBkQmQ&lt; at &gt;public.gmane.org
Abonnement abbestellen? -&gt; https://freifunk.net/mailman/listinfo/wlanware

Weitere Infos zu den freifunk.net Mailinglisten und zur An- und Abmeldung unter http://freifunk.net/mailinglisten

</description>
    <dc:creator>Albi Rebmann</dc:creator>
    <dc:date>2008-08-18T12:08:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4849">
    <title>Re: Default Gate auswählen</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware/4849</link>
    <description>Axel schrieb:

unabhängig von der OLSR-Gateway-Variante gibt es noch die Möglichkeit, 
das mit BMX und dessen Tunneldings zu realisieren.

das ganze kann auch mit anderen Tunneln geschehen, also z.b. mit 
OpenVPN. d.h. am Internetgateway ist ein OpenVPN-Server installiert und 
Freifunk-Nodes (oder auch Client-Rechner) verbinden sich dorthin. 
Vorteil dieser Lösung wäre dann gleichzeitig auch eine abhörsichere 
Verbindung zum Internetgateway.
_______________________________________________
WLANware mailing list
WLANware-OytpCXbLH6/k1uMJSBkQmQ&lt; at &gt;public.gmane.org
Abonnement abbestellen? -&gt; https://freifunk.net/mailman/listinfo/wlanware

Weitere Infos zu den freifunk.net Mailinglisten und zur An- und Abmeldung unter http://freifunk.net/mailinglisten

</description>
    <dc:creator>Ufo</dc:creator>
    <dc:date>2008-08-18T10:20:52</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4848">
    <title>Re: Default Gate verschlechtern</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware/4848</link>
    <description>Hallo 

On Samstag 16 August 2008, Albi Rebmann wrote:
Was ist hiermit
http://blogs.k-ita.de/~alx/?p=28
bzw
http://www.freifunk-bno.de/component/option,com_fireboard/Itemid,116/id,11767/catid,13/func,fb_pdf/

lg.
axel


_______________________________________________
WLANware mailing list
WLANware-OytpCXbLH6/k1uMJSBkQmQ&lt; at &gt;public.gmane.org
Abonnement abbestellen? -&gt; https://freifunk.net/mailman/listinfo/wlanware

Weitere Infos zu den freifunk.net Mailinglisten und zur An- und Abmeldung unter http://freifunk.net/mailinglisten

</description>
    <dc:creator>Axel</dc:creator>
    <dc:date>2008-08-17T09:04:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4847">
    <title>Default Gate verschlechtern</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware/4847</link>
    <description>Hallo,

habt ihr mir einen Tip wie wir die Nutzung der Gateways besser steuern
können?
Es gibt 2 Gateways ins Internet, 2 Drittel gehen über den ersten und 1
Drittel über den zweiten Gateway. Problem ist nur, der Zweite hat die
schnellere Internet-Verbindung. Lieber wäre uns das ganze anders rum.
Dummerweise hat der 2. Gateway aber auch die schlechtere WLAN Verbindungen.

Bin für Tricks dankbar.
Die Verbindungen auf den Notes mit LQ Faktor und OLSR Filter zu
manipulieren ist recht kompliziert, da sich normal mindestens 5 Notes
gegenseitig sehen und es insgesamt fast 40 sind. Manche davon sehen über
20. Sprich die Notes stehen recht eng aufeinander.

Wenn ich dem 1. Gateway einfach sagen könnte, er soll sagen Internet ist
nicht so gut beio ihm verfügbar, wäre wohl das einfachste. Sozusagen ein
LQ Faktor fürs Internet. Geht so was?


ALBI...



_______________________________________________
WLANware mailing list
WLANware-OytpCXbLH6/k1uMJSBkQmQ&lt; at &gt;public.gmane.org
Abonnement abbestellen? -&gt; https://frei</description>
    <dc:creator>Albi Rebmann</dc:creator>
    <dc:date>2008-08-16T17:21:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4844">
    <title>second DHCP Spash feture request - lets use our mesh coverage for mobility</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware/4844</link>
    <description>Hi Freifunker,

Basti from Freifunk Weimar has a great implementation of an dhcp-splash
enhancement, which I would like to explain here to maybe get it implemented
into the main dhcp-splash ;o)
The current dhcp-splash just gives you the possibility to ativate dedicated
MAC adresses per node.
In common words spoken: Your laptop gets just a dhcp lease from the node,
where you have manually entred its MAC.
But one of your big advantages in the Freifunk wireless network is the hugh
coverage area.... so beside the idea of put every laptop MAC into every
router by hand.. Basti had a great idea....

The idea:
Every node exchanges it´s current dhcp-splash MAC list via the OLSR service
anouncment plugin over the whole mesh. If a single MAC adress is anounced by
3 or more nodes than all the nodes put this MAC adress into their allowed
MAC list, to give out a dhcp lease.
In common words spoken: You just need to have your Laptop´s MAC adress
enabled on your FF-router and on 2 aditional FF-routers of your friends ...
a</description>
    <dc:creator>Bluse-Blue</dc:creator>
    <dc:date>2008-08-13T21:52:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4843">
    <title>Re: Freifunk 1.6.29, dhcp-splash, and natting</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware/4843</link>
    <description>Hi

Solved.  There was a pesky S45firewall.orig NATting everything on boot.
It is removed in 1.6.30.

Jan
_______________________________________________
WLANware mailing list
WLANware-OytpCXbLH6/k1uMJSBkQmQ&lt; at &gt;public.gmane.org
Abonnement abbestellen? -&gt; https://freifunk.net/mailman/listinfo/wlanware

Weitere Infos zu den freifunk.net Mailinglisten und zur An- und Abmeldung unter http://freifunk.net/mailinglisten

</description>
    <dc:creator>Jan Groenewald</dc:creator>
    <dc:date>2008-08-13T20:42:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4842">
    <title>Re: dhcp-splash problem: MAC adresses get lost after firmware update</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware/4842</link>
    <description>Hallo Bluse

On Wed, 13 Aug 2008 22:10:40 +0200
"Bluse-Blue" &lt;h2o-post-hi6Y0CQ0nG0&lt; at &gt;public.gmane.org&gt; wrote:


Notiert.
https://lab.openwireless.ch/trac/ticket/65

LG
Lorenz

_______________________________________________
WLANware mailing list
WLANware-OytpCXbLH6/k1uMJSBkQmQ&lt; at &gt;public.gmane.org
Abonnement abbestellen? -&gt; https://freifunk.net/mailman/listinfo/wlanware

Weitere Infos zu den freifunk.net Mailinglisten und zur An- und Abmeldung unter http://freifunk.net/mailinglisten

</description>
    <dc:creator>Lorenz Schori</dc:creator>
    <dc:date>2008-08-13T20:28:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4841">
    <title>dhcp-splash problem: MAC adresses get lost afterfirmware update</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware/4841</link>
    <description>Hi Freifunker,

This problem exists quite a while and I would like to request a change of 
dhcp-splash.
In the former and current dhcp-splash releases, the MAC addresses of laptop 
users are not stored permanently ...
and after every Freifunk firmware update... we have to manualy  fill them in 
again after updating a node.
That is very time consuming and also inifficient .. we do need to save the 
users MAC list befor flashing a node.
Could that be changed into a "MAC adresses for dhcp splash are saved 
permanetly in the NVRAM" to keep them ???

Thanks &amp; Bye Bluse 


_______________________________________________
WLANware mailing list
WLANware-OytpCXbLH6/k1uMJSBkQmQ&lt; at &gt;public.gmane.org
Abonnement abbestellen? -&gt; https://freifunk.net/mailman/listinfo/wlanware

Weitere Infos zu den freifunk.net Mailinglisten und zur An- und Abmeldung unter http://freifunk.net/mailinglisten

</description>
    <dc:creator>Bluse-Blue</dc:creator>
    <dc:date>2008-08-13T20:10:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4839">
    <title>Re: nanostation</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware/4839</link>
    <description>_______________________________________________
WLANware mailing list
WLANware-OytpCXbLH6/k1uMJSBkQmQ&lt; at &gt;public.gmane.org
Abonnement abbestellen? -&gt; https://freifunk.net/mailman/listinfo/wlanware

Weitere Infos zu den freifunk.net Mailinglisten und zur An- und Abmeldung unter http://freifunk.net/mailinglisten</description>
    <dc:creator>albert homs</dc:creator>
    <dc:date>2008-08-10T21:19:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4838">
    <title>Re: DHCP pass through</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware/4838</link>
    <description>Hello Jan,

Am Freitag, 8. August 2008 17:29:41 schrieb Jan Groenewald:



Im thinking you have to look for "dhcp-relay"

hth
stefan

_______________________________________________
WLANware mailing list
WLANware-OytpCXbLH6/k1uMJSBkQmQ&lt; at &gt;public.gmane.org
Abonnement abbestellen? -&gt; https://freifunk.net/mailman/listinfo/wlanware

Weitere Infos zu den freifunk.net Mailinglisten und zur An- und Abmeldung unter http://freifunk.net/mailinglisten

</description>
    <dc:creator>stefan</dc:creator>
    <dc:date>2008-08-09T11:16:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4837">
    <title>DHCP pass through</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware/4837</link>
    <description>Hi

I'm using OLSR-DHCP to let laptops join one mesh.

I want to do the same in a new network, but it is for one institution
with a central (LAN) DHCP server, bandwidth and network access rules
accroding to that, and I don't want to duplicate work by redoing
DHCP and adding ranges everywhere.  It is to cover floors without network
points.

Is there some way to allow the central DHCP server traffic through?
To somehow bridge every node? We used to have openwrt bridges
there which worked OK as APs, but they were each plugged into an existing
network point, and now we want to expand.

I want to replace all of them with freifunk nodes, bridge the WAN+Wireless IP
where the do have a WAN connection to the institution's LAN, and have just the
wireless IP on those not connected by ethernet. Can I just go look in
/etc/init.d/S45firewall
for the appropriate DHCP lines? Or are there other issues to watch out for?

regards,
Jan
_______________________________________________
WLANware mailing list
WLANware-OytpCXbLH6/k1u</description>
    <dc:creator>Jan Groenewald</dc:creator>
    <dc:date>2008-08-08T15:29:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4836">
    <title>Re: (mesh networks) announcement: T. Clausen speaking atfunkfeuer.at/metalab</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware/4836</link>
    <description>
pardon me: Wednesday, 13th of Aug  19:00
yes, we will have video streaming.


_______________________________________________
WLANware mailing list
WLANware-OytpCXbLH6/k1uMJSBkQmQ&lt; at &gt;public.gmane.org
Abonnement abbestellen? -&gt; https://freifunk.net/mailman/listinfo/wlanware

Weitere Infos zu den freifunk.net Mailinglisten und zur An- und Abmeldung unter http://freifunk.net/mailinglisten

</description>
    <dc:creator>aaron</dc:creator>
    <dc:date>2008-08-07T16:07:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4834">
    <title>Re: (mesh networks) announcement: T. Clausen speakingatfunkfeuer.at/metalab</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware/4834</link>
    <description>Hello! 

The lecture is very important for everyone in the field, as well as in the
academy. 

Unfortunately, many won't have the opportunity to go to the beautiful Wien
in the next days. 

Wouldn't it be possible for you to film the lecture and make it available
on the 'Net ? 

Of course, provided that Clausen authorizes the use of his image. 

All the best,
hilton  

On Thu, Aug 7, 2008, aaron &lt;aaron-oXXRWhoacHMdnm+yROfE0A&lt; at &gt;public.gmane.org&gt; said:


</description>
    <dc:creator>Hilton Garcia Fernandes</dc:creator>
    <dc:date>2008-08-07T14:38:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4833">
    <title>(mesh networks) announcement: T. Clausen speaking atfunkfeuer.at/metalab</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware/4833</link>
    <description>

Advanced topics in MANETs lecture series  at funkfeuer.at


TITLE
OLSRv2 status report and finetuning of the new RFC to the needs of
community wifi networks.

Who:       Thomas Clausen
When?    Wednesday, 13th of Aug.
Where?  www.metalab.at, Rathausstrasse 6, A-1010 Vienna,
(http://metalab.at/wiki/Lage)

Announced presence: Henning Rogge, core commiter at www.olsr.org



T. Clausen, one of the authors of RFC 3626 (OLSR) - which is being used
as the mesh routing protocol in Funkfeuer.at, Freifunk.net, Athens
Metropolitan Network and many other community networks in the world as
well as in industry , will give a small talk in front of funkfeuer.at
and interested mesh network researchers.
OLSR is probably *the* most widely deployed proactive mesh protocol
worldwide apart from proprietary US .mil mesh networks.
Thomas Clausen will describe the upcoming OLSR v2 RFC which can
accomodate many features requested by the user community and also fine
tune things with folks from funkfeuer.at based on our needs.


For </description>
    <dc:creator>aaron</dc:creator>
    <dc:date>2008-08-07T13:28:10</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.org.freifunk.wlanware/4832">
    <title>Re: [Kontaktaufnahme] Robin on Fonera 2200 usingEasyflash</title>
    <link>http://permalink.gmane.org/gmane.org.freifunk.wlanware/4832</link>
    <description>Alex,

I personally do not own a fonera2200 - but I have had one on my desk a 
couple of months ago. I remember fiddeling with a funny vlan chip - 
something not avail in openwrt but found a solution in dd-wrt. While 
flashing there are no problems then - and yes, the 2200 was the first device 
with no flash-protection - FON has set an IP addr for redboot by default.

Your eth config is compatible? Try a fixed ip addr - mostly windoze users 
complain because eth carrier detection needs too long.

You may find this post interesting (I'll attach it FYI). Comment on this 
post welcome. You may also want this URL 
http://ff-firmware.cvs.sourceforge.net/ff-firmware/ap51-flash/

// Sven-Ola

""freifunk.net Webteam"" &lt;info-OytpCXbLH6/k1uMJSBkQmQ&lt; at &gt;public.gmane.org&gt; schrieb im Newsbeitrag 
news:48988E87.70703-OytpCXbLH68MN+8nz9vMXQ&lt; at &gt;public.gmane.org
alex-mm8o1/73UMOakBO8gow8eQ&lt; at &gt;public.gmane.org schrieb:

Hi Alex,

I have fowarded your mail to our mailinglist wlanware-XldJvJHSqK/uFKmmi/icCA&lt; at &gt;public.gmane.org There
are the</description>
    <dc:creator>Sven-Ola Tuecke</dc:creator>
    <dc:date>2008-08-06T10:47:04</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.org.freifunk.wlanware">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.org.freifunk.wlanware</link>
  </textinput>
</rdf:RDF>
