DHCP issue, probably related to STP loop detection.

[Hotcooler]

Seems like there's an issue with what I assume is timings or timeouts related to loopback detection on switches.

I'm unable to recieve an IP address on Cisco switches until I enable spanning tree portfast, similarly Loopback detection on Dlink switches also prevents PE from getting an IP address. Same happens on Zyxel switches with Loop Guard enabled. So seems like some option to enable delayed DHCP request or retry count or something would probably solve the issue.

Since nearly 100% of our network use loop detection features, it severely limits advantages that PE has over cheapo wiremap devices.

Also I imagine it might be the same issue described in this thread : http://forum.pockethernet.com/index.php?topic=140.0

[jboxtel]

We're looking into this and try to find a quick fix for it.

[philip]

Same problem here (Cisco switches).

[philip]

Any update on this issue? Has a fix or workaround been found?

[jboxtel]

Hi Philip. Sorry that it takes a bit long, but we're working on it, we'll probably add an option to delay the DHCP requests or increase the retry count.

[Hotcooler]

So. It's March already. Any eta?

[JeffB]

Yes, I saw this issue too.  Or could be related to VLAN tests.   

[alko]

Hi.
I checked with my Pockethernet and have the same issue. I do not get the IP adresses from DHCP. The problem is only in version 24. I downgraded my device to versions 22 and 21 and DHCP function works.

Br, Alko.

[mgovier]

Is there any progress on fixing this DHCP issue? I have only just received my PE and, so far, on two Cisco switches and three routers, have failed to get any one to perform DHCP successfully. Physical layer cable testing works, just cannot perform any of the more interesting tests. This occurs even running just the Link and DHCP tests alone. Link test works and gives expected results.

Update May 12th: Any news? Might an earlier firmware work? I might try that anyway, let me see if I can find the earlier firmware... Just rolled back to V22 and yes, DHCP works - on at least one device. Will evaluate using this firmware for now but you need to look carefully at what has changed between V22 and V26 the device was supplied with.

[max951]

Hi, the same issue here with.
HW: 6
FW: 26

It's a misery that this problem was already known for more than 4 months but could not be solved yet.
If i could help with logfiles or any other thing, please let me know.

Br, Max

[jboxtel]

Hi guys. Short update, we've fixed the issue and will release a firmware update in the next 2 weeks.

[Travis]

Thanks for the update. Excited for the new Firmware. Does this new firmware also address the incorrect quick test LED color readout?

FYI, the link "Latest Firmware" on your website under "Support" takes you to the forum page for Firmware Version 22.

[Mike1233]

Thanks for the support and the next update.

I have a little question. In earlier firmware versions i thought that is was possible to add a static ip adres etc and then test the connexion. This give the same results as the auto dhcp connexion info. This is not working for now. Has this something to do with the problem what here is talking about or am i wrong and has it never worked like i thought it did?

[hideyourcables]

Same issue here with Cisco switches.  running HW6 firmware 26.  any news on the firmware update?  don't really want to roll the firmware back if I can help it.

[jboxtel]

An app update is coming beginning of next week, which should solve this issue.