DHCP not getting Gateway Address?

Hi Guys,

I am running v1.02 software on a MK II empeg, and have noticed that the Gateway address isn't set when the IP number is collected using DHCP (well I assume that is the problem), meaning that the empeg can't be seen outside the local subnet (not necessarily a bad thing), whereas when you set the IP, subnet mask and gateway manually the empeg can be pinged/seen from anywhere. Is this fixed in 1.1 or is it something that still needs to be addressed?

[copy emailed to [email protected]]

(list 6284, Mk1 S/N 00299 4GB blue [for sale]. Mk2 S/N 080000094 6GB blue)

This can only be a bug if you can verify that your DHCP service process on your server is actually supplying the gateway address as part of it's DHCP response, and the empeg is not picking it up. It is not a required item in a DHCP response ( I would need to check the RFC to be sure about this, and it is also server implementation dependent).

Have you checked to see if the Gateway address is being supplied by your DHCP server?

One of the few remaining Mk1 owners... #00015

The router settings are supplied in DHCP option #3 (according to RFC2132). Like it says, 'option'. However, I wouldn't discount the possibility of v1.02 being broken in this regard. Also, we've found several DHCP servers/home routers that (ahem) interpret the RFC differently.



Roger - not necessarily speaking for empeg