SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-04-13 21:16:18 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Wireguard interface not up #29

New Issue
Closed
opened 2025-11-20 05:05:07 -05:00 by saavagebueno · 5 comments
saavagebueno commented 2025-11-20 05:05:07 -05:00
Owner
Copy Link

Originally created by @xiya233 on GitHub (Jul 5, 2021).

Hello everyone

I have a 5.10 kernel:

uname -a

Linux debian-1cpu-1gb-sg-sin1 5.10.0-0.bpo.7-amd64 #1 SMP Debian 5.10.40-1~bpo10+1 (2021-06-04) x86_64 GNU/Linux

The wireguard kernel module has been loaded:

modprobe wireguard
lsmod | grep wireguard

wireguard              94208  0
libchacha20poly1305    16384  1 wireguard
ip6_udp_tunnel         16384  1 wireguard
udp_tunnel             20480  1 wireguard
libblake2s             16384  1 wireguard
curve25519_x86_64      49152  1 wireguard
libcurve25519_generic    49152  2 curve25519_x86_64,wireguard

After starting wiretrustee, there is no wiretrustee0 interface:

systemctl status wiretrustee.service

● wiretrustee.service - Wiretrustee Service
   Loaded: loaded (/lib/systemd/system/wiretrustee.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2021-07-05 14:41:31 UTC; 6min ago
 Main PID: 799 (wiretrustee)
    Tasks: 3 (limit: 1135)
   Memory: 6.7M
   CGroup: /system.slice/wiretrustee.service
           └─799 /usr/local/bin/wiretrustee up --config /etc/wiretrustee/config.json --log-level debug

ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 46:d1:1a:9d:07:2e brd ff:ff:ff:ff:ff:ff
    inet xxx.xxx.xxx.xxx/22 brd xxx.xxx.xxx.xxx scope global dynamic eth0
       valid_lft 85710sec preferred_lft 85710sec
    inet6 fe80::44d1:1aff:fe9d:72e/64 scope link 
       valid_lft forever preferred_lft forever

What did i do wrong? Any suggestions, thanks

Originally created by @xiya233 on GitHub (Jul 5, 2021). Hello everyone I have a 5.10 kernel: `uname -a` `Linux debian-1cpu-1gb-sg-sin1 5.10.0-0.bpo.7-amd64 #1 SMP Debian 5.10.40-1~bpo10+1 (2021-06-04) x86_64 GNU/Linux` The wireguard kernel module has been loaded: ``` modprobe wireguard lsmod | grep wireguard ``` ``` wireguard 94208 0 libchacha20poly1305 16384 1 wireguard ip6_udp_tunnel 16384 1 wireguard udp_tunnel 20480 1 wireguard libblake2s 16384 1 wireguard curve25519_x86_64 49152 1 wireguard libcurve25519_generic 49152 2 curve25519_x86_64,wireguard ``` After starting wiretrustee, there is no wiretrustee0 interface: `systemctl status wiretrustee.service` ``` ● wiretrustee.service - Wiretrustee Service Loaded: loaded (/lib/systemd/system/wiretrustee.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2021-07-05 14:41:31 UTC; 6min ago Main PID: 799 (wiretrustee) Tasks: 3 (limit: 1135) Memory: 6.7M CGroup: /system.slice/wiretrustee.service └─799 /usr/local/bin/wiretrustee up --config /etc/wiretrustee/config.json --log-level debug ``` `ip a` ``` 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 46:d1:1a:9d:07:2e brd ff:ff:ff:ff:ff:ff inet xxx.xxx.xxx.xxx/22 brd xxx.xxx.xxx.xxx scope global dynamic eth0 valid_lft 85710sec preferred_lft 85710sec inet6 fe80::44d1:1aff:fe9d:72e/64 scope link valid_lft forever preferred_lft forever ``` What did i do wrong? Any suggestions, thanks
saavagebueno commented 2025-11-20 05:05:08 -05:00
Author
Owner
Copy Link

@braginini commented on GitHub (Jul 5, 2021):

Hey,
Did you call wiretrustee init command?

And could you please provide the contents of /etc/wiretrustee/config.json ? Please omit the private key.

@braginini commented on GitHub (Jul 5, 2021): Hey, Did you call `wiretrustee init` command? And could you please provide the contents of `/etc/wiretrustee/config.json` ? Please omit the private key.
saavagebueno commented 2025-11-20 05:05:08 -05:00
Author
Owner
Copy Link

@xiya233 commented on GitHub (Jul 5, 2021):

Hey,
Did you call wiretrustee init command?

And could you please provide the contents of /etc/wiretrustee/config.json ? Please omit the private key.

Sorry, it's my problem.

My firewall blocks the wiretrustee port

Your project is great!

@xiya233 commented on GitHub (Jul 5, 2021): > Hey, > Did you call `wiretrustee init` command? > > And could you please provide the contents of `/etc/wiretrustee/config.json` ? Please omit the private key. Sorry, it's my problem. My firewall blocks the wiretrustee port Your project is great!
saavagebueno commented 2025-11-20 05:05:08 -05:00
Author
Owner
Copy Link

@braginini commented on GitHub (Jul 5, 2021):

I'm glad to hear that the problem has been solved
@xiya233

Could you please which port was blocked by your firewall? Signal service port?

@braginini commented on GitHub (Jul 5, 2021): I'm glad to hear that the problem has been solved @xiya233 Could you please which port was blocked by your firewall? Signal service port?
saavagebueno commented 2025-11-20 05:05:09 -05:00
Author
Owner
Copy Link

@xiya233 commented on GitHub (Jul 5, 2021):

@braginini

Yes, there may be other ports that are also blocked.

I configure the firewall to allow all traffic to connect:

firewall-cmd --set-default-zone=trusted
firewall-cmd --reload
@xiya233 commented on GitHub (Jul 5, 2021): @braginini Yes, there may be other ports that are also blocked. I configure the firewall to allow all traffic to connect: ``` firewall-cmd --set-default-zone=trusted firewall-cmd --reload ```
saavagebueno commented 2025-11-20 05:05:09 -05:00
Author
Owner
Copy Link

@braginini commented on GitHub (Jul 5, 2021):

Alright, thank you.
Just opening the signal port should be enough.

@braginini commented on GitHub (Jul 5, 2021): Alright, thank you. Just opening the signal port should be enough.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#29
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?