Summary: RoutBoard 532 will not get a public ip from my cable modems DHCP server but it will get one from any other DHCP server.
I have a RouterBoard 532 with the latest MikroTik software insatlled. I connect using WinBox and check to make sure that the interface I’m using has a DHCP Client running. Yes it does. It says searching… Now I plug the modem in directly to the controller and reboot my router so that it gets the new mac address of the new controller. After a few seconds of my router booting, the routerboard receive an IP from what appears to be a DHCP server on my modem. I get a 192.168.100.2 from somewhere. But the lease time is about 30 seconds. After all the lights become solid on my cable modem, the state changes from bound, to renewing. Then, when lease time is almost up, it changes to rebinding… and then it goes back to searching after the lease time runs out.
I’ve tried this several times with different routerboards. My D-Link is able to connect fine, any computer I connect to it will connect fine. It has to be the way I’m setting it up. The cable provider just needs a simple Dynamic DHCP connection, no fancy PPPoE or anything. I’ve read the documentation a bit and the FAQ/troubelshotting stuff. I’m finally throwing the white flag. I know it’s me because the routerboards are brand new.
Could be that your ISP is still looking for the MAC address of the D-Link.
Try turning the cable box off for a few minutes when you first connect the RouterBoard. Then leave well alone for as long as you can. It may sort itself out eventually.
My D-Link is able to connect fine, any computer I connect to it will connect fine.
Don’t each of those have their own mac address? Why would those be able to connect fine but not my router. Anytime I want I can switch devices, I just simply power cycle the modem and it all fixes itself in about 1 minute.
There’s nothing else I could be doing wrong?
Edit: “It” in the quote, refers to the modem. Maybe you thought I meant any computers I connect to the D-Link work fine. I meant any computers I connect directly to the modem will work fine.
I took it home and got a PPPoE connection working fine with NAT masq and everything. I left my router connected at my apt (where my cable connection won’t get an IP) for a good hour or two before I left for my parents house (where I have PPPoE working fine). The router never got an IP unfortunatley. Right before I left I plugged it into my computer and my d-link router .. and both got connected in a minute.
I’m sure the routerboard 500 is obviously working fine. It’s just something I’m doing wrong and I have no clue. I’ll post the exact syntax I’m using when I get back home tomorrow night.