cloudflare / cloudflare/cloudflared

cloudflared resolved edge addresses conflicts with local tun addresses while edge discovering

Open
#1,140 0 comments 0 reactions 0 assignees View on GitHub
Priority: Normal Type: Bug
Dominant language
Go
Stars
15.6k
Forks
1.4k
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
cloudflared resolved edge addresses conflicts with local tun addresses while edge discovering

it will always use local tun addresses but not those from region1.argotunnel.com

the error logs

```
Retrying connection in up to 2s connIndex=0 event=0 ip=198.18.0.5
Failed to create new quic connection error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=0 event=0 ip=198.18.0.5
```

local tun ip a results
```
eta: mtu 9000 qdisc pfifo_fast state UNKNOWN group default qlen 500
link/none
inet 198.18.0.1/30 brd 198.18.0.3 scope global Meta
valid_lft forever preferred_lft forever
inet6 fdfe:dcba:9876::1/126 scope global
valid_lft forever preferred_lft forever
inet6 fe80::9743:9172:51db:886/64 scope link stable-privacy
valid_lft forever preferred_lft forever
```

it can be seen that 198.18.0.5 are local tun ips

**To Reproduce**
Steps to reproduce the behavior:
1. setup a local tun interface
2. run cloudflared run

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.