OpenWrt Forum Archive

Topic: Client mode vanishing act

The content of this topic has been archived on 1 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

I've enabled client mode on WRT54G V3 running 8.09.1 connecting to a WL-520GU and I was impressed at how simple it was to get it working just by placing the appropriate settings in in the LuCI interface in Essentials -> Network -> Wifi.

I'd like to make the client router a bit more visible, though. If I leave the client set up in Essentials -> Network -> Local Network with the default address of 192.168.1.1 it just kind of disappears. I can actually get at the client by configuring the client address to be 192.168.2.2 in Essentials -> Network -> Local Network and adding an eth0 alias in the 192.168.2.0 subnet (ifconfig eth0:1 192.168.2.5 netmask 255.255.255.0). Then I can at least get at the client router via the web interface and SSH.

However, I'm thinking client mode is most likely implemented at the link layer since the client seems to knows absolutely nothing about the router it's connecting to. I just can't figure out how to get the client to access the WL-520GU IP address. Ultimately I'd like the client to have access to the Internet for maintenance purposes. Does anyone know if this is possible?

Thanks,
Pete

Doh. All I did to get this to work was to configure the client's IP address (I used Essentials -> Network -> Local Network) to be in the same subnet as the router (I chose 192.168.1.2) and to configure the gateway and DNS server to be the IP of the router (192.168.1.1). I was pretty sure I'd tried that and failed, which is why I was farting around with the client IP in a different subnet, but it works now. Dunno. Hopefully this will help someone else fiddling with the same thing.

Thanks,
Pete

Ensuring that the IP address for the LAN in the bridged client is set to something different than the IP address for the LAN in the access point router but still within the same subnet might be a worthwhile addition to the http://wiki.openwrt.org/doc/recipes/bridgedclient directions, especially since default settings in a lot of firmware installations set the default LAN IP to 192.168.1.1.

(Last edited by valuequest on 10 Feb 2011, 05:21)

The discussion might have continued from here.