Hi Georg, On Fri, 02 Feb 2007 at 22:54 +0100, Georg C. F. Greve wrote: > Hi all, > > after I've come to like FreeWRT much more than OpenWRT by now, I've > been working on migrating my home network to FreeWRT and I was almost > successful. Everything worked perfectly until I migrated the access > point, but since then the wireless is behaving erratic, unreliable and > I cannot figure out why. That's why I need your help. > > Here is the setup: > > [internet] --- [ AP: Linksys WRT54GL ] ...(wlan)... [ SL: Linksys WRT54GL ] > . > . > . > (wlan) > . > . > [ ON: ASUS WL 500g ] > > AP = Access point, connected by cable to cable modem (internet via DHCP). > > SL = Server Location, working as bridge > > ON = Office Network, working as bridge > > To keep things simple, I have three networks: > > 192.168.1.1 is the subnet of the access point > 192.168.2.1 is the subnet of the servers > 192.168.3.1 is the subnet of the office > > Here is the network setup file (/etc/network/interfaces) of the AP:
> # basic network configuration file > # for more information, see the FreeWRT handbook > # http://www.freewrt.org/trac/wiki/Documentation/Handbook > > auto lo > iface lo inet loopback > > # LAN ports > auto eth0.0 > iface eth0.0 inet manual > switch-ports 0 1 2 3 5* > > # Local network is bridged between WLAN & LAN > auto br0 > iface br0 inet static > bridge-ifaces eth0.0 eth1 > address 192.168.1.1 > netmask 255.255.255.0 > up route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.1.2 dev > $IFACE > up route add -net 192.168.3.0 netmask 255.255.255.0 gw 192.168.1.3 dev > $IFACE > > # WAN port gets its IP via DHCP > auto eth0.1 > iface eth0.1 inet dhcp > switch-ports 4 5 > > # WLAN with WPA2 > auto eth1 > iface eth1 inet manual > wireless-type broadcom > wireless-country CH > wireless-mode ap > wireless-ssid <essid> > wireless-channel 4 > wireless-security wpa-psk > wireless-authorization psk2 > wireless-encryption aes+tkip > wireless-wpa-key <wpa2 key> > > of the Server Location bridge: > # basic network configuration file > # for more information, see the FreeWRT handbook > # http://www.freewrt.org/trac/wiki/Documentation/Handbook > > auto lo > iface lo inet loopback > > # LAN & WAN ports all on one interface > auto eth0.0 > iface eth0.0 inet static > address 192.168.2.1 > netmask 255.255.255.0 > switch-ports 0 1 2 3 4 5* > > # WLAN with WPA2 > auto eth1 > iface eth1 inet static > address 192.168.1.2 > netmask 255.255.255.0 > gateway 192.168.1.1 > up route add -net 192.168.3.0 netmask 255.255.255.0 gw 192.168.1.3 dev > $IFACE > wireless-type broadcom > wireless-country CH > wireless-mode sta > wireless-ssid <essid> > wireless-channel 4 > wireless-security wpa-psk > wireless-authorization psk2 > wireless-encryption aes+tkip > wireless-wpa-key <wpa2 key> > > and of the Office Network: > # basic network configuration file > # for more information, see the FreeWRT handbook > # http://www.freewrt.org/trac/wiki/Documentation/Handbook > > auto lo > iface lo inet loopback > > # LAN & WAN ports on local bridge > auto br0 > iface br0 inet static > bridge-ifaces eth0 eth1 > address 192.168.3.1 > netmask 255.255.255.0 > > # WLAN with WPA2 > auto eth2 > iface eth2 inet static > address 192.168.1.3 > netmask 255.255.255.0 > gateway 192.168.1.1 > up route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.1.2 dev > $IFACE > wireless-type broadcom > wireless-country CH > wireless-mode sta > wireless-ssid <essid> > wireless-channel 4 > wireless-security wpa-psk > wireless-authorization psk2 > wireless-encryption aes+tkip > wireless-wpa-key <wpa2 key> > > > All of these nodes eventually connect to each other. As soon as a > second or third connects, the whole thing seems to breaks down, > however. > > When the AP was running OpenWRT Whiterussian RC5 and the other two > boxes were running FreeWRT 1.0 revision 1827, all worked fine. The > problems started after I migrated the access point. > > So my guess is that I am missing something about the access point. > > But what? First of all some background information. We are using the wireless drivers and WPA daemon from Whiterussian RC5. The system code for the broadcom devices is nearly the same, too. One difference between FreeWRT and OpenWrt is, that we use the binary-only "wl" util to configure the Wireless card. OpenWrt uses wlcompat to allow "iwconfig" to work for partly configuring wireless. (we also provide wlcompat and iwconfig) All the other stuff is configured via another command line tool developed by OpenWrt called wlc. Now to your problem, you are using bridging between LAN and WLAN on your AP, did you update to the version with the ebtables kernel patch removed? And did you rebuild? If you use a bridge, please put the bridge as last configured network device (we might need to fix our documentation), because otherwise the devices which should be added to the bridge, might not be activated. What you get with cat /proc/net/wl0 on the AP when you have problems? Can you use wl utility to get some more information about signal quality? So the AP only misbehaves if you use a Laptop for example to connect to it? After that both FreeWRT routers can not access the AP anymore? Are they still associated? Use "wl" to get some more information about the broken situation. Because we are using the same driver in FreeWRT as OpenWrt uses, I think it might be a configuration problem or a bug in our scripts. good luck Waldemar -- don't open your wrt, free it http://www.freewrt.org _______________________________________________ freewrt-users mailing list freewrt-users@freewrt.org https://www.freewrt.org/lists/listinfo/freewrt-users
