#45262: files hosted on ftp sites aren't getting mirrored -----------------------------+--------------------- Reporter: jchauvel@… | Owner: admin@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+--------------------- Comment (by dluke@…): Replying to [comment:15 ryandesign@…]:

I don't know much about IPv6.

There's a bunch of info online if you want to learn - I've heard good things about https://ipv6.he.net/certification/ (although I haven't gone through any of it). For our purposes here, there is a block of addresses for MacOS Forge. If everything is on the same broadcast domain, it's probably a /64 (IPv6 addresses are 128 bits long and almost always a /64).

How can I find this information?

One way, would be to look at the ifconfig output on the machine(s) / VMs. For example, the host that I run squid on has ifconfig that looks something like this: {{{ en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV> ether 10:dd:b1:a9:66:f9 inet6 fe80::12dd:b1ff:fea9:66f9%en0 prefixlen 64 scopeid 0x4 inet6 2001:418:1401:62::3 prefixlen 64 inet 129.250.34.3 netmask 0xfffffff8 broadcast 129.250.34.7 nd6 options=1<PERFORMNUD> media: autoselect (1000baseT <full-duplex,flow-control>) status: active }}} So you can see I have an IPv4 /29 and and IPv6 /64 that the host is numbered out of (along with the link-local IPv6 address that we can ignore for now).

The servers whose configurations I know how to examine (the Mac servers) have their IPv6 addresses obtained automatically (whereas their IPv4 addresses are entered manually). I can run `ifconfig` and see the inet6 address of all the servers, but I don't know if they're externally accessible.

From a host that would be connecting to the proxy do `ping6 geeklair.net` and see if you get a reply. or, if the stupid firewall policy blocks ICMP, you could to `telnet -6 geeklair.net 80` and see if you can make a tcp connection. If either (or both) of those succeed, we'll need to figure out which IPv6 block or blocks to add access to - or those hosts may try to connect via IPv6 and will be blocked by my local firewall (and denied by my squid configuration).

For example, I found the purported IPv6 address of the distfiles server, but entering it into Safari produces and error message. According to an IPv6 readiness checker, our web sites are not IPv6 ready, first of all because we don't have an AAAA record. So I'm not sure to what extent, if any, IPv6 connections are occurring within the Mac OS Forge infrastructure.

That's probably also something you should get working (AAAA records in DNS, website and any other services available over IPv6), but is not directly relevant to whether the machines are going to try to make outbound IPv6 connections or not. -- Ticket URL: <https://trac.macports.org/ticket/45262#comment:16> MacPorts <https://www.macports.org/> Ports system for OS X