Raspberry Pi Forums

I am am unable to get a dhcp lease with ip with the 512 mb version, yet with the 256 mb version using the same SD card with the same OS, it works fine. It appears as though it is specific to the 512 mb version, and not software related, as I have experienced the exact same results with 5 different OS's, all get an ip using dhcp with the 256 mb version, while no ip with the 512 mb version, that is using the same SD for both versions, therefore in each case the OS was exactly the same.

It appears to be specific to my router, as I am able to get an ip with other routers. D- Links DGL - 4100

Any one know what it may be that is causing only the 512 mb version to not be able to get an ip?

Unfortunately my isp requires dhcp for a connection. I would like to figure out what the problem is, as when my gf's 85 yr. old father is finished with it, I get it back.

His computer went down, and I loaned my 256 mb raspberry until the 512 mb version showed up, then set him up with the 512 mb version. He would have purchased a new computer, but he forgot to pay his property tax's last year, and now has to pay 2 years. After he gets that all paid off he will get a new computer. But in the mean time he is using the raspberry 512 mb. He is a retired radar engineer, and thinks the raspberry pi is really cool!

Are you sure there is no MAC address filtering within the router?

Maybe http://elinux.org/R-Pi_Troubleshooting# ... pberry_Pis is relevant.

I'd be looking at the power supply, namely the voltage across TP1 and TP2, if its marginal, stuff that works on one Pi, may not work on another.

SinOjos wrote:It appears to be specific to my router, as I am able to get an ip with other routers. D- Links DGL - 4100

Any one know what it may be that is causing only the 512 mb version to not be able to get an ip?

Some (cable) Internet providers require DHCP because you 'll get a limited amount of ip's. To make it harder to switch computers, some of these providers lock DHCP ip's to MAC adresses. Maybe that's what you're looking at?

Over here, it helps to power off the offending router for ten minutes or os. After powering up again, the list is cleared.

DBryant wrote:Are you sure there is no MAC address filtering within the router?

Not using mac address fltering.

drgeoff wrote:Maybe http://elinux.org/R-Pi_Troubleshooting# ... pberry_Pis is relevant.

Thought of that so just to make sure tried a clean new install and still no joy.

pluggy wrote:I'd be looking at the power supply, namely the voltage across TP1 and TP2, if its marginal, stuff that works on one Pi, may not work on another.

Was using a 1.2 amp 5v power supply, thought perhaps with 512 mb of memory might need a little more gas so put it on a 3 amp 5v, still no joy.

cyrano wrote:Some (cable) Internet providers require DHCP because you 'll get a limited amount of ip's. To make it harder to switch computers, some of these providers lock DHCP ip's to MAC adresses. Maybe that's what you're looking at?

Over here, it helps to power off the offending router for ten minutes or os. After powering up again, the list is cleared.

Yep tried turning everything off and rebooting the whole network in an attempt to clear out any old stuff.

I could use static ip's with the earlier slower plan with Cox cable, upgraded to the 55mb per/sec down and 10mb per/sec up and forced to use dhcp with the faster plan. I reserve ip address via my dhcp router by mac address, clearing that all out did not help.

I do not have a limit on internel ip's, nor is their any mac address locking that I am aware of. As I regularly build workstations and servers and such in my home office.

In fact on my workstations and my server for my internal network, I use 3 nics on each box which are bonded together, using Gentoo Linux. The ISP does not care, other than not providing a route to static ip's. I tried configuring a static ip and routing to their dns servers directly, they did not like that!

ISP's are becoming increasingly invasive upon customers lan's. You can run a filter/firewall server to stop them from scanning your internal network, and could pipe internet traffic through one server with a dhcp lease to make it look like only one computer is connected. I have nothing to hide so I simply use a dhcp lease for each computer.

I do run an Untangle http://www.untangle.com/ server in bridged mode for added security and control of traffic in and out of my lan. Since I have a gaming router first off the ISP router, I plugged into it by-passing the Untangle server and still no joy on getting dhcp lease. I use that method by-passing Untangle for when I am gaming, need as little latency as possible to match the twitch kiddies. I recently turned 50 and I am getting slow!

I have been able to get a dhcp lease on three different routers, but on on that one router I have a problem, the D- Links DGL - 4100.

It is merely an inconvenience, as I am not able to use my primary dhcp server. I can simply use one of my older no longer used routers plugged into one of the switches or wireless extenders somewhere in the house to provide a dhcp lease, or can use Untangle, or use my lan server to provide dhcp.

I was simply looking for an answer to why it is not working with the D- Links DGL - 4100, as that is the only router out of 4, so far, that a dhcp lease is not obtainable.

Thanks for the input from everyone.

I think it is a specific issue with the D-Links router for some odd reason. After I get the 512mb Raspberry back and I have some time. I will set up a sniffer and look at the packets from both the 256bm version and the 512mb version, to see exactly what the difference is in what is being sent. Then I may be able to determine what it is that the D-Links router does not like.