headers
Jo-Philipp Wich | 18 Aug 16:37

Re: Default Gate verschlechtern


Hi.

> Ä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...

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

Grüße,
JoW
Permalink | Reply | 0 comments |
headers
Jo-Philipp Wich | 18 Aug 14:26

Re: Default Gate verschlechtern

Aloah.

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

Ich schaue nachher mal...

Grüße,
JoW
_______________________________________________
WLANware mailing list
WLANware@...
Abonnement abbestellen? -> https://freifunk.net/mailman/listinfo/wlanware

Weitere Infos zu den freifunk.net Mailinglisten und zur An- und Abmeldung unter http://freifunk.net/mailinglisten
Permalink | Reply | 0 comments |
headers
Ufo | 18 Aug 12:20

Re: Default Gate auswählen

Axel schrieb:
> Hallo 
> 
> On Samstag 16 August 2008, Albi Rebmann wrote:
>> Hallo,
>>
>> habt ihr mir einen Tip wie wir die Nutzung der Gateways besser steuern
>> können?
> 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/
> 

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@...
Abonnement abbestellen? -> https://freifunk.net/mailman/listinfo/wlanware

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

Permalink | Reply | 1 comment |
headers
Albi Rebmann | 16 Aug 19:18

Default Gate verschlechtern

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@...
Abonnement abbestellen? -> https://freifunk.net/mailman/listinfo/wlanware

Weitere Infos zu den freifunk.net Mailinglisten und zur An- und Abmeldung unter http://freifunk.net/mailinglisten
Permalink | Reply | 3 comments |
headers
Bluse-Blue | 13 Aug 23:49

second DHCP Spash feture request - let´s use our mesh coverage for mobility

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 ...
and than your laptop will get a dhcp lease from all routers in the mesh ...
city or village wide !!!

pros: -the administration overhead of enabling mobil users in the mesh is
nicely delegatetd to a trusted decentralised system
         -we use coverage advantage of our Freifunk networks to enable
mobile users very easily compared to stand alone access point networks

In the next days I will provide the relevant parts of Basti´s code base from
Freifunk Weimar.. that may give a starting point.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bluse-Blue | 13 Aug 22:07

dhcp-splash problem: MAC adresses get lost after firmware update

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 & Bye Bluse 

_______________________________________________
WLANware mailing list
WLANware@...
Abonnement abbestellen? -> https://freifunk.net/mailman/listinfo/wlanware

Weitere Infos zu den freifunk.net Mailinglisten und zur An- und Abmeldung unter http://freifunk.net/mailinglisten
Permalink | Reply | 1 comment |
headers
Jan Groenewald | 8 Aug 17:28

DHCP pass through

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@...
Abonnement abbestellen? -> https://freifunk.net/mailman/listinfo/wlanware

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

Permalink | Reply | 1 comment |
headers
aaron | 7 Aug 15:26

(mesh networks) announcement: T. Clausen speaking at funkfeuer.at/metalab


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 international guests - try to get a cheap flight and let me know if
you need a place to sleep.
Please forward this mail to people who are interested in mesh network
research.
Sorry, in case you got this mail twice. I will probably make a list of
(Continue reading)

Permalink | Reply | 3 comments |
headers
freifunk.net Webteam | 5 Aug 19:31

Re: [Kontaktaufnahme] Robin on Fonera 2200 using Easyflash

alex@... schrieb:
> Alexandre Girard hat eine Nachricht mit dem Kontaktformular auf
> http://start.freifunk.net/contact geschickt.
> 
> Hi,
> 
> I'm coming from open-mesh.org webpage -
> http://www.open-mesh.com/activekb/questions/8/Flashing+the+Accton+Mini-Router+with+ROBIN
> 
> - to tell you about an issue with Easyflash.
> 
> I've been try to flash a Fonera 2200 with ROBIN using Easyflash, but I got
> the following message:
> 
> "Expect arp with length 60, received 42"
> 
> Some other people seems to get the same thing in dd-wrt forum.
> I wonder if you have already encounter the same problem, and a solution to
> it? If not, have you got any idea of where it could come from?
> 
> Thanks a lot,
> 
> Alex

Hi Alex,

I have fowarded your mail to our mailinglist wlanware@... There
are the experts.

Please subscribe at https://freifunk.net/mailman/listinfo/wlanware to
(Continue reading)

Permalink | Reply | 1 comment |
headers
Jan Groenewald | 5 Aug 12:48

nanostation

Hi

Is there a freifunk image which runs on the ubiquity nanostation 2?
What are the issues with this?

regards,
Jan
_______________________________________________
WLANware mailing list
WLANware@...
Abonnement abbestellen? -> https://freifunk.net/mailman/listinfo/wlanware

Weitere Infos zu den freifunk.net Mailinglisten und zur An- und Abmeldung unter http://freifunk.net/mailinglisten
Permalink | Reply | 2 comments |
headers
Don Davis | 27 Jul 18:23

basic init script question for freifunk + batmand 0.3


Hello, we're making a mesh with WRT54GLs.
With freifunk and batman 0.3.

For the nodes I have the init script

S97nodestartup.sh
#! /bin/sh
batmand eth1

which works fine.  But for the gateway I tried

S97gatewaystartup.sh
#! /bin/sh
batmand -g 5mbit eth1 vlan

In a best case scenario it has to be killed and restarted.  In less than 
ideal circumstances it freezes the router up.
I think this is because it needs to wait a bit longer in the boot up 
cycle to start after a dhcp lease has been given to the router.

Is there a script like 'watchout4batman' for the new batman that tests 
for internet connectivity and announces the router as a gateway or if no 
internet connectivity then as a gateway?  Or better yet a script that 
can be run as a cronjob to do the same thing and if batman isn't running 
to bring it up again?

_______________________________________________
WLANware mailing list
WLANware@...
(Continue reading)

Permalink | Reply | 0 comments |

Gmane