Comments on: Need Macintosh DHCP help http://www.choicywhiteboy.com/2009/12/need-macintosh-dhcp-help/ Man. Father. Geek. Husband. Gamer. Fri, 22 Jul 2011 21:34:21 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: AC http://www.choicywhiteboy.com/2009/12/need-macintosh-dhcp-help/comment-page-1/#comment-345 AC Mon, 21 Dec 2009 07:53:30 +0000 http://www.choicywhiteboy.com/?p=562#comment-345 Well, I found one work around, albeit a temporary one. I set up a vhost on the D-Link that routes DNS from the D-Link to the NAS, and then set the D-Link's "primary" DNS to the EXTERNAL interface of the D-Link causing it to turn it back around internally. If I had a static IP address for my DSL, I'd be done. For longer term, maybe I'll just make an "internal.accapehart.com" subdomain and host it out on easyDNS like I do all my public DNS info. Well, I found one work around, albeit a temporary one. I set up a vhost on the D-Link that routes DNS from the D-Link to the NAS, and then set the D-Link’s “primary” DNS to the EXTERNAL interface of the D-Link causing it to turn it back around internally. If I had a static IP address for my DSL, I’d be done.

For longer term, maybe I’ll just make an “internal.accapehart.com” subdomain and host it out on easyDNS like I do all my public DNS info.

]]> By: AC http://www.choicywhiteboy.com/2009/12/need-macintosh-dhcp-help/comment-page-1/#comment-343 AC Mon, 21 Dec 2009 06:30:43 +0000 http://www.choicywhiteboy.com/?p=562#comment-343 I'm starting to think that it really was using the (stale) lease from the D-Link. I'd been working with it wired. I went out for dinner, came back and tried wireless, and got a self-assigned IP. So maybe the NAS is failing to hand out DHCP leases after all. It sure looks like it's trying. I see it starting the handshake over and over for the wireless that never connects: <blockquote>Dec 20 22:23:48 nas dhcpd: DHCPDISCOVER from 00:26:bb:11:84:c7 via eth0 Dec 20 22:23:48 nas dhcpd: DHCPOFFER on 192.168.1.31 to 00:26:bb:11:84:c7 via eth0 Dec 20 22:23:51 nas dhcpd: DHCPDISCOVER from 00:26:bb:11:84:c7 via eth0 Dec 20 22:23:51 nas dhcpd: DHCPOFFER on 192.168.1.31 to 00:26:bb:11:84:c7 via eth0 Dec 20 22:23:55 nas dhcpd: DHCPDISCOVER from 00:26:bb:11:84:c7 via eth0 Dec 20 22:23:55 nas dhcpd: DHCPOFFER on 192.168.1.31 to 00:26:bb:11:84:c7 via eth0</blockquote> Maybe if <em>everything</em> is set to DHCP, the D-Link will just take care of it all? I’m starting to think that it really was using the (stale) lease from the D-Link. I’d been working with it wired. I went out for dinner, came back and tried wireless, and got a self-assigned IP. So maybe the NAS is failing to hand out DHCP leases after all. It sure looks like it’s trying. I see it starting the handshake over and over for the wireless that never connects:

Dec 20 22:23:48 nas dhcpd: DHCPDISCOVER from 00:26:bb:11:84:c7 via eth0
Dec 20 22:23:48 nas dhcpd: DHCPOFFER on 192.168.1.31 to 00:26:bb:11:84:c7 via eth0
Dec 20 22:23:51 nas dhcpd: DHCPDISCOVER from 00:26:bb:11:84:c7 via eth0
Dec 20 22:23:51 nas dhcpd: DHCPOFFER on 192.168.1.31 to 00:26:bb:11:84:c7 via eth0
Dec 20 22:23:55 nas dhcpd: DHCPDISCOVER from 00:26:bb:11:84:c7 via eth0
Dec 20 22:23:55 nas dhcpd: DHCPOFFER on 192.168.1.31 to 00:26:bb:11:84:c7 via eth0

Maybe if everything is set to DHCP, the D-Link will just take care of it all?

]]>