Hello,

I try to set up my ASUS WL500gD with an actual SVN: KAMIKAZE (bleeding edge, r16682)
I want to use th ASUS as a brige, connectet to an other AP in my WLAN.

First I compiled without firewall, later with firewall. I'm not completly new to this, I used bridging
before on a Linuxmachine for VPN.

My network settings is:

root@OpenWrt:~# cat /etc/config/network

config 'switch' 'eth0'
        option 'vlan0' '0 1 2 3 4 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 'dns' '192.168.100.75'
        option 'gateway' '192.168.100.75'
        option 'ipaddr' '192.168.100.11'

I take all 5 LanPorts together, I need no WAN Port.
Pinging the ASUS from a Cableconnection is OK, SSH works fine too!

I use WLAN with a WPA2 connection:

root@OpenWrt:~# cat /etc/config/wireless

config 'wifi-device' 'wlan0'
        option 'type' 'mac80211'
        option 'disabled' '0'

config 'wifi-iface'
        option 'device' 'wlan0'
        option 'network' 'lan'
        option 'ssid' '0123456789'
        option 'encryption' 'psk2'
        option 'key' 'abcdefghijk'
        option 'mode' 'sta'

Connection is OK, I can ping and SSH the ASUS over WLAN, cable disconnected.

Interfaces are up and connected:

root@OpenWrt:~# ifconfig
br-lan    Link encap:Ethernet  HWaddr 00:11:D8:D1:E1:3A
          inet addr:192.168.100.11  Bcast:192.168.100.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:473 errors:0 dropped:0 overruns:0 frame:0
          TX packets:396 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:40654 (39.7 KiB)  TX bytes:46754 (45.6 KiB)

eth0      Link encap:Ethernet  HWaddr 00:11:D8:D1:E1:3A
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:796 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:101466 (99.0 KiB)
          Interrupt:4

eth0.0    Link encap:Ethernet  HWaddr 00:11:D8:D1:E1:3A
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:796 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:98040 (95.7 KiB)

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:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:192 (192.0 B)  TX bytes:192 (192.0 B)

wlan0     Link encap:Ethernet  HWaddr 00:11:D8:D1:E1:3A
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2972 errors:0 dropped:0 overruns:0 frame:0
          TX packets:394 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:404818 (395.3 KiB)  TX bytes:54856 (53.5 KiB)

Bridge seems to be OK:

root@OpenWrt:~# brctl show
bridge name     bridge id               STP enabled     interfaces
br-lan          8000.0011d8d1e13a       no              eth0.0
                                                        wlan0

Now when I try to use my ASUS as Brigde (my PC connected to ASUS and
the ASUS connected via WLAN to an AP) the connection ends in the ASUS.
Pinging Google.com etc over Openwrt's console works fine but connections
through the ASUS are not possible!

I tried different builds, downloaded and own compiled firmwares with 2.6 Kernel.
I Could not get it to work.

When I use DD-WRT on the router bridging works, but thats not what I want!
Hardware is OK!

I think bridging is broken in the kernel?!
Someone here who could help me get it working?

Kind regards and sorry for my poor english

Lonzo

I'm guessing the problem is in the wireless, rather than the bridging, though it is possible that your platform behaves differently than the WRT54G units I use. I'd check that the Ethernet ports "work like a switch" -- in which case the "bridge" is likely set up properly and working.

As for the wireless, you'll probably get "you need to use WDS mode" or "you need to use routed mode" responses, but I have been successful in setting up a WRT54G as a non-routed station that allows a wired Canon printer to access the network, and vice versa, even for discovery broadcasts. Just posted configuration http://forum.openwrt.org/viewtopic.php?id=20932 -- which looks a lot like yours. I generally have to restart the STA router to get it to associate with the AP router.

Hello,

and thank you for your reply.

I tested yesterday your settings, but with the same results.
I dont't think wireless is the problem, pinging and SSH connect
is OK over wireless.

I see you have "broadcom" in your wireless settings, you
are running a 2.4 Kernel?

I'm using a 2.6 Kernel. Searching around the web I found
other posts people having problems with Kernel 2.6 and
bridging.

Somebody here who get it to work with newer Kernel?

Thank you for help!

lonzo

Yes, I'm running 2.4. From what I understand, support for the Broadcomm wireless is not present in the 8.09.1 version for the 2.6 kernel, only the 2.4 kernel. I don't know the status of trunk for wireless support under the 2.6 kernels.

In wireless bridging is generally broken with client-mode.

Thank you,

thats disappointing, is bridging in 2.4 Kerne OK??

greetz
Lonzo

same problem with a wl 500gp and 2.6. kernel.
can ping with cable-connection to wlan/bridge but not beyond it.
wlanbridge itself can ping beyond.

But i am using that crapy broadcom card, would it do any good to change it to an atheros? Or is it realy that brocken that only 2.4. kernel offers this feature?

Hello,

Bridge works on Kernel 2.4, but I'm not lucky with this workaround.

Is tehere a Ticket existing?