[isf-wifidog] mesh
Philippe April
isf_lists at philippeapril.com
Mer 8 Juin 10:42:01 EDT 2005
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
There's one thing that hasn't worked:
on 'default', wds0.2 joined the bridge, it shouldn't have.
So perhaps this part:
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
Isn't doing the job, the wds link seems to STILL join br0.
Can you send me (before you act on the changes below) the output of:
nvram show | grep ^wan_
Just to confirm the changes were committed alright.
Now, what we could do is to break br0, it should work after that (on
default).
nvram set lan_ifnames=vlan0
nvram set lan_ifname=vlan0
nvram set wifi_ifnames=eth1
nvram set wifi_ifname=eth1
nvram set wifi_ipaddr=192.168.20.1
nvram set wifi_netmask=255.255.255.0
nvram set wifi_proto=static
And edit /etc/dnsmasq.conf to add another line:
dhcp-range=192.168.20.100,192.168.20.250,255.255.255.0,12h
To have DHCP enabled also on the "new" wireless link (eth1 now that
it's separated).
Now, wds0.2 should NOT join br0 anymore (doesn't exist).
And you should have vlan0 = your lan ports and eth1 = your wireless.
So you could now change wifidog's config to use eth1 instead of br0.
Let me know if we're heading somewhere with this.
On 8-Jun-05, at 5:54 AM, Dr. Marios Moutzouris wrote:
> Okay here is the spew
> neuronA(router 1) - is the main linksys that has an internet
> connection
> default(router 2) - the other linksys that has to get an internet
> connection
> from neuronA
> + root at neuronA:~# ifconfig -a
> br0 Link encap:Ethernet HWaddr 00:12:17:C7:93:A3
> inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:
> 255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:247 errors:0 dropped:0 overruns:0 frame:0
> TX packets:174 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:22721 (22.1 KiB) TX bytes:25088 (24.5 KiB)
> eth0 Link encap:Ethernet HWaddr 00:12:17:C7:93:A3
> UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
> RX packets:1116 errors:0 dropped:0 overruns:0 frame:0
> TX packets:300 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:103076 (100.6 KiB) TX bytes:38657 (37.7 KiB)
> Interrupt:5 Base address:0x2000
> eth1 Link encap:Ethernet HWaddr 00:12:17:C7:93:A5
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:213
> TX packets:23 errors:6 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:0 (0.0 B) TX bytes:2779 (2.7 KiB)
> Interrupt:4 Base address:0x1000
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
> vlan0 Link encap:Ethernet HWaddr 00:12:17:C7:93:A3
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:247 errors:0 dropped:0 overruns:0 frame:0
> TX packets:174 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:23917 (23.3 KiB) TX bytes:25784 (25.1 KiB)
> vlan1 Link encap:Ethernet HWaddr 00:12:17:C7:93:A4
> inet addr:192.168.0.220 Bcast:192.168.0.255 Mask:
> 255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:515 errors:0 dropped:0 overruns:0 frame:0
> TX packets:126 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:42441 (41.4 KiB) TX bytes:12873 (12.5 KiB)
> wds0.2 Link encap:Ethernet HWaddr 00:12:17:C7:93:A5
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
> + root at neuronA:~# netstat -rn
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window
> irtt
> Iface
> 192.168.2.0 0.0.0.0 255.255.255.0 U 40
> 0 0 br0
> 192.168.0.0 0.0.0.0 255.255.255.0 U 40
> 0 0
> vlan1
> 0.0.0.0 192.168.0.1 0.0.0.0 UG 40
> 0 0
> vlan1
> + root at default:~# ifconfig -a
> br0 Link encap:Ethernet HWaddr 00:0F:66:C8:78:43
> inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:
> 255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:823 errors:0 dropped:0 overruns:0 frame:0
> TX packets:535 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:104554 (102.1 KiB) TX bytes:65823 (64.2 KiB)
>
> eth0 Link encap:Ethernet HWaddr 00:0F:66:C8:78:43
> UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
> RX packets:824 errors:0 dropped:0 overruns:0 frame:0
> TX packets:535 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:122801 (119.9 KiB) TX bytes:67963 (66.3 KiB)
> Interrupt:5 Base address:0x2000
>
> eth1 Link encap:Ethernet HWaddr 00:0F:66:C8:78:45
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:72
> TX packets:35 errors:27 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:0 (0.0 B) TX bytes:8214 (8.0 KiB)
> Interrupt:4 Base address:0x1000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> vlan0 Link encap:Ethernet HWaddr 00:0F:66:C8:78:43
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:824 errors:0 dropped:0 overruns:0 frame:0
> TX packets:535 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:107969 (105.4 KiB) TX bytes:67963 (66.3 KiB)
>
> wds0.2 Link encap:Ethernet HWaddr 00:0F:66:C8:78:45
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> root at default:~# netstat -rn
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window
> irtt
> Iface
> 192.168.1.0 0.0.0.0 255.255.255.0 U 40
> 0 0 br0
>
> root at default:~# brctl show
> bridge name bridge id STP enabled interfaces
> br0 8000.000f66c87843 no vlan0
> eth1
> wds0.2
>
> root at default:~# wl channel
> No scan in progress.
> current mac channel 6
> target channel 6
>
> root at neuronA:~# brctl show
> bridge name bridge id STP enabled interfaces
> br0 8000.001217c793a3 no vlan0
> eth1
> wds0.2
>
>
>
> root at neuronA:~# wl channel
> No scan in progress.
> current mac channel 6
> target channel 6
>
>
>
>
>
> -----Original Message-----
> From: wifidog-bounces at listes.ilesansfil.org
> [mailto:wifidog-bounces at listes.ilesansfil.org] On Behalf Of
> Philippe April
> Sent: Tuesday, June 07, 2005 4:34 PM
> To: WiFiDog Captive Portal
> Subject: Re: [isf-wifidog] mesh
>
> -----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-----
> _______________________________________________
> WiFiDog mailing list
> WiFiDog at listes.ilesansfil.org
> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>
> --
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.323 / Virus Database: 267.6.4 - Release Date: 6/6/2005
>
>
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.323 / Virus Database: 267.6.5 - Release Date: 7/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)
iD8DBQFCpwO5Oq+Ep5Xn/aARAh2FAJ0WBjaCb50fo3tluwq6sFmBxtsBKQCZATYp
+dJEWLzKgyPevQK9OMvj0Ak=
=xx8r
-----END PGP SIGNATURE-----
More information about the WiFiDog
mailing list