Questions regarding Gargoyle as a client

[lyzby]

Will Gargoyle configured as a client connect to a psk2-protected AP?

Would access from the internet be possible to a webcam on a device plugged into a Gargoyle router configured as a client?

Would USB work on a Gargoyle client router (e.g., WL-520gu, wl-500GPv2, TP WR-1053, Buffalo wzr-hp-g300nh)?

Should an appropriate usb webcam plugged into a Gargoyle client router be accessible from the outside?

Should usb-serial work on Gargoyle client router (same models as are listed above)? Would it matter whether it were broadcom or atheros?

Is there a howto for any of these steps?

Does the Gargoyle web front end do its configuring by modifying the openWrt configuration files in /etc/config, or does it have its own method of doing configuration? If so, is the configuration information viewable as text files?

[Eric]

Yes, you can connect in client mode to a psk2 network.

However, Gargoyle currently does not support USB configuration of any sort (yet) -- you would have to do that manually, and probably compile a custom image with appropriate kernel modules.

While Gargoyle uses some custom packages that do not make use of official configuration files, as much as possible is done through the default OpenWrt configuration system. You can view/edit these options in UCI or by editing config files /etc/config

There really isn't any tutorial that I know of for Gargoyle and USB since this isn't really supported (yet). I would checkout the OpenWrt wiki/forum for more info on these topics and how they relate to OpenWrt.

[lyzby]

I've tried to set up an Asus WL-520gU router (brcm47xx) to be a wifi client to allow device plugged into the router to see the internet and other devices on the other side of the wireless link.

I downloaded the broadcom 2.4 firmware, gargoyle_1.3.5-brcm-2.4-squashfs.trx, flashed it, and used the nice and easy web interface to configure the device. It says it has gotten an IP of 192.168.1.8, and has a gateway and dns of 192.168.1.1. All of this looks reasonable. But I can't ping 192.168.1.1 or http://www.google.com.

The signon text says it is "Backfire (10.03, unknown)", an "uname -a" reports "Linux Gargoyle 2.4.37.9 #3 Mon Sep 6 22:49:16 EDT 2010 mips GNU/Linux".

iwconfig reports the following:

Code: Select all

wl0       IEEE 802.11-DS  ESSID:"Omnibus4"
          Mode:Managed  Frequency:2.432 GHz  Access Point: 00:90:4C:7E:00:6E
          Bit Rate=48 Mb/s   Tx-Power:32 dBm
          RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=5/5  Signal level=-34 dBm  Noise level=-92 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

This is the right mac address for Omnibus4.

/etc/config/wireless looks as I might expect

Code: Select all

config 'wifi-device' 'wl0'
        option 'type' 'broadcom'
        option 'channel' '5'

config 'wifi-iface' 'cfg2'
        option 'device' 'wl0'
        option 'mode' 'sta'
        option 'network' 'wan'
        option 'ssid' 'Omnibus4'
        option 'encryption' 'none'

Here is /etc/config/network

Code: Select all

config 'switch' 'eth0'
        option 'enable' '1'

config 'switch_vlan' 'eth0_0'
        option 'device' 'eth0'
        option 'vlan' '0'
        option 'ports' '1 2 3 4 5'

config 'switch_vlan' 'eth0_1'
        option 'device' 'eth0'
        option 'vlan' '1'
        option 'ports' '0 5'

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 'type' 'bridge'
        option 'ifname' 'eth0.0'
        option 'proto' 'static'
        option 'netmask' '255.255.255.0'
        option 'ipaddr' '192.168.1.54'
        option 'dns' '192.168.1.54'

config 'interface' 'wan'
        option 'proto' 'dhcp'
        option 'type' 'bridge'

The only thing I note about that is that dns under lan says "192.168.1.54", which is the ip which I gave to the lan in the web interface. But I know nothing about bridging, so this may be ok.

I haven't touched /etc/config/firewall.

What do I need to do further to get connected?

[lyzby]

Ok, I'm a step closer. I hadn't set the "Connect via Client Bridge" option. Having done that, rebooted, and SSHed in, I can ping http://www.google.com.

DISREGARD THE FOLLOWING PARAGRAPHS--all is now working from the laptop with no further configuration changes after I unplugged from the Gargoyle box, turned on the wireless on the laptop, plugged back into the Gargoyle box, and turned the laptop wireless back off so that my sole connection now is wired to the Gargoyle box and thru it, wireless to the internet and the rest of my network.

SOLVED--
From my laptop, connected by wire to the Gargoyle box, and not connected wirelessly elsewhere, I can ping 192.168.1.1 and other devices on the other side of the wireless bridge, but I still cannot ping http://www.google.com, and cannot connect to the internet.

ipconfig on the laptop says that the laptop has gotten an ip address of 192.168.1.244 from Gargoyle, and has a default gateway of 192.168.1.54, the Gargoyle lan ip.

Any suggestions on how to complete the connection which is now so close?
--SOLVED