I installed Gargoyle as a set of packages on my Fonera (I changed file /usr/lib/ipkg/lists/gargoyle because md5sum's was wrong and packages can't install).
I have configured Kamikaze in mixed mode (AP+Client) - it works.
My configuration:
/etc/config/network
config interface loopback
option ifname lo
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0
config interface lan
option ifname eth0 ath0
option type bridge
option proto static
option ipaddr 192.168.3.1
option netmask 255.255.255.0
config interface wan
option ifname ath1
option proto dhcp
/etc/config/wireless
config wifi-device wifi0
option type atheros
option agmode 11bg
option channel 1
config wifi-iface
option device wifi0
option mode ap
option network lan
option ssid Skynet
option encryption psk2
option key 'd4553@5!&tg56*hj'
config wifi-iface
option device wifi0
option mode sta
option network wan
option ssid Solaris
option encryption psk2
option key 'd4553@5!&tg56*hj'
1). I can't see proper settings via Gargoyle.
No value 'LAN MAC Address', 'WAN IP Address' and 'WAN MAC Address' in 'Status' (see http://laptok.republika.pl/status.jpg).
2). No proper settins in 'Connection > Basic' (see http://laptok.republika.pl/basic.jpg). I thing it should be like this: http://laptok.republika.pl/basic2.jpg, but when i push 'Save Changes' i see again wrong seetings: [url http://laptok.republika.pl/basic.jpg[/url]. My /etc/config/wireless was changed and looks that:
config 'wifi-device' 'wifi0'
option 'type' 'atheros'
option 'agmode' '11bg'
option 'channel' '1'
config 'wifi-iface' 'cfg2'
option 'device' 'wifi0'
option 'mode' 'ap'
option 'network' 'lan'
option 'ssid' 'Skynet'
option 'encryption' 'psk2'
option 'key' 'd4553@5!&tg56*hj'
config 'wifi-iface' 'cfg3'
option 'device' 'wifi0'
option 'mode' 'sta'
option 'ssid' 'Solaris'
option 'encryption' 'none'
3). I can't set encryption on 'WPA2 PSK', only 'WPA PSK' and 'WEP' is possible in 'SSID to Join' (see http://laptok.republika.pl/basic3.jpg).
4). I have Static DHCP:
/etc/ethers
00:18:DE:23:AE:5D 192.168.3.2
00:15:58:30:80:A7 192.168.3.3
Gargoyle change file /etc/ethers and file looks that:
00:18:DE:23:AE:5D .2
00:15:58:30:80:A7 .3
After changes in file /etc/ethers by Gargoyle, Static DHCP don't work (example: 00:15:58:30:80:A7 get 192.168.3.143).
Fonera, AP+Client
Moderator: Moderators
Re: Fonera, AP+Client
Thanks for posting about the problem and providing such detailed configuration info. I think I see what's going on -- the root of the issue is your issue (3).
When testing my Fonera in client-mode, connecting to a broadcom router wpa psk2 does not work, only wpa psk. For this reason, even though this may work between atheros routers, this configuration is not officially supported in Gargoyle. I would rather have a situation where a feature is available in openwrt, but not supported by Gargoyle, than implement a feature that is only partially supported. What happened is that Gargoyle saw a configuration it didn't recognize/allow and choked.
The real issue is that there should have been better error checking to prevent all the subsequent errors that you see because of this initial problem. I have implemented such error checking in svn r29 & r30. Now, if you initially have your config set to client mode with wpa psk2 encryption, it will default to wpa psk encryption instead of none (though you'll still need to change the AP it connects to as well if you want to use Gargoyle to configure to configure client mode). Several other checks that prevent a couple of the other problems you see have also been implemented.
Since this is a fairly major issue I've updated the packages (though not the firmware images) to builds from svn r30. Try updating to the latest packages if you still want to use Gargoyle given that it doesn't support wpa psk2 encryption for atheros devices in client mode.
When testing my Fonera in client-mode, connecting to a broadcom router wpa psk2 does not work, only wpa psk. For this reason, even though this may work between atheros routers, this configuration is not officially supported in Gargoyle. I would rather have a situation where a feature is available in openwrt, but not supported by Gargoyle, than implement a feature that is only partially supported. What happened is that Gargoyle saw a configuration it didn't recognize/allow and choked.
The real issue is that there should have been better error checking to prevent all the subsequent errors that you see because of this initial problem. I have implemented such error checking in svn r29 & r30. Now, if you initially have your config set to client mode with wpa psk2 encryption, it will default to wpa psk encryption instead of none (though you'll still need to change the AP it connects to as well if you want to use Gargoyle to configure to configure client mode). Several other checks that prevent a couple of the other problems you see have also been implemented.
Since this is a fairly major issue I've updated the packages (though not the firmware images) to builds from svn r30. Try updating to the latest packages if you still want to use Gargoyle given that it doesn't support wpa psk2 encryption for atheros devices in client mode.
Re: Fonera, AP+Client
Hmm, I connecting my fonera in client-mode to a broadcom router (WRT54GS v4, fv. Thibor v15c) and WPA PSK2 work. But WEP encryption dosn't work 