[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 09/07/10 12:05, Gordon Henderson 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 applyOn Thu, 8 Jul 2010, Simon Robert wrote:HiI am running a linksys router as a wireless client. It has been flashed with a piece of software called tomato which means it can receive a wifi signal and then output it via cable to my PC. This is the method that gives me the best connection with the wifi box downstairs.All has been working well for yonks until last Monday when we switched ISP. I set the o2 box to be setup as close to the previous setup as I could. Switched WPA passwords and while I couldn't seem to switch the IP address from 192.168.1.254 and the DNS range from 192.168.1..... I was able to add 10.0.0.138 as an alternate address and 10.0.0.1 - 10.0.0.137 as an alternate DNS range. This seemed to work fine for everything on the LAN including the linksys.However the linksys appeared to suddenly stop working. No longer picking up a lease from the first router. Thinking this was down to the IP issues I replaced the o2 router with the previous one, substituting the log in details for the new ones. It works fine, but still no joy with the linksys router. The linksys is just not picking anything up from the main router, for example it used to have a LAN ID of 10.0.0.4, while having an address of 193.168.1.1 and assiging the PC something in the 193.168.1.x range.I'm assuming you've typo'd 193 for 192 here - it's just that you've done it twice.. (And you have DNS above which I presume is really supposed to be DHCP)Are you sure it's nothing as simple as a harware failure of the Linksys box?If you're sure it's OK, I'd suggest starting from scratch. Factory reset the O2 router and get it working and online. Don't bother with alternative IP address ranges in it at all, just leave it to 192.168.1.0/24. Make sure you can access it wired and wirelessly. Also make sure the Wi-Fi channel is in the range 1-11 to start with.Unless you really need it, my thoughts are that running 2 IP address ranges will serve only to confuse you.Then factory reset the tomato box, connect a PC/Laptop up to it and go through the motions of giving it a fixed IP address (I suggest 192.168.1.253 if the O2 box is .254), turning off it's own DHCP, etc. and put it back into client-bridge mode.Then see if you can get an IP address on a wired PC/Laptop (wired to the Linksys), then wireless.The DHCP server does need to be running something that responds to version 3 of the protocol to give IP addresses to devices behind a Wi-Fi bridge, but that's been out for at least 8 years now, so I'd hope it was OK there. (It's to do with multiple IP addresses behind the same MAC address on the Wi-Fi bridge unit - something we run up against in the days of the Buckfastleigh project, but ISC's DHCP hat just been updated to cover that - fortunately!) However I suspect you're OK there.Good luck! Gordon
The 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.
Nothing should have changed as far as the LAN is concerned, the only difference is the identity of the ISP. I have re-set the linksys a couple of times and upgraded to the latest version of tomatoI. I'll have a go with no encryption and see if it makes a difference, but I'm thinking it may be a hardware failiure. A shame as it worked really well and I'm now back to using powerline (homeplug) plugs which for some reason are less than optimal in this house.
The version of linksys router tomato works with is difficult to get hold of now and although the software is said to work with other routers I'd like to stick with the officially supported ones. Oh well...
Thanks for the suggestions Simon -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq