[isf-wifidog] mesh

[Philippe April]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Can you give more détails on why and what didn't work exactly?

If the setup is still in place, send me the output of:

ifconfig -a
netstat -rn
brctl show
wl channel

for both routers.

Oh, I forgot to mention, you need to install the 'wl' package I think  
in order for WDS to work.

On 7-Jun-05, at 8:38 AM, Dr. Marios Moutzouris wrote:

> I tried, but no luck:(
>
> Any other ideas?
>
> Marios
>
> -----Original Message-----
> From: wifidog-bounces at listes.ilesansfil.org
> [mailto:wifidog-bounces at listes.ilesansfil.org] On Behalf Of  
> Philippe April
> Sent: Monday, June 06, 2005 3:34 PM
> To: WiFiDog Captive Portal
> Subject: Re: [isf-wifidog] mesh
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Here's what I would do:
>
> Put them both on the same channel (no need to be same ssid)
>
> router 1:
> nvram set wl0_wds=mac_of_router_2's_wifi_interface
>
> router 2:
> nvram set wl0_wds=mac_of_router_1's_wifi_interface
>
> Also set the wl_wds variables to the same thing, it's said that it's
> required to have both (did anybody research this and can answer why?)
>
> Turn off lazy_wds. Basically with that, anybody can make you a WDS
> peer and you'll accept. No need.
>
> nvram set wl0_lazywds=0
>
> WDS links will join the bridge br0 by default. What we can try, is
> basically try to make the "client" (one that'll take the internet
> from the other)'s WAN config, the new wds link.
>
> #router2 (client)
> nvram set wan_ifnames=wds0.2
> nvram set wan_ifname=wds0.2
> nvram set wan_ipaddr=192.168.1.2
> nvram set wan_netmask=255.255.255.0
> nvram set wan_gateway=192.168.1.1
> nvram set wan_proto=static
>
> #change the IP address of the bridge, since it'll overlap with WAN
> otherwise
> nvram set lan_ipaddr=192.168.2.1
>
> #commit
> nvram commit
>
> Edit /etc/dnsmasq.conf to make it give IPs on 192.168.2.x instead of
> 192.168.1.x.
>
> So basically what I'm trying to do:
>
> #router1 - gateway
> LAN - br0: LAN ports + WIFI + WDS link (192.168.1.x)
> WAN - vlan1: Internet, you know how to configure this
>
> (basically, the usual config)
>
> #router2 - client
> LAN - br0: LAN ports + WIFI
> WAN - wds0.2: WDS link (192.168.1.2)
>
> (we're replacing the WAN link to the WDS link, so the scripts should
> do NATting to that now instead of vlan1 + default route).
>
> Make wifidog listen on br0 on both.
>
> Okay I'm totally doing this _untested_, but it should work. Feel free
> to ask questions, it's tricky ;)
>
> I'd love to see if Freifunk is doing something similar. They might
> have added custom scripts to deal with... custom setups like this  
> one :)
>
> On 6-Jun-05, at 6:33 AM, Dr. Marios Moutzouris wrote:
>
>
>> I was hoping that it would be simply tweaking some of the nvram
>> variables on
>> a standard openwrt installation. Can it not be done so?
>>
>> Thanks
>> Marios
>>
>> -----Original Message-----
>> From: wifidog-bounces at listes.ilesansfil.org
>> [mailto:wifidog-bounces at listes.ilesansfil.org] On Behalf Of Jo Walsh
>> Sent: Monday, June 06, 2005 1:29 PM
>> To: WiFiDog Captive Portal
>> Subject: Re: [isf-wifidog] mesh
>>
>> On Mon, Jun 06, 2005 at 01:09:39PM +0300, Dr. Marios Moutzouris  
>> wrote:
>>
>>
>>> I don?t know whether it belongs here, but.....how do I setup two
>>> or more
>>> linksys's in a form of mesh where only one receives an internet
>>> connection
>>> and is "shared" amongst the others. Obviously wifidog will need to
>>> be run
>>>
>>>
>> on
>>
>>
>>> each of them.
>>>
>>>
>>
>> we've had very good experiences with the Freifunk Firmware, a mesh
>> routing openWRT distribution. It has a friendly web admin GUI if you
>> visit its port 80. the ISF Wifidog ipkg runs on it just fine.
>> http://www.freifunk.net/wiki/FreifunkFirmwareEnglish
>>
>>
>> -jo
>>
>>
>>
>> -- 
>> No virus found in this incoming message.
>> Checked by AVG Anti-Virus.
>> Version: 7.0.323 / Virus Database: 267.6.2 - Release Date: 4/6/2005
>>
>>
>>
>> -- 
>> No virus found in this outgoing message.
>> Checked by AVG Anti-Virus.
>> Version: 7.0.323 / Virus Database: 267.6.2 - Release Date: 4/6/2005
>>
>>
>> _______________________________________________
>> WiFiDog mailing list
>> WiFiDog at listes.ilesansfil.org
>> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>>
>
> Philippe April
> GnuPG http://key.philippeapril.com
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (Darwin)
>
> iD8DBQFCpEKqOq+Ep5Xn/aARAhjXAKCq7ifma7DyM+5ObQedFclhUtVQawCdFXWH
> K7sKPOv4UnBZ5XpBp80DuXc=
> =gyz2
> -----END PGP SIGNATURE-----
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.323 / Virus Database: 267.6.2 - Release Date: 4/6/2005
>
>
>
> -- 
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.323 / Virus Database: 267.6.4 - Release Date: 6/6/2005
>
>
> _______________________________________________
> WiFiDog mailing list
> WiFiDog at listes.ilesansfil.org
> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog

Philippe April
GnuPG http://key.philippeapril.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFCpaI7Oq+Ep5Xn/aARAir4AJ0TAgltP/D1zFTzh2v92SCzYWILqwCeJPGN
eRaxkVcPlJ86ZB7uYwuS+lg=
=oYVz
-----END PGP SIGNATURE-----