SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-07-30 09:53:19 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Name-based routing to s3 bucket websites doesn't work #1506

New Issue
Open
opened 2025-11-20 05:31:51 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 05:31:51 -05:00
Owner
Copy Link

Originally created by @samroweemployinc on GitHub (Dec 18, 2024).

Describe the problem

We have an S3 bucket with a "simple website" interface which is behind a blah.s3-website-us-west-1.amazonaws.com DNS name. We've tried to create a name-based route for it, but it doesn't work and we see IPv6 addresses show up in it, which I don't think can work over Netbird. "Doesn't work" means that sometimes our IP restrictions give a 403 and sometimes they don't. We enabled logging on the bucket and saw that all of the 403s came directly from my ISP IP and all of the 200s came from the NB Peer as expected.

One final thing we noticed was that the IP list for that name-based-route just grows and grows despite "Keep Routes" being turned on in the n-b-r.

To Reproduce

Steps to reproduce the behavior:

  1. Create an s3 simple site and allow only private IPs via BucketPolicy ( "Condition": {"IpAddress": {"aws:SourceIp": [...
  2. Create a name-based route for that site
  3. curl a file from it over and over and sometimes get a 403 and sometimes get 200

Expected behavior

The route should be used consistently. IPv6 addresses shouldn't be in the list.

Are you using NetBird Cloud?

Self Host

NetBird version

0.34.1

Originally created by @samroweemployinc on GitHub (Dec 18, 2024). **Describe the problem** We have an S3 bucket with a "simple website" interface which is behind a `blah.s3-website-us-west-1.amazonaws.com` DNS name. We've tried to create a name-based route for it, but it doesn't work and we see IPv6 addresses show up in it, which I don't think can work over Netbird. "Doesn't work" means that sometimes our IP restrictions give a 403 and sometimes they don't. We enabled logging on the bucket and saw that all of the 403s came directly from my ISP IP and all of the 200s came from the NB Peer as expected. One final thing we noticed was that the IP list for that name-based-route just grows and grows despite "Keep Routes" being turned on in the n-b-r. **To Reproduce** Steps to reproduce the behavior: 1. Create an s3 simple site and allow only private IPs via BucketPolicy ( `"Condition": {"IpAddress": {"aws:SourceIp": [...` 2. Create a name-based route for that site 3. curl a file from it over and over and sometimes get a 403 and sometimes get 200 **Expected behavior** The route should be used consistently. IPv6 addresses shouldn't be in the list. **Are you using NetBird Cloud?** Self Host **NetBird version** 0.34.1
saavagebueno added the waiting-feedbacktriage-needed labels 2025-11-20 05:31:51 -05:00
saavagebueno commented 2025-11-20 05:31:52 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Apr 28, 2025):

Hello @samroweemployinc,

We're currently reviewing our open issues and would like to verify if this problem still exists in the latest NetBird version.

Could you please confirm if the issue is still there?

We may close this issue temporarily if we don't hear back from you within 2 weeks, but feel free to reopen it with updated information.

Thanks for your contribution to improving the project!

@nazarewk commented on GitHub (Apr 28, 2025): Hello @samroweemployinc, We're currently reviewing our open issues and would like to verify if this problem still exists in the [latest NetBird version](https://github.com/netbirdio/netbird/releases). Could you please confirm if the issue is still there? We may close this issue temporarily if we don't hear back from you within **2 weeks**, but feel free to reopen it with updated information. Thanks for your contribution to improving the project!
saavagebueno commented 2025-11-20 05:31:52 -05:00
Author
Owner
Copy Link

@samroweemployinc commented on GitHub (May 19, 2025):

Unfortunately we're not able to use the latest versions of Netbird because we don't have a single nameserver that can answer across all of our networks.

@samroweemployinc commented on GitHub (May 19, 2025): Unfortunately we're not able to use the latest versions of Netbird because we don't have a single nameserver that can answer across all of our networks.
saavagebueno commented 2025-11-20 05:31:52 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (May 19, 2025):

Hello @samroweemployinc I'm not sure I got it. The latest version would require a routing peer routing traffic to your bucket domain. With recent versions we've added a few DNS improvements, like TCP listener to ensure DNS queries with large responses, like the bucket ones, are handled by the client.

@mlsmaycon commented on GitHub (May 19, 2025): Hello @samroweemployinc I'm not sure I got it. The latest version would require a routing peer routing traffic to your bucket domain. With recent versions we've added a few DNS improvements, like TCP listener to ensure DNS queries with large responses, like the bucket ones, are handled by the client.
saavagebueno commented 2025-11-20 05:31:52 -05:00
Author
Owner
Copy Link

@samroweemployinc commented on GitHub (Aug 20, 2025):

@mismaycon Sorry for the delay. Perhaps we've misunderstood but since moving DNS resolution to the peers we've been under the impression that we can't upgrade, so all of our clients are on 0.34.1. Do we have the wrong idea that we need a single DNS server that can answer all questions?

Our company has several acquisitions that have their own private DNS servers/Route53 that know nothing about each other so if I'm on multiple routes, how does NB know which peer to use to resolve a given name?

I'd love it if we're wrong about this.

@samroweemployinc commented on GitHub (Aug 20, 2025): @mismaycon Sorry for the delay. Perhaps we've misunderstood but since moving DNS resolution to the peers we've been under the impression that we can't upgrade, so all of our clients are on 0.34.1. Do we have the wrong idea that we need a single DNS server that can answer all questions? Our company has several acquisitions that have their own **private** DNS servers/Route53 that know nothing about each other so if I'm on multiple routes, how does NB know which peer to use to resolve a given name? I'd love it if we're wrong about this.
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 triage-needed waiting-feedback
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#1506
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?