mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[GH-ISSUE #2424] [FR] Resolve IPv4/v6 Only Option #1197
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#1197
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @jyxjjj on GitHub (Feb 27, 2024).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2424
Version of s3fs being used (
s3fs --version)Version of fuse being used (
pkg-config --modversion fuse,rpm -qi fuseordpkg -s fuse)Kernel information (
uname -r)6.6.13-200.fc39.x86_64GNU/Linux Distribution, if applicable (
cat /etc/os-release)How to run s3fs, if applicable
s3fs syslog messages (
grep s3fs /var/log/syslog,journalctl | grep s3fs, ors3fs outputs)Details about issue
CURL Has an option
force_ip_resolvecan provides withv4orv6.I want commandline or configuration file support this for let CURL only resolve some IP addresses.
I can only access R2 with IPv4 because some Firewall or Dynamic IP Bind Rules.
@ggtakec commented on GitHub (Mar 6, 2024):
@jyxjjj Thanks for your request, and I will look into implementing it.
@ggtakec commented on GitHub (Mar 10, 2024):
@jyxjjj I created PR #2432.
That code can add the
ipresolveoption and solve the request of this issue.If you can, please try to use that code.
@ggtakec commented on GitHub (Mar 17, 2024):
@jyxjjj #2432 was merged, please try to use it, if yo can.
@jyxjjj commented on GitHub (Mar 17, 2024):
Oh thank you, i still need my upstream for an update. I do not have the permission to using softwares that not in upstream. Sorry I didn't notice your mention.
@jyxjjj commented on GitHub (Dec 27, 2024):
My upstream finally upgraded it and now I can finally use it.
No issues found so far:
Thank you.