WGT634U wifi?

[stanelie]

Hello.

I flashed my WGT634U with the latest gargoyle_1.5.2-brcm47xx-squashfs.trx firmware. It appears to be working fine except for everything related to wifi. I can set it up, in access point or client-bridge mode, but it doesn't work. In access point mode, I get no broadcast, and in client-bridge mode, it doesn't connect.

Is there anything I could try?

I have a serial console connected to my router if this can be helpful in running diagnostics.

Thanks!

[stanelie]

self answer:

I was able to load a version of gargoyle AND a kmod-madwifi kernel module that work together.

I had to revert to a kernel version 2.4 build of Gargoyle,
http://www.gargoyle-router.com/download ... uashfs.trx
and use an (almost) matching 2.4 build of madwifi
http://downloads.openwrt.org/kamikaze/8 ... mipsel.ipk.

Using this magical config, I have wifi. However, the client-bridge mode is problematic, it won't connect to a WPA protected network (it will however connect to a WEP one) and the bridge is not working : DHCP pass through won't work and I can't reach the internet from behind the Gargoyle router. However, I can ping things on the internet from the router itself (using a serial console), it really is connected as a client to the main access point.

Any ideas?

[stanelie]

Is there a walkthrough/list of all the required configs/software needed to manually get a working client-bridge gargoyle setup?

What changes are made to the network file when client-bridge is enabled? What software is used to pass arp/dhcp requests to the head router?
...

Any help will be welcome.

[DoesItMatter]

I will post the text versions of a couple types of configs when I'm home.

Any reason you want to use Gargoyle in this situation?

Because you are adding packages yourself, you will have to do your
own configs via command line. Keep in mind, that means if you happen
to make any related changes via the Gargoyle GUI, you can overwrite
and undo any changes you made via command line.

You may be more successful using an older build of OpenWRT
with the LUCI interface and adding on packages to that build.

[stanelie]

Hello.

The reason I would like to see Gargoyle working instead of any other distros is because so far, Gargoyle has been the most reliable and easy to setup of them all.

Have you ever tried to setup a client-bridge on openwrt through Luci???

Gargoyle is straightforward, and it does what is says it does, without making setup overly complicated. Gargoyle is the only distro with which I've been able to use DHCP over a client-bridge config.

So, I would be really happy to see Gargoyle officially support one more router.

I had to manually add madwifi because Gargoyle wouldn't see the Atheros daughter card otherwise. Also, I had to revert to an earlier build of Gargoyle because the newer builds use a 2.6 kernel that doesn't seem to like madwifi too much. I got kernel panics the only few times it would load.

Thanks again for your time.

[DoesItMatter]

The reason I would like to see Gargoyle working instead of any other distros is because so far, Gargoyle has been the most reliable and easy to setup of them all.

Have you ever tried to setup a client-bridge on openwrt through Luci???

Yes! Been there - done that! Quite fun actually!

I flashed OpenWRT 10.03.1 final on my DIR-601

Good way to test pure OpenWRT and driver support for the router.

I think you are going to be stuck compiling your own builds.

Remember Gargoyle is just the GUI for OpenWRT base underneath

So if OpenWRT is abandoning the 2.4 broadcom branch, then it
is pretty unlikely that Gargoyle will have 2.4 broadcom again.

[stanelie]

Remember Gargoyle is just the GUI for OpenWRT base underneath

Hum... I thought there was some software installed to do the arp-nat magic?

I read from the wiki that Gargoyle can be installed on top of openwrt as a package, but the link seems dead... Or maybe I was looking in the wrong place?

And I guess that a recent version of Gargoyle wouldn't work on a Openwrt 2.4 since the OpenWRT config files layout has changed...

[stanelie]

Hello.

Any news about these config files?

Thanks again!

[stanelie]

To simplify troubleshooting, I set up everything with static ip addresses.

Here is what I have so far :

-a computer attached to a wired port can ping the wgt634u
-the wgt634u can ping a computer attached to a wired port

That takes care of the wire side of things.
Next :

- the wgt634u can ping the access point to which it is connected over wifi
- the access point can ping the wgt634u over the wifi link

Wifi link is good.

Now, the problem is that a computer from the wired side can't reach anything on the wireless side, the bridge is not happening.

Here are my relevant(?) config files :

Code: Select all

/etc/config/network

config 'switch' 'eth0'
        option 'vlan0' '0 1 2 3 4 5*'
        option 'vlan1' '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.2.23'
        option 'dns' '192.168.2.1'
        option 'gateway' '192.168.2.1'

Code: Select all

/etc/config/wireless

config 'wifi-device' 'wifi0'
        option 'type' 'atheros'
        option 'channel' '2'

config 'wifi-iface' 'cfg2'
        option 'device' 'wifi0'
        option 'network' 'lan'
        option 'mode' 'sta'
        option 'client_bridge' '1'
        option 'ssid' 'potatoe'
        option 'encryption' 'wep'
        option 'key' 'mysterycode'

Any ideas?

[DoesItMatter]

Here are my config files.
I am running a Wireless bridge. Wireless connect my DIR-601 to
my main AP = Asus RT-N16, and then I use the LAN ports to connect
to a PC/PC's. I have my DIR-601 issuing DHCP addresses as well.

Code: Select all

 /etc/config/wireless

config 'wifi-device' 'radio0'
        option 'type' 'mac80211'
        option 'macaddr' '00:11:22:33:44:55'
        option 'hwmode' '11ng'
        list 'ht_capab' 'SHORT-GI-40'
        list 'ht_capab' 'TX-STBC'
        list 'ht_capab' 'RX-STBC1'
        list 'ht_capab' 'DSSS_CCK-40'
        option 'htmode' 'HT40-'
        option 'channel' '5'

config 'wifi-iface' 'stacfg'
        option 'device' 'radio0'
        option 'mode' 'sta'
        option 'network' 'wan'
        option 'key' 'something-something'
        option 'ssid' 'Asus-RT-N16'
        option 'encryption' 'psk2'

Code: Select all

/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 'type' 'bridge'
        option 'proto' 'static'
        option 'netmask' '255.255.255.0'
        option 'ifname' 'eth0 eth1'
        option 'dns' '128.107.241.185 208.67.220.220'
        option 'ipaddr' '192.168.2.1'

config 'interface' 'wan'
        option 'proto' 'dhcp'
        option 'type' 'bridge'
        option 'dns' '128.107.241.185 208.67.220.220'

config 'switch' 'eth0'
        option 'enable_vlan' '1'

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