[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 13/07/10 08:04, Gordon Henderson wrote:
there is the client bridge mode where the attached PC doesn't "see" the linksys router at all and the other wifi client mode (forget what it's called - just "client" mode maybe) where the linksys is visible to the attached PC. Both modes pick up the wifi signal from the main router. In the first mode the IP address of the linksys is completely ignored and the only reason for setting one at all is in order to be able to access the gui. In the second mode the linksys is part of the main LAN, hence a 10.0.0.n address, on the "side" picking up the signal, but needs to have a different address range on other side being output to ethernet cable attached devices. In this mode it does use its own DHCP capabilities, in the direct bridge mode the main router is used for assigning addresses.On Mon, 12 Jul 2010, Simon Robert wrote:I'm not using the o2 router at all now. I'm using the previous router with just the o2 login and paswword changed from the previous setup. So nothing has changed at all. The potential prob with the o2 router runing two sets of IP addresses doesn't applyThe tomato software has various tools, one of which is a scan of local wifi, it sees the lan from the main router no problem, so signal visiability is OK. When using the tomato software the IP address and DHCP/DNS range MUST be different from that of the main router. Hence the main router at 10.0.0.138 giving out addresses from 10.0.0.1 to 10.0.0.137 and the tomato/linksys router at 192.168.1.1 giving out addresses from 192.168.1.2 to ...50. Both routers use the same SSID and WPA1+2 password. When it was working I could see the linksys on the LAN with the address 10.0.0.4 and putting out the address 192.168.1.23 to the attached PC. I can still access the linksys from the wired PC.I can't quite get my head round that. How is the Linksys connected to your main ADSL (+Wi-Fi) router?I was under the impression you were running it in client-bridge mode, but in that mode it should not be on a separate subnet and should not be running DHCP.In client bridge mode, it acts like a client connected to the main access point and should not act as an access point itself - it then bridges the network via wi-fi through it's own Ethernet switch, extending the LAN, and its services (e.g. DHCP) through itself.If you're using it as a router then you have double NAT, which is usable, but something I'd avoid if at all possible, but I'm not sure how it's acting as a router - the Wi-Fi interface acting as it's "wan" interface? Maybe tomato can do that, but I'd really try not to.Gordon
In this case in client mode I can scan for local wifi signals from the linksys, but no longer attach to them. In direct bridge mode absolutely nothing happens as it is not attaching, not picking up an IP address etc. Direct bridge should be pretty much automatic, just a matter selecting the mode and giving the device an address so the gui remains accessable.
Simon -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq