You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Create an s3 simple site and allow only private IPs via BucketPolicy ( "Condition": {"IpAddress": {"aws:SourceIp": [...
Create a name-based route for that site
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
The text was updated successfully, but these errors were encountered:
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:
"Condition": {"IpAddress": {"aws:SourceIp": [...
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
The text was updated successfully, but these errors were encountered: