Skip to content

Missing IPv6 default route in routing table after wings was started for first time #107

@MaZe3D

Description

@MaZe3D

I have an issue where after the first start of the wings daemon no IPv6 connections can be made anymore, because the routing table misses the default route.

I made an output of the first time the software is started.

Output of ip -6 route before first wings start

2003:df:1f33:1145::/64 dev enp1s0 proto kernel metric 256 expires 86092sec pref medium
fd4f:71d8:b745:45::/64 dev enp1s0 proto kernel metric 256 expires 86092sec pref medium
fe80::/64 dev enp1s0 proto kernel metric 256 pref medium
default via fe80::230:59ff:fe28:cd3a dev enp1s0 proto ra metric 1024 expires 1492sec mtu 1492 hoplimit 64 pref medium

Output of first wings --debug

 INFO: [Jun 16 20:58:59.456] writing log files to disk path=/var/log/pelican/wings.log

                     ____
__ Pelican _____/___/_______ _______ ______
\_____\    \/\/    /   /       /  __   /   ___/
   \___\          /   /   /   /  /_/  /___   /
        \___/\___/___/___/___/___    /______/
                            /_______/ 1.0.0-beta13

Copyright © 2018 - 2025 Dane Everitt & Contributors

Website:  https://pelican.dev
 Source:  https://github.com/pelican-dev/wings
License:  https://github.com/pelican-dev/wings/blob/main/LICENSE

This software is made available under the terms of the MIT license.
The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.

DEBUG: [Jun 16 20:58:59.457] running in debug mode    
 INFO: [Jun 16 20:58:59.457] loading configuration from file config_file=/etc/pelican/config.yml
 INFO: [Jun 16 20:58:59.485] configured wings with system timezone timezone=Europe/Berlin
DEBUG: [Jun 16 20:58:59.485] ensuring root data directory exists path=/var/lib/pelican
DEBUG: [Jun 16 20:58:59.485] ensuring passwd file exists filepath=/etc/pelican/passwd
DEBUG: [Jun 16 20:58:59.486] ensuring server data directory exists path=/var/lib/pelican/volumes
DEBUG: [Jun 16 20:58:59.486] ensuring archive data directory exists path=/var/lib/pelican/archives
DEBUG: [Jun 16 20:58:59.486] ensuring backup data directory exists path=/var/lib/pelican/backups
 INFO: [Jun 16 20:58:59.486] checking for pelican system user username=pelican
 INFO: [Jun 16 20:58:59.657] configured system user successfully gid=995 uid=999 username=pelican
 INFO: [Jun 16 20:58:59.658] no log rotation configuration found: adding file now
 INFO: [Jun 16 20:58:59.663] fetching list of servers from API
DEBUG: [Jun 16 20:58:59.663] making request to external HTTP endpoint endpoint=https://pelican.EXAMPLE.com:443/api/remote/servers?page=0&per_page=50 headers=map[Accept:[application/json] Authorization:[(redacted)] Content-Type:[application/json] User-Agent:[Pelican Wings/v1.0.0-beta13 (id:FkMfSFx2tvmPw6dI)]] method=GET
 INFO: [Jun 16 20:59:00.952] processing servers returned by the API total_configs=0
DEBUG: [Jun 16 20:59:00.953] using 8 workerpools to instantiate server instances
 INFO: [Jun 16 20:59:00.953] finished processing server configurations duration=1.39128ms
 INFO: [Jun 16 20:59:00.958] creating missing pelican0 interface, this could take a few seconds...
 INFO: [Jun 16 20:59:01.259] configuring system crons  interval=1m0s subsystem=cron
 INFO: [Jun 16 20:59:01.259] starting cron processes   subsystem=cron
 INFO: [Jun 16 20:59:01.260] configuring internal webserver host_address=0.0.0.0 host_port=10000 use_auto_tls=false use_ssl=true
 INFO: [Jun 16 20:59:01.260] updating server states on Panel: marking installing/restoring servers as normal
DEBUG: [Jun 16 20:59:01.260] making request to external HTTP endpoint endpoint=https://pelican.EXAMPLE.com:443/api/remote/servers/reset headers=map[Accept:[application/json] Authorization:[(redacted)] Content-Type:[application/json] User-Agent:[Pelican Wings/v1.0.0-beta13 (id:FkMfSFx2tvmPw6dI)]] method=POST
 INFO: [Jun 16 20:59:01.265] sftp server listening for connections listen=0.0.0.0:10001 public_key=ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAILxKUk1jChGhvq4nl8AOG+fLGWtCtuR1quyUA+L+rXRi

Output of ip -6 route after first wings start

2003:df:1f33:1145::/64 dev enp1s0 proto kernel metric 256 expires 86043sec pref medium
fd4f:71d8:b745:45::/64 dev enp1s0 proto kernel metric 256 expires 86043sec pref medium
fdba:17c8:6c94::/64 dev pelican0 proto kernel metric 256 linkdown pref medium
fe80::/64 dev enp1s0 proto kernel metric 256 pref medium

As you can see, the pelican0 route was added and the default route was removed. Therefore no IPv6 connections can be made outside my network.
This issue was reproducible on a Debian 12 (clean install, and following documentation on wings install) as well as on a OpenSUSE Leap 15.6 installation (which is not listed as supported in the documentation).

IPv4 connections still work.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions