Skip to content

snet.Conn support for roaming use cases #175

@semcodech

Description

@semcodech

Binding the snet.UDPConn to an unspecified address is not possible (prevented by SCIONNetwork.OpenRaw and SCIONNetwork.NewCookedConn, would be supported by the underlying net.UDPConn.ListenUDP though.

  • Is the reason for this restriction related to the packet reception?
  • What is the recommended way of handling roaming use cases?
    Should the interface's IP addresses continuously be monitored, the connection closed and a new connection opened, or is there a better way to handle such a scenario?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions