IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Some things not adding up
Your original post mentions the first address in the DHCP lease block is 192.168.2.150, but the PC is asking for .2.101. That is outside the block and may be the reason why the router is not responding.

Setting the router to .1.64 has no impact on the modem leasing out the address. It has no clue you assigned it to the router. (Some servers ping an address to be leased out of precaution, but not your modem apparently.)

The main thing is that the broadcast should not go through the router. In your case it does, so your "router" seems to be acting as a switch. If it is one of those 4+1 port thingies, are you sure you have the modem plugged in the "internet" port? If it really is a switch, then you'll have to make one of them stop acting as a DCHP server as the broadcasts will keep reaching both devices.

Lastly, what are the netmasks? Usually these devices use a 24 bit mask, but the modem seems to use at most a 23 bit mask. If it is even less, then the networks of the modem and router overlap which can lead to other problems. I usually switch one of the devices to a 172.16 network if they both are set for 192.168.x.x.
New There was a change in there
I originally had the router set up to start giving out DHCP at .2.150, but going with the Windows school of debugging -- when everything is set up right and it's still not working, start changing things that shouldn't matter and see what happens -- I changed it to start giving out at .2.100.

Then, with the router not plugged into the modem, the PC got .2.101 from the router. I plugged the router back into the modem and restarted networking on the PC and it grabbed .1.64.

I'll double-check what I have everything plugged into. Yes, it is a 4+1. If it turns out to be that, I'll be pissed at myself, but really grateful.
--

Drew
New Aaaaarrrrrrrrrgh! That got it
I had the modem plugged into the router's "uplink" port instead of its "WAN" port. Fixed that and now everything seems copacetic. Router is handing out IPs again, and they're in the right range.

Thanks for asking the dumb "did you plug it in right?" question.
--

Drew
New Glad you got it back. Dueling DHCP servers are always fun...

     DHCP not working under WLAN - (drook) - (23)
         Dunno. I usually punt and give fixed IP addresses. -NT - (Another Scott)
         Re: DHCP not working under WLAN - (boxley) - (4)
             Don't have it - (drook) - (3)
                 dang, thats redhat - (boxley)
                 /etc/network/interfaces - (scoenye) - (1)
                     NetworkManager can ignore that. - (static)
         Your Router is borked... - (folkert) - (2)
             I'll give that a shot - (drook)
             Not quite uPNP - (scoenye)
         Getting DHCP from the wrong device - (drook) - (13)
             Disable the DHCP server in the modem? - (static) - (2)
                 Not available - (drook) - (1)
                     Ouch. :-( - (static)
             Some things not adding up - (scoenye) - (3)
                 There was a change in there - (drook)
                 Aaaaarrrrrrrrrgh! That got it - (drook) - (1)
                     Glad you got it back. Dueling DHCP servers are always fun... - (scoenye)
             Ummm... - (folkert) - (5)
                 Turns out the modem is a crippled router - (drook) - (4)
                     AT&T just... gah... - (folkert) - (3)
                         I can follow some of those TLAs, - (Ashton) - (2)
                             Well, the place I work for... - (folkert) - (1)
                                 Lucky.. lucky to work Kool-Aid free, - (Ashton)

SoylentSheep is Sheeple!
48 ms