search

MEGA65 / mega65-tools

Tools and Utilities for the MEGA65 Retro Computers
GNU General Public License v3.0
30 stars 33 forks source link

etherload and mega65_ftp using link-local IPv6 instead of IPv4 #178

Closed ki-bo closed 1 year ago

ki-bo commented 1 year ago

Is your feature request related to a problem? Please describe. Currently, the MEGA65 always uses the same address as the PC but with the last number exchanged by .65 . This imposes a constraint, especially for users that already have that address reserved for other uses (eg. in the DHCP pool of their router).

Describe the solution you'd like The tools should allow to set an arbitrary IP address to be used for the data transfer. After an initial configuration via broadcast packets, the MEGA65 shall continue to use the user-defined IP for the following communication.

The tools should use the EUI-64 IPv6 address to make communication possible without any configuration on either client or server side.

Describe alternatives you've considered

  1. Keep as is (inflexible)
  2. Provide a system-wide network configuration (huge task, maybe a feature for the future)

Additional context

ki-bo commented 1 year ago

Update: finally, I merged this request with another one where the CORE should be able to broadcast beacon packets so it can be found in the network. To avoid IP configuration to be added to the base system, we just take the EUI-64 IPv6 link-local address of the MEGA and use that one. Etherload and mega65_ftp need to be rebuilt to communicate via IPv6 for this. Also, IPv6 should be used to discover the MEGA65 in the network automatically (using said beacon), so no need to specify any IP address any more.