TeamAmaze / TeamAmaze/AmazeFileManager
IPv6 does not work for SMB
Open
Nobody has claimed this yet.
Area-FTP
Area-SMB
Area-Ssh/Scp/Sftp
Issue-Feature
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
my network configuration
Works:
- ipv4
- hostname alone
Fails:
- hostname.domainname: fails with a toast (oosp something went wrong)
- ipv6 (no bracket): cannot submit, "add" button does nothing
- ipv6 (with bracket): fails with a toast (oosp something went wrong)
Originally posted by @Palatis in #4420
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the SMB connection attempts described: hostname.domainname, an unbracketed IPv6 address, and a bracketed IPv6 address. Trace the Android/Kotlin path used when submitting the host and compare it with the working IPv4 and hostname cases; done means valid IPv6 SMB entries can be submitted and connect without an error toast.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100