@talktodan I have had the same issue. I've tried rebooting the switch via System Tools -> System reboot to no avail. Finally, I pulled out the power cable, waited half a minute and attached the power cable again. The DHCP packets get forwarded/distributed again after that.

  @talktodan Hello all!

Does anyone know if this ever got addressed by TP-Link?

I just spent the better part of two days fighting with a few Raspberry Pi's to get connected to my network.

I think I broke Google from the search commbinations and forums I went through.

LUCKILY I ran accross this topic and to my surprise,,, 

1. Unplug power from my TL-SG1016DE

2. Give it the 30 second (1 Mississippi, etc) slow count

3. Plug power back in and

4. Cry tears of joy that the 4 Raspberry Pi's (that all other forums said there was something wrong with the actual board) are now running PERFECTLY.

The only way I could get them to work prior was was either connect them directly to my router OR use a "dumb" switch connected to my router (which technically is the same)

restarting the switch via the "Easy Manage" software or the web gui got me nowhere.

There's got to be a firmware that addresses this.

  @thetechjester 

For everyone struggling with this, make sure you know to configure VLAN settings (tagged and untagged) on each interface. This dictates the EGRESS behavior only. You also must set PVID (under VLAN -> Port) to match untagged INGRESS packets to the desired VLAN. This is confusing if you're accustomed to other switches (wherein typically you can only have 1 untagged vlan per port, and thus it is implied behavior for both ingress and egress).