Ticket #513 (closed enhancement: fixed)

Opened 6 years ago

Last modified 3 years ago

upgrade networking code to allow IP6

Reported by: philip Owned by: alexander
Priority: major Milestone:
Component: ALL modules Version:
Keywords: IP6 Cc:


Lots of IP4 specific code in earthworm. Should upgrade to more agnostic network routines so IP6 can be supported. This is likely a fairly tedious and error prone thing to upgrade, but at some point will be essential.

Here is just one example, export.c in data_exchange/export char client_ip[16]; /* IP address of client from inet_ntoa */

Change History

comment:1 Changed 6 years ago by philip

Just for some background for the curious, see this wikipedia article: https://en.wikipedia.org/wiki/IPv4_address_exhaustion

Basically as of now, the regional address authorities in Asia, Europe and Latin America have already exhausted their supply of IP4 addresses, and North America is expected to exhaust its supply in May 2015. After this an ISP can only recycle existing IP4 address blocks and can no longer acquire new blocks from the regional authorities. Most likely seismic networks will not be directly effected by this for some time, but it would be really nice to have earthworm move towards being IP6 compatible well before it happens.

comment:3 Changed 3 years ago by alexander

  • Owner changed from somebody to alexander

Taking over this ticket. IPv6 upgrade is currently well-underway. Upgrades include consolidating socket initialization functions to be part of the same network utilities in place, and library functions have been written that allow for applications to be blind to the protocol used by the system.

comment:4 Changed 3 years ago by alexander

  • Status changed from new to closed
  • Resolution set to fixed

Closing out this ticket. Work will be delivered with next release, currently in test

Note: See TracTickets for help on using tickets.