IPv6 tests #129

					
				@ -0,0 +8,4 @@

				    steps:

				      - run: |

				          apt update -qq ; apt --quiet install -qq --yes iputils-ping

				          ping -c 1 -6 ::1

s3lph commented

2023-12-02 21:06:09 +00:00

Do you want to verify whether the Forgejo Runner creates its networks with enable_ipv6: true? Or do you want to take it a step further and verify that IPv6 connectivity including ip6tables NAT actually works.

This localhost ping check suffices to do the former, but to achieve the latter, either a ping or (IMO better, as it also works with unprivileged Podman containers) curl to a public IPv6-only server such as ipv6.google.com is needed. An example for this can be found in my docs PR.

Do you want to verify whether the Forgejo Runner creates its networks with `enable_ipv6`: true? Or do you want to take it a step further and verify that IPv6 connectivity including ip6tables NAT actually works. This localhost ping check suffices to do the former, but to achieve the latter, either a ping or (IMO better, as it also works with unprivileged Podman containers) curl to a public IPv6-only server such as ipv6.google.com is needed. An example for this can be found [in my docs PR](https://forgejo.codeberg.page/@docs_pull_243/docs/v1.21/admin/actions/#enable-ipv6-in-docker--podman-networks).

earl-warren commented

2023-12-02 21:17:31 +00:00

In this context, I think the simpler test is good enough as it demonstrates IPv6 is enabled. For the other part, the daemon, it is best done in the setup-forgejo tests because they provide the context where forgejo is also setup and can be configured / reconfigured in various ways for test purposes.

The documentation you wrote is the guide I follow.

In this context, I think the simpler test is good enough as it demonstrates IPv6 is enabled. For the other part, the daemon, it is best done in the [setup-forgejo tests](https://code.forgejo.org/actions/setup-forgejo/pulls/107/files) because they provide the context where forgejo is also setup and can be configured / reconfigured in various ways for test purposes. The documentation you wrote is the guide I follow.

earl-warren commented

2023-12-04 16:57:05 +00:00

For the record it is not possible to test external routing because there appears to be a bug in how IPv6 is supported in Debian LXC containers. For the purpose of verifying IPv6 is available in a workflow this is not strictly necessary although it would be a bonus.

For the record it is not possible to test external routing because [there appears to be a bug in how IPv6 is supported in Debian LXC containers](https://code.forgejo.org/forgejo/lxc-helpers/issues/19). For the purpose of verifying IPv6 is available in a workflow this is not strictly necessary although it would be a bonus.

earl-warren marked this conversation as resolved

earl-warren force-pushed wip-ipv6 from 226bf636e6 to 39e0d5b161

2023-12-03 13:56:38 +00:00

Compare

earl-warren added 1 commit 2023-12-03 14:13:26 +00:00