Compare commits

..

No commits in common. "c64cd247c34bd72f22e7099da45e99895c9eb063" and "ba7aafd464b24a7bd6dc6c12973d882ed4c1492a" have entirely different histories.

2 changed files with 2 additions and 11 deletions

View file

@ -11,17 +11,10 @@ jobs:
container:
image: ubuntu:24.04
steps:
- name: Check IPv6
run: |
- run: |
echo "My routes" && cat /proc/net/route
echo "My routes (IPv6)" && cat /proc/net/ipv6_route
echo 'Acquire::ForceIPv6 "true";' > /etc/apt/apt.conf.d/1000-force-ipv6-transport
apt-get update
apt-get install --yes curl
curl -s -o /dev/null https://ipv6.google.com
- name: Check IPv4 proxy
env:
HTTP_PROXY: "http://10.0.0.2:8888"
HTTPS_PROXY: "http://10.0.0.2:8888"
run: |
curl -s -o /dev/null https://ipv4.google.com

View file

@ -14,8 +14,6 @@ It's hostname is ``fsn1-2.forsaken-ashbirds.net``.
- __Your usage of this runner must be responsible.__
Please don't overload it or run actions which would harm the reputation of this instance.
- You are free to register your own runners inside your organizations, repositories or inside your account.
[See docs/hosting-runners.md](docs/hosting-runners.md) or [docs/hosting-runners-rootless.md](docs/hosting-runners-rootless.md) for a little guidance.
[See docs/hosting-runners.md](docs/hosting-runners.md) for a little guidance.
- If you want to volunteer additional runner capacity to the entire instance, feel free to get in touch.
- Provided runners may not be available 24/7 but should be online most of the day.
- IPv4 connectivity for HTTP connections is available through a proxy service.
Use it by specifying ``HTTP_PROXY=10.0.0.2:8888`` and ``HTTPS_PROXY=10.0.0.2:8888`` where required. (``10.0.0.0/24`` is an internal network where the proxy machine is reachable.)