Weird Tomato DHCP Issue in TekSavvy

Weird Tomato DHCP Issue in TekSavvy http://www.dslreports.com/forum/r22437565 en Fri, 04 Dec 2009 21:21:22 EDT Fri, 04 Dec 2009 21:21:22 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22458537 TilhasBB : .....
I put the 2wire in the LAN port and the ST on the WAN port.
2wire 192.168.2.1 ON LAN 4
ST 192.168.1.254 or 10.0.0.138 ON WAN
Router 192.168.1.1

Working now :)
Crossing my fingers]]> http://www.dslreports.com/forum/remark,22458537 Thu, 28 May 2009 14:16:35 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22458271 TilhasBB : the 2wire works on LAN or WAN port. Tomato is smart enough to find it and dial into it. the 2wire is on 192.168.2.1.]]> http://www.dslreports.com/forum/remark,22458271 Thu, 28 May 2009 13:31:43 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22458211 anon :

said by TilhasBB

:

Good news is, my internet is always working now but at half speed.

That's encouraging, and would be what I would expect, and is prob'ly coming thru the WAN port modem rather than the other modem.

To verify that, I suggest unplugging the other modem for a moment.]]> http://www.dslreports.com/forum/remark,22458211 Thu, 28 May 2009 13:18:49 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22458184 anon :

said by TilhasBB

:

- In case there is any confusion....

My Setup

I have TWO modems. Speedtouch 516 and 2Wire 2701
I have WRT54GL Running Tomato/MLPPP Version 1.22-mp3alpha5er1
I am running MLPPP with two connections.

Good news is, my internet is always working now but at half speed.

Two Modems ?

That changes everything !

If you had a Router with 2 WAN ports (load balancing class), I would know what to do.

Does the 2-Wire modem have a hidden router & dhcp server in it too ?

If yes, that could still cause a problem.]]> http://www.dslreports.com/forum/remark,22458184 Thu, 28 May 2009 13:13:40 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22458130 anon :

said by nigrunze

:

Try starting from scratch. Since you're running Tomato, you can make this easier. On Tomato's Basic Network page, set your modem's IP as 10.0.0.138 (for whatever reason, the speedtouch uses both 192.168.1.254 and 10.0.0.138). Log into the Speedtouch web interface and run the easy setup using the instructions from TekSavvy's FAQ on the forums. Set your modem as bridged and DHCP to be off.

Your modem SHOULD work properly now.

A couple of side questions please :

Do I understand correctly, is this Bridge Mode and disabling DHCP method simply a fancy way to tell the ST-516 Combo Modem/Router to completely disable the Router part, so that they behave JUST as a Modem ?

And are you saying that you can tell Tomato firmware what IP address to EXPECT a modem connected to their WAN port to have ?

Thanks]]> http://www.dslreports.com/forum/remark,22458130 Thu, 28 May 2009 13:06:33 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22457755 derekm :

said by TilhasBB

:

- The modem was set on Bridge BUT DHCP was on... I never realized. So I went back and disabled it, since then Tomato is only able to connect using the modem on WAN side of router. So I am only getting 1 / 2 connection.

- Good news is, my internet is always working now but at half speed.

I've never used Tomato, but my guess is that you'll need to move whatever port you have the 2nd modem plugged in to, to the WAN VLAN.

Maybe someone else running Tomato can tell you how they have it physically/virtually connected.]]> http://www.dslreports.com/forum/remark,22457755 Thu, 28 May 2009 12:10:28 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22457697 TilhasBB : - Incase there is any confusion.
My Setup
I have TWO modems. Speedtouch 516 and 2Wire 2701
I have WRT54GL Running Tomato/MLPPP Version 1.22-mp3alpha5er1
I am running MLPPP with two connections.

- I powercycled modem and router.
turned on router then turned on modem.

- I have 2wire on WAN and Speedtouch on Port4.

- 10.0.0.138 and 192.168.1.254 nothing happens

- Only Computers in device list on router page.

- The modem was set on Bridge BUT DHCP was on... I never realized. So I went back and disabled it, since then Tomato is only able to connect using the modem on WAN side of router. So I am only getting 1 / 2 connection.

- Good news is, my internet is always working now but at half speed.

nigrunze> When you set the Modem's IP in Tomato's network page thats only for the modem on the WAN side.
But i set it to 10.0.0.138 and it didn't help.]]> http://www.dslreports.com/forum/remark,22457697 Thu, 28 May 2009 12:00:37 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22456484 nigrunze :

said by Davesnothere :

Damn those Combo Modem Routers ! - They cause more problems than they solve ! (and all to save a few bucks)

And if I had read your post before responding to the one just above it, yes, I have heard of this 'Bridge' mode setting in those beasts, and it sounds like with that plan, you may have it figured out.

And we agree about re-entering the login info.

Do I understand correctly, is that simply a fancy way to tell the unit to completely disable the Router part, in these recent model ST Combo modem/routers ?

Try starting from scratch. Since you're running Tomato, you can make this easier. On Tomato's Basic Network page, set your modem's IP as 10.0.0.138 (for whatever reason, the speedtouch uses both 192.168.1.254 and 10.0.0.138). Log into the Speedtouch web interface and run the easy setup using the instructions from TekSavvy's FAQ on the forums. Set your modem as bridged and DHCP to be off.

Your modem SHOULD work properly now.]]> http://www.dslreports.com/forum/remark,22456484 Thu, 28 May 2009 07:35:58 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22456245 anon :

said by derekm_anon :

said by TilhasBB

:

I removed the DHCP on the Speedtouch modem but now Tomato isn't able to dial in with it.
and I am unable to access the modem... any ideas?

Damn those Combo Modem Routers ! - They cause more problems than they solve ! (and all to save a few bucks)

And if I had read your post before responding to the one just above it, yes, I have heard of this 'Bridge' mode setting in those beasts, and it sounds like with that plan, you may have it figured out.

And we agree about re-entering the login info.

Do I understand correctly, is that simply a fancy way to tell the unit to completely disable the Router part, in these recent model ST Combo modem/routers ?]]> http://www.dslreports.com/forum/remark,22456245 Thu, 28 May 2009 03:17:19 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22456234 anon :

said by paulwye

:

....having two DHCP servers on the same subnet is almost universally going to be a bad idea....

Agreed, and I was alluding to that point in my last post.

said by paulwye

:

Second, it's pretty obvious from your posted network config that the reason you can't get anywhere with the initially assigned IP is that the gateway is set to 192.168.1.254--i.e., that address, DNS and gateway were assigned by the second modem

I do not believe this user has two modems going, at least never said so.

But I do believe they have a Tomato router hooked in between a Combo Modem/Router and the computer(s), and in this situation, the second or phantom DHCP server would be part of rhat Combo unit.

As I perceive it, now that they have turned off the 2nd DHCP server, it has created a NEW problem, because perhaps they do not have their PPPOE login set in the Tomato router, or Gateway or DNS number could still be wrong.

So, can you still currently log into the Tomato router, after you turned off the DHCP of the Modem router ?

If you can, then review whether the suspected settings of Gateway, etc are now showing the previously good _._._.1 setting, or the earlier _._._.254 bad setting, or something else.

And (humour me on this) please enter again from scratch your TSI login settings and confirm that the Tomato router says that you have a successful login.

Any better now ?]]> http://www.dslreports.com/forum/remark,22456234 Thu, 28 May 2009 03:06:29 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22455969 anon :

said by TilhasBB

:

I removed the DHCP on the Speedtouch modem but now Tomato isn't able to dial in with it.
and I am unable to access the modem... any ideas?

It looks like you were double nat'd. (i.e. the speedtouch was nat'ing your tomato, which was nat'ing your network - sometimes).

You need to change the speedtouch to bridge mode, and connect it to the WAN port of the linksys.

You then need to enter your PPPoE details into the linksys.

From there, Everything Should Just Work. ]]> http://www.dslreports.com/forum/remark,22455969 Thu, 28 May 2009 00:50:35 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22455877 paulwye : Okay, that's just weird. I'm fairly sure that the router doesn't need DHCP to be active on the modem...actually, I don't see how that could EVER work, because you're almost certainly going to have DHCP running on the router, and having two DHCP servers on the same subnet is almost universally going to be a bad idea...did you try power cycling both the second modem and the router?

Second, it's pretty obvious from your posted network config that the reason you can't get anywhere with the initially assigned IP is that the gateway is set to 192.168.1.254--i.e., that address, DNS and gateway were assigned by the second modem, but of course since the modem isn't the device establishing the connection, there's nowhere for the internet traffic to go. So....just to be sure, you've got one modem on the WAN port and the other on one of the four remaining ports, right? What happens when you try to access 10.0.0.138 (the other IP to which the modem should respond)? ]]> http://www.dslreports.com/forum/remark,22455877 Thu, 28 May 2009 00:21:03 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22455478 TilhasBB : GOOD CALL!!!!

I completely forgot about the Speedtouch.

I removed the DHCP on the Speedtouch modem but now Tomato isn't able to dial in with it.
and I am unable to access the modem... any ideas?]]> http://www.dslreports.com/forum/remark,22455478 Wed, 27 May 2009 22:48:58 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22454560 anon :

said by nigrunze

said by derekm

said by TilhasBB

:

What i see that is wrong is
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254

Why is that???

Good Point !

I did not think of that as I am from the 'vacuum tube' era of DSL modems, you know, back in the day when if you ASK for a modem, you GET just a modem. - I have 3 of the original Alcatel Speed Touch (spares in case one fails, but like that pink bunny...), and they have never given me an ounce of trouble (though other parts of my network sometimes have).

IMNSHO, those combo units are an extreme nuisance, and Bell often but inconsistently issues them to customers without explaining what they are sending in the dreaded 'Bell Kit'.

If you are correct about your analysis, then shouldn't the Tomato/Linksys Router have been set to a different subnet in the first place (or still could be), in which case, the problem might not happen because the two routers would be properly 'nested' ? (and the Tomato/Linksys itself would then become a DHCP client of the Modem-Router) ?

BTW, I use _._._.254 as a 'Black Hole' to which to forward TCP port #113 on my router, so that GRC.com's 'Shields Up' test cannot notice it.]]> http://www.dslreports.com/forum/remark,22454560 Wed, 27 May 2009 20:18:21 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22453680 nigrunze :

said by derekm

said by TilhasBB

:

What i see that is wrong is
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254

Why is that???

192.168.1.254 is the IP address for a speedtouch modem. The ST modems have a built-in DHCP server, so you'll need to disable it.

EDIT: Assuming you're using an ST516, go to this link and uncheck "DHCP server". You may also need to uncheck "auto IP".]]> http://www.dslreports.com/forum/remark,22453680 Wed, 27 May 2009 17:51:12 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22453627 derekm :

said by TilhasBB

:

What i see that is wrong is
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254

Why is that???

I'm coming into this thread a bit late, so forgive me if this has been covered, but *do* you have a second DHCP server somewhere, like another wireless access point or something on your network?

When you are assigned a working IP, can you ping 192.168.1.254? (If so, what kind of device is it?)]]> http://www.dslreports.com/forum/remark,22453627 Wed, 27 May 2009 17:44:23 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22453295 TilhasBB : Davesnothere> Thanks for the input.
So your saying DISABLE DHCP and get every computer to get static IP?
I'd rather not do that, when people come over I just want to give them my wireless password.

These are the only two pages with network settings.

]]> http://www.dslreports.com/forum/remark,22453295 Wed, 27 May 2009 16:50:29 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22452295 anon :

said by TilhasBB

:

What i see that is wrong is :
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254

Why is that???

As I said earlier, I do not have any Tomato-specific experience, but let me ask...

Are the problem numbers all a part of 'status' screens, and does Tomato allow you to specify them somewhere on some other screen (as the original Linksys firmware did) ?

If yes to that, then what do you currently have entered in there ?

If blank, then enter the numbers which worked, to force it (hopefully) to use those numbers, and BTW, 192.168.1.1 coincidentally is the factory default IP for a WRT54 router with Linksys firmware.

Alternately, is there any reason why you should not just keep the static local IP (since it works) ?

(Besides, of course not letting the problem win.)

As mentioned earlier, I have always found static local IP's to be more stable, in a lot of ways, and especially when running a PC WIRELESS on a local net.

Hope that is of help...]]> http://www.dslreports.com/forum/remark,22452295 Wed, 27 May 2009 14:11:01 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22451492 TilhasBB : It happened again...

Boot up NO Internet

Windows IP Configuration

Host Name . . . . . . . . . . . . : ACER-One
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Peer-Peer
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : lan

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Atheros AR5007EG Wireless Network Ad
apter
Physical Address. . . . . . . . . : 00-22-69-84-5A-XX
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.68
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
Lease Obtained. . . . . . . . . . : Wednesday, May 27, 2009 11:55:40 AM
Lease Expires . . . . . . . . . . : Thursday, May 28, 2009 11:55:40 AM

Put Random Static IP in range. it gets static ip, then put it back to automatic. VOILA internet works...

Windows IP Configuration

Host Name . . . . . . . . . . . . : ACER-One
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Peer-Peer
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Atheros AR5007EG Wireless Network Ad
apter
Physical Address. . . . . . . . . : 00-22-69-84-5A-XX
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.60
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Wednesday, May 27, 2009 11:58:22 AM
Lease Expires . . . . . . . . . . : Thursday, May 28, 2009 1:18:22 AM

What i see that is wrong is
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254

Why is that??? ]]> http://www.dslreports.com/forum/remark,22451492 Wed, 27 May 2009 12:03:33 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22443930 anon :

said by TilhasBB

:

I am having a DHCP problem thats driving me crazy.
I seem to be missing something. If you guys can take a look i'd be grateful.

When a computer LAN or WIFI tries to log into the internet, It would not work. It would be assigned an IP and can access the router and local network but NOT the internet.

If you look at the Device list, Under ethe1, its assigned an IP but the Name is blank and Lease is Blank.

Rebooting the machine or router several times does not help. The machine must manually be assigned a different ip, then set to automatic to get internet access.

Problem still happens after that's been done a few days later and the same procedure must be repeated.

Just one More Thing (Columbo humour) ;)

I have seen some routers (D-Link DI-524, for one) which can do something in between Static IP and DHCP.

Funny enough, D-Link calls this 'Static DHCP', and it's in the DHCP screen.

What happens is that one one line of the form, you specify to the router the MAC address if the network interface of a particular computer you will be using, and on another line, you specify what valid local IP address to assign to that particular MAC, so that any time the router sees that PC, it gives it that IP.

Maybe the Tomato system does something like that, but only when IT feels like it.

Just one more straw at which to grab...]]> http://www.dslreports.com/forum/remark,22443930 Tue, 26 May 2009 02:45:02 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22443867 anon :

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 !]]> http://www.dslreports.com/forum/remark,22443867 Tue, 26 May 2009 02:12:11 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22441955 TilhasBB : 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]]> http://www.dslreports.com/forum/remark,22441955 Mon, 25 May 2009 18:31:55 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22440242 loginatnine : Is a lease under the 192.168.1.100 mark even valid? I mean, does anyone here has a valid setup and its dhcp range set up to 192.168.1.2 to 192.168.1.99? Because if tomato allow a dhcp request under the .100 mark and it's never working under that mark, this should definitely be considered as a bug...

I have yet to see a computer with this problem, everyone is gone for the day so I can't check what you're asking jfmezei but I'll try to get the answer asap!]]> http://www.dslreports.com/forum/remark,22440242 Mon, 25 May 2009 11:25:29 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22439554 jfmezei : 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.]]> http://www.dslreports.com/forum/remark,22439554 Mon, 25 May 2009 05:33:38 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22439213 TilhasBB : 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.]]> http://www.dslreports.com/forum/remark,22439213 Mon, 25 May 2009 02:21:01 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22439032 paulwye : 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.]]> http://www.dslreports.com/forum/remark,22439032 Mon, 25 May 2009 01:07:53 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22439004 loginatnine : 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!]]> http://www.dslreports.com/forum/remark,22439004 Mon, 25 May 2009 00:56:42 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22438979 paulwye : 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]]> http://www.dslreports.com/forum/remark,22438979 Mon, 25 May 2009 00:50:04 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22438956 loginatnine : 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]]> http://www.dslreports.com/forum/remark,22438956 Mon, 25 May 2009 00:40:35 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22438923 paulwye : 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...]]> http://www.dslreports.com/forum/remark,22438923 Mon, 25 May 2009 00:30:15 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22438848 loginatnine : Hey there

I'm having the EXACT same problem, I've even ordered another wrt54gl and the same thing happen!!! When friends come over, they can connect fine like 1 time out of 4 I would say. I have to give them a static DHCP lease in order for it to work. Basically, my DHCP range is from 192.168.1.100 to 192.168.1.149 and almost each time someone try to connect, it gives them an address like 192.168.1.7 or .4, they can access the LAN and the router config page fine but no internet...
Glad to know I'm not the only one with this problem, however, I haven't found a solution yet...I'm on velcom with a single DSL line, mlppp activated.

EDIT: these commands solved the problem for a few days but it didn't last...Feel free to try it though
»www.linksysinfo.org/forums/showt···?t=60509]]> http://www.dslreports.com/forum/remark,22438848 Mon, 25 May 2009 00:06:22 EDT Re: Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22437603 anon : You might want to look at the CPU loads for your mlppp 2 lines and wireless configuration. I remember reading about CPU usage might be too much for that. ]]> http://www.dslreports.com/forum/remark,22437603 Sun, 24 May 2009 18:14:33 EDT Weird Tomato DHCP Issue http://www.dslreports.com/forum/remark,22437565 TilhasBB : I am having a DHCP problem thats driving me crazy.
I seem to be missing something. If you guys can take a look i'd be grateful.

When a computer LAN or WIFI tries to log into the internet, It would not work. It would be assigned an IP and can access the router and local network but NOT the internet.

If you look at the Device list, Under ethe1, its assigned an IP but the Name is blank and Lease is Blank.
Rebooting the machine or router several times does not help. The machine must manually be assigned a different ip, then set to automatic to get internet access.
Problem still happens after that's been done a few days later and the same procedure must be repeated.

Here's what i've tried.
- Erase all data in NVRAM memory (thorough).
- Reput the Tomato/MLPPP Version 1.22-mp3alpha5er1 firmware.
- Changed SSID
- Formatted and reinstalled windows 7 (7100) on XPS M1330 Laptop.
- Formatted and reinstalled windows xp on Inspiron 6400
- Changed DHCP Range to what automatically initially assigning to 192.168.1.51 to 192.168.1.100
- Changed SSID and put only basic configuration (PPPOE MLPPP On with SSID wireless, disabled Bandwidth monitoring)

2 DSL Links running Dual MLPPP on WRT54GL. Not Overclocked and wifi running on default 42mw running in ventilated area away from anything electronic.

]]> http://www.dslreports.com/forum/remark,22437565 Sun, 24 May 2009 17:59:20 EDT