paulwye
join:2007-02-17
Toronto, ON
 ·TekSavvy Solutions..
1 edit | reply to TilhasBB
Re: Weird Tomato DHCP Issue
The one thing I've noticed about tomato is that it seems to want to accomodate requests to assign the same IP that the client had previously. For example:
A machine (we'll say a laptop) is on a random network, and is assigned an IP address of 192.168.0.135. Then it comes home and is connected to your router running tomato. I believe that, with DHCP, the laptop will request 0.135 again, and as I say, Tomato seems to be willing to assign that, instead of going sequentially (0.100, 0.101, 0.102, etc.). Now, why it would be agreeing to assign IPs outside the DHCP range you've specified, I have no clue. But that may be a start.
EDIT: The link to the Linksys forum posted above points to a fix for a problem that I had (as it happens, I have two old machines with 2200BG cards). I thought it was specific to the Asus router, but it's actually to do with the Tomato ND firmware. The other thing to note here is that the connection wasn't stable until I updated the wireless drivers on the client computers, and on one of them, it wouldn't talk to the Internet with Windows managing the connection (like yours, it got an IP as I recall, but no communication). I had to use the Intel PRO/Wireless utility to manage the connection, and everything's been fine since... |
|
loginatnine
join:2009-05-24
Montreal, QC
| I think that you're right, the computers who have problem always request the same IP over and over...
May I refer you to my old thread where one very helpful man pointed me to the commands I was referring in my earlier post. It worked at the beginning but the problem came back eventually...And it's not only with intel card I can confirm that my ipod touch and my friend's iphone have the same problem (unless a static dhcp is assigned to their mac address)
»www.linksysinfo.org/forums/showt···st343108 |
|
paulwye
join:2007-02-17
Toronto, ON
·TekSavvy Solutions..
| Hrm. The only two thoughts that immediately come to mind are:
1. Have you double-checked your network config in Tomato? As I recall, the out-of-the-box settings are weird, but that could be because I changed it from 192.168.1.0/24 to 192.168.0.0/24....lease times were set really high, but it won't actually accept anything higher than 10080.
2. The other thing to try would be to put yourself on a different subnet...say...192.168.6.0/24...something not commonly used, like .0 (D-Link) .1 (Linksys) and .2 (Belkin, some Bell stuff) are...that way, even if the devices request an IP that's 1.xxx, the router should say "No way, Jose" and give it an IP on the new subnet...
Cheers,
-Paul |
|
loginatnine
join:2009-05-24
Montreal, QC
| 1- Yea my network settings are fine in tomato, dhcp range is from 192.168.1.100 to 192.168.1.149. Does the lease times could have an effect?
2- Just to be sure I'm understanding what you say, you suggest I change the router gateway address to something less familiar like 192.168.2.1 so the dhcp range could be something like 192.168.2.100 to 192.168.2.149? If that's what you're trying to say, that's actually not a bad idea at all, it's pretty late around here and I manage like 6 laptops on my network so I don't want to try it right now but it's definitely worth a shot...
But damn, why the hell does tomato does that anyway??? Is that a bug I should report maybe?
Thanks for your help Paul, much appreciated! |
|
paulwye
join:2007-02-17
Toronto, ON
·TekSavvy Solutions..
| It's hard to say...I don't actually mind, because I sort of like static IPs, and this is almost as good, without having to assign a DHCP reservation to the MAC address. As it happens, the places to which our laptops travel are all on .0 subnets, so I can't really tell you if my router screws up this way or not...I'll try to experiment this week if I can. |
|
TilhasBB
Formally Goden99
Premium
join:2000-08-05
canada
| reply to loginatnine
Thanks for the input guys.
I just applied the fix on the linksys site and keep you posted if it helps.
The DHCP range isn't the program both laptops and iphone would magically want to go between 192.168.1.60 to 192.168.1.90
So I changed the range to 192.168.1.50 to 192.168.1.100
Even when the laptops connected with an ip in that range there is no internet....
I just changed the Router IP to 192.168.2.1 and range to 192.168.2.51 - 192.168.2.100
and lease time to 800minnutes.
Nothing worked. rebooted both laptops, tried assigning ip in that range then set to automatic but reverted back to the 192.168.1.x range. |
|
jfmezei
Premium
join:2007-01-03
Beaconsfield, QC
·ELECTRONICBOX
| If a client thinks its DHCP lease is still valid, it will request a "renew".
If a DHCP server accepts to renew an IPO lease that is outside of the range the DHCP server has been given, it should be considered a bug.
It may agree to renew it if it is in the same subnet.
One thing to verify: does your client with a "foreign" lease get new coordinates for the default route (aka: gateway) as well as dns servers, or does it keep those from its old DHCP lease obtained from another location ? This might explain its inability to reach the internet if it doesn't know the Ip address of the local router. |
|
TilhasBB
Formally Goden99
Premium
join:2000-08-05
canada | I will check next time i get booted off the net.
I had to go into the Tomato Basic Network Setting and set DHCP's range to 192.168.1.51 - 192.168.1.100 |
|
Davesnothere
@teksavvy.com
| reply to jfmezei
said by jfmezei  :One thing to verify: does your client with a "foreign" lease get new coordinates for the default route (aka: gateway) as well as dns servers, or does it keep those from its old DHCP lease obtained from another location ? This might explain its inability to reach the internet if it doesn't know the Ip address of the local router. You may be onto something...
I have Zero experience with Tomato firmware, but in terms of generalities, the described symptoms smack of a DNS problem, IMHO.
Personally, I DO prefer to use Static IPs within my local network (makes port forwarding easier to setup, and most times when a router needs restarting, I have found that it was due to a DHCP problem, and using Static Local IPs usually also avoids that issue), and when you do this on PCs running XP, they then insist that you manually enter your DNS settings, which can be those which your ISP told you to use, OR, you can choose to enter the same IP address as your Gateway (local router).
While you're at it, the proper Gateway IP itself needs to be entered into each computer's network settings no matter whether or not you use Static Local IPs like me.
When I switched from Bell to TSI last year (insert cheer here), I originally forgot that I had previously manually entered Bell's DNS's into my XP PCs AND into my router's main setup screen, and sometime along the way, Bell had chosen to lock down their DNS servers, so that if I was not logged into THEIR service anymore (and I had just made my change), that the Bell DNS servers would ignore me most of the time, giving me no web pages but OK local net. - Changing them to TSI's DNS's solved that. (my Win98SE PC was set up as DHCP and was therefore not bothered by any of this)
One way to test whether you have a DNS problem is to enter the actual IP address of a website into your browser instead of the web address, if you know or can find out any beforehand, and if you only can access the web site THAT way, then DNS is your category of problem.
Another thing to try on any problem computer is to run WINIPCFG (on XP at least), and tell it to release all the settings it has gathered thru the DHCP of your router (as often even a computer restart will not clear these).
Hope there is some help in all of this...
Cheers ! |
|
