DHCP with Access Point operation mode

[the Henglaender]

Hi,

Could anyone tell how to what I need to do to set up dhcp with the asus wl500gx in access point mode? Please assume that I am stupid.
I am using the wl500gx as an ethernet bridge to a fritz fon wlan. The fritz box has an dhcp server, but I don't seem to be able to get whatever it assigns back to the clients. So I intend to switch it off and use the the dhcp server in the asus box.

BTW I really don't understand why I need to have a WLAN for the DHCP server to be available.

[Antiloop]

just use Homegateway mode, set gateway address right and do not use WAN port

[the Henglaender]

Hi,

Unfortunately this doesn't work (at least for me): doing as you suggest leads to my other thread: 'Bug with Station/Ethernet Bridge?'.

[Antiloop]

Hi,

Unfortunately this doesn't work (at least for me): doing as you suggest leads to my other thread: 'Bug with Station/Ethernet Bridge?'.
I have no idea what you mean anymore

please explain better, make a visio drawing to make clear your configuation

[the Henglaender]

Hi

Attached is a quick diagram.
What I would like is to active DHCP on the wl500gx. At the moment it is in AP mode. If I set the operation mode to Gateway then it looks like the wl500gx dies/hangs: I cannot find it on the network.

[Antiloop]

okay

please note your network settings ip adresses/ subnets bla bla

and how did you setup the wl500gx to connect to the fritzbox ?

[the Henglaender]

I am doing this from memory (but i have done this so often as the only way to get back to the asus box after switching to home gateway mode is to reset it).

The firtzbox allows you to assign three separate networks and a separate dhcp server to each
lan set to 192.168.178.x and mask 255.255.255.0 dhcp enabled
usb set to 192.168.179.x and mask 255.255.255.0 dhcp enabled (nothing connected)
wireless set to 192.168.182.x and mask 255.255.255.0 dhcp disabled.
The wireless interface on the fritzbox is 192.168.182.1, lan interface 192.168.178.1, wan is get address from isp.

Asus WL-500gx
Access point mode
IP address to set to 192.168.182.2 mask 255.255.255.0 gateway 192.168.182.1
Wireless is set to Hybrid (AP+WDS)
Both fritzbox and wl500gx are on the same channel and have the same SSID
The mac address of the the fritzbox is in both the accept and the attach to lists
Security is WEP128 (WPA-PSK doesn't seem to work, although I haven't tried this with 5a)
Both fritzbox and wl500gx are set to 11g
Advanced Wireless: extended mode is ethernet bridge
Wireless status says connected to (and lists the fritz mac address)

When I switch to home gateway mode
I set the dhcp server to enabled, address range 192.168.182.20-192.168.182.254 dns 192.168.182.1 and 192.168.182.2 gateway 192.168.182.1 and leave the WLAN in its default values: get ip from ISP.

[the Henglaender]

I have played with this a bit more and have found a method to connect to the wl500gx once it is nolonger visible on the lan network: plug the cable into the wan port!

I think I read somewhere something about a boot issue with the wan port being bridged to the lan ports: I'll go and try that (my serial nummber starts with 52)

[the Henglaender]

No luck, the lan ports are still dead.

I had a look at the port configuration with ifconfig: as far as I can make out
the WAN settings in the web pages apply to the WLAN interface == eth1.
A bridge br0 is configured which consists of the normal lan ports == eth0.1 and the now redundunt WAN port == eth0. What may be interesting is that the RX packet count on eth0.1 == 0 (although something is connected to a LAN port), TX is != 0.

Has anyone got an idea what I could try or perhaps can reproduce this?

[Antiloop]

why are you using ' Ethernet Bridge' at Extended Mode while you are using HYBRID(WDS) ?

it should be 'AP or WDS' if you are using Hybrid

[the Henglaender]

Well, if you can remember that drawing I did a couple of days ago: I want other clients to attach (=AP), I have to set it at least WDS (that equals hybrid) to enter the mac address of the AP the wl500gx should attach to and to get it to attach I need at least 'station' in the extended mode

[brubber]

Asus WL-500gx
Access point mode
IP address to set to 192.168.182.2 mask 255.255.255.0 gateway 192.168.182.1 You may try setting the WL-500gx gateway and DNS server to 192.168.182.2

[the Henglaender]

You may try setting the WL-500gx gateway and DNS server to 192.168.182.2
Unfortunately that doesn't work

[the Henglaender]

In the mean time I have set wireless to AP, extended mode to 'Station', the WAN to automatic ip and reenabled the dhcp server on the fritzbox. The lan ip is set to 192.168.1.1 and dhcp enabled. The wl500gx still connects to the fritzbox and the only port that works on the wl500gx is the wan port. Below is the output of ifconfig:


br0 Link encap:Ethernet HWaddr 00:11:xx:xx:xx:D4
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: xxxx::x11:xxxx:xxxx:xxd4/10 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:444 errors:0 dropped:0 overruns:0 frame:0
TX packets:736 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:58494 (57.1 KiB) TX bytes:457144 (446.4 KiB)

eth0 Link encap:Ethernet HWaddr 00:11:xx:xx:xx:D4
inet6 addr: xxxx::x11:xxxx:xxxx:xxd4/10 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:444 errors:0 dropped:0 overruns:0 frame:0
TX packets:908 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:66486 (64.9 KiB) TX bytes:500300 (488.5 KiB)
Interrupt:4 Base address:0x1000

eth0.1 Link encap:Ethernet HWaddr 00:11:xx:xx:xx:D4
inet6 addr: xxxx::x11:xxxx:xxxx:xxd4/10 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:137 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:41018 (40.0 KiB)

eth1 Link encap:Ethernet HWaddr 00:11:xx:xx:xx:D4
inet addr:192.168.182.21 Bcast:192.168.182.255 Mask:255.255.255.0
inet6 addr: xxxx::x11:xxxx:xxxx:xxd4/10 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18 errors:0 dropped:0 overruns:0 frame:250
TX packets:15 errors:1 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:2311 (2.2 KiB) TX bytes:2241 (2.1 KiB)
Interrupt:2 Base address:0x4000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MULTICAST MTU:16436 Metric:1
RX packets:50 errors:0 dropped:0 overruns:0 frame:0
TX packets:50 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5540 (5.4 KiB) TX bytes:5540 (5.4 KiB)

Interesting is that eth0.1 RX==0 :rolleyes:
Now if I do
$brctl delif br0 eth0
then not surprisingly the wan port stops working, but now I can connect via the lan ports and low and behold ifconfig for the eth0.1 is now


eth0.1 Link encap:Ethernet HWaddr 00:11:xx:xx:xx:D4
inet6 addr: xxxx::x11:xxxx:xxxx:xxd4/10 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1005 errors:0 dropped:0 overruns:0 frame:0
TX packets:2856 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:360528 (352.0 KiB) TX bytes:780947 (762.6 KiB)
so i think this is a bug

[Antiloop]

well there is something wrong

i have to test further to collect more details, so please stay tuned :)

[the Henglaender]

i have to test further to collect more details, so please stay tuned :)
Anything new?

[Antiloop]

no, I'm short in time

and don't, the other message has been trashed, continue inhere do not duplicate the same problem into multiple threads

[the Henglaender]

... the other message has been trashed, continue in here do not duplicate the same problem into multiple threads
Well, would you resurrect it again please. In this thread we have the wl500gx in home gateway mode (at the moment) and the lan ports not working unless the wan port is removed from br0. In the one you trashed the wl500gx is in access point mode, wireless is acting as a bridge (no routing as above), the lan ports are working but the DHCP MESSAGES from the fritzbox are not being received by the clients attached to the wl500gx. This may be a problem with the wl500gx or the fritzbox not routing the dhcp messages correctly.