dhcpv4/server.go binding to interface not working properly on macOS about dhcp HOT 7 CLOSED

hey @begetan , we know of this limitation. The same problem has been addressed for the client, and I have a local branch with a partial solution implemented for the server, too. The binding is implemented in https://github.com/insomniacslk/dhcp/blob/master/dhcpv4/bindtodevice_linux.go (same goes for darwin), so this is just matter of time.

Issue #231 can be prioritized - the only thing to decide is whether to have this structure:

dhcp/client/{Client6,Client4}

or this structure:

dhcp/dhcpv6/client/Client
dhcp/dhcpv4/client/Client

Both have advantages and disadvantages. The same has to be done for server code.

I would like some input from @pmazzini and @hugelgupf on which structure to use, we can discuss it on #231.

from dhcp.

I think it would be better to have:

dhcp/dhcpv6/client/Client
dhcp/dhcpv4/client/Client

from dhcp.

A little update. With local addr = 0.0.0.0 server able to capture broadcast packets, but not able to send. Here is a failed code:

        if _, err := conn.WriteTo(r.ToBytes(), peer); err != nil {
                glog.Infof("Cannot reply to client: %v", err)
        }

There is no error message nor packet replied to requestor. For that reason I've update my proposal and focused it on final separation of Server code: #190

from dhcp.

Is this still an issue after PR #260?

from dhcp.

If you set localAddr = 0.0.0.0 it can capture packets, but from all system's interfaces of course, which isn't acceptable for real operation.

This is being looked at in #310

from dhcp.

@begetan Is this still an issue?

from dhcp.

I think this is done. Otherwise, feel free to reopen it.

from dhcp.